Study first
Review the ideas behind the questions
Review access and privacy controls before a marketing workflow moves personal data. Focus on who needs access, which rights are documented, what the tool actually allows, and how the risk changes when data or vendors enter the process.
Start With Information Risk
Access decisions are safer when the team knows which data assets are involved and what could happen if the wrong person sees or changes them.
- Information security uses technologies, policies, and practices to keep data safe.
- Teams should document service assets and identify risks from technology choices, processes, staffing, and data aggregation.
- Security risk assessment should prioritise risks that are likely or would have the biggest effect on users and the service.
In Practice
Access Is A Process Risk
A contractor, agency, or internal move changes staffing risk, so permissions should be reviewed before data access starts.
Risk Guides The Control
Check what the data exposes and who can change it. Choose controls for that risk, not for the easiest setup.
Common mistakes
Granting broad access first and planning to tidy permissions after launch.
Review assets, staffing risk, disclosure risk, modification risk, and controls before access is granted.
Q&A
What should be reviewed before granting campaign-data access?
Review the data assets, business need, role, risks, control options, and owner for the permission.
Why is stale edit access risky?
It can let unauthorised people see or change information, affecting confidentiality and integrity.
Match Rights To Real Need
Personal-data access should be documented, limited, removed when no longer needed, and checked against actual system permissions.
- Access rights to personal data must be understood and limited to users who reasonably need the access.
- Access rights should be removed when they are no longer needed.
- Technical system permissions should be checked against documented user access rights.
In Practice
Check The Tool Against The Policy
A policy that says analysts cannot export personal data is not enough if the tool still gives them export rights.
Avoid Shared Convenience Accounts
Shared accounts make it harder to prove who exported, changed, or deleted personal data.
Common mistakes
Leaving broad permissions active because a launch week is busy.
Limit permissions to documented need and remove rights when they are no longer needed.
Q&A
What should a permission review compare?
Compare documented access rights with what the tool actually allows users to do.
When should access be removed?
Remove it when the person or role no longer reasonably needs it for their function.
Build Privacy Into The Workflow
Privacy checks belong in design and lifecycle decisions, especially when a workflow uses personal data or a third-party feed.
- Data protection by design means considering privacy and data protection at the design phase and throughout the lifecycle.
- Data protection by default limits personal information to what is necessary for each specific processing purpose.
- Service teams should perform due diligence on third-party software and process data securely in a way that respects privacy.
In Practice
Review Before Connecting Feeds
A new enrichment or sync feed should have an owner, privacy review, security control, and evidence before data starts moving.
Keep Only Necessary Personal Data
If the stated campaign purpose needs job role and company segment, extra private notes should stay out of the workflow.
Common mistakes
Adding privacy review only after the automation build is complete.
Consider privacy and data protection during design and throughout the workflow lifecycle.
Q&A
When should privacy review start?
Start during design and keep it active through the workflow lifecycle.
What should default data use mean in a campaign workflow?
Use only the personal information necessary for the specific campaign purpose.