Trust
You are giving Reevly your inbox. Here is how we look after it.
Drafts only
Reevly has no way to send email or messages. It writes drafts; you send them.
Your own server
Every customer runs on a separate server with its own disk. Nothing is shared between customers.
No training, no ads
Your data is never used to train AI models, never used for ads and never sold.
Nobody reads it
Our team does not read your mail or notes unless you ask us to for support, or we must for security or the law.
Encryption
Everything travels over HTTPS. Your Google sign-in tokens are encrypted at rest with AES-256-GCM, and your server's disk is encrypted at rest by our host.
Who handles your data
- Render hosts your private server, in the United States.
- Anthropic provides the AI model, and does not train on this data.
- Our AI gateway (self-hosted) passes AI requests to Anthropic and enforces your usage cap. It keeps usage counts, not content.
- Google provides sign-in and the mail, calendar, contacts and files you connect.
- Supabase keeps the account and subscription list.
Details are in the privacy policy.
Google data
Reevly's use of data from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
Leaving is easy
Download your data at any time, and Reevly backs it up to your own Google Drive. When you cancel you have 7 days to take it with you, and then we delete it within 30 days. You can disconnect Google whenever you like at myaccount.google.com/permissions.
What this is not
This page is a plain description of how we work, not a certification. Reevly does not yet hold SOC 2. Reevly's access to Gmail goes through Google's verification and a yearly independent security assessment.
Report a problem
Found a security issue? Email support@reevly.ai and we will respond quickly.