Privacy policy

The short version

• We know your email address and a few facts about the devices you sign in on.
• Gruvato does not store your recordings or the separated tracks. Your music stays on your device.
• We keep a record of the tokens you are given, buy and spend, and of the payments behind them.
• We do not sell your data, show ads or use third-party analytics.
• You can delete your account from the app or from this website, at any time.

Who we are

Gruvato is made and run by Jarad DeLorenzo, an individual developer, who publishes the Google Play app under the developer name "delorenj" and is responsible for this policy. Where this policy says "we", it means Jarad DeLorenzo.

In the direct-download app, payments go through the Stripe account of Lasertoast Studios. The privacy contact for everything here is [email protected].

What we collect

Only what the features below need.

• Your email address. It signs you in with an emailed link and is where we send the emails described below. It is stored with your account.
• Sign-in requests. Each request records the email address, an install ID, the device platform (for example android), the app version and the time. They are deleted once they are older than about 30 minutes.
• Devices and sessions. For each device you sign in on: its install ID (a random ID the app makes on that device), platform, app version, when it first and last signed in, and a session token that we store only as a one-way hash. A device stays signed in until you sign out or delete your account.
• A coarse network bucket. When an account is created we take the network part of your IP address (the first three parts of an IPv4 address, or the first three groups of an IPv6 address) and store a hash of it. We do not store your IP address. The bucket is shared by many people; it only helps us stop one person from claiming many free songs. It is a hash of a coarse network prefix, so someone who held it could work out which network it came from: treat it as pseudonymous, not anonymous.
• Free song and token records. Every token granted, held for a split, spent, refunded or bought, with the time and the IDs and file hash that identify the recording (not its audio). The free-song record keeps the platform and app version from when it was granted, and a record of a token spent also keeps the install ID of the device that spent it.
• Your consent. When you accept the cloud upload terms we record the terms version, the time, and the install ID and app version you accepted on.
• Recording look-ups. To tell which recording a file is, the app works out an audio fingerprint on your device and sends it to Gruvato with the file's length. Gruvato forwards the fingerprint and the length to AcoustID, a recording identification service that Gruvato subscribes to as a customer, and AcoustID answers with identifiers from the MusicBrainz database. Your email address, account ID and install ID are not sent to AcoustID, and neither is the recording itself. We keep a hash of the file, its length and the answer, for your account. We do not keep the fingerprint. We also keep a count of how many look-ups Gruvato makes each month, to stay within our AcoustID plan; the count holds no fingerprint, recording or person. To stop one account from using up the limit for everyone, we keep the time of each look-up your account makes for 24 hours, and then delete it; it holds no fingerprint or recording either.
• Cloud splits. For each split: the app's ID for the recording, the recording's identifier and file hash, its length and size, the status and times, and the addresses at our processing provider where the separated tracks can be downloaded.
• Payments in the direct-download app. Stripe takes payment on its own page; we never see your card number. We send Stripe your email address, your Gruvato account ID and the pack you chose. We keep the Stripe checkout ID and payment ID, the pack, the amount, the currency and whether it was paid.
• Payments in the Google Play app. Google Play takes payment; we never see your card or your Google account. With each purchase the app gives Google a one-way hash of your Gruvato account ID, so the purchase can be matched to your account. We ask Google to confirm the purchase, and keep Google's order ID, the purchase token, the pack, the quantity, the country Google reports for the purchase, whether it was a test purchase and when it was credited, and the price and currency the app saw in Google Play. When a Google Play test purchase (made by an invited tester) credits a free test pack, we also keep a record of which devices have received one: the install ID of each device the account had signed in from, the account ID and the purchase token. It is described under how long we keep it.
• Refunds and chargebacks. When a payment is refunded or disputed, we record which purchase it was, the payment provider's event ID and how many tokens were taken back.
• Emails. Sign-in and deletion emails go out through Resend, which sees the address and the message.
• App store review sign-in. App store reviewers can sign in to one review account with a code instead of an emailed link. Each attempt is logged with its outcome and the hashed network bucket described above; the log keeps no IP address, no email address and no code that was typed.
• This website. The early-access form stores your email address, whether you teach or play, the campaign link you came from (if any) and the time. To limit abuse the site counts requests per IP address in memory for a few minutes; it does not store the address.

