Privacy policy
This English translation is provided for convenience only. The French version is the only legally binding one and prevails in case of any discrepancy: Politique de confidentialité.
Last updated: November 15, 2026.
Who is responsible
Software Family, SAS, 5 allée Valériane, 49100 Angers, France, publisher of Tavimi, is the controller of the processing described here. For any question, or to exercise your rights: contact@tavimi.com.
On this website (tavimi.com)
The website sets no cookies and uses no audience measurement tool and no third-party service: fonts and images are served from our own servers. Like any web server, it records in its technical logs the IP address, the page requested and the date of each visit, to keep the website secure and working properly.
When you write to us or book a meeting
If you write to contact@tavimi.com or book a slot from the Contact page, we receive your name, your email address, your message and, for a meeting, the slot you chose. We use them to reply to you and to prepare the meeting. Booking takes place on the Proton Calendar page, which only opens if you click the link.
In the app (app.tavimi.com)
We process:
- Your account: email address, display name, password (stored hashed), second authentication factor (authenticator app secret and encrypted backup codes, or passkeys).
- What you and your assistants write: organizations, spaces, notes, tasks, questions and answers, task logs, documentation, uploaded files, with their version history, the name of their author and the connection that wrote them.
- The audit log of each space: administrative actions (members, invitations, roles, connections authorized or revoked, deletions) and reads by assistants, reduced to identifiers, without the text of the content.
- Invitations: the invited email address and the space or organization concerned.
- Messages written to a contact from a space: the email is sent through Brevo, in your name, with your address for replies. All we keep of the message is one line in the space’s audit log (who sent it, to which address, when), never its subject or text.
- Your AI assistants’ connections: the client used, the authorized spaces, the dates of connection and renewal.
- Your API tokens, if you create any: their name, their first characters, their fingerprint (never the token itself), the spaces they open, and the dates of creation, expiry, last use and revocation.
- Addresses reported by Brevo as undeliverable (bounce, complaint, unsubscribe): the address, the type of report, its dates and the mail server’s response, so that no further invitation is sent to it.
- Your subscription, if you take the paid plan: company name, SIREN number, VAT number, billing address and billing email entered under “Facturation” (Billing), plan, number of people billed and subscription status. The payment itself takes place at Paddle: we never see your bank details.
- Technical logs: errors and requests reduced to their page type and result, without IP address or content of your spaces, to diagnose outages and protect the service.
Why, and on what legal basis
- Providing the service (account, spaces, invitations, connecting assistants): performance of the contract between us.
- Securing the service (two-factor authentication, rate limits, bot check at sign-up, logs): our legitimate interest in protecting your data and the app.
- Delivering messages written to a contact: performance of the contract for the sender; for the recipient, our legitimate interest in delivering the message a user addresses to them.
- Replying to your messages and meeting requests: steps you ask us to take before a possible contract, or our legitimate interest in replying to you.
- Billing the paid plan (subscription, invoices, VAT): performance of the contract, and our accounting and tax obligations.
- Emailing you to verify your address, reset your password or deliver an invitation: performance of the contract. We do not send marketing emails.
Your content is not sold, not used to train any AI model, and not read by us except at your request for support or where required by law.
With whom
- OVH SAS (Roubaix, France) hosts the website, the app, the database, uploaded files and logs, in France.
- Brevo (Sendinblue SAS, Paris, France) sends the app’s emails.
- Proton AG (Geneva, Switzerland) receives emails sent to contact@tavimi.com and meeting bookings (Proton Mail, Proton Calendar).
- Paddle.com Market Limited (London, United Kingdom), reseller of the paid plan, collects the payment, issues invoices and collects VAT. It receives what you enter under “Facturation” (Billing) (company name, SIREN number, VAT number, billing address and billing email), the number of people billed and your account identifier, which links the subscription to your account. It processes your payment data as a controller, under its own privacy policy.
- Cloudflare, Inc. (San Francisco, United States) provides the bot check on the sign-up page (Turnstile). Its script, loaded on that page only, receives technical signals from your browser (IP address, TLS fingerprint, User-Agent header) and tells us whether the sign-up comes from a human. Cloudflare acts as a processor for this; it also reuses these signals, as a controller, to improve its bot detection, under its own privacy policy.
Your AI assistants. Tavimi sends nothing to an AI provider on its own. When you connect an assistant (Claude, or another MCP client), it is the assistant that reads and writes in the spaces you have opened to it: what it reads is then processed by the assistant’s publisher, under the terms you have accepted with them. You choose the spaces opened to each connection and can cut it off at any time from the “Mes connexions” (My connections) page.
Apart from Proton, established in Switzerland, and Paddle, established in the United Kingdom, two countries whose level of data protection the European Commission recognizes as adequate, and Cloudflare, established in the United States and certified under the EU-U.S. Data Privacy Framework, which an adequacy decision of the Commission covers, no data is transferred outside the European Union by us.
How long
- Account and content: as long as the account exists. When it is deleted, they are erased after 30 days, during which the deletion can be canceled; backups containing them disappear no later than 30 days after that.
- Invoices: kept by Paddle, which issues them, for the period required by its accounting and tax obligations.
- Messages and meetings: three years after our last exchange, unless you become a customer (they then follow your account).
- Deleted spaces and organizations: erased 30 days after deletion, during which they can be restored.
- Invitations: a link is valid for seven days; an accepted, revoked or expired invitation is erased three months later.
- Accounts never activated (address never verified, no sign-in): erased 7 days after sign-up.
- Assistant applications registered without ever obtaining a connection: erased after one day.
- Assistant reads in the audit log: one year.
- Addresses reported by Brevo: twelve months after the last report.
- Technical logs of the website and the app: 12 months at most.
Your rights
You can access your data, correct it, erase it, request a copy in a reusable format, object to processing based on our legitimate interest or request its restriction. Your display name can be changed under “Mon compte” (My account), where you can also delete your account: it is deactivated immediately, the deletion can be canceled for 30 days, and then your spaces and their content are erased. For anything else, write tocontact@tavimi.com. We reply within one month.
If you believe your rights are not being respected, you can lodge a complaint with the CNIL (Commission nationale de l’informatique et des libertés, the French data protection authority,www.cnil.fr).
Cookies
The website sets none. The app only uses cookies that are strictly necessary for it to work: the session that keeps you signed in, the protection of forms against cross-site request forgery and the language you chose (one year). On the sign-up page, Cloudflare’s bot check may set its own technical cookies, which keep proof that the check was passed. None is used for advertising or audience measurement, and therefore they do not require consent.
Security
Traffic is encrypted (HTTPS). Two-factor authentication is mandatory for everyone. Passwords are hashed, the authenticator app secret and backup codes are encrypted in the database, and the assistants’ connection tokens are stored hashed.