ProductDevelopersGitHubDocs
Join the waitlist

Contents

  1. 1Who we are
  2. 2What this policy covers
  3. 3Information we collect
  4. 4How we use information
  5. 5AI processing
  6. 6Test accounts and secrets
  7. 7Browser sessions and evidence
  8. 8The test inbox
  9. 9The CLI and the local tunnel
  10. 10GitHub
  11. 11Sharing and service providers
  12. 12International transfers
  13. 13Retention and deletion
  14. 14Security
  15. 15Your rights
  16. 16US state privacy rights
  17. 17Cookies and browser storage
  18. 18Children
  19. 19Changes to this policy
  20. 20Contact us
PrivacyTerms

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 Summary

The 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

1. Who we are

#who-we-areLink to 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

2. What this policy covers

#scopeLink to 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

#our-roleLink to 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

3. Information we collect

#information-we-collectLink to 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.

The information we collect
InformationWhat it includesWhy we need itHow long we keep it
AccountWhat it includes Your name, email address, profile picture, and how you sign in: Google, an emailed code or a passkey. Profile pictures are stored at a web address anyone with the link can open.Why we need it To create your account, sign you in and contact you about the service.How long we keep it Until you close your account.
Sign-insWhat it includes IP address, city, browser and device type, and when each session started.Why we need it To keep you signed in, protect your account and email you when a new browser signs in.How long we keep it A session ends after 7 days without use. You can see and end your sessions in your account settings.
WorkspacesWhat it includes Workspace name and logo, members, their roles, and the email addresses you invite.Why we need it To run shared workspaces and permissions.How long we keep it Until the workspace is deleted.
Apps you testWhat it includes Names and addresses of your apps and their environments, and preview deployment addresses.Why we need it To know where to test.How long we keep it Until you delete them or the workspace.
Test accountsWhat it includes Usernames and email addresses, encrypted passwords, and test inbox addresses.Why we need it To sign in to your app the way a person would.How long we keep it Until you remove the account.
ChatsWhat it includes Messages you write or dictate, files you attach, Re:agent's replies and a record of each step it took.Why we need it To explore your app and create tests with you.How long we keep it Until you delete the chat or the workspace. We do not keep the audio of dictation.
Flows, tests and resultsWhat it includes The steps Re:agent found, the Playwright test written from them, and the result of every run.Why we need it To run your tests again and show their history.How long we keep it Until you delete them or the workspace.
EvidenceWhat it includes Screenshots, video, Playwright traces, console messages and network logs.Why we need it To show what happened in each test and why it failed.How long we keep it 30 days for passing runs and browser sessions, 90 days for failed or blocked runs.
Uploaded filesWhat it includes Files you upload for tests to use.Why we need it To use them in your tests.How long we keep it Until you delete them or the workspace.
Test inbox emailWhat it includes Sender, subject, text, and the codes and links in emails sent to test addresses.Why we need it To let tests read sign-up and sign-in emails.How long we keep it 7 days.
GitHubWhat it includes Repository names and IDs, commits, pull request numbers, deployment addresses and checks.Why we need it To test deployments and post results.How long we keep it Until you disconnect GitHub or delete the workspace.
CLI and tunnelWhat it includes Which devices you approved, and when each tunnel opened and closed.Why we need it To connect your terminal and reach apps on your computer.How long we keep it CLI credentials expire after 30 days.
BillingWhat it includes Your plan, run counts and invoices. Stripe holds your card and billing address.Why we need it To charge for Rehearsal and keep tax records.How long we keep it As long as tax and accounting law requires.
FeedbackWhat it includes What you tell us, and the page or result it is about. We email it, with your name, to our team.Why we need it To fix problems and improve Rehearsal.How long we keep it Until the workspace is deleted.
Activity and logsWhat it includes For each AI call: the model, its timing, token counts and cost, without the text. Service logs of each request: the IP address, browser type, the path without its query string, IDs and error details.Why we need it To run Rehearsal, find faults and control cost.How long we keep it Service logs: 30 days. AI call records: until the workspace is deleted.
How you use the appWhat it includes Measurements of how you use the app, for everyone who signs in. Recordings of how you use it, only if you join the improvement program. Both are linked to your account only if you join.Why we need it To find problems and improve the app.How long we keep it As set by Google Analytics and Microsoft Clarity. Leave the program any time in your account settings.
This websiteWhat it includes Standard request logs kept by Cloudflare, which serves the site. How you use the site, measured by Google Analytics and recorded by Microsoft Clarity, without knowing who you are.Why we need it To deliver and protect the website, and to see how people use it.How long we keep it Logs: as set by Cloudflare. Measurements and recordings: as set by Google and Microsoft.

