Bureava

← Back

Data Processing Agreement

Annex to the Bureava terms and conditions of sale · Reference CTR-2026-0003 · version in force on 25 October 2026.

This Agreement is entered into between MAVOIX DIGITAL SASU, publisher of the Bureava service (hereinafter "the Processor"), and each business customer of Bureava, identified at the time of its Order (hereinafter "the Controller").

It sets out the undertakings of the parties pursuant to Article 28 of Regulation (EU) 2016/679 of 27 April 2016 (hereinafter "the GDPR").

General provisions

Article 1 – Subject matter and duration

The purpose of this Agreement is to define the conditions under which the Processor, MAVOIX DIGITAL SASU, a single-shareholder simplified joint-stock company (société par actions simplifiée unipersonnelle) with a share capital of €300, whose registered office is at 4 place Albert Uderzo, 78420 Carrières-sur-Seine, France, registered with the Versailles Trade and Companies Register (RCS) under number 131 836 173, undertakes to carry out, on behalf of the Controller, processing operations concerning the personal data (hereinafter "the Data") defined below in connection with the Bureava service (hereinafter "the Service").

It is entered into pursuant to Article 28 of the GDPR and forms an annex to, and an integral part of, the terms and conditions of sale (hereinafter "the Terms"). In the event of any conflict between the Terms and this Agreement as regards the protection of the Data, this Agreement shall prevail.

This Agreement takes effect on the date on which the Controller accepts the Terms and applies for as long as the Service is used, subject to the provisions of Articles 14 and 16.

Article 2 – Nature and purpose of the processing

The Processor is authorised to process the Data on behalf of the Controller solely to the extent necessary for the provision of the Service.

The processing operations carried out are as follows:

The sole purpose of the processing is the provision of the Service to the Controller, to the exclusion of any other purpose, in particular any commercial or statistical purpose of the Processor's own.

Article 3 – Types of data and categories of data subjects

The types of Data processed in connection with the Service are as follows, depending on the functions used by the Controller:

The categories of data subjects are as follows: the executives and users of the Service; the Controller's employees, interns and job applicants; its customers, prospects, suppliers and correspondents; persons who call, or are called by, the Service; meeting participants.

As regards absences, the Service records only their general reason (leave, sickness, training or other), without any medical information. As the "sickness" reason may constitute data concerning health, the Controller records it only in the context of its obligations as an employer (Article 9.2.b of the GDPR).

The Controller refrains from voluntarily entering into the Service any other special categories of data within the meaning of Article 9 of the GDPR, or any data relating to criminal convictions and offences within the meaning of Article 10 of the GDPR. Where such data nevertheless appear in the Service, in particular in documents, calls or meetings, they benefit from the same security measures, and the Controller remains solely responsible for them.

Obligations of the Processor

Article 4 – Documented instructions

The Processor shall process the Data only on documented instructions from the Controller, including with regard to transfers of Data to a third country or an international organisation, unless required to do so by Union or Member State law to which the Processor is subject. In such a case, the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.

The Terms, this Agreement and the configuration of the Service carried out by the Controller constitute its documented instructions. Any additional instruction shall be given in writing.

The Processor shall immediately inform the Controller if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. It may then suspend the execution of the instruction concerned until it is confirmed or amended by the Controller.

Article 5 – Confidentiality

The Processor guarantees the confidentiality of the Data processed under this Agreement.

It shall ensure that the persons authorised to process the Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, that they have access only to the Data necessary for the performance of their tasks, and that they receive the necessary training in personal data protection.

The Processor shall not disclose the Data to any third party, except to Sub-processors authorised in accordance with Article 7, or in compliance with a legal obligation under the conditions provided for in Article 4.

Article 6 – Security of processing

In accordance with Article 32 of the GDPR, the Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing, as well as the risks to the rights and freedoms of the data subjects.

The measures actually implemented in the Service are as follows:

The Processor may change these measures, provided that it never reduces the overall level of security of the Service.

Article 7 – Sub-processors

The Controller gives the Processor general written authorisation to engage the Sub-processors listed in the annex to this Agreement, in Articles 17 to 22, to carry out the processing activities described therein.

