Privacy

1. The short version

• You can listen without an account. Nothing personal is needed for that.
• Signing in is optional and works through Google, Discord or Telegram. We never see your password or Telegram session secrets.
• No ads, no ad networks, no third-party trackers, and we do not sell or rent data to anyone.

2. If you use the site without an account

Your settings, queue, playback position, favourites and playlists live in your browser (localStorage). They stay on your device.

To build charts and keep the site healthy we record anonymous events: which page or track was opened, the referring website's domain, a rough country taken from the Cloudflare header, the device type (phone, tablet or computer) and a session ID. The session ID is a one-way hash of your IP address and browser, salted with a value that changes every day, so it cannot be turned back into your IP. Raw IP addresses are not written to our database.

3. If you sign in

• From Google or Discord we receive your email address, the account ID at that provider, your name and avatar (via Supabase Auth).
• From Telegram (Login / OpenID Connect with our bot) we receive your Telegram user ID, public name, @username when set, and profile photo URL. We do not receive your phone number or Telegram messages.
• Profile: username, display name, avatar, banner, bio, optional linked Telegram ID / @username, and whether your listening stats are public.
• Synced library: favourites, playlists and their covers, saved collections, likes, follows, listening history and personal stats, so they follow you across devices.
• Optional: if you use Share → Send to Telegram on a track while Telegram is linked, our bot delivers that audio file to your Telegram DM (see below).

4. How we access Google user data

When you choose "Continue with Google", Google shows a consent screen. Only after you approve does our application access Google user data through Google OAuth / OpenID Connect (scopes: openid, email, profile). We do not scrape Google products, request Gmail, Drive, Contacts, or any sensitive/restricted scopes. Access happens only at sign-in (and when you re-link Google in Settings).

Google user data our application will access:

• Google account ID (sub) — stable identifier for your login;
• Email address — to identify the account, send security-related messages (e.g. deletion confirmations), and show linked login methods;
• Name and profile picture URL — to pre-fill your display name and avatar (you can change or remove them later).

5. How we use Google user data

Grail's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

We use Google user data only to provide and improve Grail's sign-in and account features: (1) authenticate you, (2) create and maintain your Grail account, (3) show your name/avatar on your profile if you keep them, and (4) let you manage linked login methods in Settings.

We do not use Google user data for advertising, personalized ads, credit scoring, lending, selling to data brokers, surveillance, or training generalized AI/ML models.

6. How we store Google user data

Google account ID, email, name and avatar URL (or a copy of the avatar you keep) are stored in our Supabase Auth / Postgres project that hosts Grail accounts. Session cookies keep you signed in on your devices. We do not store your Google password.

7. How we share Google user data

We do not sell Google user data. We do not transfer or disclose Google user information to third parties except as needed to operate Grail: Supabase (authentication and database hosting under our project) and Cloudflare (CDN / TLS / attack protection, which sees request metadata such as IP). We do not transfer Google user data to other apps you have not chosen. Your Google email is never shown on your public profile.

We do not allow humans to read Google user data except: with your consent, for security/abuse investigation, to comply with law, or when data is aggregated and no longer tied to you.

8. How we retain and delete Google user data

We retain Google user data for as long as your Grail account exists, or until a scheduled deletion finishes (7 days after you request deletion), unless a longer period is required by law.

You can delete your data via Settings → Account → Delete account, or by emailing juicegrail@proton.me (details at /account-deletion). Deleting your Grail account removes the Google identifiers and profile copy we stored; it does not delete your Google account. You can also disconnect Google under Settings → Account while keeping the Grail account if another login method remains.

9. How we protect Google user data

Security procedures protect the confidentiality of your data. We use HTTPS encryption in transit; the database uses row-level security; only our application server writes account-related records. Access to production systems is limited to operators who need it. No system is perfectly secure — protect your Google account as well.

10. How we access Discord user data

