How it worksSupportPricingFAQ
Resources
BlogBest Practices
About
Talk to usLogin

This Data Processing Agreement (DPA) forms part of and is incorporated by reference into the Agreement between Bayescase GmbH (Processor) and the Customer identified in the applicable Order (Controller) for use of the Platform.

1. Parties and Roles

  • Controller: The Bayescase customer identified in the Order.
  • Processor: Bayescase GmbH, Julius-Hatry-Straße 1, 68163 Mannheim, Germany.
  • Roles:
    • For Customer Personal Data processed within the Platform on behalf of Controller, Bayescase acts as Processor.
    • For account, billing, communications, marketing and telemetry data for which Bayescase determines the purposes and means, Bayescase acts as an independent Controller (out of scope of this DPA and governed by Bayescase's Privacy Policy).
    • Anonymization under Section 4.6 is performed as processing on Controller's instructions; Controller may withdraw this instruction as set forth there.

2. Definitions

  • Customer Personal Data: any personal data (Art. 4(1) GDPR) provided by or on behalf of Controller to the Platform for processing on Controller's behalf.
  • Platform: Bayescase's hosted software-as-a-service platform described in the Agreement.
  • Sub-processor: any Processor engaged by Bayescase to process Customer Personal Data.
  • EU GDPR, UK GDPR, and Swiss FADP have the meanings given under applicable law. Capitalized terms not defined here have the meanings in the Agreement or GDPR.

3. Subject Matter, Duration, Nature and Purpose

  • Subject matter and duration: Processing of Customer Personal Data as necessary to provide the Platform during the Subscription Term and for 30 days after the subscription ends for export, followed by deletion subject to backups as described below.
  • Nature and purpose: Hosting, storage, retrieval, transmission, analysis, transformation, and other processing necessary to provide, secure, maintain, and support the Platform for Controller, including optional AI features requested by users, generation of AI-assisted outputs, and fraud/abuse prevention.
  • Categories of personal data: Typical B2B SaaS user/account data (e.g., name, business email, role, organization, user IDs), usage and event logs, prompts, uploaded materials, generated outputs, and any personal data contained in Customer's inputs or datasets uploaded to or entered into the Platform. Controller shall not input special categories of personal data (Art. 9 GDPR), biometric data, genetic data, government-issued identifiers, or children's data without a written amendment.
  • Categories of data subjects: Authorized Users, Controller's personnel, contractors, business contacts, and other individuals whose personal data Controller chooses to input into the Platform.
  • Sensitive data: Not intended. Controller will not submit health, biometric, genetic, or other special category data, or children's data, to the Platform or AI features unless expressly agreed in writing.

4. Controller Instructions; Processor Obligations

4.1 Instructions. Bayescase shall process Customer Personal Data only on documented instructions from Controller, including as set out in the Agreement, this DPA, and Controller's configuration of the Platform. If Bayescase is required by EU, Member State, UK, Swiss or other applicable law to process Customer Personal Data beyond Controller's instructions, Bayescase will inform Controller before processing unless the law prohibits such notice.

4.2 Confidentiality. Bayescase ensures that persons authorized to process Customer Personal Data are bound by confidentiality obligations.

4.3 Security. Bayescase implements technical and organizational measures (TOMs) appropriate to the risk, as described in Annex II, including encryption in transit and at rest, access controls, logging, and backups.

4.4 Assistance. Taking into account the nature of the processing, Bayescase assists Controller by appropriate technical and organizational measures insofar as possible for the fulfilment of Controller's obligations to respond to data subject requests under Chapter III GDPR, and to conduct data protection impact assessments and consultations with supervisory authorities (Articles 35-36 GDPR). Bayescase may charge reasonable fees for assistance that goes beyond basic configuration or self-service capabilities of the Platform.

4.5 Personal data breaches. Bayescase will notify Controller without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, and will provide information reasonably required by Controller to comply with Articles 33-34 GDPR as it becomes available. Notification will be sent to the admin email on the account unless Controller designates another address.

4.6 Anonymization for product improvement. Controller instructs Bayescase to anonymize Customer Data and Outputs as defined in the Terms so that Bayescase may use the anonymized data to improve, optimize, and fine-tune its own models, prompts, algorithms, and product features (Section 13 of the Terms). This instruction does not apply where the Order disables this use. Anonymization takes place before any such use; no inference as to Controller or data subjects is possible. Bayescase does not disclose personal or anonymized data to third parties for this purpose; Section 5 (Sub-processors) remains unaffected. Where Bayescase fine-tunes a third-party provider's model, it does so using anonymized data only; the fine-tuned model is available exclusively to Bayescase. Controller may withdraw this instruction at any time by email to Bayescase or by an administrator in the account settings of the Platform. Withdrawal takes effect prospectively, no later than 30 days after receipt; thereafter no further data of Controller will be anonymized or included in training datasets. Processing necessary to provide the Platform remains unaffected.

5. Sub-processing

5.1 Authorization. Controller grants Bayescase a general authorization to engage Sub-processors to process Customer Personal Data. The current list is available at https://bayescase.com/subprocessors and includes processors engaged by Bayescase in its capacity as Processor for Platform data, including providers used to process Customer Personal Data in connection with optional AI features requested by Controller's users. Vendors used by Bayescase in its own capacity as Controller (e.g., for billing or CRM) are not Sub-processors under this DPA.

5.2 Requirements. Bayescase shall:

  • impose on Sub-processors data protection obligations no less protective than those in this DPA (including TOMs and, where applicable, SCCs), and
  • remain responsible for Sub-processors' performance.

5.3 Changes. Bayescase will provide at least 30 days' prior notice of additions/replacements via the Sub-processor page or email. Controller may object on reasonable data protection grounds within that period. If the parties cannot resolve an objection in good faith, Controller may terminate the affected subscription and receive a pro rata refund for prepaid, unused fees.

6. International Transfers

6.1 Locations. Bayescase primarily hosts and processes Customer Personal Data in the EU/EEA (AWS eu-central-1, Frankfurt). Certain AI-related processing of prompts, context, uploaded materials, and outputs may be carried out by Bayescase's AI provider outside the EU/EEA, including in the United States, where necessary to provide the AI features requested by Controller or its Authorized Users.

6.2 Safeguards. Where Customer Personal Data is transferred to a third country without an adequacy decision:

  • For EU GDPR: Bayescase is established in the EU, so making Customer Personal Data available to Bayescase is not a transfer to a third country. Where a Sub-processor, or a company it engages, transfers Customer Personal Data to a third country without an adequacy decision, Bayescase ensures that the transfer is covered by the EU Standard Contractual Clauses (SCCs) adopted by Commission Decision 2021/914, in particular Module 3 (Processor-to-Processor), or by another appropriate safeguard under Art. 46 GDPR. Annex I describes these transfers and Annex II the technical and organizational measures. In case of conflict, the SCCs prevail for the relevant transfer.
  • For UK GDPR: The UK International Data Transfer Addendum (UK Addendum) to the EU SCCs (version issued by the UK ICO and in force on the Effective Date) is incorporated and applies to relevant transfers; the EU SCCs as amended by the UK Addendum form the relevant transfer mechanism.
  • For Switzerland: The Swiss FDPIC's provisions apply. The EU SCCs are adapted so references to GDPR are read as references to Swiss law, and supervisory authority references include the FDPIC.

6.3 Supplementary measures. Bayescase will implement appropriate supplementary measures (e.g., encryption in transit and at rest, access controls, data minimization), assess laws/practices of the destination country where reasonably possible, and document a transfer impact assessment (TIA) upon request. Bayescase will notify Controller if it can no longer comply with the SCCs and, if feasible, will suspend the relevant transfer or propose a reasonable alternative.

7. Audits and Information Rights

  • Upon reasonable written request (not more than once in any 12-month period unless required by a competent authority or following a confirmed personal data breach), Bayescase will make available information necessary to demonstrate compliance with Article 28 GDPR, which may include: security whitepapers, policy summaries, responses to security questionnaires, and descriptions of TOMs.
  • If this information is not sufficient, Controller may have an on-site audit performed at most once every 12 months, with 30 days' notice, by an auditor bound to confidentiality who is not a competitor of Bayescase. Any audit will be conducted during normal business hours, in a manner that minimizes disruption, subject to confidentiality obligations, and at Controller's expense.

8. Data Retention, Return, and Deletion

During the Subscription Term and for 30 days after the subscription ends, Controller may export Customer Personal Data via the Platform or upon request. After that period, Bayescase will delete Customer Personal Data from active systems and processing schedules, subject to legal retention obligations and standard encrypted rolling backups with a maximum retention of 35 days. Data contained in backups will be overwritten in the ordinary course of backup rotation and is not restored except for disaster recovery.

9. Liability; Order of Precedence

  • The parties' respective liability under or in connection with this DPA is governed by the limitation of liability in the Agreement. Nothing in this DPA limits either party's liability where such limitation is not permitted by law, or under the SCCs for the relevant restricted transfers.
  • In the event of a conflict between this DPA and the Agreement, this DPA controls with respect to processing of Customer Personal Data. In the event of a conflict with the SCCs for a restricted transfer, the SCCs prevail for that transfer.

10. Miscellaneous

  • Personnel; access. Bayescase ensures that access to Customer Personal Data is limited to personnel who require it for the purposes of the Platform, and that such access is revoked when no longer needed.
  • Records. Bayescase will maintain records of processing activities as required by Article 30(2) GDPR and make them available to supervisory authorities upon request.
  • Government access requests. Where legally permissible, Bayescase will notify Controller of government or other third-party requests for Customer Personal Data and will challenge unlawful requests. Bayescase will disclose only the minimum required to comply with the law.
  • Term. This DPA remains in force for so long as Bayescase processes Customer Personal Data on behalf of Controller under the Agreement.
  • AI subprocessors and instructions. Where Controller uses optional AI features, Controller instructs Bayescase to make Customer Personal Data contained in prompts, context, uploaded materials, and outputs available to Bayescase's authorized AI subprocessor solely as necessary to generate the requested response and provide the Platform.

Annex I - Description of Processing and Transfers

This Annex describes the processing of Customer Personal Data and the transfers to third countries referred to in Sections 3 and 6.

A. Parties and roles

  • Controller: the Customer named in the Order. Contact details and contact person are as stated in the Order.
  • Processor: Bayescase GmbH, Julius-Hatry-Straße 1, 68163 Mannheim, Germany, privacy@bayescase.com. Bayescase is established in the EU.
  • Sub-processors: as listed at https://bayescase.com/subprocessors.
  • AI Sub-processor and transfer to a third country: Bayescase uses the OpenAI API under a contract with OpenAI OpCo, LLC (USA). Under OpenAI's data processing addendum, data from the EEA is processed by OpenAI Ireland Ltd. (Dublin, Ireland), which transfers it to OpenAI OpCo, LLC and other affiliates outside the EEA on the basis of agreements containing the EU SCCs, or of an adequacy decision of the European Commission. For this transfer, OpenAI Ireland Ltd. is the data exporter and OpenAI OpCo, LLC is the data importer.

B. Description of the processing and transfer

  • Categories of data subjects: Authorized Users, Controller's personnel, contractors, business contacts, contact persons the Controller names to provide actual values (who may be outside the Controller's user base), and other individuals whose personal data Controller chooses to input into the Platform (e.g., stakeholders named in a business case).
  • Categories of personal data: user and account data (name, business email, role, organization, user IDs, language, MFA status, last use, acceptance of the terms); collaborator lists; usage and event logs; business case content, attached documents, AI chat transcripts and the company knowledge base; prompts, voice recordings and generated outputs; names and email addresses of contact persons for actual values, the values they enter and their opt-out records; and any personal data contained in Customer's inputs. Sent to OpenAI: the user's prompt with the relevant business case context and document excerpts, the full text of attached documents (for embeddings), voice recordings (for speech-to-text), search queries the model writes for web search, and generated outputs.
  • Sensitive data: None intended. Under Section 3, Controller does not submit special categories of personal data (Art. 9 GDPR), biometric or genetic data, government-issued identifiers or children's data unless expressly agreed in writing. The measures in Annex II apply.
  • Frequency of the transfer: Continuous, whenever users use AI features.
  • Nature and purpose of the processing: Provision of the Platform as described in Section 3. At OpenAI: AI inference, embeddings of attached documents, speech-to-text for voice input, and web search for AI features.
  • Duration of the processing: The Subscription Term, as described in Section 3.
  • Retention at OpenAI: OpenAI keeps data for up to 30 days for abuse monitoring. Response storage is disabled.
  • Retention at Bayescase: As set out in Section 8.