The Processor shall inform the Controller in advance and in writing of any intended changes concerning the addition or replacement of a Sub-processor, at least thirty days before that change, specifying the processing activities concerned, the identity and contact details of the Sub-processor and the applicable transfer safeguard.

The Controller has a period of fifteen days from the date of that notice in which to object in writing, stating its reasons. In the event of an objection, the parties shall seek a solution in good faith; failing agreement within fifteen days of the objection, the Controller may terminate the Service in writing, without penalty, with effect from the date of the change. The Processor shall then refund the portion of the price paid in advance for the remaining period.

The Processor shall impose on each Sub-processor, by contract, the same data protection obligations as those set out in this Agreement, in particular sufficient guarantees to implement appropriate technical and organisational measures. It remains fully liable to the Controller for the performance of the Sub-processors' obligations.

Article 8 – Transfers outside the European Union

The Service relies on Sub-processors established outside the European Union, listed in the annex. By accepting this Agreement, the Controller instructs the Processor to transfer the Data to those Sub-processors, solely for the services described in the annex. No other transfer takes place without documented instructions from the Controller, in accordance with Article 4.

Each transfer relies on one of the safeguards provided for in Articles 44 to 49 of the GDPR: the adequacy decision (EU) 2023/1795 of 10 July 2023, where the recipient appears on the list of the EU–US data protection framework ("Data Privacy Framework"); failing that, the standard contractual clauses adopted by the European Commission (Commission Implementing Decision (EU) 2021/914 of 4 June 2021), module 3, entered into between the Processor and the Sub-processor, accompanied by a written assessment of the transfer and, where necessary, by additional measures.

The safeguard applicable to each Sub-processor is specified in the annex to this Agreement, in Articles 17 to 22. Where a safeguard is merely declared by the Sub-processor or has not yet been put in place, the annex says so expressly.

At the written request of the Controller, the Processor shall provide it with a copy of the documents establishing the safeguard applicable to each transfer.

Where the Controller is established outside the European Union, the Data are made available to it under the standard contractual clauses of Commission Implementing Decision (EU) 2021/914, module 4, which form part of this Agreement. It is for the Controller to complete the formalities provided for by its national law, in particular for the disclosure of the Data to service providers established in other countries.

Article 9 – Assistance with the exercise of data subjects' rights

The Processor shall assist the Controller, by appropriate technical and organisational measures and insofar as this is possible, in fulfilling the Controller's obligation to respond to requests from data subjects for exercising their rights laid down in Chapter III of the GDPR, in particular the rights of access, rectification, erasure, restriction, objection and data portability.

Where a data subject submits a request to exercise their rights directly to the Processor, the Processor shall forward it without delay to the Controller, by email, and shall not respond to it itself, unless instructed to do so in writing by the Controller.

The Processor makes available to the Controller, within the Service, the functions enabling it to consult, rectify and delete the Data, or carries out those operations, as well as extraction of the Data, on the Controller's documented instructions in accordance with Article 4.

Article 10 – Personal data breach

The Processor shall notify the Controller of any personal data breach, including one occurring at a Sub-processor, without undue delay after becoming aware of it, and no later than forty-eight hours thereafter. The notification shall be sent by email to the address of the owner of the Controller's account in the Service, or to any other address designated by the Controller in writing.

The notification shall contain at least the following information, provided in phases where it cannot be provided at the same time:

It is for the Controller to notify the breach to the supervisory authority and, where appropriate, to the data subjects, the Processor providing it with the necessary assistance.

Article 11 – Data protection impact assessments and prior consultation

Taking into account the nature of the processing and the information available to it, the Processor shall assist the Controller in carrying out the data protection impact assessments provided for in Article 35 of the GDPR, in particular by providing it with the description of the processing operations carried out in the Service and of the security measures implemented pursuant to Article 6.

The Processor shall also assist the Controller, where appropriate, in carrying out the prior consultation of the supervisory authority provided for in Article 36 of the GDPR, by providing it with the relevant information in its possession.

Article 12 – Documentation and audits

The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and in this Agreement, in particular the description of the security measures and the up-to-date list of Sub-processors.

