Privacy Policy. What we do with personal data, and why.
How Rapid Review, Inc. handles personal data on its website, in its app, its assistant and its GitHub App, for billing and in support, and your rights. Last updated 12 November 2026.
Who we are.
Rapid Review, Inc., 2261 Market Street STE 73436, San Francisco, CA 94114, USA, is responsible for the personal data this policy describes. For anything about your data, write to privacy@rapidreview.dev.
This policy covers rapidreview.dev, the Rapid Review app at https://app.rapidreview.dev and its assistant, the Rapid Review GitHub App, billing and support. It doesn’t cover the code and other content in our customers’ repositories: there we process personal data for our customers, under our Data Processing Addendum. For that data, ask the organization whose repository it is.
The website.
rapidreview.dev uses no analytics service. It sets cookies of its own only for what you choose at the foot of a page: your theme, if you pick a light or dark one, for a year (picking System removes it); your answer to our question whether we may follow your visit, for six months; and, if you allow it, your visit, as below. Cloudflare, which serves the site, processes your IP address to deliver the pages and protect them.
We count every page view, and every click on to the app or to our documentation, by day, and for two days at most by hour too: the page, the referring site’s name, campaign tags in the link (such as utm_source and utm_campaign), your country as Cloudflare tells it, your browser’s family (such as Firefox) and whether it runs on a phone or tablet, and whether a browser, an agent or a crawler asked. Nothing in these counts tells one visitor from another, and nothing is stored on your device for them.
If you allow it, a cookie holds a random token for two hours, so that we can see how a visit goes from page to page and on to the app. With it we record the page you allowed it on and the pages you view after it, the referring site’s name and the campaign tags of that page, and your country. When you go on to the app, the token goes with you once, in the address, and the app keeps it in a cookie of its own until you sign in. If you sign in to the app or install the GitHub App, we count it under the same visit, with a keyed digest of your GitHub id in place of the id. Without your consent, or when your browser sends Global Privacy Control or Do Not Track, there is no such cookie and nothing is linked. You can change your answer at any time at the foot of any page. We never record your IP address, your browser’s user agent or a fingerprint.
The contact form takes your email address, an optional name, the topic and your message, and passes them to our support desk, as support mail. Cloudflare Turnstile checks that a person sends it, from signals your browser gives it. Your IP address is used to limit how many messages are sent, and isn’t stored.
The app and the GitHub App.
You sign in to the app with GitHub. We receive your GitHub id, login, name and avatar, and read from GitHub which accounts and repositories you can see, to show you only those. The Rapid Review app shows reviews and findings only to people who can see the repository on GitHub, and only as long as GitHub shows it to them.
The app sets cookies it needs to work: your session (seven days), the sign-in in progress (ten minutes), a sign-in that waits for you to accept the Terms (ten minutes), the account you last opened and your theme (a year each), and, where the assistant is on, whether its panel is open and what it shows (until you close the browser). Where you allowed us to follow your visit on rapidreview.dev, it keeps that visit’s token until you sign in, two hours at most. We record the changes you make, such as to review settings and learnings, in the account’s audit log.
When you accept the Terms of Service and the Data Processing Addendum in the app, we keep which version you accepted and when, with your GitHub id and login, to show the agreement.
When you first sign in to the app, our team is notified at once through our own push service, with your GitHub login. When you use an invite or referral code, when you sign in or on an account’s Usage and billing tab, we keep your GitHub id and login with it, and the account its credits go to. Cloudflare Turnstile checks that a person sends the code form on the app’s sign-in page, as it does the contact form.
When an admin applies for free open-source reviews, we keep the application, the applicant’s GitHub login and note, and what we read about the repository to decide it.
For each account the GitHub App is installed on, we keep the installation, its account and repositories, its settings, and its credits and plan.
The assistant.
Where the assistant is on for an account, you can ask it about Rapid Review and the account in the app. With each question we send AI model providers your question, the earlier turns of the conversation, the page you asked from, the facts about the account that you can already see in the app, read again for each question, and the changes you could make. They go through OpenRouter to Anthropic, which writes the answer, and to TypeSafe, which checks it. They never include a pull request’s title, a commit, your repositories’ code or another person’s GitHub login, unless you write them in your question.
Neither provider may train its models on them. We ask that TypeSafe keeps nothing once it has answered; Anthropic may keep a request for a time under its own policy.
The answers are written by AI and shown to you without a person reading them first. A person on our team is always a ticket away: Open a ticket under a conversation has the assistant write a message to support from it, which you read and can change before you send it. It then goes as support mail, and our team sees the conversation with it.
We keep your conversations, with the facts sent with each question, the changes proposed, what you did with them and your votes, to show them to you and so that our team can check and improve the assistant’s answers. No one else in the account sees them in the app. A change you make from one of its proposals is recorded in the account’s audit log as yours, via the assistant.
A conversation is deleted 180 days after its last turn or, if you opened a ticket from it, once the support conversation the ticket went to is deleted too. Your conversations are tied to your GitHub account, not to an email address: to have them deleted, ask from the app while you are signed in, and we delete them with the support mail you sent from the app. A request by mail deletes the support mail of the address it came from, once we can tell the request came from that address, and doesn’t reach your conversations.
Reviews and AI models.
To review a pull request, Rapid Review sends AI model providers the changed code of the files it reviews, with the surrounding and related code the review’s mode includes; the pull request’s title, description and linked issues; and, in repositories that record learnings, the replies in Rapid Review’s own review threads.
We send review requests only to model providers that do not train on the data. We don’t require zero data retention, so a model provider may keep request data, including your code, under its own policy for a time.
Changes to files that look like secrets, such as .env files, private keys and credentials, are never sent to a model, whatever the repository’s include rules say.
Rapid Review keeps a record of each review and its findings, the summary of each reviewed pull request, the learnings with a history of changes to learnings and review settings, and each reviewed pull request’s title, author and state. To give its reviewers context, it also stores parts of your repository’s code.
Code, pull requests and replies can hold personal data, such as the names and email addresses of the people who wrote them. We process it for the customer whose repository it is, under the Data Processing Addendum.
Billing.
Payments run through Stripe. Stripe collects your payment details, which we never see in full, and gives us the billing contact, address, tax ID, the plan and the invoices. Stripe also processes payment data under its own privacy policy, as a controller, for example to prevent fraud.
Support.
What happens to the messages you send us, which AI models read them and why, is in Support mail and your data. A conversation and everything in it, your messages, their attachments and our replies, is deleted 180 days after its last message.
When you write from the app about an account, your message can carry facts about it that you can already see in the app: for its owner and its members, the settings of the repositories you name and their pushes that weren’t reviewed in full; for its owner, also its plan, credits and daily budget. They are used only to draft a reply for a person on our team: the part a draft needs reaches the drafting model’s providers, OpenRouter and Anthropic.
Why we process it.
- To provide the service and answer you: your account, sign-in, reviews, invite and referral codes, billing, support and the assistant, to fulfil our contract with you or take the steps you ask for before one (Art. 6(1)(b) GDPR).
- To meet legal duties, such as keeping invoices for tax law (Art. 6(1)(c) GDPR).
- With your consent: following your visit on the website from page to page and on to a sign-in or an install in the app, with a cookie (Art. 6(1)(a) GDPR). You can withdraw it at any time at the foot of any page.
- For our legitimate interests: keeping the service and the website secure, preventing abuse, counting page views without telling visitors apart, telling our team at once of a new sign-up, sorting support mail, and checking and improving the assistant’s answers (Art. 6(1)(f) GDPR). You can object to these at any time.
We don’t sell personal data, don’t share it for advertising, and make no decision with legal or similarly significant effect about you by automated means alone.
Who receives it.
Our service providers process personal data for us: Cloudflare hosts the website, the app, the GitHub App, the support desk and our push service; OpenRouter passes requests to the AI model providers, and Amazon Web Services runs some of the models for us directly, through Amazon Bedrock; Stripe handles payments; Apple’s push notification service delivers to our team’s iPhones the notification our push service sends of each new sign-up, with its first lines. Each, with what it handles and where, is on our Sub-processors page.
GitHub receives what the GitHub App posts on your pull requests, under your own agreement with GitHub. We disclose data to authorities only where the law requires it.
Transfers outside the EU.
Rapid Review, Inc. is in the United States, and so are most of our providers. Where personal data from the European Union, the United Kingdom or Switzerland goes there, the transfer rests on the EU–US Data Privacy Framework and its UK and Swiss extensions for providers certified under them, and otherwise on the European Commission’s standard contractual clauses.
How long we keep it.
- Sessions: seven days; a sign-in in progress, or one waiting for you to accept the Terms, ten minutes.
- Which Terms you accepted, and when: while you use Rapid Review, and after that as long as we may need to show the agreement.
- Page views counted, and visits followed with your consent, on the website: 13 months, so a year can be compared with the one before. Your answer to whether we may follow your visit stays on your device for six months.
- Notifications to our team of a new sign-up: 30 days on our push service, a day at most with Apple’s push service while it waits for a phone to come online, and on our team’s phones until we delete them.
- Support mail: 180 days after a conversation’s last message.
- Conversations with the assistant: 180 days after a conversation’s last turn, or as long as the support conversation a ticket from it went to, if that is longer. Sooner, if you ask from the app while you are signed in.
- Reviews, learnings, settings and the audit log: while the account uses Rapid Review. Its owner can ask us to delete them, and we do within 30 days.
- Invoices and billing records: as long as tax law requires.
Your rights.
You can ask us what data we hold about you and for a copy of it, to correct it, to delete it or restrict how we use it, and for the data you gave us in a common, machine-readable format (Art. 15 to 18 and 20 GDPR). You can object to processing based on our legitimate interests (Art. 21 GDPR).
Write to privacy@rapidreview.dev. To have support mail deleted, write from the address it came from. If we can’t verify your mail, we email that address a link to confirm the request, and delete once you follow it. For your conversations with the assistant and the support mail you sent from the app, ask from the app while you are signed in. We answer within one month. You can also complain to a data protection supervisory authority, in particular in the EU country where you live or work (Art. 77 GDPR).
Security.
We protect personal data with technical and organizational measures, which the Data Processing Addendum lists. To report a security issue, write to security@rapidreview.dev.
Changes to this policy.
Rapid Review is for businesses, and not for people under 18. We publish each new version of this policy here with its date, and tell account owners about material changes in the app.