Privacy & Compliance · Combined Reference

The CLEAR Crew — Privacy, Compliance & Accessibility

Every privacy, student-data, and accessibility commitment for the CLEAR Crew detective thinking game, on one printable page.

Applies to: index.html · A self-contained classroom critical-thinking game (grades 3–8). Last updated: June 29, 2026 · Version 1.0

‹ Back to the game
This page is not legal advice. It describes how the CLEAR Crew game is built so a school or district can review it. Your district's counsel or privacy officer should review any specific obligations against your local Data Sharing Agreement (DSA/DPA).
↑ top

1 · What this tool actually does

The CLEAR Crew is a single HTML file that runs entirely inside the student's web browser. There is no server behind it, no account to create, and no database. It teaches the CLEAR critical-thinking process (Claim · Lens · Evidence · Alternatives · Response) through detective cases.

Plainly: the game collects no personal data and sends nothing anywhere. Students tap answer choices; the game checks them in the browser and shows feedback. Nothing they do is recorded off their device.

  • No accounts, logins, names, emails, or passwords.
  • No server, database, or backend — the whole game is the one file.
  • No data is transmitted; once the page has loaded it works fully offline.
  • No trackers, advertising, analytics, or tracking pixels.
  • No use of student activity to train AI models — there is no AI in the tool.
  • The only "memory" is which cases were solved in the current visit, held in the page until you close or reload it, and the current case ID written into the page's own web address (URL) so a teacher can share a direct link. Neither leaves the device.
Tier: client-side Zero data collection No accounts Works offline

One honest exception (external request): the page links to Google Fonts to load its two display fonts. That request goes to Google's font servers and, like any web font request, exposes standard request metadata (such as IP address and browser type) to Google — but carries no student work, no answers, and no identifying content from the game. A school that wants a truly zero-external-request build can ask for a version with the fonts embedded in the file (or substitute system fonts); the game is otherwise unchanged.

↑ top

2 · Short version

↑ top

3 · Terms of use

Who may use it

The CLEAR Crew may be used by educators, students under school supervision, families, schools, and districts. When used with students, the teacher, school, or district decides whether it is appropriate for those students and obtains any consent their local policy requires.

Acceptable use

Use the game for classroom and at-home critical-thinking practice. Do not modify it to collect personal data, add tracking, or present unsafe content to students. Do not represent the game as endorsed by, or as collecting data on behalf of, any organization that has not agreed to that.

Ownership & license

The CLEAR Crew is an educational resource created by Miguel Guhlin (MGuhlin.org). Schools and teachers may use, copy, host, and share the file for non-commercial educational purposes. [Confirm the exact license you want here — e.g. CC BY-NC 4.0 or CC0 — before publishing.]

As-is, no warranty

The game is provided "as is," without warranty of uninterrupted availability, fitness for a particular purpose, or guaranteed legal compliance for a specific school system. Schools remain responsible for deciding whether it fits their requirements.

↑ top

4 · Privacy policy

What "student personal information" means here

Student personal information is any information that identifies, relates to, or can reasonably be linked to a student — names, identifiers, work product, uploads, recordings, or activity logs tied to a student.

What the game collects

None of the above. The CLEAR Crew has no field to enter a name, no upload, no microphone or camera use, no login, and no code that sends data to any server. It does not read precise location, contacts, or device identifiers.

What is processed, and where

How any of it is used

Only to run the game on the student's screen — show the case, check answers, and display progress. There is no other use, because there is no other place for the data to go.

What the game does not do

No advertising, no behavioral profiling, no cross-site tracking, no sale or sharing of data, no AI model training, and no re-identification of anyone.

↑ top

5 · Student-privacy commitments (PROTECT)

P — Parental rights & access
Because no student data is stored anywhere, there is no record to access, correct, export, or delete on a server. Parents and eligible students with questions should contact the teacher or school that assigned the game (see section 11). Schools respond under FERPA, COPPA, state law, and local policy.
R — Retention & deletion
Nothing is retained off the device. To clear in-browser game state, close or reload the tab, or clear the browser's site data. There is no backup, snapshot, or stored copy to purge.
O — Opt-out options
There is nothing to opt out of: no ads, no profiling, no data sale, no AI training. A school wanting zero external requests can use the embedded-fonts build (section 1).
T — Transparency
This page lists every data behavior and the single external request. The full source is one readable HTML file a district can inspect.
E — Encryption & security
Serve the file over HTTPS in production so it is delivered securely. There is no server-side data store to encrypt because no data is stored server-side.
C — Consent & age
Designed for grades 3–8, which includes children under 13. Because the game collects no personal information, it is built to be usable without triggering data-collection consent requirements; schools still follow their local consent and notice process. (See COPPA in section 7.)
T — Third-party management
No third-party service receives student data. The only third-party endpoint touched is the Google Fonts CDN, for fonts only (section 9).
↑ top

6 · GDPR compliance summary

For schools where the UK GDPR or EU GDPR may apply (including EU/UK students or staff), the CLEAR Crew is designed around data minimization by default: it processes no personal data, so most GDPR obligations have nothing to attach to.

Roles

For any classroom deployment, the school or district is the data controller. The game's author has no access to any student data and operates, at most, as a provider of software that performs no processing of personal data on the author's behalf.

Lawful basis & minimization

Because the tool collects and transmits no personal data, there is no processing requiring a lawful basis under Article 6, and the principle of data minimization (Article 5(1)(c)) is met at the strongest level — nothing is collected.

Data-subject rights (Articles 15–22)

