Your data and privacy

Test attempts

Test answers and calculated results are processed on the server. Completed attempts may be stored so results can be shown in an account, associated with an anonymous browser visitor, and used for aggregate site analytics.

HEXACO Personality Test

The assessment asks for explicit completed-response storage consent before it starts. Until completion, responses, random question order, timing totals, and the current position remain in this browser so progress can be resumed. No item responses are sent to the server before the final submission.

On completion, all 96 raw responses are stored with stable private item IDs, their random delivery order, response timings and revision counts, response-quality indicators, calculated raw scale scores, and the frozen assessment, scoring, and norm version identifiers. The record is linked either to your signed-in account or to a random pseudonymous browser visitor. It may be used for saved results, reproducible scoring, and future aggregate assessment analysis.

Response-quality warnings never change scores. Free result responses do not include the private scoring directions, item-to-facet key, norms, facet percentiles, or domain percentiles. The reference layer is returned only after a server-side premium-entitlement check.

Enneagram Personality Test

The assessment keeps progress, a random browser participant ID, previous-attempt links, results, and optional feedback in your browser until you clear them. JSON and CSV files are created only when you choose to export them.

Every completed attempt also stores its stable core, quality-check, experimental cross-check, and adaptive-comparison item IDs; raw response values; delivery and left/right presentation order where applicable; response timings and revisions; scoring versions; nine core scores; and provisional three-centre pattern. This ordinary attempt record is separate from optional consented calibration events, allowing the result to be reproduced and future scoring methods to be evaluated against the original responses.

If you actively select research consent, the completed question IDs and order, responses, broad optional research categories, response timings, quality flags, calculated evidence, previous self-type, and any later fit feedback are sent to TypologyOnline for assessment calibration and research. Names, email addresses, precise birth dates, account details, advertising identifiers, IP addresses, and browser user-agent strings are not added to the calibration record.

Jungian Personality Type Test research assessment

As with the other assessments, a completed Jungian attempt stores its 48 stable item IDs and raw 1–5 responses, random delivery order, randomised A/B presentation orientation, response timings, calculated scale positions, assessment and scoring versions, and non-scoring response-pattern indicators. This preserves the evidence needed to reproduce the result, show saved account history, inspect aggregate item performance, and evaluate later scoring versions.

If you actively select anonymous-research consent, the same versioned response record and any optional structured accuracy and context feedback may additionally be sent to the separate Jungian research collection. Declining that optional consent does not prevent completion, ordinary attempt storage, or local JSON and CSV export.

The research record does not include your username, email, account ID, IP address, precise location, advertising identifiers, browser user-agent string, or free text. The random session UUID is transformed with a secret server-side keyed hash before the encrypted event is stored. Scores are independently recomputed on the server. Every paired comparison has equal scoring weight, and the resulting scale positions are not population percentiles or probabilities.

Accepted events are retained for up to 3650 days, subject to documented periodic review and earlier deletion where required. To request deletion, retain the session UUID in your JSON export and provide it through the contact page. Collection does not automatically change live scoring; any model change requires offline analysis, holdout evaluation, review, and an explicit new version.

Pseudonymous linkage and scoring checks

Random browser participant and attempt identifiers are transformed using a secret server-side keyed hash before storage. This allows retest records to be linked without retaining the original browser identifiers. Submitted client scores are retained for auditing, while the primary rational core score is independently recomputed on the server before analysis. Experimental contrasts, adaptive comparisons, previous-type information, and feedback remain separate from that primary score.

Purpose, consent and retention

The purpose of collection is to inspect data quality, question performance, structure, stability, and possible future calibration. The basis for this optional research collection is your explicit consent. Declining consent does not prevent you from completing the assessment or exporting your own record.

Accepted research events are retained in restricted, encrypted application storage for up to 730 days, unless they must be removed sooner. Access is limited to authorised server administrators using private command-line tools. Raw accepted events remain separate from processed analysis exports.

Research deletion and future versions

You can clear browser copies from the assessment. To request deletion of a submitted research record, use the contact page and provide the participant or attempt ID shown in your JSON export; the operator can transform that identifier and remove matching records without storing it in readable form.

Collected responses do not automatically alter this assessment or anybody else's result. Any scoring change must be analysed, evaluated on held-out data, reviewed, and released under a new explicit version. This experimental assessment is not validated for diagnosis, employment, selection, or treatment decisions.

Accounts

Accounts are optional. If you create one, saved test history and article bookmarks can be attached to it. An article bookmark stores the article identifier and the time it was saved so it can appear in your account. Passwords are protected using Laravel’s standard password hashing and are never stored as readable text.

For account security, responsible-use enforcement and payment-dispute handling, TypologyOnline may store the current account status and reason, status dates, an append-only history of status decisions, an operator or case reference, and a limited encrypted private decision note. Where Stripe billing is used, the site may also store Stripe dispute, customer, charge and payment-intent identifiers, dispute status and reason, amount and currency, and relevant evidence-due and event dates. Raw Stripe webhook payloads, submitted dispute evidence and complete payment-card details are not stored in this account-restriction record.

If premium billing is enabled, TypologyOnline may record the plan and price requested, the version identifiers of the purchase policies acknowledged before Checkout, relevant Stripe Checkout/subscription/invoice/payment identifiers and timestamps, entitlement changes, and the first time a premium report is generated, accessed, or downloaded. This limited delivery record does not contain assessment answers or scores, IP addresses, browser user-agent strings, device fingerprints, or complete card details.

Operational account information is available only through restricted administrative access. The routine administrator console shows account and completion metadata needed to operate the service, but does not display raw assessment responses, scores, result payloads, demographics, OAuth provider identifiers, or encrypted private restriction notes. Access to individual account and dispute summaries is recorded in an append-only administrator audit history.

An open payment dispute may pause premium access and new purchases while leaving free account features available. A serious security or responsible-use restriction may prevent account sign-in. Contact TypologyOnline through the contact page if you believe an account restriction is mistaken or want it reviewed.

Optional demographics

Demographic questions are optional. When provided, each field is stored with version history so original responses can be distinguished from later updates in aggregate analysis.

Search insights and cookies

No third-party site-usage analytics service is currently configured. Essential first-party cookies may still be used for security, account access, saved results, privacy preferences, and normal site behaviour.

TypologyOnline records a small set of first-party assessment milestones: a test was started, a completed attempt was stored, the full result was displayed, an anonymous result was later attached to an account, or another assessment was started after viewing a result in the same browser tab. These counts help measure completion and improve the assessment journey; they are session events rather than unique-person or audience figures, and they cannot explain why somebody left.

Lifecycle records contain a one-way random journey key, fixed event type, assessment identifier, optional source assessment identifier, version and timestamps. They do not contain an account ID, visitor ID, test-attempt ID, username, email address, IP address or hash, user-agent value or hash, advertising identifier, device fingerprint, answers, scores, demographics, page URL, referrer or free text. A short-lived encrypted follow-on token can be held in the current tab's session storage and is removed after the next successful assessment start.

Duplicate milestones are rejected, automated write volume is capped outside the primary database, and raw lifecycle events expire after no more than 395 days. Lifecycle measurement does not alter assessment scoring or replace the completed-attempt record.

The optional first-party search-insight system is currently disabled, so search terms and search-result clicks are not stored for site analysis.