Privacy policy
What Oyez keeps, and what it doesn’t
Following channels takes no name, no e-mail, no phone number. This page says what is stored all the same for the app to work, why, for how long, and how to erase it.
Last updated: 11 October 2026 · Version française. If the two versions differ, the French one prevails.
In short
- You follow channels: Oyez only knows a random identifier, your devices and your subscriptions. Nothing that tells who you are.
- You post for an organisation: we have your e-mail address to sign you in, and what you post is public.
- No ads, no selling of data, no audience tracking, in the app or on this site.
- Places you visited stay on your phone, and the server forgets your finished stays.
- Everything is erased in one tap: Settings › “Delete my data”.
Who is responsible
The data controller is [to be completed: name or company name, legal form, address, SIRET], publisher of Oyez. For any question about your data: contact@oyez.info.
If you follow channels
What is stored on our servers
- An anonymous profile: a random identifier, the time of your daily digest, your time zone, and the date of your last visit (to erase inactive profiles).
- Your devices: the kind (iPhone, Android, browser), the language, and the notification token used to send you notifications.
- Your subscriptions: the channels you follow, the notification mode you chose, your favourites, the teams you follow during a tournament, the end date of a stay you enter, and what you have already read.
- Two secrets only you hold: the sync code (to get your channels back on another phone; we only keep a fingerprint of it) and the secret address of your calendar, if you use it. Both can be renewed in the settings.
Organisations see how many people follow their channel, never who.
What stays on your phone
The latest news of your channels (to open them offline), your settings and your “Places visited”. They never leave the device and are gone when you uninstall the app.
The camera and notifications
The camera is only used to read QR codes, and the image is analysed on the phone, never sent. Notifications are only on if you allow them.
What we never collect
Name, e-mail, phone number, contacts, photos, GPS location, advertising identifier. When you call or write to an organisation from its channel, the exchange happens outside the app, with your phone or your messaging app: Oyez sees nothing of it.
Reports and confirmations
If you report a publication, we keep the reason and any comment, linked to your anonymous profile to avoid duplicate reports. Don’t put personal data in it. If you confirm an organisation on site (“Confirmed by its members” badge), the confirmation is linked to your anonymous profile, once per organisation.
If you post for an organisation
- Your account: e-mail address, name if you give one, the organisations and channels you have rights on, date of last sign-in. You sign in with a link sent by e-mail, valid for 20 minutes: no password.
- What you post: the organisation’s name and logo, address, opening hours, contacts, schedule, publications, PDF documents. All of it is public to whoever has the channel’s code. Don’t put other people’s personal data in it; the contacts shown are chosen channel by channel.
- A linked calendar: if you link a Google or Outlook calendar, Oyez gets read-only access to the chosen calendar, stored encrypted, and only reads its events to keep the channel’s schedule up to date. The access is deleted when you unlink the calendar; you can also revoke it from your Google or Microsoft account. An iCal address is stored encrypted the same way.
- Organisations that pay (pools): name, address, SIRET, Chorus Pro service code and purchase order, for invoices.
The use of data received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: it only serves to show the channel’s schedule, is neither sold nor used for advertising, and is read by no one.
Why, and on what basis
| Purpose | Legal basis |
|---|---|
| Running the app: subscriptions, notifications, digests, schedule, sync between phones | Performance of the service you ask for |
| Editors’ sign-in, managing organisations and channels, calendar linking | Performance of the service |
| Security and fighting abuse: limits on code attempts and notifications, reports, community badge | Legitimate interest (protecting members and organisations) |
| Invoicing organisations | Legal obligation |
For how long
| Data | Kept |
|---|---|
| Anonymous profile, devices and subscriptions | Until “Delete my data”, or 12 months without opening the app |
| Finished stay (campsite, resort…) | Asleep at its end date, or after 7 days without opening it; deleted from the server 30 days later |
| Report | As long as it takes to handle it, then [to be specified]; it stays even if its author erases their data |
| Editor account | Until “Delete my account”, in the app’s editor space |
| Sign-in links | 20 minutes, then erased |
| Invoices | 10 years (accounting obligation) |
| Server logs (IP address, date, page requested) | [to be specified, 6 months at most] |
Who else is involved
- OVHcloud (France) hosts the servers and the database, in France.
- Google Firebase delivers notifications to phones and browsers. It only receives the device’s notification token and the notification’s text, never your identity. Google may process this data outside the European Union, under the EU–US Data Privacy Framework and standard contractual clauses.
- Apple and Google deliver notifications on iPhone and Android, and distribute the app; their own rules apply to your store account.
- [to be specified: e-mail provider] sends sign-in links to editors.
- Google and Microsoft, only if an editor links their calendar, as described above.
We neither sell nor rent any data, and share it with no one else, unless the law requires it.
Cookies and trackers
This site sets no cookie and does not measure its audience. The app has no ads, no tracker and no audience measurement; what it keeps on the phone only serves to run it. Editors signed in to the web version stay signed in thanks to a token stored in the browser.
Children
Oyez is used a lot by parents, and often talks about children: that is why there is no account, no photo and no chat. A publication must hold no personal data and no photo of anyone; the only images are the organisation’s logo and pictograms.
Security
Exchanges are encrypted (HTTPS). Secrets (device identifiers, sync code, sign-in links) are only stored as fingerprints; calendar access is encrypted. Code attempts are limited per device and per IP address.
Your rights
You can access your data, correct it, erase it, object to its processing or restrict it, and ask for a copy.
- You follow channels: since we don’t know who you are, the simplest is to act in the app. Settings › “Delete my data” deletes your profile, your devices and your subscriptions from our servers; unsubscribing from a channel deletes that subscription. For any other request, write to us with your sync code, the only way to find your profile.
- You post: “Delete my account”, in the app’s editor space, deletes your account; an organisation you were the only admin of is then no longer shown. For any other request, write to contact@oyez.info from your account’s address.
We answer within one month. If you think your rights are not respected, you can complain to the French data protection authority, the CNIL.
Changes
If this policy changes, the date at the top of the page changes too. A significant change will be announced in the app.