Skip to content

Legal & trust

Data Processing Agreement

This Data Processing Agreement describes how Coby protects personal data processed for its business customers. The annexes set out the standard processing and security arrangements. The customer Order and deployment schedule select the applicable services and complete the project details before processing begins.

Last updated

Standard agreement

1 Parties and scope

This DPA forms part of the service agreement between COBY, a French société par actions simplifiée registered with the Nanterre Trade and Companies Register under number 107 178 071, with registered office at 14 allée de Saint-Cucufa, RDC G, bâtiment A1, 92420 Vaucresson, France (Coby), and the customer identified in the accepted order (Customer). The service agreement, including the Order and incorporated Terms of Service, is the Agreement.

Applicable Data Protection Law means the EU GDPR and applicable implementing law, and the UK GDPR and UK Data Protection Act 2018, as amended, to the extent applicable. Controller, processor, personal data, processing and personal data breach have the meanings given in that law.

Customer Personal Data means personal data that Coby processes on Customer's behalf, including identifiable source material, extracts, prompts, outputs, embeddings and customer-specific model artefacts. Customer Data has the meaning in the Terms. Customer is the controller and Coby the processor, unless the deployment schedule identifies Customer as a processor and Coby as its subprocessor. In that case, Customer confirms that it has the necessary upstream instructions and authorisation.

This DPA is accepted through an Order incorporating it or by separate written agreement. The Order identifies the parties, authorised contacts and service term. Coby's separate controller activities, including business relationship management, billing, service security and technical performance monitoring for its own purposes, and optional analytics for its own website or service evaluation, are described in its Privacy Notice. This DPA authorises only processing on Customer's behalf; it grants no right to reuse Customer Personal Data for Coby's own analytics or other purposes.

2 Instructions and permitted use

Coby will process Customer Personal Data only on documented instructions in the Agreement, the completed schedules and subsequent lawful instructions from Customer's authorised contacts. Instructions cover international transfers. Where applicable law requires other processing, Coby will inform Customer beforehand unless prohibited by that law. Coby will promptly inform Customer if it considers an instruction unlawful and may suspend the affected processing while the parties resolve it.

Coby may train, fine-tune or evaluate models dedicated to Customer where included in the agreed service and instructions. The deployment schedule identifies the purpose, data categories, providers, locations and retention for these operations. Separate approval is not required for each run within that scope. Supplementary research or demographic datasets selected by Coby must be lawfully usable and non-personal.

Customer data, derived content and models adapted using it are reserved for Customer's service. Coby and its providers will not sell that data, use it for advertising, use it for other customers, or use it to train or improve shared or general-purpose models, including after anonymisation. Any defined additional use requires Customer's express prior authorisation in the Order or another written agreement specifying the data, purpose and safeguards, subject to applicable law. The Terms' permission to use aggregated, anonymous technical statistics does not authorise reuse of Customer Data or anonymisation of Customer Personal Data for Coby's own purposes. Provider retention must be identified in the deployment schedule and consistent with the agreed purposes and protections.

Customer is responsible for lawful purposes, source permissions, required notices and instructions. Coby remains responsible for its own obligations. Special-category personal data, criminal-offence data and children's data are excluded unless expressly agreed with appropriate safeguards. If unexpected sensitive material is identified, Coby will restrict access and consult Customer on isolation, deletion or a lawful revised scope.

3 Personnel and security

Coby will restrict access to authorised personnel who need it for the service, ensure suitable confidentiality obligations and provide appropriate data protection and security instruction. Access will be reviewed and removed when no longer needed.

Coby will implement the measures in Annex II and any agreed deployment supplement, taking account of the processing risks, state of the art and implementation cost. Measures must be operational before the relevant processing begins and address confidentiality, integrity, availability, resilience, restoration and regular assessment as appropriate. Coby may improve them without materially reducing the agreed level of protection.

For a deployment in Customer's environment, the schedule allocates operating, access, backup and security responsibilities and identifies external data flows.

4 Subprocessors

Customer gives general written authorisation for the subprocessors and operations identified in the register incorporated into its deployment schedule. Annex III describes the standard configuration; only the services selected for the deployment are authorised. Coby will assess relevant safeguards, impose materially equivalent data protection obligations in writing and remain responsible to Customer for its subprocessors' performance of those obligations.

