This Privacy Policy explains what personal data the Jukebee mobile application and the jukebee.app website collect, how it is used, and the choices you have. The service is operated by Yevhen Stryzh (individual, Ukraine) — "Jukebee", "we", "us". Contact for privacy matters: [email protected].
Account info — email address and hashed password (managed by Supabase Auth). If you sign in with Apple or Google, we receive the identifier and email your provider shares.
Content you create — the song briefs, lyrics, generated tracks, cover art, clips and albums you make in Jukebee.
Content screening — before a track or music video appears in Discover, its title, lyrics, cover art and video frames are sent to an AI model provider for an automated check against the Community rules; a new @username, display name or avatar is checked the same way. Only the content being checked is sent, never your email or other account details. We store the result (allowed or not, the rule concerned and a short reason), not a copy of the content. If the check cannot run, publishing waits until it can.
Profile & social data — your @username, display name and avatar; your friend connections; tracks and music videos you publish to Discover; likes and saves; the users you block and the publications you hide from your Discover. Published tracks and videos — together with your @username, display name and avatar — are visible to all Jukebee users. Unpublished tracks stay private to your account.
Reports and moderation — the reports you file (what you reported, the reason and any note you add); reports other users file about your publications or your account (you are never told who filed them); the screening results described above; and our moderation decisions about your content or account (removal, restoration, ban).
Uploads — images you upload (e.g. your avatar), stored under unguessable per-user paths.
Voice dictation — the microphone is used only when you tap the mic button, and speech-to-text runs via your phone's own operating-system recognizer. For dictation we never receive or store audio — only the resulting text, if you submit it.
Melody recordings (“Sing my melody”) — when you hum a melody for a track, the recording is uploaded to our storage under an unguessable name so the music model can follow it, and is deleted automatically as soon as the generation finishes or fails (at the latest within a few hours). If you choose Keep as proof the melody is mine when attaching a melody, we keep that one recording in private storage linked to your account, together with its checksum and date, so your License Certificate can prove the melody is yours. You can download or delete a kept recording at any time from the track's Download menu; deleting your account deletes every kept recording. A kept recording is never used to identify you and never used to train anything.
Device push token — Expo Push token + platform (iOS / Android), only if you grant notification permission.
Usage analytics & crash reports — we use Google Firebase Analytics (feature-usage events such as sign-up, generation started/succeeded, paywall viewed) and Firebase Crashlytics (crash reports with device model and OS version) to improve Jukebee. These are processed by Google — see firebase.google.com/support/privacy. We do not use advertising networks or sell data.
We do not collect: precise location, contacts, browsing history, advertising IDs, biometric data (a kept melody recording is authorship evidence you chose to keep, not an identifier), or financial/health information.
To make the app work — your content belongs to your account, and generation requests are processed by AI providers.
To run the social features you choose to use (publishing, friends, sharing).
To keep Jukebee safe — to screen what is published, handle reports and blocks, and enforce the Community rules, including removing content and banning accounts that break them. A service where anyone can publish cannot be offered safely without this, and app stores require it.
To send notifications you opt into (push via the Expo Push API).
To understand usage and fix crashes (Firebase — internal product analytics only, never shared with advertisers).
Supabase (database, storage, auth) — supabase.com/privacy.
Vercel (backend hosting) — vercel.com/legal/privacy-policy.
Google Firebase (analytics + crash reporting) — firebase.google.com/support/privacy.
Expo Push API (notification delivery) — expo.dev/privacy.
AI model providers — the prompts and reference content you submit are processed by the configured music/image/text providers to produce your results. No personal account data beyond the prompt content is sent.
Content screening is currently performed by Google (Gemini API), with DeepSeek as a backup when Google is unavailable. These providers may process the content outside your country, including in the United States and China. Beyond the content being checked — which, for a profile check, is your @username, display name or avatar — no personal account data is sent.
Purchases are processed by Apple (App Store). We never see your payment details; we receive only transaction records (product, date, status) needed to activate what you bought.
Access / portability — Settings → "Export my data" gives you a machine-readable JSON copy, or email us and we respond within 30 days.
Erasure — Settings → "Delete my account", see the Data Deletion page for exactly what happens.
Rectification — edit your data in-app, or contact us.
Objection — turn off push notifications, unpublish your tracks, or delete your account entirely.
Blocks and moderation — see and undo your blocks in Settings → Blocked users. To contest a moderation decision about your content or account, email [email protected].
While your account is active, data is retained so the app works. A melody recording you chose to keep is retained until you delete it from the track's Download menu or delete your account. Reports, blocks, hidden items, screening results and moderation decisions are kept while the accounts involved exist, so that reports can be reviewed and decisions enforced.
When you delete your account: your profile (@username, avatar), tracks, albums, publications, likes, saves, friend connections, blocks, hidden items, the reports you filed, the reports and moderation records about your account, screening results, notifications, presets, settings, uploaded files, kept melody recordings and push tokens are permanently deleted; published tracks and videos disappear from Discover.
We keep one record about a deleted account: a salted fingerprint of its email address — never the address itself, and it cannot be turned back into your email — together with the number of purchased credits left unused, whether the free welcome credits were already used, and, if the account was banned for breaking the Community rules, the date and reason of that ban. If you sign up again with the same email, your purchased credits come back, the free welcome credits are not granted a second time, and the ban applies to the new account.
We retain anonymized usage records (which AI operations ran and what they cost — with the link to you removed) for service accounting. They can no longer be connected to you.
Records of your purchases are held by Apple under their own policies; our copy is deleted.
Jukebee is for users aged 18 and over, and its Discover chart contains content published by other users. We do not knowingly collect data from anyone under 18. If you believe a minor is using Jukebee, contact us and we will delete the account.
All data in transit uses TLS. Passwords are hashed by Supabase Auth. Uploads and media live under unguessable per-user storage paths, and database access is protected by row-level security; privileged access is restricted to the backend service role.
We may update this policy; the "Last updated" date reflects changes. Material changes (new data categories, new processors) will be communicated via in-app notification.