Start hereDecide what to file
~56 days leftOpen step
Guide library
Regulation Africa

Côte d’Ivoire data protection formalities

Law No. 2013-450 and Décret No. 2015-79 on personal data filings

Decide whether the activity needs a declaration, an authorization or another procedure. Prepare the filing and check what must happen before launch or transfer.

Who it applies to

Controllers that process personal data within the scope of Law No. 2013-450. Check the local filing representation requirements and the separate procedure for certain public-sector processing.

What you’ll produce

A route decision for each covered activity, a case file with receipts or decisions, and a record of approved processing, transfers and changes.

For transfer formalities, the law defines a third country as a state outside ECOWAS. Check the destination’s status and applicable authority instructions when you plan the transfer. The declaration exemption for a qualified privacy correspondent does not waive an authorization requirement.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Who files and who receives decisions?
Confirm the controller, eligible local filer and signing authority. Give two named staff access to the correspondence inbox and a shared record of filing versions, dates and references.
What can go live while the formalities are open?
Have the business owner and Legal agree which processing can proceed, which activities must wait for a receipt or authorization, and how staff can operate in the meantime.
Who can approve a change to the filed operation?
Make Procurement and Engineering flag new support locations, providers, data categories and purposes before approval. Ask the privacy lead to decide whether an updated or separate filing is required.

How to spend the first week

  1. Ask HR, Operations and the service owner to walk through one actual collection workflow. List which legal entity determines the purpose and who can access the data.
  2. Take the latest filing form and build a checklist from Article 9. Assign each field and supporting attachment to the staff member who can confirm it.
  3. Add the authority’s receipt and any authorization conditions to the project’s launch checklist. Ask Engineering to demonstrate that covered enrollment and remote access stay disabled pending clearance.

What to review each week

