Legal
Data processing addendum
Effective and last updated October 31, 2026.
This Data Processing Addendum ("DPA") attaches to the Bayesin Terms of Service (the "Agreement"). Capitalized terms not defined here have the meanings given in the Agreement.
1. Scope, roles, and incorporation
1.1. This DPA forms part of the Agreement between Bayesin, Inc ("Bayesin") and the customer identified in the Agreement ("Customer") and governs Bayesin's processing of Personal Data contained in Customer Data in connection with the Service.
1.2. Roles. Customer is the controller of Personal Data (or a processor acting on behalf of another controller, in which case Customer warrants it is authorized to instruct Bayesin on that controller's behalf), and Bayesin is Customer's processor. Bayesin processes Personal Data only on Customer's documented instructions, including those given by configuring and using the Service. Bayesin is an independent controller of account and usage data about Customer's users, as described in its Privacy Policy; this DPA does not apply to that data.
1.3. Subject matter, duration, nature, purpose, categories, and data subjects are described in Annex I. Bayesin's security measures are described in Annex II. Authorized sub-processors are listed in Annex III.
1.4. If this DPA conflicts with the Agreement, this DPA prevails for the processing of Personal Data. If this DPA conflicts with the Standard Contractual Clauses or the UK Addendum (Section 6), those clauses prevail.
2. Definitions
"Personal Data" means any information relating to an identified or identifiable natural person that Bayesin processes on Customer's behalf under 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 (2016/679) ("GDPR"); the GDPR as retained in UK law ("UK GDPR") and the UK Data Protection Act 2018; the Swiss Federal Act on Data Protection; and US state privacy laws including the California Consumer Privacy Act as amended by the CPRA ("CCPA").
"Standard Contractual Clauses" or "SCCs" means the European Commission's standard contractual clauses for the transfer of personal data to third countries (Commission Implementing Decision (EU) 2021/914), using Module 2 (controller-to-processor) where Customer is a controller and Module 3 (processor-to-processor) where Customer is a processor.
"UK Addendum" means the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner (version B1.0, or any later version it issues).
"Sub-processor" means a third party engaged by Bayesin to process Personal Data in connection with the Service.
Other terms — "personal data breach", "data subject", "processing", "supervisory authority" — have the meanings given in the GDPR.
3. Bayesin's processing obligations
3.1. Instructions. Bayesin processes Personal Data only on Customer's documented instructions and only to provide, maintain, and secure the Service (including investigating suspected security or acceptable-use violations), unless required by applicable law — in which case Bayesin will inform Customer of that requirement before processing, unless prohibited from doing so. Bayesin will promptly inform Customer if, in its opinion, an instruction infringes Data Protection Laws.
3.2. Confidentiality. Bayesin ensures that persons authorized to process Personal Data are bound by confidentiality obligations and receive appropriate data-protection training.
3.3. Security. Bayesin implements and maintains the technical and organizational measures in Annex II, appropriate to the risk, taking into account the state of the art, costs of implementation, and the nature, scope, context, and purposes of processing.
3.4. No sale, no secondary use. Bayesin does not sell Personal Data, does not share it for cross-context behavioral advertising, does not retain, use, or disclose it for any purpose other than performing the Service for Customer, and does not combine it with personal data received from other sources, except as permitted by Data Protection Laws for service providers/processors.
3.5. Data subject requests. Taking into account the nature of the processing, Bayesin will reasonably assist Customer, at Customer's cost for material assistance, in responding to data-subject requests to exercise rights under Data Protection Laws (access, rectification, erasure, restriction, portability, objection). Where the Service provides self-service controls (e.g., suppression and erasure per subject), Bayesin may direct Customer to those controls first. An erasure made through those controls removes the subject's data from live systems within one hour and from backups within seven days. If Bayesin receives a data-subject request directly, it will redirect the requester to Customer and, where lawful, notify Customer.
3.6. Compliance assistance. Bayesin will reasonably assist Customer with data protection impact assessments and prior consultations with supervisory authorities where required under Articles 35–36 GDPR, taking into account the nature of the processing and the information available to Bayesin.
3.7. Deletion and return. Bayesin will delete Personal Data on the schedule in Section 7.6 of the Agreement: seven days after a self-serve subscription ends or Customer requests deletion, during which it remains available for export, with deleted data leaving backups within 15 days of that date. Applicable law may require longer retention. On request, Bayesin will certify deletion in writing.
4. Personal data breaches
4.1. Bayesin will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a personal data breach affecting Personal Data processed under this DPA.
4.2. The notification will describe, to the extent then known: the nature of the breach; the categories and approximate number of data subjects and records concerned; likely consequences; and measures taken or proposed to address and mitigate it. Bayesin may provide information in phases as it becomes available and will reasonably cooperate with Customer's investigation and any notification obligations.
4.3. Notifications under this Section will be sent to the security or privacy contact Customer designates in the Service, or otherwise to the account owner.
5. Sub-processors
5.1. Authorization. Customer authorizes Bayesin to engage the Sub-processors listed in Annex III. The current list is also available at https://bayesin.com/trust or on request at privacy@bayesin.com.
5.2. Changes. Bayesin will give at least 30 days' notice by email before engaging a new or replacement Sub-processor. Customer may object on reasonable data-protection grounds within that notice period; the parties will work in good faith to resolve the objection. If unresolved within 30 days, Customer may terminate the affected subscription with a pro-rata refund of prepaid unused fees.
5.3. Flow-down and liability. Bayesin imposes data-protection obligations on each Sub-processor no less protective than this DPA and remains liable for each Sub-processor's performance to the same extent as for its own.
6. International transfers
6.1. EU/EEA and Switzerland. Where Bayesin processes Personal Data subject to the GDPR in a country the European Commission has not found adequate, the SCCs (Module 2 or Module 3, as applicable) are incorporated and apply as follows: (a) Customer is the data exporter and Bayesin the data importer; (b) Clause 7 (docking) applies; (c) Clause 9, option 2 (general authorization with advance notice) applies, with the notice period in Section 5.2; (d) Clause 11 (optional redress) does not apply; (e) for Clause 17, the governing law is that of Ireland; (f) for Clause 18, the courts are those of the same Member State; (g) Annexes I, II, and III to this DPA serve as Annexes I, II, and III to the SCCs.
6.2. United Kingdom. For transfers subject to the UK GDPR, the UK Addendum is incorporated and applies, with this DPA's Annexes completing its tables.
6.3. Switzerland. For transfers subject to Swiss law, the SCCs apply with modifications required by the Swiss Federal Data Protection and Information Commissioner.
6.4. Supplementary measures. Where required by Data Protection Laws (including following Schrems II), Bayesin will maintain supplementary measures — including encryption in transit and at rest and access controls as described in Annex II — and will, to the extent lawful, notify Customer of any government access request and challenge it where reasonable.
7. Audits and information
7.1. Bayesin will make available information reasonably necessary to demonstrate compliance with this DPA, including responses to reasonable written questionnaires and copies of applicable third-party certifications or audit reports.
7.2. Where the information under Section 7.1 is insufficient, Customer may, no more than once per 12 months and on at least 30 days' notice, conduct or commission an independent audit of Bayesin's relevant controls, at Customer's expense, during business hours, subject to confidentiality and without unreasonably disrupting operations. Findings are Bayesin's Confidential Information.
7.3. Nothing in this Section limits any audit or inspection right granted by the SCCs to a supervisory authority.
8. US state privacy laws
8.1. With respect to Personal Data subject to the CCPA, Bayesin acts as a service provider/contractor. Bayesin will not: (a) sell or share Personal Data; (b) retain, use, or disclose Personal Data for any purpose other than the business purposes specified in the Agreement and this DPA, or as otherwise permitted by the CCPA; or (c) combine Personal Data with personal data received from other persons or collected from Bayesin's own interactions, except as permitted by CCPA regulations.
8.2. Bayesin certifies that it understands and will comply with the restrictions in Section 8.1, and will notify Customer no later than five business days after it determines it can no longer meet its obligations under applicable US state privacy laws.
8.3. Each party will comply with its obligations under other applicable US state comprehensive privacy laws (e.g., Virginia, Colorado, Connecticut, Utah, and successors), with Bayesin acting as "processor" where those laws define one.
8.4. The specific business purposes for which Bayesin processes Personal Data are fitting and reporting Customer's attribution, media mix, forecasting, and budget-allocation models, and operating, debugging, and securing the Service for Customer.
8.5. Customer may take reasonable and appropriate steps to ensure that Bayesin uses Personal Data consistently with Customer's obligations under the CCPA and, on notice, to stop and remediate unauthorized use of Personal Data.
9. Liability and term
9.1. Liability under this DPA is subject to the limitations and exclusions in Section 15 of the Agreement, except to the extent those limits cannot apply under mandatory Data Protection Laws or the SCCs.
9.2. This DPA takes effect on the effective date of the Agreement (or the date above, if later) and continues for the duration of Bayesin's processing of Personal Data, plus the deletion period in Section 3.7.
9.3. This DPA is governed by the governing law of the Agreement (Delaware), except where the SCCs or UK Addendum specify otherwise.
Annex I — Processing details
- Subject matter: Provision of the Bayesin attribution, media mix modeling, forecasting, and budget-allocation Service
- Duration: Term of the Agreement plus the deletion period in Section 3.7
- Nature of processing: Collection (via Customer-configured connections and uploads), storage, organization, analysis (statistical/Bayesian modeling), retrieval, and deletion of Customer Data
- Purpose: Fitting and reporting marketing attribution and revenue models for Customer; operating, maintaining, and securing the Service
- Categories of data subjects: Customer's customers, leads, and website/app visitors whose interactions appear in Customer Data
- Categories of personal data: Identifiers and pseudonymous IDs (e.g., email, name, phone, browser, cookie and device IDs, CRM IDs); approximate location derived from IP address; interaction/touchpoint events (ad clicks, page views, conversions, and on-page events including truncated copied text); transaction/revenue data associated with such events
- Special categories: Not intended to be processed. Customer will not submit special categories of personal data (Art. 9 GDPR) or sensitive personal information (CCPA) without Bayesin's prior written agreement
- Frequency: Continuous during the subscription term (models refresh nightly and refit weekly, per documentation)
- Retention: Per Customer-configured retention windows and Section 3.7
Competent supervisory authority: determined in accordance with the GDPR/UK GDPR (for SCCs Clause 13: the authority of the Member State where Customer is established, or otherwise as specified in Clause 13).
Annex II — Technical and organizational measures
- Access control: role-based access to production systems on least-privilege; unique credentials; multi-factor authentication for administrative access; prompt deprovisioning on role change or offboarding.
- Encryption: TLS 1.2+ for data in transit; AES-256 encryption at rest for databases and backups.
- Tenant isolation: logical separation of each organization's Customer Data; authorization checks on every data access within the Service.
- Credentials and secrets: third-party API tokens and connection credentials stored encrypted in a secrets-management system; no plaintext storage.
- Logging and monitoring: access and audit logging of administrative actions and data exports; alerting on anomalous activity.
- Vulnerability management: dependency and vulnerability scanning; security patches applied per severity-based timelines; periodic penetration testing.
- Development practices: code review prior to production deployment; separation of development/test and production environments; no Customer Data in development or test environments.
- Backup and availability: encrypted backups with documented restore procedures, retained for seven days.
- Personnel: confidentiality obligations for all personnel with data access; security and privacy awareness training on hire and annually.
- Incident response: documented incident response plan, including the breach-notification procedure in Section 4.
- Vendor management: security review of Sub-processors before engagement and periodically thereafter.
Annex III — Sub-processors
- Amazon Web Services: Infrastructure, event storage, and the data sync engine. United States (us-east-1).
- Google Cloud: Model fitting (Cloud Run). United States (us-central1).
- Supabase: Account sign-in and application database. United States.
- Vercel: Application hosting. United States.
- Resend: Transactional email. United States.
- Sentry: Error and performance monitoring. United States.
- PostHog: Product analytics in the application. United States.
- Anthropic: AI explanations of aggregate results, only if Customer's organization turns them on. United States.
- GTmetrix: Page performance tests that Customer's users start. Canada.