Privacy Policy
Last updated 31 October 2026
This policy explains what information Ruvma collects, why, and what we do with it. It covers our website, the Ruvma app and the connections agencies set up in it.
1. Who we are
Ruvma is run by [Company legal name], [Registered address] (“Ruvma”, “we”, “us”). For anything about your information, write to [contact email].
2. What Ruvma does
Ruvma is a service for web agencies. It reads the change requests an agency's clients send by email, makes the edits on the clients' websites through the connections the agency sets up, checks the result and shows the agency a preview. Nothing goes live until someone in the agency approves it.
3. Information we collect
- Account information: the name and email address of each team member, how they sign in, the agency's name and who has which role.
- Clients and sites: the clients an agency adds, the senders it allows for each, their websites, and the notes and preferences the agency writes about them.
- Emails and attachments: messages from an agency's clients that reach Ruvma, through a forwarding address or a connected mailbox, and the files attached to them.
- Connections: the keys and tokens that let Ruvma reach a connected mailbox (Gmail or Outlook), GitHub repositories through Ruvma's GitHub App, WordPress sites through the Ruvma Connector, and Vercel previews. They are stored encrypted.
- Website content and changes: the pages and code Ruvma reads to make a change, the changes it makes, previews, check results and each request's history.
- Technical data: logs of requests to our servers, including IP addresses and browser details, and records of the AI calls each request used.
4. How we use it
We use this information to run Ruvma for the agency: to turn emails into requests, plan and make the changes, check them, show previews, publish what the agency approves, and send the agency notifications. We also use it to keep Ruvma secure, to help when you ask for support, and to find and fix problems.
We don't sell personal information, and we don't use it for advertising.
5. AI processing
To understand a request and make the change, Ruvma sends what the request needs, such as the email, its attachments, the relevant page content or code, to Anthropic's Claude models. Anthropic processes it on our behalf under its commercial terms, which don't allow it to train its models on that content. Ruvma doesn't use your content to train AI models either.
6. Google user data
When an agency connects a Gmail mailbox, Ruvma has read-only access. It looks at who sent each new message, reads in full only the messages from the senders the agency allows for its clients, and turns those into requests. It doesn't use other messages for anything, and it can't send, change or delete email in the mailbox.
Ruvma's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We don't use Google user data for advertising, we don't sell it, we don't use it to develop, improve or train generalized AI or machine-learning models, and people at Ruvma don't read it unless the agency asks us to, it's needed for security, or the law requires it.
7. Who we share it with
We share information only with the providers that run parts of Ruvma, and only for that:
- Cloudflare, which hosts Ruvma, stores files and routes and sends email.
- Neon, which hosts our database.
- Anthropic, which runs the AI models.
- GitHub, Vercel, Google and Microsoft, when an agency connects them, to do what the agency connected them for.
The WordPress sites and repositories an agency connects receive the changes it approves. We may also disclose information when the law requires it, or to a successor if Ruvma's business is sold or merged, under this policy.
8. Agencies and their clients
An agency decides which clients, mailboxes and sites it connects. For its clients' emails and websites, the agency is responsible for having the right to share them with Ruvma, and Ruvma processes them on the agency's instructions. If you're an agency's client and have a question about your information, please contact the agency first; we'll help them answer.
9. How long we keep it
We keep an agency's information while its account is open. Requests, emails and their attachments stay with the request so the agency can see what was asked and what changed. When an agency deletes its account, we delete its information within [30] days, except where the law requires us to keep it longer.
10. Security
Information travels encrypted, and keys and tokens are encrypted at rest. Ruvma reaches only what an agency connects: the GitHub App only the repositories the agency picks, and the Ruvma Connector works as its own WordPress user with limited permissions. No system is perfectly secure; if something happens that affects your information, we'll tell you without undue delay.
11. Your rights
Depending on where you live, for example under the GDPR or Turkey's KVKK, you can ask to see, correct, export or delete your information, or object to how we use it. Write to [contact email]. You can also complain to your data protection authority.
12. International transfers
Our providers may process information in other countries. Where the law requires it, we rely on safeguards such as standard contractual clauses.
13. Children
Ruvma is a service for businesses and isn't meant for anyone under 16.
14. Changes to this policy
When we change this policy, we update the date above, and we tell agencies by email before a change that matters takes effect.