Somebody AI
OverviewTermsPrivacyDPASubprocessorsAcceptable UseVoice & Likeness ConsentAssessment AddendumCookies
Legal

Data Processing Addendum

Effective date: 26 September 2026 Last updated: 26 September 2026 Version: 1.0

This Data Processing Addendum (“DPA”) forms part of the Terms of Service or other written agreement (the “Agreement”) between Somebody AI Inc. (“Somebody”) and the customer that has agreed to it (“Customer”). It applies automatically when the Agreement incorporates it; no signature is required. Customers who want a countersigned copy can request one from privacy@somebodyai.co.

Contents
  1. Definitions
  2. Roles and scope
  3. Customer instructions
  4. Somebody’s obligations
  5. Customer’s obligations
  6. Subprocessors
  7. Security
  8. Personal Data Breaches
  9. Data subject requests
  10. Assessments and AI regulation
  11. Audits
  12. Return and deletion
  13. International transfers
  14. US state privacy laws
  15. Biometric and sensitive data
  16. Government requests
  17. Liability, term and precedence
  18. Annex I – Description of processing
  19. Annex II – Security measures
  20. Annex III – Subprocessors

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 Customer Personal Data under the Agreement, including the EU General Data Protection Regulation 2016/679 (“GDPR”), the GDPR as retained in UK law and the UK Data Protection Act 2018 (“UK GDPR”), the Swiss Federal Act on Data Protection (“FADP”), the California Consumer Privacy Act as amended by the CPRA (“CCPA”), and other US state comprehensive privacy and biometric privacy laws.
  • “Customer Personal Data” means personal data within Customer Data that Somebody processes on behalf of Customer under the Agreement.
  • “Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data processed by Somebody or its Subprocessors.
  • “Subprocessor” means any third party (including a Somebody affiliate) engaged by Somebody to process Customer Personal Data.
  • “SCCs” means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914.
  • “UK Addendum” means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018.
  • “controller”, “processor”, “data subject”, “personal data”, “processing”, “business”, “service provider”, “sell” and “share” have the meanings given in the applicable Data Protection Laws.

2. Roles and scope

2.1 Customer is the controller (or business) of Customer Personal Data and Somebody is its processor (or service provider). Where Customer is itself a processor on behalf of a third-party controller, Somebody is Customer’s subprocessor, and Customer warrants that its instructions are authorized by that controller.

2.2 This DPA does not apply to personal data for which Somebody is a controller, such as account administration, billing, security logs and our own sales and marketing data. Our Privacy Policy governs that data.

2.3 BYOK providers. Where Customer configures an Agent to use its own account with a Third-Party Provider, that provider is Customer’s processor, not a Somebody Subprocessor. Somebody’s processing is limited to relaying Customer Personal Data to and from that provider in transit and storing transcripts in Customer’s account. Customer is responsible for its agreement with that provider, including any data processing terms and transfer mechanism, and for configuring that provider’s retention, training, region and safety settings. An incident at that provider is not a Personal Data Breach under this DPA, although Somebody will notify Customer promptly if it becomes aware of one affecting Customer Personal Data. Somebody’s obligations under this DPA continue to apply to its own processing, including the relay of data in transit, the storage of credentials, and transcripts.

2.4 The subject matter, nature, purpose and duration of processing, and the types of personal data and data subjects, are described in Annex I.

3. Customer instructions

3.1 Somebody will process Customer Personal Data only on Customer’s documented instructions, unless otherwise required by law, in which case Somebody will inform Customer of that legal requirement before processing unless the law prohibits it. The Agreement, this DPA, Customer’s configuration of the Services (including Agent settings such as transcript recording, page awareness and recording), and Customer’s use of the dashboard and API are Customer’s complete instructions. Additional instructions require written agreement.

3.2 Somebody will promptly inform Customer if, in its opinion, an instruction infringes Data Protection Laws, and may suspend the affected processing until the instruction is confirmed or modified.

