GDPR
Back office → GDPR. It needs its own permission, separate from administering everything else.
Who a data subject is
Not just an account. A subject is assembled from everything the platform knows: a partner, a contact, an email address, a user account, an employee record. Somebody who never signed in but appears in your HR records is a subject.
Export
A subject's data, gathered and handed over in a readable form.
Mail export is organization-level only
Personal mailboxes are not included, and cannot be. The privacy rule that says a personal mailbox belongs to its owner does not bend for an export request — an export that reads staff mail would be a breach committed in the name of compliance.
Erasure
Erasure anonymises rather than deletes: the person disappears, the business records that must survive do not. Revisions and change logs that would otherwise carry the old values are cleared too — an anonymisation that leaves the name in the revision history has not anonymised anything.
Documents under a legal retention obligation are never erased. They are marked retained, and the reason is recorded.
Consent
Consent is recorded with what it was for and when it was given. Marketing mail is opt-in and cannot be configured otherwise.
Cookies
Visitors are asked before anything optional is set. Analytics and similar run only behind that consent — the consent is the switch, not a banner over a switch that was already on.
Public /gdpr and /cookies pages come with the platform, in English and
Slovak, and are yours to edit.
Records of processing
The register of what you process, why, on what basis and for how long. It is maintained here rather than in a document somebody keeps on a laptop.
Retention
Retention periods are configured per kind of data and enforced by a scheduled job. Data past its period is removed automatically, except what is retained by law.