Service Providers

Last updated: November 3, 2026

These are the companies that receive personal information so we can run Koutei PDF. Our Privacy Policy explains why we collect it and how long we keep it.

1. Providers we use today

Supabase

What for: Sign-in and our database
What it receives: Account details, sign-in records, credit balance, plan and payment records, billing notifications from Paddle, API key hashes, the free invoice generator’s limit counters (a keyed hash of an IP address, never the address), and document generation counts (under a keyed code, not the account ID); and a 90-day record of each final document made in the app and of each document or preview made with an API key (for example the template, size, time and any reference label you send; never the document or what you put in it), 24-hour retry records (one-way hashes of the Idempotency-Key and the request, with the template, its version, whether it was a final document or a preview, its status and the document’s ID) and API rate-limit records (keyed, one-way hashes)
Where: EU West (Ireland, eu-west-1)
Role: Processes data on our behalf (processor)

Vercel

What for: Hosts the website and its server code, and counts visits to it (Web Analytics, without cookies)
What it receives: Every web request, including the document details you submit (passed through, not stored); request logs with IP address and browser details; for visitor statistics, the time, the page viewed and its general route, the address of the page that linked to it as the browser reports it, approximate location (country, region and city), browser and operating system with their versions, device type and the version of the statistics script, with a request hash deleted after 24 hours; a count of each invoice made, with the page that made it and its link tag; and, from visitors to the free invoice generator who turned on “Remember my details on this device”, a count of each return on a later day, with the same details as a page view and how long since their last invoice there (one day, two to seven days, eight to fourteen days, or longer)
Where: US East (Washington, D.C., iad1), with a global edge network
Role: Processes data on our behalf (processor)

Railway

What for: Hosts the engine that renders your PDFs and images
What it receives: The document details you submit, only while the document is rendered; logs without document content
Where: US West (California)
Role: Processes data on our behalf (processor)

Paddle

What for: Merchant of record: checkout, payments, tax, invoices, receipts and refunds
What it receives: Your email address and account ID from us; the payment, address and tax details you give Paddle at checkout
Where: United Kingdom, with global processing
Role: Uses data under its own privacy policy (independent controller)

Resend

What for: Sends sign-up confirmation, sign-in link and password reset emails
What it receives: Your email address and the email we send you
Where: United States
Role: Processes data on our behalf (processor)

Google (Sign in with Google)

What for: Lets you sign in with your Google account, if you choose to
What it receives: Google shares your name, email address, profile picture and Google account ID with us
Where: Global
Role: Uses data under its own privacy policy (independent controller)

Google Workspace

What for: Our business email, for support and privacy requests
What it receives: Emails you send us and our replies
Where: Global
Role: Processes data on our behalf (processor)

What for: Delivers short alerts to us when a new account is created, when our billing system needs attention, each morning with a count of the day before and when an invoice is made with the free invoice generator (at most about twenty notices an hour)
What it receives: For each new account: when it was created, how it signed up (for example email or Google), its link tag if it has one, whether its email address is confirmed, and the part of the email address after the @ (for example gmail.com); never the rest of the email address, a name or an account ID. Billing alerts: how many payment notifications from Paddle need attention and their type (for example transaction.completed), that a payment notification could not be verified as coming from Paddle, that a possible duplicate subscription was detected, or that the access key our server uses with Paddle was refused or missing, and when; never anything about who they concern. Daily count: each morning, how many accounts were created the day before, how many made documents and how many documents, how many API keys were made and how many accounts hold one, how many accounts paid for the first time, and how many accounts have made documents on two or more of the last 14 days; numbers only, never anything about who they concern. When an invoice is made with the free invoice generator (at most about twenty notices an hour): when it was made and how many have been made that day; never anything about who made it or what it contains
Where: Global
Role: Offers no data-processing agreement, so it receives only what is listed above

Cloudflare (Turnstile)

What for: Runs the security check on the sign-in page, which tells people from automated bots
What it receives: While the sign-in page runs the check: your IP address, details of your browser and its connection (such as the user agent and TLS fingerprint) and which site is asking, never what you type into the form; and, while the check is switched on in Supabase, the check’s one-time token, which Supabase sends back to Cloudflare with your IP address to confirm it. Cloudflare also uses these signals to improve its bot detection, under its Turnstile Privacy Addendum.
Where: Global (Cloudflare’s network)
Role: Processes data on our behalf (processor)

2. Changes to this list

We update this page before we start using a new provider that will receive personal information. If you have a business agreement with us that requires notice, we will also tell you directly. Questions: privacy@kouteisystems.com.