Coby will give at least 15 calendar days' advance notice by email to Customer's designated contractual contact of a proposed addition or replacement, identifying the provider, function, data, locations and safeguards. Customer may agree in writing to a shorter notice period. Customer may object within the applicable notice period on reasonable data protection or security grounds. The parties will work in good faith to resolve a timely objection, including by considering reasonable alternatives. If they cannot resolve it within 30 calendar days after Coby receives the objection, either party may terminate only the affected service by written notice. Customer will receive a refund of prepaid fees for the unused portion of that service. The parties may agree a longer resolution period in writing.

A new subprocessor will not receive Customer Personal Data before the notice period expires and any timely objection is resolved or the affected processing ends. An emergency change requires prompt notice and an expedited documented agreement.

Coby will maintain an accurate register and provide relevant contractual evidence on reasonable request, subject to proportionate redaction of unrelated confidential information.

5 Locations and international transfers

The deployment schedule records storage, processing and relevant remote-access locations. Coby will not initiate a restricted transfer without the applicable authorisation and lawful safeguards.

Where required, the appropriate EU Standard Contractual Clauses and UK Addendum or International Data Transfer Agreement will be completed and made binding before the transfer, together with any necessary transfer assessment and supplementary measures. An applicable adequacy decision may instead provide the transfer basis. Each onward transfer must be covered by a valid transfer mechanism.

Coby will notify Customer of a material change affecting a transfer safeguard and cooperate on a lawful solution, including suspension and return or deletion where necessary. Government access requests will be assessed, challenged where appropriate and disclosed to Customer where lawful, with disclosure limited to what is legally required.

6 Individual rights and assistance

Coby will forward requests or complaints concerning Customer Personal Data to Customer without undue delay and assist with their handling, taking account of the processing and information available. Coby will not respond substantively on Customer's behalf except on instructions or where law requires.

Assistance includes locating, exporting, correcting, restricting or deleting relevant source and derived data. Before personal data is used for training, the parties will establish an effective procedure for requests affecting both the training data and any adapted model containing personal data. The procedure includes retiring or replacing affected model artefacts where necessary to give effect to applicable rights.

Coby will reasonably assist Customer with security obligations, breach assessments, data protection impact assessments and prior consultation with a supervisory authority. Standard compliance documentation and routine responses are included. Customer-specific or substantial assistance beyond routine responses may be charged only at reasonable rates and a scope agreed in advance. Charges must not delay urgent statutory compliance or make statutory assistance rights ineffective. Assistance caused by Coby's breach is not additionally chargeable.

7 Incidents and notifications

Coby will notify Customer without undue delay and in any event within 48 hours after becoming aware of a personal data breach affecting Customer Personal Data. Coby will also notify Customer without undue delay of a material security incident compromising the confidentiality, integrity or availability of Customer Data. Routine unsuccessful attacks without such compromise do not automatically require individual notification.

Notice will provide available information about the incident, affected data and people, likely consequences, containment and remediation, and a response contact. Further information will follow without undue further delay; Coby will not wait for a completed investigation before giving the initial notice.

Coby will investigate, contain and remediate the incident, preserve relevant evidence, cooperate with Customer and provide updates and findings as they become available. Customer remains responsible for its own notifications to authorities and individuals. Notification does not itself admit liability.

Coby's incident contact is founders@joincoby.com; Customer designates its contact in the Order. Ordinary support hours do not extend these notification duties.

8 Information and audit

Coby will make available information necessary to demonstrate compliance with this DPA and allow and contribute to audits, including inspections, by Customer or a suitable independent auditor mandated by it. Documentary evidence may be reviewed first where it reasonably addresses the issue.

Routine audits normally take place during business hours, on at least 15 business days' notice and no more than once a year, with reasonable confidentiality and protection for other customers. These limits do not restrict supervisory authorities, legally required audits, material incidents, credible compliance concerns or necessary follow-up.

Coby will remedy substantiated non-compliance and provide a proportionate action plan. Customer bears its own costs and its auditor's fees for routine audits. Coby provides standard compliance documentation and routine responses without additional charge; customer-specific or substantial assistance beyond routine responses may be charged only at reasonable rates and a scope agreed in advance. These arrangements must not delay urgent compliance or make statutory audit rights ineffective. Coby bears its own remediation costs and reimburses reasonable, documented external audit costs directly necessary to verify an established material breach by Coby.

