Draft to be reviewed by a lawyer. This text is not in force yet.
Privacy policy
Draft of 17 November 2026
Who processes your data
Eco2Net [address and contact to be completed] publishes Inbloom. For company accounts, the client company decides how its members use Inbloom: it is the controller, and we act on its behalf (see the data processing agreement). For the data of the website, accounts and invoicing, we are the controller.
What we process
- Account: first name, last name, e-mail address, the addresses of the linked Outlook mailboxes, your occupation if you give it, your preferences and signatures.
- Content: your conversations with the assistant, your requests, the drafts produced, the mails you hand to it, the attachments and files you add, your templates, categories and favourite contacts.
- Company: its name, licences, members, their roles and seats.
- Usage and security: the log of AI requests (date, type, cost), technical errors, the IP address and a device fingerprint (kept as an irreversible hash) to limit code attempts and free trials (three a day per place or per browser, one per address).
Why
To run Inbloom (writing, summarising, organising at your request), sign you in, manage your company's licences, protect accounts from abuse and follow the cost of the service. We do not sell your data or use it for advertising.
Where your data is
On a Google Cloud server in Paris (European Union): database, files and nightly backups. The publisher also keeps full copies of this server on a computer reserved for its administration [location and protection of these copies to be confirmed].
Artificial intelligence
For each task, Inbloom sends OpenAI, our AI provider, what the task needs: the mail concerned, the files you ticked, your request, your writing preferences, and your voice messages for their transcription. Requests are sent asking OpenAI not to keep them for reuse.
OpenAI processes this data in the United States and may keep it for a limited time to detect abuse, under its own terms [OpenAI terms, transfer outside the European Union and safeguards to be checked by the lawyer]. A company that chooses its own OpenAI key goes through its own contract with OpenAI.
How long
- Sign-in codes: 10 minutes at most, erased once used.
- Session: 7 days at most, closed after 24 hours without activity.
- Devices signed in to an account (hashed fingerprint, dates, last IP address): 90 days after their last use.
- A conversation you delete: erased for good after 30 days.
- Log of technical errors: 30 days.
- Server backups: the copies of the last nights, replaced as they go.
- Account and content: as long as the account exists. [period after a licence ends and after the account is deleted to be set]
- History of code attempts: [period to be set]
Who else has access
- Google Cloud, host.
- OpenAI, artificial intelligence provider.
- The service sending sign-in e-mails [to be completed].
- The payment provider, once online payment opens [to be completed].
- Your company's administrator sees its members, their seats, their usage and the devices signed in to their account (dates and last IP address); they do not read your conversations.
- One exception: the exchanges the assistant flags by itself (very vulgar language, frustration, a request it could not satisfy) are kept 90 days with your message and its reply, read by your company's administrators, and the publisher sees only how many there are, except for its own organisation and for accounts without a company.
Cookies
The site and Inbloom use one cookie only, your session's, needed to stay signed in. A random identifier kept in your browser is used to limit code attempts. No audience measurement or advertising tools.
Your rights
You may access your data, have it corrected or erased, ask for a copy, object to a processing or ask for it to be restricted, by writing to us [contact address to be completed]. You may also complain to your data protection authority (the CNIL in France). A conversation can be deleted at any time from Inbloom's Conversations tab. A client company can get its data as one file from its console, and ask for it to be deleted.