Security & trust

Clear handling of sensitive financial work.

An analyst needs to know where information goes, who can access it and how a report is produced. These are the controls and operating choices currently described for MiyarLens.

AI runs server-side

Claude is called from the server. The provider key and prompt templates do not reach the browser; usage is logged as metadata only.

Sign-in and passwords

Passwords are hashed with BCrypt. Sessions use token-based authentication and login attempts are rate-limited.

Access control and audit

User and admin roles are separate. The admin audit log records old and new values for administrative changes.

Cloud hosting

The platform runs on Google Cloud using Cloud Run and Cloud SQL. Credentials are kept in Secret Manager.

Data retention

A written data-retention policy is in place. Ask for the policy when reviewing a deployment or procurement.

Roadmap

SSO and MFA

Single sign-on and multi-factor authentication are on the roadmap; they are not presented here as current capabilities.

We'll answer with the relevant implementation details rather than a generic checklist.

Have a security or procurement question?