Privacy Policy

1. The short version

We do not sell personal data. We do not take your private key or seed phrase. If you turn on quick trade, your wallet PIN stays in page memory and is never written to disk. A sign-in uses a session cookie through our existing auth proxy. Watch history stays in your browser's session storage. A Knicks ticket application is saved only when our database keys are configured, and then only with the username, Twitter username, and team picks you submit.

2. Sign-in cookie

Connecting a Jelly wallet signs you in through jelly.fun's auth proxy. Jelly sets a session on its side. Our proxy stores the corresponding session on this site as an HTTP-only cookie named session, and a short-lived HTTP-only cookie named session_nonce while a sign-in is in progress. On an HTTPS visit those cookies are marked secure, and they use SameSite lax. They exist so this browser can stay signed in and so the proxy can forward your requests to Jelly. They are not advertising cookies. We do not use them to follow you across other websites. Signing out, or an expired session, clears them.

While the session is valid, the site asks Jelly for the account tied to it. That response can include your Jelly username, display name, profile photo, wallet id, wallet address, token balances, and referral-reward figures. We use those to show the header, the wallet panel, and trade controls. We do not run a separate profile database for that information.

3. Wallet PIN

Quick trade is off until you turn it on. If you turn it on, you type a 4 to 6 digit wallet PIN. That PIN is held only in the memory of the open page. It is not written to disk, local storage, session storage, a cookie, or our servers, and it is not written to logs. It is cleared when you turn quick trade off. Closing or reloading the page clears it as well, because it was never stored. Do not turn quick trade on if someone else can use the device while the page is open.

4. What stays in this browser

Watch history is stored in sessionStorage on your device, under this site. Each entry can include the video id, caption, username, token mint, token symbol, thumbnail address, and stream address, up to a short recent list. It lets you reopen a clip in this tab. It is not sent to us as a saved profile. Session storage lasts for the browser session and is cleared when that session ends.

The same browser session can also hold a display handle, a challenge team choice, and a local note of wallet value used on the challenge screen. Those values stay on the device for the session. They are not a copy of your private key.

5. Challenge applications

If you apply for the Knicks ticket challenge, and if the site's Supabase project URL and anon key are configured, we store the application so the promotion can be run. The record is your Jelly username, your Twitter username, and your team picks. If those keys are not set, the application is not saved. We use that record to administer the promotion, to check a duplicate application, and to announce a result if the promotion's conditions are met. We do not sell it.

When the same database is configured, a challenge-screen trade note may also be stored: ticker, side, team, amounts, and the handle entered on that screen. Real swaps you sign still go through Jelly. They are not stored as a private jelly.fun brokerage account.

6. Waitlist

If you join the waitlist, we store the email address you submit, and the time you submitted it, so we can contact you about access. That store is used only when it is configured. If it is not configured, the address is not kept.

7. Services the site calls

To run the interface, the site calls other services with the minimum the call needs:

• Jelly, for sign-in, your profile, your wallet, balances, quotes, swaps, videos, and the public trading leaderboard. Authenticated calls go through our auth proxy with your session cookie.
• Jupiter, for token prices, charts, and token search. Those calls send mint addresses or a search query, not your PIN.
• Helius-style balance APIs, meaning public Solana balance and account lookups of that kind, when a balance or token read needs a chain response. Those calls can include a wallet address or a mint. They do not include a private key or a wallet PIN.
• Other public market-data services, when a price, logo, or chart needs a second source. Those calls send a mint or a query.

Those providers process the request under their own terms. A normal HTTPS request can also expose an IP address and a user agent to our host and to the service being called. We do not add an advertising or analytics tracker to the page.

8. What we do not collect

We do not collect, and we do not ask you to paste:

• a private key or a seed phrase;
• a government ID, a selfie, a phone number, a postal address, or a date of birth;
• precise GPS location;
• contacts, photos from your camera roll, or microphone recordings; or
• a payment card number. Wallet activity uses your Jelly wallet, not a card form on this site.

We do not sell personal data. We do not rent it, and we do not trade it to data brokers or advertisers. We share information only as this policy describes: with the service that must see it to complete a request you started, with a host or database that stores a challenge application or a waitlist email when that store is turned on, or if the law requires a disclosure.

9. Public chains

A submitted trade, a wallet address, and a token balance on Solana can be read by anyone who looks at the chain. That publicity comes from the network, not from a sale by us. Do not send a trade if you are unwilling to have the resulting transaction public.

10. How long it lasts

The session cookie lasts until you sign out or it expires. The nonce cookie is short-lived. The PIN exists only while quick trade is on in that page. Watch history and the other session-storage values last for the browser session. A challenge application or a waitlist email is kept while we run that program, and then deleted or left only as long as we need to resolve a dispute about it or to meet a legal duty. We do not keep a private-key archive, because we never receive the key.

11. Age

The site is for people 18 and older. We do not knowingly collect personal information from anyone younger. If you believe a minor has sent us information, contact us through the public channels jelly.fun already uses and we will delete what we can identify.

12. Changes

We can update this policy by posting a new version on this page and changing the date above. Continued use of the site after that posting means you accept the update. The Terms and Conditions explain the bargain for using the site, including liability limits and the agreement not to bring a class action.

This page does not publish a separate legal entity, postal address, or personal name. Questions can be sent through the public channels jelly.fun already uses.