MCP Connector Privacy Policy

This policy covers the Replov MCP connector, which lets an AI assistant such as Claude manage your Replov apps on your behalf. It sits alongside our general Privacy Policy, which continues to apply to your Replov account itself. Where this page is more specific, it governs the connector.

The connector is operated by Replova Labs Private Limited. Data protection queries: privacy@replov.com.

1. The most important thing to understand

This is inherent to the feature — logs are only useful for debugging if they arrive intact. But it means the connector's privacy impact depends on what your own applications log. Before using log access on a production app that handles personal data, consider what that app writes to stdout.

The same applies to repository URLs, branch names, commit messages and app names: all are shared with the assistant when relevant to your request. Environment variables are not accessible through the connector at all — it can neither read nor set them.

2. What the connector can access

Access is granted per permission, and you see the exact list on the consent screen before connecting. The connector can never do more than your own account can do.

Reading

• Your apps: names, IDs, type, status, compute tier, region and public URLs
• Runtime logs (see section 1)
• Deployment history: timestamps, status, commit hashes, commit messages and build errors
• Source repository URL and branch
• Billing tier and price of each app — not payment methods or wallet balance

Acting

• Creating apps and triggering deployments
• Changing an app's compute tier — this changes what you are billed
• Rolling back to an earlier deployment
• Permanently deleting apps

The connector cannot access your payment methods, wallet balance, account settings, password, other users' resources, or anything outside the Replov account you authorized.

3. Protections on destructive actions

Deleting an app, rolling back a deployment, and moving an app to a paid tier are refused on the first request. The connector instead returns a description of what would happen and takes no action. Only a second, explicit request carries it out. Deleting additionally requires the app's exact name to be repeated back, so a deletion cannot be confirmed without the assistant having identified the specific app.

This runs on our servers, not in the assistant, so it applies regardless of how the AI client is configured.

4. Who else receives your data

Whatever the connector returns is received by the operator of the AI assistant you connected — for Claude, that is Anthropic. Their handling of that data is governed by their own privacy policy and your agreement with them, not by this one. Replov has no control over, and no visibility into, how long they retain it or how it is used.

Replov does not sell your data, and does not share it with any party other than the AI assistant you explicitly connected.

5. Access tokens

• Authorization uses OAuth 2.1 with PKCE. Your password is never shared with the AI assistant.
• Tokens are random values stored only as irreversible hashes. A database compromise does not yield a usable token.
• Access tokens expire after 1 hour. Refresh tokens are replaced on every use.
• Tokens are checked against our records on every request, so disconnecting takes effect immediately rather than when a token would have expired.
• A token is bound to a single user and a single service. It cannot be used to reach another account or replayed elsewhere.

6. What we record

Every action the connector takes on your behalf is recorded so you can see what an AI assistant did on your account. Each entry holds the time, your user ID, which assistant made the request, the operation, the app it targeted, and whether it succeeded, was refused, or was only a preview.

The connector cannot read or set environment variables at all, so none appear in the audit trail. Setting one through an assistant would require its value to pass through the conversation, which is why that capability is deliberately absent.

Log content retrieved through the connector is not stored in this audit trail. Entries are retained for 12 months.

7. Your control

• Disconnect at any time — from your AI assistant's settings, or from Replov under AI Agents. All tokens are revoked immediately.
• Review what was done — your connector audit trail is shown under Agent activity on the AI Agents page.
• Request deletion of your audit entries by writing to privacy@replov.com.
• Never connect it at all — the connector is entirely optional and Replov works exactly the same without it.

8. Where data is processed

Connector infrastructure runs in India, in DigitalOcean's Bangalore region (BLR1), alongside the rest of the Replov platform. Managed PostgreSQL databases provided through Vitibase run in AWS Asia Pacific (Mumbai),ap-south-1. Daily encrypted backups of volumes and Redis are stored in DigitalOcean Spaces in Singapore. Data is handled under India's Digital Personal Data Protection Act. Data sent onward to the AI assistant's operator may be processed outside India under their own terms.

9. Changes

If we add tools or change what the connector can access, this page is updated and the date above changes. Material expansions of access require you to re-authorize, so you will see the new permissions on a consent screen before they take effect.