Sub-processors · timestore

This is the code-derived list of third parties that process data on our behalf. The DPA that would adopt this list as an annex is still a draft and is not offered for execution. Every entry below maps to a provider the code actually integrates — we don't list vendors we merely might use, and we don't hide one we do.

What's in use today

The public waitlist still uses Loops (see Privacy). Hosted early access also uses the processors marked in use below: object storage, the control plane, the event bus, sign-in, and billing. General availability is a later bar. This list is who can see early-access data now, not a promise that a DPA has been executed.

The list

Sub-processor Purpose Data processed Status

Loops ↗ coordinator/src/loops-delivery.ts, web/timestore-dev/src/pages/api/waitlist.ts Transactional and early-access email Email address; optional persona answers from the waitlist form; the notification body the recipient already sees in their own queue Waitlist

Cloudflare R2 ↗ coordinator/src/r2-objects.ts Object store — content-addressed packfiles and large blobs Your repository objects (content-addressed by SHA-256); no account profile data Early access

Convex ↗ coordinator/convex/ Control-plane database — accounts, ref metadata, billing records Account identifiers, ref/checkpoint metadata, subscription rows; no repository bytes Early access

NATS (Synadia) ↗ coordinator/src/nats-announce.ts Durable event bus — ref-announce / replication notifications Ref-announcement events (repo + ref identifiers and checkpoint ids); no repository bytes Early access

Clerk ↗ web/app-timestore/app/server/auth.ts Authentication and session management Authentication identity (email / OAuth identifier), session tokens Early access

Stripe ↗ coordinator/convex/billing.ts Payment processing and subscription billing Billing contact, payment method (held by Stripe — never by us), subscription state Early access

Where your data lives (residency)

We're going to be straight about this rather than gesture at a region map we can't honor.

Objects (Cloudflare R2). Our object store does not pin a region — it uses Cloudflare's default auto placement, where Cloudflare chooses the location. We do not set a fixed bucket region in code, so we won't claim one.
Control plane (Convex) and event bus (NATS). We do not offer a per-customer region choice for either. We will not name a region the code does not pin.

Per-region data residency — including EU-only residency — is not offered. Nothing here is a commitment that your data is stored in, or kept out of, any particular country. If region residency is a hard requirement, ask legal@timestore.dev before you rely on hosted.

Changes to this list

A notice period for adding or replacing a sub-processor belongs in the DPA, which is still a draft and not offered for execution. Until that exists, we keep this page current and date-stamped. Email legal@timestore.dev to hear about changes.