COPRSETR WORKSHEET
Senegal filing change log
Senegal CDP data protection filings · Step 4 · Maintain the filed scope and prepare for inspection- Who prepares it
- Privacy operations + system owner + Vendor Management
- When to prepare it
- At changes, on closure and throughout operation
Worked example
This example uses 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.
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.
Review
A reviewer can follow the change from the operational request to each new filing or notice and the exact settings released.
Handoff
Give the updated record to Privacy and the service owner so the next CDP inspection can trace the change.
Use the issuer’s current instructions and any required forms when you submit.
CDP inspection framework (opens in a new tab)