AUVYTrust Center
Trust you can review
EU-hosted workspaces, public processor disclosures, and the contracts buyers need — written for security, legal, and procurement review.
- Core EU hosting
- Public AVV / DPA
- Processor register
- AI transparency
AUVYTrust Center
EU-hosted workspaces, public processor disclosures, and the contracts buyers need — written for security, legal, and procurement review.
Companies selected by AUVY that process data on our behalf. Regions, optional paths, and available contract or privacy sources are listed per processor.
| Subprocessor | What they do | Data involved | Where | Optional |
|---|---|---|---|---|
| Primary EU hosting for the product and customer workspaces | Account and login data, workspace content and files, operational service data | EU (Helsinki) | No | |
| EU cloud infrastructure and AI model access | Workspace content, prompts, uploaded files, service logs | EU (Frankfurt) | No | |
| EU AI model services (where configured) and voice transcription | Workspace content, prompts, attached files, audio and transcripts for voice features, service logs | EU (Frankfurt, Sweden) | No | |
| Web search and fetching public page content when you use those features | Search queries, requested URLs, returned public web results and page text | EU (Azure EU) | No | |
| Hosting and delivery of the AUVY web application | Request metadata and delivery telemetry | EU (Frankfurt); edge delivery may process request metadata globally | No | |
| Subscription billing, invoices, and payment methods | Email, billing name and address, payment method (held by Stripe), subscription and invoice details | EU (Ireland) | No | |
| Transactional email (account, billing, and system messages) | Recipient email, message content, delivery metadata | EU send (Ireland); account metadata in US (GDPR DPA, SCCs, DPF) | No | |
| Product analytics and feature flags when enabled | Pseudonymous user ID, feature usage events, workspace metadata | EU (Frankfurt) | Yes |
This list covers AUVY-selected processors that are active or production-capable. “Optional” means the provider receives data only when the relevant feature or configured path is enabled and invoked; it does not mean every workspace uses that provider. OpenPulse is an AUVY-operated service on internal EU infrastructure and is therefore described here but not listed as a third-party subprocessor. Customer-selected integrations and destinations remain separate recipients under the customer’s control. Inactive optional model credentials are not represented as active subprocessors. For German professional secrecy (§ 203 StGB), AUVY may further limit available providers and features for the workspace.