The app itself
GuitarVee runs on your computer. There is no GuitarVee account, no sign-in, and no sync of its own. Your songs, setlists, settings and practice history are saved in GuitarVee’s own folders on your computer (com.guitarvee.app inside AppData\Roaming and AppData\Local on Windows; ~/.local/share/com.guitarvee.app on the Steam Machine), and GuitarVee itself never sends them anywhere. Looper takes stay in memory until you export them somewhere you choose. Deleting those folders removes the data from that computer.
If Steam is running when you start GuitarVee, Steam records that the app is running and receives the achievements you unlock, and a pack you choose to publish to Steam Workshop is uploaded to Steam. On the Steam copy, when Steam Cloud is on for GuitarVee, Steam keeps a copy of your songs, setlists, custom chords, drum patterns, amp presets, attached audio, drum samples and achievements so they follow you to another computer; settings and practice history stay on each computer, and a copy kept by Steam Cloud is Steam’s to delete. You can turn Steam Cloud off for GuitarVee in Steam. Steam’s own privacy terms cover that data. Without Steam, nothing leaves your computer.
This website
The site is plain HTML. Google Analytics is the only thing on it that collects anything, and it only sets its cookie after you have allowed it.
Google Analytics
Every page loads Google Analytics 4, which is what tells us whether anyone is reading the pages at all. It records the usual web statistics, in aggregate: which pages were opened, roughly where in the world the visit came from, the type of device and browser, the site that linked here, and — only if you allowed it — a random visitor identifier stored in a cookie in your browser. A click on a link to the download ZIP is counted the same way, as a file-download event.
Your choice. The first time you open the site it asks whether Google Analytics may set its cookie. Allow sets the cookie, which lets a return visit be recognised as the same browser. Decline sets no cookie and stores no identifier: each page view is still sent to Google Analytics, but as a one-off visit with no identifier, so it cannot be tied to any other. Choosing Decline after an earlier Allow also removes the cookie. A browser that sends the Global Privacy Control signal is treated as a decline without being asked. Your answer is kept in your browser’s local storage as the single word granted or denied, and nowhere else.
None of that includes your name, your email, or anything you typed into the app. Google’s handling of the data it receives is covered by Google’s own privacy terms. A browser that blocks analytics scripts, or an extension that does, will stop it, and the rest of the site keeps working normally — nothing here needs JavaScript.
Downloads
The download buttons are ordinary links straight to the ZIP files — every build, with its SHA-256 beside it. This site does not log downloads, does not count them itself, and runs no script of its own around them; a click on one of those links is counted by Google Analytics as a file-download event, the same way it counts a page view. Whatever web host serves the file keeps its own standard access log, the way every web server does.
Bug reports
There is no report form. Bug reports arrive as ordinary email, so a report contains exactly what you chose to write and whatever your own mail app puts on a message — your email address among it. Reports are read, used to fix things, and kept until the issue is closed. Nothing is entered into a database, a tracker, or a mailing list.
What is not done with any of it
- Not sold. Not to anyone, for any reason.
- Not shared beyond Google Analytics, named above — apart from the web host’s standard access logs, the email service that delivers bug reports, and Steam, when you run the app through it.
- No advertising and no ad tracking pixels.
- No newsletter list. The email address on a bug report is used to reply to that report.
- No other scripts. The analytics tag is the only external request the site makes; the only other script is the cookie-choice box itself.
Asking for deletion
Write to guitar@guitarvee.com — the same address as everything else — and say what you want removed. If you emailed a bug report and want it deleted, mention roughly when you sent it so the right one can be found. Requests about analytics records are handled the same way, though those identify a browser rather than a person and may already have aged out.
If you would rather type the address by hand: guitar (at) guitarvee.com, with an @ where the “(at)” is.
Changes
If what is collected changes, this page changes with it and the date at the top moves. There is no mailing list to notify.