A European client usually asks a Moroccan supplier for the same core documents: a signed data processing agreement, standard contractual clauses with completed appendices, a security description, a list of sub-processors and hosting locations, an incident procedure and evidence of Moroccan CNDP formalities. Preparing them once as an evidence pack shortens every negotiation.
- Clients ask for the same eight documents again and again
- Build one reusable evidence pack instead of answering ad hoc
- Describe only controls you can prove
- Align the Moroccan and European workstreams
- Turn every question into a dated action, not a promise
To answer a European customer’s GDPR request, start with the service, your role and the personal data you can access. Then assemble processing terms, access locations, supplier details and operational evidence. A broad compliance statement cannot replace a dossier describing the actual service.
01Identify what is delaying signature
Ask for the exact requirement: a questionnaire, contractual appendix, security review or particular evidence. Identify the approver and deadline. A buyer waiting for processing terms does not necessarily need a complete company audit. Tie each request to the relevant service and assign an owner for the response.
Talk to a DPO for 30 minutes, free of charge: they tell you what applies to your company and where to start.
02Build a usable evidence pack
Organise evidence into service and data, contracts, access and suppliers, and operating procedures. Give each document an owner, date and service scope. Describe limitations honestly: a written procedure that has not been tested should be labelled accordingly. Do not send customer records, CVs or production credentials as evidence.
03Connect the Moroccan and European workstreams
Separate GDPR applicability, commitments to the customer and the Moroccan formalities that need assessment. Your registered address cannot resolve all three. Prepare an entity and access diagram, then have outstanding contractual or regulatory questions reviewed before promising a service start date.
04Turn questions into a resolution plan
Use a simple matrix: customer request, available evidence, gap, action, owner and deadline. Uncertain answers become follow-up items rather than checked boxes. RGPD Conseil Maroc can review the pack and prioritise missing evidence in a defined engagement; the customer retains its procurement decision.
Illustrative example: a Casablanca development company is awaiting approval from a French customer. The first task is to map each question to evidence and identify missing documents. The deliverable is a coherent submission pack, not a universal compliance certificate.
05The eight documents buyers ask for
| Document | What the buyer checks | Typical delay if missing |
|---|---|---|
| Data processing agreement | Article 28 obligations, instructions, audit rights | Signature blocked |
| SCCs with appendices | Right module, accurate description of the transfer | Transfer cannot start |
| Security description | Access control, encryption, backups, testing | Security review stalls |
| Sub-processor list | Hosting, tools and subcontractors with countries | Approval requested again and again |
| Incident procedure | Detection, internal escalation, alert timing | Contract clause cannot be accepted |
| Record of processing activities | Evidence of a structured compliance system | Doubt about maturity |
| CNDP filings and receipts | Evidence of Moroccan regulatory formalities | Questions about local compliance |
| DPO or compliance contact | A named person who can answer | Escalation goes nowhere |
06Building an evidence pack that survives scrutiny
An evidence pack is a folder, kept up to date, that answers the buyer's questions with documents instead of sentences. It does not need to be long, but every statement should be backed by something the buyer can open.
- A two-page compliance overview in plain English
- The documents in the table above, in one place
- Screenshots or exports for access control, logging and backups
- Evidence of staff training: material and attendance
- A short incident log, even if it is empty
- A version date on each document and a named owner
Never describe a control you cannot demonstrate. A request for proof usually follows, and a gap discovered at that stage costs far more than an honest 'in progress'.
07Connecting the Moroccan and European workstreams
The European buyer sees one half of your compliance, and the CNDP sees the other. A single project should feed both.
| Topic | European buyer asks for | Moroccan side requires |
|---|---|---|
| Inventory | Record of processing activities | Basis for CNDP filings |
| Hosting and tools | Sub-processor list and locations | Transfer authorisations |
| Security | Annex of technical and organisational measures | Security measures in the filing |
| Staff | Confidentiality and training | Information to employees |
| Incidents | Alert to the customer without delay | Security obligation under Law 09-08 |
08Turning questions into a resolution plan
Buyers rarely expect perfection, but they expect a credible path. When a question exposes a gap, answer in three parts: what exists today, what will be done, and by when. Attach an owner. This format is far more convincing than a generic assurance and it also gives your own team a to-do list.
| Question received | Weak answer | Strong answer |
|---|---|---|
| Are laptops encrypted? | Yes, all of them | Yes for managed laptops; the last 12 devices will be encrypted by the end of next month, owned by IT |
| Do you train staff? | We have a policy | Annual session, last held in March, attendance list attached |
| Do you have an incident procedure? | We take security seriously | Procedure v2 attached, tested in a tabletop exercise in June |
09Who in your company should own this
- A management sponsor who can accept commitments
- A compliance lead or outsourced DPO who maintains the pack
- IT, who supplies and documents technical evidence
- Sales, who forward questionnaires and never answer them alone
- Legal or an external adviser, who reviews contracts before signature
10Timing: when to prepare
The best moment to build the pack is before the first serious European prospect, but the second best is as soon as one appears. A supplier that starts from zero typically needs six to ten weeks to prepare the documents, run interviews and finish the Moroccan filings. If a signature date is already fixed, work backwards from it and prioritise what the buyer has asked for.
11Example: a design studio and its first German customer (illustrative)
A Moroccan design studio wins a pilot with a German company. The customer asks for a DPA, SCCs and a security annex in three weeks. The studio decides to prepare the pack once: it documents its tools, signs the missing supplier terms, completes the appendices and files the related formalities with the CNDP. The German customer's procurement team signs on schedule, and the same pack is used for the next two prospects.
12More questions answered
Is an 'attestation of GDPR compliance' something we can get?
No official attestation of GDPR compliance exists. What you can give a client is evidence: a record of processing, contracts, security description and filings.
Should we sign the customer's DPA as it is?
Read it first. Many clauses can be negotiated, in particular audit modalities, notification timing and liability. Do not accept commitments you cannot keep.
Do we need a DPO?
Not always, but many customers ask for a named contact. An outsourced DPO, from 4,900 MAD per month for a small company, is a common answer.
How long does it take to get ready?
Six to ten weeks from scratch. Faster if documents already exist and the buyer's priorities are clear.
Can we reuse the pack for every customer?
Mostly yes. Keep a core version and adapt the appendices and descriptions to each service.
What if the buyer asks for a certification?
Ask what they want to verify. Most requests are met with documents; certifications such as ISO 27001 cover security rather than GDPR compliance as a whole.
13Your starting dossier
- Service description and data categories
- Current processing agreement and appendices
- Hosting, access and downstream providers
- Rights, incident and exit procedures
Describe the situation without submitting customer records, passwords or confidential documents in the initial form.
14Practical questions
What should I prepare before contacting RGPD Conseil Maroc?
Prepare: Service description and data categories; Current processing agreement and appendices; Hosting, access and downstream providers; Rights, incident and exit procedures. Include your deadline and unresolved decisions. A summary is enough for the initial conversation.
Does an introductory call replace the engagement?
No. The introductory conversation clarifies your requirements. A proposal then defines documents reviewed, deliverables, responsibilities and price before work starts. Customer or regulator decisions are not guaranteed.
15Continue preparing
GDPR vendor questionnaire: prepare answers and supporting evidence
Answer GDPR vendor questionnaires with evidence on roles, contracts, hosting, access and corrective actions. A practical guide for suppliers and buyers.
Read the guideEU hosting with overseas support: GDPR access checks
EU servers and overseas teams? Map support access, exports, providers and legal entities before assessing GDPR international transfers.
Read the guideDPA, SCCs and TIA: which transfer documents do you need?
Understand processing agreements, standard contractual clauses and transfer impact assessments. Organise an EU–Morocco or EU–MENA transfer dossier.
Read the guideKeep reading
GDPR compliance
Audit, record of processing, policies and procedures: your Law 09-08 and GDPR compliance built on your real processing.
See the offer ↗ Free 30-min call ↗