Where is data stored?

Primary database: Supabase PostgreSQL

Your audit results, property configurations, user accounts, and billing metadata are stored in a Supabase-hosted PostgreSQL database. The database is located in the eu-west-1 (Ireland) region. Supabase uses AWS infrastructure for this region.

Row-Level Security (RLS) is enabled on all tables containing user data. RLS policies ensure that database queries can only return rows belonging to the authenticated user. there is no application-level code that can accidentally expose one user's data to another.

API backend: Cloud Run (europe-west2)

The Tag & Analytics Audit backend API and audit worker services run on Google Cloud Run in the europe-west2 (London) region. Cloud Run is a serverless container platform. instances scale to zero when not in use and spin up on demand. Audit jobs run as ephemeral containers, and no persistent state is stored on the container filesystem.

Task queue: Upstash Redis

Audit jobs are queued using Celery backed by an Upstash Redis instance. Upstash Redis is configured to use the eu-west-1 (Ireland) region. The task queue holds job metadata (property ID, audit configuration, status) while audits are running. Task payloads are cleared from Redis once a job completes.

Frontend: Vercel Edge Network

The Tag & Analytics Audit web application is hosted on Vercel. Static assets (HTML, CSS, JavaScript) are distributed globally via Vercel's Edge Network CDN for performance. Dynamic server-side rendering runs in Vercel's EU compute regions. No user data is processed at edge nodes. all data access goes through the Cloud Run API.

Data transfers outside the EU

When Tag & Analytics Audit queries the Google Analytics APIs, data flows between our Cloud Run instance (EU) and Google's API infrastructure. Google's API servers are globally distributed, but the GA4 Data API for EU properties operates under Google's EU data processing terms. No audit data leaves our EU infrastructure. API responses are processed in-memory in Cloud Run and only the derived check results are written to the EU database.