The Processor shall allow for and contribute to audits, including inspections, conducted by the Controller or by an auditor mandated by it. The mandated auditor shall be bound by a duty of confidentiality and may not be a competitor of the Processor.

The Controller shall inform the Processor of any audit in writing, giving thirty days' notice. Save in the event of a data breach, serious indications of a breach of obligations or a request from a supervisory authority, audits shall take place no more than once a year and shall be at the Controller's expense. The audit shall take place during business hours, without disrupting the operation of the Service or prejudicing the data of the Processor's other customers.

As regards Sub-processors, the Processor shall provide their available audit reports or certifications. It keeps the record of processing activities provided for in Article 30.2 of the GDPR and communicates it to the Controller on request. It shall cooperate with the supervisory authority at its request.

Obligations of the Controller and final provisions

Article 13 – Obligations of the Controller

The Controller undertakes to:

Article 13 bis – Telephone calls

At the start of each call, the Service itself announces that the caller is speaking with an automated voice assistant and that the call is being transcribed. The Controller supplements the information given to callers, in particular on its website, in accordance with Article 13 of the GDPR.

Article 14 – Fate of the Data at the end of the Agreement

Upon the end of the provision of the Service, for whatever reason, the Processor shall, at the Controller's request, return all the Data to the Controller, in a structured and commonly used format, within thirty days.

The Controller may moreover, at any time, download its Data from the Service; files that cannot be downloaded directly from it are handed over on simple request.

From the day after the end of the Service, the Service becomes read-only. Thirty days after the end of the Service, the Processor shall delete the Data in the Service, unless Union or Member State law requires storage of the Data; in that case, the Data retained shall be limited to what that law requires and shall not be subject to any other processing. Back-up copies and those of the Sub-processors disappear at the end of their retention period, and no later than ninety days after the end of the Service; they are no longer used in the meantime.

In the event of the Processor ceasing its activity, the Controller may obtain the return of its Data under the conditions of this Article.

The Processor shall provide written confirmation of the deletion at the request of the Controller.

Article 15 – Liability

Each party shall be liable for damage resulting from its own breaches of the GDPR and of this Agreement, under the conditions laid down in Article 82 of the GDPR.

The Processor shall be liable for the damage caused by processing only where it has not complied with obligations of the GDPR specifically directed to processors or where it has acted outside or contrary to lawful instructions of the Controller.

As between the parties, each party's liability shall be exercised within the limits provided for in the Terms, without prejudice to the rights that data subjects hold under the GDPR. Each party shall bear the administrative fines imposed on it. The liability cap provided for in the Terms does not apply in the event of gross negligence or wilful misconduct.

Article 16 – Term, acceptance and governing law

This Agreement is accepted by the Controller at the same time as the Terms, when placing the Order, and does not need to be signed separately. On request, the Processor shall provide the Controller with a signed copy.

It remains in force for as long as the Service is provided, and its provisions on the fate of the Data set out in Article 14 shall survive until they have been fully performed.

This Agreement is drafted in French; any translation is provided for information only and, in the event of discrepancy, the French version prevails. The Processor shall inform the Controller by email, at least thirty days in advance, of any amendment to this Agreement; an amendment that reduces the protection of the Data applies only with the written agreement of the Controller.

This Agreement is governed by French law. Any dispute relating to its formation, interpretation or performance shall be settled in accordance with Article 16 of the Terms.

Annex: list of Sub-processors

Article 17 – Cloudflare, Inc.

Article 18 – Anthropic, PBC

Article 19 – ElevenLabs

Article 20 – Telnyx LLC

Article 21 – Brevo (Sendinblue SAS)

Article 22 – Supabase, Inc.

Article 23 – Services connected by the Controller

Where the Controller itself connects to the Service an account that it holds with a third party (a Google mailbox or calendar, or Meta Facebook Pages or Instagram accounts, for example), that third party remains its own service provider, under the contract that binds them, and is not a Sub-processor. The Processor accesses that account only to the extent authorised by the Controller, who may withdraw that access at any time. For Facebook Pages and Instagram accounts, the procedure is set out on the page Facebook and Instagram data: deletion instructions.

For any question about this Agreement: [email protected].

Back to home