9 Return and deletion

At the end of the service, Customer may choose return and/or deletion of Customer Personal Data, unless law requires retention. On request, Coby will return the data before deletion in the usable electronic format agreed for the deployment. Return of data does not itself transfer rights in Coby's platform or require delivery of model weights unless agreed in the Order; mandatory rights remain unaffected.

Coby will delete active Customer Personal Data and customer-adapted model artefacts within 30 days after service termination or an applicable deletion instruction, subject to any earlier legal requirement. Backup copies are retained for no more than 90 days from creation and deleted no later than 90 days after active deletion. The maximum total period from termination or the applicable instruction is 120 days.

Where applicable switching law requires a transition or data-retrieval period, the relevant data remains available for that period, including at least 30 calendar days after the transition period ends where the EU Data Act applies. These requirements take precedence over contractual access termination, the standard active-deletion deadline and the overall 120-day limit. Once switching has been successfully completed and the required retrieval period has expired, Coby will erase the retained data without undue delay. The data remains protected under this DPA and is used only for the agreed exit arrangements or as required by law. The backup retention limits above continue to apply.

These limits cover source copies, extracts, embeddings, indexes, graph data, prompts, outputs, caches, training datasets, adapted weights, adapters and checkpoints, including manual backups and approved providers' copies. These deletion limits also cover any Customer Personal Data present in logs, including inadvertent content; this does not authorise content logging. The restrictions on customer-adapted model artefacts also apply under the Terms regardless of ownership.

Backups awaiting expiry remain protected and excluded from ordinary use. Any necessary restoration must reapply deletion and access restrictions before normal use. Where law requires continued retention, Coby will identify the relevant requirement where lawful, restrict use to that purpose and delete the data when retention is no longer required.

On request, Coby will confirm completion of return or deletion and identify the expiry date of any remaining protected backups; any mandatory certification requirement remains unaffected. Credentials will be removed or revoked when the corresponding authorisation ends. Any lawful variation to these deadlines requires express written agreement before the affected processing.

10 Duration and contractual terms

This DPA continues for as long as Coby holds Customer Personal Data. The Agreement's liability provisions apply between the parties, including its aggregate cap, subject to mandatory law and mandatory transfer clauses. They do not restrict individuals' statutory rights or the powers of supervisory authorities.

This DPA prevails over conflicting general terms on personal data processing. Mandatory transfer instruments prevail within their scope. Governing law and jurisdiction follow the Agreement except where mandatory transfer clauses require otherwise. Amendments require written agreement.

Annex I Processing details

The following is the standard service description. Before processing begins, the Order and deployment schedule identify the applicable operations, authorised sources, data and people concerned, service term, contacts and any customer-specific differences.

  • Purpose and duration: configuration, provision, support and security of the agreed customer intelligence, research, analysis or modelling service, for its contractual term followed by return and deletion.
  • Sources and access: sources authorised by Customer, normally accessed through read-only APIs with minimum permissions. Exports or other access methods require agreement.
  • People concerned: customers, users, research participants, business contacts and authorised service users represented in the approved sources, as applicable to the project.
  • Data categories: approved research, feedback, interview or support content, business context, product-use information, necessary identifiers and contact details, and related derived content. Sensitive categories remain excluded unless expressly agreed.
  • Operations: retrieval, storage, organisation, extraction, indexing, embeddings, analysis, generation of outputs, support, export, correction and deletion. Customer-dedicated training, fine-tuning and evaluation apply only where selected.
  • Outputs and use: analyses or simulations for human evaluation. Simulations are inferred outputs. The standard service does not include solely automated individual decisions with legal or similarly significant effects.
  • Return: source data and agreed customer-specific outputs in a reasonably usable, commonly used electronic format appropriate to the data, specified in the deployment schedule.
  • Retention: active data and model artefacts follow section 9. For logs processed on Customer's behalf, routine operational logs are retained for 30 days and security logs for six months. Such logs remain subject to this DPA even when they contain only metadata. Applicable earlier deletion requirements take precedence. Routine logs contain necessary metadata and references rather than duplicated customer content.
  • Customer-directed analytics: any analytics performed solely on Customer's instructions are specified in the deployment schedule and subject to this DPA. Optional analytics for Coby's own website or service evaluation are separate controller activities covered by its Privacy Notice and applicable consent requirements; they are not included in the processing described in this annex.

