Who else touches it, if anyone.

This list applies to the hosted service and this website. If you run Tileward in your own VPC or air-gapped, none of it applies to your data — no sub-processor of ours is in that path, because we are not in that path either.

The list

Current sub-processors.

Sub-processor	Purpose	Data categories	Location
Cloudflare, Inc.	Serves tileward.com. Cloudflare touches the marketing website only, never customer product data (prompts, completions, Context, audit records), which the row below covers.	The referring URL, the country reported for the connection, and the browser user-agent for each page view. Connection IP addresses are necessarily visible to route the request.	United States only.
Amazon Web Services (AWS) and Google Cloud Platform (GCP)	Running the model behind api.tileward.com, storing what Context holds for hosted customers, and hosting the account and billing database — including account email addresses.	Account data (name, work email, company, hashed API keys); prompts, completions, stored conversation turns and documents; audit records.	United States only.
Stripe, Inc.	Taking subscription payments.	Billing contact and payment details. Card details are entered on Stripe’s hosted pages and never reach our servers; we store the brand and last four digits only.	Stripe, Inc. is a US company. Where its systems process and store data is Stripe's own commitment, not ours: see Stripe's own sub-processor list for the current answer.
None — handled in-house	Account email: sign-in, key issuance, billing notices. Sent from our own servers.	Name, email address, message content.	N/A — no third party involved.
Google LLC Google Calendar booking	Booking a call with us. "Book 30 minutes" opens a Google Calendar booking panel in the page — there is no lead form and no separate database of enquiries on our side; the calendar event that results is how we see it.	Whatever you enter on Google's own booking page to reserve a slot — typically your name, email address, and the time you choose.	Google's own commitment, not ours: see Google Workspace's sub-processor list for the current answer.