Legal and trust
Privacy Notice
Plain-language summary
An example explanation of the minimal data the planned interface would need and why.
Key points
- Public research does not require an account.
- Precise location and raw IP history are not part of the rights-context preference.
- Magic codes and links are never stored as readable account data.
1. Data categories
A future account would need an email address, account status, language preference, and any rights context the user explicitly chooses to save.
A private My products list records an association with a product. It is not proof of purchase and does not require a serial number, receipt, or precise location.
2. Purpose and minimization
Account data would be used to provide access, preferences, and requested product-list features. Editorial ratings are not personalized for commercial targeting.
The interface does not request browser geolocation. Rights context is a separate, reversible selection and cannot be inferred from language.
3. User control
The planned service will explain export, correction, and deletion routes before accounts become operative.
Retention periods and processors must be documented against the final architecture rather than promised by this prototype.