Privacy policy
- Effective
- 24 September 2026
- Provided by
- Gruvi Software Inc.
We email workspace owners at least 30 days before a change to how we use personal information takes effect. Other changes update the date above.
Summary
#summaryLink to SummaryThe points that matter most, in brief. Each section below also opens with a one-line summary. The full text is what applies.
- We collect what you give us, what Rehearsal records while it tests your app, and a few technical details such as the IP address you sign in from.
- Passwords for test accounts are encrypted. The app never shows them again, and they never reach the AI model.
- An AI model run by Microsoft reads your chat messages and the pages our browser visits. We do not use your content to train AI models.
- We do not sell your personal information or use it for advertising. This website uses Google Analytics and Microsoft Clarity to see how it is used. They set cookies, and they do not know who you are.
- Our GitHub App never asks GitHub for the files in your repositories.
- To see, correct, export or delete your information, write to hello@rehearsal.dev.
1. Who we are
In short: Rehearsal is made by Gruvi Software Inc., and we are responsible for your information.
Rehearsal is made by Gruvi Software Inc., a Delaware corporation. In this policy, "we", "us" and "our" mean Gruvi Software Inc.. "You" means anyone who visits our website or uses Rehearsal.
We decide how and why your account, billing and usage information is used, so for that information we are the controller under data protection law. The section on our role for workspace content explains the one case where we act for a customer instead.
Gruvi Software Inc. also makes Gruvi, a separate product with its own privacy policy. This policy covers Rehearsal only.
2. What this policy covers
In short: The website, the app, the CLI, the GitHub App, the test inbox and our emails.
This policy covers:
- our website at rehearsal.dev;
- the Rehearsal app at app.rehearsal.dev, and the API behind it;
- the Rehearsal command line tool (the CLI) and the tunnel it opens to your computer;
- the Rehearsal GitHub App;
- the test inbox, which receives email for your tests;
- the emails we send you.
It does not cover the apps you test with Rehearsal, or services you connect to it, such as GitHub or Vercel. Their own policies apply to them.
Our role for workspace content
A workspace can hold personal information about people other than its members. A screenshot of your app may show a customer's name. A file you upload may contain an address. A test account may use a colleague's email address.
We handle that information only to run Rehearsal for the customer who owns the workspace, and only as they instruct. For it, the customer is the controller and we are their processor. If your information is in someone else's workspace, contact them first. We will help them answer you.
3. Information we collect
In short: What you give us, what Rehearsal records while it tests, and a few technical details.
The table lists each kind of information, where it comes from, why we need it and how long we keep it. The retention section gives more detail on deletion.
Where it comes from
- From you, when you sign up, set up a workspace, chat with Re:agent or upload a file.
- From Google, if you sign in with Google: your name, email address and profile picture. We ask Google for nothing else.
- From GitHub, if you install our GitHub App: the repositories you choose and events about their deployments, pull requests and pushes.
- From Stripe, if you pay: whether a payment succeeded, and your subscription.
- From the apps you test: whatever those pages show while our browser visits them.
- From your browser: your IP address and browser type with each request, and your rough location (the city) when you sign in.
What not to give us
Rehearsal is built for test accounts and test data. Please do not give it real customers' accounts, production passwords, payment card numbers, health information or other sensitive personal information. If a page you test shows such information, it will appear in the evidence Rehearsal records.
4. How we use information
In short: To run Rehearsal, bill you and keep it secure. Never for advertising, and we never sell it.
We use your information to:
- run Rehearsal: sign you in, drive the browser, write and run your tests, and show you the results;
- send the emails the service needs, such as sign-in codes, run reports and invoices;
- bill you and keep the records tax law requires;
- keep Rehearsal secure, prevent abuse and investigate problems;
- answer your questions and act on your feedback;
- understand how Rehearsal is used, from counts and logs, so we can fix and improve it;
- comply with the law and enforce our terms.
We do not sell your personal information, and we do not use it for advertising. We do not make decisions about you based only on automated processing that have legal or similarly significant effects.
Emails we send
We send email about your account and the service: sign-in codes, invitations, alerts about new sign-ins, run reports, and notices about your plan, free week and usage. Stripe sends invoices and receipts. We do not send marketing email.
You choose which run reports you get in your settings.
Legal bases
If you are in the European Economic Area, the United Kingdom or Switzerland, the law requires a legal basis for each use.
5. AI processing
In short: A Microsoft-run AI model reads your chat and the pages we visit. Nobody trains models on it.
Re:agent, the assistant in the app, uses an AI model to explore your app and create tests. A second AI step turns what Re:agent found into a Playwright test. Short AI calls also name your chats and tidy up dictated speech.
What the model receives
- the messages you write in the chat, and any files or images you attach;
- the name and email address of the test account Re:agent signs in with;
- the audio of your voice when you dictate a message, so it can be turned into text;
- for each page our browser visits: its address, its title, a text outline of what is on it, and the last few errors and failed requests the page reported;
- the contents of files your app offers for download, when Re:agent checks one;
- emails in the test inbox that Re:agent reads, including any codes and links in them;
- the name, type and size of files you uploaded for tests, but not their contents;
- when a test is written, the flow Re:agent found and what Playwright reported for each attempt.
The model never receives the password of a test account. The section on test accounts explains how.
Who runs the model
All of these calls go to Azure OpenAI in Azure AI Foundry, a Microsoft service. The models are made by OpenAI and run in Microsoft's cloud. We do not send your content to OpenAI directly, or to any other AI provider.
We ask Microsoft not to store responses for later use. Microsoft's terms for this service say that prompts and outputs are not used to train its models or OpenAI's, and are not shared with OpenAI. Microsoft may keep them for up to 30 days to detect abuse.
Training
We do not use your content, your tests or your evidence to train AI models, and we do not let anyone else do so.
6. Test accounts and secrets
In short: Passwords are encrypted, never shown again, and never reach the AI model or a test file.
Re:agent signs in to your app the way a person would, with a test account you give it. Please use test accounts made for testing, not a real person's account.
- A password you enter in the test account form is encrypted before we store it, with AES-256-GCM. The app never shows it again, to you or to any other member.
- The AI model never sees it. The model types a placeholder, and our systems put the real password in at the moment of typing. Nothing else can be typed into a password field.
- The generated test does not contain it. The test reads the password when it runs, and we write it down as a placeholder in every step we store.
- Codes and links from the test inbox are handled the same way: what we keep says
{{code}}or{{link}}, not the code itself. - The browser that runs your test does receive the password, because it has to type it into your app.
Secrets such as a Vercel deployment protection bypass are stored the same encrypted way. You can remove a test account or a secret at any time.
One limit: if you type a password into the chat yourself, it becomes part of the conversation and the model reads it. Use the test account form instead.
7. Browser sessions and evidence
In short: Our browser records screenshots, video and traces, kept privately behind short-lived links.
Rehearsal's browsers run on our servers, not on your computer. While one works in your app, it records what happened so you can check it later:
- a screenshot at each step;
- a video of the session;
- a Playwright trace, which includes copies of the page and the network requests it made;
- the console messages and network log of the page;
- the result of each step and of the test.
This evidence shows whatever your app showed, including any personal information on screen. We store it privately. The app shows it through links that stop working after a short time, one hour by default.
While someone watches a browser live, we stream pictures of the page to them. The live stream is not recorded separately and is not stored.
Who can see it
A browser you open from a chat is private to you until it produces a test flow. From then on, workspace members who can view the project can see it. Evidence from test runs is visible to members who can view the project.
8. The test inbox
In short: Email sent to test addresses is kept as text for 7 days, then deleted.
Rehearsal can give a test account its own email address, so a test can read sign-up and sign-in emails.
- Amazon Simple Email Service receives the mail for us in the United States. We delete the original message from Amazon's storage as soon as we have read it.
- We keep the sender, the subject, the text of the message (up to 64 KB), and the codes and links found in it. Attachments are dropped unread. HTML is turned into text and not kept.
- We refuse spam, viruses, automatic replies and messages over 1 MB.
- We never forward, reply to or display these emails outside your workspace.
- Messages are deleted after 7 days. An address stops accepting mail 30 days after it was made.
9. The CLI and the local tunnel
In short: The tunnel passes traffic between our browser and your computer. We do not store that traffic.
The CLI runs on your computer. You sign it in by approving it in the app. It then keeps a credential in a file that only your user account can read. The credential works only with Rehearsal and expires after 30 days.
To test an app on your own computer, the CLI opens an encrypted connection from your computer to our tunnel service. While it is open, our browser reaches the local address you chose through it. You close it by stopping the CLI.
- Requests from our browser, and your app's answers, pass through our tunnel service. It does not log or store them. We keep the tunnel's name, the local addresses it may reach, who opened it and when it expires.
- Your terminal shows each request as it passes: its method, its path without the query string, its status and how long it took. That list stays on your computer.
- Runs against a local app keep screenshots and video, but no Playwright trace.
- The credentials the tunnel uses never reach the AI model, a generated test or the evidence.
We publish the CLI through npm. When you install it, npm's own privacy policy covers the download.
10. GitHub
In short: The GitHub App reads deployments and posts checks. It never asks for your source code.
Connecting GitHub is optional. If you install the Rehearsal GitHub App on repositories you choose:
- We receive events about deployments, pull requests and pushes, and we post a check with each run's result.
- We store the repository names and IDs, commit identifiers, pull request numbers, deployment addresses and the checks we posted.
- GitHub requires read access to repository contents for us to receive push events. We never ask GitHub for your files, and we do not read your source code.
- When you link your GitHub account, we do not ask for your email address and we do not store GitHub's access token.
- Check results appear on GitHub to anyone who can see the repository. We never put links to evidence on GitHub.
You can uninstall the app from GitHub at any time.
12. International transfers
In short: Your information is stored in the United States, under safeguards for European data.
We are based in the United States, and we store your information there. If you use Rehearsal from elsewhere, your information travels to the United States. Some providers in the table above may process it in other countries.
When we transfer personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on the European Commission's Standard Contractual Clauses and the United Kingdom's International Data Transfer Addendum.
13. Retention and deletion
In short: Deleted items vanish from the app at once and from our systems within 30 days.
We keep information while we need it to run Rehearsal for you, and then delete it. The table of information we collect gives the period for each kind.
- Deleting something in the app. When you delete a project, test, file or other item, it disappears from Rehearsal at once. We delete it from our systems within 30 days.
- Deleting a workspace. The workspace and everything in it, including its evidence, disappear at once. We delete them from our systems within 30 days.
- Closing your account. Write to us and we will delete your account within 30 days. Work you did in a workspace stays with that workspace.
- Backups. Deleted information can remain in database backups for up to 35 days, and deleted files can be recovered by us for up to 14 days. After that they are gone.
- Records we must keep. We keep invoices and payment records for as long as tax and accounting law requires.
14. Security
In short: Encryption in transit and at rest, private evidence, and strict access checks.
No system is perfectly secure, but these protections are in place:
- Connections to Rehearsal are encrypted in transit.
- Our database and file storage are encrypted at rest by our cloud provider. Evidence and uploaded files are private and reachable only through short-lived signed links.
- Test account passwords and other secrets are encrypted with a key kept in a separate key vault.
- A generated test runs with only the settings it needs, never with our own secrets. The browsers that run tests hold no database access.
- Every request for workspace content checks that you belong to the workspace and have permission.
- Our logs leave out message contents, passwords, sign-in codes and session tokens, and shorten email addresses so they cannot be read.
We do not hold a SOC 2 or ISO 27001 certification. If a breach affects your personal information, we will tell you without undue delay, and the authorities where the law requires. To report a security problem, write to hello@rehearsal.dev.
15. Your rights
In short: You can see, correct, export or delete your information, and object to some uses.
Depending on where you live, you may have these rights over your personal information:
How to use them
- Many things you can do yourself: edit your profile, remove test accounts and files, delete projects and workspaces, and turn the improvement program on or off in your account settings.
- For anything else, write to hello@rehearsal.dev from the email address on your account.
- We may ask you to confirm your identity first. We answer within one month, or sooner if the law where you live requires it.
- We will not charge you or treat you differently for using your rights.
- If your information is in a customer's workspace, we will pass your request to that customer, as explained in our role for workspace content.
- You can also complain to the data protection authority where you live. We would like the chance to fix the problem first.
16. US state privacy rights
In short: California and other state residents have the same rights. We do not sell or share data.
If you live in California or another US state with a privacy law, you have the right to know what we collect, to get a copy, to correct it and to delete it. You can use an authorised agent. If we refuse a request, you can appeal by replying to our answer.
In the last 12 months we collected these categories, for the purposes in how we use information:
- identifiers, such as your name, email address and IP address;
- commercial information, such as your plan and invoices;
- internet activity, such as sign-in times and how you use the app;
- audio, when you dictate a message;
- the sign-in details of test accounts, which we use only to run your tests.
We do not sell personal information or share it for cross-context behavioural advertising, as those terms are defined in California law. We have not done so in the last 12 months.
18. Children
In short: Rehearsal is not for anyone under 16.
Rehearsal is a tool for work. It is not meant for anyone under 16, and we do not knowingly collect information from them. If you believe a child has given us personal information, write to us and we will delete it.
19. Changes to this policy
In short: We give workspace owners 30 days' notice of changes to how we use personal information.
When we change this policy, we publish the new version here and change the effective date at the top. If a change affects how we use your personal information, we email workspace owners at least 30 days before it takes effect.
20. Contact us
In short: Email, phone or post.
Write to hello@rehearsal.dev, call +1 (845) 478-8411, or send post to Gruvi Software Inc., 2810 N Church St STE 90490, Wilmington, DE 19802, United States.