Password protection
The authentication code uses password hashing and hash verification to protect account passwords.
Password verification compares a supplied password against its stored hash.
SECURITY & PRIVACY
Financial clarity.
A considered approach to access.
Understand the security controls implemented in the EXEVIQ project and the scope of this overview.
TRANSPARENCY FIRST
Clear information about current controls.
This page describes controls present in the application code. Their coverage and configuration in a deployed environment require separate verification. It does not represent an independent security certification or a complete security audit.
Signed access tokens
The authentication layer checks access-token signatures, required claims and expiry before accepting a session.
Invalid or expired access tokens are rejected by the authentication check.
Session validation
Authentication checks that the user is active and that the session token version matches the current user record.
Tokens with an outdated version are rejected as expired or revoked sessions.
Company access checks
The company-access service checks membership for a specific user and company.
The service denies company access when a matching membership is not found.
Role permissions
The project defines permissions for administrator, finance manager, analyst and viewer roles.
Permission checks reject roles that do not have the requested permission.
PRIVACY INFORMATION
Details deserve clarity.
Company access controls are part of the application foundation. A complete privacy notice also needs to explain how the operated service handles personal and company data.
Further information to be confirmed
- Data collected and the purposes for processing it.
- Hosting locations and service providers.
- Retention and deletion procedures.
- Privacy contacts and request procedures.
This overview is not a substitute for the service’s complete privacy notice.
EXPLORE THE PLATFORM