Auvra Labs
Trust
Public trust center for security reviewers, buyers, and clients. This page summarizes how Auvra protects access, limits provider use, and keeps customer data out of public surfaces.
Version public_trust_2026-06-14_v1
Auvra Method
How Auvra qualifies, prepares, reviews, and measures revenue work before external actions.
Consent-Safe Outbound
How send readiness, suppression, approval, and channel-specific consent stay separate.
Terms of Service
Draft operating terms for the Auvra console. Not enforced until legal review is complete.
Privacy Policy
How Auvra handles account, workspace, telemetry, security, and provider data.
Subprocessors
Infrastructure, AI, research, enrichment, billing, and communication providers by status.
Security Contact
Good-faith vulnerability disclosure contact and reporting expectations.
Status
Public service posture and the shallow uptime monitor endpoint.
Operating controls
Tenant isolation
A signed-in user only sees workspace data after auth, MFA when required, legal acceptance when enforced, and workspace membership checks.
Provider gates
Provider calls run through workspace settings, active Lead Plan gates, spend ceilings, and review queues.
Human approval
CRM writes, outreach, billing changes, and destructive operations stay behind explicit approval boundaries.
Usage controls
Usage is tracked as Auvra credits and raw provider units without exposing internal markup or provider-cost accounting to company users.
Public authority
Public pages explain Auvra's method and channel boundaries without exposing private workspace data or implying unsupported automation.
Current scope
Auvra prepares evidence-backed sales work for humans. External outreach, CRM writes, billing changes, provider execution, and destructive operations stay gated unless a future reviewed release explicitly enables the relevant action class.