C. Competent supervisory authority

  • For Bayescase as Processor: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg.
  • For the Customer as Controller: the supervisory authority competent for the Customer.
  • For the transfer to the USA: the supervisory authority competent for the data exporter, OpenAI Ireland Ltd. (Clause 13 of the SCCs).

Annex II - Technical and Organizational Measures

Bayescase GmbH implements the following measures under Art. 32 GDPR. They are proportionate to the risk of processing Customer Personal Data in the Platform, reviewed at least once a year, and updated when the Platform changes. The Information Security Policy (aligned with ISO/IEC 27001:2022 Annex A and NIST CSF 2.0) governs them.

1. Confidentiality

Physical access control

  • The Platform runs only on Amazon Web Services in the EU (eu-central-1, Frankfurt), in data centers certified to ISO 27001 and SOC 2. Bayescase operates no data centers, servers or file shares of its own.
  • Work devices are full-disk encrypted, lock automatically after at most 10 minutes and receive automatic security updates.

System access control

  • Users sign in with Amazon Cognito (SRP, no passwords sent to Bayescase). There is no self-registration; the Customer's administrator invites users.
  • TOTP multi-factor authentication. Customers can make it mandatory for their organization, and the server enforces it on every request.
  • Access to the cloud environment only through single sign-on with MFA and short-lived credentials. Personnel have no long-lived access keys. Root accounts have MFA and no access keys.
  • The internal admin portal uses its own user pool with mandatory MFA. Only named administrators have accounts.
  • Deployments go through CI/CD with federated, keyless roles. Manual changes to production resources are not allowed.