Annex II Security measures

The following measures apply to the relevant service components. Any customer-specific allocation of responsibilities or additional measures is recorded in the deployment schedule before processing.

  • Access control: individual authorised accounts, minimum necessary privileges, multi-factor authentication for administrative and other sensitive personnel access, access reviews and timely removal of access.
  • Customer separation: appropriate logical or physical controls separating each customer's data, retrieval, exports, training jobs and adapted model artefacts. Where graph storage is used, its configuration is specified in Annex III and the deployment schedule. Effective separation of customer data and adapted models is required in every configuration. Any dedicated-instance requirement is specified in the deployment schedule.
  • Encryption and credentials: encryption of Customer Data at rest and in transit, including databases, files and backups; TLS for service connections; controlled storage of credentials and removal or revocation when authority ends.
  • Personnel: confidentiality obligations and appropriate data protection and security instruction; access limited to those who need it for their duties.
  • Backup and recovery: protected backups, restricted restoration access, tested restoration appropriate to the service, retention limits and reapplication of deletion after recovery.
  • Logging and maintenance: proportionate operational and security logging, restricted access to records, assessment of vulnerabilities, appropriate remediation and regular review of security measures.
  • Analytics and diagnostics: optional tracking only after the applicable consent, with refusal and withdrawal respected. Customer documents, prompts and AI responses are excluded from replay before transmission. Analytics and diagnostics are minimised to exclude customer content, secrets and unnecessary personal information.
  • Incident response: a reporting route, assessment, containment, investigation and remediation, with customer notification under section 7.

Any additional service levels or recovery objectives are specified in the Order.

Annex III Standard providers and deployment

Coby's standard hosted configuration uses AWS in Europe (Paris), France (eu-west-3). Depending on the agreed service, it may include Neo4j Aura on AWS for graph storage and AWS Bedrock for inference. The table describes available components; the deployment schedule identifies those selected for Customer. Customer-specific alternatives, including hosting in Customer's environment, may be agreed in writing.

Standard providers and deployment components
Provider and serviceFunction and dataStandard location
AWS infrastructureApplication hosting, storage, computing and backups; authorised customer material, credentials, service metadata and model artefacts. Coby-operated open-source models may use AWS GPU infrastructure for agreed training and inference.Europe (Paris), France, eu-west-3.
Neo4j Aura operated by Neo4j on AWS, where selectedManaged graph database containing authorised entities, relationships and derived representations, with backups and service metadata. Appropriate logical or physical controls ensure effective separation of each customer's data and adapted models. The deployment schedule specifies the configuration, including any dedicated instance, tier and capacity.AWS Europe (Paris), France, eu-west-3.
AWS Bedrock where selectedInference using the approved inputs and outputs. The selected model, provider retention and logging configuration are recorded before use.AWS source region Paris; inference restricted to the European Union.

Before processing, the incorporated register identifies each included provider's contracting legal entity, exact service, data scope, processing and storage locations, relevant international access and applicable contractual safeguards. The selected configuration must meet this DPA's customer-dedicated use and deletion requirements.

For Bedrock, the deployment schedule identifies the selected model, EU inference regions, provider retention and logging configuration. These settings must comply with the agreed instructions, use restrictions, retention requirements and the content exclusions in Annex II before Customer Personal Data is processed.

Tools used for Coby's own business administration are described in the Privacy Notice. Email is used for administrative support coordination. Customer content and diagnostic files containing Customer Personal Data must be exchanged through an authorised transfer method agreed for the deployment, using only providers covered by the applicable register. Any collaboration, support, analytics or monitoring provider processing personal data on Customer's behalf must be included in that register before use. Customer-owned source systems are identified in the deployment schedule with their data flows and responsibilities.

The project schedule completes the source and data selection, service components, provider register, any training instructions, authorised contacts, return format and any agreed deployment variations. These details are agreed with Customer before processing, under the authorisation and transfer procedures in this DPA.