Support and Service Level Policy
This Support and Service Level Policy ("Policy") is incorporated into the Master Subscription Agreement between Taint Labs and Customer. Capitalized terms not defined here have the meanings given in the Master Subscription Agreement or the Product Appendix.
01Scope
1.1 Covered Services. This Policy applies to the Services that an Order Form identifies as generally available and that Customer has subscribed to for a current, paid Subscription Term ("Covered Services"). At present the only Service with a Product Appendix is Stryct Finder (Product Appendix 1).
1.2 Support Level. Each Order Form states the support level that applies to Customer (Section 2). If an Order Form does not state one, Standard Support applies.
1.3 Early Access Services. Early Access Services are excluded from the Availability Commitment (Section 5), the Evaluation Run commitments in Section 6.3, and Service Credits (Section 7). Taint Labs will provide support for Early Access Services on a commercially reasonable, best-efforts basis, without response targets, unless the Early Access Terms or an Order Form state otherwise. The Early Access Terms control for Early Access Services.
1.4 Not covered. This Policy does not cover:
(a) the public website at stryct.ai, the public leaderboard, the Attack Catalog and Documentation at docs.stryct.ai, or any other freely available content, none of which carries an availability commitment;
(b) Customer Agents, Third-Party Services, or any Customer code, CI system, repository host or infrastructure;
(c) professional services, custom attack development, remediation work on a Customer Agent, or security consulting, which require a separate Order Form or statement of work [●]; and
(d) the interpretation of Results beyond explaining how the Services produced them (Section 3.4).
02Support Levels
2.1 Levels. Taint Labs offers the support levels below. All figures are placeholders pending business confirmation; suggested values reflect common enterprise SaaS practice and are not commitments until confirmed.
| Standard Support | Premium Support | |
|---|---|---|
| Included with | Every paid subscription to a Covered Service | Purchased separately on an Order Form [●] |
| Channels | [●] (written, ticket or email) | [●], plus [●] |
| Support hours | [●] | [●] |
| Named Customer contacts | [●] | [●] |
| Initial response target, S1 | [●] | [●] |
| Initial response target, S2 | [●] | [●] |
| Initial response target, S3 | [●] | [●] |
| Initial response target, S4 | [●] | [●] |
| Status updates during an open S1 | [●] | [●] |
| Designated support contact at Taint Labs | No | [●] |
| Periodic service review | No | [●] |
2.2 Response targets. A response target is the time between Taint Labs' receipt of a properly submitted request (Section 3.2) and Taint Labs' first response from a person, not an automated acknowledgment. Response targets are targets, not guarantees of resolution or of a resolution time. Failure to meet a response target is not a breach of the Agreement and does not give rise to Service Credits, unless an Order Form expressly provides otherwise.
2.3 Language. Support is provided in English.
03Requesting Support
3.1 Channel. Customer submits support requests through [●]. No support mailbox is published at present; Taint Labs will tell Customer the support channel in writing at onboarding and before any change to it. The published addresses (legal@, privacy@, security@, press@ and demo@taint.ai) are not support channels, except as stated in Section 3.5 and Section 9.
3.2 What a request must include. A request is properly submitted when it comes from a named Customer contact and includes: the affected Service and workspace or project; the proposed severity; a description of the problem and its business impact; the time it started; the identifier of any affected Evaluation Run, CI job or pull request; and steps to reproduce, where known. Taint Labs may reasonably reassign severity under Section 4.3.
3.3 Severity outside support hours. Under Standard Support, a request submitted outside support hours is treated as received at the start of the next support-hours period. Under Premium Support, an S1 request is received when submitted [●].
3.4 Questions about Results. Support includes explaining how the Services produced a Result: which attack ran, the trace behind a finding, how the benign twin task was compared, and how a grade or score was calculated under the Documentation. Support does not include advising on whether a Customer Agent is safe to deploy, designing Customer's remediation, or re-grading a Result. Results are measurements, not certification.
3.5 Vulnerabilities in the Services. A suspected security vulnerability in the Services themselves should be reported to security@taint.ai or through stryct.ai/report rather than the support channel, so that it reaches the team that handles it.
04Severity Definitions
4.1 Levels.
| Severity | Definition | Examples |
|---|---|---|
| S1 — Critical | The Covered Service is unavailable to all of Customer's Users, or a fault in the Services blocks every Customer CI pipeline that runs the Services, and no workaround exists. | The web application or API returns errors for all requests; the Taint Labs CI integration fails every job before any Evaluation Run starts, across all Customer repositories. |
| S2 — High | A major function of the Covered Service is materially impaired, or a subset of Customer pipelines is blocked, and no reasonable workaround exists. | Evaluation Runs start but none complete; Results cannot be retrieved; CI check status is never reported back to pull requests in some repositories. |
| S3 — Medium | A function is impaired but a reasonable workaround exists, or the impact is limited to a small number of Users, runs or repositories. | Report export fails in one format; intermittent run failures that succeed on retry; a dashboard view is slow or incomplete. |
| S4 — Low | A general question, a documentation issue, a cosmetic defect, or a feature request. | How to configure a run; a broken Documentation link; a request for a new attack class. |
4.2 Security findings are not support incidents. A finding, failed grade, low score or successful attack reported in Customer's Results about Customer's own Customer Agent is the Services working as intended. It is not a defect, an outage, or a support incident at any severity, and it does not count against availability. Likewise, a CI pipeline that fails because Customer configured it to fail on a finding is not blocked by the Services. Customer may still open an S3 or S4 request to ask how a finding was produced (Section 3.4). If Customer believes a Result is wrong because the Services malfunctioned (for example, a run graded against the wrong Customer Agent, or a trace that does not match the finding), that is a defect and is assigned severity under Section 4.1 based on its impact.
4.3 Reassignment. Taint Labs may reassign severity, after telling Customer why, where the request does not meet the definition proposed. An S1 or S2 request requires Customer to keep a contact reasonably available to work with Taint Labs while it is open; if Customer is not available, Taint Labs may downgrade the request until Customer is.
05Availability Commitment
5.1 Commitment. For each Covered Service, Taint Labs will use commercially reasonable efforts to make the Covered Service Available at least [●] of the time in each calendar month (the "Availability Commitment"). [●]
5.2 Definitions.
(a) "Available" means that the Covered Service's [●] accept and respond to properly formed requests without a server-side error attributable to Taint Labs.
(b) "Unavailable" means a period of at least [●] consecutive minutes during which the measured components are not Available, as determined under Section 5.3. Shorter periods are not counted.
(c) "Monthly Availability" means: (total minutes in the calendar month minus Excluded Minutes minus Unavailable minutes) divided by (total minutes in the calendar month minus Excluded Minutes), expressed as a percentage.
(d) "Excluded Minutes" means minutes in which the Covered Service is not Available for a reason listed in Section 5.4.
5.3 Measurement. Taint Labs measures availability with [●] and its own service logs. Taint Labs' measurement controls unless Customer shows, with its own records, that it is materially wrong. [●]
5.4 Exclusions. Unavailability caused by any of the following is excluded from the calculation and is not eligible for Service Credits:
(a) Scheduled Maintenance performed under Section 8, and Emergency Maintenance up to [●] hours per calendar month;
(b) Third-Party Services, including outages, rate limits, errors, deprecations or latency of any model API, model provider, SDK, MCP server, repository host or CI provider that a Customer Agent calls or Customer selects. A model API, hosting or other provider that Taint Labs itself uses under its own account is Taint Labs' Subprocessor or subcontractor (MSA Section 6.4), not a Third-Party Service, and its unavailability is not excluded under this item;
(c) Customer Agents, including a Customer Agent that is unreachable, misconfigured, crashes, times out, refuses tasks, or exhausts its own credentials, quota or budget;
(d) Customer's systems and network, including Customer's CI runners, firewalls, proxies, DNS, credentials, internet access, or the environment in which Customer operates an on-premises deployment of Stryct Finder (a Customer-Run Runner under Product Appendix 1, Section 4.3) [●];
(e) Customer's use contrary to the Agreement, the Acceptable Use Policy or the Documentation, including exceeding usage limits on an Order Form, and suspension under the Agreement;
(f) Force majeure events as described in the Master Subscription Agreement (Section 23.3), and widespread internet disruptions outside Taint Labs' reasonable control;
(g) Early Access Services, and any feature labeled early access, beta, preview or pilot within an otherwise Covered Service; and
(h) Actions taken at Customer's request or by Taint Labs to protect the security or integrity of the Services or other customers, where reasonable and promptly communicated.
06Evaluation Runs
6.1 Availability is not run completion. The Availability Commitment measures whether Customer can reach the Covered Service and start, monitor and retrieve Evaluation Runs. It does not measure how long an Evaluation Run takes to finish, and it is not met or missed by the outcome of any run.
6.2 Why run time varies. An Evaluation Run executes attack tests and benign twin tasks against a Customer Agent and usually depends on Third-Party Services, such as the models and tools the Customer Agent calls. Run duration depends on the number of attacks selected, the size and speed of the Customer Agent, the concurrency Customer purchased, and the rate limits and latency of those Third-Party Services. Taint Labs does not control most of these factors.
6.3 Run commitments. For Covered Services, Taint Labs will:
(a) begin executing a properly submitted Evaluation Run within [●] of submission, measured as a monthly [●], excluding runs held in a queue because Customer has reached its purchased concurrency [●];
(b) not charge, or count against usage limits, any Evaluation Run that fails to complete because of a fault in the Services, and permit Customer to re-run it [●]; and
(c) report a run that cannot complete as failed, with the reason Taint Labs can determine, rather than return a partial Result presented as complete.
6.4 No completion-time guarantee. Any run-duration estimate shown in the Services or the Documentation is an estimate, not a commitment. A slow or failed run caused by a Third-Party Service or a Customer Agent is not a support incident above S3 and does not give rise to Service Credits. [●]
07Service Credits
7.1 Schedule. If Monthly Availability for a Covered Service falls below the Availability Commitment, Customer is eligible for a credit against the monthly Fees for that Covered Service for the affected month ("Service Credit") as follows:
| Monthly Availability | Service Credit (% of that month's Fees for the affected Covered Service) |
|---|---|
| Below [●] and at or above [●] | [●] |
| Below [●] and at or above [●] | [●] |
| Below [●] | [●] |
Where Fees are billed other than monthly, the monthly fee is the fee for the billing period divided by the number of months in it.
7.2 Claim process. To receive a Service Credit, Customer must submit a claim through [●] within [●] days after the end of the affected month. The claim must identify the Covered Service, the dates and times of the Unavailability, and any supporting records. Taint Labs will review the claim and respond within [●] days. A claim not submitted on time is waived.
7.3 Application. Approved Service Credits are applied to the next invoice for the affected Covered Service. Service Credits have no cash value, are not refundable, and cannot be transferred, except that if the Agreement ends without a further invoice, Taint Labs will [●].
7.4 Cap. Service Credits for a Covered Service in any calendar month will not exceed [●] of the fees for that Covered Service for that month.
7.5 Eligibility. Service Credits are not available while Customer has undisputed fees more than [●] days overdue, during a free, trial, pilot or Early Access period, or for Unavailability Customer did not report to Taint Labs while it was occurring, where Customer could reasonably have done so.
7.6 Sole remedy. Except as provided in Section 7.7, Service Credits are Customer's sole and exclusive remedy, and Taint Labs' entire liability, for any failure to meet the Availability Commitment.
7.7 Chronic failure. If Monthly Availability for a Covered Service falls below [●] in [●] months in a rolling [●]-month period, or below [●] in any single month, Customer may terminate the affected Covered Service by written notice to legal@taint.ai within [●] days after the end of the month that gives rise to the right. On such termination, Taint Labs will refund any prepaid Fees for the affected Covered Service covering the period after the termination date. This right is in addition to Service Credits already earned.
08Maintenance
8.1 Scheduled Maintenance. Taint Labs will give Customer at least [●] notice of Scheduled Maintenance expected to make a Covered Service Unavailable, and will use reasonable efforts to perform it during [●]. Scheduled Maintenance will not exceed [●] hours per calendar month.
8.2 Emergency Maintenance. Taint Labs may perform maintenance without advance notice when needed to address an urgent security vulnerability or to prevent imminent harm to the Services or to Customer Data ("Emergency Maintenance"), and will notify Customer as soon as reasonably practicable.
8.3 Notice method. Maintenance notices are given by [●].
8.4 Runs during maintenance. Taint Labs will use reasonable efforts to let in-progress Evaluation Runs finish, or to report them as failed and re-runnable under Section 6.3(b), rather than lose them silently.
8.5 Infrastructure. The Services run on third-party infrastructure, including Cloudflare [●]. Maintenance that an infrastructure provider performs on its own platform is governed by Section 5.4(b) unless counsel resolves the bracket in that section otherwise.
09Security Incidents
9.1 Separate process. Security incidents affecting Customer Data are handled under the Information Security Addendum and, where Personal Data is involved, the Data Processing Addendum, including their notification timelines and contents. This Policy's severity levels and response targets do not govern those notifications and do not shorten or extend them.
9.2 Reporting. Customer should report a suspected security incident involving the Services to security@taint.ai, and may also open an S1 or S2 support request if the incident affects availability.
9.3 Not a security incident. A finding about a Customer Agent in Customer's Results is not a security incident affecting the Services (Section 4.2).
10Customer Responsibilities
Customer will:
(a) designate and keep current its named support contacts, and make sure they are trained Users familiar with the Documentation;
(b) submit requests as described in Section 3.2 and provide reasonable information, logs, run identifiers and access needed to diagnose the issue;
(c) maintain the Customer Agent, its credentials, quotas and budgets for any Third-Party Services it calls, and the CI configuration and runners that invoke the Services;
(d) keep the CI integration and any client components on a version that Taint Labs supports [●];
(e) apply workarounds and fixes Taint Labs provides, where reasonable;
(f) not include in a support request secrets, credentials, or Personal Data beyond what is needed to resolve it; and
(g) use the Services in line with the Agreement, the Acceptable Use Policy and the Documentation.
Taint Labs is not responsible for failing to meet a target in this Policy to the extent caused by Customer not meeting these responsibilities.
11Changes to this Policy
11.1 Taint Labs may update this Policy from time to time. An updated Policy applies from its effective date, except that no update will materially reduce the support level, response targets, Availability Commitment, Service Credits or chronic-failure right that apply to Customer during Customer's then-current Subscription Term. A materially less favorable change takes effect for Customer only at the start of its next renewal term.
11.2 Taint Labs will give Customer at least [●] days notice of a material change by [●], and will keep prior versions available on request [●].
11.3 Order of precedence. If this Policy conflicts with another document in the Agreement, the following order applies (highest first): (1) the Order Form, only for commercial terms it expressly overrides; (2) the Data Processing Addendum, for processing of Personal Data only; (3) the Information Security Addendum; (4) the Product Appendix; (5) the Master Subscription Agreement; (6) this Policy and the Acceptable Use Policy. The Early Access Terms control over all of the above for Early Access Services only.