Data Processing Agreement
Version 1.1 · 2026-11-17
1. Parties and scope
This Data Processing Agreement ("DPA") is between:
- the customer that uploads data to Attify or connects one of its systems to Attify ("Customer", the controller); and
- Dor Tagger, trading as Attify ("Attify", the processor).
It forms part of the Terms of Service and applies whenever Attify processes personal data contained in the Customer's conversations, meetings and bookings (from an upload or a connected help desk, CRM, calendar, booking tool, agent platform or observability tool), or in the interactions a vendor streams to Attify as witnessed data ("Customer Personal Data"). For witnessed data, the vendor that streams it is a Customer under this DPA, and so is the vendor's customer once it consents, each in the role section 2.4 sets out. It does not cover the account, billing and service data Attify handles as its own controller, which the Privacy Policy describes.
If this DPA and the Terms conflict on data protection, this DPA wins. "Data protection law" means the EU General Data Protection Regulation, the UK GDPR, the Swiss Federal Act on Data Protection, and any other data protection law that applies to the processing. Terms such as controller, processor, personal data, processing and personal data breach have the meanings that law gives them.
2. Roles
2.1 Uploads, connected audits and buyer dashboards
When the Customer uploads an export for a check, or connects its own systems for a connected audit or a buyer dashboard, the Customer is the controller and Attify is its processor. Attify computes the results the Customer asks for and returns them to the Customer. If the Customer chooses to contribute its anonymous audited outcomes to the Attify Index, Attify also pools them, as aggregates only, into the Index under that consent.
2.2 Vendor verification and traction reports
In a vendor verification program three parties are involved: the vendor (whose AI agent is audited), its customer (whose systems hold the records), and Attify.
- The customer that connects its systems is the controller of the records in them, and the Customer under this DPA. The vendor is not a party to this DPA for those records and never receives them.
- The customer instructs Attify through the consent scope it agrees to before connecting. The scope is recorded word for word, with who agreed, for which organization and when. Under it, the customer instructs Attify to:
- read every record in the connected system from the last 90 days, then each day's new ones, with read-only access;
- keep message text 30 days, then delete it, and keep the scores computed from it;
- compute scores under the standard and show the vendor the customer's results (rates and counts), never its records;
- include the customer in published results that pool every customer and never name it;
- let the vendor share a traction report with investors it chooses, with the customer's usage and results as a numbered customer, never by name unless the customer opts in;
- read the email addresses of the system's admins (or the platform account's people) to check that the customer is a company separate from the vendor, and email one of them to ask whether the customer uses the vendor's product;
- let Attify reviewers read a redacted sample to check the judge.
- Aggregated results (rates, counts and intervals across many records) do not identify any data subject. Attify publishes and attests them as its own opinion under the published standard.
- The vendor is a separate customer of Attify. It receives results and consent records only. Its reports, including the per-customer edition of a program's attestation, quote no record.
2.3 Attify as controller
Attify is the controller of account data (names and emails of the people who use Attify), billing data, consent records, vendors' attestations for their deployments, the audit log and the traction-report view log. The Privacy Policy covers them.
2.4 Witnessed data
Witnessed data is what a vendor's AI agent sends Attify about its interactions at one customer (a deployment), as they happen, through the Ingest API, an SDK or OpenTelemetry, or what Attify reads from the vendor's own agent platform or observability account for a deployment. Every request is authenticated with a key Attify issues for that deployment, and Attify timestamps every event when it arrives. Attify reads nothing from the customer's own systems unless the customer connects one.
- The vendor sends the data and is a Customer under this DPA for it. Attify processes it on the vendor's instructions, to produce the vendor's private report on the deployment. Without the customer's consent, that is the only use.
- The customer instructs Attify once it consents. Witnessed data counts toward a vendor's verification or badge only after the vendor's customer records its consent in Attify: who agreed, for which organization, when, the scope word for word and the retention, as for connected data (section 2.2). From then on Attify also processes the data on the customer's instructions, under that scope. The scope includes the monthly reconciliation: the customer confirms the month's total from its own records or the vendor's invoices, and checks a random sample of interactions against its own systems. Where the customer has connected its own help desk, Attify may answer the sample from it.
- Withdrawal. The customer can withdraw its consent at any time. Attify then processes the vendor's interactions only for the vendor's private report, and deletes their text on the usual schedule (section 9).
- Roles. The people in witnessed data are the customer's end users, and people on the customer's side who take part. Whether the vendor sends their data to Attify as the customer's processor or as a controller in its own right depends on the vendor's contract with its customer, and the vendor answers for it (section 4). Where the vendor acts as the customer's processor, Attify acts as the vendor's subprocessor, and the vendor is responsible for any authorization its customer must give for that. Once the customer consents, Attify also acts as the customer's processor for verification. In every case Attify acts only on the instructions this section describes.
3. Attify's obligations
Attify will:
- process Customer Personal Data only on the Customer's documented instructions: this DPA, the Terms, the consent scope where one applies, and the settings the Customer chooses in the service. If the law requires other processing, Attify will tell the Customer first unless the law forbids it;
- tell the Customer if it believes an instruction breaks data protection law;
- make sure everyone authorized to process Customer Personal Data is bound by confidentiality;
- apply the technical and organisational measures in Annex II;
- use subprocessors only as section 5 allows;
- help the Customer, taking into account the nature of the processing, to answer data subjects' requests and to meet its obligations on security, breach notification, impact assessments and prior consultation;
- delete or return Customer Personal Data as section 9 says;
- make available the information needed to show compliance with this DPA, and allow audits as section 8 says.
Attify will not sell Customer Personal Data, use it for advertising, or use it to train AI models.
4. Customer obligations
The Customer:
- is responsible for having a lawful basis to share the data with Attify, and for any notice or consent its data subjects need;
- confirms its instructions comply with data protection law;
- uploads or connects only data it has the right to share, and only from systems it controls;
- keeps its own access credentials, links and tokens safe.
For witnessed data, the vendor that streams it also warrants that:
- before a deployment streams, it has attested that it has the right to share that customer's interaction data with Attify for verification. Attify records who attested, when and the version of the Terms;
- it holds that right for as long as it streams, gives the end users any notice it owes them, and sends no data it may not share.
A false attestation is a breach of the Terms (section 6), and grounds to suspend the vendor's access and revoke any score it supported.
5. Subprocessors
- The Customer gives general authorization for Attify to use the subprocessors listed in Annex III.
- Attify will tell the Customer of any intended addition or replacement at least 30 days in advance, by email to the Customer's organization owners and by updating Annex III. The Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the Customer may disconnect and end the affected service, and Attify will refund prepaid fees for the unused period.
- Attify will impose on each subprocessor data protection obligations no less protective than this DPA, and remains responsible to the Customer for its subprocessors.
6. Personal data breaches
- Attify will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.
- The notice will describe, as far as known: what happened, the categories and approximate number of data subjects and records affected, the likely consequences, and the measures taken or proposed. Information not yet known will follow as it becomes available.
- Attify will take reasonable steps to contain the breach and reduce its effects, and will help the Customer with any notification it must make.
- Notice goes to the Customer's organization owners by email. Notifying a breach is not an admission of fault.
7. International transfers
- Attify's API and database run in the EU (Render and Supabase, Frankfurt).
- Attify is operated from a country that the European Commission, the United Kingdom and Switzerland recognize as giving adequate protection to personal data, so Attify's own access to Customer Personal Data from there needs no further safeguard. If that recognition lapses, the parties agree to the Standard Contractual Clauses (Commission Decision (EU) 2021/914), Module 2 (controller to processor), incorporated by reference, with the details in Annex I, the general authorization in section 5 as clause 9 option 2, and the law and courts of Ireland under clauses 17 and 18.
- Some subprocessors in Annex III process Customer Personal Data outside the EEA, including in the United States. For each such transfer Attify relies on the EU-US Data Privacy Framework where the subprocessor is certified under it, and otherwise on the Standard Contractual Clauses, Module 3 (processor to processor).
- For transfers subject to the UK GDPR, the UK International Data Transfer Addendum to the Standard Contractual Clauses applies. For transfers subject to Swiss law, the Standard Contractual Clauses apply with the amendments the Swiss Federal Data Protection and Information Commissioner requires, the Swiss Act standing in for the GDPR where it applies.
8. Audits
- Attify will answer the Customer's reasonable written questions about its processing and provide the information needed to show compliance with this DPA.
- If that information is not enough, or a regulator requires it, the Customer may audit Attify, at most once a year, with 30 days' notice, during business hours, at its own cost, through an auditor bound by confidentiality. The audit must not give access to other customers' data.
- The published standards, judge prompts and verification rules are public and can be checked by anyone.
9. Return and deletion
- During the service, Attify deletes Customer Personal Data on these schedules (Annex II, part G):
- an uploaded file within 30 minutes of upload, or when the full audit finishes;
- a check's results and reports after 30 days;
- message text from a connected system 30 days after the record's last update, with the judge's cached answers for that connection;
- message text of witnessed data, redacted when it arrives, at most 30 days after it arrives, whether or not the customer consented, with the judge's cached answers for that deployment.
- On disconnect, Attify deletes the connection and everything read from it: records, scores, per-record outcomes, queued jobs, the encrypted credentials and the judge cache. Attify also revokes its authorization at the platform where the platform's API allows it, and otherwise shows the Customer where to revoke it. On deletion of a deployment, Attify deletes everything the deployment sent: its events and interactions, the scores computed from them, and its keys.
- On deletion of the organization, Attify deletes the organization's data. The Customer's organization owner can first export it as JSON.
- What stays. Consent records and audit-log entries are kept as the evidence of what was agreed and done; they hold no message text. Scores already published, their attestations, Index editions and the public changelog stay as the public record; they contain pooled aggregates, not Customer Personal Data. A frozen traction report keeps its aggregate numbers. For witnessed data, event metadata (ids, times, sequence numbers, a digest of each event and how the request was authenticated) and the scores computed from the text are kept without text until the deployment is deleted; the vendor's attestation stays in the audit log.
- Attify may keep data longer only where the law requires it, and then only for that purpose.
10. Liability and term
- Each party's liability under this DPA is subject to the limits in the Terms, unless data protection law does not allow it.
- This DPA lasts as long as Attify processes Customer Personal Data, and ends when that data has been deleted or returned under section 9.
11. Changes
Attify may update this DPA to reflect changes in law or in the service. It will tell the Customer's organization owners by email at least 30 days before a change that reduces the protection of Customer Personal Data applies.
Annex I: Details of processing
Annex II: Technical and organisational measures
A. Access control
- API key. Every server-to-server call to the API needs the API key. The browser never sees it: the web server adds it.
- Sign-in. Sessions come from the identity provider and are verified on every call (signature, issuer, expiry, authorized party).
- Role-based access. Owners and members per organization; reviewer and admin roles count only in Attify's own organization, so no customer can grant itself staff access. A connection is visible only to its token holder or the members of the organization that connected it.
- Links and tokens (check links, invitations, share links, investor requests) are random and stored only as hashes. Share links expire (30 days by default, at most 90) and can be revoked; an optional allowlist limits them to named, signed-in viewers.
- Deployment keys. Witnessed data is accepted only with a key Attify issues for that deployment, shown once, stored sealed, and revocable. Requests are signed with it (from OpenTelemetry, they carry it over TLS instead), and a stale signature is refused. Attify timestamps every event when it arrives.
B. Encryption
- Traffic is encrypted in transit with TLS.
- Connector credentials are encrypted at rest with envelope encryption: each secret has its own random data key (AES-256-GCM), wrapped by a key-encryption key that never touches the database. The row's id is authenticated with the ciphertext, so a copied ciphertext does not decrypt elsewhere. Keys can be rotated.
- Attestations are signed with Ed25519, and so is the receipt Attify returns for every batch of witnessed data it receives (what arrived and when); public keys are published.
C. Minimization and redaction
- Connectors store only the fields the standard needs, and read with read-only access.
- Before any text reaches the LLM judge, it is redacted: links, email addresses, @handles, order, account and ticket numbers, phone numbers, long digit runs and first names in direct address become placeholders. Redaction is pattern-based and cannot catch every personal detail in free text.
- Only a sample reaches the judge: at most 200 records per subject per audit, plus small samples for contact reasons.
- Witnessed text is redacted when it arrives, before it is stored. The text of system and tool messages is not kept.
- Reports cite records by opaque evidence ids, never the system's own ids. Public surfaces show pooled results only, and a built-in check refuses to write a public file that names a brand or prints a brand's own interval.
D. Logging and accountability
- An append-only audit log records consent, publication, revocation, sharing, billing and plan changes.
- Every consent records who agreed, when, and the exact scope shown.
- Every program status change, random customer draw and publication is logged in a public changelog with its reason.
- The traction-report view log records every opening of a share link.
E. Integrity of results
- Scores are frozen when made; nobody can change a number during the review window or after.
- Random selections use a secret seed, with a SHA-256 commitment logged so the draw can be checked.
- The judge is validated against human labels before any score publishes.
F. Availability and resilience
- The API runs on Render and the Postgres database on Supabase, both in the EU (Frankfurt). The database is backed up as Attify's database runbook sets out: by hand, before every change that drops or rewrites data and on a regular schedule, until the database moves to a plan with daily automated backups.
- Background work runs on a database job queue that resumes after a restart; a backfill resumes from its cursor.
- Spending caps and rate limits protect the service from abuse.
G. Retention and deletion
H. People
- Attify is run by one person, its operator, who is bound by confidentiality and accesses Customer Personal Data only as far as support and operations need. Anyone given access later is bound by confidentiality and instructed on this DPA before they get it.
- Reviewers see the redacted sample only, never the judge's labels while labeling.
I. Error monitoring
When enabled, errors are reported to Sentry with technical details only, never message text. Not enabled at the time of writing.
Annex III: Subprocessors
Each help-desk platform (Intercom, Zendesk, HubSpot, Salesforce, Gorgias, Freshdesk), each CRM, calendar or booking tool (HubSpot, Salesforce, Google Calendar, Microsoft 365, Calendly, Cal.com), and each agent platform or observability tool the Customer connects (Vapi, Retell AI, ElevenLabs, Bland, Voiceflow, LangSmith, Langfuse), is the Customer's own provider, not Attify's subprocessor: Attify reads from it with the Customer's authorization.
Witnessed data adds no subprocessor: it is stored on the same hosting (Render and Supabase), and only sampled, redacted text of it reaches the judge (Anthropic), as for connected data. The systems a vendor streams from are the vendor's own, not Attify's subprocessors.