Hosting personal data in the EU does not remove the transfer question if engineers outside the EU can see the data. Under the GDPR, remote access from a third country such as Morocco can itself be a transfer. Map who can access the data, from where and why, reduce unnecessary access, then align contracts, SCCs and the transfer assessment with how support really works.
- EU servers do not remove transfer questions if support sits outside the EU
- Remote access from a third country can be a transfer
- Map access as well as server locations
- Reduce standing access and prefer just-in-time, logged access
- Contracts, appendices and the assessment must match operations
The hosting region does not describe every data movement. Support, administration, local copies and providers can create access from other countries. Assessing a transfer requires identifying the entities and recipients involved and examining the actual access arrangements.
01Map access as well as servers
Start with a support ticket and follow the request, console, logs, possible export and closure. Record countries, accounts, authorised staff and their employing entity. Include support, monitoring and backup tools. This diagram exposes access that an invoice for European hosting cannot show.
Talk to a DPO for 30 minutes, free of charge: they tell you what applies to your company and where to start.
02Identify the recipient
Distinguish a subsidiary, independent provider and employee of the same entity. The assessment cannot be inferred solely from a user’s location. Document the relationships and review the mechanism for the actual flow. Do not automatically reuse another customer’s conclusion where entities and contracts differ.
03Reduce unnecessary access
Consider time-limited access, named accounts, suitable test data and restrictions on unnecessary exports. Check what logs actually show. Describe each measure with its scope and owner: “encryption” alone does not explain who can read data during support.
04Align contracts and operations
Compare the map with processing appendices, provider lists and sales answers. Correct “Europe only” statements if they describe storage alone. RGPD Conseil Maroc can prepare a data-flow map, open questions and a documentary safeguards review; responsibility for IT implementation should be explicitly assigned.
Illustrative example: an application hosted in Paris is administered by a separate Moroccan company. The map should include that access even if no complete database is downloaded. The review examines accessible data and the relationship between the companies.
05Servers are only half of the picture
Many companies assume that EU hosting settles the GDPR transfer question. In practice, regulators and customers look at two things: where data is stored, and who can access it from where. A support engineer in Morocco who can open a customer's database through a remote session accesses personal data from a third country, even if nothing is copied. That access is generally treated as a transfer and needs a lawful transfer mechanism.
06Map access, not only hosting
| Question | Why it matters |
|---|---|
| Where is the data stored, including backups? | Defines the primary location |
| Who can access it, in which company and country? | Defines transfers and sub-processors |
| How do they connect: VPN, remote desktop, direct tool? | Defines risk and logging |
| Is access standing or granted per ticket? | Standing access increases exposure |
| Can they download or only view? | Affects the supplementary measures |
| Is access logged and reviewed? | Needed for accountability |
07Identify the recipient
For each access path, identify the legal entity that accesses the data. It may be your own subsidiary, a sister company, a support provider or an individual contractor. Each is a recipient, and their role differs: a group company acting for you is a processor or sub-processor, a partner deciding its own use is a controller. The role decides which contract and SCC module applies.
| Recipient | Likely role | Document |
|---|---|---|
| Your Moroccan subsidiary giving support | Processor or sub-processor | Intra-group DPA and SCCs |
| An outsourced support company | Sub-processor | Sub-processor DPA, SCCs, customer approval |
| A freelancer with admin rights | Sub-processor | Contract with data clauses, access policy |
08Reduce unnecessary access
- Replace standing access with time-limited access granted per ticket
- Use masked or synthetic data for troubleshooting where possible
- Prefer view-only access over export
- Restrict access by role and by customer
- Record every session and review a sample monthly
- Remove access on role change or departure
Reducing access is often the cheapest supplementary measure, and it also makes the transfer assessment easier to conclude.
09Align contracts and operations
| Document | Check |
|---|---|
| Customer DPA | Mentions support from Morocco and the sub-processor |
| SCC appendices | Describe remote access accurately |
| Transfer assessment | Reflects real access model and logging |
| Support procedures | Match what the documents promise |
| CNDP filings | Cover transfers and access from abroad on the Moroccan side |
10Example: an EU-hosted application with a Casablanca help desk (illustrative)
A French software company hosts its application in the EU and uses a help desk in Casablanca. The help desk can see customer records during tickets. The company maps the access path, moves from permanent accounts to ticket-based access, hides sensitive fields, signs SCCs with its Moroccan affiliate, updates the sub-processor list and informs customers. Its next customer review passes without a transfer finding.
11What customers will ask
- Do any people outside the EU have access to our data?
- From which countries, and under which safeguards?
- Is access logged and can we see the logs?
- What happens when an access request arrives from an authority?
- Which sub-processors are involved?
12Your checklist for EU hosting with outside support
- Access map showing people, countries and purposes
- Transfer mechanism documented for each recipient
- Standing access replaced with ticket-based access
- Support sessions logged and sampled
- Sub-processor list and customer notices updated
- Moroccan filings aligned if the support team is in Morocco
13Choosing safeguards that fit the access model
| Access model | Safeguard that helps |
|---|---|
| Occasional view-only support | Time-limited access and masking |
| Regular administration | Strict role separation and full logging |
| Bulk processing in Morocco | SCCs and full transfer assessment |
14More questions answered
Is viewing data remotely really a transfer?
Yes. Making personal data accessible from a third country can be a transfer even without copying it.
Do we need SCCs for a Moroccan affiliate?
Usually yes, unless another valid mechanism applies. The right module depends on the roles.
Can we avoid the issue by keeping support in the EU?
That removes the transfer, but may not be practical. Many companies keep a reduced and well-controlled access model instead.
What about Moroccan law?
Access from abroad may also need to be declared or authorised on the Moroccan side if Moroccan data is involved.
Do we need to tell customers?
Yes. Support locations and sub-processors normally belong in the DPA or sub-processor list.
Can you review our support model?
Yes. A scoped review covers access mapping, documents and measures, quoted after a free 30-minute call.
15Your starting dossier
- Entities and access countries
- Support, logs, exports and backups
- Actual permissions and restrictions
- Flow-specific contracts and safeguards
Describe the situation without submitting customer records, passwords or confidential documents in the initial form.
16Practical questions
What should I prepare before contacting RGPD Conseil Maroc?
Prepare: Entities and access countries; Support, logs, exports and backups; Actual permissions and restrictions; Flow-specific contracts and safeguards. 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.
17Continue preparing
European client GDPR requirements: documents for Moroccan suppliers
Prepare GDPR contracts, data-flow records and supporting evidence when a European customer reviews your Moroccan company. Practical supplier checklist.
Read the guideGDPR 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 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 ↗