What this site knows about you.

• One third party: Google Analytics. It is told your IP address, your browser, and which pages you read here. Advertising and cross-device tracking are switched off. Details below, including how to stop it.
• Everything else is served from this origin. The fonts, the mapping library, the map geography, the documents — none of it comes from a CDN or an embed, and the site’s Content-Security-Policy enforces that rather than asking to be believed.
• No account, no login, no newsletter, no ads, no ad networks, no social widgets, no session recording, no fingerprinting, no A/B tooling.
• Nothing you do here is stored by this project except a message you deliberately send through the tip form, which is delivered as email and not kept in a database.

Google Analytics 4 runs on every page of this site. It loads a script from googletagmanager.com, which means Google receives your IP address, your user agent, your approximate location derived from that address, the pages you visit here, and the referrer that brought you. It writes a first-party cookie so that a second visit from the same browser is recognized as the same browser.

Two of its features are switched off in the configuration this site ships, and you can verify both by reading the page source:

• allow_google_signals: false — no advertising identifiers, no remarketing audiences, and no stitching of your activity here to a signed-in Google account across devices.
• allow_ad_personalization_signals: false — nothing collected here is used to target advertising.

There is a third setting the site does not have to ask for. On some page loads the tag also attempts a request to www.google.com, which is the beacon behind the advertising features named above. This site’s Content-Security-Policy does not list that origin, so the browser refuses the connection outright — the ordinary analytics beacon goes through and that one does not. You can watch it happen: open your browser’s developer console on any page here and the refusal is printed as a CSP violation. That is the policy doing the thing a policy is for, rather than a promise about what a third party will choose to do.

What it is here for is dull and worth stating: how many people read this, which chapters they reach, and which documents get opened. Nothing on this site is sold, and there is nothing to convert anyone to.

To stop it: any content blocker (uBlock Origin, Privacy Badger) blocks it outright; Firefox and Safari block it by default in their standard settings; Google publishes an opt-out browser add-on; and a Do Not Track or Global Privacy Control signal from your browser is a good reason to use one of the first three, because Google Analytics does not honour either. Blocking it costs you nothing on this site — no feature here depends on it, and no page will notice.

It is fair to point out the tension. The rest of this site was built to keep a reader of a page about surveillance from being handed to a third party before it drew: the mapping library is vendored, the typefaces are self-hosted, and the chapter maps stopped using CARTO’s tile CDN precisely because requesting a map tile tells someone else which part of a map you were looking at. Analytics is a deliberate exception to that, made with open eyes, and this paragraph exists so it is not a quiet one.

This site is served by Vercel. Serving a page requires receiving a request, and a request carries your IP address, the page you asked for, your user agent and your referrer. Vercel handles those to deliver the response and keeps operational logs of them for a limited period. That is true of every website you have ever loaded, including this one, and no privacy policy can make it untrue.

What this site does not do with them: there is no server-side logging of readers by this project, no log retention under its control, no analytics database, no visitor table, and no account of any kind to create.

The form at /contact takes a message, optionally an email address, and optionally a note about what it concerns. It sends them as an email to one mailbox, through Resend, and that is the entire life of the data. There is no database behind it: the email is the record. If the send fails, the message is lost, and the page says so rather than showing you a tick.

The email includes the IP address the message was sent from, alongside the time — the same thing any mail server records, kept because a form with no attribution at all is a form that cannot be triaged when it is abused. Leave the address field blank and the message is otherwise anonymous; there is then no way to reply, which is the trade.

Addresses given here are used to reply and for nothing else. There is no list, no newsletter, and nothing is passed to a third party.

One cookie, set by Google Analytics: _ga, and a _ga_<id> alongside it. They hold a randomly generated identifier for your browser and nothing else — no name, no address, nothing you typed. They expire after two years, and clearing site data removes them immediately.

This site sets no cookies of its own, and uses no localStorage, no sessionStorage and no IndexedDB. There is no consent banner because there is nothing here to consent to beyond the one cookie above, which your browser and any blocker can refuse without breaking a single feature.

Filters, searches and map positions are held in the page's own URL — that is why the address bar changes as you use them. It stays in your history the way any URL does, and it is not sent anywhere by this site.

Everything published here was produced by the City of Alpharetta in answer to a written request under the Georgia Open Records Act. It concerns a government program: cameras, agencies, agreements, alert counts and money. It is aggregate and institutional.

One production received in answer to that request is deliberately withheld and appears nowhere on this site, in any form — it concerns named individuals rather than the ALPR program. It is excluded by the manifest the site is built from, so it cannot reach a page, a search index, a sitemap or a link.

No plate numbers, no individual reads, and no personal records are published here. If you believe something on this site identifies a private individual, say so at /contact and it will be looked at.