Privacy

Who is responsible

FullVolume is written and published by JURMR, an individual, and the data controller for the small amount of personal data involved is that same person. Contact is the issue tracker on GitHub.

This page covers the game FullVolume, the charting tool FullVolumeCharter and the website fullvolumethegame.xyz.

What is not collected

It is a shorter list than the other one, so it goes first. None of the following exists anywhere in FullVolume:

• An account, a login, an email address or a password.
• An analytics SDK, an event pipeline or a usage counter.
• A crash or error reporting service.
• An advertising identifier, a device fingerprint or any persistent user ID.
• Any third-party tracker, pixel or tag, in the game or on this site.
• A copy of your singing, of any length, anywhere.
• A list, index or sample of your music library.
• Your name, your location, your contacts, your files or your other software.

Nothing is sold, rented or shared with anybody for marketing, because there is nothing to sell and no marketing department to sell it.

What stays on your computer

FullVolume keeps everything it knows about you in Documents\Full Volume. That folder is yours: you can read it, copy it, back it up or delete it, and the uninstaller deliberately never touches it.

Singer profiles

The names you typed and the colors you picked. Local only.

Scores and stars

Your best result per song. There is no leaderboard and nothing is uploaded.

Settings

Audio device, calibration figure, backdrop choice, difficulty, whether the update check is on.

Song folders

The list of folder paths you added, and a cache of what was found in them, so the game does not rescan every launch.

Custom backdrops

The pictures and videos you dropped in. Yours, on your drive.

Player.log

A local diagnostic log Unity writes as the game runs. It is never sent anywhere. If you attach it to a bug report, you are choosing to share it, so have a look at it first.

Your microphone

The game needs your microphone, because that is the game. Here is exactly what happens to it.

While you sing, the incoming audio is read in short frames, measured for pitch, scored against the chart, and discarded. It is held in memory for a fraction of a second and then it is gone. It is never written to disk and never transmitted while you are singing on your own, and there is no record afterwards of anything other than the number at the end.

The one exception is an online room, and that is section 5.

Windows decides which programs may use your microphone, and you can revoke it from the game at any time under Windows privacy settings. Doing so does not stop the rest of the game working, it just means nothing scores.

Online rooms

This is the part where data genuinely leaves your machine, and it only happens while you are in a room.

Your voice

Encoded and sent to the server, which passes it on to the other people in the room so they can hear you. Microphones are open in the lobby; once a song starts, the room switches to push to talk, so nothing goes out unless you hold your key.

Your singer name

Whatever you typed. Everyone in the room sees it, and if the room is public it is visible in the room list. Pick accordingly.

Chat messages

Relayed to the room. Not stored after the room ends.

Scores, and which songs you have

Your live score during a song, and whether the queued song is in your library, so the room can say who is missing it.

Your IP address

Unavoidable: a server cannot send you packets without knowing where to send them. It is used to route traffic and to block somebody abusing a room, and nothing else.

Two things worth knowing about the voice path. First, the server relays voice frames without ever decoding them, so it is not capable of listening to a room even in principle. Second, the music itself never crosses the network at all: everybody plays their own local copy against a shared clock, which is why it stays in time.

Nothing about a room outlives it. When a room closes, its names, chat and scores go with it. Server operators may hold short-lived connection logs for keeping the thing running, as any server does.

Hosting a room from inside the game means other players connect to your own machine and therefore see your IP address, exactly as they would in any other peer-hosted game.

The update check

When it starts, the game asks GitHub whether there is a release newer than the version you are running. That request goes to GitHub's public releases API, carries no identifier of any kind, and GitHub sees it the way it sees any other anonymous request: an IP address and a user agent, under their privacy statement.

Nothing is installed without you clicking yes. The check can be switched off entirely under Settings, General, Check for updates, and with it off the game makes no network request of its own at all.

Discord

If Discord is running on the same computer, the game can tell it what you are playing, so your friends see "FullVolume" and the song on your profile. That is Discord's rich presence feature and it works entirely between the game and the Discord app on your own machine.

