Skip to content

Privacy Policy

This policy explains what JamRiff (“we”, “us”) collects when you use it, why we need it, who helps us run the service and how you stay in control of your data.

We decide how and why your personal data is used for JamRiff, which makes us its controller (and, for people in India, its “data fiduciary” under India's Digital Personal Data Protection Act). This policy covers the website and app at jamriff.com and the emails we send. Our Terms of Service explain the rules for using JamRiff.

Last updated 9 November 2026

On this page

The short version

  • Your tracks are private. Only you can see your recordings and transcriptions.
  • We use your recordings only to transcribe them and run JamRiff for you.
  • We don’t sell your personal data. Analytics and advertising cookies are optional: in the EU, EEA, UK and Switzerland they run only if you allow them, elsewhere until you turn them off, which you can do at any time.
  • Delete a track or your account and it’s gone from JamRiff at once, and deleted for good 7 days later. Until then we can bring it back.
  • An account nobody uses for 6 months is deleted, after we email you twice.
  • Card details go straight to our payment providers. We never see your full card number.

Information you give us

  • Account details: your name, email address and password. Passwords are stored only in a hashed form we can't read back.
  • Sign-in with Google or Facebook: if you use it, we receive your name, email address and, if the provider shares it, your profile picture. We never receive your password for those services.
  • Profile and preferences: your date of birth if you choose to add it, your main instrument, skill level and settings such as how tracks open and whether we email you when a transcription is ready.
  • Your recordings: audio and video files you upload, recordings you make with your microphone, and the YouTube and audio file links you paste, with the files we get from them. We use the microphone only while you are recording, after your browser asks for your permission.
  • Your library: the transcriptions we make, track titles, albums, the settings you choose for each track, and ratings or comments you leave on a transcription.
  • Billing: your plan, subscription status, payment history and credit balance. Our payment providers collect your payment details, and in some countries your billing name and address. We receive only what we need to run your subscription, such as whether a payment went through.
  • Messages: what you write when you email us, and whether you joined the Premium waitlist.

Information collected automatically

  • Sign-in sessions: when you sign in, we record the session with your IP address and browser type, so you stay signed in and we can spot sign-ins that aren't yours.
  • Security and abuse prevention: to stop spam, password guessing and free-credit abuse, we count requests per network address, using a keyed hash of your IP address rather than the address itself. Some actions, such as starting a guest session, run a bot check by Cloudflare Turnstile.
  • Country: we read your country from our network provider so we can show prices in your currency and use the right payment options.
  • Usage records: the credits each transcription used and when you last opened a track, so we can show your balance and your recent tracks.
  • Technical logs: our servers log requests and errors to keep JamRiff running and secure.
  • Analytics: with optional cookies on, Google Analytics records the pages you visit and what you do in JamRiff (for example starting a transcription, downloading or upgrading), with your device, browser and the approximate location Google works out from your IP address. It never receives your recordings, the contents of your tracks or your email address. Nothing is sent to Google Analytics while optional cookies are off.
  • Advertising: with optional cookies on, Meta (the Meta Pixel and Conversions API) and Google Ads learn which of our ads brought you to JamRiff and whether you then signed up, made your first free transcription or paid, with your browser, device, IP address and the ad click identifiers in the link you followed. If you're signed in, they also receive a one-way hash of your email address, made on your device, so they can match you to your own Meta or Google account to measure and improve our ads; they never receive the email address itself, your recordings or your tracks.

How we use it

  • To provide JamRiff: create your account, transcribe your recordings, show your library and keep your settings.
  • To send the emails the service needs: confirming your address, resetting your password, confirming an email change, telling you a transcription is ready, and messages about your subscription, payments and top-ups.
  • To run billing: take payments, apply credits, handle renewals, cancellations and refunds.
  • To keep JamRiff safe: prevent fraud, abuse and attacks, and enforce our Terms of Service.
  • To answer you when you contact us, and, if you joined the Premium waitlist, to tell you when it opens.
  • To improve JamRiff, for example from the ratings you give transcriptions and from errors we find in our logs.
  • To meet our legal obligations, such as keeping accounting records.

With optional cookies on, we use what you do on JamRiff to measure our ads on Meta and Google and to show our ads to people likely to use JamRiff. We don't use your recordings or tracks for advertising and we don't make automated decisions about you that have legal or similarly significant effects.

How your recordings are handled

Your recordings and transcriptions are stored privately in your account. They are reachable only through short-lived, signed links made for you, and no one else using JamRiff can see them.

To transcribe a track, a copy of the audio is sent to our transcription service. That copy is deleted automatically within 7 days. We keep your own copy of the audio for as long as the track exists, so you can play it alongside your score. For a YouTube link, the video itself plays from YouTube.

Who we share it with

We share personal data only with providers who help us run JamRiff, and only as much as they need:

ProviderWhat for
Amazon Web ServicesStoring your recordings, transcriptions and downloads, and sending our emails.
Our hosting and database providersRunning the JamRiff app and its database.
CloudflareNetwork security and the Turnstile bot check.
StripeTaking payments, and in some countries acting as the seller of your subscription.
Google and MetaSign-in with Google or Facebook, only if you use it.
YouTube (Google)Playing linked videos through YouTube’s embedded player, only for YouTube tracks.
Google Analytics and Tag ManagerMeasuring how JamRiff is used, with optional cookies on.
MetaMeasuring and improving our ads (Meta Pixel and Conversions API), with optional cookies on.
Google AdsMeasuring and improving our ads, with optional cookies on.
StapeRunning our tagging server, which passes analytics and ad measurement on to Google and Meta, only as far as you allow them.

These providers may use your data only to provide their service to us, except Stripe when it acts as a seller or payment provider, and Google, Meta and YouTube for their own services, which follow their own privacy policies (for YouTube, the Google Privacy Policy).

We may also disclose data if the law requires it, to protect people's rights and safety, or as part of a merger or sale of JamRiff, in which case this policy keeps applying to your data. We don't sell personal data. With optional cookies on, the ad measurement described above may count as “sharing” for cross-context behavioral advertising under some US state laws; turning optional cookies off under Cookie settings, or a Global Privacy Control signal from your browser, stops it.

Cookies and browser storage

JamRiff uses only what it needs to work, plus optional analytics and advertising cookies. In the EU, EEA, UK and Switzerland they stay off until you allow them. Elsewhere they are on until you turn them off: choose Reject all in the cookie banner, or use the switch below. If your browser sends a Global Privacy Control signal, they stay off.

WhatWhy
Session cookieKeeps you signed in. It lasts up to 30 days and is renewed while you use JamRiff.
Sign-in cookiesShort-lived, set while you sign in with Google or Facebook.
Sidebar cookieRemembers whether you collapsed the app’s sidebar. It lasts a year.
Browser storageRemembers small things on your device, such as where you were in a track, so a page your browser closed in the background opens where you left off.
Cloudflare TurnstileMay set its own cookies during a bot check.
YouTube playerLoaded only when you open a YouTube track. YouTube may set its own cookies.
Cookie choiceRemembers your answer to the cookie banner, in your browser’s storage, so we don’t ask again.
Google Analytics cookies (_ga, _ga_…)Optional (see above): tell your visits apart over time. They last up to two years, and turning optional cookies off deletes them. Google Tag Manager, which loads them, runs on every page but sets no cookies of its own.
Advertising cookies (_fbp, _fbc, _gcl_…)Optional (see above): Meta’s and Google’s, to tell which ad brought you here. They last up to 90 days, and turning optional cookies off deletes them.

You can clear cookies and storage in your browser at any time. If you do, you'll be signed out.

How long we keep it

DataKept until
Your account and profileYou delete your account, or 6 months without using JamRiff (paying for Premium counts as using it). We email you 30 and 7 days before; logging in keeps it.
Tracks, recordings and transcriptionsYou delete the track or your account, and 7 days after that.
A transcription that failed or was cancelledAbout 10 minutes after it ends.
The transcription service’s copy of your audioDeleted automatically within 7 days.
Guest sessions and their tracks30 days after the guest’s last visit, unless you create an account.
Sign-in sessionsYou sign out, or up to 30 days without use.
Security counters (hashed addresses)Up to 2 days.
A deleted account or trackKept 7 days so it can be restored (log in to restore an account; write to us for a track), then deleted for good with its files.
Payments, subscriptions and the credit ledgerKept for accounting and tax law. When you delete your account, they are no longer linked to you.

How we protect it

JamRiff uses encrypted connections (HTTPS), stores passwords only as hashes, keeps session cookies out of reach of page scripts, and serves your files only through short-lived links made for your account. Once your email is confirmed, changing it needs approval from that address. No service can be perfectly secure, so if you notice anything suspicious, tell us at support@jamriff.com.

If there is a data breach. If your personal data is affected by a breach, we'll tell you by email without undue delay: what happened, what data it involved, what we are doing about it and what you can do. We'll also report it to the authorities where the law requires, such as the Data Protection Board of India.

Your rights and choices

Depending on where you live, you have the right to:

  • see the personal data we hold about you and get a copy of it;
  • correct it: you can change your name, email, date of birth and preferences in your profile;
  • delete it: delete a track from its menu, or your whole account from your profile;
  • object to or restrict some uses, or withdraw consent you gave;
  • name someone to exercise your rights if you die or can’t act for yourself (in India);
  • complain to your data protection authority, such as the Data Protection Board of India or your local authority in the EU or UK.

To use any of these rights, email support@jamriff.com from the address on your account. We may need to confirm it's you before we act, and we'll reply within the time the law gives us. You can turn off “track ready” emails in Preferences. Emails about your account's security and your payments can't be turned off while you have an account.

International transfers

We are based in the United States, and we and our providers may process your data there and in other countries. Where the law requires it, we rely on safeguards such as standard contractual clauses so your data stays protected wherever it is processed.

Children

JamRiff isn't meant for children under 13, and we don't knowingly collect their data. If you are under 18, a parent or guardian must agree to this policy and our terms for you. If you believe a child has given us data without that consent, email support@jamriff.com and we'll delete it.

Changes to this policy

We'll update this policy when JamRiff or the law changes, and change the date at the top. If a change affects how we use your data in an important way, we'll tell you by email or in the app before it applies.