Skip to main content
CoreReflex

CoreReflex · privacy

Practice stays private by default

Scenarios work without analytics consent. If you opt in, CoreReflex records only coarse daily totals and a random browser key used to count consenting browsers.

Analytics choice: Not set

You can turn optional analytics on or off at any time. Turning it off clears this browser's pseudonymous key when storage is available; if it is offline, the key is pruned after 180 inactive days. Already aggregated daily totals cannot be linked back to a browser.

What optional analytics count

  • Scenario starts, completion of the ten-second pause, reaching the debrief, and a broad safer / questioning / riskier response category.
  • Counts are stored by day and scenario only. Response categories are never linked to the browser key, and no selected letter or answer text is stored.
  • A random, pseudonymous browser key distinguishes first-time and returning consenting browsers. It is not a verified person count: one person can use multiple browsers, and a shared browser can represent more than one person.

What CoreReflex analytics do not collect

Names, email addresses, account profiles, ages, demographic details, message content, selected-option letters, free-text answers, or response timing. The app does not write IP addresses or user-agent strings into its analytics tables; the hosting provider may still retain standard security logs.

Early access and organization requests

If you join early access, CoreReflex stores the email address, region, request type and consent timestamp you submit. Organization pilot requests store organization name, type, country, seat count, an optional organization domain and consent timestamp; the form does not ask for a person's email or other personal contact information. These records are kept separate from practice responses and anonymous analytics. The app does not collect payment details, and no alert email is sent until delivery is connected.

A browser access token may be stored as an HTTP-only cookie after a valid access code or waitlist signup. Only a one-way hash of that token is stored with the access grant; it contains no contact information.

Retention and withdrawal

The browser key expires after 180 days without activity and its pseudonymous database record is pruned during analytics activity. Daily aggregate totals are retained for up to 24 months; expired rows are pruned on the next dashboard visit or opted-in event. Turning analytics off deletes the browser-key record and stops future collection; already aggregated daily totals remain because they cannot be associated with a browser.

What the impact dashboard means

Practice starts, pause completion, debriefs, and in-simulation response categories are early product signals only. They do not establish that a scam was prevented, money was saved, or learning lasted outside the simulation. The supplied analytics brief's prevalence estimates and proposed government-data feeds are not treated as CoreReflex results; no such feeds are connected.