What it shares is the song title and artist, and the album art where there is any. It goes to Discord, under their privacy policy, and who can see it is governed by your own Discord settings. Turn off activity status in Discord, or close Discord, and there is nothing to share.

FullVolumeCharter

The charting tool is offline software. It reads the audio and lyric files you point it at, works on them on your machine, and writes a .fvchart where you tell it to. Your working draft is saved locally so you can pick a song back up.

It has no account, sends nothing anywhere, and does not upload your audio for processing. Every bit of the pitch reading, the tempo detection and the syllable splitting happens on your own computer.

The one thing to be aware of is what a .fvchart file contains: the song's audio and art are packed inside it. If you hand somebody the file, you are handing them the recording.

This website

fullvolumethegame.xyz is almost entirely static files. The only server-side code is what takes charter applications and runs the owner's admin page, covered in the next section. Nobody browsing the site is logged in.

• No cookies for visitors. The only cookie on this site belongs to the admin page, and only the owner ever signs in there.
• No analytics and no trackers. No Google Analytics, no tag manager, no pixels, no third-party scripts of any kind.
• No fonts fetched from anybody. The typefaces are served from this domain rather than from Google Fonts, so loading a page tells nobody else that you did.
• Browser storage, kept on your device. Whether you switched the SFX toggle on, and a half-written charter application so a reload does not lose it (cleared once it is sent). Both are saved by your own browser under this site's name, never leave your device, and clearing site data removes them.
• Hosting logs. The site is served by Netlify, who like every host see the requests that reach them: IP address, user agent, the page asked for and the time. That is standard access logging for delivering and protecting a website, under Netlify's privacy policy. I do not have an analytics product on top of it.
• Downloads come from GitHub. Clicking the download button sends you to GitHub's release hosting, and GitHub sees that request.

Charter applications

Applying to become a verified charter is the one place this site asks you for anything. What you send is stored with the site's host, Netlify, and read by the owner:

Your Discord username

So you can be told the answer. It is shown on the admin page and nowhere public.

Your Drive folder link

Opened when you apply, to check it is shared and count the charts in it. If you are accepted, the charts in it are listed on the Marketplace.

Why you applied

Read by the owner, and never published.

Your IP address

Never stored as it is. A one-way scrambled form of it is kept for a day to stop the form being flooded.

To have an application or your verified listing removed, ask on the issue tracker or in the FullVolume Discord.

Marketplace downloads

The Marketplace page holds its catalogue as ordinary files on this site, so browsing and searching it involves no third party at all: the filtering happens inside your own browser.

Downloading a chart does involve one. The file comes from whichever community catalogue holds it, and that site sees the request the way any site sees a download. Those sites have their own privacy policies and I have no control over them and no visibility into them.

The tip jar

The tip jar opens Ko-fi. All payment handling happens on Ko-fi's side under their privacy policy. I never see a card number, a billing address or anything else of the sort. I see what Ko-fi shows any creator: that somebody tipped, the amount, and whatever name or message they chose to attach. The game itself has no payment code in it whatsoever.

Children

FullVolume is not aimed at young children and collects nothing from anybody, so there is no children's data to hold. That said, the online rooms have open microphones and strangers in them, and there is one developer rather than a moderation team. If a child is going to use the online side, a private room with a code among people you know is the sensible way to do it.

Your rights

Depending on where you live, you may have rights to see, correct, export or erase personal data held about you, and to object to its processing. Those rights are real and they are yours.

In practice, there is almost nothing here to exercise them against. I hold no account, no profile and no record of you. Everything the game knows about you is in a folder on your own drive, which makes access, export and erasure the same action: open Documents\Full Volume, and copy or delete it.

For the small residue that exists elsewhere, such as hosting logs or an address blocked for abusing a room, get in touch and it will be dealt with.

Changes

If what the software does with data ever changes, this page changes with it and the date at the top moves. A change that matters, such as anything new leaving your machine, will also be called out in the release notes for the version that introduces it. It will never be introduced quietly.

Contact

Questions about any of this, or about something on this page that does not match what you are seeing, go to the issue tracker. If you would rather not ask in public, say so there and another route can be arranged.