4. Somebody’s obligations

Somebody will:

  • not use Customer Personal Data to train, fine-tune or improve AI models, and not use it for any purpose other than providing, securing and supporting the Services to Customer, preventing abuse, and complying with law;
  • ensure that personnel authorized to process Customer Personal Data are bound by confidentiality obligations, receive appropriate privacy and security training, and access it only as needed to provide the Services, give support Customer has requested, investigate security incidents or abuse, or comply with law;
  • implement the measures in Annex II; and
  • make available to Customer the information reasonably necessary to demonstrate compliance with this DPA.

5. Customer’s obligations

Customer is responsible for: (a) the lawfulness of its instructions and its collection of Customer Personal Data, including a lawful basis for processing; (b) providing all notices and obtaining all consents required from End Users and Depicted Persons, including AI disclosure, notice of voice processing and transcription, recording consent under wiretap and eavesdropping laws, and biometric consent, as described in our Voice, Recording & Likeness Consent Policy; (c) configuring the Services appropriately, including transcript recording, retention, page-awareness and recording settings, and allowed origins; (d) not submitting data prohibited by Section 5.5 of the Terms; and (e) its own security, including User credentials and API keys.

6. Subprocessors

6.1 General authorization. Customer grants Somebody general authorization to engage Subprocessors. The current Subprocessors are listed in our Subprocessor List, which Customer approves.

6.2 Obligations. Somebody will enter into a written agreement with each Subprocessor that imposes data protection obligations no less protective than this DPA, to the extent applicable to the nature of its services, and will remain liable to Customer for each Subprocessor’s performance of those obligations.

6.3 Notice of changes. Somebody will give at least 30 days’ notice before a new Subprocessor begins processing Customer Personal Data, by updating the Subprocessor List and emailing Customer’s account owner and anyone who has subscribed to updates. In an emergency (for example, to maintain the Services or address a security risk), Somebody may replace a Subprocessor on shorter notice and will notify Customer as soon as practicable.

6.4 Objection. Customer may object on reasonable data protection grounds within 15 days of notice. The parties will discuss the objection in good faith. Somebody may offer an alternative, such as not using the new Subprocessor for Customer or allowing Customer to use its own provider under BYOK. If no resolution is reached within 30 days, Customer may terminate the affected Services on written notice and receive a refund of prepaid fees for the unused period.

7. Security

Somebody will implement and maintain appropriate technical and organizational measures to protect Customer Personal Data, taking into account the state of the art, costs of implementation, and the nature, scope, context and purposes of processing and the risks to individuals, including at least the measures in Annex II. Somebody may update those measures provided the update does not materially reduce the overall level of protection.

8. Personal Data Breaches

8.1 Somebody will notify Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach.

8.2 The notice will describe, to the extent known: the nature of the breach, including categories and approximate numbers of data subjects and records concerned; the likely consequences; the measures taken or proposed to address the breach and mitigate its effects; and a contact point. Where information is not available at first, Somebody will provide it in phases as it becomes available.

8.3 Somebody will take reasonable steps to contain, investigate and remediate the breach and will provide reasonable cooperation so that Customer can meet its own notification obligations. Unless required by law, Somebody will not notify regulators or data subjects on Customer’s behalf without Customer’s approval, except to the extent the breach also affects data for which Somebody is controller. Notice of a breach is not an acknowledgement of fault or liability.

9. Data subject requests

9.1 The Services let Customer access, export, correct and delete transcripts and other Customer Personal Data. Taking into account the nature of the processing, Somebody will provide reasonable assistance to Customer to respond to requests from data subjects exercising their rights under Data Protection Laws, to the extent Customer cannot do so itself using the Services.

9.2 If Somebody receives a request directly from a data subject relating to Customer Personal Data, it will forward the request to Customer within 5 business days where it can identify Customer, and will not respond except to direct the data subject to Customer, unless required by law.

