Account · Security

Account security

Managed authentication, protected sessions and safe habits.

Last updated · 9 September 2026 · Version 3.0

Account features depend on the active Cevor product. This page describes the security model without promising a particular sign-in method on every platform.

1. Authentication

Cevor uses managed authentication. Available sign-in methods may include email credentials, secure links, codes or supported identity providers. Session tokens are stored by the client to keep a user signed in.

2. Access controls

Database policies and server-side role checks restrict protected records. Restaurant access also requires separate authorization and association; an account alone does not grant Business access.

3. Sessions and devices

Cevor and its authentication provider process session and security information needed to maintain access and investigate abuse. Session lifetime and sign-out controls depend on the current client and provider configuration.

4. Your responsibilities

Protect the email account or identity provider used to sign in.
Do not share passwords, codes or session links.
Sign out on shared devices and report suspicious access.

5. Incidents and limits

Cevor investigates credible reports and follows applicable breach-notification law. No system is risk-free, and Cevor does not claim a formal security certification on this page.

Contact

For questions, write to hello@cevor.app