PProven PortalsBack to home

Legal and trust

Trust and security

Access

Users sign in with a short-lived email link. Roles set what a person may do. Grants set which account, team, property, job, or file that person may see. The server and database both check access.

Data safety

Web traffic uses TLS. Files use private storage and short-lived links. Secret keys stay on the server. Browser security headers block common framing, content, and data risks. We use vendors that provide controls needed to run the service.

AI and key actions

The built-in helper may read only data the signed-in user may read. It does not get a service key. It cannot bypass access checks. Key steps such as access changes, approvals, signing, billing, and deletion need clear user action.

Logs, upkeep, and response

We log key account and access changes. We check code, packages, access rules, and production health. We keep an incident plan and will tell affected clients as required by law and contract. No service can promise zero risk.

Report a problem

Email security@provenportals.com. Do not send a password, secret key, or client file in the first note. Tell us what you found and how to reach you. We will confirm the report and work to fix valid issues.