Morocco Law No. 09-08: declaration, prior authorization and international transfers
Choose the right CNDP form for each activity, assemble what the regulator asks for and check what must be in place before processing or transferring the data.
Organizations processing personal data within the territorial and material scope of Law No. 09-08. Check whether an overseas controller needs to notify a representative established in Morocco.
What you’ll produce
A signed filing decision, the submitted form and attachments, authority correspondence, and evidence that the live process matches the authorized or declared scope.
A sensitive use, national identity card number or matching of files can change the route. For a transfer authorization, CNDP requires approval of the underlying processing filing before it grants the transfer authorization.
What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Morocco CNDP data protection filings kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Choose the CNDP filing route · Local counsel + privacy lead + process owner [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which activities include a national identity number, sensitive data, criminal records or matching of files across purposes?
Can anyone outside Morocco access, back up or analyze the data, and what evidence do we have about the destination and safeguards?
Worked scenario
A Casablanca employer wants to move candidate and staff records to a hosted HR tool. HR maps the recruitment and employment workflows, Legal checks the conditions for the private-sector HR authorization form, and IT confirms the countries used for hosting and support. The team checks the transfer basis and, if authority approval is required, links that request to the HR filing before enabling overseas access.
Check obligations separately for operations in GDPR scope.
FROM THE SOURCE
Cases and numbers
CNDP deliberation · 11 April 2014
An HR filing covers a defined purpose
Deliberation 298-AU-2014 sets the model for private-sector HR authorization. For recruitment, the CNDP says employers should disclose possible external checks and give candidates a chance to explain discrepancies.
What to check Review the candidate notice, the actual screening workflow and the process for asking about a discrepancy before filing the HR dossier.
CNDP also lists an eight-day window to notify the filer if the activity needs prior authorization. When the dossier is incomplete, the windows start after the requested documents or information are supplied.
What to check Capture the formal receipt and monitor authority correspondence. Assign someone to stop the rollout if CNDP changes the filing route.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Choose the CNDP filing route
Who Local counsel + privacy lead + process ownerWhen Before the activity goes live
Break the project into actual processing purposes. Check scope and exemptions. Determine whether to prepare a normal declaration F211, simplified declaration F214, normal prior authorization F112, or decision-specific authorization F113. Check the current CNDP procedure for the named activity and document who can sign.
What to produce
Processing inventorySpreadsheet
Gather first
Interviews with product, operations and HR
System and vendor inventories
Applicable processing and recordkeeping rules
How to prepare it
Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.
Worked example
Fictional details. Use the same fields with evidence from your work.
Activity and purpose
P-014, send invoice receipts
Data and people
Billing email and amount for customer account contacts
Roles and basis to verify
Service company as controller. Contract analysis referenced in L-019.
Current CNDP procedures and applicable deliberations
How to prepare it
Write a separate row per activity. Record the purpose, categories of people and data, collection point, recipients and locations.
Check exemptions and authorization triggers. Compare the activity with any applicable decision before selecting the simplified or decision-specific route.
Record the form, legal basis, signer and hold point. Have counsel and the system owner verify the actual facts before filing.
Worked example
Fictional details. Use the same fields with evidence from your work.
Controller and activity
Fictional Atlas Market Maroc, employment and recruitment workflow.
Route considered
F113 under deliberation 298-AU-2014. Legal confirms whether all proposed HR purposes and data meet the decision’s scope.
Open item
IT must confirm overseas support locations. A separate transfer review is open even if the HR filing route is clear.
Release owner
Privacy lead records the route. Business sponsor approves rollout after filing and transfer gates are cleared.
Check before handing it over
The reader can reproduce the selected route from the facts and the cited CNDP procedure.
Give the signed decision and activity inventory to the authorized filer.
Who Authorized signatory + Privacy + project ownerWhen Before processing under a declaration or authorization route
Reconcile the form with notices, collection screens, controller records, legal basis, recipients, retention and vendor contracts. Attach signatory evidence and the route-specific documents. Track intake, formal receipt, supplemental requests and the applicable decision separately.
What to produce
CNDP application evidence sheetSpreadsheet
Gather first
Current prescribed form
Approved activity inventory
Signature authority
Notices and collection documents
Applicable consent or other legal basis
Processor contract
How to prepare it
Match each form answer and mandatory attachment to an owner. Check decision-specific fields and label the approved versions.
Reconcile stated purposes and recipients with the actual user screens, retention settings and vendor agreement. Bring unresolved differences to Legal.
Archive the signed form and attachments. Record the submitted date, any items requested by CNDP and the version sent in response.
Worked example
Fictional details. Use the same fields with evidence from your work.
Filing and evidence item
F113 HR dossier | employment document with data protection wording.
Document owner
HR supplies the dated contract model. Privacy compares notices, rights contact and purposes against the system.
Related items
Applicable candidate and intern materials, processor confidentiality clauses and the authorized signature record.
Status
Internal review open. Save the filed version and response record after submission.
Check before handing it over
A second filer can identify the correct form, confirm each mandatory attachment is complete and reproduce the submission.
Hand the approved form and attachments to the authorized signer. Keep the submission proof in the same case folder.
Log the submission date, completeness questions and formal outcome separately. Check whether CNDP required the declaration to move to prior authorization.
Compare the documented scope and any conditions with the go-live process. Verify each transfer separately.
Have Privacy and the release owner sign the decision. If a filing or transfer condition is open, state what stays disabled and who must clear it.
Worked example
Fictional details. Use the same fields with evidence from your work.
Decision
HR platform release on hold for overseas support. Keep that role disabled while Legal checks the transfer route.
Evidence to review
Formal processing authorization, transfer assessment and result, and proof the actual access settings match the permitted scope.
Sign-off
Legal and platform owner compare the filed purpose, data and destinations with the go-live configuration.
Change trigger
A new supplier, destination or collection purpose reopens the release decision.
Check before handing it over
The release owner can trace permissions to the formal filing and any separate transfer decision.
Send the signed release or hold record to the rollout lead before changing production settings.
Who Privacy counsel + Procurement + EngineeringWhen Before enabling access or sending data abroad
Map transfer countries, recipients, access methods and purposes. Assess the conditions in Articles 43 and 44 and the current CNDP country list. Where required, prepare F118, reference the underlying CNDP receipt or authorization, and document contracts or other safeguards and the transfer decision.
What to produce
CNDP cross-border transfer fileMemo
Gather first
Underlying filing receipt or authorization
Data flow and vendor support locations
Articles 43 and 44
Latest CNDP transfer procedure and F118
Contractual safeguards
How to prepare it
Record each destination and recipient, including routine support and backup copies. Verify the actual configuration with IT and the supplier.
Assess the applicable transfer basis and whether authorization is required. If filing F118, cite the underlying filing and attach the evidence called for by CNDP.
Record the authority outcome, if required, and compare it with actual access. Assign monitoring of changes to Procurement and the service owner.
Worked example
Fictional details. Use the same fields with evidence from your work.
Transfer
HR-03, proposed overseas support for the fictional Atlas Market Maroc recruitment system.
Evidence to collect
Provider’s actual support country and access workflow, named recipient, contract clauses and underlying HR filing reference.
Decision
On hold until the destination and transfer route are verified and any required CNDP decision is recorded.
Controls
Time-limited support role and access logging. Engineering verifies these limits before activation.
Check before handing it over
The record connects the destination, recipient, purpose and safeguards to the legal route and any decision required for release.
Give the approved transfer scope to Security, Procurement and the service owner before enabling access.
Log the submission date, completeness questions and formal outcome separately. Check whether CNDP required the declaration to move to prior authorization.
Compare the documented scope and any conditions with the go-live process. Verify each transfer separately.
Have Privacy and the release owner sign the decision. If a filing or transfer condition is open, state what stays disabled and who must clear it.
Worked example
Fictional details. Use the same fields with evidence from your work.
Decision
HR platform release on hold for overseas support. Keep that role disabled while Legal checks the transfer route.
Evidence to review
Formal processing authorization, transfer assessment and result, and proof the actual access settings match the permitted scope.
Sign-off
Legal and platform owner compare the filed purpose, data and destinations with the go-live configuration.
Change trigger
A new supplier, destination or collection purpose reopens the release decision.
Check before handing it over
The release owner can trace permissions to the formal filing and any separate transfer decision.
Send the signed release or hold record to the rollout lead before changing production settings.
Who Privacy operations + service ownerWhen After launch and before changing filed particulars
Maintain rights channels and match collection screens, retention, recipients and access to the filed position. Route a material change to Privacy to determine the required updated or new filing. Save earlier versions and proof of the authority’s response.
What to produce
Rights workflowMemo
Gather first
Covered rights and scope exceptions
Intake channels and identity verification rules
Systems, vendors and escalation contacts
How to prepare it
Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.
Worked example
Fictional details. Use the same fields with evidence from your work.
Trigger
A verified customer requests access through the support form.
Triage
Open a case and record receipt time, jurisdiction and deadline.
Handoffs
Billing and customer operations return records using restricted links.
Quality check
Reviewer checks redactions, exemptions and controller instructions where applicable.
Close
Send the response securely and save delivery evidence and date.
Check before handing it over
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.
Worked example
Fictional details. Use the same fields with evidence from your work.
Record ID
REQ-022
Event and date
Verified access request received 2026-11-07 UTC
Owner and target
Privacy operations, internal review by 2026-11-23
Decision and status
Approved response, sent securely
Completion evidence
Case delivery record, 2026-11-24
Follow-up
None, approved by the reviewer
Check before handing it over
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Work out whether you need controller registration, processor registration, or both. Prepare the e-DPO application, check the certificate, and set up renewals and change notices.