Providers and subprocessors
This list describes specific data flows and services supporting Voicedot. Entries do not all have the same legal role; some operate only after a user choice or configuration is enabled.
On this page
Providers and services
A subprocessor processes customer data on Voicedot’s behalf within the applicable agreement. This list also covers operations, billing and analytics tools, identity and scheduling services, and channels selected by users. Their role depends on the specific flow and service terms; being listed does not make every entry a subprocessor. Check the terms of selected integrations and external agents before sharing data.
Providers and services
OpenAI
- Purpose
- Voice transcription and feedback processing with AI.
- Data involved
- Audio for transcription, plus feedback and context needed for requested AI processing.
- When used
- Depending on the feature being used.
Cloudflare R2
- Purpose
- Private snapshots, temporary audio and encrypted backups.
- Data involved
- Saved page views, audio and object metadata; encrypted copies of app and service data.
- When used
- File and backup storage; scope depends on the feature.
Hetzner
- Purpose
- Application hosting and infrastructure.
- Data involved
- Application and operational data on the hosted infrastructure.
- When used
- Depending on the feature being used.
Stripe
- Purpose
- Payments, subscriptions and billing.
- Data involved
- Payment, billing and subscription information handled through the payment workflow.
- When used
- Depending on the feature being used.
Resend
- Purpose
- Email delivery, incoming replies and, when enabled, activation or marketing messages.
- Data involved
- Recipient and sender addresses, email content and delivery information.
- When used
- Scope depends on mail configuration and enabled communications.
Plausible
- Purpose
- Website, tutorial and app analytics running on Voicedot’s server.
- Data involved
- Visits and selected interactions, without note content, email addresses or login tokens.
- When used
- Self-hosted on Voicedot’s server (stats.voicedot.ai), without cookies.
Appliku
- Purpose
- Application deployment and server management.
- Data involved
- Deployment configuration and build logs; administrative access to managed infrastructure.
- When used
- Service operations tool.
Cloudflare (proxy/CDN and Turnstile)
- Purpose
- HTTPS traffic proxying for voicedot.ai and its subdomains, infrastructure protection including bot detection, and Turnstile: protecting sign-in and account creation in the app from automated abuse.
- Data involved
- Traffic handled by the proxy, including request content and technical connection data; at times the cf_clearance cookie on app.voicedot.ai. Turnstile: browser and connection signals (such as the IP address, TLS fingerprint and User-Agent), the token and IP address for verification and the cf.turnstile.u entry in browser storage; no email address and no form content.
- When used
- All traffic to voicedot.ai and its subdomains; Turnstile in the app where you ask for an email with a link. Cloudflare, Inc. as processor (Cloudflare Data Processing Addendum) and, when improving bot detection, also as a separate controller; transfer to the United States under the EU-U.S. Data Privacy Framework.
Google (sign-in)
- Purpose
- Authentication when you choose Google sign-in.
- Data involved
- Account identifier, email, basic profile and authentication data; not note content.
- When used
- Optional identity service when Google sign-in is configured.
Cal.com
- Purpose
- Consultation scheduling when you open the calendar and make a booking.
- Data involved
- Information supplied for the booking, such as name, email, answers and selected time.
- When used
- Optional scheduling service; widget conversations are not sent automatically.
Amazon SES
- Purpose
- Alternative email delivery transport.
- Data involved
- Recipient addresses, message content and delivery information.
- When used
- Only when the SES mail backend is configured; it is not always active alongside Resend.
Slack
- Purpose
- Feedback delivery to the customer’s selected channel; separately, configured operator alerts.
- Data involved
- Customer integration: author email, category, page, pin indicator, note excerpt and dashboard link. Operator alerts: identifiers, metrics and restricted technical signals, without note content or audio.
- When used
- Customer channel only when connected; operator alerts only when enabled. These are separate flows.
Telegram
- Purpose
- Operator notifications about security, availability and product metrics.
- Data involved
- Restricted technical signals, identifiers and metrics; without note content, transcripts or audio.
- When used
- Only when the alert channel is configured and enabled.
Analytics and cookies
Plausible runs on Voicedot’s server. App events are stored in its own database; configured operator notifications may forward restricted identifiers and metrics. They do not send note content, transcripts or audio. A Slack channel selected for feedback delivery is a separate integration and receives a message excerpt and the author’s email.
On the website, in the tutorials and in the app, Plausible counts visits, without cookies. PostHog is not used.
Updates and questions
We review this list when we add, remove or materially change a provider. Customers who need contractual processing terms should also review the DPA and Privacy Policy.
Questions about a provider or data processing? Contact support.