TRUST ATLAS WORKSHEET
CNDP release decision
Morocco CNDP data protection filings · Step 3 · Review every transfer out of Morocco- Who prepares it
- Privacy counsel + Procurement + Engineering
- When to prepare it
- Before enabling access or sending data abroad
Worked example
This example uses 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.
Gather first
- Declared or authorized scope
- Authority responses, formal receipt or decision
- Transfer file
- Technical readiness checks
How to prepare it
- 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.
Review
The release owner can trace permissions to the formal filing and any separate transfer decision.
Handoff
Send the signed release or hold record to the rollout lead before changing production settings.