Atrim Enterprise Data Processing Agreement
This Data Processing Agreement ("DPA") forms part of the Atrim Enterprise Terms of Service (the "Agreement") between Atrim LLC, doing business as Atrim.ai ("Atrim," "we," "us," or "our"), and the customer that has accepted the Agreement ("Customer," "you," or "your"). It governs Atrim's processing of Personal Data on Customer's behalf and, under Schedule 3, its separate processing of retained telemetry examples for detector improvement. By accepting the Agreement, Customer accepts this DPA.
If this DPA conflicts with the Agreement, this DPA governs with respect to (a) the processing of Personal Data and (b) the use of Customer Data, or data derived from it, for detector improvement and the prohibition on model training in Schedule 3. If the Standard Contractual Clauses or the UK Addendum (Section 10) conflict with this DPA or the Agreement, the Standard Contractual Clauses or the UK Addendum govern.
1. Definitions
Capitalized terms not defined here have the meanings given in the Agreement.
- "Data Protection Laws" means all laws applicable to the processing of Personal Data under the Agreement, including the EU General Data Protection Regulation (Regulation 2016/679) ("GDPR"), the GDPR as retained in UK law ("UK GDPR"), the Swiss Federal Act on Data Protection ("FADP"), and the US State Privacy Laws.
- "US State Privacy Laws" means the California Consumer Privacy Act as amended by the California Privacy Rights Act, together with its regulations ("CCPA"), and the comprehensive consumer privacy laws of other US states to the extent they apply to the processing.
- "Personal Data" means any information relating to an identified or identifiable natural person that is contained in Customer Data, and includes "personal information" as defined in the US State Privacy Laws (including information relating to a household).
- "Data Subject" means the natural person to whom Personal Data relates.
- "Telemetry Data" means the traces, metrics, and logs Customer sends to the Service and the aggregates, incident records, findings, and analysis results Atrim derives from them.
- "Account Data" means Customer Data that is not Telemetry Data: account and workspace settings, Authorized User identities and authentication records, billing records, usage-metering counters, and support correspondence.
- "Subprocessor" means any third party engaged by Atrim that processes Personal Data on Customer's behalf, including a third party engaged by another Subprocessor.
- "Security Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data processed by Atrim or a Subprocessor.
- "Standard Contractual Clauses" or "SCCs" means the clauses annexed to European Commission Implementing Decision (EU) 2021/914.
- "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, version B1.0.
2. Roles and Scope
2.1 Roles
For processing on Customer's behalf, including telemetry processing to provide the Service and workspace administration, Customer is the controller (or a processor for its own customers) and Atrim is its processor (or subprocessor). For that processing under the US State Privacy Laws, Atrim is a "service provider" or "processor," and Schedule 2 applies.
Atrim separately acts as an independent controller when processing account and business-contact information for its own billing, business-relationship administration, legal compliance, and handling disputes, as described in the Privacy Policy. Atrim also acts as an independent controller for the separate detector-improvement purpose in Schedule 3. The processor obligations in this DPA apply to processing on Customer's behalf; Schedule 3 preserves contractual protections for retained examples. These distinctions do not reduce the Agreement's confidentiality or security obligations.
2.2 Nature and Purpose of Processing
Atrim processes Customer Data to provide the Service: ingesting, storing, indexing, analyzing, and displaying Telemetry Data that Customer sends from its systems, producing derived analysis of that telemetry, and operating Customer's account. Separately, subject to Customer's contribution controls, Atrim processes selected examples as a controller to develop, test, and improve static detection rules used across the Service under Schedule 3. Analysis includes AI-assisted investigation, in which the portions of Telemetry Data needed to answer a given request are sent to the large language model providers listed in Section 7.
2.3 Categories of Data and Data Subjects
Customer determines what telemetry it sends. Personal Data in Telemetry Data, if any, depends on how Customer instruments its systems and may include identifiers such as IP addresses, user or account IDs, email addresses, and request content that appear in span attributes, metric labels, or log bodies. Personal Data in Account Data processed on Customer's behalf includes the names, email addresses, and authentication records of Authorized Users. Data Subjects may include Customer's end users, employees, and contractors.
2.4 Duration
Atrim processes Personal Data on Customer's behalf for the term of the Agreement and until deletion is complete under Section 6. Schedule 3 governs the duration of detector-improvement processing.
3. Customer Obligations
3.1 Lawful Instructions
Customer is responsible for the lawfulness of the Personal Data it sends, including any required legal basis, notices, and authority to disclose it and instruct processing on its behalf. Atrim remains responsible for the lawful basis and other obligations applicable to its separate controller processing under Schedule 3.
3.2 Personal Data in Telemetry
Customer shall not transmit end-user Personal Data in telemetry except as technically necessary, and shall redact or pseudonymize it before transmission. Atrim does not scan or redact incoming telemetry payloads; the separate safeguards for retained detector examples are in Schedule 3.
3.3 Prohibited Data
Customer shall not send the categories of data prohibited by Section 3.3 of the Acceptable Use Policy, including special categories of Personal Data under GDPR Article 9, data relating to criminal convictions and offences, and Personal Data of children under sixteen (16) years of age, unless Atrim has agreed to receive it in writing.
4. Atrim Obligations
4.1 Processing on Instructions
When processing on Customer's behalf, Atrim will process Personal Data only on Customer's documented instructions, which are the Agreement, this DPA, and Customer's use and configuration of the Service, unless required otherwise by law, in which case Atrim will notify Customer before processing unless the law prohibits it. Atrim will inform Customer if it believes an instruction infringes Data Protection Laws.
4.2 Confidentiality
Atrim will ensure that personnel authorized to process Personal Data are bound by confidentiality obligations and process it only as needed for the purposes permitted by this DPA.
4.3 Detector Improvement
Schedule 3 governs Atrim's use of retained telemetry examples to improve static detection rules, including contribution controls and deletion.
5. Security
5.1 Security Measures
Atrim will implement and maintain the technical and organizational measures described in Annex II of Schedule 1, and will not materially reduce the overall protection they provide during the term of the Agreement.
5.2 Security Incidents
Atrim will notify Customer without undue delay after becoming aware of a Security Incident affecting Customer, using the workspace owner's email or the security contact designated to legal@atrim.ai.
Notice will describe, to the extent known, the incident, the categories and approximate volume of data affected, likely consequences, response measures, and a contact point. Atrim will provide updates as material facts become known, take reasonable steps to contain and remediate the incident, and cooperate with Customer's notification obligations. Incomplete information will not delay initial notice. Notice is not an admission of fault.
6. Retention and Deletion
6.1 Telemetry Data
Customer's query window for raw signals and their signal aggregates is fourteen (14) days on Starter, thirty (30) days on Pro, and sixty (60) days on Scale, measured from their event timestamps, not ingestion. Incident records, findings, and analysis results are not windowed by plan.
Telemetry Data is scheduled for deletion at an age of no more than sixty (60) days. Raw signals and signal aggregates use event time; other records use their applicable creation, update, computation, or ingestion time, or cache expiry. Physical reclamation may take up to one storage partition, and not more than thirty-one (31) days, beyond the applicable retention period. Until reclaimed, expired records may remain accessible to Atrim's authorized operations personnel. Logical deletion under Section 6.3 instead renders the affected data unqueryable by every account.
Service database backups expire within five (5) days of being taken. Backups are not edited; Atrim will not use deleted data in backups except to restore the Service, and will re-apply deletions before restored data is served. For Telemetry Data deleted under Section 6.3, remaining physical copies, including backups, expire no later than ninety-six (96) days after completed logical deletion. Detector Improvement Dataset examples are governed separately by Schedule 3.
6.2 Account Data
Account Data processed on Customer's behalf is retained for the term of the Agreement and deleted under Section 6.3. Atrim may retain only the account, billing, usage-metering, and related correspondence records necessary for its own accounting, tax, legal-compliance, or dispute purposes, for no longer than necessary for those purposes, as described in the Privacy Policy. Retained records remain confidential and protected and may be used only for those purposes. These records are outside the Telemetry Data periods in Section 6.1; this exception does not extend retention of telemetry or detector examples.
6.3 Deletion on Instruction or Termination
A deletion is filed on Customer's verified instruction, given by a workspace owner at privacy@atrim.ai or through self-service account deletion as described below, or, where the Agreement ends without one, at the end of the return window in Section 6.4. Filing revokes the workspace's access to the Service immediately; subject to the limited retention in Section 6.2 and retention required by law, Atrim renders affected Customer Data unqueryable within thirty (30) days of filing ("logical deletion"). The ninety-six (96)-day final-copy deadline in Section 6.1 starts when logical deletion is completed, not when the instruction is filed; together these periods allow no more than one hundred twenty-six (126) days from filing. Logical deletion does not restart a record's ordinary retention period. Personal Data retained as required by law remains confidential and protected and may be processed only for that purpose.
Deletion operates on Customer's workspace. Self-service account deletion in the Service is a workspace deletion instruction only where the deleting user is the workspace's sole member; otherwise it removes that user's access, and Atrim removes that user's remaining Account Data on request at privacy@atrim.ai. Atrim cannot selectively delete one Data Subject's records from inside telemetry payloads; see Section 8.
6.4 Return of Data
During the term, Customer may request a copy of the Customer Data Atrim then holds at privacy@atrim.ai, and Atrim will provide it in a commonly used, machine-readable format. A deletion instruction cannot be reversed and ends access at once, so Customer must request any copy before instructing deletion. Where the Agreement ends without a deletion instruction from Customer, whichever party ends it, Atrim will not file the deletion for fourteen (14) days after the effective date, and will provide a copy requested within that window before filing the deletion.
7. Subprocessors
7.1 Authorization
Customer authorizes Atrim to engage the Subprocessors listed in Section 7.2. Atrim will bind each Subprocessor by written agreement to data protection obligations no less protective than this DPA and remains liable to Customer for its Subprocessors' performance.
7.2 Current Subprocessors
Each entry states the legal entity, the processing location, the purpose, and the data it receives.
- Google LLC (Google Cloud Platform) — United States — hosting and compute for the Service; object storage. Receives all Customer Data.
- ClickHouse, Inc. (ClickHouse Cloud) — United States — storage and query of Telemetry Data. Receives Telemetry Data.
- Supabase, Inc. — United States — account, authentication, and application database. Receives Account Data.
- Stripe, Inc. — United States — payment processing and billing. Receives billing contact and payment details.
- Resend, Inc. — United States — transactional email. Receives Authorized User email addresses and notification content.
- Slack Technologies, LLC — United States — Atrim's internal operational alerting. Receives workspace identifiers and workspace owner email addresses contained in operational alerts.
- Together AI, Inc. — United States — large language model inference for AI-assisted investigation. Receives the portions of Telemetry Data included in an analysis request.
- Anthropic, PBC — United States — large language model inference for AI-assisted investigation. Receives the portions of Telemetry Data included in an analysis request.
- OpenAI, L.L.C. — United States — large language model inference for AI-assisted investigation. Receives the portions of Telemetry Data included in an analysis request.
- OpenRouter, Inc. — United States — routing of large language model requests to inference hosts. Receives the portions of Telemetry Data included in an analysis request. For failover requests, OpenRouter forwards the request only to the failover hosts listed below. For closed-question decision requests, OpenRouter forwards the request only to TypeSafe AI, Inc.; Atrim configures each decision request, and its OpenRouter account, so that the request is served only by a host that does not use request content to train its models.
- TypeSafe AI, Inc. — United States — large language model inference for closed-question decision requests, reached through OpenRouter as the only host that serves the decision model. Receives the portions of Telemetry Data included in a decision request.
- Failover inference hosts reached through OpenRouter: Amazon Web Services, Inc. (Amazon Bedrock) and Google LLC (Vertex AI) — United States or another region in which the host serves the model — large language model inference, used only when the primary provider is unavailable. Atrim configures every failover request so that it may be served only by the hosts named in this entry. If neither is available, the request fails rather than being routed elsewhere.
Large language model providers receive only the portions of Telemetry Data needed to answer a given analysis request. Atrim engages each such provider under terms, or configures each request with settings, under which the provider does not use the request content to train its models. Atrim does not represent that every provider retains nothing: a provider may retain request content for abuse monitoring, safety, or legal compliance for the period its terms provide, and Atrim will state the applicable period for each provider on request.
7.3 Changes
Atrim will update the list in Section 7.2 and notify Customer by email, to the workspace owner or the contact designated under Section 5.2, at least thirty (30) days before a new Subprocessor begins processing Personal Data. Customer may object on reasonable data protection grounds within that period. Atrim cannot exclude an individual workspace from a Subprocessor, so if the objection is not resolved before the new Subprocessor begins processing, Atrim may proceed, and Customer may terminate the affected Service at any time until thirty (30) days after that processing begins and receive a pro-rata refund of prepaid fees for the remaining term. Atrim will not allow a new Subprocessor to process Personal Data before the notice period ends; if a Subprocessor must be replaced urgently, Atrim will suspend the affected function rather than engage an unnotified replacement.
8. Data Subject Requests
For processing on Customer's behalf, Atrim will assist Customer with Data Subject requests through appropriate technical and organizational measures, taking into account the nature of the processing. Requests received directly concerning that processing will be forwarded to Customer without undue delay; Atrim will otherwise respond only to direct the Data Subject to Customer, unless Customer authorizes it. Atrim will respond to requests concerning its own controller processing under applicable Data Protection Laws and cooperate with Customer where a request concerns both parties.
On Customer's request, Atrim will delete, correct, or provide a copy of an Authorized User's Account Data. Atrim cannot locate or selectively delete an individual's records inside telemetry payloads; assistance may require deletion of the affected dataset as a whole. Customer may request assistance at privacy@atrim.ai.
Customer should instruct Atrim promptly and identify any applicable deadline. Atrim will promptly verify the requester's authority and assist with the request, completing the available action within the period in Section 6.3, or sooner where Customer's deadline requires and technically feasible.
9. Assistance and Audits
Atrim will provide reasonable assistance with Customer's data protection impact assessments and prior consultations with supervisory authorities, to the extent they relate to Atrim's processing. Atrim will make available, on request, the information reasonably necessary to demonstrate compliance with this DPA, including written responses to reasonable security questionnaires and any third-party audit reports or certifications Atrim holds.
Where that information is insufficient under Data Protection Laws, Customer or an independent auditor it appoints may audit Atrim's compliance with this DPA no more than once in any twelve-month period, on at least thirty (30) days' notice, during business hours, at Customer's cost, and subject to confidentiality obligations. These frequency, notice, and cost limits do not apply where an audit is required by Data Protection Laws or by a supervisory authority, or where Customer has reasonable grounds to believe Atrim is in breach of this DPA, or in the twelve months following a Security Incident affecting Customer; in those cases Customer may audit on reasonable notice. Atrim will inform Customer if it cannot comply with an audit request because of a legal obligation.
10. International Transfers
10.1 Location
Atrim stores Customer Data in the United States and processes it there, except that a failover inference host identified in Section 7.2 may process an analysis request in another region. Atrim's personnel with access to Customer Data are located in the United States. Atrim will not transfer Personal Data to a third country except under a transfer mechanism recognized by Data Protection Laws.
10.2 EEA Transfers
For processing on Customer's behalf, where Personal Data protected by the GDPR is transferred to Atrim in a country without an adequacy decision, the parties enter into the Standard Contractual Clauses, which are incorporated into this DPA, as follows: Module Two (controller to processor) applies where Customer is a controller and Module Three (processor to processor) where Customer is a processor; Clause 7 (docking) applies; under Clause 9, Option 2 (general written authorization) applies with the notice period in Section 7.3; the optional wording in Clause 11 does not apply; under Clause 13 the competent supervisory authority is determined by Clause 13(a) and Annex I.C of Schedule 1; under Clause 17, Option 1 applies and the law of Ireland governs; under Clause 18, the courts of Ireland have jurisdiction. Annexes I, II, and III of the SCCs are completed by Schedule 1. Customer is the data exporter and Atrim is the data importer; the SCCs are executed by Customer's acceptance of the Agreement and Atrim's provision of the Service.
10.3 UK Transfers
Where Personal Data protected by the UK GDPR is transferred to Atrim, the SCCs as completed in Section 10.2 apply as amended by the UK Addendum, which is incorporated into this DPA. Table 1 of the UK Addendum is completed with the parties' details in Annex I.A of Schedule 1; Table 2 refers to the SCCs as completed in Section 10.2 and Schedule 1; Table 3 refers to Annexes I, II, and III of Schedule 1; in Table 4, either party may end the UK Addendum as set out in its Section 19.
10.4 Swiss Transfers
Where Personal Data protected by the FADP is transferred to Atrim, the SCCs as completed in Section 10.2 apply with these amendments: references to the GDPR are read as references to the FADP; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority under Clause 13; the term "member state" is not read so as to exclude Data Subjects in Switzerland from enforcing their rights in Switzerland under Clause 18(c).
10.5 Onward Transfers
Atrim will ensure that each Subprocessor that receives Personal Data originating from the EEA, the UK, or Switzerland is bound by a transfer mechanism recognized by Data Protection Laws.
11. Liability
Each party's liability under this DPA is subject to the Agreement's limitations and exclusions, including the data protection cap in Section 9.4 of the Agreement, and counts toward the same aggregate limits. Those limitations and exclusions do not apply to the extent prohibited by Data Protection Laws, the SCCs, or the UK Addendum.
12. Term and Survival
This DPA takes effect when Customer accepts the Agreement. All its obligations continue after termination for as long as Atrim or any Subprocessor retains Personal Data from Customer Data, including in backups, legally required copies, or the Detector Improvement Dataset. The prohibition in Schedule 3 on training or fine-tuning machine learning models with Customer Data, or data derived from it, survives without limit of time.
13. Changes to This DPA
Atrim may update this DPA as described in the Agreement. Atrim will not make changes that materially reduce the protection of Personal Data or the protections in Schedule 3 except where required by Data Protection Laws, and will give the notice required by the Agreement for material changes.
14. Contact
Questions about this DPA, or requests for a countersigned copy, may be sent to legal@atrim.ai. Privacy and data-subject requests may be sent to privacy@atrim.ai. Security vulnerabilities and suspected Security Incidents may be reported to security@atrim.ai. Security contacts may be designated by writing to legal@atrim.ai.
Atrim LLC
6523 California Ave SW, #516
Seattle, WA 98136
Schedule 1 — Transfer Particulars (Annexes to the SCCs and UK Addendum)
Annex I.A — List of Parties
Data exporter: Customer, with the legal name, address, and contact details Customer provided at sign-up, in its billing details, or in its Order. Role: controller (Module Two) or processor (Module Three). Activities: use of the Service to monitor its own systems. Signature and date: the exporter's acceptance of the Agreement.
Data importer: Atrim LLC, 6523 California Ave SW, #516, Seattle, WA 98136, United States. Contact: legal@atrim.ai. Role: processor (Module Two) or subprocessor (Module Three). Activities: provision of the Service described in Section 2.2. Signature and date: provision of the Service to the exporter after its acceptance.
Annex I.B — Description of Transfer
- Categories of data subjects: the exporter's end users, employees, and contractors, as described in Section 2.3.
- Categories of personal data: identifiers and request content inside Telemetry Data as described in Section 2.3; names, email addresses, and authentication records of Authorized Users in Account Data processed on the exporter's behalf.
- Sensitive data: none intended; Section 3.3 prohibits the exporter from sending it unless Atrim has agreed in writing, in which case the safeguards agreed in that writing apply.
- Frequency: continuous, for as long as the exporter sends telemetry.
- Nature and purpose: the processing on Customer's behalf described in Section 2.2; the separate controller processing under Schedule 3 is not covered by these processor-transfer particulars.
- Retention period: as set out in Section 6.
- Transfers to subprocessors: to the Subprocessors in Section 7.2, for the purposes stated there, for as long as Atrim uses the Subprocessor for that purpose and, for large language model providers, the period described in Section 7.2.
Annex I.C — Competent Supervisory Authority
Determined by Clause 13(a) of the SCCs: where the exporter is established in an EU member state, the supervisory authority of that member state; where the exporter is not established in an EU member state but falls within the scope of the GDPR under Article 3(2) and has appointed a representative under Article 27(1), the supervisory authority of the member state in which the representative is established; where the exporter is not established in an EU member state but falls within Article 3(2) without having to appoint a representative under Article 27(2), the supervisory authority of one of the member states in which the data subjects whose personal data is transferred are located. The exporter identifies the resulting authority in its Order or by notice to legal@atrim.ai. For the UK Addendum, the UK Information Commissioner. For Swiss transfers, the Federal Data Protection and Information Commissioner.
Annex II — Technical and Organizational Measures
- Encryption. Customer Data is encrypted in transit using TLS and at rest using the storage encryption of the hosting and database providers in Section 7.2.
- Tenant isolation. Each workspace's Telemetry Data is isolated in the telemetry database by per-workspace database credentials and row-level policies, so a workspace can query only its own data and only within its plan's visibility window.
- Access control. Access to production systems by Atrim personnel uses individual, named accounts and is limited to the roles that need it. Production secrets are held in a managed secret store, are never committed to source control, and are rotated on compromise or personnel change.
- Logging and monitoring. Administrative actions, erasure actions, and authentication events are logged, and the logs are retained and reviewed under Atrim's audit-log review process.
- Retention and deletion. Automated retention limits and the deletion process in Section 6, with a documented restore-and-re-erase procedure for backups.
- Incident response. A documented incident-response runbook covering containment, credential rotation, assessment, and the notification in Section 5.2.
- Secure development. Changes to the Service pass code review and automated tests before release; dependencies are monitored for published vulnerabilities; a vulnerability-disclosure contact (security@atrim.ai) is published.
- Personnel. Personnel with access to Customer Data are bound by confidentiality obligations and receive data-protection guidance.
- Subprocessor management. Subprocessors are engaged under written terms per Section 7.1 and reviewed for their security practices before engagement.
- Assistance to the exporter. The measures in Sections 8 and 9.
Annex III — List of Subprocessors
The Subprocessors in Section 7.2, with the contact point legal@atrim.ai for each.
Schedule 2 — US State Privacy Law Terms
To the extent the US State Privacy Laws apply to Personal Data, the following terms apply in addition to the rest of this DPA. Terms used in this Schedule have the meanings given in the applicable US State Privacy Law.
- Customer discloses Personal Data to Atrim only for the limited and specified business purposes of providing the Service on Customer's behalf described in Section 2.2.
- Atrim will not sell or share Personal Data, and will not retain, use, or disclose it for any purpose other than those business purposes and as permitted by the applicable US State Privacy Law, or outside the direct business relationship between Atrim and Customer.
- Atrim will not combine Personal Data received from Customer with personal information it receives from another person, or collects from its own interaction with a consumer, except as permitted by the applicable US State Privacy Law.
- Atrim will comply with the obligations applicable to service providers and processors under the US State Privacy Laws and will provide the same level of privacy protection as those laws require of Customer.
- Atrim will notify Customer within five (5) business days if it determines that it can no longer meet its obligations under the applicable US State Privacy Law.
- Customer may take reasonable and appropriate steps to ensure that Atrim uses Personal Data consistently with Customer's obligations, including through the information and audit rights in Section 9, and may, on reasonable notice, require Atrim to stop and remediate any unauthorized use of Personal Data.
- Atrim will engage subcontractors only under a written contract that imposes the obligations in this Schedule, and will notify Customer of them under Section 7.3.
- Atrim certifies that it understands and will comply with the restrictions in this Schedule.
Schedule 3 — Detector Improvement Dataset
Atrim retains selected Telemetry Data examples (the "Detector Improvement Dataset" or "dataset") solely to develop, test, and improve static detection rules. Customer contributes unless it opts out through the workspace settings page currently labeled "Training Data". The Agreement's rights over Aggregated Data do not apply to this dataset.
Scope. This Schedule governs examples drawn from Customer's Telemetry Data after Customer accepts the Agreement. The dataset also holds telemetry from Atrim's own systems and from test and pre-release workspaces, including data collected before this DPA took effect; that data is not Customer Data and is outside this Schedule.
Controller responsibility. Atrim acts as an independent controller for selecting and retaining examples and using them to improve static detection rules across customers. Atrim is responsible for establishing a lawful basis, providing required notices, responding to Data Subject requests, and ensuring lawful transfers for this purpose. Customer's contribution setting is a contractual control, not a representation of consent from Data Subjects.
Continuing protections. The confidentiality, security, incident-notice, provider, assistance, audit, transfer, liability, survival, and change protections in this DPA continue to protect the dataset. Providers processing examples on Atrim's behalf are subject to the protections in Section 7 as Atrim's processors. Schedule 2's protections also apply contractually, without representing this separate purpose as service-provider processing. Atrim remains responsible for its controller obligations; the processor-transfer clauses in Section 10.2 do not themselves establish a transfer mechanism for this purpose.
Permitted use. Atrim will not use Customer Data, or data derived from it, to train or fine-tune machine learning models or build datasets for that purpose. This does not prevent AI-assisted investigation under Section 2.2. Atrim may use generalized detection rules across customers and retain them after deleting source examples, provided the rules contain no Customer Data or Personal Data.
Safeguards. Examples are drawn from Telemetry Data, never Account Data. Atrim selects fields and masks identifiers before including examples, including exception messages and stack traces. Incident titles, descriptions, and context are excluded. Masking does not guarantee anonymity: service names and other content may identify Customer, and Personal Data may remain. Atrim protects that Personal Data under this DPA and will not attempt to re-identify Data Subjects. Atrim does not sell the dataset or disclose examples to others for their own use; providers may process them only on Atrim's behalf under the protections in Section 7.
Contribution controls. A workspace owner or administrator may opt out at any time. Opting out excludes the workspace from subsequent exports into the dataset; existing examples remain until deleted. While the workspace exists, Customer may request deletion of its examples at privacy@atrim.ai; Atrim will delete them within thirty (30) days.
Retention and deletion. Source Telemetry Data remains subject to Section 6. Dataset examples are retained only for as long as necessary to develop, test, and validate static detection rules, outside the Telemetry Data limits in Section 6.1, subject to earlier deletion on Customer's request or workspace deletion. Atrim will periodically review continued necessity and delete examples no longer necessary. Workspace deletion also deletes its dataset examples, whether or not Customer opted out, within thirty (30) days of the deletion being filed. Section 13 governs changes to this Schedule.