Three taps of hunting for the step they left. Every drop here is a customer you already paid to acquire.
What Strait does
Opens the KYC step itself; the reference rides in the link, the details stay in your app.
2SMS in India
A new short domain for every campaign.
What it costs you
Each one has to be added to your DLT template before the SMS can go out, or the message is blocked.
What Strait does
Your links live on your own workspace subdomain: register it once and every link fits.
3Your security review
Nobody can say where tap data goes.
What it costs you
The review stalls, and the launch waits with it.
What Strait does
Row-level security, roles, signed webhooks, and a data-location box that answers in one glance.
/ 03CHANNELS· WHERE YOUR LINKS LIVE
One link, wherever you send it
Every place below runs through the same Strait link, and every tap lands on the screen it points to. Channels are counted on their own, even without UTM tags where the app can be recognised.
SMS
KYC and payment reminders
hilltop.strait.link/kyc
WhatsApp
EMI and bill nudges
hilltop.strait.link/emi
Push
Offers and limits
hilltop.strait.link/offer/limit
Email
Statements and offers
hilltop.strait.link/offer/transfers
Print
QR at a partner counter
hilltop.strait.link/partner/qr
Journeys
Drop people back where they left off
Finish KYC
A reminder SMS opens the document step itself, not the home screen and three taps of hunting.
Pay a bill or an EMI
The link carries the bill reference in its path or parameters, and your app opens directly on the payment screen.
Claim an offer
Campaign links open the offer screen and expire on the day the offer ends, with a clear page instead of an error.
Refer a friend
Invite codes ride along with the link, through the install on Android. See the referrals page for what is coming next.
Controls
What your security review will ask
Separated workspaces
Postgres row-level security keeps each workspace’s data apart in the database itself.
Roles and two-factor sign-in
Owners, admins, members and read-only viewers. Any member can turn on an authenticator code, and then the database refuses a session without it.
Keys with limited powers
The publishable key in your app can resolve links and report opens, and nothing more. Secret keys stay on your server and are stored hashed.
Audit log and signed webhooks
Changes to links, keys and settings are recorded with who made them. Webhooks carry a timestamped HMAC signature.
Less personal data
We keep part of an IP address, store app opens without query strings, and collect no names, phone numbers or advertising IDs from people who tap.
If we stop, your links don’t
Export every link and tap on any plan, plus a Cloudflare Worker you deploy yourself, which keeps links on a domain you own redirecting without us (custom domains: live on Starter and up).
Where data lives
Database in Singapore, link server in the US, taps answered from Cloudflare’s edge. No India region yet, and no payment or KYC data is stored.
A written breach promise
Notification within 6 hours of confirming an incident, and a report to CERT-In in the same window. The DPA is on the website, and we countersign it on request.
In messages
Built for links sent by SMS in India
Your links live on your own subdomain, so you add one domain to your DLT template and your links, and nobody else’s, pass. If one link is ever abused, it can be switched off on its own without touching the rest of your workspace.
Keep personal data out of the link itself: put a reference in the path and look the details up in your app after it opens.
In the dashboard
Make a link in one form, no code
app.straitlink.in
New link. Make a link in the dashboard: a short path, where it goes, optional tags and UTM fields. Demo workspace, sample data.