Privacy policy
The short version. Your music files, your library and what you listen to stay on your own devices. We never upload them, and there is no analytics in EyePlayer: no play tracking, no screen tracking, no crash reporting. The only thing our server holds is what a licence needs: if you make an account, your email address from Google sign-in, a name for each device, and records of trials and purchases. We do not sell data and we do not share it with advertising networks.
What stays on your device
The following exist only on your own phone or PC and are not uploaded to us:
- Your music files and the contents of your library. The app connects only to servers you configure (your own NAS, web folder, HTTP server or Drive), never uploading your files to us.
- What you listen to. Play counts, skips, ratings and when you last played something are recorded on the device so features like "most played" work. They are never sent to us.
- Your equaliser, playback and interface settings.
- The addresses and usernames of servers you add. Passwords are kept in the device's own protected storage.
Analytics: there aren't any
EyePlayer contains no analytics, no telemetry and no crash reporting. We do not record what you play, which screens you open, or how long you listen, and there is no third-party analytics or advertising SDK in either app. The apps talk to our server only to do the things listed below: sign in, check a licence, fetch a house ad on the free tier, and look for an update. Nothing else is sent.
If that ever changes, this policy and the Google Play data-safety listing will be updated before the change ships, the apps will point it out, and consent will be asked for where the law requires it.
What our server stores, and why
If you create an account (for the free trial, a purchase, or syncing your licence between phone and PC) our licensing server keeps:
| Data | Why |
|---|---|
| Your email address and a Google account identifier | Sign-in, and attaching purchases made on the web to your account |
| A name for each signed-in device (e.g. “Studio PC”) and its platform | So you can see which device holds your seat, and pick it out when moving the licence |
| A one-way salted hash of a device identifier (a “fingerprint hash”) | Fraud prevention: limiting free trials to one per device. The hash cannot be reversed into anything that identifies the device |
| Trial and licence status, with dates | Delivering what you're entitled to |
| Purchase records: which product, when, and the payment provider's reference | Delivering purchases, handling refunds, and tax law. We never see your card or bank details. Payment is handled entirely by Paddle |
| If ads are shown in the free tier: which ad was shown or tapped, and when | Capping how often you see one, and counting whether campaigns are seen. Ads are served from our own server; this data goes to no ad network |
The mailing list
We send you one kind of email on our own initiative, and only one: a receipt when you buy Premium, telling you how to switch it on. We also reply if you write to support. There is no marketing mail unless you ask for it by joining the mailing list below, and the two are kept apart.
If you join the mailing list on our home page, we store your email address and the date you joined. Nothing else, and it is not linked to any app account. It is used only to write to you about EyePlayer. Every mail includes an unsubscribe link, or write to support@eyeplayer.org and we will remove you.
Who else is involved
- Google operates the sign-in (we receive your email address and a Google account identifier; we never see your password). That is the only thing Google does for us. There is no in-app purchase in either app, so no billing runs through Google.
- Paddle is our merchant of record for purchases on the web and PC. Paddle handles payment details, invoices and VAT under its own privacy policy.
- Cloudflare hosts our server and database. Like any host, it processes connection metadata (such as IP addresses) to deliver traffic and block abuse.
- Brevo carries our outgoing email under its own privacy policy. That is the receipt we send when you buy Premium, and any reply we send you from support@eyeplayer.org. Brevo can see the address we write to and the text of the message.
Email you send to support@eyeplayer.org reaches us through Cloudflare's email routing and is kept on our own server so we can answer it. We delete support mail once the question is settled and there is no reason to keep it.
There is no analytics in the apps, and no analytics company receives anything about what you play. This website is the one exception, and it is worth being exact about it: eyeplayer.org uses Cloudflare Web Analytics, which counts page views so we know whether anyone is reading the site. It sets no cookies, does not follow you to other websites, and cannot be linked to your EyePlayer account or to anything you listen to. It runs on the website only. It is not in the phone app or the PC app, and it never will be without this policy saying so first.
House ads on the free tier are served from our own server on Cloudflare, not from an ad network, so no advertising company receives anything about you. If a third-party analytics or ad network is ever added to the apps, this policy and the Google Play data-safety listing will be updated first, and consent will be requested where the law requires it.
How long we keep things
- Account data is kept until you delete your account. Deletion takes effect immediately and the data is purged from the database within 7 days.
- Purchase records are kept after account deletion, because tax law requires sellers to retain transaction records (typically 6 years).
- The trial-lock hash: the salted device-fingerprint hash and the date a free trial was used are kept after account deletion. This is what prevents “delete account, repeat free trial” abuse. It contains no name, no email, and cannot be reversed into anything that identifies you or the device.
- Mailing list entries are kept until you unsubscribe.
Your rights and choices
You can use EyePlayer's player features without any account at all. If you have an account, you can delete it yourself from inside either app (see how to delete your account) or by emailing support@eyeplayer.org. Depending on where you live (including under the EU and UK GDPR), you may also have rights to access, correct, export or restrict the data above; write to the same address and we will honour them.
Children
EyePlayer is not directed at children and we do not knowingly collect data from anyone under 13 (or the higher age your country sets for consent).
Changes
EyePlayer will keep evolving, and this policy may be revised from time to time to keep up with new features, new platforms, or the law. If it changes materially, the date at the top changes and the apps will point it out before the change applies to you. The commitment at its heart is the part we don't intend to move: being upfront about what we collect, and never selling it or handing it to third-party ad networks.
Contact
EyePlayer is published by Philip Alexander Orr.
Privacy questions: support@eyeplayer.org