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.
Profile & social data — your @username, display name and avatar; your friend connections; tracks you publish to the Discover chart; likes and saves. Published tracks — together with your @username, display name and avatar — are visible to all Jukebee users. Unpublished tracks stay private to your account.
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. We never receive or store audio recordings — only the resulting text, if you submit it.
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, 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 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.
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.
While your account is active, data is retained so the app works. When you delete your account: your profile (@username, avatar), tracks, albums, publications, likes, saves, friend connections, notifications, presets, settings, uploaded files and push tokens are permanently deleted; published tracks disappear from Discover.
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 not directed at children under 13. We do not knowingly collect data from anyone under 13. If you believe we have, please contact us.
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.