Data access control

  • Role-based access at company level (admin, member), portfolio level (portfolio manager) and case level (owner, editor, viewer), enforced on the server.
  • One central authorization layer that every API route must use. It fails closed. The tenant comes from the authenticated token, never from the request.
  • Disabled users lose access with their next request, even if their token hasn't expired.
  • Each server function gets permissions only for the resources it needs.
  • Production access is limited to named personnel. Access is reviewed every quarter and removed within 24 hours when someone leaves or changes role.

Separation control

  • Logical separation of customer data by tenant identifier on every record, checked on every request.
  • Development, staging and production run in separate AWS accounts. Production data is not used in non-production environments, except with the Customer's written consent, and every such copy is logged.
  • Internal AI quality signals are skipped for customers who opt out.

2. Pseudonymization and encryption

  • Encryption in transit: TLS 1.2 or higher with HSTS for all external traffic; no unencrypted endpoints.
  • Encryption at rest for databases, object storage, logs and backups, with AWS-managed keys. Backups use a dedicated key with automatic rotation.
  • Credentials for customer data sources are stored only in an encrypted parameter store, never in the database or the code.
  • Website analytics use a pseudonymous hashed identifier instead of IP addresses.

3. Integrity

Transfer control

  • All data moves over HTTPS. Uploads use short-lived pre-signed links for one object. No email or portable media are used for customer data.
  • Calls from the Platform to customer endpoints are HTTPS-only and protected against server-side request forgery.
  • Transfers to the AI Sub-processor are limited to what the requested feature needs. Response storage and tracing are turned off in production.

