Start hereChoose a filing route for each activity
~56 days leftOpen step
Guide library
Regulation Africa

Senegal CDP data protection filings

Senegal Law No. 2008-12: declarations, authorizations, opinions and transfers

Choose the Senegalese filing route, build the case file and check which receipt, decision or transfer evidence you need before rollout.

Issuing authority
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.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

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

  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.

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
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. 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.
  3. 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.
  4. 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.

What to read next

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.

CDP quarterly report No. 01-2025, declarative activities (opens in a new tab)

CDP plenary decision · reported April 2025

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.

CDP quarterly report No. 01-2025, refusals (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • One month, extendable once

    Declaration receipt

    Article 18 permits a reasoned extension. The formal declaration receipt is the document that allows implementation.

    Official reference (opens in a new tab)
  • Two months from receipt, extendable once

    Opinion or authorization decision

    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.

    Official reference (opens in a new tab)
  • Before a transfer to a third country

    Notify CDP and check the transfer route

    Articles 49 to 51 distinguish prior notification, narrowly scoped exceptions and authorization based on sufficient safeguards where applicable.

    Official reference (opens in a new tab)
The whole journeyabout 56 days across 4 steps
  1. 01Choose a filing route for each activity, Privacy lead + Senegalese counsel + system owner, about 7 days
  2. 02Complete the dossier and log what CDP receives, Privacy lead + authorized filer + Security, about 14 days
  3. 03Clear the processing and transfer release gates, Privacy counsel + Procurement + release owner, about 21 days
  4. 04Maintain the filed scope and prepare for inspection, Privacy operations + system owner + Vendor Management, about 14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 8 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Choose a filing route for each activityPrivacy lead + Senegalese counsel + system ownerBefore collecting or changing covered personal dataSet a start dateProcessing inventory; Senegal CDP route decisionOpen
Complete the dossier and log what CDP receivesPrivacy lead + authorized filer + SecurityBefore initiating the covered activitySet a start dateSenegal Article 22 dossier; Response logOpen
Clear the processing and transfer release gatesPrivacy counsel + Procurement + release ownerBefore rollout or a transfer to a third countrySet a start dateSenegal transfer and release record; External decisionOpen
Maintain the filed scope and prepare for inspectionPrivacy operations + system owner + Vendor ManagementAt changes, on closure and throughout operationSet a start dateSenegal filing change log; Rights workflowOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Choose a filing route for each activity

    Who Privacy lead + Senegalese counsel + system owner When 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.

    1. Split the project by purpose and actual data used. Mark separate features, especially national identifiers, facial matching and file connections.
    2. 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.
    3. 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

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. 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.
    3. 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.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.

    Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.

    Senegal CDP route decisionMemo

    Gather first

    • Processing inventory
    • Controller or representative mandate
    • CDP forms
    • Law No. 2008-12, Articles 17 to 21

    How to prepare it

    1. List each purpose and the settings that implement it. Check biometrics, national identifiers, criminal information, health research and file connections against Article 20.
    2. Compare exemptions, simplified forms and any public-service route with the actual facts. Decide whether distinct activities need distinct filings.
    3. 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.

  2. 02

    Complete the dossier and log what CDP receives

    Who Privacy lead + authorized filer + Security When 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.

    How to do this step

    Before you start

    Article 22 particulars, prescribed form, collection screens, retention settings, security measures and supplier contracts.

    1. 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.
    2. Resolve differences among the contract, system and description before signing. Archive the bundle and proof of delivery.
    3. 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

    1. 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.
    2. 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.
    3. 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.
    Supporting evidence
    Redacted screenshots, retention settings, notice photo and supplier contract access limits.
    Filing status
    Route check complete. Filer keeps the exact submitted bundle and waits for the formal document applicable to the route.

    Check before handing it over

    A backup filer can match each submitted answer to an approved piece of evidence and distinguish intake from the authority outcome.

    Deliver the approved form and bundle to the signatory and preserve the resulting case reference.

    Response logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. 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.
    3. 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.

  3. 03

    Clear the processing and transfer release gates

    Who Privacy counsel + Procurement + release owner When 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.

    1. 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.
    2. Assess each external destination under Articles 49 to 51. Preserve the notification or authorization evidence and check the conditions against the supplier terms.
    3. 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

    1. List each proposed destination and recipient, including supplier troubleshooting, backups and contractors. Verify where the team actually accesses or stores records.
    2. 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.
    3. 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.

    External decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. 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.

  4. 04

    Maintain the filed scope and prepare for inspection

    Who Privacy operations + system owner + Vendor Management When 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.

    1. Use the change ticket to compare the activity with the existing filing. Record changes to purpose, data, recipients, retention or countries before approval.
    2. Have the authorized filer submit the new request or notice required under Article 22 and preserve the proof. Update the rights and vendor records.
    3. 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

    1. Compare each planned or completed change with the last filed version and record the affected particulars and actual change date.
    2. 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.
    3. 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.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. 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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes