How iPhone install matching works
Someone taps your link on an iPhone, installs your app from the App Store and opens it. This page explains, in plain words, how we find the screen they wanted, what we use to do it and what we don't.
On this page 9
Navigating, not tracking
iOS passes nothing through the App Store. So when your app opens for the first time, it has to ask us "which link was this?" with nothing in hand but what the phone looks like and the network it's on.
We use that only to open the right screen in the same app: the screen behind the link the person just tapped. It routes one tap. We don't build a profile, follow anyone across apps or websites, or use it for advertising, and the signals are gone within about 2 days.
You choose the method
Strait has two ways to do this on iPhone. You choose which to use, with two switches in Dashboard → Settings → iPhone installs:
| Method | What it does | What the person sees |
|---|---|---|
| Device matching | The link page notes a few device and network details for up to an hour, and the app's first open is matched to them (what we use). | Nothing: no prompt, no clipboard |
| Paste handoff (also called the clipboard boost) | Get the app copies a one-time link; the app reads it on its first open. Exact, single use, 24 hours. | iOS's "Allow Paste" prompt, or your app's Paste button |
Every combination works, and the dashboard shows a sentence for the one you picked:
| Device matching | Paste handoff | What happens on the app's first open |
|---|---|---|
| Off | Off | No deferred link on iPhone. People land on the app's home screen. Installs are still counted. |
| On | Off | Device matching only. If nothing matches, the app opens on its home screen. The clipboard is never read. |
| Off | On | Paste handoff only. No device details are kept. If the person doesn't allow the paste, the app opens on its home screen. |
| On | On | Device matching runs first. Only if it finds nothing does the app read the clipboard, so a device match never shows the paste prompt. |
Defaults. New workspaces start with both switches off, so nothing is matched until you choose. Workspaces created before 10 October 2026 keep the values they had.
No app release needed. The choice isn't built into your app. On its first open, the SDK asks our server /v1/match, and the answer carries your workspace's current choice. The SDK reads the clipboard only when that answer says paste handoff is on and device matching found nothing (or is off), and it doesn't keep the setting for later. So a change in the dashboard applies to versions already in the App Store, from the next first open (within about a minute).
What we use
When someone without your app taps Get the app on the link page in Safari, we save these signals with that tap. When your app opens for the first time, the SDK sends the same fields and our server compares them.
| Signal | Where it comes from | How we keep it |
|---|---|---|
| IP address | Seen by our server on the tap and on the first launch | Only as a keyed hash (HMAC-SHA256 with a server-side secret). The IP itself is never stored. |
| IPv6 /64 network | Seen by our server | Only as a keyed hash, like the IP |
| Network prefix (IPv4 /24 or IPv6 /48) and network operator number (ASN) | Seen by our server | As is |
| Screen size and pixel ratio | The browser, then the app | As is |
| Language and time zone | The browser, then the app | As is |
| iOS version (major) | The browser's user agent, then the app's | As is |
Phones often have two addresses (IPv4 and IPv6) and can use either one for the tap and the other for the first launch. So the Get the app page, and the app's first launch when nothing matched over IPv6, send the same fields once more to v4.straitlink.in, our IPv4-only address, so both sides can be compared on the same IPv4. It's the same data, kept the same way (a keyed hash of the IP), and a match made this way is never shown as certain. If your app's network traffic goes through an allowlist, allow v4.straitlink.in next to your link domain.
This is device data, and comparing it is a kind of device matching. We say so plainly so you can describe it accurately to your users and to Apple.
How long we keep it, and what it's used for
- A tap's signals can be matched for 1 hour. Our nightly cleanup erases them once that hour is a day old, so they're gone within about 2 days of the tap (at most 49 hours).
- They're used only to open the right screen in the same app that owns the link.
- One tap gives at most one match.
- When two taps look alike (for example two identical iPhones on one Wi-Fi network tapping different links), we refuse to match either of them rather than guess. The app then opens normally on its home screen.
What we never do
- No advertising, and no measuring of advertising.
- No sharing or selling of this data, and no data brokers.
- No linking across apps: a match only ever happens inside the workspace that owns the link.
- No advertising identifier (IDFA), and no reading of anything else on the phone.
Why there's no App Tracking Transparency prompt
Apple defines tracking as linking data collected in your app with other companies' data for targeted advertising or advertising measurement, or sharing it with data brokers (Apple: User privacy and data use). Install matching does none of that: the data stays with your workspace and is used only to open your own app's screen. So it isn't tracking under that definition, and the SDK doesn't ask for ATT.
To be honest about the other side: Apple's page on required-reason APIs also says that fingerprinting is not allowed, whether or not a user gives permission to track. ATT doesn't change that. Device matching sits close to that line, and Apple decides what counts, so there is a risk that App Review flags it. That's why the choice is yours: device matching is off for new workspaces, you can turn it on or off at any time, and paste handoff on its own gives an exact match only after the person pastes, with no device details kept. The dashboard shows this note next to the Device matching switch. Each customer decides what's right for their app.
The off-switch
Dashboard → Settings → iPhone installs → Device matching. It's off for new workspaces; workspaces created before 10 October 2026 keep the value they had. Each switch saves as soon as you flip it.
When you turn it off:
- The link page stops saving these signals, and our server stores none.
- Signals already saved for your workspace are erased.
- A first launch on iPhone gets no match, so the app opens on its home screen (unless paste handoff finds the link).
Android isn't affected: it uses the Google Play Install Referrer, which carries the exact link through the install (see Deferred deep linking).
The clipboard boost (paste handoff)
Paste handoff, which we also call the clipboard boost, gives an exact match instead of a signal match, but only when the person pastes. It's off by default. Turn it on in Dashboard → Settings → iPhone installs → Paste handoff; that one switch is all it takes. The SDK learns it from /v1/match on the app's first open, so there is nothing to change in your app. (React Native, Flutter and Unity apps pass a clipboard adapter once, so the SDK can read the clipboard when your workspace asks for it.)
The old SDK option clipboardBoost: true is deprecated and ignored: the dashboard switch decides. You can leave it in your code or remove it.
How it works:
- On the link page, Get the app also copies a one-time link to the clipboard. The link holds a random token. We store only a hash of it, it works once, and it expires after 24 hours.
- On the app's first launch, the SDK asks
/v1/matchfirst. If device matching is on and finds the install, the SDK never touches the clipboard and no prompt appears. Only if there's no match and the answer says paste handoff is on does the SDK check whether the clipboard probably holds a web link. iOS answers that without showing anything. If the server can't be reached, the SDK leaves the clipboard alone and tries again on the next launch. - Only if it does, the SDK reads the clipboard. This shows iOS's "Allow Paste" prompt. If the person allows it and the text is one of your handoff links, the SDK sends just the token to our server and the app opens the exact screen.
- Instead of the prompt, you can show Apple's Paste button (
UIPasteControlor SwiftUIPasteButton; the iOS SDK includesStraitPasteButton). Tapping it is the person's consent, and iOS shows no prompt.
The SDK never reads the clipboard unless your workspace has paste handoff on, and it sends nothing but a Strait handoff token. Anything else on the clipboard stays on the phone. If there's no token, or it was already used or has expired, the app gets the device-matching result. With both on, device matching runs first on the first launch and the clipboard is read only when it finds nothing, so most people never see the paste prompt. Both attempts count as one install.
App Store privacy label
A ready-made answer for App Store Connect → App Privacy, for the data the Strait SDK handles. It matches the SDK's privacy manifest (PrivacyInfo.xcprivacy). Add whatever else your own app collects.
| Data type | Purpose | Used for tracking | Linked to the user |
|---|---|---|---|
| Coarse Location (derived from the IP address) | App Functionality | No | No |
| Other Data (screen size, language, time zone, iOS version) | App Functionality | No | No |
| Product Interaction (link opens) | App Functionality; also Analytics if you use Strait analytics | No | No |
User ID (only if you call setUserId) |
App Functionality; Analytics | No | Yes |
- Used for tracking: No. Nothing is combined with other companies' data for advertising or shared with data brokers.
- Linked to the user: No for the first three, because Strait has no user accounts or identity: no names, emails, phone numbers or advertising IDs. If you join Strait data (for example the tap id on a purchase) to your own user accounts, answer "Linked to the user" accordingly.
- User ID: Yes, linked. If your app calls
setUserId, your own id for the signed-in user goes with later events to yourapp.eventwebhook. Emails and phone numbers are hashed on the phone and never sent raw. The iOS SDK's privacy manifest declares it from 0.11.8. If you don't callsetUserId, leave User ID out. - The clipboard boost sends only a one-time token that Strait created, not the person's clipboard contents.
Our full data list is in the Privacy policy.