Privacy policy

Jambox desktop app and jamboxapp.com — last updated 29 September 2026

Jambox is a practice studio for musicians. This page says exactly what the app and this site do with your information, and it is short on purpose: most of what Jambox does never involves us at all.

Your audio never leaves your computer

Loading a track, separating it into stems, detecting chords and building a practice mix all happen on your machine. Those files are not uploaded, and we cannot see them: there is no server-side copy, and no feature that would create one.

What we do store, if you sign in

• Your account. When you sign in with Google we receive your email address, your name and your profile picture URL. We never receive your Google password, and we have no access to anything else in your Google account.
• Your devices. A record linking your account to the copies of Jambox you have installed, so a paid plan or a purchased credit follows you to your own machine rather than a stranger's.
• Usage counts. How many songs you have imported, how many credits you have, and a log of coarse events (app started, song imported, update prompt shown) with the app version and platform. This is what makes free-tier limits enforceable and tells us which builds are in use.
• Payments. If you buy Jambox Pro, our payment processor (Stripe) holds your payment details and we store the resulting subscription status and receipt — never your card number.

Signing in with Google

Sign-in uses Google OAuth through our authentication provider (Supabase). We request only your basic profile — openid, email and profile — and we use it for one thing: to know which account the app is signed in to. Google's own handling of your data is described in the Google Privacy Policy, and in How Google uses information from sites or apps that use our services.

What we do with Google user data

Jambox's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Concretely: the only Google data we receive is your basic profile (name, email address and profile picture URL); we use it only to identify which account the app is signed in to; we do not use it for advertising, we do not sell it, and we do not transfer it to anyone except the service providers named on this page that are needed to run Jambox. Nothing in Jambox reads your Gmail, Drive, Calendar or contacts — those scopes are never requested.

Importing a song from a link

The import feature is the one part of the app that sends something about a song to us: the link you paste is fetched and converted by our service, then handed back to your machine. The audio it produces is stored on your computer, not on ours.

Who else is involved

• Supabase — authentication, the database and the server functions that run the import. It stores the account data listed above.
• Stripe — payments and subscriptions.
• Cloudflare — this website and the download host, the same way any website is served.
• Google — sign-in only, as above.

We do not sell your information, we do not share it for advertising, and there is no analytics, advertising or crash-reporting SDK in the app or on this site. The only information we have about you is what is listed on this page.

Keeping it, and deleting it

Account data is kept while your account exists. Ask us to delete your account and we will remove the rows described above — account, device links, usage counts, credits — and cancel any subscription through Stripe. Payment records that a tax authority requires us to keep are the one exception, and Stripe holds those.

Children

Jambox is not directed at children under 13, and we do not knowingly collect their data.

Changes

If this policy changes in a way that matters, the date at the top changes and the new version is published here before the change takes effect.

Contact

Jambox is operated by Tao Xie, an individual operating as Jambox. Questions, access requests and deletion requests: support@jamboxapp.com.