Private music sharing — control who hears your music before it's ready for the world
Share unreleased music privately with full control over who hears it. TYFRA Vault lets you set expiry dates, restrict downloads, and track exactly who listened — without a public link.
Unreleased music is commercially valuable partly because it is unreleased. A demo that leaks before its release window, a stem pack shared too broadly, a work-in-progress that ends up on social media before the announcement — these are not hypothetical risks for working musicians. They happen regularly, and the consequences range from an annoying conversation to a lost sync opportunity or a ruined release campaign.
Private music sharing is not just about keeping files confidential. It is about controlling who has access, for how long, and what they can do with what they hear. This page covers how private sharing works in practice, what controls are actually necessary, and how TYFRA Vault handles the full scope of it. Related: secure audio file sharing, share music privately (sharing & storage guides), and the Vault hub.
What private music sharing actually requires
"Private" in the context of music sharing means different things in different situations.
Private from the public. An unreleased track that should not be publicly discoverable. This is the baseline — the file should not appear in search results, public playlists, or anywhere a stranger could find it without being given a link.
Private from the wrong collaborators. A project with multiple stakeholders where not everyone needs access to everything — the mix engineer does not need to see the split documentation, the featured artist does not need access to the stems.
Private from forward distribution. A track shared for listening and feedback should not be redistributable — the recipient should not be able to share the file with people you have not approved.
Private for a limited time. A pre-release share sent to radio stations four weeks before release should stop being accessible after the release date, so the pre-release version does not remain in circulation indefinitely.
A private sharing system that handles all of these scenarios requires more than a password-protected folder.
Why public cloud storage links are not private sharing
When most musicians share music "privately," they share a Google Drive link set to "anyone with the link" or a Dropbox shared folder with the collaborator added by email. This is a significant reduction in public exposure, but it is not genuinely private sharing.
"Anyone with the link" means anyone. A link forwarded to a third party — intentionally or accidentally — gives that person full access. There is no notification when the link is forwarded and no mechanism to revoke access for one recipient without revoking it for everyone.
No expiry means no end. A shared Google Drive link does not expire automatically. A track shared for a specific purpose remains accessible indefinitely unless you manually remove access — which requires remembering to do it, knowing which link to revoke, and being confident you have not removed access for someone who still needs it.
No tracking means no visibility. A Google Drive link does not tell you whether anyone has actually listened to the track, when they accessed it, or whether they downloaded it. You are sharing into a void.
No download control. A shared link in most generic tools allows the recipient to download the file. If the track should not be downloadable — a pre-release share to industry contacts where you want them to listen but not keep the file — there is no way to enforce this.
Compare approaches on Vault vs Dropbox and Vault vs Google Drive.
How TYFRA Vault handles private music sharing
Every file in Vault is private by default. It is not publicly discoverable, not indexed by search engines, and not visible to anyone outside the project unless you explicitly share it. Public discovery is an opt-in feature — you choose when and what becomes publicly visible.
Share links with granular controls
When you generate a share link in Vault, you set four parameters:
Expiry date. The link stops working automatically at the date and time you set. A pre-release share sent four weeks before release date expires on release day without any manual action. A link sent to an A&R contact for a 48-hour listening window expires in 48 hours.
Download permissions. On or off. Turn downloads off and the recipient can listen in-browser but cannot save the file. The audio plays from BunnyCDN — it does not transfer to the recipient's device.
Comment permissions. Whether the recipient can leave timestamped feedback. For industry contacts you want to hear the track without engaging them in a feedback loop, turn comments off. For mix engineers and collaborators, turn them on.
The link itself. Each link is a unique URL. If you generate separate links for separate recipients, you can revoke access for one person without affecting others.
Tracking who listens
Every share link tracks:
- View count — how many times the link has been opened
- Play events — whether the track was actually played, not just the page loaded
- Last accessed timestamp — when the most recent access occurred
- Download events — whether the file was downloaded (if downloads are enabled)
This is how you know whether the A&R contact actually listened, not just whether they opened the email. It is how you follow up with confidence — "I saw you played the track on Tuesday" is a more informed conversation opener than "just checking if you had a chance to listen."
Separate links for separate recipients
For sensitive shares — demos to labels, stems to mix engineers, masters to sync supervisors — generate a separate link per recipient. If one link needs to be revoked (the recipient left the label, the collaboration fell through), you revoke that link without disturbing anyone else's access. The underlying file in Vault is unaffected.
Private sharing for different music industry contexts
Demos to A&R. A demo should be shareable for listening without being downloadable. Set downloads off, set an expiry of two to four weeks, and track whether it was played. If it was not played, you follow up. If it was played multiple times, you follow up differently. See A&R solutions.
Pre-release tracks to radio and press. Set an expiry matching the release embargo date. Downloads off unless you are providing station-quality files specifically for broadcast. Separate links per outlet so you know which one is listening.
Stems to a mix engineer. Downloads on — they need the files to work. No expiry, or a project-duration expiry. The mix engineer does not need comment access; use in-project comments for feedback on the mix rather than external share link comments.
Masters to sync supervisors. Professional presentation — all metadata visible, instrumental version labelled separately, no download required for initial consideration. If they want to license it, send a high-quality download with formal terms attached. See sync licensing.
Work-in-progress to collaborators. Project-level access rather than share links — collaborators with project access see revisions as they are uploaded, leave timestamped feedback in-project, and have the version context that a standalone share link does not provide. See collaborating on music online and remote music collaboration.
What private sharing protects
The commercial case for controlled sharing is straightforward. A track shared without controls is a track that can be distributed without your knowledge, downloaded without your consent, and accessed indefinitely without your awareness. The loss of control is not always catastrophic — many informal shares cause no problem at all. But when a problem does arise, the absence of controls means no way to identify what happened, no way to limit the damage, and no way to prevent recurrence.
Private sharing with expiry, download controls, and access tracking does not guarantee nothing goes wrong. It does mean that when something does go wrong, you have information and levers that do not exist with a generic shared link. Pair with controlling access to music files and sharing without download for the full control stack.
How TYFRA fits
- All files private by default — not publicly discoverable without explicit share
- Public discovery is opt-in only
- Smart share links: expiry date, download on/off, comment permissions
- Play/view/download tracking per link
- Separate links per recipient — revoke one without affecting others
- Timestamped comments on share links (optional)
- BunnyCDN delivery — no file transfer to device when downloads are off
- Project-level collaborator access for ongoing collaboration
- £9.99/mo · free tier available
Related on TYFRA
Common questions
Your data flows with you across TYFRA
These aren't separate apps. Your tracks, metadata, splits, contacts, and conversations stay connected—so every tool in the TYFRA suite can work from the same source of truth.