Launch or redesign
New store, application, marketplace, loyalty program or purchasing journey.
RCM
A merchant site concentrates identities, addresses, buying history, exchanges with support, browsing behaviors and sometimes more revealing data than expected. Between the shop, payment, delivery, advertising, emailing and analysis, the data circulates in an ecosystem rarely controlled by a single contract.
Compliance is therefore not just about legal notices or a cookie banner. It is necessary to check what is triggered before the visitor's choice, who receives the information, how long it is kept, how a customer exercises their rights and whether the promises displayed correspond to the technical configurations.
RCM combines documentary review, functional control, supplier mapping and action plan. Complex developments, security audits and advice relating to consumer law remain separate so that the quote indicates precisely what will be checked and what is the responsibility of another specialist.
Scoping starts with the facts: systems, teams, people involved, data, customers, suppliers and countries. The obligations are then qualified separately with regard to the GDPR and Moroccan law 09-08. This method avoids applying a generic response to processing activities that have neither the same purpose nor the same level of risk.
A mission may begin before a launch, during a negotiation or after a gap appears.
New store, application, marketplace, loyalty program or purchasing journey.
Advertising pixels, emailing, segmentation, similar audiences and consents to check.
Payment, delivery, CRM, customer reviews, support or hosting introduced in the chain.
Decisions and limits are made visible at each stage.
Visitor journey, account creation, ordering, support, returns and prospecting.
Data, purposes, bases, recipients, tracers, countries and durations.
Information, cookie choices, forms, contracts, settings and procedures.
Periodic tests, new tags, requests for rights and proof of implementation.
These situations are points of analysis, not automatic conclusions.
Beacons can transmit identifiers before the visitor's choice.
Creating an account or purchasing should not automatically impose unnecessary prospecting.
Store, CRM, payment, delivery and support each retain part of the journey.
Inactive accounts, carts, tickets and leads require adapted rules.
The roles between platform, seller, payment and logistics must be qualified.
Export, deletion or opposition require coordinated research between tools.
Each check must have a responsible person, frequency and proportionate proof.
List purpose, provider, duration, trigger and category of consent.
Distinguish between order execution, account creation, loyalty and prospecting.
DPA, security, location, processors and data review meeting.
Rules by order, account, prospect, support, fraud and evidentiary obligations.
Point of entry, identity, multi-tool search, validation and secure response.
Control after redesign, new tag, campaign, application or change of CMP.
The final scope depends on maturity, risks and elements already available.
Steps, data, purposes, tools, managers and information points.
Inventory, triggering, consent, withdrawal and proof of choice.
Confidentiality, cookies, forms and notices adapted to actual operation.
Payment, logistics, CRM, marketing, support, hosting and reviews.
Research, validation, deadlines, decisions, models and secure delivery.
Priority fixes with product, marketing, IT and operations managers.
The same activity may fall within both frameworks for different reasons.
Roles, responsibilities, information, rights, security, subcontracting and transfers outside EEA.
Treatment in Morocco, rights, security and formalities of declaration or authorization.
Access, hosting, recipients, mechanism, context and additional measures.
Contracts, registers, decisions, controls, training, incidents and actions followed.
The amounts are confirmed after scoping; no fictitious pricing is published.
Targeted interviews, review of available elements, major risks and sectoral roadmap.
Fixed price · after scopingAgreed deliverables, corrections, review meeting and operational transfer to internal managers.
From — on estimateVolume, deadlines, meetings, controls, new projects and contract overruns.
Subscription · on quoteRCM provides GDPR advice, law 09-08 and operational assistance. The client organization retains its decisions, responsibilities, budgets, validations and technical actions. No mission guarantees absolute compliance, absence of sanction or a favorable decision from an authority.
These answers present general principles. Processing, roles, countries and contracts should be reviewed before any conclusion.
No. The document must correspond to the processing actually carried out. Compliance also depends on trackers, forms, account settings, supplier contracts, durations, security and ability to respond to requests. RCM checks the consistency between public information and the observed journey.
Certain elements strictly necessary for the requested service may fall under a different regime, but the measurement, personalization or advertising tracers must be qualified individually. The simple presence of an “accept” button is not enough if tags are triggered before the choice or if the refusal is not effective.
Roles vary depending on operations. The service provider may act under its own obligations for certain purposes and as a processor for others. We must examine contracts, flows and uses rather than assuming a single role for the entire relationship.
A period must be determined according to the applicable purposes and obligations. Account activity, orders, warranties, accounting, litigation and prospecting do not necessarily follow the same rule. The conservation plan distinguishes sets from uniform deletion.
RCM can audit the configuration, define the rules and monitor the result. Developments or advanced interventions in the tag manager can be carried out by your team or a technical specialist, depending on the scope confirmed in the quote.
An activity in Morocco may fall under Law 09-08 and CNDP formalities, while the GDPR may apply for other reasons related to the establishment, targeted persons or European customers. RCM describes each framework and each flow separately before assembling the joint actions.
Present your tools, data, customers, suppliers, countries and deadlines. RCM will indicate the first useful perimeter.
Scoping the mission →