Report filings by route, receipt date and current status. Show decisions or formal receipts still pending, changes awaiting review and conditions that must be met before go-live.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Côte d’Ivoire data protection formalities 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  Decide what to file · Local counsel + controller’s privacy lead [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 HR, Operations and the service owner to walk through one actual collection workflow. List which legal entity determines the purpose and who can access the data.
2. Take the latest filing form and build a checklist from Article 9. Assign each field and supporting attachment to the staff member who can confirm it.
3. Add the authority’s receipt and any authorization conditions to the project’s launch checklist. Ask Engineering to demonstrate that covered enrollment and remote access stay disabled pending clearance.
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

  • Which legal entity determines the purpose, and who can file or act as its representative in Côte d’Ivoire?
  • Does the activity use biometrics, medical records, identifiers or a destination outside ECOWAS that puts it on an authorization route?

Worked scenario

An Abidjan employer plans to replace badge access with fingerprints. HR, Security and Legal compare the options and prepare an Article 7 authorization request for the biometric system. The project lead blocks employee enrollment until the required decision is received and its conditions are reflected in the rollout.

What to read next

  • Ghana Data Protection Act

    Review the separate registration process if your organization also operates in Ghana.

  • EU GDPR

    Compare separate EU processing and transfer obligations when the same service handles EU data.

FROM THE SOURCE

Cases and numbers

Authority decision · 19 June 2025

Vendor maintenance can be part of a transfer filing

In decision 2025-1263, the Data Protection Authority authorized Advans Côte d’Ivoire to transfer personal data to Tunisia for maintenance of its DIGILAF web application.

What to check Map remote vendor access, including application maintenance. Match the activity, destination and purpose to the scope of the official decision before enabling the access.

Data Protection Authority decision 2025-1263 (opens in a new tab)

Statutory timing

1 monthInitial Article 11 decision period after receipt

Put the decision window on the launch plan

The authority can extend the period by one month with reasons. Article 11 treats silence after the applicable decision period as refusal.

What to check Record the actual receipt date and any extension. Keep launch dependent on the required declaration receipt or approval.

Law No. 2013-450, Article 11 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • One month from receipt

    Article 11 decision period

    The authority may extend the period by one month with reasons. Article 11 treats silence at the end of the applicable period as refusal.

    Official reference (opens in a new tab)
  • Before a covered transfer

    Hold transfer until authorization

    Article 26 requires prior authorization for transfers to a third country as defined by the law.

    Official reference (opens in a new tab)
The whole journeyabout 56 days across 4 steps
  1. 01Decide what to fileLocal counsel + controller’s privacy lead · ~7 days
  2. 02Assemble and submit the case filePrivacy lead + accountable local filer · ~14 days
  3. 03Verify transfer conditions and the release decisionPrivacy counsel + Procurement + service owner · ~21 days
  4. 04Keep rights and filing records currentPrivacy operations + Security + service owner · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 9 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Decide what to fileLocal counsel + controller’s privacy leadBefore collecting data or changing a live activitySet a start dateProcessing inventory; Ivorian filing route decisionOpen
Assemble and submit the case filePrivacy lead + accountable local filerBefore in-scope processingSet a start dateIvorian filing cover sheet; Notification recordOpen
Verify transfer conditions and the release decisionPrivacy counsel + Procurement + service ownerBefore a covered transfer or go-liveSet a start dateIvorian transfer authorization record; Ivorian processing release decisionOpen
Keep rights and filing records currentPrivacy operations + Security + service ownerDuring operation and whenever filed facts changeSet a start datePrivacy notices; Rights workflow; Change logOpen
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

    Decide what to file

    Who Local counsel + controller’s privacy lead When Before collecting data or changing a live activity

    List the purposes, operators, data fields, recipients and processing locations. Work through declarations, exemptions, simpler routes, Article 7 authorizations and the special procedure in Article 13 where relevant. Confirm the eligible filing entity and signatory.

    How to do this step

    Before you start

    System walk-through, actual data fields and locations, controller and processor agreements, and local representation records.

    1. Give each activity a filing row. Identify its controller, purpose, covered people, data categories, recipients and intended transfer countries.
    2. Check prior authorization triggers and any special route before considering a declaration or exemption. Document which legal provision supports the route and who is eligible to file.
    3. Have the system owner confirm the draft facts and have local counsel sign off on the route before scheduling enrollment or access.

    What a reviewer should see

    A dated route memo and processing inventory link the filing decision to actual system settings and a named local filer.

    When to escalate

    Raise uncertain authorization triggers, foreign access or an unresolved filing entity before the project commits to a launch date.

    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.

    Ivorian filing route decisionMemo

    Gather first

    • Processing inventory and local entity details
    • Articles 5 to 13 and the authority’s current procedures
    • Data fields, operators, purposes, access and locations

    How to prepare it

    1. Write down which entity determines the purpose and how the actual system operates. List the data, recipients, countries and any biometric or health processing, identifiers, file interconnection or public-sector purpose.
    2. Record the applicable route and the supporting legal provision. Check any claimed declaration exemption separately from authorization triggers. Confirm the eligible local filer and authority instructions.
    3. Have the privacy lead and project owner approve the decision and record what will block the launch. Reopen the analysis if the purpose, data or destinations change.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and entity
    B-014, employee entry control at an Abidjan warehouse. Fictional employer Sassandra Logistics determines the purpose.
    Proposed data
    Fingerprint templates, employee ID and entry logs. Security operates the readers. Staff can use a staffed check-in during preparation.
    Applicable route
    Prior authorization under Article 7 for biometrics. Verify the current form and eligible local applicant with the authority.
    Decision and release condition
    Keep badge access until receipt of the required authorization and verification of its conditions. Privacy lead owns the dossier.
    Reopen if
    A vendor will access biometric records remotely, a location changes or the system will be used for a new purpose.

    Check before handing it over

    The route follows the actual data and uses. The team can show the supporting provision, responsible filer and written release condition.

    Give Legal’s route decision to the project lead and the local filer before either starts work that relies on approval.

  2. 02

    Assemble and submit the case file

    Who Privacy lead + accountable local filer When Before in-scope processing

    Use the authority’s current form and Article 9 to check party details, data categories and sources, retention, staff access, recipients, safeguards, processors and transfers. Check the latest dossier fees and filing route. Keep the submitted version and the intake acknowledgment.

    How to do this step

    Before you start

    Current authority form, approved route, retention and access details, contracts, and statements of security safeguards.

    1. Assign every Article 9 field to an owner. Reconcile inconsistencies between the form, attachments, contract and current service configuration.
    2. Confirm the signature, attachments and any current fees with the authority. Submit the signed version through the applicable official channel.
    3. Keep the exact filed copy and record when it was received. Log any questions and the legal decision window against that receipt date.

    What a reviewer should see

    A reviewer can match each form field to the corresponding evidence and reproduce the exact version the authority received.

    When to escalate

    Escalate a missing acknowledgment or a request that changes the planned operation to the local filer and project owner.

    What to produce

    Ivorian filing cover sheetMemo

    Gather first

    • Current prescribed filing form and route decision
    • Controller and local representative details
    • Processing inventory, processor terms and safeguards
    • Dossier fee, submission and receipt instructions

    How to prepare it

    1. Get the current form from the authority. Map each Article 9 field to a factual record, such as data inventory, retention schedule, contracts, access matrix and security controls.
    2. Check who signs and which attachments and fees the authority currently requires. Have the operator confirm the described permissions and destinations match what will run.
    3. Track the submitted version, intake acknowledgment, questions and eventual decision. Record the official declaration receipt or authorization separately from the initial acknowledgment.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Dossier and filer
    CI-BIO-014 v3, submitted by the fictional Ivorian employer’s authorized signatory. Legal entity documents and mandate are attached.
    Purpose and fields
    Warehouse entry verification, fingerprint templates and staff IDs, collected in person from enrolled employees. No reuse for attendance scoring.
    Retention, access and recipients
    Security can see enrollment status, HR processes rights requests, and the detailed records follow the approved retention schedule RET-14.
    System and safeguards
    Template encryption, restricted admin roles and logged access. Record the processor’s actual support locations and attach the contract.
    Submission record
    Version 3, official channel, intake reference CI-014. Written authorization and conditions still pending.

    Check before handing it over

    The checklist agrees with the files submitted and the operational reality. Official receipts and decisions have separate fields.

    File the cover sheet with the prescribed documents. Keep a copy for the privacy lead and release approver.

    Notification recordSpreadsheet

    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

    Verify transfer conditions and the release decision

    Who Privacy counsel + Procurement + service owner When Before a covered transfer or go-live

    Map actual destinations and access arrangements. For a transfer to a third country, assess the level of protection under Article 26 and obtain prior authorization. Distinguish an intake acknowledgment from the formal declaration receipt or required authorization. Check written conditions and escalate a refusal or elapsed decision window.

    How to do this step

    Before you start

    Official filing correspondence, data locations and vendor access logs, transfer assessment and proposed release configuration.

    1. Have Procurement and the service owner verify where the provider stores or accesses data, including remote support. Route any third-country transfer for the required authorization.
    2. Compare the applicable formal receipt or authorization with the release scope. Assign each written condition to an owner and test it in the planned configuration.
    3. Sign a release memo only after assembling the required documents and evidence. Keep a dated hold decision and the next owner if the authority refuses the request or the decision period elapses without a response.

    What a reviewer should see

    The release record links the applicable formal receipt or decision to the planned go-live, actual provider locations and proof of conditions.

    When to escalate

    Give Legal an elapsed decision window, refusal, missing document or out-of-scope configuration before anyone switches on the activity.

    What to produce

    Ivorian transfer authorization recordSpreadsheet

    Gather first

    • Data flow, vendor support and hosting locations
    • Articles 7 and 26 and current authority instructions
    • Recipient agreement, safeguards and decision record

    How to prepare it

    1. Give each transfer a record. Enter the sender, recipient, purpose, categories, country, access method and who can see the records. Check the actual hosting and support paths.
    2. Determine whether the destination is a third country under the law and document the protection assessment and any required authorization route. Submit the applicable official request with its supporting facts.
    3. Record the written decision, exact scope and conditions before enabling a covered transfer. Check actual access against that scope and review when the provider, purpose or country changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID and transfer
    TR-008, remote troubleshooting for a fictional lending application hosted in Abidjan.
    Parties and destination
    Local controller, contracted maintenance provider in Tunisia. Staff may view restricted diagnostic records.
    Safeguards and facts to assess
    Time-limited access, named engineers, audit logs, minimization and a documented destination assessment.
    Authorization status
    Draft ready. Production access stays disabled pending the authority’s decision and Internal Security approval.
    Owner and change trigger
    Privacy and Procurement. Reassess if a provider assigns support to another country or needs a wider dataset.

    Check before handing it over

    A reviewer can compare each actual transfer with the named authorization and verify its conditions.

    Give the decision and confirmed technical limits to Procurement and the system owner. Preserve the receipt and decision in the filing register.

    Ivorian processing release decisionMemo

    Gather first

    • Approved filing route
    • Intake acknowledgment and any extension
    • Formal receipt or written decision
    • Release checklist and technical access tests

    How to prepare it

    1. Identify the precise version of the processing activity that is ready to launch. Record the filing reference, receipt date and any reasoned extension separately from the formal declaration receipt or written authorization.
    2. For an authorization, compare the decision with the live system’s purpose, data, scope and locations. Give each condition an owner and attach proof that it was met.
    3. Have Privacy and the project owner sign the release decision. If the required document is missing or the allotted period ended without a decision, record the hold and have the filer confirm the next step with the authority.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and owner
    B-014, warehouse entry control. Fictional Sassandra Logistics operations manager.
    Filing evidence
    Intake reference CI-014. Prior biometric authorization is still pending.
    Proof to attach before release
    Written authorization, scope comparison against access-control settings, test of the approved retention schedule and condition-by-condition evidence.
    Release decision
    On hold. Keep staffed check-in and existing badges. Procurement can prepare training while Privacy handles the authority request.
    Next checkpoint
    Privacy checks the Article 11 date and whether a reasoned extension was received. Reopen with the system owner when the decision arrives.

    Check before handing it over

    The release decision links to the required authority document, verifies its scope and names the people who cleared each condition.

    Share the signed memo with the implementation owner before enabling enrollment or a covered transfer.

  4. 04

    Keep rights and filing records current

    Who Privacy operations + Security + service owner When During operation and whenever filed facts change

    Maintain notices, rights contacts, security and processor commitments. Notify the authority without delay when information covered by Article 9 changes. Review whether a new purpose, data category or country needs a separate filing or decision.

    How to do this step

    Before you start

    Filed copy and approval conditions, rights queue, processor contracts and system change records.

    1. Run a rights request through the actual systems and processors. Record which teams can search, correct or delete records and where they preserve the response.
    2. Add a privacy checkpoint to procurement and system changes. Compare proposed changes against the filed record and any approval conditions.
    3. Notify the authority without delay when Article 9 information changes. Retain the prior version, submission evidence and updated decision where applicable.

    What a reviewer should see

    The privacy lead can trace a changed provider, field or location from the project ticket to the authority communication and current filing record.

    When to escalate

    Hold an out-of-scope addition while Privacy confirms the required filing or authorization.

    What to produce

    Privacy noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.

    Send approved text to the publishing owner and give support teams the version and effective date.

    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.

    Change 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.

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