Bonmoniq legal

Privacy Policy

Last updated: 2026-10-25

This English version is provided for information as a free translation. The French version is the official legal version. If there is any conflict, the French version prevails.

Who is responsible

Information	Detail
Controller	Bonmoniq SASU
Legal form	SASU, Société par Actions Simplifiée Unipersonnelle (single-shareholder)
SIREN	104 435 557
Head-office SIRET	104 435 557 00012
RCS	Paris
Registered address	47 rue Vivienne, 75002 Paris, France
Legal representative	Dmitrii Poroshkov, President
Privacy contact	privacy@bonmoniq.com
Legal contact	legal@bonmoniq.com
Data protection officer	No DPO is designated; privacy@bonmoniq.com is the point of contact

Bonmoniq does not have the same role for all data:

Bonmoniq is the controller for the website, its Customers' accounts and business contacts, business verification, billing, security, fraud prevention, support and relations with prospects. This policy describes that processing.
Bonmoniq is a processor for Customer Content (conversations, contacts, notes, tasks, files, recordings, transcripts, live call captions and AI processing carried out in the Workspace), which it processes on the Customer's instructions. The Customer is then the controller, and that processing is governed by the Data Processing Agreement.

Purposes, legal bases and periods

Purpose	Data	Legal basis (Article 6 GDPR)	Period
Provide the Service, manage accounts and Workspaces	Name, email, role, preferences, Workspace membership	Performance of a contract, Art. 6(1)(b), where the person is the contracting party (sole trader); otherwise legitimate interest, Art. 6(1)(f), in performing the contract with the business Customer and supporting its Users	Life of the account, then the deletion period (see "Retention periods")
Manage the relationship with the Customer's business contacts (administration, billing, support)	Name, email, job title, exchanges	Legitimate interest, Art. 6(1)(f)	Duration of the contractual relationship, then a limited evidential archive
Verify the Customer's business	See "Business verification"	See "Business verification"	See "Retention periods"
Keep evidence of acceptance of contractual documents	Accepted version, language, date and time, IP address, browser, account and Workspace	Legitimate interest, Art. 6(1)(f), in establishing and defending its rights	5 years after the end of the contract
Billing, accounting and tax obligations	Business name, billing address, email, VAT number, invoices, payments	Legal obligation, Art. 6(1)(c) (French Commercial Code Art. L123-22; French General Tax Code Arts. 286 and 289)	10 years
Collect payments	Payment method (processed by the payment provider), amounts, due dates	Performance of a contract, Art. 6(1)(b), where the person is the contracting party; otherwise legitimate interest, Art. 6(1)(f)	Duration of the relationship, then the accounting period
Security, fraud and abuse prevention, connection and audit logs	IP address, browser, timestamps, security events, abuse signals	Legitimate interest, Art. 6(1)(f), in securing the Service and the network; legal obligation, Art. 6(1)(c), where communications-data retention rules apply	12 months rolling, unless a legal obligation or ongoing proceeding applies
Route and bill communications as an operator (Telephony module)	Calling and called numbers, timestamps, duration, routing	Performance of the contract with the Customer and legitimate interest, Art. 6(1)(b) and (f); legal obligation, Art. 6(1)(c), where it applies	See "Retention periods"
Support	Requests, exchanges, useful technical information	Performance of a contract, Art. 6(1)(b), or legitimate interest, Art. 6(1)(f)	Duration of the contractual relationship, then a limited evidential archive
Prospects (contact form, business exchanges with companies)	Name, business email, company, message	Legitimate interest, Art. 6(1)(f), in replying and developing business with professionals	3 years from collection or from the last actual contact initiated by the prospect
Communications to existing Customers about similar services	Name, business email	Legitimate interest, Art. 6(1)(f)	Until objection
Optional audience measurement of the website and application, when enabled	See the Cookie Policy	Consent, Art. 6(1)(a)	See the Cookie Policy

Where Bonmoniq relies on legitimate interest, a balancing test is carried out and can be provided on request. Consent can be withdrawn at any time, as easily as it was given, without affecting earlier processing (Article 7(3) GDPR).

Emergency-location information

