Privacy policy
What Daily Briefs knows about you, why it knows it, and what you can ask us to do with it.
Last updated Sep 2, 2026
Who is responsible
The publisher of this site, ineoo, decides what is collected here and why. Anything on this page reaches a person at the address below.
What is collected
Only what the service needs to run. There is no profile, nothing inferred about you, and nothing bought from anyone:
- Your account: a name, an email address, and a hashed password. Nothing else is asked for.
- Your topics: which ones you follow, and since when.
- Your Telegram link, if you make one: the chat identifier, the language of your captions, and the wording you agreed to with its date — that record is what proves the messages were asked for.
- Delivery records: which brief went to you and whether it arrived, so a failed send can be retried rather than lost or repeated.
Why, and on what basis
Each purpose stands on its own legal basis under the GDPR:
- Running your account and delivering the briefs you asked for — performance of the contract between us.
- Writing to you on Telegram — your consent, given by pairing, withdrawn by unpairing or by blocking the bot.
- Transactional email, to verify an address or reset a password — performance of the contract.
- Rate limits and abuse protection, which hold an address and an IP for at most an hour — our legitimate interest in keeping the service standing.
What the models never see
A brief is written for a topic, not for a reader. The language model receives press articles and returns a summary; the speech model receives that summary and returns audio. Neither is given your name, your address, your topics or anything else about you — the pipeline that calls them runs to completion before anyone is picked to receive the result.
Who else processes it
Four providers, each for one job and nothing beyond it:
- OpenAI, in the United States, for the summary and the audio — press articles only, never your data.
- Resend, for transactional email and for the messages sent from the contact form. It receives the address it has to write to.
- Telegram, for delivery. It receives your chat identifier and the brief.
- Scaleway, in France, which hosts the servers and the database.
How long it is kept
Your account and your topics last as long as the account does. Unpairing Telegram removes the link and stops the delivery on the spot; the consent record stays while the account exists, since it is the evidence that the messages were wanted. Ask for the account to be closed and everything above is deleted within thirty days. Rate-limit counters expire on their own within the hour.
Cookies
Two, both strictly necessary, neither shared with anyone:
- A session cookie, set when you sign in, which is what keeps you signed in.
- A cookie holding the language you picked, so the site opens in it next time.
There is no analytics, no audience measurement and no third-party script on this site. Nothing here asks for your consent to cookies because nothing here tracks you.
Your rights
Under the GDPR you can ask for:
- A copy of what is held about you, and the same in a portable form.
- A correction — your name you can also change yourself, from your profile.
- Erasure, which closes the account and takes everything attached to it with it.
- An objection to a processing, or the withdrawal of your consent to Telegram, which unpairing does immediately from your profile.
There is no self-service deletion button yet. Write to the address below and it is done by hand, within thirty days. contact@dailybriefs.fr
Complaints
If our answer does not satisfy you, you can lodge a complaint with the CNIL, the French data protection authority, at cnil.fr.
Changes
This policy moves when the service does. The date at the top of this page says when it last did.