Privacy boundary

Permit history, not people search.

The fact that a government portal exposes a field does not mean Permit Archive should retain or republish it. Personal and contact fields are denied before durable storage.

01 / Fields

A default-deny boundary at capture.

Kept when permitted

Permit identifiers, types, status, and public description
Application, issue, expiration, and completion dates
Project/site address and parcel identifier
Declared valuation, square footage, units, and public fees
Contractor business name and public business-license facts
Source URL, capture time, evidence hash, and rights record

Denied before storage

Personal email addresses and all phone numbers
Homeowner, applicant, qualifier, or individual names
Contractor home, mailing, or permit-holder addresses
Birth dates, signatures, IDs, accounts, or credentials
Unreviewed complaint narratives or allegations
Any newly added source field until separately reviewed

Public controls

Suppression overlays hide a record without rewriting evidence
Suppressed records stay out of pages, search, sitemaps, and APIs
Legally required deletion overrides the archival preference
Important facts always link back to the official source

02 / Requests

No public record pages exist yet.

The removal channel opens before record publication.

The documented process is available now. Intake, rapid high-risk suppression, and reviewer contact will be activated before any individual permit page becomes public.

Read the removal process

03 / Measurement

Aggregate site traffic, without an advertising profile.

Cloudflare Web Analytics measures the public foundation.

The public site uses Cloudflare's cookie-free Web Analytics beacon to count visits and page views and to measure page performance. Permit Archive does not add Google Analytics, an ad pixel, cross-site identifiers, or a visitor account to this foundation release.

Private captures, permit rows, evidence objects, source queries, and denied personal fields are never sent to Web Analytics. Traffic counts describe measured browser visits; they do not prove search demand, indexing, customers, or revenue.