Account authentication
HSEZON uses authenticated user sessions for private application areas. Passwords are handled using secure password-hashing functions rather than being stored as readable passwords.
HSEZON contains professional HSE records, project information and user-provided evidence. Security and privacy controls are therefore treated as an important part of the platform's development.
This page explains HSEZON's current security approach without making unsupported certifications or guarantees. Security controls will continue to mature as the platform develops.
HSEZON uses authenticated user sessions for private application areas. Passwords are handled using secure password-hashing functions rather than being stored as readable passwords.
Application workflows use protections such as CSRF validation where implemented to reduce unauthorized form submissions and request manipulation.
Server-side application code uses parameterized/prepared database operations in core workflows to reduce SQL-injection risk.
Projects, HSE records and account functions are intended for authenticated application use rather than public search indexing.
Supported upload workflows can apply file-type validation and controlled filenames. Users should still avoid uploading unnecessary confidential or sensitive information.
AI service credentials are intended to remain on the server and should never be exposed to users through browser-side code or public pages.
When a user intentionally uses an AI-assisted feature, submitted content may need to be processed by an AI service provider to generate the requested result. Users should minimize personal, confidential and sensitive information in prompts, photos and documents and should review the AI Usage Policy and Privacy Policy.
Review our Privacy Policy and AI Usage Policy for more detail.