Questions
The things people ask first.
Including the ones with an awkward answer. If a question you have is not here, the documentation is more detailed and [email protected] reaches a person.
- What is a deep link?
- A link that opens a specific screen inside a mobile app rather than the app’s home screen — a particular product, order or article. On iOS these are called universal links: an ordinary https:// address that opens your app when it is installed and a web page when it is not.
- Is this a Firebase Dynamic Links alternative?
- It is built for the same job. Google shut Firebase Dynamic Links down in August 2025, which left small app teams choosing between enterprise attribution suites and building link handling themselves. We are the third option: self-serve, published pricing, and one thing done properly.
- What works today?
- Accounts and teams, apps with a permanent link host of their own, iOS and Android configuration with the files Apple and Google fetch, link creation, the redirect service, QR codes, deferred matching, install attribution, and the JavaScript SDK. Billing, webhooks and charts over time are not built. The changelog records what shipped and when.
- How much does it cost, and can I be charged today?
- Prices are published on the pricing page, starting at £0. They are provisional and billing is not switched on, so you cannot be charged today and nothing on the site is an offer.
- Do I need your SDK to use universal links?
- No. Universal links are an Apple mechanism: your app declares which domains it handles, Apple fetches a file from that domain, and the system opens your app. Handling the incoming link is a few lines against Apple’s own API. The SDK is for the parts Apple does not do — deferred linking after an install, and attribution — and it is optional.
- What is deferred deep linking, and how well does it work?
- Opening the right screen after somebody installs the app, rather than only when they already have it. When the link itself survives the install it is exact. When it does not, we fall back to matching, and matching is not certain: in our own simulation it matched 40.6% of installs with a 3.41% false positive rate, and on a busy shared network that became 48.7% matched with 19.17% wrong. Both figures are on the deferred matching documentation page, along with how to turn the guessing off.
- Does the SDK track my users?
- No. It reads no advertising identifier and collects no personal data. Matching uses coarse signals only — platform, a hashed IP address and a timestamp — held for sixty minutes and then deleted. There is no cross-app graph and no persistent device identifier shared with anybody. The one thing it can ask your user for is permission to read the clipboard, and only if you switch clipboard matching on, which is off by default.
- Where is my data stored?
- In the United Kingdom. The database is in London and every service we add has to be able to process data in the UK or EU, or we do not use it. The sub-processor list on this site is the current, complete one.
- Do you support Android?
- Yes. App Links, the assetlinks.json file Google fetches, and the Play Install Referrer, which makes a deferred install match exact rather than inferred — iOS has no equivalent. The integration in your app is the same five lines on both platforms. What we cannot measure yet is how often Google delivers the referrer in the wild, and the Android documentation says so rather than publishing a number we have not measured.
Start on the free plan.
One app, a thousand clicks a month, live and test environments, and two-factor authentication. No card, and no way to be charged while billing is switched off.