Skip to main content

Security

Last updated: [date] — draft pending legal review.

An overview of how Repuvane protects your account and your data. See Architecture for how the product is built.

Authentication​

Sign-in is handled entirely by Clerk, a dedicated identity provider. Repuvane never stores your password directly.

Data isolation​

Every business's reviews, voice settings, and reply history are scoped to that business's account. A teammate you invite (a Worker) only ever sees your business's data — never another Repuvane customer's.

Human approval by design​

No reply is ever posted to a review platform without explicit human approval. There is no setting that removes this step — it's a structural part of the product, not a configurable toggle.

Team access controls​

Only the Owner of a business can invite or remove teammates, or change business-identity settings. A Worker's access is scoped to the review workflow — see Team Roles.

Infrastructure​

Repuvane is built on established, independently-secured infrastructure:

  • Clerk for authentication (SOC 2 Type II).
  • Convex for application data storage.
  • Vercel for application hosting, with TLS/HTTPS enforced end to end.
  • Anthropic for AI drafting.

AI drafting and your data​

When Repuvane drafts a reply, the review text and your voice settings are sent to Anthropic's API for that single request. This data is not used to train a model that's shared across other Repuvane customers.

Reporting a security issue​

If you believe you've found a security vulnerability, please report it to info@mavarosystems.com rather than filing a public issue. We'll respond as quickly as we can.