Pular para o conteúdo

Crivora · Access Control Policy

Access Control

Who can access what at Crivora, and how that access is granted, reviewed and revoked.

Policy owner
Crivora
Effective date
Last reviewed
Review cadence
at least annually and when material changes occur
Version
1.0
URL
https://usecrivora.com/security/access-control/en
Versão em português

1. Scope

Applies to Crivora user accounts, internal app functions and administrative accounts of the providers used in operations (hosting, database, source code repository, email, payments and integrations).

2. Principles

  • Unique accounts: each person uses their own account; generic or shared accounts are not allowed.
  • Authentication is required for any non-public area.
  • Least privilege and need-to-know: each account receives only the access its role requires.
  • Credentials are personal and never shared, including over chat or email.

3. App users

  • Each user can access only their own data; isolation is enforced on the server for every query and file.
  • Passwords are stored only as bcrypt hashes.
  • Sessions use HttpOnly, Secure and SameSite cookies.

4. Privileged access

  • Internal and administrative app functions are restricted to an authorized user configured on the server or to server-side secrets; without that configuration they are unavailable.
  • Administrative accounts of critical providers (hosting, source code, email, payments and integrations) are restricted to the technical owner and must use multi-factor authentication.
  • Integrations use only the scopes they need (for example, read access to TikTok Shop rankings).

5. Granting, review and revocation

  • Privileged access is granted only by the technical owner, for a defined need.
  • Privileged access and authorized integrations are reviewed at least annually and whenever a role, provider or integration changes.
  • Access that is no longer needed is revoked, and associated credentials are rotated where applicable.
  • Integration tokens can be revoked by the holder at the provider; the integration then requires a new authorization.

6. Contact

Questions about this policy: contato@usecrivora.com.