Privacy Policy
Last updated November 6, 2026
This privacy policy in short
- We keep what it takes to sign you in, bill you and show you your test results, and nothing for advertising.
- Page text and screenshots go to an AI model through a model gateway we run. We do not use them to train anything.
- Test-account passwords are encrypted and never reach the AI.
- Screenshots are deleted after 30 days on Free and 90 days on Starter and Pro, and everything goes when you delete an app or your account.
- Launch check reports are unlisted, use no AI and are deleted after 30 days.
- You can ask for a copy of your data, or for its deletion, at any time.
1. About you
- Your account: your email address, plus your name and picture if you sign in with Google, used to sign you in and to reach you about payments and support.
- Email sign-in: a keyed hash of each one-time code (it expires after 10 minutes) and of the IP address that asked for it, kept 7 days to limit abuse.
- Your session: a random token in a cookie; the database stores only its hash.
- Plan, credits and purchases: your plan and renewal date, how many credits you have, what used them, and for each payment the order number, product, amount and date.
- API keys: a name you choose, when each key was created and last used, and a hash of the key. The key itself is shown to you once and never stored.
- Chat: the messages you exchange with TestRuna about each app.
- Support: the emails you send to our support address and our replies.
- Visits: pages viewed, referrer, browser, country (from your IP address, which is not stored) and where people click on public pages, counted with Umami on our own server, without cookies. Do Not Track turns it off.
2. About the apps you test
- The address, the description you give us and your test settings, including a monitoring schedule. For a deploy hook we keep only a hash of its secret URL, and when it was last called.
- Requirement documents and test cases: documents you upload when adding an app (Word, PDF, Markdown or text), with the text recognized in their images, the sections you choose to use, and the test cases written from them and from your pages, with your edits.
- What our browser sees: screenshots, the text and structure of pages, console errors and the addresses of failed requests, plus the steps it recorded for each test.
- Test accounts: if you add one, its password (and its authenticator secret, if the account asks for two-factor codes) is encrypted (AES-256-GCM) before it is stored. It is typed into your app's sign-in page (or the hosted one it uses, such as Auth0) by our browser, or used to work out the code, and is never shown to the AI or to you again. The browser session created with it is deleted when the run ends. Checking an account before you add the app stores nothing.
- Launch checks: the address you checked, the report (score, the problems found with any keys masked, and the files and links they affect) and two screenshots of the page. To limit abuse we also store, with each check, a keyed hash of the IP address it came from, never the address itself. A report is unlisted: anyone with its link sees the score and the kinds of problems, and only the person who ran the check sees the details, once signed in from the same browser.
- Studio: the requirements you type, the documents you upload (with the text recognized in their images), and the modules and test cases written from them, filed under the projects and systems you name, and the email addresses you invite to your team.
- Report recipients: email addresses you add to receive a summary after each run. Every report has a one-click link that takes that address off the app's list.
If the app you test shows personal data, it can appear in screenshots and page text. Use test accounts and test data where you can.
3. How AI is used
To design and run tests and to answer you, we send page text, screenshots of the page being checked, your app description and your chat messages to an AI model, DeepSeek V4.1 Flash. The requests go through a model gateway that we run ourselves, which passes them on to the model provider. Passwords of test accounts are replaced with placeholders before anything reaches a model. The requirement documents you upload, when adding an app or in Studio, go the same way, images included, to read them and write tests, modules and test cases.
Some failed checks get a second opinion from another model, TypeSafe's Jev, asked at TypeSafe directly, or through OpenRouter when TypeSafe cannot answer. That request contains the expected result, the page address and the page text, not screenshots.
We do not use your apps, results or messages to train any model. The free launch check uses no AI at all: its findings come from fixed rules run on our own servers.
4. Who else processes data
| Service | What for |
|---|---|
| Sign-in with Google, if you use it: we receive your email address, name and profile picture, never your password. | |
| Railway | Hosting of the app, the database and stored screenshots (servers in Singapore), and of the browsers that test your app and of the service that reads the requirement documents you upload and runs Studio (in the eastern United States). |
| Our model gateway and the AI model provider behind it | Page text, screenshots and your messages, to design tests, run them and answer you; the requirement documents you upload, to read them (images included) and write tests and test cases. |
| TypeSafe, and OpenRouter as a backup route | A second opinion on some failed checks from TypeSafe’s Jev model, asked at TypeSafe directly, or through OpenRouter when TypeSafe cannot answer. Receives the expected result, the page address and the page text, not screenshots. |
| Waffo Pancake and Creem | Checkout, as merchants of record for purchases made through them: they receive the name, email, billing address or country and payment details entered on their checkout page, and send the receipt. We receive only the result. Payment card data is processed by a PCI-DSS certified payment processor and not stored on our servers. |
| Stripe | Card payments for earlier purchases and subscriptions, through our own payment service. Stripe receives your payment details; we receive only the result. |
| Cloudflare | DNS, forwarding of email sent to our support address, and delivery of sign-in codes and test report emails. |
We do not sell or share personal data for advertising.
5. Cookies
| Cookie | Purpose | Kept for |
|---|---|---|
tr_session | Keeps you signed in. Holds a random token; we store only its hash. | 30 days |
tr_oauth_state, tr_next | Protect the Google sign-in against forgery and remember where to send you back. | 10 minutes |
tr_checks | Remembers which launch checks this browser ran, so their details open for you once you sign in. Holds only signed check ids. | 30 days |
All of them are needed for the site to work, so there is no cookie banner.
6. How long we keep it
- Screenshots and results of test runs: 30 days on Free, 90 days while you are on Starter or Pro. The latest result of each test stays until you delete the app, because the test map shows it.
- Apps, chats, recorded tests, the test cases written for an app and the requirement documents uploaded for it: until you delete the app or your account.
- Studio documents and test cases: until you delete them or your account.
- Launch check reports, their screenshots and the IP hash stored with them: 30 days.
- Email sign-in records: 7 days.
- Report recipients: until they unsubscribe, you remove them, or you delete the app. You can also switch an app's reports off at any time.
- Purchase records: kept after account deletion, because payments must stay reconcilable with the payment processor's records.
7. Deleting and getting your data
Delete an app from its Settings panel, and your whole account from the Billing page. Both take effect immediately and remove the screenshots from our storage; deleting your account also deletes your Studio work, except in teams others own. For a copy of your data, a correction, questions about this privacy policy or anything else (including the rights you have under the GDPR, the UK GDPR or California law), email support@testruna.com. We answer within 30 days.
8. Where data is processed
The app and its database run in Singapore; the browsers that visit the apps you test, and Studio, run in the eastern United States; and some of the services above process data in other countries, including the United States. By using TestRuna from elsewhere, including the EU and the UK, your data is transferred there under those providers' standard safeguards.
9. How we protect it
- Every connection to TestRuna uses HTTPS, and the database is not reachable from the internet.
- Session tokens and API keys are stored only as hashes, and test-account passwords are encrypted (AES-256-GCM).
- Test screenshots are served only to the account the app belongs to, and to us when we need to help with it or look into abuse.
- The browsers that visit your app run as a separate service that holds no database or payment credentials.
10. Email
We send no newsletters or marketing email. We write to you only about your account (sign-in codes included), payments or support, and run reports go only to the addresses added in an app's settings, each with a one-click unsubscribe.
11. Server logs
Our hosting provider records requests to testruna.com (IP address, browser, page and time). We use these logs to keep the service running and to investigate abuse; the provider deletes them after a short period.
12. Children
TestRuna is not meant for anyone under 16, and we do not knowingly collect their data.
13. Changes to this privacy policy
When this privacy policy changes, the date at the top changes too. Significant changes will also be announced in the app.
14. Questions about this privacy policy
Write to support@testruna.com from the email address of your TestRuna account, so we can match the request to it.