Privacy policy

In short

• The songs you import are processed in your browser. The audio is never uploaded.
• Your songs, scores, lines and settings are kept in your browser, on your device.
• The apps keep a usage log of what is used, including the names of the song files you import. It holds no IP address.
• If you sign in with Google, the site keeps your Google account's id, email, name and photo, and your usage log is linked to your account.
• There are no ads, nothing is sold, and no advertising or tracking scripts run on the site.

On your device

DrumFX separates the drums, finds the beats and writes the score in your browser. The songs you import, the backing and drum tracks made from them, the scores and lines you write, your practice record and your settings are kept in your browser's storage (IndexedDB and local storage) on this device. They are not sent to the site, and the site cannot read them. Clearing the site's data in your browser deletes them.

The usage log

To see which features are used and what goes wrong, DrumFX and BeatFX send a log of what happens in them to the site's server. It is kept only on groovefx.app. It holds:

• a random id made in your browser for the browser, and one for each visit (a visit ends after 30 minutes without use);
• the features used, such as play, import, save or a finished BeatFX run, and errors;
• the names of the song files you import (never the files themselves);
• the browser, operating system, device type, screen size and language, the page you arrived from and its campaign tags (utm), the app's version, and how long the app was in use;
• the country and region your connection comes from, as worked out by our host, Cloudflare. Your IP address itself is not stored.

When you are not signed in, the log is not linked to a name or account. When you are signed in, the server links your visits to your account (see below).

To turn the log off in a browser, open the browser console on groovefx.app and run localStorage.setItem('gfx.telemetry', 'off').

Your account

Writing and saving songs in DrumFX asks you to sign in with Google. Importing and playing do not. When you sign in, Google tells the site your account's id, your email address, your name and your profile photo, and the site keeps them. A cookie (gfx_session) keeps you signed in for up to 30 days. The server stores only a hash of it. Signing out deletes that session.

While you are signed in, your usage log is linked to your account, so the site's administrators can see what an account did, including the names of the song files it imported. Your songs themselves are still kept only in your browser.

Other services

Each of these receives your IP address and browser details when your browser contacts it, as any web server does. The site sends them nothing else about you.

• Cloudflare hosts the site, its server functions and the usage log's database.
• Google handles signing in, if you choose to.
• Hugging Face serves the drum separation and beat models, which download once, the first time you import a song.
• jsDelivr serves ONNX Runtime, the engine that runs those models.
• YouTube plays the intro video, from its privacy-enhanced youtube-nocookie.com address. It is loaded only when you press play.

How long it is kept

• Usage log events are deleted after 400 days. The summary of each visit (its dates, device, country and how long it lasted) is kept until you ask for it to be deleted.
• Your account is kept until you ask for it to be deleted. Sign-in sessions end after 30 days.
• What is in your browser stays there until you delete it or clear the site's data.

Seeing or deleting it

Write to [email protected] from the email address of your account to get a copy of what is kept about you or to have your account and its log deleted. If you were not signed in, send the visitor id from your browser's local storage (gfx.vid) and we will delete that browser's log. Depending on where you live, you may also have the right to correct, restrict or object to the use of your data and to complain to your data protection authority.

The site is not directed at children under 14, and it asks for no information that would tell their age.

Changes and contact

If this policy changes, this page will show the new version and the date it changed. Questions go to [email protected].