Privacy runs on clocks you don't control
Every other compliance discipline runs on a cycle you schedule. Privacy runs on inbound triggers with hard deadlines: 72 hours from a breach you didn't plan for, 30 days from a request that arrived in an inbox nobody watches. Govrly holds the records those clocks depend on, connected to the controls that protect them.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What are privacy operations?
From the compliance programmes we build and run in Saudi Arabia: privacy operations are the day-to-day running of a data protection programme: maintaining a record of what personal data you hold and why, documenting the lawful basis for each processing activity, answering data subject requests within the deadline, assessing breaches against the notification window, and recording every cross-border transfer with its justification.
This is distinct from knowing what the law requires. Understanding the Saudi PDPL is a reading exercise; running privacy operations is a records exercise, and it is where enforcement findings actually land. The published enforcement decisions have not turned on sophisticated legal argument — they have turned on missing records.
The operational difficulty is that privacy is reactive in a way the rest of compliance is not. You choose when to run a gap assessment. You do not choose when someone submits a deletion request, and you certainly do not choose when a breach occurs.
Everything depends on the inventory
Each layer below rests on the one above it. Teams we work with that start at the bottom — writing a privacy notice first — end up describing a programme they cannot actually operate.
What personal data you hold, where it sits, why you process it, who it is shared with, and how long it is kept. Without this, none of the layers below can be answered honestly — and it is the artefact most often missing when an investigation opens.
Identified and documented for each processing activity, not assumed across the organisation. Where consent is the basis, it needs to be captured in a form you could actually evidence.
A team cannot answer an access or deletion request within 30 days if you do not know which systems hold that person's data. The inventory is what makes the deadline achievable rather than aspirational.
Assessing impact within 72 hours requires knowing what data the affected system held. Without an inventory, the first hours of the window are spent establishing what was even at risk.
Which vendors touch which data categories, where it goes, under what mechanism, and with what assessment behind the decision. A processor moving data outside the Kingdom is still your transfer.
Defined periods per activity, and evidence that data is actually deleted when they expire. Retaining data past its purpose is a finding, and it enlarges every breach that follows.
The clocks, and when they actually start
Most missed deadlines are not missed at the end. They are missed at the beginning, because nobody noticed the clock had started.
This page describes operational practice, not legal advice. Confirm the deadlines and conditions applying to your organisation with counsel, and against current SDAIA guidance.
| Trigger | Deadline | When the clock actually starts |
|---|---|---|
| Personal data breach | 72 hours | On becoming aware — which happens at the operational level, not when it reaches the privacy team. Without an escalation path, most of the window is consumed by internal triage. |
| Data subject request | 30 days | On receipt — including a request sent to a general inbox, a support ticket, or a branch. Requests rarely arrive through the channel you designed for them. |
| Harmful breach | Without delay | Affected individuals must also be notified where the breach may cause them harm, separately from the regulator notification. |
| New processing activity | Before launch | Lawful basis, inventory entry, and retention period established before processing begins — not documented retrospectively after the service is live. |
| Cross-border transfer | Before transfer | Conditions and any required assessment addressed before data leaves the Kingdom, with the reasoning recorded at the time. |
Where privacy operations fail
- 01/07The notice describes intent, the records describe nothing
A published privacy notice says what the organisation intends to do. Without records of processing, nothing establishes what it actually does — and the notice becomes a statement nobody can substantiate.
- 02/07Consent was collected but never logged
Marketing consent in particular has to be demonstrable: who consented, to what, and when. An unlogged consent is functionally indistinguishable from no consent.
- 03/07Requests arrive through unmonitored channels
A deletion request sent to a general inbox still starts the 30-day clock. Missed requests generate complaints, and complaints are how a large share of investigations begin.
- 04/07The 72-hour window is spent finding out what happened
Without an inventory, the first day is establishing which systems were involved and what data they held — before assessment can even start.
- 05/07Transfers happen through processors nobody mapped
A vendor moving data outside the Kingdom is still your transfer. Without vendor records linked to data categories, this stays invisible until it is discovered externally.
- 06/07Retention periods exist on paper only
Defined in a policy, never enforced in a system. Data that should have been deleted three years ago is still there, and it is in scope for every request and every breach.
- 07/07Privacy runs separately from security
The technical and organisational measures privacy requires are the same controls your cybersecurity framework already governs. Two programmes produce two incomplete evidence sets instead of one complete one.
Privacy operations in Govrly
Privacy records sit alongside your controls, evidence, vendors, and risks — because the safeguards privacy demands are the safeguards your security programme already runs.
Privacy operations is one use case. The control library, risk register and audit lifecycle, evidence workflow, and vendor assessments draw on the same underlying records — linked below rather than duplicated here.
What you hold, where, why, on what basis, with whom it is shared, and for how long — maintained as a live record rather than an annual spreadsheet exercise.
Documented against each processing activity individually, with consent records where consent is the basis relied upon.
Logged from intake, routed to an owner, tracked against the 30-day deadline, and closed with a record of exactly what was provided.
Incidents raised, assessed against the notification threshold, and tracked within 72 hours — with the decision reasoning preserved rather than reconstructed later.
Destination, mechanism, data categories, and the assessment behind each decision, retrievable when the regulator asks rather than rebuilt on request.
The access control, encryption, and logging behind your privacy obligations are the same records carrying your NCA ECC or SAMA CSF requirements. Implement once, evidence once.
Privacy and security ask different questions of the same controls
This is why running them as separate programmes is expensive rather than thorough.
Same control, same owner, same evidence — two sets of questions answered from one implementation rather than two parallel programmes producing partial answers.
| Control | Security asks | Privacy asks |
|---|---|---|
| Access control | Is access restricted to authorised users? | Is access limited to those with a lawful purpose for this data? |
| Encryption | Is data protected in transit and at rest? | Are the safeguards appropriate to the sensitivity of the personal data? |
| Logging | Can we detect and investigate an incident? | Can we establish what personal data was affected, and by whom? |
| Asset inventory | What systems do we operate? | Which of them hold personal data, and which categories? |
| Vendor management | Does this supplier meet our security bar? | What personal data do they process, and where does it go? |
| Deletion | Is media securely disposed of? | Is data deleted when its retention period expires or a request requires it? |
Standing up privacy operations
Sequence matters more here than in any other use case, because the clocks do not wait for you to be ready.
- 01/07Build the inventory before anything else
Every other obligation depends on knowing what personal data exists, where, and why. Starting anywhere else produces a programme you cannot operate under time pressure.
- 02/07Document lawful basis per activity
Not per department and not organisation-wide. Where consent is relied on, confirm it is captured in a form you could produce on request.
- 03/07Open a monitored intake channel
One route, watched, with a named owner and a tracked clock. Then test it with an internal request before a real one arrives.
- 04/07Rehearse the 72-hour path
Define what triggers assessment, who decides, and how the regulator is notified. A tabletop exercise is worth more here than a written procedure, because the failure mode is hesitation rather than ignorance.
- 05/07Map processors to data categories
Which vendor touches which data, where it goes, and under what mechanism. This is usually the largest blind spot.
- 06/07Make retention operational
A period defined in a policy but never enforced in a system is not a retention control. Evidence of actual deletion is what closes it.
- 07/07Connect privacy to the security programme
Link the technical and organisational measures to the controls your cybersecurity framework already governs, so one evidence set serves both obligations.
Privacy operations — FAQs
The day-to-day running of a data protection programme: maintaining a record of what personal data you hold and why, documenting the lawful basis for each processing activity, answering data subject requests within the deadline, assessing breaches against the notification window, and recording every cross-border transfer with its justification.
A maintained inventory of what personal data the organisation holds, where it sits, why it is processed, the lawful basis for each activity, who it is shared with, and how long it is retained. It is the foundation every other privacy obligation rests on, and the artefact most often missing when an investigation opens.
Because the deadlines depend on it. A team cannot answer an access or deletion request within 30 days if you do not know which systems hold that person's data, and you cannot assess a breach within 72 hours if you do not know what the affected system contained. Without an inventory, the early part of every deadline is spent establishing basic facts.
On becoming aware of the breach — and awareness begins at the operational level, not when the news reaches the privacy team. Without a defined escalation path from the people who notice first, a significant part of the window is consumed by internal triage before assessment even begins.
On receipt, including requests that arrive through channels you did not design for them — a general inbox, a support ticket, a branch, or a social media message. Requests rarely arrive through the official route, which is why a single monitored intake channel matters more than a well-drafted procedure.
No, and separating them is usually counterproductive. The technical and organisational measures privacy requires — access control, encryption, logging, deletion — are the same controls a cybersecurity framework already governs. Running two programmes produces two incomplete evidence sets rather than one complete one.
In a form that is demonstrable: who consented, to what specific processing, when, and by what method. Marketing consent in particular attracts attention. An unlogged consent is functionally indistinguishable from no consent when someone asks you to produce it.
The destination, the data categories involved, the mechanism relied upon, and the assessment behind the decision — recorded at the time the decision is made rather than reconstructed when the regulator asks. This includes transfers made by processors acting on your behalf.
That page explains what the law requires — scope, obligations, penalties, and how it compares to GDPR. This page is about running the operation: the records, workflows, and clocks that turn those requirements into something you can actually demonstrate on the day you are asked.
Yes. The underlying records — processing activities, lawful basis, rights requests, breach decisions, transfers, retention — serve both regimes, with each keeping its own definitions and reporting. Organisations subject to both find most of the operational work is shared even though the legal requirements differ.
Have the records before the clock starts
Inventory, lawful basis, rights requests, breach decisions, and transfers — connected to the controls that protect them.
