Privacy

Only what is necessary.

The assessment works without an account. A random identifier is kept in a protected cookie, and only its cryptographic fingerprint is stored. This page explains what data is recorded, why it is needed and how long it is kept.

What is recorded

Answers, response times, changes of mindScore the assessment and improve the items.Stored with the session. Automatic deletion is not yet in place; see the current limitations below.

Declared confidence per questionCompare stated certainty with actual accuracy.Requested for each answer except “I don’t know”. Stored with the session.

Optional context: age range, education, occupational category, income range, regionDescribe the sample used to calibrate future norms.Entirely optional. Answers are stored as categories, never exact values. If you decline all five questions, nothing is recorded.

Device identifier (random value stored only as a fingerprint)Tell a first attempt from a retake, protect the norms, and disclose the known aggregate history on a certificate.Stored for twelve months in a cookie. It contains no network, account or identity data. Clearing cookies removes it.

First name, last name and email at unlockDeliver the report and, only with your consent, display your name on the certificate.Recorded only for a purchase or a report won. The certificate remains linked to an alias unless you agree to publish your name. This data is never sold and is deleted after a verified request, except where accounting rules require retention.

Share cards: public token, opens, tests startedCount link opens and assessments started from the share.Created only if you share. The token cannot be traced back to the session.

Daily marketing counters: page view, start click, language, mobile/desktop, broad channelUnderstand how people move through the site without identifying them.Aggregated by day. No IP, full referrer URL, fingerprint or visitor identifier.

Model runs through the API: model name declared by the operator and publication statusExclude model runs from human norms and indicate which runs M.I. publishes.Unrelated to human sessions.

Stripe identifiers and the accounting recordRecord proof of purchase.Retained for accounting obligations, even after account deletion.

Certificate: public alias, serial, aggregate attempt history, token hash, revocationEnable reliable public verification, including after several attempts.The minimal registry survives deletion, otherwise a revoked certificate would verify as valid.

What is never collected or exposed

No raw keystrokes, no fingerprinting, no named leaderboard.
No IP address is written to the database: it is used only for rate limiting, in memory, and disappears with the process.
A certificate contains no email, IP address, Stripe identifier or access secret. A name appears only with explicit consent.
A public share page exposes no session identifier: the token cannot be traced back to the assessment.
Tab changes are logged but never automatically penalised.

Your rights

The assessment runs without an account and no identity is linked to anonymous attempts.
For an access or deletion request concerning a purchase, email contact@mi-index.com from the address used at unlock.

Current limitations

Your delivery email remains stored until it is deleted following a verified request. A retention period and automatic deletion still need to be implemented.
No scheduled deletion is in place yet, so the periods above are not applied automatically.
Request limits apply separately to each server instance, not across the whole service.
The service operator remains responsible for legal retention periods and for deleting data from backups and technical logs.

More about the method →