For the Telephony module, emergency-location processing may include the physical address declared by the Customer or User, the associated line and member, a callback number, address-registration status, changes and acknowledgements of service limitations. Information required to register an address or route an emergency call is transmitted to the selected carrier and, through the emergency-service chain, to the competent emergency answering or dispatch service. Access within a Workspace is limited to authorized persons who need it to configure the service or handle emergency notifications.

IP addresses provide only an approximate network location and may reflect a VPN or proxy. They are not proof of the caller's physical address. This notice does not announce continuous GPS tracking or an enabled automatic-location feature. The applicable purposes, legal bases and retention limits are those stated in this notice for telephony, security, emergency calls and declared emergency locations; emergency addresses are not used for advertising.

Google user data

Google connections are optional and request permission separately for the feature you choose. Signing in with Google does not by itself give Bonmoniq access to your contacts, Drive or Gmail.

Sign-in: Bonmoniq requests your Google account identifier, name, email address and, if provided by Google, profile picture to identify your account and sign you in.
Contacts import: read-only access to Google Contacts is used for a one-time import. Bonmoniq reads names, email addresses, phone numbers and organization details so you can review and select contacts for the Workspace address book. It does not change your Google Contacts. After the read, Bonmoniq requests revocation of the access token and does not retain a Google access or refresh token for this import. The review session expires after 30 minutes; its temporary data is deleted after import or during expired-session cleanup.
Google Drive: when this integration is enabled for the Workspace, Bonmoniq requests per-file access through Google's file picker. It reads only the files you select and copies them into the Space you choose; Google-native documents may be exported as PDF. Bonmoniq does not write to Drive or read unrelated Drive files. The Drive access token remains in the browser and is not stored by Bonmoniq's server. Removing access at Google does not delete copies already imported into Bonmoniq.
Gmail: where the Email channel offers this connection and you choose it, a separate authorization allows Bonmoniq to read emails and their attachments from the connected mailbox and send emails on your instructions. This is ongoing mailbox access, not the one-time Contacts import. Credentials needed to maintain that connection are retained while it is connected. No Gmail access is granted by signing in, importing contacts or selecting Drive files.

Imported contacts, files and emails are Customer Content. They are stored, shared with authorized Workspace users and processed to provide the features the Customer chooses, under the Data Processing Agreement and the retention periods below. Customer-authorized AI assistance may process that content to provide the requested feature; processing is not model training. Bonmoniq does not use Google user data to train its own AI models. The separate provider disclosures and limitations in "Artificial intelligence" apply where the Customer selects a feature that uses an external provider; this paragraph does not promise that every external provider has zero retention or a verified training opt-out.

Bonmoniq does not sell Google user data or use it for advertising. Bonmoniq's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Access and transfers are limited to providing the features you authorize and the permitted security, legal and other exceptions in that policy.

You can revoke Google's authorization at any time in your Google account connections. Revocation stops the authorized Google access, but does not by itself erase data already imported. You can delete imported content in Bonmoniq or exercise the rights described below; the applicable deletion and backup periods remain those in this policy and the DPA.

Business verification (KYB)

To open a business account, Bonmoniq verifies the Customer's business against the official registry: the French business registry (recherche-entreprises.api.gouv.fr, INSEE Sirene open data) using the SIREN or SIRET, or Companies House for a United Kingdom company where that registry is available. A dated copy of the registry response is kept as verification evidence. For a sole trader, this data (including name and address) is personal data. It is used only to verify a Customer; this is not a prospecting activity and the data is never used as a lead source.

For the Telephony module only, obtaining a number may require documents specific to the country and number type (registration extract, identity document, proof of address). These documents are encrypted at rest; if encryption is not available, the upload is refused. When enabled, an automated pre-review by a Bonmoniq-operated model reads the documents to route the file to the appropriate verification; it never decides approval or refusal. Documents are sent to a carrier only where that carrier requires them to assign the number and that delivery is enabled for that carrier. They are never sent to the payment provider or used for any other purpose.

Following approval, documents are deleted as soon as the carrier's decision is received, unless the Customer expressly chooses the retention option below. If the Customer expressly chooses to keep its approved documents for a later request in the same country, they are kept for at most 90 days from upload; this choice can be withdrawn at any time. If verification is refused, documents are deleted 30 days after the refusal unless resubmitted. Verification metadata (business name, registration number, representative, decision, dates, carrier reference) is kept separately, in a restricted-access archive, for 5 years after the end of the contract.

