The primary principle of the Service: Anonymity is guaranteed not just by promises in documents, but by the technical architecture of the website itself. We physically do not collect data that could link you to your identity, your answers, or the results obtained.
1. Zero Tracking Architecture
We have fundamentally abandoned any digital profiling and marketing tracking tools:
No advertising or analytical cookies
There are no Google Analytics, Yandex.Metrika, or social media trackers on the website.
The only technical cookie file
Used exclusively for the website to "remember" your preferred interface language. It contains no personal data or unique identifiers.
Local browser storage (localStorage)
For your convenience, your draft answers (so you do not lose progress if the tab is accidentally closed) and the keys to your results are stored directly on your device. Our server does not request them in the background, and you can erase this data at any moment — simply by clearing your browser cache or clicking the "Forget and erase from server" button in the interface.
2. Anonymization of the Network Footprint
The web server requires technical logs solely to protect against network attacks, prevent spam, and ensure stability. However, we have configured them so that they do not allow user identification:
🛡️ Masking IP addresses on entry
Your real IP addresses are stripped by the server "on the fly" and are never recorded on the hard drive. Only masked network tokens with the last part removed (e.g., 194.28.112.0) are saved in system files, making it impossible to determine a specific device or person.
⏱️ Timing Attack Protection
The time of each request to the server is forcibly rounded to 1 minute (without saving seconds and milliseconds). This makes it technically impossible to correlate network events and track your activity second-by-second.
🚫 Complete refusal to record Referer
The server has forcibly excluded referral history logging. The system physically does not store information on which website, search engine, or page you came to the Service from.
3. Data Storage and Auto-deletion
All temporary technical metrics and personal elements have a strictly limited life cycle:
Web server system logs
Automatically and permanently overwritten and deleted after exactly 7 days using the system rotation mechanism.
Protection against spam and heavy load
Temporary anonymous metrics in Redis are subject to complete destructive purge within 25–48 hours.
Test results (for the user)
Intermediate calculations, the personal key (UUID), and the date and time of test completion (forcibly rounded to 1 hour) are stored in the database for 31 days so that you can reopen them using your link. You can delete them prematurely at any moment by clicking the "Forget and erase from server" button.
Research Database (for algorithm calibration)
To verify the mathematical accuracy of the methodology, calibrate scales, and adapt the algorithm to different language environments, an anonymized research profile is saved in a separate database:
Matrix of answers (numerical values);
Gender, interface language, and country code (without details down to city or provider);
Date and time of test completion, forcibly rounded to 1 hour;
Duration of the test, rounded to 1 minute.
4. Architectural Data Decoupling
All arrays of information within the system are stored in completely isolated containers:
1. Technical server logs (masked IP, User-Agent, and time, deleted after 7 days).
2. Final result (calculated categories, UUID, and completion time rounded to the hour — with automatic deletion after 31 days).
3. Anonymized research profile (numerical matrix of answers, country, language, and completion time rounded to the hour — without network addresses, precise seconds, or personal identifiers).
There are no links between these blocks. Network logs are not linked to answers, answers are not linked to the final result, and results are not linked to your network address. It is technically impossible to match a research entry or saved result with the identity of a specific person.
Summary and GDPR / CCPA Compliance:
Thanks to data minimization, instant masking of network addresses, and the absence of tracking, our Service fully complies with the European GDPR regulation and the Californian CCPA law. The mechanisms used belong to the "Strictly Necessary" category, which allows us to protect your privacy by default and not distract you with intrusive cookie consent banners.