Input control

  • A structured audit log records authentication events, authorization denials, cross-tenant access attempts, administrative actions, deletions and exports, with tenant, user and time.
  • AWS CloudTrail records all administrative activity in all accounts, with log file validation. Changes to CloudTrail raise an alert.
  • Business cases keep a version history of every publish.
  • Every API input is validated against a schema; output of AI features is validated before it changes a model, and users accept or reject proposed changes.

4. Availability and resilience

  • Serverless AWS services spread across several availability zones in one region; throttling on every API route.
  • Point-in-time recovery for all production databases (35 days); versioning on the storage that holds customer content (35 days).
  • Daily backups copied into a separate AWS account, into a locked, immutable vault (35 days) that production identities can't change or delete.
  • Deletion protection on production databases and the user directory.
  • AWS GuardDuty threat detection in all accounts; alarms on errors, throttling, CloudTrail tampering and cost anomalies.

5. Rapid restoration

  • The whole environment can be rebuilt from version control into a clean account.
  • Recovery targets: RTO 24 hours; RPO ≤ 5 minutes with point-in-time recovery, ≤ 24 hours from the isolated vault.
  • A disaster recovery test at least once a year, with a written report.

6. Regular testing, assessment and evaluation

  • Every change passes required checks before it reaches production: type checks, automated tests, linting, a dependency vulnerability audit and static application security testing (SAST). Every change is reviewed by a person and by an AI review tool.
  • Weekly dynamic application security testing (DAST) against staging.
  • In-depth internal security reviews every quarter and before major releases, each with a findings report and a remediation log.
  • Fix deadlines: critical 7 days, high 30 days, medium 90 days.
  • Published vulnerability disclosure policy (security.txt, security@bayescase.com).

7. Organization

  • A named owner for information security and data protection (the managing director), with a deputy who holds sealed break-glass credentials.
  • Confidentiality agreements and security awareness training before access, repeated every year.
  • Incident response procedure: customers are notified within 24 hours of a confirmed incident affecting their data; for personal data breaches without undue delay, in time for Art. 33 GDPR.
  • Sub-processors are bound by data processing agreements with SCCs where needed, reviewed every year, and listed publicly with 30 days' notice of changes.
  • Data minimization: no special categories of data, no payment card data. Voice recordings are deleted after transcription. Data is deleted after defined retention periods; for Customer Personal Data, Section 8 applies.