Privacy Policy

Address Context processes the addresses you search, the property information you choose to save in your browser, and the resident insights you submit. Requests to the site and its integrated services also involve technical information, such as IP addresses and request URLs. Analytics and advertising services process additional information as described below.

The resident review form does not ask for a name, email address, telephone number or account registration. Any personal information you include in a written review becomes part of that submission. The separate administrator sign-in form processes a password to authorize moderation access.

When you search, the address is sent to our geocoding endpoint and then to the U.S. Census Bureau to find a matching address and coordinates. Our property research endpoints use the address, coordinates, parcel references or broader geographic identifiers, as needed, to retrieve property, tax, market, crime, environmental and internet-availability information.

Some lookup results are temporarily cached on the server. The search feature does not write a persistent search-history record to our application database. This is separate from browser storage, resident review records, and information processed by analytics or infrastructure services.

The selected property is stored in your browser so you can move between research sections. Property-sharing links include the address in the URL; recipients can view that address. URLs may also appear in browser history, request logs and analytics. Avoid putting confidential information in a search or shared link.

When you submit through the resident insights form, we store the following in Supabase:

• The property reference key, property address, latitude and longitude.
• Your selected role: current resident, former resident, owner or visitor.
• The ratings you provide for noise, parking, maintenance, internet, safety and overall experience, and your optional written comment.
• A record identifier, creation time, moderation status (pending, approved or rejected), and an update time when a moderation decision is recorded.
• An IP-derived hash, when an IP address is available, for submission rate limiting.

The submission endpoint reads an IP address from request headers and transforms it with a secret-keyed HMAC-SHA256 hash. It stores that hash, rather than the raw IP address, in the resident insights record. The hash is used to limit submissions from the same source. This does not mean that hosting, analytics or advertising services cannot separately process an IP address.

Submissions start as pending and can be reviewed by administrators. Approved contributions can display your role, ratings, comment and submission date alongside the property. Do not include contact details, sensitive personal information or information about other people that you do not want published. Features labeled “Coming soon,” including the draft community question composer, do not currently submit those drafts.

We use Google Analytics (GA4), when enabled for the site, to measure site usage and traffic. The Google tag supports page-view and usage measurement, including page URLs, browser and device information, and interactions collected by enabled Google Analytics settings. The site does not add custom GA4 events containing resident review text or search form contents. A property address in a visited URL may nevertheless be included in page measurement.

We also use Vercel Web Analytics for page views and traffic measurement. Our custom events record that a property search succeeded (with the source “address_search”) and that a research tab was opened (with the section name and source “top_tabs”). These custom event fields do not include the searched address or review text. Vercel describes its Web Analytics measurement as cookie-free; see Vercel’s analytics privacy information.

Google provides a Google Analytics opt-out browser add-on for supported browsers. Browser privacy controls can also limit tracking technologies.

The site integrates Google AdSense. Third-party vendors, including Google, may use cookies or similar technologies to serve ads. Google advertising cookies help Google and its partners serve ads based on visits to this site and other sites on the Internet.

You can manage personalized advertising preferences through Google Ads Settings. Learn more about how Google uses information from sites and apps that use its services.

Google analytics and advertising services may set or read cookies and use similar technologies. Where a Google consent management platform (CMP) message is enabled and displayed, including for visitors in the European Economic Area (EEA), the United Kingdom and Switzerland, it may offer advertising and cookie consent choices. Use that message and any available privacy settings control to manage or revisit your choices.

We use localStorage for “selectedProperty” (the matched address, coordinates and available address components) and “savedProperties” (addresses you choose to save). These browser records have no automatic expiration in the application. You can remove saved properties using the save control where available, or clear this site’s storage in your browser. Clearing storage may reset your property selection and saved list.

Administrators receive an HTTP-only session cookie named “project_reality_admin” after successful sign-in. It expires after eight hours and is cleared on sign-out. It is used for moderation access.

• Match searched addresses and assemble relevant property research.
• Keep your chosen property available across research sections and support saved properties and sharing.
• Store, moderate and publish resident contributions, and limit abusive submissions.
• Measure traffic and feature usage, and support advertising.
• Authenticate administrators and diagnose service errors.

Resident insight storage and moderation use server-side database access, and moderation endpoints require an administrator session. These controls help restrict access; they are not a guarantee against every security risk.

The services contacted depend on the feature, location and enabled provider configuration:

• Google: Analytics and AdSense as described above, and consent messaging where enabled. Google Maps and Street View links send the selected property location to Google when you follow them.
• Vercel Web Analytics: site traffic and feature-use measurement.
• Supabase: storage and moderation of resident insights, including the fields listed above.
• U.S. Census Bureau: address geocoding, coordinate-based geography lookups and American Community Survey statistics.
• OpenStreetMap: building data through Overpass services and map tiles loaded directly by your browser. Tile requests reveal the requested map area and involve your IP address.
• Regrid: coordinate-based parcel and property/tax lookups when the provider is configured and available.
• Los Angeles city and county data services: parcel, assessment, zoning, land-use, boundary and permit records, using location or property references.
• FEMA National Risk Index and U.S. Bureau of Transportation Statistics: geographic hazard and transportation-noise data delivered through Esri ArcGIS services.
• InternetProviders.ai: property coordinates for internet availability based on FCC-reported data. This lookup goes to InternetProviders.ai, rather than directly to the FCC.
• FBI Crime Data Explorer and Austin and San Diego public-data services: crime information requested by geographic area or reporting agency, where supported.
• Federal Housing Finance Agency (FHFA): downloaded public house-price datasets used for market context.

Public-data requests generally originate from our server. Providers receive the location or lookup parameters needed for the request, rather than the contents of your resident review. Direct browser requests, such as analytics, ads and map tiles, involve browser connection information. Third-party services handle information under their own policies.

Resident insight records, including moderation information and the anti-abuse hash, are stored in Supabase. The current submission and moderation system does not set an automatic deletion period. The one-hour submission-rate check is not a one-hour deletion schedule.

Selected and saved properties remain in browser storage until replaced or removed. Server lookup caches are temporary and vary by feature; property and tax caches use a 24-hour freshness window. Cache freshness does not establish a retention period for provider records or infrastructure logs. Analytics, advertising and provider retention also depends on those services and their settings; we do not specify a fixed period for them here.

• Choose whether to submit a resident review and what to include. Approved content can be public.
• Clear site data or control cookies through your browser settings. Some preferences or features may reset or stop working.
• Use Google Ads Settings and the Google Analytics opt-out option linked above.
• Where a CMP message or privacy settings control is available, use it to manage advertising and cookie consent. Ad-personalization settings do not turn off all analytics or all cookies.
• Consider who can access a property-sharing link before sending it.

Address Context’s property research tools are intended for a general audience and are not directed to children under 13. The resident insights form does not ask for age or date of birth. Children under 13 should not submit personal information through resident reviews.

We may update this policy as the site’s features or data practices change. Updates will be posted on this page with a revised “Last Updated” date.

For questions about this Privacy Policy or how Address Context handles information, contact contact@addresscontext.com. Please do not use a public resident review to send a private privacy inquiry.