Introduction
Data Classification
Data categories and sensitivity levels processed by the SSM.ro platform
The SSM.ro platform classifies information by sensitivity levels in order to apply proportional security controls (access, encryption, retention, sharing).
Classification levels
| Level | Description | Examples |
|---|---|---|
| Public | Information intended for the public; disclosure causes no harm | Marketing pages, public documentation, terms and conditions |
| Internal | Internal operational information; access limited to staff | Configurations, internal technical documentation, operational metrics |
| Confidential | Sensitive business or security information; disclosure may cause harm | Architecture diagrams, risk register, SOPs, audit reports |
| Personal data | Data identifying a natural person, protected under GDPR | Name, email, phone, employer, employee badge |
| Sensitive / special personal data | National identifiers, exceptionally required for issuing qualified certificates | CNP, ID card series/number, ID card copy |
Platform data mapping
| Data type | Classification | Location | Main controls |
|---|---|---|---|
| Digital document content | Confidential / personal data | AWS S3 (SSE, versioning, Block Public Access) | Access only via authenticated API; per-organization isolation |
| Employee data (name, contact, badge) | Personal data | Heroku Postgres (encrypted at rest) | Server-side RBAC; tenant isolation |
| Data sent for signing (document hash) | Confidential | Transmitted to the signature provider (eIDAS QTSP); typically only the document hash, full document only if the provider requires full transmission | mTLS or API token; minimization |
| Identification data (CNP, ID card series/number) | Sensitive personal data | Transmitted to the provider exceptionally, only for one-time issuance of a qualified certificate when the client supplies the identity; not used in the standard advanced signature flow | mTLS or API token; minimization; dedicated processing basis |
| Client activity logs | Internal / personal data | Heroku Postgres (3 months) | Super User access; self-service export |
| Signature audit trail | Confidential | AWS CloudWatch Logs (5 years, append-only) | IAM-restricted; encrypted |
| Compliance documents (DPIA, risk register) | Confidential | Provided on request, under NDA | Controlled external distribution |
Handling principles
- Minimization — only the data necessary for the stated purpose is processed (see Privacy Policy).
- Encryption — confidential and personal data are encrypted in transit (TLS 1.2+) and at rest.
- Isolation — each organization's (tenant's) data is logically isolated at the query level in both models; in the Enterprise model, the infrastructure is additionally physically dedicated per client.
- Retention — each category has a defined retention window (see Data Retention and Deletion).
- Confidential documents — distributed externally only under NDA, as part of audit processes.