
Hypothetical scenario: a Durban e-commerce brand hands Google Ads and GA4 access to a new agency. A staff member asks the obvious question - now that the agency is 'inside' Google, can it see my personal Gmail and YouTube history? Here is the honest answer, mapped layer by layer.
The Durban Scenario: A New Agency Gets Ads Access and the Team Asks What Else It Can See
A retailer agrees to grant a working agency access to its Google Ads account and GA4 property. Most of the team is relieved. One person is not: their personal Gmail address is also the login for the admin account. They want to know what a third party with Ads visibility can actually read.
The answer separates cleanly. Ads access does not open an inbox. But the same Google login surface hosts consumer privacy toggles, ads-account data sharing and admin visibility - and those are managed in different places by different people. Confusing them creates both privacy anxiety and genuine gaps.
The Privacy Surface Map: Three Layers of Google Data Control
| Layer | What it governs | Where it lives | Typical owner |
|---|---|---|---|
| One - consumer activity | Personal search, YouTube, location and ad personalisation data | My Activity, My Ad Center | The individual |
| Two - ads and analytics governance | Ad account data, audience lists, product linking | Google Ads, GA4, Merchant Center | Marketing lead |
| Three - admin visibility | Who can see and export ad and audience data | User management and manager accounts | Business owner |
Layer One: Consumer Activity Controls - My Activity, Web & App Activity, Location and YouTube History
At myactivity.google.com a user can pause Web & App Activity, YouTube History and Location History, review what has been saved, and set an auto-delete window. This governs personal data tied to that login - not ad account data.
Location History (surfaced as Timeline) affects how Google Maps personalises for that individual. It has only an indirect bearing on local marketing signals, and stopping it does not restrict what an advertiser can target.
What the Ad Personalisation Toggle in My Ad Center Actually Changes (And What It Does Not)
Inside My Ad Center, switching off personalised ads stops Google using that account's activity to target advertising. It does not stop ads appearing, and it does not touch a business's Google Ads account.
Separate consumer privacy from ad performance. Disabling personal ad personalisation does not materially damage a campaign's ROAS - Ads relies on its own signals and consented conversion data, not one employee's YouTube history.
Third-Party App Access: Reading Scopes Before You Approve 'Sign in with Google'
Each 'Sign in with Google' grant carries scopes - read-only calendar access differs sharply from full Gmail or Drive access. Before approving, read the scope list. Full permission audits are a separate discipline; full permission audits sit on layer one and belong to the individual, not the ad account.
Layer Two: Google Ads and Analytics Data Governance - Roles, Linking and Customer Match Consent
On layer two the question is not what Google stores about a person, but who inside the organisation can see customer lists, conversion values and audience segments. Google Ads roles range from read-only to admin, and manager accounts extend that access across properties. Analytics and Search Console links should be deliberate, not leftover from a past agency.
Customer Match is the sharpest edge: uploading a customer list is direct marketing under POPIA section 69, so consent and opt-out evidence must exist. Because Google's data centres sit offshore, section 72 cross-border transfer considerations apply.
Layer Three: Admin Visibility - Why User Management Is a Privacy Decision, Not Just an IT One
Anyone with user-management access can see ad and audience data and can grant it onward. That is an account-governance issue, not an inbox setting. Review the user list quarterly, remove stale agency logins, and prefer manager-account access over shared credentials.
Consent Mode and Privacy Toggles Are Not the Same Thing
Consent Mode governs how tags behave before a visitor consents, and matters most for EEA and UK audiences. A colleague switching off their personal ad personalisation is unrelated. If you serve European traffic, your conversion tracking and CRO setup needs Consent Mode configured alongside clean server-side tracking - not instead of it.
Privacy settings are hygiene, not compliance. They support a POPIA conversation; they do not create a lawful basis, safeguards or consent records on their own. Treat them as one input, not the answer.
How the Three Layers Map to Owner and Review Cadence
| Control | Owner | Cadence |
|---|---|---|
| Web & App Activity, My Ad Center | Individual | Annually |
| Ads roles and product links | Marketing lead | Quarterly |
| Customer Match and consent records | Marketing lead + counsel | Per upload |
| User management access | Business owner | Quarterly |
Comparing the Controls: What Each Setting Changes, Who It Applies To and What It Leaves Alone
| Setting | Changes | Leaves alone |
|---|---|---|
| Web & App Activity off | Stops activity being saved to the account | Ad account performance data |
| Ad personalisation off | Stops activity-based targeting | Ads appearing; campaign delivery |
| Auto-delete window | Limits retention of personal activity | Ads audience lists; conversion history |
| Role removal in Ads | Revokes ad and audience visibility | Personal account settings |
What a South African Team Should Document for a POPIA Conversation
Keep a simple register: which account holds which role, the lawful basis for each audience list, consent and opt-out evidence for Customer Match, and where conversion data is reported. Pair that with reporting that separates platform-reported conversions from verified outcomes so the data trail matches the story.
Building a Repeatable Privacy Review Into Your Ad Account Onboarding
Fold the review into onboarding rather than running it ad hoc. A workable checklist:
- Confirm each individual's consumer privacy settings independently of business access
- Assign minimum viable Google Ads roles
- Document Customer Match consent per list before upload
- Confirm Consent Mode status for any EEA/UK traffic
- Record review dates in the account governance note


