Subprocessor List

This list is part of the Data Processing Addendum (Data Processing Addendum) between Taint Labs Corporation ("Taint Labs") and Customer. It names the Subprocessors Taint Labs engages to Process Customer Personal Data in providing the Services, and is completed as Annex III of the Standard Contractual Clauses where they apply. Capitalized terms have the meaning given in the DPA.

Version
1.0
Published
November 15, 2026
Entity
Taint Labs Corporation

01Scope of this list

1.1 This list covers Subprocessors of Customer Personal Data only. Taint Labs also uses service providers for its own controller-side Processing of Account Data and website data; those are named in the Taint Labs Privacy Policy (https://stryct.ai/privacy.html, section 10). Where a provider does both, it appears here and there.

1.2 A Third-Party Service that Customer selects, configures or that a Customer Agent calls on Customer's own account (for example, the model provider a Customer Agent uses, or Customer's own source control host) is not a Taint Labs Subprocessor (DPA Section 2.5).

1.3 Entries marked [●] are candidates drawn from the evaluation harness's configuration. They are not yet confirmed as part of the production Services path for Customer Data and must be resolved before this list is given to any customer.

02Infrastructure and service operation

Subprocessor Purpose Customer Personal Data categories Location
Cloudflare, Inc. Hosting and edge delivery, DDoS and bot protection, rate limiting, request logging; D1 databases. [●] All categories in DPA Annex I that the Services store or transmit, including traces and Results [●]; IP addresses and request metadata United States [●]
Clerk, Inc. User sign-up, sign-in, session management and sign-in security for the Services User names, business email addresses, authentication records, session IP addresses and user-agents United States
Resend [●] Transactional email (for example, notifications) [●] User email addresses; message content only if confirmed above United States

03Evaluation path

The evaluation harness can call hosted models for the attacker role, the judge role, and benchmark targets. Its default configuration uses local models only; the hosted providers below are optional. A provider belongs on this list only if a Taint Labs-held account processes Customer Data — for example, a hosted judge model that reads a Customer Agent's trajectory.

Any hosted model provider that processes Customer Data under Taint Labs' account is listed here before it does so, and is used only on API terms that prohibit training on that data and, where the provider makes them available, on zero- or limited-retention terms (DPA Sections 2.5 and 3.5; MSA Section 7.4). No provider in the table below may be moved into the production path until it meets that condition. [●]

Candidate Subprocessor Possible purpose Customer Personal Data categories Location
OpenAI [●] Hosted attacker or judge model Customer Agent traces, prompts, tool outputs sent for judging [●]
Anthropic [●] Hosted attacker or judge model As above [●]
Google (Gemini API) [●] Hosted attacker or judge model As above [●]
DeepSeek [●] Hosted attacker or judge model As above [●]
OpenRouter [●] Routing to hosted attacker or judge models; routes onward to further model providers As above [●]
Langfuse or other trace exporter [●] Optional trace/telemetry export Traces [●]

[●] [●]

04Other providers that may touch Customer Data

Provider Purpose Data Location
Email mailbox host [●] Support and security correspondence sent to legal@, privacy@, security@ or demo@taint.ai Whatever Customer or its Users email, which may include Customer Data United States (per Privacy Policy section 13)
Google (Google Calendar) Demo bookings (pre-contract, controller-side) Booker name and email [●]

05Notice of changes

5.1 Taint Labs will give notice of a new or replacement Subprocessor at least 30 days before it begins Processing Customer Personal Data (DPA Section 6.3), by: (a) updating this list, with a new version number and date and a revision note naming what changed; and (b) emailing the notice to the contact Customer designates for this purpose in the Order Form, or, if none, to Customer's primary account contact. [●]

5.2 Customer may object in writing on reasonable data protection grounds, under DPA Section 6.4, by writing to privacy@taint.ai within that 30-day notice period. The parties will discuss the objection in good faith; if it is not resolved, Customer may terminate only the affected Service and receive a refund of prepaid fees for its unused remainder. Customer has no right to approve or block the engagement of a Subprocessor.

5.3 Taint Labs will use only the published addresses legal@, privacy@, security@, press@ and demo@taint.ai for these purposes; no other mailbox is introduced for subprocessor notices.