please post for the world to see
If you came here from a copy that Lonezsi runs, the same machine serves other projects too, and one page covers all of them. This page is the longer one for this program.
JR!TER is software you run yourself, on your own machine. There is no company behind it, no analytics, and no server of ours that your library passes through. It is on somebody's disk rather than in a service, and that somebody is whoever set it up.
An account here is an account on that one machine and nowhere else. If several people have one, each has a separate library and the app never shows one person another's; the exception is a song somebody deliberately shares with you, and whoever runs the machine can read the files on it either way. There is more about both further down.
Nothing here is asking you to agree to anything. You are not being tracked, so there is no banner to dismiss. This page exists so the answers are written down somewhere you can find them, and because the two things you might actually want, a copy of everything and a way to get rid of it, are buttons in Settings rather than a request somebody has to answer.
Four things leave your machine, and only one of them happens without you asking: connecting a Google account, publishing a song to YouTube, fetching ffmpeg the first time you need it, and two typefaces the library page loads from Google. That last one is the one that is not your choice. All four are set out below.
JR!TER is released under the MIT licence, copyright 2026 Lonezsi. The full text is in the
file named LICENSE beside the source, and it is the licence that governs,
not this summary of it.
In plain words: you may use it, read it, change it, run it on as many machines as you like and pass it on, for money or not, so long as the copyright notice and the licence travel with it.
The MIT licence provides the software as is, without warranty of any kind, and the authors are not liable for any claim or damage arising from it. That is not a formality here. This is a personal project that renders audio, deletes rows and uploads video, and it can lose your work. Keep your own copies of anything you would be sorry to lose. The Take a copy button in Settings is partly for that.
Your recordings, lyrics, artwork, titles and notes are yours. Neither this project nor its author receives any right in them, is sent any of them, or has any way to reach them. Publishing is something you do, not something JR!TER does with your material.
None is promised. Nobody is obliged to fix a fault, answer a question, or keep any feature working in a later version.
Consumer law in your country may give you rights that cannot be signed away, and where it does, those rights win: nothing here is meant to reduce them. If a single term turns out to be unenforceable, the rest still stands.
Whoever runs this copy of JR!TER. If that is you, on your own machine, for your own music, then you are the only person who decides anything about this data and there is nobody to write to about it. The author of the software is not involved: no copy of your library reaches them, and they have no way to obtain one.
Under the GDPR, processing carried out by a person in the course of a purely personal or household activity falls outside the regulation entirely (Article 2(2)(c)). Running your own music library on your own machine is that activity. This notice is written anyway, because the exemption stops applying the moment you give the address to other people and hold their material in it, and because being able to check what a program does beats assuming it.
This server can hold an account for more than one person. Each account has its own database file and its own folder of audio, and nothing in the application will show one account another's songs, renders, samples, lyrics, presets, albums or settings. Signing up needs an invite from the owner.
The one thing that crosses between two accounts is a song deliberately shared. Sharing gives the other person that one song: they can play its current render, read its words, and work on its equaliser and limiter. Anything they save becomes a copy in their own library rather than a change to yours. It gives them nothing else: not your other songs, not your samples, not your renders list, not your account, and nothing that posts anywhere. The person who shared it can take it back at any time, and what the recipient made stays in their own library because it was always theirs.
What the separation is, and what it is not. It is a wall inside the application. It is not a wall against whoever runs the machine. The person whose computer this is has the files: they can open any account's database with any SQLite tool and play any audio file in any account's folder, exactly as they could with any other program's data on their own disk. No software running on somebody's own machine can prevent that, and it would be dishonest to describe this as though it could. If you would not want the owner of the server to be able to read something, do not put it here.
If you are the person running this and you have given accounts to other people, you are holding their material. The exemption for purely personal or household activity described above stops covering you at that point, and the responsibilities in this notice become yours towards them: telling them what is held, letting them take a copy or have it deleted, and looking after it. JR!TER gives every account the same two buttons described below, which covers the first of those without you having to do anything by hand.
All of it sits in the data directory of the machine running the server, in a SQLite database and a folder of files. JR!TER does not copy it anywhere else, back it up to anything, or send it to any service. If that machine is backed up by something else, then that something else has your library too.
There is no access log. The server does not record who asked for what, or when, and the line that would have written it was deliberately emptied. Two smaller things are true. Failed sign in attempts are counted per address in memory, which is what lets a short password survive being on the internet, and those counts are gone when the server stops. And if you run it as a background service, whatever the server prints goes to a log file on that machine, which holds startup messages and faults rather than requests.
One, and only once you sign in: the cookie that keeps you signed in. It holds a signed token and nothing else. No identifier, no profile, nothing that could follow you anywhere. There is no analytics cookie because there is no analytics.
That is why this page has no cookie banner. Consent under the ePrivacy rules is not required for storage strictly necessary to provide the service the user asked for, and a cookie whose entire job is to remember that you signed in is that. Asking you to click a box about it would be theatre.
Named exactly, with when. Nothing else, ever.
A notice describing how you could in principle request your data is worth less than a button that hands it over, so these are in Settings:
For as long as you keep it. Nothing expires, nothing is tidied away on a schedule and nothing is deleted behind your back. Deleting a song removes its rows, and its audio goes when nothing else refers to it.
This is a tool for making records, not a service for the public, and it is not directed at children.
It carries the date below, and any change to it is written into the devlog with the release it went out in, so you can see what changed and when rather than being told that it did.
This text last changed in JR!TER 2.4.1, on 7 September 2026.