Commission de Protection des Données Personnelles (CDP)
Timing
File before covered processing. Article 18 gives CDP one month to issue the declaration receipt, with one reasoned extension possible. Article 23 gives two months from receipt for opinion or authorization requests and also allows one reasoned extension.
Reviewed
Inside this guide
4 steps · 8 templates
Who it applies to
Public and private controllers within Law No. 2008-12. Review the exemption, authorization and public-service rules for each activity and confirm local representation where applicable.
What you’ll produce
A documented filing route, submitted forms and evidence, the authorized or declared scope, and a process for reporting changes or ending the activity.
A filing acknowledgment and the formal declaration receipt serve different purposes. CDP has a transfer filing form. Check Articles 49 to 51 and how the regulator applies them before enabling overseas access or storage.
Who can stop a feature or an overseas access change?
Name a rollout owner and a Privacy approver. Give Security the power to leave facial matching, new recipient access or overseas support disabled while a filing or transfer decision is open.
Which document lets each activity start?
Require the project lead to list each activity’s route and the corresponding authority document or counsel-reviewed basis. Keep the delivery acknowledgment separate from the declaration receipt and other decisions.
Who sees changes early enough to refile?
Route planned changes to data fields, retention, recipients and access locations to Privacy through the normal change approval. Give the filer a backup owner and access to the regulator’s correspondence.
How to spend the first week
Walk the warehouse, clinic or service desk with the people who run it. Compare documented purposes with what staff can collect or see in the actual system.
Pull the current route forms and assign each Article 22 field to a person who can supply evidence. Confirm who can sign or act for the controller.
Ask the provider to demonstrate the countries where it can store, back up and access personal data. Record open decisions against the project’s rollout tasks.
What to review each week
List activities by filing route and responsible owner. Include receipt dates, extensions, open decisions, unresolved access locations and outstanding notices for changed or retired processing.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Senegal CDP 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 a filing route for each activity · Privacy lead + Senegalese counsel + system 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. Walk the warehouse, clinic or service desk with the people who run it. Compare documented purposes with what staff can collect or see in the actual system.
2. Pull the current route forms and assign each Article 22 field to a person who can supply evidence. Confirm who can sign or act for the controller.
3. Ask the provider to demonstrate the countries where it can store, back up and access personal data. Record open decisions against the project’s rollout tasks.
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
Does the activity use biometrics, a national identifier, genetic data, a health research dataset, records of offences or interconnections between files?
Where can the supplier or its subcontractors access the data, and what must the business receive or document before activating it?
Worked scenario
A Dakar distributor plans badge access and cameras at its warehouse. The facility lead marks each camera’s field of view and notices that the vendor has enabled facial recognition. Legal assesses the resulting biometric route, and IT checks whether the supplier can review footage abroad. The rollout owner holds each open part of the project until its filing and transfer conditions are resolved.
Compare the filing routes when the same supplier also serves Morocco.
FROM THE SOURCE
Cases and numbers
CDP quarterly report · January to March 2025
105Files handled in the first quarter of 2025
What passed through the regulator in one quarter
The CDP counted 83 declarations, 19 authorization requests and three files brought back for review. It separately reported issuing 78 declaration receipts and 21 authorizations across two plenary sessions.
What to check Track intake, receipt, authorization and follow-up separately. Compare outcomes only for filings whose later decisions you can match back to the same requests.
Facial recognition went beyond the stated CCTV purpose
The CDP reported refusing to issue a receipt for Harmony Beverages SARL’s CCTV system because facial recognition was excessive for the stated purposes, which included protecting people, property and the building surroundings.
What to check Record the features enabled in the actual camera system and how each supports its stated purpose. Document the test configuration and reevaluate if the supplier proposes facial matching.
Article 23 provides for a deemed favorable authorization if CDP is silent after the applicable period. Verify receipt, extensions and how the rule applies to the actual request before relying on it.
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 a filing route for each activity
Who Privacy lead + Senegalese counsel + system ownerWhen Before collecting or changing covered personal data
Map purposes, operators and data. Check Article 17 exemptions, Article 19 simplified routes and Article 20 prior authorization triggers. For a listed automated public-service use, check the Article 21 opinion and regulatory-act route. Document the chosen form and the eligible filer.
How to do this step
Before you start
Live system walkthrough, data fields, legal entity list, public-service mandate if applicable, and vendor scope.
Split the project by purpose and actual data used. Mark separate features, especially national identifiers, facial matching and file connections.
Check Articles 17 to 21 and the relevant authority forms. Have local counsel verify the filing route for each feature and whether a representative can sign.
Give the system owner the approved scope and any open holds. Keep the selected legal provisions alongside the observations that support the route.
What a reviewer should see
A dated route memo links the actual configuration to its statutory trigger, form, filer and release condition.
When to escalate
Escalate a proposed simplified route where enabled features or data indicate prior authorization.
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.
List each purpose and the settings that implement it. Check biometrics, national identifiers, criminal information, health research and file connections against Article 20.
Compare exemptions, simplified forms and any public-service route with the actual facts. Decide whether distinct activities need distinct filings.
Write the chosen form, source, signatory, accountable reviewer and document needed before rollout. Record features that remain disabled pending review.
Worked example
Fictional details. Use the same fields with evidence from your work.
Organization and activity
Fictional Niokolo Distribution, a Dakar warehouse using badges and security cameras.
Route and rationale
Assess badge access and cameras against their applicable CDP forms. Facial recognition remains disabled pending a separate Article 20 assessment.
Inputs to check
Camera views, retention, visitor and staff notices, vendor support location, role access and the actual toggles in the camera system.
Decision owner
Senegalese counsel reviews the filing routes. Security supplies dated screenshots and agrees who can change feature settings.
Check before handing it over
Each route follows the enabled features and actual uses. A reviewer can identify the trigger, form, signer and release condition.
Give the signed decision to the filer and the feature limits to the rollout owner.
Who Privacy lead + authorized filer + SecurityWhen Before initiating the covered activity
Select the current CDP form, reconcile the Article 22 particulars with the system and attach route evidence. Include controller or representative identity, actual collection, retention, access, recipients, rights contact, suppliers and transfers. Save the exact submitted version and proof of receipt.
Trace each field on the form to a named owner and a verified answer. Use redacted or test records to show what the system collects and who can inspect it.
Resolve differences among the contract, system and description before signing. Archive the bundle and proof of delivery.
Record each authority communication by type and date. Assign one person to monitor requests, extensions and decisions, and give a second person access.
What a reviewer should see
The filer can reproduce the exact dossier, including signed attachments, delivery acknowledgment and subsequent correspondence.
When to escalate
Raise missing evidence or regulator requests that push an activity beyond the project release date.
What to produce
Senegal Article 22 dossierSpreadsheet
Gather first
Official route form
Article 22 particulars
Current workflow and data diagram
Signatory proof
Notices, retention and provider documents
How to prepare it
Create one row for each form question and supporting document. Assign a factual owner for purposes, data origin, people, retention, rights handling, access, recipients, security and transfers.
Check the filing answers against the real system and contract. For camera processing, document field of view, recorded areas, defaults and what staff can see.
Export an approved bundle and log submission, acknowledgment, formal declaration receipt or decision and follow-up requests as separate entries.
Worked example
Fictional details. Use the same fields with evidence from your work.
Document and owner
Warehouse camera layout and field-of-view images, owned by Facilities.
Application answer
Cameras monitor the loading access points. The system has no enabled facial matching. Use a test frame to check that a workstation is outside the field of view.
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.
Who Privacy counsel + Procurement + release ownerWhen Before rollout or a transfer to a third country
Use the formal récépissé for a declaration. For an authorization or opinion route, check the outcome and any permitted reliance on Article 23 with local counsel. Check transfer destination protections and prior information under Article 49, any narrow Article 50 grounds and the Article 51 authorization route where applicable. Confirm CDP’s current process and record the proof before rollout.
How to do this step
Before you start
Filing versions, formal receipt or decision, dates and extensions, provider evidence, and the proposed access configuration.
Check the filing outcome against the actual scope. If considering Article 23, get a local-counsel decision supported by the receipt date and any extensions.
Assess each external destination under Articles 49 to 51. Preserve the notification or authorization evidence and check the conditions against the supplier terms.
Have Security verify that only cleared access is enabled. Obtain Privacy and service-owner sign-off before release.
What a reviewer should see
The release record identifies the processing and transfer evidence, approved features, destinations and any controls that remain disabled.
When to escalate
Escalate gaps in notification, authorization, scope or interpretation before the team changes a production setting.
What to produce
Senegal transfer and release recordMemo
Gather first
Processing filing record
Supplier hosting and support diagram
Articles 18, 23 and 49 to 51
Security settings and sign-off
How to prepare it
List each proposed destination and recipient, including supplier troubleshooting, backups and contractors. Verify where the team actually accesses or stores records.
Record the transfer conditions and what was sent to CDP. Preserve the decision where required. If considering a deemed authorization for processing, have Legal document the receipt date, any extension and the basis for reliance.
Compare the authorized or declared operation with the planned configuration. Sign a release only when each applicable processing and transfer requirement is evidenced.
Worked example
Fictional details. Use the same fields with evidence from your work.
Filing and scope
Fictional warehouse cameras. Keep identifying footage on local storage. The vendor requested access from a foreign support location.
Release decision
Keep the foreign support account disabled. Privacy checks destination protection and the CDP route before any remote access is enabled.
Proof to attach
Formal processing receipt or applicable decision, transfer assessment and regulator correspondence, and a test showing only approved support access.
Accountable owners
Privacy handles CDP correspondence. Security verifies access. Operations authorizes the rollout against the approved scope.
Check before handing it over
The reviewer can trace every processing and transfer gate to evidence and an explicit release or hold decision.
Hand the approved settings and conditions to the system owner and provide the hold decision where a gate is still open.
Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.
Worked example
Fictional details. Use the same fields with evidence from your work.
Document expected
Issuer’s final decision or confirmation
Reference
Official portal or case ID
Received and verified by
Compliance coordinator, 2026-11-10
Scope and conditions
Matches the agreed service boundary and version. Follow-up recorded separately.
Location and access
Restricted evidence folder, named reviewers only
Check before handing it over
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Maintain the filed scope and prepare for inspection
Who Privacy operations + system owner + Vendor ManagementWhen At changes, on closure and throughout operation
Compare changed data, purposes, recipients and destinations with the filed particulars. Submit a new request when Article 22 requires one and inform the CDP when the treatment is ended. Keep the rights workflow, supplier records and test evidence ready for a CDP inspection.
How to do this step
Before you start
Current filed particulars, release evidence, vendor changes, rights requests and CDP inspection framework.
Use the change ticket to compare the activity with the existing filing. Record changes to purpose, data, recipients, retention or countries before approval.
Have the authorized filer submit the new request or notice required under Article 22 and preserve the proof. Update the rights and vendor records.
Rehearse an inspection by asking the service owner to retrieve the current filing, show the settings and walk through a rights request.
What a reviewer should see
A reviewer can trace one change from proposal to CDP correspondence and the final system setting.
When to escalate
Hold a change with unclear filing coverage and assign the decision to Privacy and the executive who owns the service.
What to produce
Senegal filing change logSpreadsheet
Gather first
Filed Article 22 particulars
Release decision and system changes
Supplier notices
Current CDP forms and inspection framework
How to prepare it
Compare each planned or completed change with the last filed version and record the affected particulars and actual change date.
Check whether Article 22 requires a new request or a notice that processing has ended. Set the accountable filer, applicable approval gate and recipients of the updated information.
Keep the prior and replacement evidence together. Check that operations, notices, contract terms and access now reflect the cleared scope.
Worked example
Fictional details. Use the same fields with evidence from your work.
Change
Maintenance vendor proposes remote access to warehouse footage from another country.
Affected particulars
Recipient, access and transfer destination. Open a new filing review before the support role starts.
Accountability
Privacy assesses and communicates with CDP. Engineering can show that the new account remains disabled until the review is closed.
Closeout evidence
Written authority response where applicable, updated filing copy, approved settings and date shared with Facilities.
Check before handing it over
A reviewer can follow the change from the operational request to each new filing or notice and the exact settings released.
Give the updated record to Privacy and the service owner so the next CDP inspection can trace the change.
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.
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.
Register with Tanzania’s PDPC before collecting or processing covered personal data. Prepare the DPO appointment, file through RCMIS and track certificate renewals and transfer permits.