10. Assessments and AI regulation

Somebody will provide reasonable assistance, at Customer’s reasonable request and taking into account the information available to Somebody, with Customer’s data protection impact assessments, prior consultations with supervisory authorities, and assessments required of deployers under AI laws (for example, transparency obligations under Article 50 of the EU AI Act). This includes describing how the Services process data and how the player displays AI disclosure.

11. Audits

11.1 Somebody will respond, once in any 12-month period (or more often if required by a supervisory authority or after a Personal Data Breach), to a reasonable written security and privacy questionnaire, and will provide its then-current security documentation, penetration test summaries and any third-party audit reports or certifications it holds.

11.2 If this information is not sufficient to demonstrate compliance with this DPA or the SCCs, Customer (or an independent auditor bound by confidentiality and not a Somebody competitor) may carry out an audit, including an inspection, on at least 30 days’ written notice, during business hours, no more than once every 12 months, and in a way that minimizes disruption and does not compromise other customers’ data or Somebody’s security. Customer bears its own costs. If the audit reveals a material breach of this DPA by Somebody, Somebody will reimburse Customer’s reasonable audit costs and promptly remediate the breach.

12. Return and deletion

12.1 During the subscription and for 30 days after termination, Customer may export Customer Personal Data using the dashboard or API.

12.2 After that export period, Somebody will delete Customer Personal Data from its active systems within 30 days, and from any backups within a further 60 days, unless retention is required by law. Retained data remains subject to this DPA and will be used only for the purpose for which it is retained.

12.3 Custom Avatars, Custom Voices and associated source materials are deleted within 30 days as described in Section 7.4 of the Terms.

12.4 On request, Somebody will certify deletion in writing.

13. International transfers

13.1 Somebody may transfer and process Customer Personal Data in the United States and other countries where it or its Subprocessors operate, subject to this Section.

13.2 EEA. For transfers of Customer Personal Data from the EEA to a country without an adequacy decision, the SCCs are incorporated into this DPA and apply 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 clause) applies; in Clause 9, Option 2 (general written authorization) applies, with the notice period in Section 6.3; the optional language in Clause 11 does not apply; in Clause 13, the competent supervisory authority is determined in accordance with that Clause and Annex I.C; in Clauses 17 and 18, the laws and courts of Ireland apply; and Annexes I, II and III of the SCCs are completed by the corresponding Annexes of this DPA.

13.3 UK. For transfers from the United Kingdom, the SCCs apply as amended by the UK Addendum, which is incorporated into this DPA. Tables 1 to 3 of the UK Addendum are completed with the information in this DPA and its Annexes, and in Table 4 either party may end the UK Addendum as set out in its Section 19.

13.4 Switzerland. For transfers from Switzerland, the SCCs apply with the following changes: references to the GDPR are to the FADP; the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; references to Member State law and courts include Swiss law and courts for claims arising in Switzerland; and “data subject” includes persons whose data is protected under the FADP.

13.5 Supplementary measures. Somebody encrypts Customer Personal Data in transit and will handle government access requests as described in Section 16. On request, Somebody will provide information reasonably needed for Customer’s transfer impact assessment, including a summary of Somebody’s own assessment of the laws of the destination countries.

13.6 Conflict. If there is a conflict between this DPA and the SCCs or UK Addendum, the SCCs or UK Addendum prevail. If a transfer mechanism is invalidated, the parties will cooperate to put in place an alternative lawful mechanism.

14. US state privacy laws

To the extent the CCPA or another US state privacy law applies, Somebody, as a service provider or processor: (a) will not sell or share Customer Personal Data; (b) will not retain, use or disclose it for any purpose other than the business purposes specified in the Agreement, including outside the direct business relationship between the parties; (c) will not combine it with personal information it receives from other sources, except as permitted by law; (d) will comply with applicable obligations and provide the same level of privacy protection required of businesses; (e) will notify Customer if it can no longer meet its obligations; and (f) grants Customer the right to take reasonable and appropriate steps to ensure Somebody’s use is consistent with those obligations and to stop and remediate unauthorized use. Somebody certifies that it understands and will comply with these restrictions.

