LimitedImplementation, done for youLearn more
Security

How Snapflow handles your product and data

Snapflow signs in to your product with a demo account you give it, to take screenshots for your help center. This page is for whoever has to say yes to that: what we store, what the agent does in your app, and where your data goes.

One screenshot session
  1. Stored encryptedThe demo account's password, AES-256-GCM
  2. A fresh browserIsolated, nothing carried over
  3. Signed in by codeThe password never reaches an AI model
  4. Stops before risky buttonsDeletes, payments, plan changes, invites
  5. Screenshot, then closedThe browser is thrown away

Encrypted at rest

Passwords are encrypted with AES-256-GCM and only decrypted inside a browser session, to sign in.

Typed by code

Passwords are never sent to an AI model and never shown again after saving.

No irreversible clicks

The agent never confirms a deletion, a payment, a plan change or a message to other people.

A fresh browser every time

Every session runs in a new browser that is closed when it's done. Not even a cookie carries over.

Everything logged

Every run and every change is in your workspace's Activity log, with who started it.

Yours to delete

Delete a demo account or a help center and its data goes with it. Closing your workspace deletes everything.

On this page

The demo account

Give Snapflow a dedicated account, not a person's. Its data appears in your screenshots, so it should hold realistic, tidy sample data rather than real customers. Add one account per role your articles cover (an admin, a member, a free plan) and Snapflow picks the right one for each screenshot.

Snapflow signs in with a username and password. It can't complete single sign-on or two-factor prompts, so the demo account needs a password and no second factor. Keep its access to what your articles show.

How we store sign-in details

  • Encrypted at rest with AES-256-GCM. The key is held in our servers' configuration, never in the database next to the data it protects.
  • Decrypted only by the background job that signs in, for the length of that browser session. The dashboard never shows a saved password again.
  • Typed into your sign-in form by code. Recorded sign-in steps keep a placeholder, not the value, and no password is ever part of what an AI model sees.
  • Deleting a demo account deletes its sign-in details. You can do that at any time.

What the agent does in your app

To take a screenshot, the agent follows the steps in your article: it opens pages, clicks through navigation, opens dialogs and fills forms, the way a customer would.

It will

  • Opens pages and clicks through navigation
  • Opens dialogs and menus
  • Fills in forms the article describes

It never clicks anything that

  • Deletes anything
  • Spends money or upgrades
  • Changes a plan
  • Sends invites or messages
  • Confirms a permanent removal

Before every click it reads what it's about to press. Anything that deletes, spends money, changes a plan or sends something to other people (deleting a workspace, upgrading, sending an invite, a “Confirm” in a dialog that says it will permanently remove something) is never clicked. The check runs in our code, not in the AI's instructions, so it can't be talked out of it. The screenshot is taken of the screen just before.

An article that shows saving a setting can lead the agent to save it, so use an account whose sample data you don't mind it changing.

When you add a demo account, Snapflow also explores your app as it, so it knows which screens exist. Exploring only opens links. It never clicks buttons or submits forms, and it skips anything that signs out, deletes, invites, exports, sends or touches billing.

Screenshots and what's public

Each screenshot gets a permanent address on screenshots.usesnapflow.com so you can embed it in your help center. Like any image in a public help center, anyone with that address can view it. Earlier versions are kept in your workspace so you can switch back; they aren't served at the permanent address.

Where data goes

We use these providers to run Snapflow, through their business offerings. Article text and screenshots of your app are sent to the AI providers to plan and take screenshots; sign-in details never are.

Supabase

Database, file storage and sign-in to Snapflow

Vercel

Hosts the Snapflow dashboard

Railway

Runs the background jobs, including the headless browser that re-takes screenshots

Browserbase

The cloud browsers the agent 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

Slack

Our internal notifications, for example when someone asks for a pilot or runs an audit

Your controls

  • Delete a demo account, and its sign-in details, whenever you like.
  • Remove your help center to delete its articles and every screenshot made from it.
  • See every audit, screenshot run, re-take and change in the Activity log, with who started it.
  • To close your workspace and delete all of its data, email us and we'll do it.

What we don't have yet

Snapflow is young. We don't have a SOC 2 report yet, and signing in to Snapflow itself uses email and password or Google, not your company's single sign-on. If your team needs a security questionnaire answered or a data processing agreement, email us and we'll work through it with you.

Contact and reporting a problem

Questions, a questionnaire, or something you think is a vulnerability: daniel@usesnapflow.com.