Legal bases: performance of a contract, Art. 6(1)(b), where the sole trader is the contracting party; legal obligation, Art. 6(1)(c), where obligations to identify electronic communications subscribers apply; legitimate interest, Art. 6(1)(f), in preventing fraud and keeping evidence of the verification.

Recipients

Data is accessible only to authorized Bonmoniq personnel and to the recipients below, each for its purpose. Contracting entities, processing regions and transfer safeguards are stated from Bonmoniq's accounts and the providers' published agreements; they must not be inferred from the provider's name alone.

Recipient	Purpose	Role	Location and safeguards
Scaleway SAS	Hosting of the Service: application servers, databases (Scaleway Managed PostgreSQL) and the servers running the AI models operated by Bonmoniq	Processor	Scaleway SAS, 8 rue de la Ville-l'Évêque, 75008 Paris, France. The application server, the AI server (dedicated Elastic Metal server) and the database are located in the Paris region (fr-par), France.
Scaleway SAS	Sending of messages from the website contact form (Scaleway Transactional Email)	Processor	Same company; Paris region (fr-par)
Scaleway SAS	Sending of Service emails (sign-in, invitations, notifications) through Scaleway Transactional Email, the provider selected for this sending, when this sending is enabled for the Service	Processor	Same company; Paris region (fr-par). For this service, Scaleway's data processing agreement places processing in the European Union by default and requires Scaleway to inform Bonmoniq in advance of any transfer outside the European Union and, where one occurs, to apply the Standard Contractual Clauses
Cloudflare, Inc.	Delivery of the website and Service interface, DNS, CDN, DDoS protection and network security, anti-bot protection of forms (Turnstile); storage of the Service's files (R2), such as attachments, media and encrypted business-verification documents	Processor	Global network; Cloudflare, Inc. is established in the United States. The storage buckets are configured in Cloudflare's European Union jurisdiction. Cloudflare's published data processing addendum provides for the European Commission's Standard Contractual Clauses for transfers
Amazon Web Services EMEA SARL (Amazon SES, Amazon S3, Amazon SQS)	Sending and receiving emails of the Email channel when the Customer uses an address on Bonmoniq's mail domain; an incoming email is held temporarily before it is imported, then deleted, at the latest after one day	Processor	Contracting party under AWS's standard customer agreement for accounts in Europe, the Middle East and Africa: Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg. Region: Europe (Paris), eu-west-3. AWS's data processing addendum incorporates the Standard Contractual Clauses for transfers
Stripe	Payment collection	Processor for payment processing; independent controller for its own obligations (fraud prevention, financial regulation)	Stripe Payments Europe, Limited, Ireland: contracting entity under the Stripe Services Agreement for accounts in the European Economic Area; another Stripe entity may be an additional party for certain services. Stripe's data processing agreement provides for the Standard Contractual Clauses for transfers
Olinda SAS (Qonto)	Bonmoniq's business bank account, receipt of transfers	Independent controller	France, European Union
Google, Apple	Sign-in with a Google or Apple account, where offered and when the user chooses it	Independent controllers	Under their own policies
Google, Microsoft	Connection of a mailbox to the Email channel, at the Customer's request	Providers of the Customer's mailbox; Bonmoniq accesses it on the Customer's behalf	Under the Customer's contracts with those providers
Twilio, Telnyx, Sinch	Telephony module: see "Telecommunications carriers"	Depending on the purpose and the carrier	See below
Push services of browsers and operating systems (for example Google, Mozilla, Apple, Microsoft)	Delivery of notifications when the user turns them on in the browser	Providers chosen by the user's browser or device	The notification content is encrypted; the push service processes the subscription address and delivery data
Cartesia AI, Inc.	Premium voices, for Workspaces with a paid company subscription: see "Artificial intelligence"	Processor, only when a Premium voice is explicitly selected	See below
Cloudflare Web Analytics, PostHog	Optional audience measurement, when enabled: see the Cookie Policy	Processors	See the Cookie Policy

Bonmoniq does not sell personal data.

