About
We build one thing: iPhone Safari browsers in the cloud.
Use one yourself in the desktop app, run it from your code, or hand the job to an AI agent. Either way, websites see Safari on an iPhone. We compare what websites can measure against real iPhones. Any difference counts as a bug in the engine.
What we build
Built in, not bolted on.
What a website measures about the browser comes from the engine itself, and we test it against real iPhones. We add no script to a page to change what it reads. See how it works →
Why we started
Start from Safari, not a disguise.
Mobile automation used to mean a desktop browser dressed up as a phone, and every trick made it less like Safari. So we started with Safari's engine. We picked iPhone first because it matters most for mobile shopping, testing and account work.
Your data
Your data, plainly.
Where your data lives
Your account data lives on our EU servers. Sessions run on Macs in data centres in the US and the Netherlands. Stored files, like avatars and each profile's encrypted browser data, use a storage network that can copy them outside the EU. Every outside company that handles your data (our sub-processors), where it runs and the legal basis for each transfer is on our sub-processors page.
What we keep, and what we don't
Live video and the network log are never stored. AI sessions keep a transcript of your messages and the AI's replies, with card numbers we recognise, saved logins, and passwords or codes typed into password fields masked. We don't sell your data, and we don't train models on it without your separate consent. We keep a short record of each browser session for 90 days. Our privacy policy lists every category in full.
Moves like a person
Touch, scrolling and typing move at a person's pace, with pauses between them. You pick the pace for each session. Save a finished AI agent session as a saved task: a readable record of what the agent did, which you can view or delete.
Operating commitments
What we promise to do.
How we change vendors (GDPR Art. 28(2))
Sub-processors are the outside companies that handle customer data for us. Section 3.4 of our data processing agreement sets when adding or replacing one takes effect and, after Launch, the notice we give: a dated notice on /legal/sub-processors (the list is also at /trust/sub-processors), and by email as well if you ask at [email protected]. You can object to a new sub-processor on reasonable data-protection grounds. If we can't find another way, you can end the affected service without penalty and get back the unused part of what you prepaid.
Export your audit log and profile settings any time.
Export your audit log as CSV or JSON, and each profile's settings as JSON through the API, any time. Self-Hosted Enterprise contracts include source escrow, set up with your contract. Full details: the FAQ "What happens if Driftstack as a business goes away?"
How we publish incidents: /trust/incidents.
Company facts
Who you're dealing with.
- Entity
- Driftstack, a sole proprietorship (eenmanszaak) registered with the Dutch Chamber of Commerce (KvK) under number 42064799
- Headquarters
- Netherlands
- Funding
- Independent — customer-funded
- Sub-processors
- /trust/sub-processors
- Contact
- [email protected]
Ready when you are
Want to try it?
7-day free trial. No card needed.