Security

How Cernia handles access, credentials and changes.

Access. Sign-in by email link, Google or Microsoft; organizations are isolated at the database with row-level policies; roles are owner, approver, analyst and viewer.

Credentials. Granted through each platform's own sign-in where offered, entered once where not; encrypted at rest with a key Cernia controls; decrypted only inside the request that uses them; never logged, never in a report or a message; read and write grants are separate.

Changes to your platforms. Every change is a plan with an ID, a hash and an expiry; an approver says yes to the plan; each field is re-read before it is written; a rollback plan exists before the first change; nothing is deleted; budgets, bids and targeting are not changed until you enable it.

Audit. Every read of your data, every plan, approval, apply, rollback and credential use is logged with who, what and when, and is available to your owners.

Models. Answers run on the model you choose, on Cernia's account or your own key. Platform rows are summarised by scripts before a model reads them.

Questions: security@cernia.ai.