For the WhatsApp Business integration, Bonmoniq uses Telnyx as its communications provider. Where the connection is activated, the data needed to deliver the communication, including sender and recipient identifiers, message content and delivery information and, for WhatsApp calls, call content and routing information, pass through Telnyx and the WhatsApp platform. Telnyx processes data on Bonmoniq's instructions where its DPA assigns it that role, and acts as an independent controller for the purposes assigned to it as controller. Its DPA section 4.6 also covers transmission through third-party networks and over-the-top platforms such as WhatsApp; those participants are not all treated as Telnyx sub-processors under that agreement. The carrier and international-transfer disclosures below apply. This planned provider choice does not itself confirm activation of the integration or processing only within the European Union.

Telecommunications carriers

These carriers are involved only where the Customer uses the Telephony module. Bonmoniq relies on three partner carriers: Twilio, Telnyx and Sinch. They are not all used for every call or number: the carrier is selected according to the country, the number, the destination and the service. The country of a number does not guarantee that data is processed in the European Union. A call or message also passes through the networks serving its origin and its destination, so where a carrier processes it depends in particular on that destination, not on the country in which Bonmoniq's account with the carrier is registered or invoiced.

A carrier's role depends on the purpose, the product concerned and its own agreement; it is not the same for every carrier:

as a processor or sub-processor, for the functions that Bonmoniq delegates to it on the Customer's behalf and that its agreement treats as processing on Bonmoniq's instructions;
as an independent controller, for operating its own network, its traffic and usage data, fraud prevention and compliance with its legal and regulatory obligations (for example routing emergency calls and responding to requests from authorities), and for any other processing its agreement assigns to it as controller. In particular, Sinch's Data Processing Agreement (section 3(a)(iv)) treats the transmission of communications as processing for which Sinch is an independent controller, and the Twilio and Telnyx agreements set out their own cases in which they act as controllers. That processing is governed by the carrier's own privacy policy.

Carrier	Published processing agreement	Contracting entity, regions and transfer safeguards
Twilio	Data Protection Addendum	Twilio Ireland Limited, 70 Sir John Rogerson's Quay, Dublin 2, D02 R296, Ireland: contracting party under Twilio's standard terms of service for customers registered in the European Economic Area, which incorporate this addendum, unless a separate written agreement provides otherwise; also the issuer of Bonmoniq's invoices. Other Twilio affiliates may supply certain services depending on the country or product. Transfers (Schedule 3 of the addendum): a single mechanism applies, in this order of precedence: the EU-US Data Privacy Framework and its UK and Swiss extensions, to which Twilio Inc. is self-certified; Twilio's Binding Corporate Rules; then the European Commission's Standard Contractual Clauses, with Twilio Inc. as data importer, Module 1 (controller to controller), Module 2 (controller to processor) or Module 3 (processor to processor) depending on each party's role. Processing region: Twilio states that, where no other region is selected, data is processed in its default region in the United States (US1), and that not all data is guaranteed to remain in a selected region. When checked on 11 October 2026, Bonmoniq's Twilio account had no number and no Elastic SIP trunk in that region, and Twilio is not yet activated for Bonmoniq's traffic; before any activation, the region configured for Bonmoniq's route will be verified and stated here.
Telnyx	Data Processing Addendum	Telnyx LLC (and, where applicable, its subsidiaries or affiliates), 600 Congress Avenue, 14th Floor, Austin, TX 78701, United States: party to Telnyx's standard terms and conditions of service, which incorporate this addendum, unless a separate written agreement provides otherwise. Telnyx states that its primary processing facilities are in the United States; some services allow a processing region to be selected (section 5.5). Transfers (section 5): the addendum states that Telnyx is certified to the EU-US Data Privacy Framework and its UK and Swiss extensions; the addendum also incorporates the European Commission's Standard Contractual Clauses, Module 1 (controller to controller), Module 2 (controller to processor) or Module 3 (processor to processor) depending on each party's role, which continue to apply if that certification ends, and the UK addendum for transfers from the United Kingdom
Sinch	Data Processing Agreement	Sinch Sweden AB, Lindhagensgatan 112, 112 51 Stockholm, Sweden: contracting party under Sinch's standard terms of service for services that a customer domiciled outside the United States and Canada orders itself through the Sinch dashboard, which incorporate this agreement, unless a separate agreement provides otherwise. Sinch may transfer personal data within its group to provide its services globally. Transfers (Annex 1 of the agreement): the European Commission's Standard Contractual Clauses, Module 2 (controller to processor) where Sinch acts as processor and Module 3 (processor to processor) where it acts as sub-processor, together with additional security measures. Processing locations: Sinch publishes regional endpoints for its services (for voice: the United States, Brazil, Europe, Singapore and Australia, with a global address that routes to the nearest region) and a list of sub-processors whose application depends on the service and the Sinch region. For voice, SIP trunking and messaging, that list names hosting and support locations in the European Union (including Ireland, Germany and Sweden), the United Kingdom, the United States, Canada, Brazil, Australia, Singapore and other countries where Sinch group entities provide support. Sinch is not yet activated for Bonmoniq's traffic and no Sinch processing region has been selected; before any activation, the region configured for Bonmoniq's route will be verified and stated here.

