Where personal data goes and who can see it
Sounds familiar? We collect customer data through forms, tracking and AI tools, and we're not sure we handle it properly.
Your contact forms, analytics tags, CRM (customer database), newsletter tool and any AI assistant each send customer data somewhere. We map what personal data you collect, which tools it passes through and who can see it, then check your consent setup and each vendor's data settings. You get practical fixes and internal guidelines for using AI and other tools with customer data. Scoping comes first, since the size of the review turns on how many tools you use, what data they hold and where your customers live. Nothing here is legal advice or a certification, so where the law is involved a qualified privacy professional reviews the findings or we refer you to legal counsel.

What you get
- Inventory of the tools that collect or store personal data, from forms to AI assistants
- Data flow map: what is collected, where it goes, who can see it and how long it is kept
- Review of your cookie banner and consent setup against how your tags actually behave
- Check of each vendor's data settings, such as sharing, storage location and use for AI training
- Findings with practical fixes, ranked by risk and effort
- Internal AI and tool usage guidelines for your team, written as practical guidance and not as a legal document
- Referral to legal counsel for questions that need a lawyer
Is this right for you?
- You are adding tracking, a CRM or AI tools and want to know what data they will see
- You serve customers in the EU or UK and aren't sure your cookie banner works as intended
- You have staff pasting customer details into AI tools without written rules
- You were asked by a client or partner how you handle their data and had no clear answer
What it changes
Your data written down in one place
One document shows what personal data you collect, which tools hold it and who has access.
Fixes you can act on
Findings come with practical changes, such as dropping form fields you never use or limiting who can export customer lists.
Clear rules for AI and other tools
Your team has written guidelines on what customer data may go into AI and other tools, and what must stay out.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Agreed after a short call, once the tools and data flows in scope are listed
How we deliver it
-
Agree on the scope
We start with a short call to list your tools, the data they handle and the countries your customers are in, then agree on what the review covers.
-
Map the data
A privacy specialist traces each form, tag, integration and AI tool, and records what data moves where.
-
Check consent and vendors
Your cookie banner is tested against what your tags actually do, and each vendor's data settings are reviewed.
-
Report and refer
You get the findings, the fixes and the AI and tool guidelines. Legal questions then go to a qualified privacy professional, or we refer you to legal counsel.
What we need from you
- A list of the tools you use for forms, email, CRM, analytics, payments and AI
- Admin or read-only access to those tools and to your website, authorized in writing by the business owner
- Your current privacy policy and cookie banner settings, if you have them
- The countries your customers are in
- Someone who knows how staff use AI tools day to day
What's not included
A specialist looks at your situation first, so the scope is agreed after a short call.
Not included
- Legal advice and legal documents such as privacy policies
- A formal audit or compliance certificate of any kind
- Acting as your data protection officer
- Making the changes themselves, quoted separately, including consent mode and tracking tags (see Analytics & conversion tracking)
Limits to know
- This is not legal advice or a certification. Where the law is involved, a qualified privacy professional reviews the findings or we refer you to legal counsel.
- The review covers the tools and data flows you show us at the time. New tools need a new check.
- The internal AI and tool guidelines are practical guidance, not a legal document.
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: Privacy & data-handling review
3 connected services
After this
What usually follows once this is done.
-
Website security hardening
Access findings lead to tightening accounts and permissions.
Part of these packages
-
Practical AI implementation
Assess: Pick the use case, check what data it touches and set a baseline before anything is built. The assessment includes a data sensitivity check, and a privacy review is added when the pilot touches personal data.
-
Digital product & MVP launch
Optional add-on: When the product stores personal data.
Read before you decide
Common questions
Will this make us GDPR compliant?
Compliance is a legal judgment, and this review is neither legal advice nor a certification. It gives you a clear map of your data and practical fixes, and legal questions go to a qualified privacy professional or your lawyer.
Do you write our privacy policy?
A privacy policy is a legal document, so a lawyer should write or approve yours. The data flow map gives them the facts about what you collect and where it goes.
Why is the review scoped after a call?
A business with one contact form and one analytics tag needs a short review. One with a CRM, a store, ad tracking and AI tools across several countries needs far more. The call lists your tools and markets so the quote matches the work.
We want to use AI with customer data. Where does this fit?
Run the review before or alongside the Automation & AI assessment, so the data each AI tool may see is agreed first. The usage guidelines then carry over to AI assistants with human review and to any other tool you add.