Supabase
Purpose: Authentication, database and authorization metadata
Data: Account, workspace, entitlement and proof metadata
Processing region: Seoul (project region)
Every service permitted to process your data.
Effective 2026-08-30 · Last updated 2026-10-19
A provider appearing here does not mean every feature is live; the status page states the active deployment mode.
The last-updated date identifies this notice. Your workspace agreement is the versioned self-service terms and processing addendum linked from the Terms page.
Where each provider processes data, and the basis for any transfer outside Korea. Every region below is the region TAVONEL is configured for; where nothing is configured, the row says so rather than naming one. A configured region is not a residency guarantee — a provider's own control plane, support systems and backups sit outside what our configuration decides — and the privacy notice carries the same statement about international processing.
The two components that hold your document bytes are named with their regions: the content-disarm service that rasterizes and scans every source runs on Google Cloud Run in Seoul, orchestrated by a Cloudflare worker, and the GPU OCR that reads the sanitized result runs on a RunPod endpoint whose region TAVONEL does not pin.
Vercel
Purpose: Website and serverless application hosting; consent-based cookieless website analytics
Data: Requests, operational logs, application metadata and, with analytics consent, public-page views and selected interactions (no workspace events)
Processing region: Seoul (icn1) for serverless functions, set in deployment configuration; requests reach it through Vercel's global edge network
Cloudflare
Purpose: DNS, R2 object storage, and the worker that orchestrates content disarm
Data: Uploaded source bytes and sanitized derivatives
Processing region: The R2 bucket carries an Asia-Pacific location hint, which is best-effort and is not a residency guarantee; the worker runs on Cloudflare's edge network
Google Cloud
Purpose: Content disarm and reconstruction: the IAM-only PDFium and ClamAV service that rasterizes and scans every source before anything downstream reads it
Data: Uploaded source bytes and the sanitized PDF produced from them
Processing region: Seoul (asia-northeast3), set in the service configuration
RunPod
Purpose: Scale-to-zero GPU OCR
Data: Sanitized document candidates and processing telemetry
Processing region: Not pinned. The endpoint is addressed by id and TAVONEL sets no region for it, so we do not state one.
Paddle
Purpose: Merchant-of-record billing when commercial mode is enabled
Data: Billing identity, checkout and subscription events
Processing region: Global infrastructure; may process outside Korea
Resend
Purpose: Transactional inquiry delivery
Data: Inquiry name, work email, optional company, inquiry type, selected plan when arriving from Pricing, optional qualification answers, interface language and message
Processing region: Global infrastructure; may process outside Korea
Purpose: OAuth identity provider; optional, consent-based public website analytics
Data: Google account identity and authentication events; with analytics consent, pseudonymous browser identifiers, device information, public-page visits and selected interactions. No customer source contents or workspace events.
Processing region: Global infrastructure; may process outside Korea
Change notice
Material processor changes are recorded here before they apply to live customer processing, and a sub-processor addition or replacement is notified 30 days in advance with a right to object. Contact privacy@tavonel.com for a data-processing review.
What has changed
2026-09-16. Google Cloud is listed as its own row. The content-disarm service has always run there — a Cloudflare worker orchestrates it, and the PDFium and ClamAV sanitizer is on Google Cloud Run in Seoul — and this page attributed the whole of it to Cloudflare, which understated what Google Cloud receives. No processing changed and no new provider was added; the disclosure was corrected. Processing regions were narrowed from “global infrastructure” to the region each service is configured for, or to a statement that none is pinned. Vercel's purpose gained the cookieless website analytics the privacy notice already described.