Privacy policy
What GA4 BigQuery PII Auditor accesses, what it stores, and for how long.
What we access
When you connect your Google account, this tool requests two permissions: the BigQuery
scope (bigquery — to list the GCP projects' BigQuery datasets and tables you
select, and run SELECT/dry-run queries against them) and a narrow Resource Manager scope
used only to list the GCP projects you can see, so you can pick one from a dropdown. With
these it can read: the names of your BigQuery projects and datasets, the daily GA4 export
tables in a dataset you explicitly select, and — for the two audits it runs — event names,
event-parameter/user-property/item-parameter field names (never their
values), and per-day event counts. This tool's own code never calls a write or delete API —
it only ever runs dry-run and SELECT queries. What actually prevents it from writing to or
deleting anything in BigQuery is the IAM role you (or whoever signs in) hold on the target
project: grant "BigQuery Data Viewer" + "BigQuery Job User" (not Editor/Owner) and this tool
is unable to change anything there, regardless of what the OAuth permission allows in
principle.
What we do with it
Each audit is run on demand. When you select a project and dataset, the tool queries BigQuery for the window you chose, summarizes the results in memory, and renders the report in your browser. Query results are not written to a database or log file — they exist only for the duration of that one request, to build the page (or CSV/YAML export) you asked for.
Who we share it with
Nothing is sold, shared with third parties, or used for advertising. No analytics or tracking scripts run on this tool. The only places your data goes are: Google's own BigQuery and Resource Manager APIs (to fetch and query the project/dataset you selected) and this app's own server (to summarize it and render your report) — nowhere else.
What is stored, and where
Only one thing is kept beyond a single request: your Google OAuth token, held in your browser's signed session cookie for the duration of your session. It is never written to a server-side database, disk file, or log. Signing out (or clearing cookies) removes it. Unlike the GTM Naming Auditor, this tool has no "confirm and remember" feature — nothing else persists server-side between visits.
How we protect it
The site is served over HTTPS, so traffic between your browser and this app is encrypted in transit. Your Google OAuth token lives only in a signed, HTTP-only session cookie — it's never written to a database, disk file, or log, and a signature check stops it from being tampered with. The server itself sits behind an access password before any of this is reachable.
How long we keep it, and how to have it removed
Your Google sign-in lasts only for your browser session — it's gone as soon as you sign out or clear cookies, and nothing about that session is kept afterwards. There is nothing else kept server-side to remove.
Who can see this
Only the person who connects their own Google account sees that account's data — each audit runs against the Google credentials of whoever is signed in, and the report is shown only to them.
Questions
For questions about this tool or this policy, contact fanny@datawithfanny.com.
See also: what this tool does.