RightHow it's satisfied
Access / portabilityNo personal data is held to provide; in-browser state is already on the user's own device.
RectificationNo stored personal data to correct.
Erasure ("right to be forgotten")Closing/reloading the tab or clearing site data removes all local state; there is no server copy.
Restriction / objectionNo profiling, automated decision-making, or marketing to restrict or object to.

International transfers

No personal data is transferred anywhere. The Google Fonts request involves Google as an independent font provider; schools with strict transfer requirements can eliminate even that by using the embedded-fonts build. [EU/UK districts: confirm font-CDN posture with your DPO if relevant.]

↑ top

7 · Texas compliance

Plain-language mapping to the Texas and federal rules that apply to K–12 students. Not legal advice; your district counsel should confirm against your DSA.

Texas SCOPE Act (Securing Children Online through Parental Empowerment)

SCOPE protects Texas minors under 18 with rules on age registration, parental controls, harmful-content strategies, and data-use limits. The CLEAR Crew has no account system, so there is no age to register or lock, and it has no data-collection or advertising to limit. It presents only fixed, teacher-reviewable educational case content. Note that some SCOPE provisions have been challenged and partly enjoined in federal court; this tool reflects only what such a no-account, no-data tool would need, not enjoined provisions.

FERPA (Family Educational Rights and Privacy Act)

FERPA governs education records. The game creates no education record (no stored, identifiable student work). When a school uses it for instruction, the school retains full control; there is no vendor-held record to inspect, correct, or disclose.

COPPA (Children's Online Privacy Protection Act)

COPPA governs collecting personal information from children under 13. The CLEAR Crew collects no personal information from any child, which is the cleanest possible COPPA posture. Where a school uses it with under-13 students, the district may act as the parent's agent for consent under its existing policy, though no collection is occurring.

Texas Education Code §32.151–32.156

This framework governs data agreements between districts and online service providers handling covered student information. Because the game transmits no covered student information, there is no data exchange to govern; a district may still attach the short addendum in section 8 to its records.

CIPA (Children's Internet Protection Act)

CIPA is a network-level obligation on schools and libraries (an internet filter plus an internet-safety policy) — not a privacy law on a tool. The CLEAR Crew contains no external links for students to follow, no chat, no uploads, and no user-generated content, so it introduces no new filtering surface. It does not replace the district's required network filter or internet-safety policy.

↑ top

8 · District data privacy addendum (short form)

A district that catalogs classroom tools may attach this short attestation. A full signature-ready addendum is unnecessary for a tool that collects no student data, but the fields below can be filled in for recordkeeping.

School / district / organization[fill in]
Deployment owner / contact[teacher or campus tech lead — fill in]
Privacy/security contact email[fill in before publishing]
ToolThe CLEAR Crew (index.html), v1.0
Where it's hosted[e.g. district web server / GitHub Pages / Google Sites iframe — fill in]
Approved educational purposeTeaching the CLEAR critical-thinking process to grades 3–8.
Student data collectedNone.
Data transmitted to providerNone.
SubprocessorsNone for student data. Google Fonts CDN serves fonts only (removable via embedded-fonts build).
RetentionNo server-side data; in-browser state ends on tab close/reload.
Data-use commitmentsNo sale, sharing, advertising, profiling, or AI training. No re-identification.
↑ top

9 · Third-party & data inventory

ItemLocal storageExternal requestStudent-identifying data
Game logic & casesNone (in-memory only)NoneNone
Case progress / solved badgesIn-page memory; cleared on reloadNoneNone
Direct-link to a caseURL hash (e.g. #case=rumor)NoneNone — case ID only
Confetti / animationsNoneNoneNone
Display fontsNoneGoogle Fonts CDN (fonts only)None — no game content sent

Network egress declaration: aside from the optional Google Fonts stylesheet, the game makes zero outbound network requests. It contains no analytics, advertising, tracking, social, or backend calls. This is verifiable by reading the single source file.

↑ top

10 · Accessibility statement (VPAT-lite)

The CLEAR Crew aims to meet WCAG 2.1 Level AA for this kind of interactive content. This summary is for procurement reviewers who want a VPAT-style overview without the full form.

AreaStatusNotes
Text & readingSupportsHigh-contrast text, large readable type, semantic headings, scalable with browser zoom.
Color useSupportsCorrect/incorrect answers use a ✓/✗ mark and words, not color alone.
Pointer / touch inputSupportsAll answers are tappable buttons sized for touch; works on tablets and interactive whiteboards.
KeyboardPartially supportsButtons are native and Tab/Enter-activatable; a full keyboard-only audit and explicit focus styling on every control is a known gap (see below).
MotionPartially supportsConfetti is brief and decays in ~3 seconds; honoring prefers-reduced-motion to suppress it is a planned improvement.
AudioSupportsThe game has no sound, so no audio barriers and no narration dependence.

Known gaps (stated honestly)

To report an accessibility barrier, contact the deploying teacher or school, who can relay it to the author. [Add a direct contact here if you want reports to reach you directly.]

↑ top

11 · Contact, requests & policy changes

For classroom use, privacy or accessibility requests should go first to the teacher, school, or district that deployed the game. Because no student data is collected or stored by the tool, there is no provider-held record to retrieve or delete; schools handle any related education-record requests under their own FERPA/COPPA process and should acknowledge within 10 school days and complete within 30 calendar days when feasible.

Author / resource contact: Miguel Guhlin — [add preferred contact email or MGuhlin.org contact link before publishing].

Material changes to this policy will be posted here with an updated date and version.

Version history

DateVersionSummary
June 29, 20261.0Initial combined privacy, GDPR, Texas (SCOPE/FERPA/COPPA/TEC 32.151/CIPA), district addendum, and accessibility statement for the CLEAR Crew game.