How Better Choice Society handles data.

Scope

This policy applies to betterchoicesociety.org and related pages, forms, and email addresses. The site is intended for students 13 and older, educators, parents, guardians, and other adults. Students under 13 should not submit email addresses, personal information, or classroom scenarios through this site.

Better Choice Society is not a crisis, counseling, legal, medical, or disciplinary service. If a situation involves safety, self-harm, harassment, abuse, threats, or illegal activity, contact a trusted adult, school official, emergency service, or appropriate professional support instead of using this site.

What We Collect

Information you submit

• Newsletter forms may collect an email address, role, consent checkbox, page source, referral link, and timestamps.
• Scenario and educator forms may collect role, school or organization when provided, email when provided, de-identified scenario text, permission choices, page source, referral link, and timestamps.
• Email sent to @betterchoicesociety.org addresses may be forwarded through Cloudflare Email Routing to a Gmail account for review and response.

Information from site use

• The interactive course and curriculum units may store progress, theme selection, exercise answers, point totals, XP, levels, badges, learning-streak dates, and which game concepts have already been introduced in the visitor's own browser (localStorage). This data never leaves the device, is not linked to any account or name, and is deleted when browser data is cleared or when the visitor uses the reset button on the My Progress page.
• There is no teacher dashboard or class-activity report, and we do not track individual students. For the pilot we only use a coarse, owner-created ref label in a page's link to tell broad traffic sources apart. We do not accept free-text "class codes," and no class label is sent to analytics.
• The Long Game (the phone game at /game): your progress (level, streak, cards, Practice XP, independent mastery, and which short concept introductions you have seen) is stored on your own device. The introduction flag lets a completed course lesson replace a redundant game primer and is never sent to our server. We count game starts and completions through the same first-party daily aggregates described below; those events do not include the generated nickname, player ID, answers, account, or session ID. The game contains no advertising or third-party analytics. Friend "squads" and push reminders are turned off during the pilot. Earlier pilot versions stored a random player ID, generated nickname, and aggregate game totals in Cloudflare D1. If that older record exists, the game's "Manage or delete my data" control can still delete it using the deletion credential kept on the same device.
• We use our own first-party measurement endpoint to count page views, coarse traffic sources, selected button and form events, time engaged, and browser performance metrics. It does not use an analytics cookie, advertising ID, account, fingerprint, full IP address, full user agent, page or session ID, learner answer, generated nickname, or free-text submission.
• For measurement we add each event immediately to daily totals containing the page path, an approved event name, a short approved content or campaign label, the referring site's hostname, a two-letter country code supplied by Cloudflare, a coarse mobile/desktop category, and numeric performance summaries. A random event ID is retained for no more than two days solely to prevent a browser retry from being counted twice. Daily totals are retained for up to 25 months. We do not use Google Analytics, Google Ads tags, Meta Pixel, or another advertising tracker.
• Cloudflare may process technical logs, IP addresses, browser data, security signals, and request metadata to operate and protect the site. Rate-limiting stores only salted, hashed IPs — never raw IP addresses.

How We Use Information

• Operate the website, forms, email routing, and classroom-support workflows.
• Send occasional updates when someone signs up for the newsletter.
• Draft human-reviewed replies to educator or student scenarios.
• Improve lessons, examples, onboarding materials, and outreach.
• Measure traffic, diagnose site problems, prevent abuse, and understand which outreach links are useful.

We do not sell student personal information. We do not knowingly ask students to submit names, school names, usernames, exact locations, screenshots, discipline records, medical details, or other identifying details in scenario forms.

Vendors and Services

We use service providers that help operate the site and manage outreach. These currently include Cloudflare Pages, Cloudflare D1, and Cloudflare Email Routing for hosting, storage, first-party measurement, and email routing; and Gmail and Google Drive for outreach email, sheets, and draft documents. These providers may process data according to their own terms and privacy practices.

If we later add a newsletter provider, CRM, classroom integration, or automated response agent, we will update this policy and keep human review in place for scenario replies.

Students and Classroom Examples

Scenario submissions should be anonymous and de-identified before they are sent. A submitted scenario may be used internally to draft a reply or improve lessons. We will ask for permission before turning a scenario into a public classroom example, and we will remove identifying details before publication.

Educators are responsible for following their school, district, and local privacy requirements before inviting students to submit information or use the site in class.

Your Choices

• You can avoid newsletter or scenario forms and contact us by email instead.
• You can clear local course progress by clearing browser data for this site.
• You can delete your Long Game device data, plus any legacy pilot server record associated with it, using the game's "Manage or delete my data" control. Legacy deletion uses a delete key kept only on your device, so no one who merely saw the pseudonymous ID can delete that record. The device copy and delete key are erased only after the server confirms deletion; if the server cannot confirm, both stay on the device so you can retry.
• You can ask us to delete or correct information you submitted.
• You can opt out of future outreach by replying with a clear opt-out request.
• You can use browser settings or privacy tools to limit cookies and similar tracking technologies.
• We honor Global Privacy Control and Do Not Track signals for our optional first-party measurement. You can also turn measurement off below. The only cookie this control sets is a first-party preference that remembers “off” for one year.

We keep newsletter and outreach records until they are no longer needed or until a deletion request is honored. First-party measurement is aggregated into daily totals immediately; short-lived deduplication IDs are retained for no more than two days and daily totals for no more than 25 months. Cloudflare may retain security and edge-operation logs according to its service settings and policies.

Contact

Privacy requests can be sent to [email protected]. General questions can be sent to [email protected].

We may update this policy as the site, storage, analytics, or educator workflows change. The "Last updated" date above will reflect the latest version.