Privacy policy.
What Vynl collects, why, for how long, and what you can do about it.
Draft for legal review. This text is an example. It does not bind anyone yet and will be replaced once a lawyer has reviewed it. Fields in [brackets] are still to be filled in.
1. Who is responsible
This policy covers the Vynl website, the Vynl listening app, the Creator Studio and the API behind them. The controller is [Company legal name], [legal form], [registered address], [country], registered under [registration number].
For anything about your data, write to [privacy contact email]. [EU representative, if one is required]
2. What we collect and why
Vynl is in beta. This is what the product does with personal data today. If the product changes, this table changes with it.
| Data | What | Why |
|---|---|---|
| Account | Email address, password, role (listener, creator, admin) and account status. The password is stored as a hash by our authentication provider, so Vynl cannot read it. | Create and secure your account. |
| Profile | A username, and optionally a display name, avatar, banner, bio, country and language, plus preferences such as explicit content and favorite genres. | Your identity on Vynl and personalization. |
| Activity | Playlists (public or private), library favorites, and the artists and users you follow. | Run the service. |
| Listening | Which track and artist, when, how many seconds were really played, where the play started (album, playlist, search), device type, app version, listening entitlement, and a country derived from your connection by our host. The IP address itself is not stored. | Count plays to pay artists, give artists aggregated audience statistics, and prevent fraud. |
| Playback checks | The position and state of the player about every 15 seconds while a track plays. | Verify that plays are real. |
| Fraud signals | Events and scores linked to an account or a play and, if enabled, a salted fingerprint of the IP address that changes every day. [Fingerprint not active at the moment] | Fraud prevention. |
| Creator content | For creators: the version and date of the terms accepted, the declared type of content, the rights confirmation, the primary genre, audio files, images, and every AI declaration with its history. | Publish music, pay creators, and keep a record of how AI was used. |
| Payments | Plan, status and billing period. Card details and the identity checks required for creator payouts are handled by our payment provider, not stored by Vynl. Not live during the beta. | Billing and payouts. |
| Consent records | Each yes or no you give, for which purpose, on which version of our texts, when, and from where. | Prove what you accepted. |
| Security log | When an administrator acts on an account, including opening a listening history. | Security and accountability. |
Legal basis for each purpose: [to be completed with counsel: contract, legitimate interest, consent or legal obligation].
3. What we do not do
- We do not store IP addresses, only a country.
- We do not locate you more precisely than a country.
- We do not use advertising cookies or third-party analytics.
- We do not sell your personal data.
- The listening history of an individual account is only opened by an authenticated administrator using two-factor authentication, and every opening is logged.
- When an account is deleted, its plays are detached from it.
4. Cookies
This website sets no cookies. As with any website, our hosting providers see technical connection data such as your IP address and browser in their server logs. The home page may also ask our API for the latest tracks.
The listening app and the Creator Studio only use strictly necessary cookies: the sign-in session and, where a notice is shown, a technical cookie that remembers which version of our texts you accepted. There are no advertising cookies.
5. Who receives your data
We use service providers to run Vynl. They only act on our instructions.
- Supabase: database, authentication, file storage and the emails sent for sign-in.
- Vercel: hosting of the website and the web apps.
- Render: hosting of the API.
- Stripe: payments and identity checks for creator payouts. [Upcoming, not live during the beta]
- An advertising partner: [to be chosen, only after the beta]
Hosting regions and the safeguards used when data leaves Switzerland or the EU: [to be documented for each provider]. Some information is public by design: your artist page and your public playlists can be seen by anyone.
6. How long we keep it
| Data | Kept for | Notes |
|---|---|---|
| Playback checks | [30 days] | Then deleted. |
| IP fingerprint | [30 days] | Then erased. |
| Plays | [to be set] | They are the proof of what is owed to artists. When an account is deleted they are detached from it. |
| Payments and accounting records | [10 years] | Accounting law. Not live yet. |
| Security log | [to be set] | It cannot be altered. |
| Consent records | While your account exists | [Whether proof is kept after deletion: to be decided] |
| Deleted accounts | Anonymized | For artists, the name, bio, images and country are removed and releases are archived. Audio files, covers, avatar and banner are deleted after [30 days] unless a legal hold applies. |
7. Your rights
You can ask to see your data, correct it, delete it, receive a copy of it, object to some uses of it, and withdraw a consent at any time.
Write to [privacy contact email]. We answer within [30 days]. [The Privacy and data page of the app will also let you export your data and delete your account.]
If you are not satisfied, you can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) or to the data protection authority of your country in the EU.
8. Age
Vynl is meant for people aged [16] or over.
9. Advertising
There is no advertising on Vynl today. Free accounts with ads are planned for after the beta. Before that, this policy will be updated, and personalized advertising will only be used with your prior consent, which you will be able to withdraw.
10. Security
Only our API reads and writes the database. Administrator access uses two-factor authentication, and sensitive actions are logged.
11. Changes to this policy
Each version of this text has a label. When a change matters, we will tell you and, where the law requires it, ask you to accept the new version.