Privacy notice · in force from 27 September 2026 · updated 16 November 2026
How Millionfold handles personal data
This notice covers two different things: the free instrument, which runs entirely in your browser, and the hosted service at millionfold.me, which stores an account of your run when the hosted version is active.
1. Who runs this service
Millionfold is operated by Binary Business ApS, Bueparken 156, 2750 Ballerup, Denmark, CVR 46903420 ("we", "us", "the operator"). For privacy questions, rights requests and support, contact us at [email protected]. Our supervisory authority is Datatilsynet, the Danish Data Protection Agency (datatilsynet.dk).
2. The free instrument (no account, no answers sent)
The assessment and its classic view run entirely in your browser. Generated questions, your answers, timing, scores and history are written only to your own browser's local storage and IndexedDB. Nothing is sent to us, to the operator, or to any third party while you use the free instrument outside a hosted session — there are no analytics, trackers or third-party requests. On millionfold.me, the pages also tell the service when a quick estimate starts or finishes and when an assessment starts: the request carries only that event's name, with no identifier, cookie, answer or score, and the service adds it to the daily totals described in section 3. You can delete this local archive at any time from the Saved runs page; clearing your browser storage deletes it, and we cannot recover it for you because we never received it.
Where the free instrument runs without the hosted service, its Report a problem control keeps a problem report in your browser: you can read the exact report, save it as a file or copy it, and nothing is sent to anyone.
3. What the hosted service stores, and why
When the hosted service is active, we process personal data for six distinct purposes, each on its own legal basis:
| Purpose | What we process | Legal basis |
|---|---|---|
| Saved runs and the purchased report | Your run content and, if you buy a report, order and delivery records | Performance of the contract with you as the participant/buyer |
| Calibration research | Derived findings and pseudonymous response rows from runs you have not restricted | Your explicit opt-in consent, recorded as a purpose version on the run; you can restrict a run from calibration at any time from the Saved runs page |
| Challenge mode | Your display name, IQ ± SE and sitting count, disclosed to whoever opens the link you create; if they consent, their own display name, IQ ± SE and sitting count are disclosed back to you | Your consent, given by creating the link; the invitee's own consent for their disclosure back to you. Either of you can revoke it, which deletes the pairing |
| Billing contact | The email address you give at checkout | Performance of the purchase contract, together with the payment provider's own terms |
| Operational logs | Event codes and keyed peer identifiers, kept to detect abuse and keep the service running | Our legitimate interest in a working, abuse-resistant service |
| Problem reports | A problem report you choose to send with Report a problem, and the optional note and contact address you type into it | Your consent, given each time by pressing Send; you can delete a sent report from the same browser |
4. Data inventory: every table we keep, and what erases it
This lists every stored table that can carry personal data, in plain words, matching the operator's own data inventory exactly:
| Table | Personal data it can hold | What erases it |
|---|---|---|
nf_owner | A hash of your guest credential, and the account it may be linked to | Account deletion, or automatic guest expiry |
nf_run, nf_run_item, and the stored run objects | Run content: the generated items, your answers, timing, your optional age, and the model versions used | Deleting the run, or deleting the account it belongs to |
nf_domain_run and its stored objects | A domain sitting's content: the unscored cognitive-task items, your answers and timing — no IQ or score of any kind | Deleting the run, or deleting the account it belongs to, the same way as a scored run |
nf_run_validation and the calibration tables | Derived findings and pseudonymous calibration rows | Deleting the run, restricting it from calibration, or invalidating the calibration snapshot it fed |
nf_challenge | The display name, IQ ± SE and sitting count you chose to put on a challenge link — disclosed to whoever opens it; creating the link is your consent | Revoking the challenge, or 30 days after the link's own 30-day expiry |
nf_challenge_consent | The invitee's display name, IQ ± SE and sitting count — disclosed only to you, the challenger, after the invitee's own consent | Either party revoking the challenge (deletes the pairing immediately), or the same 30-day sweep as nf_challenge |
nf_challenge_invite | An optional recipient email address for a challenge link you ask us to send, held only until that one message is sent, then only a keyed hash | The plaintext address is cleared once the send is accepted or cancelled; the row itself follows nf_challenge's 30-day sweep |
nf_challenge_suppression | A keyed hash of an address that asked not to receive challenge email again — it names no person, run or account | Kept indefinitely, so the request keeps working; never joined to export or deletion |
nf_report_order, nf_report_entitlement, nf_report_refund, nf_payment_event | Order state, the payment provider's own identifiers, refund amounts and the time you confirmed immediate delivery — never a name, address or raw webhook body | Payment events are pruned 10 days after they are superseded; order and refund rows are kept as financial evidence |
nf_report_buyer | The email address you used at checkout | Run deletion, account deletion, or automatically after 90 days |
nf_report_recovery, nf_report_notification | A keyed hash of the address used for purchase recovery, and mail delivery attempt state | Pruned after 10 days, or on deletion |
nf_report_document | The rendered PDF's object key and content digests (the document itself lives in private storage, not this table) | Run deletion (the stored bytes are then queued for erasure) |
| Launchkit's own account tables | Your email address, sessions, and magic-link sign-in verifications | Account deletion, through the identity controller |
nf_operation_log, nf_request_window | Event codes and keyed hashes of the requesting peer — never your answers or address | 30 days, and 60 seconds, respectively |
| Problem reports, held by the operator's error collector for Millionfold | Only a report you send with Send: the build of the page, your browser's major version, an error code and where in Millionfold's own code it happened, a random report identifier, and the optional note and contact address you typed. Never an error message, your answers, scores or questions, a web address, your sitting or your account | Delete report in the same browser; otherwise the technical part after 14 days, and the note and contact after 7 days |
nf_daily_count | The service counts how many quick estimates are started and finished and how many assessments are started each day, as plain daily totals with no identifier, cookie or address attached. | Kept as daily totals while the service runs; never joined to a run, an owner or an account, and not carried over by a restore from backup |
5. How long we keep things (retention periods)
These periods are the service's enforced configuration, not aspirations — they are the defaults the service computes at startup:
- Saved runs and reports, including domain sittings: kept until you delete them, or the purpose they were collected for is retired.
- Challenge links and any invitee consent: kept until revoked, or 30 days after the link's own 30-day expiry (60 days from creation if never revoked) — an unsent or undelivered invite email is cleared with it. A "do not email me again" request is kept indefinitely, so it keeps working; it is never joined to a run, owner or export.
- Operational logs: kept 30 days.
- Encrypted backups: kept at most 14 days.
- Problem reports: nothing is collected until you press Send, and only the report you were shown is sent. Its technical part is kept actively for 14 days (up to 28 days including backups); the optional note and contact address are kept actively for 7 days (up to 21 days including backups). Your browser keeps the receipt that lets you delete the report for up to 28 days: Delete report has the collector delete it within 24 hours, and its copies leave the backups as they expire; Forget receipt only removes that receipt from your browser. A receipt is not a promise of a reply.
- Superseded payment events: pruned 10 days after they are superseded; the order and refund rows themselves stay as financial evidence for five financial years, under the Danish Bookkeeping Act.
- Billing contact (your checkout email): kept 90 days, or deleted sooner if you delete the run or your account.
- Temporary render objects (a report mid-generation): kept at most 1 hour.
- An upload that never completes (nothing was stored): its placeholder record is removed after 24 hours.
6. Your rights
You can exercise the following from the product itself, without contacting us first:
- Deletion — an individual run, or your whole hosted account, can be deleted from the Saved runs page; deletion revokes access to derived reports and to future calibration use and cannot be undone.
- Restriction — a run can be excluded from calibration research without deleting it, from the Saved runs page.
- Revoking a challenge — either you or a consenting invitee can withdraw a challenge from its own link page at any time, which deletes the consent pairing immediately.
For a copy of the personal data we hold about you (in a machine-readable form if you ask for one), and for anything else the product itself cannot do — for example correcting an inaccurate record, or a question about this notice — write to us at [email protected], quoting your purchase reference if you have one; it names no person on its own. We answer within one month.
7. Processors and hosting
The hosted service runs on servers in Germany (Hetzner), within the EU. Uploaded and generated files, including report documents, are stored using Cloudflare R2.
Transactional mail — account sign-in links, a challenge link you ask us to send, and, once available, purchase receipts — is sent through one mail provider at a time, from a millionfold.me address:
| Recipient | Purpose | Personal data | Location |
|---|---|---|---|
| Cloudflare, Inc. (Cloudflare Email Service), email service provider | Delivers the transactional mail described above | The recipient's email address and the message: a sign-in link, a challenge link or a purchase notice | United States, on Cloudflare's global network |
| Resend, email service provider | Delivers the same mail whenever we send through it instead of Cloudflare | The recipient's email address and the message: a sign-in link, a challenge link or a purchase notice | United States |
A report purchase is sold through Link, the checkout of our payment provider Stripe (Stripe Managed Payments), which is the merchant of record: it sells the report, charges your card, issues the receipt and accounts for VAT. Link receives your payment details and your email address directly, under its own privacy policy, which you accept at checkout; we never see or store your card number. We receive the order and refund state described in the data inventory above, the email address you gave at checkout (kept as the billing contact above), the time you confirmed immediate delivery, and the document you purchased.
8. Cookies
The hosted service sets one cookie: a session credential that proves which guest or account a request belongs to. It is HttpOnly, scoped to SameSite=Strict, and carries no tracking identifier, profile or third-party value. We set no advertising, analytics or third-party cookie.
9. Who can use the service
The service is intended for adults. We do not offer children's norms, and we do not verify age beyond an optional self-declared figure used only to annotate your own run.
10. Language
This notice is published in English only, and English governs its interpretation. We currently sell only where that is sufficient. The test itself is available in every language the site offers.
11. Changes
We may update this notice as the service changes. Material changes will be dated and, where they affect an existing purpose, announced before they take effect.