Personal data compliance in one auditable flow.
Personal data obligations repeat on a fixed rhythm: a new processing activity starts, a consent needs documenting, a data subject asks what you hold, a breach requires a regulator notice within 72 hours. Each of those moments has a deadline and a paper trail requirement. Tenderely BPM turns those recurring obligations into structured steps that run on time, stay traceable and do not depend on one person's memory.
What does a data compliance function repeat?
01
Keeping the processing inventory current
Every time a new tool, vendor or activity touches personal data, the inventory needs an update. When this lives in a spreadsheet, versions drift and the picture is always slightly out of date.
02
Recording data transfers
Transfers to processors, sub-processors and cross-border recipients each require a record of what was shared, with whom and on what legal basis. Without a structured record, the question is unanswerable.
03
Managing privacy notices and consent
Notice texts change. When a version changes, the old text must be archived and the individuals who consented under it must be identifiable. A copy in a document folder is not a version history.
04
Responding to data-subject requests
Access, correction, erasure and portability requests each have a legal deadline, usually 30 days. Tracking them in an inbox means the deadline is only visible if someone remembers to check.
05
Notifying a breach within 72 hours
A personal data breach triggers a mandatory regulatory notification window that starts counting the moment the incident is detected. Missing it is a separate violation on top of the breach itself.
06
Documenting erasure and destruction
Retention schedules reach their end date, and the destruction of data must be recorded. Periodic erasure cycles without a record are indistinguishable from cycles that never happened.
Where does this break down today?
The inventory is a spreadsheet nobody trusts
It was accurate on the day it was written. Since then three vendors changed, two new processes started and a tool was retired. The document stayed the same and has quietly become fiction.
Subject requests are tracked in an inbox
A request arrives by e-mail. It is forwarded, it waits, it is followed up and eventually answered — or not. The 30-day clock runs regardless, and there is no view of which requests are still open.
Consent records are not linked to notice versions
Knowing that a person consented is not enough. You also need to know which version of the notice they read when they did. Without that link, the consent record does not hold up.
A breach triggers a scramble
When an incident happens, the team discovers that the notification checklist is in a document, the contact details for the regulator are elsewhere and nobody is certain what was exposed. The 72-hour window narrows while people search.
What changes with Tenderely BPM
01
The inventory is a living record
Each processing activity is a structured record with its own status, legal basis, retention period and responsible owner. Adding or retiring an activity creates a timestamped entry, not an edited cell.
02
Consent is tied to the notice version
When a notice is updated, the old version is archived automatically. A consent record carries a reference to the exact version in force when it was given, so the link is unambiguous.
03
Subject requests run to a deadline
Each request opens a timed step. Tenderely BPM sends a reminder when the response window is approaching, so the 30-day obligation is visible without anyone having to count backwards from an e-mail date.
04
Breach response is a guided flow
An incident opens a structured record that walks the team through assessment, containment and notification steps. The 72-hour window is an SLA on the notification step, not a date in someone's head.
05
It connects to the person record you already have
The module binds to the person form already in your workspace — patient, employee, customer or any other — so subject requests and consent records are linked directly to the people they concern.
06
Audit evidence is always ready
Every record carries a full history of who acted, what they changed and when. When a regulator asks for evidence of a process, the answer is a report, not a reconstruction.
FAQ
Does this work for any sector, not just healthcare or finance?
+
Yes. The module is sector-independent. It installs alongside whichever sector or process packages you already use and binds to the person record in your workspace, whatever that person type is — customer, patient, employee, student or subscriber.
How does the module handle the 72-hour breach notification requirement?
+
An incident record opens a structured flow. The notification step carries a 72-hour SLA from the moment the incident is logged. The platform sends reminders as the window narrows, and the step cannot be completed without the required fields being filled in. The completed record is the evidence that the obligation was met.
Can data subjects submit requests from outside our system?
+
Yes. A public form can be published as a link or embedded on your website. A person who submits a request through it creates a record inside your workspace without needing an account. The 30-day response clock starts from submission.
Who can see consent records and processing inventory entries?
+
Role-based and field-level permissions control access. The compliance officer can see everything; a department head can be limited to the processing activities their team owns; individual consent records can be restricted to roles that have a legitimate need. Every access to a sensitive record is logged.
What happens when a privacy notice changes?
+
The previous version is archived as a dated record and a new version record is created. Any consent given under the old version remains linked to it, so you can always identify which individuals consented under which text — which is exactly what an audit or a subject-access request requires.