Where the Telephony module is used, Bonmoniq also processes, as controller, limited data about people the Customer calls and about callers (numbers, timestamps, routing data) to operate, bill and secure the Service. This data is obtained through the Customer's use of the Service (Article 14 GDPR).

Artificial intelligence

The AI features of the Service (AI voice agent, conversation assistance, transcripts, summaries, pre-review of verification documents when enabled) run on models operated by Bonmoniq. Conversation content is not sent to a third-party AI provider for this reasoning. Transcripts and summaries are produced automatically; summaries are marked in the Service as written by AI.

Premium voices. The AI voice agent is part of the Telephony module. Its voice is by default a Standard voice, synthesized by Bonmoniq without calling an external provider. Premium voices are reserved for Workspaces with a paid company subscription. Where such a Customer explicitly selects a Premium voice, including to listen to it before choosing it, the text to be spoken is synthesized by Cartesia, currently the only Premium provider. That provider receives:

the text to be spoken, which may contain personal information from the conversation;
the chosen voice, language and sound settings;

and returns the generated audio. It receives neither the caller's voice nor the call transcript. The agent's notices (AI notice, recording notice) are spoken with the chosen Premium voice; a notice in a language that voice does not speak is spoken by another Cartesia voice, failing that by a Standard voice. A Standard voice, and its notices, never call an external provider. Premium voices are available only when Bonmoniq has enabled them for the platform; otherwise the agent uses a Standard voice. Any other Premium provider would be used only after this policy and the Data Processing Agreement have been updated.

Provider	Published processing agreement	Contracting entity, location, retention and use for training
Cartesia	Data Processing Addendum	Cartesia AI, Inc., established in the United States, under its public self-service terms, which incorporate this addendum. Bonmoniq does not state that this data is processed only in the European Union. Transfer: the addendum incorporates the European Commission's Standard Contractual Clauses, Module 2 (controller to processor) and Module 3 (processor to processor) (section 12.2). Retention: under Annex I of the addendum, data is kept for as long as necessary for the purpose of the processing and in accordance with applicable law; Cartesia publishes no fixed retention period for each request. Section 10.2 allows Bonmoniq to request return of the data up to 90 days after termination of Bonmoniq's agreement with Cartesia; Cartesia must then delete remaining copies within 180 days after returning the data, subject to the legal qualifications in that section. Closing a Customer Workspace does not itself terminate Bonmoniq's agreement with Cartesia. These are not a fixed per-request period or a verified deadline for deletion after a Workspace closes. Cartesia's support stated on 14 October 2026 that no set retention period applies to this data, that deletion requests are filed by the customer and that it cannot automate them, and on 15 October 2026 that it can process only one such request per organization every 90 days. Bonmoniq's policy is therefore to submit to Cartesia, manually and every 90 days, a request to delete the data retained for Bonmoniq's entire Cartesia organization. This 90-day interval is a limit on how often a request can be made, not a retention period: Cartesia does not delete this data automatically. Cartesia's support stated on 16 October 2026 that each request covers all inputs and outputs retained in its system when the deletion is processed, and that Cartesia completes the deletion within 90 days after the request is submitted. That period runs from the submission of a request, not from an individual synthesis or the closure of a Workspace. Bonmoniq therefore does not state that each copy held by Cartesia is deleted within 90 days of its creation, and Bonmoniq has not independently verified the completion of any deletion. Zero data retention, an Enterprise option, is not enabled. Training: the addendum limits the processing of personal data to Bonmoniq's documented instructions (sections 3.1 and 3.2). Cartesia's privacy policy, which describes the processing for which Cartesia acts as controller, states that content may be used to train its models and points to account data controls to opt out, with effect only for the future. On 14 October 2026, Bonmoniq turned off the "Contribute to model training" control in the data controls of its Cartesia organization and verified that the setting was saved as disabled. This organization-level setting applies from the date it was saved, including to the text sent for synthesis and the generated audio. It does not reverse any use made before that date, and Bonmoniq has not independently verified Cartesia's internal processing. Bonmoniq therefore does not state that this content has never been, or can never be, used for training.

