On this page 13 sections
- Report a vulnerabilitysecurity@straitlink.in
- Data Processing AddendumWe countersign on request.
- Live statusstatus.strait.link
Short answers for a vendor review
- What if the one person running Strait stops? Your links don't depend on us. On every plan you can export every link, every tap and a Cloudflare Worker you deploy on your own account, which keeps links on a link domain you own redirecting without us. It can't take over
strait.linklinks; on Starter and up your links can live on a custom domain you own. See Exporting your data. - Where is data stored? The database is in Singapore (Supabase
ap-southeast-1), and so is the link server (Render, since 22 October 2026); taps are answered from Cloudflare's global network. There is no India region yet. Details under Architecture. - What is stored? Links, and taps with coarse device details and a shortened IP prefix. No names, phone numbers, payment or KYC data, unless you put them in a link yourself, which we ask you not to do.
- Shared link domain? Each workspace has its own subdomain (
<handle>.strait.link). Abuse is against our Acceptable Use Policy, and an abused link or workspace can be switched off without touching anyone else's links. Custom domains are live on Starter and up. - Two domains? Both domains are ours: strait.link carries your links (and the API), and straitlink.in is our website and dashboard.
- A signed DPA? The DPA is on this site. We countersign on request. Email privacy@straitlink.in.
- Certifications and SLA? None yet; the list below says exactly what's missing.
Architecture
| Layer | What runs there |
|---|---|
| Cloudflare (global edge) | This website, the dashboard at app.straitlink.in, the status page, and every link domain (<handle>.strait.link). Simple redirects are decided at the Cloudflare location nearest the person tapping; everything else is passed on to our link server. |
| Link server and API | A Node.js service hosted on Render, in its Singapore region, next to the database (since 22 October 2026). It accepts requests only when they come through Cloudflare; a request sent directly to its host is refused. |
| Database and sign-in | Postgres and authentication on Supabase, in its Singapore region (ap-southeast-1). |
The full list of providers that process data for us is in the Privacy Policy.
Encryption
- In transit: every Strait address serves HTTPS only, and plain-HTTP requests are redirected to HTTPS. This website sends
Strict-Transport-Security(one year, including subdomains), so browsers that have visited it use HTTPS for straitlink.in and its subdomains without trying HTTP first. - At rest: the database is encrypted at rest by our database host, Supabase. Backups are encrypted separately (see Backups).
Access control
- Workspace isolation: each workspace's data is separated in the database itself, with Postgres row-level security, so a signed-in user can only read and change the workspaces they belong to.
- Roles: each member is an owner, admin, member or viewer. Viewers have read-only access: they can't create secret keys, see webhook signing secrets, or change webhooks.
- Robot check and confirmed emails: dashboard sign-up, sign-in and the resend-email forms use Cloudflare Turnstile, and our sign-in service refuses a request without a passing check. A new account works only after its email address is confirmed, and a password needs at least 10 characters, with a letter and a digit.
- Two-factor sign-in: any dashboard user can turn on an authenticator-app code (Settings → Security). Once it's on, the database itself refuses that account's data to a session that hasn't entered the code, so a stolen password alone isn't enough.
- Keys: secret keys (
st_live_…) are stored as a SHA-256 hash and shown once, when created. The publishable key (st_pub_live_…) that ships in apps can only resolve links, report app opens, match installs and send events; it can't create, change or read links. - Audit log: changes to links, keys, webhooks and settings are recorded by the database with who made them and what changed.
- Our own access to production systems is limited to the people who run the service.
Webhook signing
Every webhook is signed with your webhook's own secret. The X-Strait-Signature header carries a timestamp and an HMAC-SHA256 of the timestamp and the raw body (t=…,v1=…), so you can check that a request came from us and refuse old or replayed ones. See Verify the signature for working code in Node, Python and Go.
Harmful links
- Known malware sites are refused. Every destination is checked against the public URLhaus malware list, which we fetch every 3 hours and check against on our own server (no destination is sent to anyone else to check it), and against our own blocklist. The check runs when a link is created through the API, the dashboard or an import, when its destination is edited, and again when someone taps it: a tap on a listed destination shows a warning page instead of redirecting. We checked all three on the live service on 3 November 2026.
- Report a harmful link to abuse@straitlink.in. Links used for phishing, malware or spam are switched off under the Acceptable Use Policy.
Data minimisation
- IP addresses are never stored in full. We keep the network prefix only: the first three parts of an IPv4 address (a /24), or the first 48 bits of an IPv6 address. For iPhone install matching we also keep, until one day after the 1-hour match window, a shortened keyed hash (HMAC-SHA256, server-side secret) of the full address and of the IPv6 /64, plus the network operator's number (ASN).
- App opens are stored with the URL's host and path, never the query string.
- iPhone match signatures can be used for 1 hour, at most once, and are erased one day after that window ends. When two taps look alike, we match neither: we refuse rather than guess.
- Taps, opens, installs and events are kept for 13 months, then deleted by a nightly job.
- Webhook delivery history (status, attempts, your server's last answer, and the signed payload we sent) is kept for 30 days, then deleted by the same nightly job.
- We don't collect names, emails, phone numbers, advertising IDs or clipboard contents from the people who tap links (the optional iPhone clipboard boost sends only a one-time token we created, stored as a hash).
Details and every retention period are in the Privacy Policy.
Exporting your data
You can export all of your workspace's data at any time, on every plan: your links, every tap (joined to the app opens and installs it led to), every conversion event, and your webhook settings, plus a Worker that keeps links on a domain you own redirecting without us (custom domains are live on Starter and up). Webhook signing secrets are never included. Exports contain everything, so in the dashboard only owners and admins can download them; each download uses a one-time link that expires after 60 seconds. From a server, an export needs a secret key. See Export.
Deleting your account
In the dashboard, open Settings → Security & privacy → Delete my account, sign in again if asked, choose Email me a code, then type the 6-digit code we email to your address and your email. Your sign-in and email address are removed at once, and you leave every workspace. A workspace only you are in is closed (its links stop) and deleted for good after 30 days. If other people use a workspace you alone own, close it or ask support to make someone else an owner first, and cancel any paid plan first. We email you a confirmation.
Backups
- The database is backed up every night. Each backup is checked to be complete and to contain data, then encrypted with AES-256 before it's stored.
- Encrypted backups are stored as GitHub Actions artifacts and in Cloudflare R2 (Asia-Pacific region), and deleted automatically after 30 days. So data you delete can remain in an encrypted backup for up to 30 days after deletion.
- Restoring is a written procedure: a backup is always restored into a new, separate database, never over the live one. We rehearse it every quarter. The first rehearsal, on 12 October 2026, restored a nightly backup into a separate database and matched production exactly: every table, all 6,251 rows, every function and permission. Restoring the data took 3.6 seconds; a full restore into a new database project is estimated at 30 to 45 minutes. The rehearsal also found a permissions gap in our written restore steps, which we fixed the same day. A failed nightly backup alerts us by email.
- Support: a person answers every email. Replies within 1 working day, IST.
Incident response
If we confirm a security incident affecting your data, we will notify you without undue delay and within 6 hours of confirming it, report it to CERT-In within the 6-hour window the law requires, and send a detailed follow-up report within 72 hours. We email your workspace's owners. The email says what happened, what data is affected, and what we're doing about it. Service problems and outages are posted on the status page.
Reporting a vulnerability
Email security@straitlink.in. Please include:
- what you found and where (URL, endpoint or SDK);
- the steps to reproduce it;
- what an attacker could do with it.
Please give us reasonable time to fix it before you tell anyone else, and don't access other people's data, run denial-of-service tests or send spam while testing. Use your own workspace and links. Our contact details for researchers are also in /.well-known/security.txt.
What we don't have yet
We'd rather say this plainly than leave you to find out:
| What | Status |
|---|---|
| SOC 2 or ISO 27001 report | Planned. Not started. |
| Independent penetration test | Planned. Not done yet. |
| Uptime SLA | None yet. Live and past service health is on the status page. |
| Requiring two-factor for every member of a workspace | Planned. Today each person turns it on for their own account. |
| Single sign-on (SSO) | Planned for Enterprise. |
If you need answers to a security questionnaire, email security@straitlink.in.