Where it comes from

#sourcesLink to 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

#what-not-to-sendLink to 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

4. How we use information

#how-we-use-informationLink to 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

#emailsLink to 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

#legal-basesLink to Legal bases

If you are in the European Economic Area, the United Kingdom or Switzerland, the law requires a legal basis for each use.

Legal bases for each use
UseLegal basis
Running Rehearsal, sending service emails and billingLegal basis Performing our contract with you or your organisation.
Security, preventing abuse, fixing problems, understanding use from logs and analytics, and acting on feedbackLegal basis Our legitimate interest in running a secure and reliable service. You can object.
The improvement program, which records how you use the app and links measurements to your accountLegal basis Your consent, which you can withdraw at any time in your account settings.
Tax records and answering lawful requestsLegal basis Complying with our legal obligations.
Personal information inside a customer's workspace contentLegal basis The customer's instructions. The customer chooses the legal basis as controller.
5

5. AI processing

#ai-processingLink to 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

#ai-what-is-sentLink to 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

#ai-providerLink to 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

#ai-trainingLink to 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

6. Test accounts and secrets

#test-credentialsLink to 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

7. Browser sessions and evidence

#browser-evidenceLink to 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

#evidence-visibilityLink to 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

8. The test inbox

#test-inboxLink to 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

9. The CLI and the local tunnel

#cli-and-tunnelLink to 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

10. GitHub

#githubLink to 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.

11

11. Sharing and service providers

#sharingLink to Sharing and service providers

In short: We share information with the providers that run Rehearsal for us, and in a few other cases.

We share personal information only in these cases:

  • With the service providers in the table below, who process it for us under contract and only to provide their service.
  • Inside your workspace. Members see workspace content according to their role and permissions.
  • With GitHub, when you ask us to post results there.
  • When the law requires it, or to protect the rights, safety or property of our users, the public or us.
  • In a business transfer, such as a merger or sale of assets. We will tell you before your information becomes subject to a different privacy policy.
  • With your consent.

Our service providers

#subprocessorsLink to Our service providers
Service providers that process personal information for Rehearsal
ProviderWhat it does for RehearsalWhere
Microsoft AzureWhat it does for Rehearsal Runs our servers, database, file storage, key vault, logs and the browsers that test your apps.Where United States (Central US)
Microsoft Azure OpenAIWhat it does for Rehearsal Runs the AI models behind Re:agent, test writing, chat titles and dictation.Where United States (East US 2). Microsoft may process a request in another region where it runs the model.
CloudflareWhat it does for Rehearsal Serves rehearsal.dev and app.rehearsal.dev, protects our network, and carries the local tunnel.Where Global network
Amazon Web ServicesWhat it does for Rehearsal Sends our emails and receives email for the test inbox.Where United States (us-east-1)
StripeWhat it does for Rehearsal Takes payments, manages subscriptions and sends invoices and receipts.Where United States
GitHubWhat it does for Rehearsal Delivers deployment and pull request events and shows our checks, if you connect it.Where United States
GoogleWhat it does for Rehearsal Signs you in with Google, if you choose it. Supplies the small icons the app shows for your apps, which tells Google their web addresses.Where United States
Microsoft ClarityWhat it does for Rehearsal Records how people use rehearsal.dev. In the app, records only people who join the improvement program, linked to their account.Where United States
Google Analytics, run by Google LLCWhat it does for Rehearsal Measures how people use rehearsal.dev, and how everyone signed in uses the app. In the app, it links measurements to your account only if you join the improvement program.Where United States
SentryWhat it does for Rehearsal Collects error reports from the app, with personal details removed.Where United States
GruviWhat it does for Rehearsal Runs the help chat in the app. Gruvi is another product of ours, with its own privacy policy.Where See Gruvi's privacy policy