When you choose "Continue with Discord", Discord shows an authorization screen. Only after you approve does our application access Discord user data through Discord OAuth2 (identify and email scopes). We do not read your Discord messages, servers, friends list, or payment info. Access happens only at sign-in (and when you re-link Discord in Settings).

Discord user data our application will access:

• Discord user ID — stable identifier for your login;
• Email address (if Discord provides it for your account) — to identify the account, send security-related messages, and show linked login methods;
• Username / global display name and avatar URL — to pre-fill your display name and avatar (you can change or remove them later).

11. How we use Discord user data

We use Discord user data only to provide and improve Grail's sign-in and account features: (1) authenticate you, (2) create and maintain your Grail account, (3) show your name/avatar on your profile if you keep them, and (4) let you manage linked login methods in Settings.

We do not use Discord user data for advertising, personalized ads, credit scoring, lending, selling to data brokers, surveillance, or training generalized AI/ML models.

12. How we store Discord user data

Discord user ID, email (when provided), name and avatar URL (or a copy of the avatar you keep) are stored in our Supabase Auth / Postgres project that hosts Grail accounts. Session cookies keep you signed in on your devices. We do not store your Discord password.

13. How we share Discord user data

We do not sell Discord user data. We do not transfer or disclose Discord user information to third parties except as needed to operate Grail: Supabase (authentication and database hosting under our project) and Cloudflare (CDN / TLS / attack protection, which sees request metadata such as IP). We do not transfer Discord user data to other apps you have not chosen. Your Discord email is never shown on your public profile.

We do not allow humans to read Discord user data except: with your consent, for security/abuse investigation, to comply with law, or when data is aggregated and no longer tied to you.

14. How we retain and delete Discord user data

We retain Discord user data for as long as your Grail account exists, or until a scheduled deletion finishes (7 days after you request deletion), unless a longer period is required by law.

You can delete your data via Settings → Account → Delete account, or by emailing juicegrail@proton.me (details at /account-deletion). Deleting your Grail account removes the Discord identifiers and profile copy we stored; it does not delete your Discord account. You can also disconnect Discord under Settings → Account while keeping the Grail account if another login method remains.

15. How we protect Discord user data

The same security procedures as for other account data apply: HTTPS in transit, database row-level security, application-server-only writes, limited production access. Protect your Discord account as well.

16. How we access Telegram user data

When you choose "Continue with Telegram", Telegram shows its authorization screen (Login Widget / OpenID Connect via our bot, e.g. @jwmusicbot). Only after you approve does our application receive Telegram profile fields for sign-in. We do not read your chats, contacts, phone number, payment info, or channel memberships. Access happens at sign-in and when you link Telegram under Settings.

Telegram user data our application will access:

• Telegram user ID — stable identifier to link your Grail account and (if you ask) deliver files to your DM;
• Public name and @username (when set) — to show the linked login method and pre-fill profile hints;
• Profile photo URL — to optionally copy an avatar into our profile-media storage (you can change or remove it).

17. How we use Telegram user data

We use Telegram user data to: (1) authenticate you, (2) create and maintain your Grail account, (3) show name/avatar if you keep them, (4) let you manage linked login methods in Settings, and (5) if you press Share → Send to Telegram, send that track's audio file to your Telegram direct messages through our bot.

We do not use Telegram user data for advertising, personalized ads, credit scoring, lending, selling to data brokers, surveillance, or training generalized AI/ML models. We do not message you in Telegram except when you trigger a send (or rare operational replies you start with the bot).

18. How we store Telegram user data

Telegram user ID and @username are stored on your Grail profile in our Supabase Postgres project. A copy of the avatar may be stored in our profile-media bucket. Session cookies keep you signed in on the website. We do not store your Telegram password or cloud password.

19. How we share Telegram user data

We do not sell Telegram user data. Operating Grail involves Supabase (database under our project), Cloudflare (CDN / TLS / attack protection), and Telegram (Bot API) when you sign in or when you ask us to deliver a track to your DM — Telegram then processes that delivery under Telegram's terms. Your Telegram ID is not shown on your public profile.