Bonmoniq plays a notice telling the caller that they are interacting with an artificial intelligence at the start of every call handled by an AI voice agent. See the AI transparency notice.

Recordings, transcripts and people contacted

Where the Customer turns on call recording or transcription (Telephony module), the content may reveal special categories of data (Article 9 GDPR) expressed by participants. The Customer is the controller of that processing, responsible for informing participants and for complying with applicable consent rules. Bonmoniq acts as processor under the Data Processing Agreement.

Live call captions

Live call captions start automatically with the call in the Telephony module. Neither the Customer nor an employee can turn them off; there is no separate manual start or captions toggle. Speech recognition operated by Bonmoniq turns both parties' speech into text for live display and uses no external speech-recognition or AI provider. Captioning does not itself record the call or create a saved caption transcript. The initial call announcement informs participants about captions together with the recording announcement; there is no separate mid-call captions announcement. Recording controls remain separate: stopping a recording, including by pressing 9 where offered, does not stop captions.

If a participant objects to captions, or required consent is absent or withdrawn, the Customer must end the call rather than continue that processing. Captions cannot be disabled while continuing the call. Ending the call does not itself delete any separate recording or other retained content; applicable requests follow the Privacy Policy and DPA. This policy does not assert that the Service automatically detects an objection or consent status.

The caption text is displayed to the authorized User handling the call. Supervisor access remains off unless the Customer separately enables it and informs its staff and, where required, consults their representatives. An authorized owner or administrator may then read captions only for a line they may access in the same Workspace. Each read is logged without the caption words; if the log cannot be written, the text is not shown.

The Customer remains responsible for a lawful purpose, proportionality, participant and staff information, any required consent and the handling of objections and other data protection requests. Automatic captioning and the absence of an off switch do not waive these duties or Bonmoniq's duties as processor. Participants may contact the Customer about the processing, or Bonmoniq using the contacts in this policy; no user-controlled captions stop is promised.

Caption audio is processed transiently in Service memory. Caption text is buffered in the Service and authorized browsers for live display until technical session cleanup after the call; cleanup is not immediate at hang-up and no fixed period is promised. Captions are not archived as a saved caption transcript or audio file, and the separate transcript retention period does not apply to caption text. Any separate recording, saved transcript or AI conversation retains its own retention rules. Associated information and supervisor-read records contain no caption words and follow the retention appropriate to their purpose.

Speech captured in captions may reveal special categories of data (Article 9 GDPR); the Customer's existing responsibilities apply. Captions may contain errors, change while provisional or omit words. They assist with following the call, are not a certified record and do not make automated decisions about a person. Human speech captioned in this way remains human speech, not AI-generated speech. In an AI-agent or call-flow test, captions may display caller text already recognized for the agent and the exact agent response text without transcribing synthetic audio again.

Retention periods

The periods below are Bonmoniq's choices or product settings. They are not maximum periods set by law for every use, and a legal obligation or ongoing proceeding may require different retention.

The active-deletion and backup periods below cover copies in the Service operated by Bonmoniq, including its infrastructure hosts. Copies already transmitted to Cartesia for optional Premium synthesis are subject to the specific retention and return/deletion conditions disclosed under "Artificial intelligence" and in the DPA; Bonmoniq does not represent that those copies follow its own 30-day deletion and 90-day backup periods. Bonmoniq forwards the Customer's applicable deletion or return instructions to Cartesia without undue delay and follows up on their execution. The 90-day cadence of Bonmoniq's organization-wide deletion requests to Cartesia, described under "Artificial intelligence", is neither a retention period nor a deadline for erasure. It does not suspend that forwarding and follow-up, and it is not a period during which a request to exercise your rights may wait. This distinction does not remove data-subject rights or Bonmoniq's responsibility for its sub-processors.

