Contact

Tell us what you are integrating

Palms Links is sold as an annual subscription against a verified domain, so an enquiry is a conversation rather than a checkout. The more concrete you are about volume and destination hosts, the faster the answer is useful.

Your name Required

Work email Required

The reply goes here. We do not use it for anything else.

Organisation

Domain to be verified Optional

The domain the subscription will be bound to — usually where your destination pages live. It has to pass ownership verification before any key is issued.

What is this about?

Message Required

Useful to include: roughly how many links per month, whether destinations are on one host or many, and whether you need request signing or an IP allowlist.

Submitting stores your name, email, organisation, the domain you typed and your message, so the enquiry can be answered and so a later subscription can be traced back to how it started. The lawful basis is your own request, not consent — so there is no box to tick, and you can ask for the record to be deleted at any time. See the privacy notice.

How quickly you will hear back

Subscriptions, quotes, integration questions	Target: one working day
Vulnerability reports	Committed: five working days
Data-subject requests	Statutory: 30 days

Working days are Sunday to Thursday, Riyadh time. The first row is a target and not a contractual commitment: there is no on-call rota, no 24/7 desk and no published support SLA, and saying otherwise on a marketing page would be a promise nobody here can keep at three in the morning.

Write directly instead

General and subscriptions
info@palmslinks.io
Privacy and data-subject requests
privacy@palmslinks.io
Writing to this address is what starts the statutory clock — the form does not.
Security reports
security@palmslinks.io
Also published at /.well-known/security.txt. Please do not put vulnerability details in this form.

Already integrating?

If an API call is failing, the fastest possible message contains the request_id from the response, the key id (plk_live_… — never the secret) and roughly when it happened. That is enough to find the exact call in the request log. The error catalogue usually answers it before you need to write at all.