15. Biometric and sensitive data

15.1 Somebody does not derive biometric identifiers or templates (such as voiceprints or face geometry) from End User conversations, and does not use the Services to identify individuals.

15.2 Where Customer instructs Somebody to create a Custom Avatar or Custom Voice from materials that may contain biometric information or special categories of personal data, Customer will obtain the Depicted Person’s prior written (and, under the GDPR, explicit) consent as described in our Consent Policy, and Somebody will: use such data only to create, operate and verify consent for that Avatar or voice; not sell, lease, trade or otherwise profit from it; and destroy it in accordance with the retention schedule in Section 6 of our Privacy Policy.

15.3 Somebody is not a business associate under HIPAA, and Customer will not submit protected health information unless the parties have signed a business associate agreement.

16. Government requests

If Somebody receives a legally binding request from a public authority for access to Customer Personal Data, it will, unless legally prohibited: notify Customer promptly and provide a copy of the request; review the legality of the request and challenge it where there are reasonable grounds to do so; disclose only the minimum data required; and redirect the authority to request the data from Customer directly where possible. Somebody will maintain a record of such requests and provide aggregate information to Customer on request, where permitted.

17. Liability, term and precedence

17.1 Each party’s liability under this DPA is subject to the limitations and exclusions of liability in the Agreement, except that nothing in this DPA limits either party’s liability to data subjects under the SCCs.

17.2 This DPA remains in effect as long as Somebody processes Customer Personal Data.

17.3 In a conflict, the following order of precedence applies: (a) the SCCs and UK Addendum; (b) this DPA; (c) the Agreement.

17.4 Somebody may update this DPA to reflect changes in law or the Services, with at least 30 days’ notice of material changes. Updates will not reduce the protection of Customer Personal Data during Customer’s current subscription term without Customer’s agreement.

Annex I – Description of processing

A. List of parties

Data exporterCustomer, as identified in the Agreement or account. Contact: the account owner. Role: controller (or processor). Activities: use of the Services under the Agreement.
Data importerSomebody AI Inc., 1401 Pennsylvania Ave, STE 105-2124, Wilmington, Delaware 19806, USA. Contact: privacy@somebodyai.co. Role: processor (or subprocessor). Activities: provision of the Services.

Each party’s acceptance of the Agreement constitutes its signature of these Annexes and the SCCs.

B. Description of transfer and processing

Categories of data subjectsEnd Users who interact with Customer’s Agents (for example website visitors, customers, learners, employees); Customer’s Users; Depicted Persons whose likeness or voice Customer uses; individuals whose information appears in Customer Content.
Categories of personal dataVoice audio streamed during conversations (processed in memory, not stored); conversation transcripts and timestamps; session, agent and pseudonymous visitor identifiers; identity attributes Customer chooses to pass to the player (for example name, email, locale, roles, LMS learner ID); page context and form data an End User asks an Agent to handle; assessment and feedback results; any personal data in Customer Content such as knowledge documents; for Custom Avatars and Custom Voices, images, video, voice recordings and consent records of the Depicted Person.
Sensitive dataNone intended. Custom Avatar and Custom Voice materials may contain biometric data, processed only with explicit consent and subject to Section 15 and Annex II. End Users may volunteer sensitive information in conversations; Customer should configure its Agents to discourage this where appropriate.
FrequencyContinuous, for the duration of the Agreement.
Nature of processingReceiving and relaying audio and text in real time to AI speech and language models; generating speech, text and avatar animation; storing, displaying, searching, exporting and deleting transcripts; summarizing Customer-uploaded documents; hosting Custom Avatar and Custom Voice assets; operational logging and support.
PurposeProviding the Services to Customer under the Agreement.
RetentionAs configured by Customer and its plan; thereafter as described in Section 12. Voice audio from conversations is not retained after processing.
Subprocessor transfersAs listed in Annex III, for the same subject matter, nature and duration as above.

