Address privacy
Your home address is not a profile.
CivRep uses an address only long enough to determine which public boundaries apply, then discards it.
Protected in transit
Address forms submit with POST over TLS. An exact address is never placed in the page URL.
Excluded from analytics
Exact addresses are not sent to analytics, advertising systems or CivDIP research profiles.
Not retained
The CivRep application does not write an address to its database, cache, backup or search history.
Not repurposed
Addresses are not sold, shared for marketing, used to build audiences or attached to an account.
Technical handling
The lookup endpoint rejects GET requests, limits request size and disables caching. During a lookup, the address is sent over TLS to Brunswick County's official GIS address locator. The resulting point is checked against official county boundary layers and U.S. Census district geography. CivRep returns only district names and officials, never the submitted address or coordinates, and clears the in-memory address after processing.
Abuse prevention
Short-lived request limits use a salted, one-way token derived from the network address supplied by the hosting edge. The raw address and submitted search are not placed in the limiter, stored in a visitor profile or retained by CivRep.
Exact boundary matching
A result appears only when the official county address file and each required boundary layer return an exact match. If a service is unavailable or a boundary is ambiguous, CivRep stops the lookup instead of filling gaps or inferring a district.
Manual alternative
You can browse a community without entering a home address. Manual selections stay in the current browser tab and are not saved. They do not claim to identify address-specific district seats.