Privacy Policy
Last updated: October 14, 2026
This Privacy Policy explains what personal data TextDigo collects, how we use it, and the rights you have over it.
1. Data we collect
Account details (name, email, organisation), the conversations and contacts you process, and technical data such as log and usage information.
2. How we use data
To provide and secure the service, to support you, to bill you, and to improve the product. We do not sell your personal data.
3. Sharing
We share data only with the processors needed to run the service (e.g. messaging and infrastructure providers) under appropriate agreements. With your consent (the "Marketing" category of the cookie preferences), the pages you view on our site and some actions are also sent to Meta Platforms through the Meta pixel, to measure how effective our ads are. Meta then processes this data under its own privacy policy.
4. Shared WhatsApp deliverability registry
WhatsApp offers no way to check in advance whether a number can receive a message. To avoid sends that are bound to fail, which damage the reputation of every customer's lines, TextDigo maintains a technical deliverability registry shared across all organisations on the platform. For a given phone number it records only whether WhatsApp accepted or refused a delivery. It holds no sending organisation, no contact and no message content: it cannot reveal who ever wrote to a number. A refusal is only retained at the shared level once several independent organisations have observed it, and it becomes retryable again after a delay. Anything specific to a business relationship, such as a block or a marketing opt-out, stays confined to the sending line concerned and is never pooled. This processing relies on our legitimate interest in maintaining the delivery quality of the service.
5. Our team's access to your data
Answering a support request sometimes means looking at what you are looking at: a conversation that will not send, a badly imported contact, an unexpected automatic reply. We chose to frame that rather than leave it to our teams' discretion. By default our support can open your account to handle your request, and five rules apply without exception. Every access requires a written reason, which is shown to you as written. It lasts one hour at most, extendable once, and expires on its own: nobody has to remember to close it. You are notified every time, through an alert you cannot switch off. Everything consulted is logged, and that log is readable from your settings, refusals included. And you can take the access back at any moment, in one click. Our teams can never WRITE in your place: no sending a message, no editing a contact, no launching a campaign, no creating an API key in your name. Those gestures stay yours. If you would rather nothing be readable without your explicit agreement, one setting on your organisation enforces it: our support will then wait for one of your administrators to approve, request by request. TextDigo's management never reaches the content of your exchanges under either setting: it sees volumes and aggregates only. There is one narrow exception to whichever regime you chose: during an ongoing technical incident, emergency access can be opened with a second manager's authorisation, for one non-renewable hour. You are told immediately in that case, not asked. This processing rests on the performance of our contract with you and on our legitimate interest in keeping the service running.
6. Retention
We keep personal data for as long as your account is active or as needed to provide the service and meet legal obligations. Entries in the deliverability registry described above are deleted once they have not been observed for the applicable retention period.
7. Your rights
Depending on your location you may access, correct, export or delete your personal data. Contact us to exercise these rights.
8. Contact
For privacy requests, email [email protected].