We set exactly one kind of cookie ourselves — the sign-in cookie that keeps you logged in while you work through an assessment that takes about forty minutes. Without it you would be signed out halfway. It is strictly necessary, it carries no advertising identifier, and it is not shared with anybody. Your draft answers are held in your browser's own storage rather than in a cookie, and they never leave your device in that form.
No advertising pixel and no behavioural-analytics script runs on any screen of the assessment, on the intake form, or on the storyboard. That is the part that matters most to us and it is absolute: nothing a student does while answering questions is reported to an advertising platform, ever. It is enforced by an allowlist in the code rather than by convention.
An advertising pixel does run on seven kinds of page, and here they are: the homepage, the sign-in page, the sign-up page, the results list, a result page, the unlock page and the account page. On those pages it records that the page was opened, and when an account is created, an assessment is completed, a checkout is started or a payment completes, it reports that the event happened along with the amount where there is one. It never reports a name, an email address, a phone number, an essay, an answer or a score. The pixel is shared with our sibling assessment product, which means the advertising platform can recognise the same browser across both sites using its own cookies — it is told nothing by us that would let it recognise a person.
Two more third-party scripts exist in this product: the payment gateway's checkout, which loads only when you choose to pay, and the booking calendar on the result page. Each sets its own cookies on its own domain when it loads. Neither is present on any page a student passes through while taking the assessment.
The site also sends a browser header refusing camera, microphone, location and advertising-topic participation across every page.