Administration and Security

Privacy controls

The privacy controls Ottili ONE gives your company: GDPR data-subject rights, company-scoped tenant isolation, encryption, account and data security, sub-processor transparency, the Data Processing Agreement (DPA) and clear status labels.

Overview

Privacy is not an option in Ottili ONE — it is part of the shared control plane. Ottili ONE is built for the GDPR (EU General Data Protection Regulation): personal data is processed strictly company-scoped, and your company keeps control over its data — who sees it, how it is stored, and when it is deleted.

This article summarises the privacy controls Ottili ONE offers today, and clearly distinguishes between Live, Beta, Private Beta, In Development, Planned and Concept. Deeper articles are linked at the end under [Related articles](#related-articles).

GDPR data-subject rights

Through the Backup and Data Export Center*, authorised company administrators can exercise GDPR data-subject rights for your company's data:

Right to data portability:* Export your company data (e.g. CSV, JSON) for your own archiving or to transfer it to another provider.
Right to erasure:* Create and track GDPR data requests for backup and erasure. Erasure is company-scoped and happens within the correct tenant boundary — it affects only your company's data.
Traceability:* Every export or erasure action produces a company-scoped audit event.

Details and exact steps are in [Data retention](/docs/data-retention).

Company-scoped tenant isolation

Your data stays yours — and another company's data stays theirs. Ottili ONE is company-scoped:

Fail-closed check:* The shared assert_same_company() function rejects any request without or with the wrong company context.
Database row-level security (RLS):* PostgreSQL filters every platform row by the verified company_id; the runtime default is deny-by-default.
No cross-tenant:* One company can never read or modify another company's data.

More in [Tenant isolation](/docs/tenant-isolation).

Encryption (at rest and in transit)

Ottili ONE applies encrypted storage and transport:

Passwords:* User passwords are hashed with Argon2id*; Ottili ONE never stores plaintext passwords.
JWT access tokens:* Ottili ONE issues signed JWT access tokens (HS256*) and verifies them on every authenticated request.
Encryption at rest:* Backups can be encrypted at rest with AES-256-GCM* when backup encryption is enabled and a passphrase is configured (configuration-dependent / opt-in).
Transport (TLS):* Service-to-service traffic verifies TLS/SSL certificates; outbound mail uses STARTTLS when enabled. Public website traffic is secured through the platform gateway (Caddy).

Session, token-rotation and further details are in [Account and data security](/docs/account-and-data-security).

Account and data security

Privacy starts with access. Ottili ONE provides controlled identity:

Second factor:* Where enabled, Passkeys (WebAuthn)* and Multi-Factor Authentication (TOTP)* add a second verification step.
Sessions:* Sessions expire after an idle period and an absolute maximum lifetime; both are configurable by your organisation.
Secrets management:* All configuration and integration secrets are injected via environment variables and validated at startup; sensitive fields are masked during inspection.

More in [Secrets management](/docs/secrets-management) and [Account and data security](/docs/account-and-data-security).

Sub-processors and the Data Processing Agreement (DPA)

When Ottili ONE uses external services on behalf of your company, it does so transparently:

Sub-processors:* A published sub-processor list documents which processors handle personal data.
Data Processing Agreement (DPA):* Ottili ONE provides a Data Processing Agreement.
Public transparency:* This information is available via the public privacy pages (e.g. ottili.one/legal/data-processing).

Consent and cookies

On the public Ottili websites you manage consent and cookies through the privacy and cookie notices provided there. The public privacy policy is available at ottili.one/legal/privacy (German: ottili.one/legal/datenschutz); cookie settings are at ottili.one/legal/cookies.

Certifications and compliance status

Ottili ONE is built for privacy. The current status, maintained in the Product Truth registry:

GDPR (EU data protection):* Referenced — Ottili ONE is designed for the GDPR (data-subject rights, lawful bases, erasure limits, sub-processor transparency).
SOC 2 Type II:* Planned — no attestation completed yet; we do not claim this certification.
ISO/IEC 27001:* Planned — alignment is planned; Ottili is not yet certified.
ISO/IEC 27017:* Not held — we do not claim this certification.

Claims that are not yet verified are never presented as certified.

Status labels

Ottili ONE clearly distinguishes between Live, Beta, Private Beta, In Development, Planned and Concept. What these terms mean is described in [Understand feature status labels](/docs/understand-feature-status-labels).

[Account and data security](/docs/account-and-data-security) — authentication, sessions, isolation, audit.
[Data retention](/docs/data-retention) — storage, export, GDPR erasure.
[Tenant isolation](/docs/tenant-isolation) — why your data stays isolated.
[Secrets management](/docs/secrets-management) — how sensitive values are managed.
[Audit logs](/docs/audit-logs) — traceable, company-scoped logs.
[Security overview](/docs/security-overview) — how the security architecture fits together.
[Understand feature status labels](/docs/understand-feature-status-labels) — what the status terms mean.
[Company administration](/docs/company-administration) — manage roles and access.

Was this article helpful?