Back to OpenStation

OpenStation · Invite-only beta

Privacy

What data we use, why we use it and how to exercise your rights.

Version of 3 October 2026

Who is responsible?

Meutey Gabriel-Sandap, also known as MEUGS, in France, is responsible for OpenStation's data processing. Contact: meutey.sandap@gmail.com.

Data and purposes

  • Applications and invitations: email address, nickname, introduction, project and optional social links, to review your application and manage access to the beta. This processing responds to your request to access the service.
  • Account and station: email, identifier, password protected by the authentication service, profile, avatar, follows and posts, to provide the features you request. Your station profile, frequency, content and statistics are public; your login email and password are not.
  • Broadcasting and listening: transmitted audio, live titles and times, interactions and technical identifiers needed for the player and counters. Live broadcasts are not automatically recorded. To diagnose playback failures, the player reports an error code, the broadcast identifier and the browser family to OpenStation's technical logs, without sending audio, passwords or message content. To detect repeated incidents affecting several networks, the server also stores a keyed fingerprint of the network address, specific to each broadcast, and a minute timestamp. The raw address is not stored in this diagnostic table.
  • Security and moderation: reports, decisions, technical connection data and fingerprints used to limit abuse. Our legitimate interest is to protect the service and its users; some requests may also be subject to a legal obligation.

Required fields are needed for the requested feature: an application or account cannot be processed without an email address. Avoid including sensitive data in your introduction or reports. Data is neither sold nor used for targeted advertising.

Browser storage

Cookies and local storage support sign-in, language, the player, optional locking and the installed app. The site does not set advertising trackers. OpenStation's optional audience analytics are disabled for this beta.

You can clear these items in your browser. This may sign you out and reset your preferences. Private content and account pages are not stored in the app's offline cache.

Recipients and hosting

People authorised to administer OpenStation only access the data needed for their duties. Vercel hosts the site, Supabase manages accounts, the database and files, and Cloudflare transmits live broadcasts. The main database and application server are configured in Germany; delivery and some providers' technical processing may involve other countries, including the United States and Singapore.

Resend sends account emails, including account recovery messages. It processes the recipient's address, message content and delivery information. Sending is configured from Ireland; email data is stored in the United States.

GitHub Actions backs up the database and files daily. Data is processed temporarily on its servers, then the encrypted archive is retained in OpenStation's private repository. The decryption key is kept separately, outside GitHub. This processing may take place in the United States; see GitHub's privacy statement.

Providers offer data processing agreements and contractual safeguards for international transfers: Vercel, Supabase, Cloudflare and Resend. You may ask the publisher for details or a copy of the applicable safeguards.

Retention periods

  • Account, profile and station history: while you use your account, then deleted when you request account closure in settings. Follows and associated data are cleaned up with the account.
  • Audio files: while broadcasting in a loop; deleted when the broadcast stops. Avatars are replaced or deleted with the profile.
  • Applications and rejections: up to 12 months after their last update, unless you submit a new request.
  • Reports and moderation decisions: 12 months after a report is closed or a decision is made, unless separate retention is necessary for a dispute or legal obligation.
  • Technical data: playback failure fingerprints expire after one hour and are removed by the next health check (scheduled every five minutes); anti-abuse limits expire with their control window; old audience analytics events are deleted after 30 days. Provider logs follow the retention periods of the respective plans and are accessible only to authorised people.
  • Account emails: Resend retains messages and sending logs for 30 days on the current plan. Its backups persist for 7 days; after the Resend account is closed, remaining data is deleted within 90 days. Provider details.
  • Automatic backups: encrypted GitHub archives are kept for 3 days. They are used only to restore service after an incident.

When exceptional retention is necessary, access remains restricted and an end date is set according to the reason. Backups are encrypted and used only for incident recovery; erasure requests must also be respected when restoring a backup.

Your rights

You may request access, correction, erasure, restriction and, where applicable, portability of your data. You may object to processing based on legitimate interests on grounds relating to your situation.

Email meutey.sandap@gmail.com, stating your request and the account concerned. Proportionate identity verification may be requested if there is doubt. We respond within one month and inform you if a lawful extension is necessary. You may also lodge a complaint with the CNIL.