Where your data goes
The services Snapflow runs on, what the AI services see, and why published screenshots are public.
Written by Daniel Nadasan
Updated 1 min read
On this page
Snapflow runs on a small number of other companies' services. This article lists each one and what it handles.
The services Snapflow uses
| Service | What it does |
|---|---|
| Supabase | Database, file storage and sign-in to Snapflow |
| Vercel | Hosts the Snapflow dashboard |
| Railway | Runs the background jobs, including the browser that re-takes screenshots |
| Browserbase | The cloud browsers Snapflow uses to work out new screenshots and check sign-ins |
| Anthropic (Claude) | Reads articles and page screenshots to plan and take screenshots |
| Google (Gemini, through Browserbase) | Reads the page to find the buttons and fields a step mentions |
| Cloudflare R2 | Serves published screenshots at their permanent address |
| Stripe | Payments. We never see or store card numbers |
| Resend | Sends Snapflow's emails |
| PostHog | Product analytics on the Snapflow dashboard |
What the AI services see
To plan and take screenshots, the text of your help center's articles and pictures of your product's screens are sent to the AI services above.
Sign-in details never are. A demo account's password is typed into your sign-in form by code. See How demo account passwords are stored.
What's in a screenshot
A screenshot shows what the demo account sees. That's why we recommend a demo account with sample data: real customer data never needs to reach Snapflow at all.
Published screenshots are public
Each screenshot you publish has a permanent address that anyone with the link can open. That's what lets it show in your help center. Don't publish a screenshot of something your help center's readers shouldn't see.
Security has more detail, and the privacy policy covers personal data.
Did this answer your question?
Still stuck?
Email daniel@usesnapflow.com and you'll hear back from Daniel, who built Snapflow.