Launch baseline · effective November 5, 2026. Describes actual soft-launch data flows. Not a compliance certification.
Privacy Policy
Privacy Policy
Effective date: November 5, 2026
1. Who this covers
This notice explains what the SHOTCLOCK web app at shotclock.fun stores or transmits during soft launch. It is operated as a DOU DIGITAL project. A dedicated privacy mailbox, postal address, and registered legal entity details are not published on this site yet — see section 8.
2. What stays on your device
The browser keeps local / session data used to run the product, including: language preference (`huddle.lang` and a `lang` cookie), theme and brand-kit choice, soft-local account / handle / avatar fields, study progress, practice chips, favorites, notifications, on-device Stars / cash / SOL display balances, registration UI state, and similar product settings. Clearing this site's data in your browser removes that copy. Logging out clears the soft-local user record this app manages on the device.
3. Accounts and identity
When NEXT_PUBLIC_DYNAMIC_ENVIRONMENT_ID is configured, sign-in can use Dynamic for email one-time codes and optional wallet connect. In that case Dynamic processes authentication data under its own terms; SHOTCLOCK receives a user id and may receive an email and public wallet address to attach to your session. Without that configuration, accounts are created and stored only on this device (soft local). We do not invent a separate password database in this app.
4. Online multiplayer
When you join an online table or freeroll event, the game server receives a stable player id, display name, enrollment / seat info, answers, and timing needed to run the match and show shared results. Match state is for gameplay. Public leaderboard pollution with test accounts should be avoided; soft-launch freerolls are free and do not take card payments through SHOTCLOCK while paid entry is disabled.
5. Payments
Live paid entry and live Stars pack checkout stay off unless payments flags are explicitly enabled. UI may mention Whop (card packs) or Dynamic (wallet) as intended processors for a future launch; those flows do not process live paid Bomb Pops entry today. SHOTCLOCK is not designed to store full card numbers. Any future settlement references would be operational records only after payments are actually turned on.
6. Cookies, analytics, ads
We set a first-party lang preference cookie (SameSite=Lax) so your language choice can persist. Theme and most progress use localStorage, not ad trackers. This soft-launch build does not ship a third-party advertising pixel or analytics SDK in application source. Hosting providers (for example Vercel for the website, Render for the game server when running) may process standard technical request logs under their own infrastructure policies.
7. Your choices
Change language in the site footer. Switch theme in settings. Log out to clear the soft-local session this app stores. Clear site data in your browser to remove local progress. If you signed in through Dynamic, use that provider's account controls for provider-side credentials. There is not yet a dedicated in-app "delete my cloud account" button beyond logout / provider controls.
8. Contact for privacy questions
Official social accounts are not linked in the footer yet (placeholders stay hidden until real profiles exist). In-app Messages are marked coming soon and are not a support inbox. No verified privacy email or support route is published on this site today. Until an official channel is listed here or in the footer, we cannot claim a working privacy inquiry path. Do not send personal data to unofficial accounts claiming to be SHOTCLOCK.
9. Changes
We may update this Policy by posting a new version with a new effective date. Material soft-launch changes will be reflected on this page.
Related: Terms of Play · Home