ChoiceDrop information
Privacy
How ChoiceDrop keeps tool inputs local, uses browser storage, measures production performance and prepares optional advertising without activating it.
Tool inputs stay local
Names, choice lists, ratings, tags, wheel entries, notes and generated results are processed in your browser. ChoiceDrop is a static site and does not send this content to an application server or require an account.
Shared lists and facilitator sessions
My lists can store reusable people rosters and general choice lists, including optional participant labels, ratings, leader status, tags and active state. Facilitator sessions can store a local roster snapshot, notes, activities and results that the user deliberately saves after reveal. These private application pages are local to this browser and are excluded from search indexing.
Compatible tools use a short-lived same-tab hand-off to identify the local saved item. Names and roster contents are not placed in ordinary query parameters or sent in the page request.
Saved progress and interrupted outcomes
Favourites, recent tools, theme choice, saved lists and wheels, no-repeat queues, pair schedules and session progress may be stored locally when a feature needs them. For a persistent no-repeat or removal flow, an interrupted animation may leave its already-selected outcome in a local pending transaction so the original result can be revealed or the pre-selection state can be restored. A pending outcome is not recorded as a completed session result.
Export, import and deletion
Exports are created locally and downloaded only when you ask. Imports are read and validated in the browser. Use My lists for individual list controls and Privacy & settings to inspect, export, import or delete all ChoiceDrop application data. Clearing browser site data can also remove saved content and offline files, so export anything important first.
See the Cookie policy for the distinction between local application storage, temporary same-tab storage, offline caches and possible future advertising storage.
Production analytics
On the canonical site at https://choicedrop.net, a guarded third-party Cloudflare Web Analytics script measures page views and web-performance timings. It is not loaded on local builds, continuous-integration checks, preview deployments, automated browser tests or offline pages. ChoiceDrop does not deliberately pass names, lists, ratings, generated results or URL query strings to the analytics integration.
The current integration uses no application analytics cookie and does not track visitors across unrelated websites. Because the script runs in the production page, this application-level separation also relies on Cloudflare handling the script as described in its service and privacy terms.
Advertising and consent
Google AdSense is not active. No Google advertising script, advert request or advertising consent-network request is loaded. A later owner-supplied verification meta tag would be inert page metadata and would not load Google code.
The production site already trusts a guarded Cloudflare Web Analytics script for page and performance measurement. AdSense would add Google and advertising partners, broader purposes and possible advertising storage. Because third-party page scripts are not technically isolated from same-origin browser storage, any later advertising must use a separate storage-isolated origin; the current build rejects live advertising while that boundary is unresolved.
If a rollout is approved after that decision, a Google-certified consent management platform will be configured through the AdSense dashboard. ChoiceDrop will not use a homemade consent banner.
Other monetisation
Affiliate recommendations, digital products and supporter links are disabled. No related third-party scripts are loaded.
Hosting logs
The static host may keep ordinary infrastructure logs, such as request time, requested path, approximate network information and browser details, for security and reliability. ChoiceDrop does not combine these logs with tool inputs.
Shared URL fragments
A wheel may be shared by placing its configuration after the # in a URL. The fragment is not sent in the HTTP request, but anyone who receives the full link can read it. Saved rosters are not added automatically. Do not put sensitive personal information in a shareable URL.
Edited template hand-offs
When you edit a curated template and open it in a tool, its bounded entries are held temporarily in one-use session storage in that tab. The target tool consumes and removes the hand-off. Template entries are not put in the address, uploaded or made available to another visitor.