licence

What you may do with a file you buy

A file you buy is licensed to you, for your own listening. Keep it, play it as often as you like, move it between your own devices. What the licence does not cover is passing it on — uploading it, sharing it, broadcasting it, or using it in a business — and each of those has a route that is inside the licence rather than around it. The full terms are set out here rather than behind a link, because terms nobody reads bind nobody.

What the licence permits

This is the permission itself, stated before the limits, because a licence read only as a list of refusals invites the reader to test it.

Listen to or watch the file yourself, as often as you like, for as long as you keep it.
Keep it on any device you own, and move it between them.
Convert it to another format for your own playback.
Play it where you are, to people who are there with you, outside any business setting.
Keep your copy after the download window closes.

What it does not permit

The permission above ends if the file is used outside it. Ending it does not require notice and does not entitle anyone to a refund of a completed purchase.

Uploading it to any public or shared service, including video, music, social and file-sharing platforms.
Passing it on — sending, selling, lending, or sharing the file or any part of it, including an excerpt.
Broadcasting or streaming it, or playing it in any public or commercial place.
Using it in a paid or professional practice, in a venue, or as part of a service offered to others.
Including it in another work, product, or dataset, or using it to train a model.
Removing or altering the identifying information carried inside the file.

The file itself does not enforce this

There is no lock on a downloaded file and we are not going to suggest otherwise. A WAV, an MP3 and an MP4 are open formats with no copy protection in them, anything of the sort would be stripped out in minutes, and every scheme that has been tried broke playback for the people who paid rather than for the people who did not.

So the licence is a permission, not a mechanism. What sits behind it is two things we can actually do: state the boundary exactly, and write it inside the file so it is still legible years after the page that sold it. There is no third thing. We do not mark copies individually, so an uploaded file cannot be traced back to whoever bought it — we would rather say that than imply a capability we chose not to build.

Your copy is identical to everybody else's

The file you download is byte for byte the file every other buyer of the same session downloads. It carries what it was built from — the programme, the beat and carrier, the length, the digest of the build, and the licence with its version — and nothing that distinguishes your copy from anyone else's.

That was a decision rather than an omission. Marking each copy would let us trace a leaked file back to an order, and it would mean the file carried something about you into every place it was ever posted. Metadata travels with a file. We would rather not be able to trace an upload than build a product that quietly tags the person who paid for it.

It has a second consequence worth stating: because every copy is the same file, it is stored once and addressed by its digest. You can check that what you received is what was published, and so can anybody else.

In the file: The programme, the beat and carrier, the length, the digest of the build that produced it, and the licence with its version.
Not in the file: Your name, your email address, your payment details, your country, the time you bought it, and any reference that would single out your copy.

If a copy is published anyway

We can ask the platform to remove an unauthorised copy using evidence of our rights in the programme. Because every buyer receives identical bytes, the uploaded file alone does not identify a buyer or an order.

We do not use automated content matching and do not intend to. A ten hertz beat on a two hundred hertz carrier is not distinctive enough to match reliably, and a matcher trained on it would claim other people's recordings as readily as our own. Taking down somebody else's work by accident is a worse outcome than missing a copy of ours.

A different use needs a different licence

Practice, venue, broadcast and commercial use are available under a separate licence. Ask at protoscience@anulum.li rather than assuming the answer is no — a therapist who wants to play a session in a consulting room is asking a reasonable question, and the personal licence is simply the wrong instrument for it.

What the licence does not reach

It covers the recording delivered to you. It does not claim the frequencies, the method, or the idea of a binaural session, none of which anybody owns. Nothing here restricts you from generating comparable audio yourself, from any source, including ours: the source code is published under the GNU Affero General Public License and says so.

This is version 2026-08-29 of the personal use licence. Files carry the version they were sold under, and a later version does not reach back and change it.