C. Competent supervisory authority

Where Customer is established in the EEA, the supervisory authority of its establishment. Where Customer is not established in the EEA but is subject to the GDPR under Article 3(2), the supervisory authority of the Member State where its EU representative is established or, if none, where the relevant data subjects are located. For the UK, the Information Commissioner’s Office; for Switzerland, the FDPIC.

Annex II – Technical and organizational security measures

Architecture and data minimizationAvatars render client-side in the End User’s browser, and no camera access is requested. Voice audio is relayed in memory and not stored. Transcript recording can be disabled per Agent, and a disabled setting is enforced at ingestion. Page observation is opt-in, excludes password, hidden, file and payment fields and form values, and strips query strings and fragments from URLs.
EncryptionTLS 1.2+ for all data in transit between browsers, Somebody services and Subprocessors. Customer AI provider credentials are encrypted at rest with application-level encryption, never returned in API list responses, and redacted from logs. Data stores are encrypted at rest.
Access controlAuthentication through a dedicated identity provider with support for multi-factor authentication. Organization-based tenant isolation on every data record. Role-based permissions (admin and member roles, scoped API keys). Least-privilege production access limited to named personnel, with MFA required for administrative and infrastructure access. Deletion of transcripts is restricted to administrators and audit-logged.
Player and API securityPublishable player keys restricted to Customer-configured allowed origins and stored only as SHA-256 hashes, with constant-time comparison. Short-lived signed session tokens bound to origin. Rate limiting on public playback and token endpoints. Input size limits on realtime sessions. Sensitive configuration cannot be overridden from host pages.
Logging and monitoringStructured application logs with automatic redaction of authorization headers, cookies and secrets. Conversation content is not written to production logs. Security-relevant administrative actions are audit-logged. Logs are retained for a limited period and access is restricted.
InfrastructureProduction services run as isolated containers built by a CI pipeline using short-lived workload identity (no long-lived deploy keys). Databases are not exposed to the internet and require authentication. Edge protection and TLS termination are provided by a content delivery and DDoS protection network. Secrets are held outside source control.
Availability and resilienceAutomated, encrypted database backups with periodic restore testing. Backups are retained for no more than 90 days.
AI provider controlsSomebody-managed AI providers are used under API or business terms that prohibit training on submitted data. Where a provider offers zero or reduced data retention for Somebody’s use case, Somebody enables it where available.
PersonnelConfidentiality undertakings for all personnel and contractors with access to Customer Personal Data, security and privacy training on onboarding and annually, and prompt revocation of access on role change or departure.
Vendor managementSecurity and privacy due diligence before engaging Subprocessors, and written data protection terms with each.
Incident responseA documented incident response process covering detection, triage, containment, notification (see Section 8) and post-incident review.
Secure developmentCode review for production changes, dependency updates, separation of development and production environments, and no use of production Customer Personal Data in development or testing.
DeletionCustomer-controlled deletion of transcripts and sessions. Deletion of Customer Personal Data on termination as described in Section 12, including data held by Subprocessors.

Annex III – Subprocessors

The Subprocessors authorized by Customer are those listed on our Subprocessor List as in effect from time to time under Section 6.

Somebody AI Inc · 1401 Pennsylvania Ave, STE 105-2124, Wilmington, Delaware, USA 19806 © 2026 Somebody AI Inc · somebodyai.co · Privacy · Terms · Cookie settings

Cookies on somebodyai.co

We use strictly necessary cookies to run this site. With your permission we also use analytics cookies to see how visitors use the site and our app, and a marketing-attribution cookie from our CRM provider to understand which pages lead to sign-ups. We never sell your data. See our Cookie Policy.