Cookie Policy
Last updated: August 10, 2026
This page explains how NEKTIQA uses browser cookies and local storage. We currently use only strictly necessary technologies and do not use analytics or advertising cookies.
Cookie and browser-storage inventory
The list below is kept current with the application. Auth.js technologies are activated only during sign-in and authenticated use.
| Cookie | Purpose | Retention | When used |
|---|---|---|---|
| NEXT_LOCALE | Remembers your preferred site language. | 365 days | When you save your choice |
| nektiqa_cookie_consent | Records your cookie-notice choice and the policy version. | 180 days | When you save your choice |
| authjs.session-token / __Secure-authjs.session-token | Keeps your authenticated account session secure. | 30 days | During sign-in and while signed in |
| authjs.csrf-token / __Host-authjs.csrf-token | Protects the sign-in flow against cross-site request forgery. | Session | During sign-in and while signed in |
| authjs.callback-url / __Secure-authjs.callback-url | Returns you to the requested page after sign-in. | Session | During sign-in and while signed in |
| nektiqa-public-psi-fingerprint (localStorage) | Prevents abuse of public tests (rate limiting). | 30 days | During public tests |
Third-party services
Google OAuth and Stripe Checkout open on external provider domains. Any cookies they set are governed by their own privacy and cookie notices and data-processing terms; they are not controlled as NEKTIQA cookies.
Your choices
Strictly necessary technologies cannot be disabled on this site because account access, subscription handling, language preferences, and public-test limits would not work correctly. You can delete cookies and site data in your browser at any time. We will notify you again if this policy changes in a way that affects your choice.