Privacy Policy
LEGAL REVIEW REQUIRED. This is a draft that describes how Huddle works today. It has not been reviewed by an attorney and is not yet in force.
Version 0.10 · Not yet in effect · Updated 2026-11-02
This policy describes the data Huddle handles today. It is a draft and doesn't claim compliance with any particular privacy law.
What we collect
| Who | What | Why |
|---|---|---|
| Players (no account) | A team name, an optional mascot emoji and name, and their answers and choices in a game; Remote/Hybrid also stores display name, membership, captain/approval/ready status, self-selected local/remote presence and curated reactions | To run and score the game |
| Account holders | Name, email address, sign-in details (handled by our sign-in provider), Huddle name, role, locale preference | To sign in, manage a Huddle and format application views |
| Creators | Packs, questions, media links and rights statements, branding, notes and files you provide for AI building, including Language Practice learning targets, and the Huddle rating, content labels and review history Huddle stores for each pack | To build and host games |
| Organizations | Display names, default locale and time-zone settings, feature flags, schedules, planned events, session history, Session Reports, ratings and feedback, and any prizes, sponsor names and image links they add | To run games and show reports, prizes and events |
| Returning teams (venue leaderboards, when a venue turns them on) | A venue-scoped team name, the results and championship points of games it finished there, and a hashed team code. No email, phone number or real name. Standings can be public: names, points, wins and games only | To keep a team's record across game nights |
| Everyone | Technical data such as IP address (for rate limiting), device and browser type, and server logs | To keep the Service secure and working |
| Product events | Pseudonymous journey events (a pack, session or creator id and small settings). Not team names, answers or free text | To improve the product |
Prize winners are shown by team name only; Huddle doesn't ask for or store contact details to give out prizes. Players are not asked for an email, phone number or real name. Team names and Remote/Hybrid display names, roster status and reactions are visible to the group. Use a nickname rather than a real full name. Names are not verified identities; device IPs and precise location are not shown to players.
Cookies and device storage
- Sign-in cookies keep you signed in. They are HttpOnly.
- Host cookies remember that a device has entered a host PIN, for about 10 minutes.
- Browser storage keeps a session-scoped guest credential to restore the same team and role after reconnect or a group rematch. Removing a membership revokes its ability to participate. Clearing storage loses that access. It also remembers small conveniences, such as your last screen choice and Room check ticks. They stay in your browser.
We don't use advertising cookies or sell personal data.
Who we share with
Only the services needed to run Huddle:
- Cloudflare, which hosts Huddle, stores its data and files, protects it from abuse and sends sign-in and password-reset emails for us (Huddle runs its own sign-in; no separate sign-in provider holds your password);
- AI providers, when you use an AI feature, and to rate new and edited packs, including private ones, for content (the pack text is checked; it is not used to identify you). What you type, paste or upload for AI building, and the question text being checked, is sent to the provider you or the server uses;
- a payment processor, if billing launches (it isn't live);
- anyone required by law, or to protect people and the Service.
Prelaunch registration requests
When approval is enabled, we store the requested email address, organization name and requester account identifier where applicable, request type and time, and the review decision, reviewer and approval-use time. The designated master user reviews these requests to control prelaunch access. We do not save passwords with requests. Approval does not send an automatic notification; the reviewer communicates the outcome directly.
How long we keep it
- Registration requests and decisions: retained for prelaunch access review and security records. They have no automatic expiry; you may request deletion using the contact details below.
- Pending Study materials: originals and extracted text remain in the private authoring workspace while you work or retry. They are deleted when a generated draft is saved or you cancel. A source excerpt included in a question remains in that pack. Pending materials do not expire automatically; cancel an abandoned attempt to remove them.
- Session Reports and history are kept until a host deletes them. Idle games close automatically.
- Account data is kept while the account exists.
- Logs and product events are kept for a limited time for security and improvement.
[RETENTION PERIODS AND DELETION PROCESS: to be confirmed by counsel and operations.]
Your choices
You can edit your profile, delete finished games and reports, archive or unpublish packs, and ask us to delete your account or data. Contact us (see below).
Children
Accounts are for adults. Huddle is used in rooms that may include young people, and players are asked for a team name and, in Remote/Hybrid, a display name. Huddle doesn't knowingly collect personal information from children for accounts. Hosts who run games for children are responsible for choosing suitable games and for their own rules about children's participation. [AGE AND CHILDREN'S PRIVACY POSITION: to be set by counsel.]
Security
Scoring and permissions are checked on the server. Host controls are PIN protected, and access is separated by Huddle. No system is perfectly secure.
Changes
We update the version and date above when this policy changes and notify account holders of material changes.
Contact
Version history
- 0.10 · not in effect · Named the hosting, data and email provider (Cloudflare) in place of generic hosting, database and sign-in providers, for the move to Cloudflare; remains a draft pending counsel review.
- 0.9 · not in effect · Described manual prelaunch account and organization approval requests and decision records; remains a draft pending counsel review.
- 0.8 · not in effect · Clarified locale preferences and rollout-gated Spanish/French interface catalogs; game content and billing currency remain separate. This policy remains a draft.
- 0.7 · not in effect · Described automatic content rating of new and edited packs (including private ones) by an AI service provider, stored ratings and review history; remains a draft.
- 0.6 · not in effect · Added personal and organization English region preferences, organization time zone, and Language Practice pack metadata; remains a draft.
- 0.5 · not in effect · Described pending Study materials, AI processing and deletion after draft creation or cancellation; remains a draft.
- 0.4 · not in effect · Added persistent venue leaderboards (venue-scoped team names, results and championship points, hashed team codes) and venue events; remains a draft.
- 0.3 · not in effect · Added Remote/Hybrid guest membership, public display names, readiness, presence, reactions and browser rejoin credentials; remains a draft.
- 0.2 · not in effect · Added Venue Prizes wording: the venue provides and is responsible for its prizes. LEGAL REVIEW REQUIRED before Venue Prizes launches.
- 0.1 · not in effect · First draft describing the product as built. Not yet in force.