Password storage
Passwords continue to use the application’s established secure password hashing rather than being stored as plaintext.
Security
This overview describes controls present in the released application and static-site architecture. It does not claim certifications or compliance status.
Application controls
Passwords continue to use the application’s established secure password hashing rather than being stored as plaintext.
Project membership and roles determine who can view or change review work, with separate administrator controls.
The application uses authenticated browser sessions. Password reset and selected administrative actions invalidate older sessions through session versioning.
The production deployment is configured for secure cookies and HTTPS-based public application URLs.
Application HTML responses include noindex and nofollow instructions, and the app-domain robots file disallows crawling.
When enabled by an administrator, new users verify their email through expiring, single-use tokens stored only as hashes.
Administrators manage users, projects, files and application settings through the protected administration workspace.
The marketing site is static, has no application API connection and contains no authenticated project information.
Authenticated application