We do not allow humans to read Telegram-linked account data except: with your consent, for security/abuse investigation, to comply with law, or when data is aggregated and no longer tied to you.

20. Send to Telegram (optional feature)

If Telegram is linked to your account, you can send a catalog track to yourself in Telegram (⋯ → Share → Send to Telegram). Our servers read the audio from our media storage and upload it to Telegram's Bot API addressed to your linked Telegram user ID. Files over Telegram's bot limit (currently 50 MB) are not sent. Sends are rate-limited per account to prevent abuse.

The file appears in your chat with our bot. Telegram stores that message according to Telegram's policies. Unlinking Telegram, blocking the bot, or deleting the chat stops further deliveries; past messages in Telegram remain until you delete them there.

21. How we retain and delete Telegram user data

We retain Telegram-linked identifiers for as long as your Grail account exists, or until a scheduled deletion finishes (7 days after you request deletion), unless a longer period is required by law.

You can unlink Telegram under Settings → Account (while another login method remains), delete the account via Settings → Account → Delete account, or email juicegrail@proton.me. Deleting or unlinking removes the Telegram ID / @username we stored; it does not delete your Telegram account or messages already delivered in Telegram.

22. How we protect Telegram user data

The same security procedures as for other account data apply: HTTPS in transit, database row-level security, application-server-only writes, limited production access. Protect your Telegram account as well.

23. What other people can see

Your username, display name, avatar, banner, bio, badges and role badge, playlists you publish, and your listening stats if you switch them to public. Your Google or Discord email and your Telegram user ID are never shown on your public profile. Anything public can be copied or screenshotted by others, so only put there what you are fine sharing.

24. Why we use this data (site-wide)

• To play music, synchronize your library and show your profile.
• To count plays for charts and recommendations.
• To stop abuse: rate limits look at your IP for a short time in server memory (and per-account limits for Telegram sends).
• To find and fix bugs.
• Google, Discord and Telegram account data: for sign-in, account features, and optional Send to Telegram as described above.

25. Services we rely on

• Supabase: database and Google/Discord sign-in (and account rows including linked Telegram IDs under our project).
• Cloudflare: DNS, content delivery, the tunnel to our server and attack protection. Like any CDN it sees your IP address and requests.
• Google: only if you choose Google Sign-In; Google's Privacy Policy also applies to data Google holds about you.
• Discord: only if you choose Discord sign-in; Discord's Privacy Policy also applies to data Discord holds about you.
• Telegram: only if you choose Telegram sign-in and/or Send to Telegram; Telegram's Privacy Policy also applies to data Telegram holds about you.
• Music files and covers are served from our own server.

26. Cookies and local storage

We use a sign-in cookie (Supabase session), localStorage for settings, library and player state, and a service worker cache for app files and covers. There are no advertising or tracking cookies. Clearing site data in your browser signs you out and resets local settings.

27. How long we keep other data

We retain personal information for the length of time needed to fulfill the purposes in this privacy policy (providing your account and the archive), unless a longer period is required by law. Anonymous statistics are kept to build charts and only ever shown as totals. Server logs are kept for a short operational period.

28. Your choices

You may request that your data be deleted by using Settings → Account → Delete account, or by emailing juicegrail@proton.me (see also /account-deletion). You can edit your profile, make playlists private, hide your stats, or disconnect Google, Discord or Telegram under Settings → Account (while at least one login method remains). For a copy of your data, write to juicegrail@proton.me. We may ask you to confirm that the account is yours.

29. Children

Grail is not meant for children under 13. If we learn an account belongs to a child under 13, we delete it.

30. Contact

Privacy questions and data requests: juicegrail@proton.me. Operator of the service: Juice WRLD Grail fan project, website https://juicewrldgrail.com.

31. Changes

If this policy changes, we update the date at the top of the page. Using the site after that means you accept the new version.