Crivora · Data Classification Policy
Data Classification
How Crivora classifies data and which protections each level requires.
- Policy owner
- Crivora
- Effective date
- Last reviewed
- Review cadence
- at least annually and when material changes occur
- Version
- 1.0
- Contact
- contato@usecrivora.com
- URL
- https://usecrivora.com/security/data-classification/en
1. Levels
| Level | Examples | Requirements |
|---|---|---|
| PUBLIC | Website pages, published policies, public product information. | May be published. Changes are reviewed before publishing. |
| INTERNAL | Operational metrics, usage counts, internal documentation. | Restricted to the team; not published. |
| CONFIDENTIAL | Account data (name, email), projects, uploaded and generated images, subscription data, stored market data. | Authenticated access restricted to the owner and the technical owner; HTTPS-only transport; per-account isolation on the server; stored only on hosting infrastructure with provider-declared encryption at rest; not exposed in logs. |
| RESTRICTED | Password hashes, API credentials, OAuth tokens, app secrets, encryption keys, payment and webhook secrets. | Server-side only; never in the browser, source control or logs; OAuth tokens encrypted at rest (AES-256-GCM); passwords stored only as hashes; rotated on suspected exposure. |
2. General rules
- When in doubt, the higher level applies.
- Data is collected and kept only when needed for its purpose (see /security/data-protection/en).
- Encryption in transit (HTTPS) applies to every level transmitted over the internet.
- At rest: the application encrypts OAuth tokens (AES-256-GCM) and stores passwords only as hashes; the database and files run on Hostinger hosting, whose DPA declares encryption at rest of personal and sensitive data (databases, shared directories). Crivora does not directly manage that infrastructure encryption.
Crivora · Data Classification · https://usecrivora.com/security/data-classification/en · contato@usecrivora.com