Who we are
revise.build (“Revise”, “we”) is operated by Monestiva LLC. Questions about this policy go to hello@revise.build.
What we collect
- Account details. Your email address, and the name and profile picture your sign-in provider shares, so we can identify you and your teams.
- Team information. Team names, membership and roles, invitation links, and the settings a team chooses, including which AI provider it uses.
- Repository connections. Identifiers for the repositories you connect and the credentials needed to read them and to open review requests. Access tokens are encrypted at rest with a key that is never stored in the database.
- Your code, while a workspace runs. A connected repository is cloned into a private cloud workspace so the preview can run. The workspace is not reachable from the public internet and is torn down on the schedule described below.
- Edits and requests. The changes you save, the text you type to describe them, and the explanation returned, kept as your change history so you can undo, resume on another device, and send work for review.
- Usage and billing. Which features you use, the AI and workspace budget consumed, and, if you pay, the records our payment provider returns. We never see full card numbers.
- Technical logs. Request logs and workspace startup logs kept for reliability and security, with credentials removed before they are stored.
How AI requests are handled
When you ask for a change, your request and the relevant source files are sent to an AI provider to produce the edit. With Revise AI that provider is Anthropic, using our account. A team may instead connect its own OpenAI or Anthropic account, or a ChatGPT subscription; then requests go to that provider under the team’s own agreement. We do not use your code or requests to train models. Each provider’s own terms govern what it retains.
Who processes data on our behalf
- Supabase, for the database and sign-in.
- Fly.io, for hosting and for the private workspaces that run previews.
- Anthropic, and OpenAI when a team chooses it, for AI edits and startup diagnosis.
- Stripe, for payments.
- Resend, for sign-in and invitation emails.
- GitHub, GitLab or Bitbucket, whichever hosts the repository you connect.
How long we keep things
- A workspace is paused after a few idle minutes and its disk is removed about a day after the session ends. Nothing on it survives except the changes you saved.
- Saved changes and review history stay with your account until you undo them, delete the project, or delete the account.
- Usage and billing records are kept for as long as accounting rules require.
- Workspace and request logs are kept for a limited period for reliability and security.
Your choices
- You can review and change your profile and AI settings in Settings.
- You can delete your account from Settings. Deletion removes your profile, your saved changes, your workspaces and their disks, and cancels subscriptions on teams you own. Reviews already sent to other people’s repositories remain there, because they are their records.
- You can ask us for a copy of your data or for corrections at hello@revise.build.
Cookies
We use cookies only to keep you signed in and to attach a private preview to your session. There is no advertising or cross-site tracking.
Security
Traffic is encrypted in transit. Repository credentials are encrypted at rest. Workspaces run on private networks with no public address, and the code you connect is never sent to a model unless you ask for an edit. No system is perfectly secure; if you believe your account has been compromised, contact us and change your sign-in details.
Children
Revise is a tool for work and is not directed at children under 16. We do not knowingly collect their data.
Changes
If this policy changes in a way that matters to you, we will update the effective date above and tell signed-in users in the product. See also our terms of service.