Use data only when it supports a clear product need.
This policy covers information connected to browsing the platform, maintaining an authenticated session, operating technical services, and handling messages sent to the team.
The aim is not to build a tracking-heavy product. Collection should remain proportionate to security, reliability, and meaningful product improvement.
Operational signals, account details, and information you choose to send.
- Technical request information such as IP address, browser details, timestamps, and application logs.
- Account and authentication information required to provide signed-in features.
- Messages, feedback, or support details submitted directly by you.
- Aggregated usage signals used to understand reliability and improve the experience.
Small pieces of storage can keep the experience working securely.
Cookies or similar browser storage may be used for essential session behavior, authentication, security protections, and interface preferences. They should not be treated as permission for unrelated profiling.
Keep information protected—and no longer than its purpose requires.
Reasonable technical and operational controls are used to protect platform information. Retention periods should reflect the reason the data exists, legal obligations, security needs, and practical troubleshooting windows.
No online service can promise absolute security, so controls and retention practices must continue to evolve with the platform.
Questions and requests should lead to understandable answers.
You may ask for clarification about platform data, request appropriate access or correction, or raise a concern through the contact channel. Applicable rights vary by location and context.
This is a product-facing summary and should be reviewed with appropriate legal guidance before broader commercial use.