Data minimisation
Products should request only information needed to provide the service, operate safely or meet a legitimate business requirement.
Privacy
Collect less. Protect what is needed.
Privacy is treated as a product and engineering responsibility. Data collection should be proportionate, transparent and limited to a defined purpose.
Core approach
Practical privacy controls.
Purpose clarity
Users should be able to understand why information is requested and how it supports the relevant product or workflow.
Restricted access
Access to personal or commercially sensitive information should be limited by role, operational need and appropriate authentication controls.
Retention discipline
Information should not be retained indefinitely without a clear operational, legal or contractual reason.
Third-party review
External services and integrations should be selected with attention to the information they receive and the function they perform.
Incident response
Suspected exposure, misuse or unexpected access should be investigated, contained and documented promptly.
Website enquiries
Direct communication remains controlled by the sender.
When someone contacts EVENAI by email, the information supplied is used to understand and respond to the enquiry. Sensitive information should not be sent unless it is necessary and an appropriate handling method has been agreed.