How SpeakDo protects your ERP
Last updated: August 2026
1. Passwordless authentication
Each enrolled device (phone, tablet) generates its own cryptographic key pair locally at the moment it's paired with the ERP. The private key never leaves the device and is never transmitted, including to MargePro SASU. Every request is signed with this key rather than protected by a shared password — so there is no user password that could leak.
2. Encryption of ERP access
Your ERP's API key is never stored in plain text (libsodium, authenticated secretbox). It is decrypted temporarily in memory during authorized calls to your ERP, then wiped immediately after use, with administration access strictly limited and logged.
3. Tokens and replay protection
- Session and payment tokens are stored as hashes only, never in plain text
- Every signed request carries a timestamp and a single-use nonce: an intercepted and replayed request is rejected
- All communications are encrypted over TLS (HTTPS required)
4. Minimization of data sent to the language engine
The LLM is used to understand a request and prepare a structured action — never to decide permissions or write freely into the ERP. SpeakDo doesn't forward a copy of your ERP: it selects only the context needed for the action at hand.
Some actions — notably identifying a company or a contact — apply a minimal selection of allowed fields: name, reference and city, never the full record or banking data. This per-action minimization is being rolled out progressively across the rest of the catalog.
SpeakDo favors European providers for hosting and language processing — notably OVHcloud, with Scaleway as a fallback depending on the services activated.
Under OVHcloud's published commitments for AI Endpoints, submitted content isn't used to train or improve the models. SpeakDo doesn't log full prompts by default.
The LLM proposes an action from a closed catalog; the ERP applies the user's real permissions and carries out the write, after confirmation when required.
SpeakDo talks about minimization, not anonymization: some requests naturally need a customer name or an identifiable business detail. The privacy policy details the processing and its purposes.
5. Your ERP keeps control
SpeakDo doesn't replace your permissions or your approvals:
- The permissions applied are those of the ERP user — not SpeakDo's
- Writes use a closed, versioned action catalog, never a free write decided by the language model
- Every sensitive operation is shown to the user before confirmation
- A device can be revoked at any time from Dolibarr: revocation is immediate for any write (permissions are systematically re-checked when confirming an action); for a simple lookup, it takes effect within 10 minutes at most (session revalidation window)
6. AI agents and controlled catalog
An AI agent connected to SpeakDo (via MCP) never gets open access to your ERP. It receives the same closed action catalog as the PWA, filtered by the same ERP permissions and, where applicable, by a role profile that further restricts the relevant actions to a given context. See SpeakDo AI Agents and Role profiles.
7. Hosting and availability
The service is hosted by OVH SAS, in France. The database is inaccessible from the public network.
8. Incident notification
For account data for which MargePro SASU is the data controller, MargePro commits to notifying the CNIL within 72 hours in accordance with Article 33 of the GDPR when the risk requires it. For your ERP's business data, processed by MargePro as a data processor, MargePro informs you without delay in the event of an incident: it is up to you, as the controller of that data, to assess the incident and, where applicable, notify the CNIL.
9. Report a vulnerability
Found a security vulnerability? Contact us at hello@speakdo.fr with the detail needed to reproduce it. Please do not publicly disclose a vulnerability before it has been fixed.