Your recordings and the separated tracks

Gruvato does not store your recordings, and it does not store the separated tracks. Your library is on your device.

For a cloud split, the app sends your recording straight from your phone to our processing provider, fal, which separates the drums. We ask fal to delete the upload after about an hour and the separated output after about 3 days. During those 3 days the app can download the result through Gruvato, which passes it along without saving it. After that Gruvato stops serving it. What fal actually keeps, and for how long, is governed by fal's own terms and privacy policy.

Gruvato takes audio bytes from you and never web addresses.

Who else handles your data

• Stripe takes payments in the direct-download app and keeps payment records as the law requires.
• Google Play takes payments in the Google Play app, keeps its own payment records, and confirms each purchase to us.
• Resend sends our emails.
• fal receives your recording and returns the separated tracks.
• AcoustID (AcoustID OÜ, Estonia) receives the audio fingerprint and length for a look-up, from Gruvato's servers, and answers with MusicBrainz identifiers. It is an independent service with its own terms and privacy policy, not a processor acting on our instructions, so we list it here as someone your data is shared with. It receives no email address or account identifier from us. Gruvato's own attributions to AcoustID and MusicBrainz are on the open source licences page.
• Cloudflare carries traffic to gruvato.com and api.gruvato.com, so it sees requests, including IP addresses, as any network provider does.

We do not sell personal data, and we show no ads. The app and this website contain no third-party analytics.

How long we keep it

• Your account, devices, sessions, consent record, recording look-ups and split records: until you delete your account.
• Sign-in requests: about 30 minutes. Deletion links: 15 minutes.
• Token, purchase, refund and cost records: kept after you delete your account, without your email address, as our record of what was granted, bought and spent. They are filed under a random account number, but they still carry the recording IDs and file hashes of the songs you prepared, the processing provider's job IDs, and the install ID of the device that spent each token. The free-song record keeps the platform and app version.
• Test-pack records: a record of which install IDs have received a test pack (the install ID, the account ID and the purchase token), kept after you delete your account, without your email address. We keep it so that the same device cannot get repeated free test packs by deleting its account and signing up again. It affects only invited testers who made a Google Play test purchase, and it is not removed when you delete your account.
• Free-song attempt records (install ID, network bucket and time): kept while your account exists. After you delete it they are removed once they are 24 hours old (an operator setting), counted from when each was recorded, not from the deletion. They stay that long so that deleting and signing up again cannot be used to claim free songs over and over.
• Server logs: the account service writes events such as errors, failed sign-ins and each review sign-in attempt (with the hashed network bucket, never an IP address) to the server's system journal. They are kept for up to 3 weeks (an operator setting), or less if the journal fills first.
• Recordings and separated tracks at fal: we ask for deletion after about 1 hour and about 3 days, as above.
• The early-access list: until you ask us to remove you.

Delete your account

There are two ways, and either one deletes the same things.

• In the app: sign in, open your account and choose Delete account.
• On the web: go to gruvato.com/delete-account, enter your email address, open the link we email you and press Delete my account. The link works for 15 minutes.

Deleting removes your email address, your sign-in, your devices and sessions, your consent record, your recording look-ups and private song bindings, and your split records with the addresses of the separated tracks. A split that is still running is cancelled and its token is released, not charged. Every device is signed out.

Tokens you have left are lost; they cannot be moved or refunded by deleting. What stays is described under how long we keep it: the token, purchase and cost records and, for invited testers, the test-pack records, with no email address attached.

If you sign up again with the same address, that is a new account. It follows the same free-song limits as any new account.

If you joined the early-access list but never made an account, email us and we will remove you.

Your choices

You can ask us what we hold about you, ask us to correct it, or ask us to delete it, by emailing us. Account deletion above needs no email to us.

Security

Everything between the app and Gruvato, fal, Stripe and Google travels over HTTPS, and the app refuses to reach Gruvato any other way. Sign-in links and session tokens are stored only as one-way hashes. Payment details never reach us.

If you pair the app with a Gruvato backend you run yourself, the app talks to it directly over your own network, which may not use HTTPS. That traffic does not reach us.

Changes

If this policy changes we will change the date at the top. Anything that changes what we collect will be reflected here before it ships.

Contact

Questions, requests or removals: [email protected].