You can use Juke without an account, and most people do — a mock draft runs entirely in your own browser and needs nothing from us but the page. There is now also an optional account, which exists for one reason: so your drafts follow you from your phone to your laptop. What follows is a specific account of what the app actually does in each case, not a template filled in with the usual disclaimers.
- A mock draft on your own
- Accounts, and what signing in changes
- Drafting with your league
- Email you give us on purpose
- What your browser talks to directly
- What goes through Juke's own server
- Hosting, and Cloudflare's own analytics
- What we never collect
- Cookies and local storage
- Children
- Changes to this page
- Contact
01A mock draft on your own
Drafting solo and signed out, the whole app runs in your browser and nothing about your draft is sent to a server at all — there is no server in that path to send it to. The board, the projections, the scoring and the grade are all computed on your own machine from files the page already downloaded.
Your progress — the seat you picked, every pick made, your league
settings, your queue and watchlist, and any draft you've finished
— is written to your browser's own local storage
(localStorage), on your device only. Signed out, Juke has
no way to read it back, because there is nowhere for it to be read back
from except the browser it was written on. Clearing your browser's site
data deletes it permanently, the same as clearing it for any other site.
That local copy is always written first and is always the real one. Signing in adds a second copy on our server; it does not move anything off your device or make an account necessary to draft. Section 02 is what that adds.
02Accounts, and what signing in changes
An account is optional. Nothing about drafting requires one, and the whole app works signed out exactly as section 01 describes. What an account buys is one thing: the draft you are in the middle of, and the locker of drafts you have finished, follow you to any browser you sign in on instead of living in one.
Identity is handled by Clerk, a third-party authentication provider, not by us. Signing up, logging in, your password, signing in with Google, verifying your email address and keeping you signed in all happen inside Clerk's own components, and the details go to Clerk rather than through Juke. Juke's own code never sees or stores your password. Clerk is a separate company processing that data on our behalf, under its own privacy policy.
What Juke's own database stores about you is deliberately small. Three tables, and only the first exists merely because you signed in:
| Who you are | The account id Clerk issues, and two timestamps — when the row was created and when you were last seen. Not your email address, and not your name: the page already has both from your own session, so a second copy here would be a copy we did not need and would have to protect. |
| Your draft in progress | The same saved draft described in section 01 — seat, picks, settings, queue, watchlist — stored whole against your account id, and replaced each time you save. There is only ever one. |
| Your finished drafts | One row per completed mock: the picks, the league it was, and the grade report, against your account id and the date it finished. |
That is the whole of it. No behavioural profile, no record of what you looked at, nothing about you beyond the drafts you chose to run.
Deleting things. Removing a draft from your locker deletes it
from your account as well as from your browser. Your account itself is
Clerk's to delete, from the account screen behind your avatar —
and doing that now deletes everything in the table above with it.
Clerk tells Juke the account is gone and the three rows are removed:
your id, your draft in progress, and every finished draft. Nothing is
kept back and there is nothing left to ask us for.
This page said the opposite until 2 September 2026, because it was
true: there was no link between the two, and describing one that did
not exist would have been worse than admitting the gap.
03Drafting with your league
Sending an invite link creates a shared room, and a room is the one case where drafting does involve a server — everyone in it has to agree on what happened, which your browser alone can't arbitrate. While that room is open, it holds:
- who's sitting in which seat, and the display name each person typed in;
- every pick that's been made;
- the chat messages sent in that room.
A room needs no account, signed in or not. Your browser generates a random id the first time you join one, stored the same way as everything in section 01, and that id is what the room uses to tell you apart from the person in the next seat. It is not your Clerk account id, and the room is never told your email address or your real name — only the display name you type into it yourself.
A room isn't kept forever. Once every participant has been disconnected for six hours, the room and everything in it — seats, picks, chat, display names — is deleted automatically.
04Email you give us on purpose
Several parts of the site are not built yet — the Waiver, Trade, Prospect, Strategy and League rooms, and sports other than football. Where one of those is offered, pressing it opens a short form that asks for an email address so we can tell you when it opens. That form is the only place Juke itself collects an email address, and it is always something you type on purpose.
What is stored is the address, which button asked for it, and when. It is used to email you about the thing you asked about, and it is not sold, shared or used for advertising. Ask us at the address in section 12 to be removed.
05What your browser talks to directly
A few things load straight from someone else's server, the same way an embedded video or a web font does on most sites — that server sees the request come from your browser directly, including your IP address, the same as it would for any site using it:
| Player photos | Sleeper's own image server, linked directly rather than copied onto ours. |
| Live scores | ESPN's public scoreboard, only fetched while there are games actually being played. |
| Fonts | Google Fonts (Gabarito, Hanken Grotesk, Montserrat, Inter). Archivo and IBM Plex Mono are served from Juke's own domain instead. |
| Sign-in | Clerk, while you are signing up, logging in or signed in — see section 02. Its own bot check (Cloudflare Turnstile) and its avatar images load the same way. |
None of these get anything from Juke beyond the ordinary fact that your browser asked for a file — no draft data, no room data, nothing you've typed.
06What goes through Juke's own server
Besides the account storage in section 02, two things are proxied through Juke's server instead of being called directly, specifically so the provider's own access key never has to sit in a page your browser can read:
- Player news headlines, from Tank01 — fetched when you open a player's sheet, cached briefly (fifteen minutes) so the same headline isn't fetched fresh from the provider every time.
- GIF search in room chat, from GIPHY — only if you actually search for one.
Both requests carry Juke's own server as the visible caller, not your browser, and neither is told anything about you beyond what's needed to answer that one request (a player id, or a search term).
07Hosting, and Cloudflare's own analytics
The site is hosted on Cloudflare, which sees the same standard request information — your IP address, browser and the page requested — that any hosting provider sees for any site it serves. Separately, Cloudflare injects its own Web Analytics beacon into every page on this site to measure real-world load times and errors. That beacon is Cloudflare's, added at their network edge rather than by anything in Juke's own code; it doesn't use cookies and isn't the kind of beacon that follows you across other, unrelated sites.
08What we never collect
- No payment information. Juke is free, there is nowhere in the app to enter a card number, and nothing in it is for sale today.
- No password reaches Juke's own code. If you set one, it goes to Clerk and stays there — see section 02.
- No advertising trackers, and nothing here is sold or shared with anyone for marketing.
- No location data beyond the coarse, IP-level location any web request already carries.
- No record of what you browse. Juke stores the drafts you run, not the players you looked at, the pages you visited or how long you stayed.
09Cookies and local storage
Juke's own code sets no cookies. Everything in sections 01 and 03 is held in local storage, which is not a cookie and is never sent to a server automatically the way a cookie is — it only leaves your browser when the app deliberately sends it, as in a room or a sync.
Signing in does set cookies, because keeping you signed in is what they are for. They are Clerk's, set on Juke's domain by Clerk's own code, and they hold your session — not your draft, and nothing about what you do here. Signing out clears them. Signed out and never signed in, there are no cookies on this site at all.
10Children
Juke isn't directed at children. It's a fantasy football tool, built with an adult fantasy-football audience in mind. There is now a sign-up, and it does not ask for an age or attempt to verify one — so this is a statement about who the site is for, not a gate that enforces it. If you believe a child has created an account here, write to the address below and we will remove it.
11Changes to this page
If what the app actually does changes, this page changes with it — the same rule the rest of the app follows: nothing here should describe a version of Juke that no longer exists. The date at the top moves when it does.
12Contact
Questions about this page, a request to delete the drafts stored against your account, or to be taken off the early-access list: [email protected].
← Back to the Draft Room Terms of Service →