Anonymous account layer
Rilev does not require name, email, or phone to begin the core anonymous assessment experience.
Back to docs
Anonymity Technical Guide
A compact technical explanation of how Rilev reduces identity exposure before the product even starts discussing analysis or reporting.
Separated data layer
Assessment records and account records are intentionally separated so the platform does not maintain a normal readable join.
Collection minimization
The architecture is strongest when unnecessary identity and tracking data never enter the system in the first place.
Bounded disclosure
When richer workflows exist, sharing should stay explicit, scoped, and user-directed rather than silently expanding the trust boundary.
How this differs from a privacy policy
A privacy policy explains legal commitments. An anonymity architecture explains system shape: what is not collected, what remains separated, and where the platform intentionally limits linkability.
That distinction helps people understand the product, and it gives crawlers a clearer conceptual model than a single broad marketing page can provide.