Subprocessors
Programmable LLC · Programmable Watch · last updated November 10, 2026
The third parties that process customer data to run Programmable Watch, what each does, and what it can see. Changes are announced 30 days ahead in the Service and on this page. The shared Programmable sign-in (Logto) is operated by us on our own infrastructure and is not a third party.
| Provider | Purpose | What it sees |
|---|---|---|
| OVHcloud | Hosting of the application and database (Virginia, United States) | Everything the Service stores, encrypted at rest where noted in the DPA |
| Cloudflare | DNS, TLS termination and request filtering in front of the application, and the Turnstile bot check on the public supplier check and the newsletter sign-up | Requests in transit, including IP addresses; no stored data |
| Stripe | Subscription billing | Account email, organisation name, payment details you enter with Stripe directly |
| Resend | Email: digests, invitations, document requests, scheduled exports and the monthly exclusions digest newsletter | Recipient addresses and email content, including supplier names and finding titles |
| Sentry | Error reports (only when enabled) | Stack traces and error messages; no request bodies, cookies, headers or query values |
| Programmable.info | The public-record registry the Service queries (operated by us) | Supplier names, states and identifiers sent as search terms; no decisions, notes or documents |
| Anthropic | Only when an organization's owner turns on AI help in the chat (off by default): reading a typed request Watch's rules couldn't | Only the typed request, with the list of things the chat can do; no supplier records, names from the account or earlier messages |
| Google LLC (Google Analytics) | Counting visits: page views on the public site and the dashboard, under the consent rules in the privacy and cookie policies | Page paths (secret links and tag pages left out), campaign tags, browser and device type, approximate location from the connection, and Google Analytics cookie ids where those are set; dashboard pages are titled only “Programmable Watch”, so no supplier, watchlist or case names |
| Backblaze B2 or compatible object storage | Encrypted off-site backups (only when configured) | Encrypted archives it cannot read |