Privacy Policy

Auvra Labs Privacy Policy (DRAFT pending legal review; not yet in force)

Version 2026-06-12-draft1

1. What we collect. Account basics (name, email, role), workspace data clients import or connect (contacts, companies, CRM records), product telemetry (which screens are used, errors), and security events (sign-ins, permission denials). We do not collect more than the product needs.

2. How we use it. To run the service: building review queues, scoring leads, showing usage and results, keeping tenants isolated, and keeping accounts secure. Error reports are scrubbed before they leave the app: no request bodies, no cookies, no emails, no secrets.

3. Who can see what. Your workspace data is visible to your workspace members based on their role. Auvra staff access is limited to operating and supporting the service, and master-admin access is recorded.

4. Subprocessors. We use infrastructure and provider services to run the product (hosting, database, error tracking, and the research or enrichment providers a workspace turns on). Providers only receive what their job needs, and provider calls are off by default until a workspace enables them.

5. Contact data inside client workspaces. Clients are the controllers of contact data they import. Auvra classifies contacts at ingestion and blocks personal contacts from becoming outreach-eligible without an approved consent path.

6. Retention and deletion. Workspace data is retained while the contract is active. Deletion requests follow the recorded retention and deletion process, with legal holds honored.

7. Security. Tenant isolation is enforced at the database layer, secrets stay out of logs and telemetry, and security-relevant actions write audit events.

8. Your choices. Ask your workspace admin to correct or remove data about you, or contact us for anything the console does not cover.

This draft is a placeholder for structure and product honesty. It is not legal advice and has not completed legal review.