Privacy policy
What Releavo collects, why, who processes it, and what you can do about yours.
Last updated October 11, 2026.
Releavo ("we") runs releavo.app, the Releavo apps for Mac, Windows, iPhone and iPad, and Releavo's MCP server. This policy covers those. A self-hosted install of Releavo is run by the organisation that installed it, and its data stays with them.
Questions, or a request about your data: [email protected].
What we collect
Your account. Your name, email address, password (kept as a one-way hash by our sign-in provider), photo if you add one, and the workspaces and projects you belong to with your roles in each.
What your team puts in Releavo. Docs and their versions, stories, epics, sprints, comments, risks, test cases, chat messages with Releavo, files you upload, and what Releavo writes for you. This belongs to your team; we hold it to run the service.
Voice input. When you press the mic, the recording is sent to be turned into text and the text comes back to the box. We don't keep the recording.
Tools you connect. When someone in your team connects Jira, GitHub, Figma or another tool, we store its sign-in or token encrypted, and keep what Releavo reads from it in your project (for example, a mirrored issue, or what changed in a pull request). The AI never sees the credentials themselves.
AI apps you connect over MCP. Which app, what you allowed it (read only, or read and act, and which projects), and when it was last used.
Billing. Your workspace's plan, seats, credit balance and usage, and invoices. Card details go straight to Stripe; we never see or store them.
Technical data. Our servers log requests (IP address, browser, time, the page or action, errors) to keep the service running and secure. We count page visits on the public site with Cloudflare, without cookies.
Cookies and browser storage
We use one kind of cookie: the sign-in cookie that keeps you signed in. Your browser also keeps a few preferences for you (theme, panel sizes, the workspace you last opened). There are no advertising or tracking cookies.
How we use it
- To run Releavo: show your team its work, run Releavo's AI on your requests, follow your connected tools, and write code when your team asks.
- To send email about your account and your work: sign-in and password links, invites, a draft waiting for you, usage alerts, and a notice when an app connects to your account. We don't send marketing email.
- To bill your workspace.
- To keep Releavo secure, prevent abuse, and fix problems.
- To improve Releavo, using what we see of how it's used, not by reading your team's content.
We don't sell your data, and we don't use it for advertising.
AI
Releavo's AI works on your team's content when someone asks it to, or when a connected tool has news for it. To do that we send the relevant content to the model provider and get the answer back. Your content is processed to answer, and isn't published or shared with other customers.
If a workspace admin sets the workspace to use its own model (your Anthropic key, Amazon Bedrock, Microsoft Foundry, or a model you run), Releavo sends the content to that provider instead, under your agreement with them.
Who processes it, and where
We use these providers to run Releavo. Each gets only what its job needs.
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, sign-in, uploaded files | Singapore |
| Our own servers | The web app | Australia |
| Fly.io | Releavo's AI worker and coding dev boxes | Singapore |
| Cloudflare | Network and security, domain, email forwarding, page counts | Worldwide |
| Anthropic | Releavo's AI (Claude), including web search when it looks something up | United States |
| OpenAI | Turning voice recordings into text | United States |
| Making music, when you ask Releavo for a track | United States | |
| Stripe | Payments, invoices and billing | United States and elsewhere |
| Resend | Sending email | Japan |
| Tailscale | Only if your workspace connects its private network | Worldwide |
Tools your team connects (Jira, GitHub, GitLab, Azure DevOps, Figma, Linear, Notion, Sentry, MCP servers) receive what Releavo does in them on your team's instructions, under your agreement with them.
People in your workspace see what their roles allow; client stakeholders see approved versions only. We may disclose data if the law requires it, and we'd tell you unless we're not allowed to.
Because our providers are in several countries, your data may be stored and processed outside the country you're in. We choose providers that protect it to the standard this policy describes.
How long we keep it
- Your account and your team's work: while the account and workspace exist.
- A deleted project: its docs, versions, chats and uploaded files are deleted with it.
- A deleted account: within 30 days of your request, except what we must keep by law (invoices and payment records, for as long as tax law requires).
- Server logs: a few weeks.
- Copies in our database provider's backups expire on their own schedule, usually within a few weeks.
Your choices and rights
You can see and change your profile in Releavo at any time, and workspace admins can remove members and delete projects. To get a copy of your data, correct it, or delete your account, email [email protected] from your account's address; we'll answer within 30 days.
Depending on where you live (for example under Australia's Privacy Act, or the GDPR in the EU and UK), you may also have the right to object to or limit how we use your data. If you're unhappy with how we've handled it, tell us first; you can also complain to your privacy regulator (in Australia, the OAIC).
Security
How we protect Releavo, and how to report a problem: see Security.
Children
Releavo is for work, and not for anyone under 16.
Changes
When this policy changes we'll update it here and change the date at the top. If a change affects how we use your data in a significant way, we'll email workspace admins before it applies.