Privacy notice

At a glance

The tool is designed for food-access planning, not advertising or individual profiling. Most map calculations use data prepared in the active bundle. A normal map check does not create a public report. A saved report is different: it retains the submitted location and creates an unlisted public link that anyone with the link can open.

Ordinary map and address checks

A normal map check is processed to return the requested result and is not published as a report. The application may create a short-lived anonymous operational record for rate limiting, troubleshooting, aggregate administration, and service maintenance. These non-saved search records are configured for deletion after 90 days.

Saved reports and public links

When a user requests an official or saved result, the application stores the submitted input, matched address when available, latitude and longitude, assessment result, selected view, travel mode, data summary, and a generated UUID. The UUID URL is unlisted, not password-protected: anyone who receives it may view the report until it expires. Saved reports are configured for deletion after 1,095 days.

Address verification and geocoding

Street-address searches are sent to the U.S. Census Bureau geocoder so the application can verify and locate the address. The geocoder may return a standardized or approximate match, and the result identifies the provider and match status when available. ZIP-code and city/town lookups use bundled local data. The application does not send a city or ZIP lookup to a per-search routing provider.

Bundled processing and map services

Store records, coverage geometry, census geography, demographic layers, routing coverage, and city/town centroids are read from the active data bundle. The map may request basemap tiles from OpenFreeMap while you pan or zoom. The local GraphHopper preparation process is used to create routed coverage before a bundle is uploaded; the public lookup normally reads that prepared coverage instead of routing each request again.

Operational, security, and administrator records

The hosting platform and application may record operational information needed to protect and operate the service, such as authentication events, rate-limit events, error records, administrator actions, bundle activation records, and ordinary web-server logs. These records are access-controlled and are handled according to the hosting configuration, security procedures, and applicable records requirements.

Retention settings

The current application settings provide these automatic cleanup windows:

• Anonymous non-saved search records: up to 90 days.
• Saved reports with public UUID links: up to 1,095 days.
• Geocoder cache records: up to 180 days.
• Route cache records: up to 180 days.

A legal hold, security investigation, backup, or hosting-system retention rule may require a record to remain longer. The site administrator is responsible for reconciling those requirements.

Sharing and tracking

The tool does not sell location searches, use advertising trackers, or create an advertising profile. Essential session, security, and language-preference cookies may be used. A saved report is intentionally shareable by URL, so do not save a location that should not be shared through an unlisted link.

Your choices

You can use ordinary map checks without creating a saved report. Do not submit a precise address when a ZIP code or city-level result is sufficient. To ask about a report, retention, deletion, or an accommodation, use the contact methods below.

Questions and requests

For privacy questions, corrections, deletion requests, or accessibility accommodations, contact the current site administrator using one of these methods:

Email

redwards@viablefood.org

Telephone

618-306-6480

Read the accessibility statement