Privacy Policy
Last updated 8 November 2026
I'm Samir. I make Vein on my own, under the name OneCubeStudio, and I wrote this myself. It's longer than I'd like, because the honest version has to name everything.
Vein is a music player for files you already have. Your songs, playlists, ratings, notes and listening history sit on your phone. They stay there unless you sign in and use a feature that needs them somewhere else, and signing in is optional. If you never do, every section below about accounts and friends is simply not about you. Besides the lookups described under Things the app looks up online, three technical things leave an Android phone even if you never sign in: crash reports, Google Cast's search for speakers and TVs, and a notification token. Each is described below.
What stays on your phone
All of this lives on the device only, and goes when you uninstall:
- Your music files, plus the tags, artwork and lyrics inside them
- Playlists, likes, pins, ratings, private notes, the never-play list
- Listening history, play counts, statistics
- Settings, themes, the equalizer
- If you turn it on in Library tools, its history: which songs a repair, a cover search, a tag fill or a duplicate delete changed, and what it did to each. It is never uploaded, synced or backed up, and Clear history there removes it.
In the web app (web.veinmusic.app) the music folder or files you pick are read inside your browser and never uploaded. The tags and covers read from them, and the list of folders you picked, are kept in the browser's own storage for that site, and go when you remove a folder in Music folders or clear the site's data.
Two things copy some of it elsewhere. Settings → Sync keeps a copy of your playlists, likes, ratings, notes, listening history and statistics (never your songs) in the Vein folder in your own Google Drive, or in the Drive of another Google account if you pick one for backups, where I can't read it. Once you are signed in and have allowed Drive, and Vein has looked for a copy already there, that copy updates by itself: a couple of minutes after a change, when you leave the app, and every few hours. Turn off Sync automatically there and it only happens when you tap Sync. Backup & restore writes the same thing to a file you choose where to send, only when you tap it.
If you sign in
Signing in goes through Firebase Authentication, with Google Sign-In or Sign in with Apple, whichever you choose, on any device. With Google, what I get is your email address, your display name, your profile photo and a user ID. With Apple, what I get is a user ID Apple makes for Vein, an email address (a private relay address Apple makes, which forwards to yours, if you choose to hide your email) and your name, which Apple shares only the first time you sign in, and only if you let it. Your Google or Apple password never comes anywhere near me.
You can add the other way to the same account in Settings, Account (Link Apple, Link Google), so either one signs you in. If your account signs in with Apple only, Vein keeps your songs and backups in the Google Drive of a Google account you pick for that alone (Connect Google Drive); it is not used to sign you in. On Windows and Linux, Apple's sign-in page in your browser hands its answer back to the app through a small Vein server function, which passes it straight to your computer and keeps nothing.
After that, these things live on Firebase under your account:
- Your profile. The handle, display name, status, bio and avatar you picked. Any signed-in Vein user can see it, and the playlists you marked as shared.
- Playlists you shared. Only the ones you marked as shared. The rest never leave your phone.
- Friends. Who you're connected to, pending requests, and the people you blocked (the block list is private to you; nobody is told).
- Presence. What you're playing right now, if your sharing setting allows it, and only to whoever that setting names.
- Listening summaries. Your top songs and artists, your streak and your weekly listening minutes. Shared with friends or everyone according to your history setting; set it to no one and they are stored under your account but shown to nobody.
- Your devices. Each signed-in device publishes its name, its operating system and what it is playing, so your other devices can pick up where it left off. Visible only to your own account, and blank while private listening is on.
- Things between you and your friends. Sync requests, songs handed to one another, reactions, and playlist activity.
- Which songs you have, if you switch it on. “Let friends see which songs I have” is off unless you turn it on. When it is on, your account keeps a list of codes made from each song's title and artist, so your friends' apps can show that you have a song they are missing and let them ask you for it. It is not a list of names or files, but a friend's app can check whether you have a particular song. Only your accepted friends can read it, never someone you have blocked or who has blocked you. It is deleted when you turn the switch off, when you sign out, when you delete your account, and on its own if your app has not updated it for 45 days, and it is in your data download. If your phone is offline when you sign out, it is deleted the next time you sign in on that phone, and friends cannot read it once those 45 days are up.
- Listen Together. While you are in a session, the room holds the song playing, the chat, the requests, party mode’s rounds and scores (your pick in a round is for you and the host to see), and a hashed list of which songs you own (so the host knows what you can play along with — not the files, not the names). All of it is deleted when the session ends.
- Asking to listen along. While a friend can see you playing in Vein, they can ask to join you. The request holds who asked and when, nothing else. It reaches your phone as a notification with their name and @handle, and it runs out after 10 minutes. If you accept, a Listen Together session starts with them in it. Who may ask (friends, or nobody) is kept with your presence so their app knows whether to offer it, and you change it in Settings under “Who can ask to listen along”. Old requests are deleted once they have run out, and all of them when you delete your account.
- Listen-along links. While you host a session,
you can copy a link (
veinmusic.app/l/and a random code) to post in a chat. It holds that it is yours, when it was made, until when it works (a day at most), and whether its page shows the song playing. The page never shows your name or anything else about you. If you choose to show the song, anyone who sees the link sees that song. In the app only your friends can use it, and it leads to the same request as asking to listen along, so your setting and your blocks still apply. It stops working when the session ends, when you stop it, or after a day, and it is deleted when you delete your account. - Reports you file about somebody. Kept until I have looked at them, and not deletable by you, so a complaint can't be made to disappear. A report says what kind it is, gives your user ID and theirs, and quotes what is being reported: the chat message, or their name, handle and bio. It stays on my servers, where I read it, and is not sent anywhere else.
- “Tell the developers” reports. When something in the app fails, Vein offers a button that sends me what was tried, what went wrong, the app's version and your device's system, and, when it was about a song, that song's title, artist, album, format and size. You can also open it yourself, from Settings and, on a Mac, the Help menu, to report a bug or send an idea, and what you write goes with it. It can also send a screenshot of the screen you were on: the app shows it to you first, and it goes only if it is still attached when you tap Send. The app shows you all of it before you send. When the failure was about a song on your device, the same tap also sends me the song file itself (up to 50 MB); a song from Drive or a server sends only its id, never a copy. The song file is sent only when you tap that button, and it is deleted after 30 days, with the report. Nobody can read these from the app, you included; I read them in the Firebase console. A private GitHub issue, where Vein's code is kept, notes that a report arrived with only a reference, whether it is a bug or an idea, the app's version, the platform and the kind of error, never what you wrote or anything that identifies you. Reports and ideas are also read by an AI assistant (Claude, by Anthropic) working for Vein to find and fix bugs, and they are still deleted after 30 days. Deleting your account deletes them too.
- Telegram, if you link it: your Telegram user ID, chat ID and username, until you unlink.
- Notification tokens. So your phone can be told about a friend request, a friend asking to listen along, or a change to a shared playlist.
If you turn on Web profile in Settings, your profile
— name, handle, status, bio, avatar, the names of your shared
playlists, and your top songs if history sharing is set to everyone
— becomes a public page at
veinmusic.app/u/your-handle that anyone can open. Turn
it off and the page disappears.
You can turn any of it off in the app, and you can delete all of it. See Deleting your data.
Songs you back up
Backing a song up puts it into a folder called “Vein” in your own Google Drive, on your own storage, still yours. All Vein keeps on my side is a note of the title, artist, length, which file it is, and which file holds its cover. Not the audio.
Vein asks Google for one permission there, called
drive.file. It covers files this app created and nothing
else. Vein can't see or list the rest of your Drive: not your documents,
not your photos, not music you put there yourself.
Songs backed up by an older version are still sitting in Firebase Cloud Storage, so they keep working. Delete any of them from Settings → your account → cloud library.
Songs that pass through my servers
Three features copy an audio file to Firebase Cloud Storage for a while. None of them happen on their own:
- Listen Together. While you host a session, the song playing is copied up so that a member who does not have it can still hear it. It is replaced when the song changes and gone when the session ends. A party mode round sends at most 16 seconds of the host’s song, cut into one short sound file per step with no title or tags, and members get each file only when its step is played. They are gone when the party or the session ends.
- Sending a song to a friend who asked for it. A copy waits for seven days, readable only by that friend, then it is deleted.
- Telegram. An audio file you send to the Vein bot waits up to seven days for you to save it, then it is deleted.
Things the app looks up online
A few features ask the internet a question. Those requests carry a song title, an artist name or whatever you typed, plus your IP address, which is unavoidable. Except where it says otherwise below, they don't carry your name or your account.
- MusicBrainz fills in album, year, composer, genre and language tags that are missing.
- LRCLIB finds lyrics — automatically for each song you play, unless you turn Auto-import off in Settings.
- Deezer provides the charts, artist pages, thirty-second previews, suggestions, and album-art lookups (which send a song's title and artist). Importing a playlist from a Deezer link asks Deezer for that playlist, from your phone. The suggestions on Home send the names of your top artists; Settings → Suggestions from the web turns that off. In the web app these Deezer requests go through Vein's own server (a Firebase Cloud Function), as a browser cannot ask Deezer itself. They are made with your signed-in account; the server keeps Deezer's answers for up to six hours, without your account. Google's request logs for that server keep each request's address, which includes your search words, with your IP address and the time, for 30 days.
- AcoustID identifies a song from a fingerprint of its audio when you ask it to.
- radio-browser.info is the station directory. Playing a station tells it that station got played, which is how the popularity list works. It isn't told who played it.
- Podcast searches go through Vein's own server (a Firebase Cloud Function) to the Podcast Index directory, so its key stays off your phone. That request is made with your signed-in account, and Google logs the caller's IP address; the words you searched are not stored. Apple's directory answers the rest, with the words you typed and nothing else.
- Importing a playlist from a YouTube or YouTube Music link goes through Vein's own server (a Firebase Cloud Function), which uses YouTube API Services with Vein's key, so the key stays off your phone. That request is made with your signed-in account; the server passes the playlist and video IDs to YouTube and keeps nothing, and Google logs the caller's IP address. Each video's ID, link and length, and its title as YouTube wrote it, stay on your phone, are checked with YouTube again before they are 30 days old, are deleted if they cannot be, and are never in a backup. The song title and artist Vein reads from them stay with the playlist, like any other song name. YouTube's handling is covered by the Google Privacy Policy. Playlist files you import stay on your phone.
- Radio stations, preview clips, podcast feeds and episodes stream straight from whoever hosts them, so those hosts see the request the same way a browser would. Downloaded episodes are kept on your phone only. In the web app, a podcast feed or an episode's chapters the browser cannot read from their host are fetched by Vein's own server instead, with your signed-in account; the server keeps a copy of a feed for up to an hour, and of chapters for up to two hours, without your account. Google's request logs for that server keep the address asked for, with your IP address and the time, for 30 days. In the web app, a cover, podcast picture, station icon or profile photo the browser cannot load from its host is fetched by Vein's own server instead, with your signed-in account; the server keeps a copy of that picture for up to two hours, without your account. Google's request logs for that server keep the picture's address, with your IP address and the time, for 30 days. In the web app, to list only the stations your browser can play, Vein briefly opens each listed station's https stream address when you open Radio (not Home), so those stations see your IP address, as when you play one.
- A Subsonic or Navidrome server, if you add your own: your username and a hashed password go to that server with every request. Use an https address.
- A Jellyfin server, if you add your own: your username and password go to that server once, to sign in, and the password is not kept. After that Vein uses the access token the server issues, which is stored with the server's address and your username in your device's keystore. The server lists this device among its sessions, under a random id made at sign-in, with the app's version and the device's operating system. While you play a song from it, Vein tells the server which song, how far into it you are and when you pause or stop, as Jellyfin's own apps do, so its play counts stay right; private listening sends none of this. Disconnecting asks the server to sign that token out. Use an https address.
- Theme fonts. A Google font chosen for a theme is downloaded by your device from GitHub (raw.githubusercontent.com, where Google publishes its fonts) the first time a theme needs it, so GitHub sees your IP address then, and the file is kept on your device. A font file you import yourself stays on your device, apart from your own backups, and a theme file you export carries it, where the font's licence allows, only to wherever you send that file.
If something in Vein goes wrong, whether the app crashes or carries on, a technical report goes to me through Firebase Crashlytics: what went wrong in the code, the device model and OS version. It never includes your songs themselves, your name or your listening history. Now and then an error's details name a file on your device, such as a song's file name. This is on by default because it is how broken releases get found and fixed, and Settings has a switch that turns it off.
On Android, Google Cast starts with Vein, signed in or not, and looks for speakers and TVs on your Wi-Fi so the Cast button can show when there is one. Finding and talking to Cast devices is done by Google Play services, which Google says collects diagnostic and usage data about Cast, whether or not you cast anything. Choose a speaker or TV and it is sent the song's title, artist, album and cover, and plays the audio from your phone over your own Wi-Fi. Songs from a server or from Drive pass through your phone on the way, so the device is never given your server's address or your sign-in.
On Android, Firebase Cloud Messaging also gives the phone a notification token when Vein starts, signed in or not: the address Google delivers Vein's notifications to. It is kept under your account only once you sign in.
These only happen if you set them up:
- ListenBrainz or Last.fm. Connect one and switch scrobbling on, and the songs you play get submitted to that account. Off until you do both.
- Discord, on Windows and Linux (and on a Mac once Vein can reach Discord there). Off until you turn it on. While it is on, the song's title, artist, album, a link to its cover and where you are in it are shared with Discord, through the Discord app on your computer, and shown on your Discord profile. To find a cover for a song that has none, Vein may look its title and artist up on Deezer; no file is uploaded. With Hide song names on, Discord is only told that you are listening on Vein.
Private listening
There's a Private listening switch in Settings that pauses the lot. While it's on, nothing goes into your history, nothing reaches your friends or your other devices, nothing gets scrobbled.
What I don't do
- No ads, and no advertising identifiers.
- No analytics of my own. Google's Cast library collects some diagnostic and usage data, and crash reports go through Firebase, as described above.
- Nothing sold, nothing handed to data brokers.
- Crash reporting can be switched off in Settings.
Children
Vein isn't aimed at children under 13, and I don't knowingly collect anything from them.
Deleting your data
In the app: Settings, then Delete account. That removes your profile and handle, the playlists you shared, your friendships on both sides, your presence, summaries and devices, your notification tokens, every file of yours on my servers, and the account itself. Permanently.
It also clears what Vein put in your Google Drive. Every song you uploaded with Vein, and your settings and library backup, are deleted for good: from your own Drive and, if you picked a different Google account for backups, from that account's Drive too. The Vein folder itself goes to Drive's trash once nothing is left in it. If something else is still inside, such as another Vein account's songs or a file you put there yourself, the folder stays with it. If Vein can't reach a Drive at that moment (no connection, or Drive access not allowed), what's in it stays, and you can delete it in Drive yourself.
If your account signs in with Apple, deleting it first asks you to confirm with Apple again, and on an iPhone or Android phone Vein then asks Apple to disconnect it from your Apple ID before anything else is deleted. You can also remove Vein yourself at any time in your Apple ID settings (Sign in with Apple).
A few things stay, and here is why:
- Reports — the ones you filed and the ones filed about you — so that abuse can't be erased by deleting the account. (Not “Tell the developers” reports, which go with it.)
- What you left in a friend's Listen Together room that is still open: your messages, and any requests and votes from before you left it. They go when that room ends.
- Things that are other people's but name you: a block list you are on; songs you added to a friend's collaborative playlist, with your name on them, and your place among its collaborators, until that friend changes them; and songs a friend sent you, which are deleted after seven days like any other. Copies of what you sent are deleted from your friends' notification lists, but a notification already shown on a friend's phone stays there.
- Crash reports already sent, which Firebase keeps for 90 days and which don't name you.
It doesn't touch anything on your phone. To clear that too, uninstall Vein or wipe its storage in Android settings.
Locked out of the app? Email me and I'll delete it for you, everything above included, except what's in your Google Drive, which only you can reach: open Drive and delete the folder named Vein, or just the files you want gone. First I send a one-time code to the address the account signs in with, in a new email of mine, not a reply to yours, and I delete the account only once that code comes back to me. Without it nothing is deleted, so nobody can have your account deleted by writing in your name. There's also a page about this.
For a copy of everything my servers keep for your account, go to Settings, then Download your data, which saves it as one file; if you're locked out, email me from the address the account uses and I'll send it to you.
How long I keep it
Until you delete it, with four exceptions: songs handed to a friend and files sent through Telegram are deleted after seven days, “Tell the developers” reports and the songs sent with them after 30, crash reports after 90, and reports stay as described above.
Feedback you email me, from veinmusic.app/feedback or any other way, holds your email address and what you wrote. I delete it 12 months after our conversation ends, or sooner if you ask.
Where it's kept
The account side (profile, shared playlists, friendships, presence, the files above) is on Google Firebase: Authentication, Firestore, Cloud Storage, Cloud Functions and Cloud Messaging. Google may process that outside your country. Your songs are in your own Google Drive, under your own Google account.
In a web browser (web.veinmusic.app), you sign in through Apple's or Google's sign-in window, run by Firebase; Google's also asks to let Vein use the Vein folder in your Google Drive. The browser then keeps, in its own storage for this site, what the app keeps on a phone: your sign-in, a copy of your account's data so it opens quickly, and Google Drive's permission, which lasts an hour. Signing out deletes the browser's copies of your account's data and of the Drive permission, and the songs saved ahead for playing (with another Vein tab still open, the account's data goes the next time the site opens). You can withdraw Vein's Drive access entirely in your Google account's settings.
The web app is a beta. Like any website, the server that sends it to you (Google's Firebase Hosting) sees your IP address and browser with each request. Each time it starts, your browser fetches Google's Firebase code from www.gstatic.com and fonts from Google Fonts (on Google's gstatic.com), including letters Vein does not carry itself, such as Chinese, Japanese or emoji, so Google sees your IP address then too. The browser keeps a copy of the app's files and of those Google files in its storage for this site, so the app also opens without a connection; clearing the site's data removes them. Now and then the app asks the site which version it serves, to offer a reload when there is a new one, and that request carries nothing about you. No crash reports are sent from the web app. If you connect a Jellyfin or Subsonic server or ListenBrainz in the browser, what Vein keeps to stay signed in to it is kept in the browser's storage for this site, scrambled with a key kept beside it: that keeps it from being read at a glance, but is not as strong as a phone's keystore. Disconnecting there, or clearing the site's data, removes it.
If this changes
The date at the top changes and the app's release notes mention it.
Getting hold of me
Samir, OneCubeStudio. samirabilhasanli@gmail.com