Privacy policy
What Walkthru collects when you scan or test a site, why, who processes it and how to take it with you or delete it. Emails, long numbers and typed values are masked in your browser before any AI model sees a page.
Last updated
The short version
- We collect what we need to run tests and show you reports. Nothing is sold, and there are no advertising or analytics trackers.
- Emails, long numbers and anything typed into forms are masked in your browser before a snapshot leaves it.
- Screenshots are deleted automatically after 30 days. Everything else is yours to export or delete at any time.
What we collect
Your account
Your email address, and the name and profile picture your sign-in provider (Google or GitHub) shares. Profile details you add in Settings, such as your business name, role, team size and website.
Test runs
The site address, the goal and test user you chose, and for each step: a text outline of the page (buttons, links, headings, visible errors and whether a form field is filled, never its value), the action taken, the test user's thoughts, and accessibility and page-speed measurements.
Up to eight screenshots per run of the tab being tested. Form fields are visually masked and Scout is hidden before each capture.
Instant Scans
The address you scan and the public pages we read from it. Your network address is used briefly to limit scans and is not stored with the report. If you give an email address for the report, it is used to send it and is not stored in our report database. Our email provider processes delivery under its own retention rules.
Weekly watch and competitor comparisons (paid plans)
The sites you choose to watch, when each was last checked and what changed, and the report of every check. For a comparison, the addresses you enter and the public pages we read from each of them, the same way a search engine reads a public page. We only read public pages of sites you do not own.
Test run safety log
For every test run we start or refuse: your account, the site's host name, whether it ran as a visitor or on your verified domain, the goal, and each action's type with the label of the control it used (for example "click: Pricing"). Never what was typed, never page text. It exists to investigate abuse and is kept 90 days, even if you delete the run.
Feedback and error reports
Messages you send us from Send feedback, with the page you were on. When the service fails, we record which part failed and the kind of error, never the content of your request.
API keys and deploy hooks
When you create an API key for the MCP server or a deploy hook for a watched site, we store only a one-way fingerprint (a SHA-256 hash) of it, never the key itself, plus its name and when it was last used. Scans your editor starts through MCP are saved as runs in your account like any other.
How we use it
- To run your tests and scans and to write, store and show your reports.
- To email a report when you ask for it.
- To keep the service working and safe, for example to enforce limits and investigate errors.
- To record how many AI tokens each run used, so we can keep prices sustainable.
AI processing
Test users and report summaries are generated by AI models from third-party providers. They receive the masked text outline of each page, the goal and earlier steps. They do not receive your password, cookies or the values typed into forms.
We do not use your runs to train models. Providers process requests under their API terms.
What the Chrome extension reads
Only the tab you start a test in, and only while the test runs. From that tab it reads a masked outline of the page (buttons, links, headings, visible errors and control labels, with emails, long numbers and typed values masked) and takes up to eight screenshots with form fields hidden.
It never reads the site's cookies, local storage, session storage or saved passwords, never reads your browsing history or other tabs, and never watches your network requests. An automated test fails our build if the extension's code ever touches those. It talks only to Walkthru's API and our database provider.
Who we share it with
Only the service providers that run Walkthru for us:
- Supabase
- Sign-in, database and private screenshot storage.
- Groq and Google (Gemini)
- AI models for test users and report writing. Google Gemini also answers questions asked to Scout in a team workspace: it then receives the question and that workspace's shared findings, report summaries and recent messages.
- OpenRouter
- Routes report-writing requests to the configured model provider. Requests include masked page text, the goal, earlier steps and scan findings.
- Google PageSpeed Insights
- Mobile speed measurements for the public address being scanned.
- Resend
- Sending reports by email, only when you ask.
A report becomes visible to others only when you create a public link for it, or share it into a team workspace, where that workspace's members can read it. Instant Scan reports have a public link by design. In a team workspace, the other members see your name and email address and what you post there.
How long we keep it
- Screenshots: deleted automatically 30 days after the run.
- Instant Scan report emails: not stored in our report database; our email provider processes delivery under its own retention rules.
- Run request replies: available for retries for 24 hours, then their cached contents are erased by expiry checks or the six-hour cleanup pass. Minimal request fingerprints remain until account deletion to prevent old retries recreating a run.
- API keys, deploy hooks and watched sites: kept until you revoke or remove them, or delete your account.
- Runs, steps and reports: kept until you delete them.
- Test run safety log: 90 days, then deleted automatically.
- Team workspace chat, comments and activity: kept until the author deletes a message or the owner deletes the workspace. When you delete your account, what you wrote in other people's workspaces stays, signed "Former member" instead of your name.
- Your account: kept until you delete it. Deleting it removes every run, report and screenshot, then the account itself.
Your choices and rights
From Settings you can download everything we hold about you as one file, and permanently delete your account. You can delete a single run from its report.
You can also ask us to access, correct or delete your information, or object to how we use it, by emailing [email protected]. We reply within 30 days.
Cookies and local storage
We do not use advertising or analytics cookies. Your browser stores your sign-in session, and the extension stores its connection to your account. Website sign-out asks the installed extension in this browser to disconnect before signing out. If that cannot be confirmed, we show a warning to disable the extension in Chrome. A disconnected or changed account stops further browser actions; an action or request already sent may finish. An unfinished server run can be ended from its original account's dashboard.
Private API session validation is cached for up to five minutes, never beyond access-token expiry. Supabase access tokens can remain valid until they expire even after sign-out. Signing out does not delete reports or remove public links or team access. Other browsers and devices have their own stored connections.
Security
Production traffic uses encryption. Private reports are restricted to their owner unless shared: public-link reports are readable by anyone with the link, and workspace reports by authorized members. Screenshots sit in private storage behind short-lived links. Read more on our security page.
Children
Walkthru is a tool for businesses and developers and is not meant for anyone under 16.
Changes and contact
If we change this policy in a way that matters, we will update the date above and tell signed-in users before it takes effect. Questions go to [email protected].