Privacy

Last updated 4 October 2026.

P&Z Radar reads public Planning & Zoning agendas from municipal websites and emails the results to subscribers. It is operated from the United States by the same person who runs LaborCurrent (formerly WARN Firehose). Questions, corrections and deletion requests all go to questions@pnzradar.com, and a real person answers them.

What we collect

Your email address and your alert settings. That is the account: the address alerts go to, the plan, the cities, counties, keywords and watchlist parcels you chose, and whether you want alerts instantly or as a daily digest. You give us all of it directly.

Payment details — which we never see. Card payments run entirely through Stripe. Card numbers are never sent to, processed by, or stored on our servers. We keep only the customer and subscription identifiers Stripe gives us, so we know your plan is active.

What you type into the contact form — name, email and message — so we can reply.

Aggregate traffic statistics, via Plausible Analytics. Plausible is cookieless, stores no personal profile, and does not track you across other sites. Our application omits Plausible from private/noindex pages, such as your profile, filter settings and trial-verification pages. This is a restriction on our Plausible integration, not a claim that no service processes those requests.

Campaign attribution. When you arrive at /try through a campaign link and submit a trial signup, we record campaign parameters and valid Google ad-click identifiers (gclid, gbraid and wbraid) with the trial. We use them to measure which campaigns lead to verified trials. Our offline-conversion export contains the captured click identifiers, a PNZ-specific conversion name, the verification time, and an opaque Order ID for deduplication. It does not include your email, name, subscriber ID or access token. These identifiers are attribution data, even though the export omits those account details.

The export creates a file; it does not send it to Google. Uploading that file to Google Ads would disclose those conversion records to Google for campaign measurement and requires a separate decision before it is performed. This policy update does not activate uploads. No Google advertising website tag is used for this capture-and-export flow.

Pip assistant. If you use Pip, we process your question and recent conversation turns to answer it. Recent turns can be saved in this tab's session storage. When optional AI answering is enabled, your question, recent history and relevant public-page context are sent to Anthropic to generate an answer. Do not enter passwords, access tokens or other sensitive information.

Business addresses from public records

We also send cold introductory emails to businesses that appear as applicants or agents in the public municipal documents we already read — the same packets the cases come from. Those addresses are published in public records; we skip government, school and municipal-platform domains. We store the address, the filing it came from, and whether we have written to you.

Every one of those emails carries a one-click unsubscribe link, and unsubscribing is permanent — the address is recorded as opted out so a later run cannot pick it up again. You can also just reply and ask, or write to questions@pnzradar.com, and we will remove it by hand.

What we never do

We do not sell, rent or trade personal information or buy email lists. We measure our own advertising campaigns as described above; the current application does not embed Google advertising tags or retargeting pixels.

Who else touches it

Only the services that make the product work: Stripe (payments and billing), Amazon SES (sending email), Plausible (aggregate analytics), Cloudflare (website delivery, security and performance reporting), and our own server on Amazon Web Services, where the database lives. Each gets only what its job needs. Google would receive offline conversion records only if a separate upload is performed, as described above. Anthropic receives the Pip inputs described above when optional AI answering is enabled.

Cookies

The application uses functional cookies for signed-in sessions, the owner's admin login and, where enabled, restricted preview access. Plausible analytics and the trial click-identifier capture described above do not require advertising or tracking cookies. Stripe's hosted payment pages may use their own cookies for payments and fraud prevention.

The zoning data itself

Cases, applicants, addresses and hearing dates come from public records published by cities and counties. We extract and organise them; we do not create them, and we cannot remove a case from a city's own public record. If we have got a detail about a filing wrong, tell us and we will fix it.

Keeping it, and getting rid of it

Account data is kept while the account exists. Every alert email has an unsubscribe link that works immediately and without logging in. You can change your cities, keywords and delivery settings any time from your profile. Ask us to delete your account and we will delete it, along with the address, rather than merely deactivating it.

Changes

If this policy changes materially we will update the date above and say so to active subscribers.