Data	Period
Customer Content in the Bonmoniq-operated Service	For the life of the Workspace. After a deletion request or the end of the contract, at most 30 days during which it can be exported, then active deletion. Ending paid access alone is not deletion or formal termination of the processing of retained content; return and deletion follow a valid deletion request or formal termination, with support access for applicable requests
Export archives	7 days after creation
Backups of the Bonmoniq-operated Service	Automatic daily snapshots of the Service database: 7 days; other backups: rotation of at most 90 days
Server technical logs	Rotation by volume (a fixed number of files of limited size per service, the oldest deleted first); no duration in days is promised
Technical copies of events exchanged between components of the Service	7 days after delivery
Call history and call detail records (Telephony module)	12 months from the call
Restricted copy of traffic data (numbers, date, time and duration of the call), kept for the communications-data retention obligations that may apply to Bonmoniq as an operator	1 year from the call, including after the Workspace is closed
Log of emergency calls	1 year from the call
History of the emergency locations declared by members	1 year from each change; the member's current location is kept while it is in use
Call recordings (audio)	90 days by default; the Customer may choose 30, 90, 180, 365 or 730 days for a legitimate purpose. For a line in an EU or EEA country, or in a country without a recording profile, at most 180 days
Transcripts	365 days by default; the Customer may choose 90, 180, 365 or 730 days for a legitimate purpose. For a line in an EU or EEA country, or in a country without a recording profile, at most 365 days. A transcript is never kept for less time than the audio it comes from. Call summaries follow the transcript
Live call captions (audio and text)	Not archived as a saved caption transcript or audio file and not subject to the period for transcripts. Audio is processed transiently; caption text is buffered for live display until technical cleanup of the session after the call, without a fixed period. See "Live call captions"
Voicemail messages	Same period as the call recordings of the line concerned
Log of access to and deletion of recordings	3 years (1,095 days)
AI voice agent conversations and their transcripts	12 months from the start of the conversation; the caller's number and the technical connection data of the session are erased after 30 days
Actions carried out and actions suggested by the AI voice agent, with the decision taken on each suggestion	12 months from the action or the suggestion
Web Chat visitor sessions	12 months after the last activity; the conversations themselves are Customer Content
Copies of emails sent by the Service	Content: 30 days after sending; delivery records and notification history: 12 months
Security and audit logs	12 months rolling
Event metadata linked to a person	Anonymized or deleted after 12 months, unless a legal retention obligation applies
Business verification documents	See "Business verification"
Business verification metadata, evidence of acceptance of contractual documents	5 years after the end of the contract, restricted-access archive
Invoices and accounting records	10 years
Prospects	3 years from collection or from the last actual contact initiated by the prospect; opening an email does not extend this period
Optional audience measurement	See the Cookie Policy

Transfers outside the European Union

Some recipients are established in the United States or may access data from the United States, in particular for support or security. A transfer to a third country takes place only to the recipients that actually make one, and it is covered by an adequacy decision (including the EU-US Data Privacy Framework, only where the recipient concerned is certified) or by the European Commission's Standard Contractual Clauses suited to each party's role. The instrument applicable to each recipient is stated in the tables above or will be stated there; a copy can be requested at privacy@bonmoniq.com.

US providers and the CLOUD Act

Bonmoniq cannot guarantee complete independence from US law. Providers established in the United States, or their US parent companies, may be subject to laws such as the CLOUD Act, which can in principle require them to disclose data they hold regardless of where it is stored. Bonmoniq reduces this risk through data minimisation, encryption in transit and at rest, contractual safeguards and by running AI reasoning on models it operates.

Rights of data subjects

Under Articles 15 to 22 GDPR, data subjects have rights of access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent, by writing to privacy@bonmoniq.com. They may object at any time, on grounds relating to their particular situation, to processing based on legitimate interest, and without giving reasons to prospecting.

For Customer Content, Bonmoniq forwards the request to the Customer as controller where the Customer is identifiable.

Bonmoniq does not take decisions producing legal effects or similarly significantly affecting a person based solely on automated processing (Article 22 GDPR), including by the AI voice agent. The automated pre-review of verification documents helps route the file and does not decide.

Data subjects may lodge a complaint with the CNIL (www.cnil.fr) or with the supervisory authority of their country of residence or work.