Trust and technical due diligence

• Auth.js sessions and bcrypt-hashed passwords.
• Role-based permissions enforced in the service layer, not only in the interface.
• Tenant queries are organization-scoped; department managers are additionally department-scoped.

• No advertising analytics, behavioral tracking SDKs, or external data sharing in core workflows.
• Evidence files remain outside public paths and require authorization to download.
• Public proof profiles exclude email, drafts, feedback, and internal activity.

Read the privacy policy →

• Sensitive actions are recorded in an organization audit trail.
• A work owner cannot review their own submission or issue their own readiness decision.
• Credentials are tied to a published role standard, accepted proof, and a recorded decision.

• Supports on-premise, private VPC, or a single-server pilot deployment.
• Core workflows run on Next.js and MySQL without a required paid external service.
• Container runtimes are optional and disabled by default; guided simulation is the safe baseline.

• Rate limits cover authentication, evidence uploads, and report exports.
• Evidence uploads validate extension, MIME type, file signature, and size.
• Security headers and CSP restrict framing and external analytics connections.

• Enterprise SSO and full directory synchronization are not currently delivered.
• The current rate limiter is in-memory; multi-node deployment needs a shared store such as Redis.
• Files are local by default; high availability needs shared persistent storage and a backup policy.
• The platform supports promotion or mobility decisions; it does not automate them.