Privacy Policy
This document explains what data OYRO collects, why, for how long, and what you can demand. It describes the product as it works, not an intention.
Who is responsible
The data controller is Jean Claude Volcy, a sole trader (French “entrepreneur individuel”, EI), registered at 55 rue Daniel Mayer, 37100 Tours (France), SIREN 820 283 984.
For any question or request about your data: contact@oyro.dev.
Three principles, before the details
- OYRO sells no data, shows no advertising, and shares nothing with advertisers.
- OYRO builds no advertising profile and uses no algorithmic ranking: what you see comes from the people you added, in time order.
- What you send is visible only to the people you choose. No private content is public, and no permanent address exists for a private file.
What OYRO collects, and why
| Data | Why |
|---|---|
| Email address or phone number | create your account and sign you back in (one-time code) |
| Date of birth | check that you are at least 16. It is never shown to anyone |
| Username, display name, bio, profile photo | make you recognisable to your friends |
| OYRO Code | let someone add you without searching by username |
| Friends, requests, blocks | operate the network of relationships |
| Photos, videos, messages, Moments | deliver them to the people you choose |
| Delivery and read state | tell you whether a message arrived and was read (can be turned off) |
| Screenshot events | warn the sender of a Glimpse, where the platform allows it |
| Device model, OS version, language, install identifier | send notifications in the right language to the right device |
| Notification token | reach your phone. It is readable by no one, not even you |
| Reports and moderation measures | handle abuse and tell you what concerns you |
| Technical counters (rate limits, logs) | prevent abuse and diagnose failures |
On what legal basis
- Performance of the contract: your account, conversations, Moments, notifications — without this data the service does not exist.
- Legitimate interest: security, abuse prevention, moderation of reports, rate limiting, failure diagnosis.
- Consent: notifications, which you can refuse at any time without losing the use of the app.
- Legal obligation: retention of certain items when a competent authority requires it.
For how long
These are the durations the server actually applies, not theoretical maximums. Deletions are carried out by scheduled server jobs, so they may happen up to twenty-four hours after the stated deadline.
| Data | Duration |
|---|---|
| Opened Glimpse | the media is deleted after viewing |
| Trace of an opened or expired Glimpse (the row in your list) | 24 hours |
| Glimpse never opened | 7 days |
| Moment | 24 hours |
| Message read, then conversation left | erased at once, unless someone kept it |
| Message never read | 7 days |
| Kept message | until the chosen deadline, 30 days at most |
| Trace of an erased message ("messages erased") | 24 hours |
| Media you kept in your Memory | kept as long as you keep it — deleted as soon as you forget it |
| Replaced profile photo | deleted on the next purge run |
| Reported content (moderation evidence) | 90 days at most |
| Technical metadata and logs | 30 days |
| Deleted account | permanently erased 14 days after your request |
Conversation messages are ephemeral. When you leave a thread, what you read there is erased — the text is removed from the database, not just from the screen. Your own messages go the same way once the other person leaves the thread in turn. Keeping something has to be asked for: a retention lasts from twelve hours to 30 days, it is visible on both sides, and it is renewable — nothing becomes permanent on its own.
Your Memory is the one thing that does not erase itself, and it only holds what you put there: media you captured yourself and chose to keep. A Glimpse or Moment you received cannot go in — you only keep what you authored. Those media stay in private storage, readable by you alone, until you remove them or delete your account. An account can hold 2000 of them at most.
How it is protected
- Private files live in closed storage: no public address exists for them.
- One exception, and it is deliberate: your profile photo is served from public storage, at an address nobody can guess. That is what lets it appear instantly in a list. Anyone holding that address can see the photo; nobody can find it without it.
- Every file read goes through an authorisation checked on the server and an address valid for a few seconds.
- Every table is protected by access rules in the database: the app does not decide what you may read, the server does.
- No notification carries a message’s text or a media file: only the type of event and an identifier.
- Error reports are scrubbed of content, tokens and file addresses before being sent.
- Traffic is encrypted in transit. OYRO does not yet offer end-to-end encryption: the server can technically access content, and does so only to deliver it and to handle a report.
Who else sees anything
Data is hosted with Supabase in the Paris, France region. The third parties below act for one specific reason, and are not allowed to use this data for anything else.
| Third party | Role and location |
|---|---|
| Supabase | database, file storage and authentication hosting — European Union (Paris) |
| Vercel | hosting of this website — United States and European Union |
| Resend | sending the service’s emails (sign-in codes, account-related messages) — Ireland (sending region) and United States |
The following third parties are required for functions not yet enabled in production; they will be at launch, and this list will be up to date before the corresponding function exists.
| Third party | Role and location |
|---|---|
| Expo | delivery of notifications to Apple and Google — United States |
| Apple | app distribution, iOS notifications, Sign in with Apple — United States and European Union |
| app distribution, Android notifications, Sign in with Google — European Union and United States | |
| Twilio | sending the sign-in code by SMS — United States |
| Sentry | crash and error reports, scrubbed of content and tokens — United States |
Some of these third parties are established outside the European Union. Transfers rely on the European Commission’s standard contractual clauses.
What you can demand
- Access your data and obtain a copy: Settings → Take my data produces a file immediately, without going through us.
- Correct it: your profile is editable at any time.
- Have it deleted: Settings → Delete my account. Deletion is permanent after the window to change your mind.
- Object to processing based on legitimate interest, or ask for it to be restricted.
- Withdraw your consent to notifications, with no consequence for anything else.
- Lodge a complaint with the CNIL (www.cnil.fr), the French data protection authority, if you believe your rights are not respected.
For any request the app cannot settle: contact@oyro.dev. We answer within one month.
Minors
OYRO is not available to people under 16. Date of birth is asked at sign-up and checked on the server; an account declared below the minimum age cannot be opened.
If we learn that an account belongs to someone below that age, it is closed and its data deleted. A parent or guardian may write to us to request that closure.
If this document changes
A substantive change is announced in the app before it takes effect. The date of the last revision appears at the bottom of this page.