We will update this list before we add or replace a provider that handles workspace content.

12

12. International transfers

#international-transfersLink to 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

13. Retention and deletion

#retentionLink to 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

14. Security

#securityLink to 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

15. Your rights

#your-rightsLink to 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:

Your privacy rights
RightWhat it means
AccessWhat it means Ask what we hold about you and get a copy.
CorrectionWhat it means Have wrong or incomplete information fixed.
DeletionWhat it means Have your information deleted, unless we must keep it by law.
PortabilityWhat it means Get your information in a common format to take elsewhere.
ObjectionWhat it means Object to a use that relies on our legitimate interests.
RestrictionWhat it means Ask us to pause a use while a concern is settled.
Withdraw consentWhat it means Take back a consent you gave, such as the improvement program.
ComplaintWhat it means Complain to your data protection authority.

How to use them

#exercising-rightsLink to 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

16. US state privacy rights

#us-state-rightsLink to 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.

17

17. Cookies and browser storage

#cookiesLink to Cookies and browser storage

In short: The website and the app set analytics cookies. The app also uses cookies to keep you signed in.

On rehearsal.dev we use Google Analytics and Microsoft Clarity to see how the site is used. They set cookies. They do not know who you are.

If you choose a light or dark theme, your browser remembers it in local storage. It never leaves your device.

Cookies and browser storage on rehearsal.dev
WhatWhyHow long
Google Analytics cookies, whose names start with "_ga"Why Count visits and see which pages people read.How long Up to 2 years.
Microsoft Clarity cookiesWhy Record how people use the site.How long Up to 1 year.

In the app we use:

Cookies and browser storage in the app
WhatWhyHow long
Sign-in cookies, whose names start with "__Secure-rehearsal"Why Keep you signed in, and protect a Google or passkey sign-in while it happens. Scripts on the page cannot read them.How long The session cookie lasts 7 days after you last use the app, or until you sign out. The others last 5 minutes.
rehearsal.last_login_methodWhy Remembers how you last signed in, so the sign-in page can offer it first.How long 1 year.
return_to and invite_redirectWhy Bring you back to the page you asked for after you sign in or accept an invitation.How long 15 minutes, or until you close the browser.
sidebar_state and i18n_redirectedWhy Remember whether the sidebar is open and which language the app used.How long The sidebar cookie lasts 7 days. The language cookie stays until you clear it.
Local and session storageWhy Keep unsent drafts of chat messages, and remember choices such as your theme, panel sizes, speaking language and which chats you have read.How long Drafts are kept 14 days. Other choices stay until you clear them.
Help chat storageWhy Keeps your help conversation. Gruvi receives a coded identifier, not your name or email address.How long Until you clear it.
Microsoft Clarity cookiesWhy Record your use of the app, only if you join the improvement program.How long Removed when you leave the program.
Google Analytics cookies, whose names start with "_ga"Why Measure how you use the app. Linked to your account only if you join the improvement program.How long Up to 2 years.

We do not use advertising cookies anywhere.

18

18. Children

#childrenLink to 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

19. Changes to this policy

#changesLink to 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

20. Contact us

#contactLink to 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.

Gruvi Software Inc.

Post
2810 N Church St STE 90490, Wilmington, DE 19802, United States
Email
hello@rehearsal.dev
Phone
+1 (845) 478-8411

Product

  • Product
  • Developers
  • GitHub
  • Docs

Company

  • hello@rehearsal.dev
  • Privacy
  • Terms

Rehearsal by Gruvi Software Inc.

© 2026