Auvra Labs
Subprocessors
Auvra uses the providers below to host the product, secure accounts, monitor errors, research leads, enrich business contacts, and support future approved billing or communication workflows.
Version subprocessors_2026-06-14-draft1 - draft pending legal review.
United States
Application hosting
Hosts the web application and serverless routes. No client outreach is executed by Vercel.
account metadata, workspace metadata, application logs
United States, current project region
Database and authentication
Stores tenant data with row-level security and powers authentication.
account data, workspace data, database records, authentication data
United States / vendor-managed regions
Error monitoring
Receives scrubbed error telemetry only when production DSNs are configured.
scrubbed error metadata, route context, release metadata
Vendor-managed model infrastructure
AI inference
Used only behind provider gates for approved AI tasks such as OCR and structured analysis.
prompt inputs, structured outputs, business-card image content when OCR is enabled
Vendor-managed regions
Research provider
Runs public-web lead research only after the active Lead Plan and spend gates allow it.
lead research queries, public-source snippets, source URLs
Vendor-managed regions
Contact enrichment
Enriches contacts only after a lead clears fit, timing, and approved-provider gates.
company domains, contact enrichment requests, business contact candidates
Vendor-managed regions
Contact enrichment
Planned optional enrichment source. Not a default live source.
company domains, contact enrichment requests, business contact candidates
Vendor-managed regions
Billing
Planned enterprise billing system. Client-facing billing brand remains Auvra Labs.
billing contact data, contract billing records, payment metadata
Vendor-managed regions
Transactional email
Planned transactional email provider. Cold outbound remains gated separately.
email addresses, transactional email content
Vendor-managed regions
SMS and telephony
Provider credentials exist for future approved SMS/voice work. Automated sending remains blocked until release gates pass.
phone numbers, SMS metadata, approved message content
Customer tenant and provider-managed regions
Email and calendar connection
Optional customer-connected account path. Auvra does not connect it by default.
connected mailbox metadata, calendar metadata, approved message drafts
Customer tenant and provider-managed regions
Email and calendar connection
Optional customer-connected account path. Auvra does not connect it by default.
connected mailbox metadata, calendar metadata, approved message drafts
How Auvra limits provider use
Optional research, enrichment, AI, communication, and billing providers are not blanket access to client data. They are routed through workspace settings, provider gates, usage ceilings, and review queues. External outreach and destructive actions still require explicit human approval.