GeoEVENVIRONMENTAL SCREENING

TRANSPARENT BY DESIGN

Where your data goes.

This notice describes the implemented application and the proposed free public release. Private preview configuration may have some controls disabled.

Drawings and screenings

Drawing stays in the tab until you run a test or export. A test sends the area and its properties to the GeoEV server. The server sends the area geometry and configured query parameters to your selected environmental data providers. It returns enriched GeoJSON directly; the application does not persist screening geometry, result attributes or a job history.

Shapefile imports

When enabled, your ZIP is uploaded to GeoEV for bounded in-memory conversion and projection to WGS84. Files are not extracted to disk or retained as application records. Importing alone does not query environmental services. Keep your own original files and review converted geometry before screening.

Maps and external services

The map loads OpenLayers from jsDelivr, basemap tiles from OpenStreetMap, and imagery and legends from selected providers. Those services receive normal connection metadata and the map extent needed to serve content. Screening providers receive the query geometry. Their own policies apply; GeoEV cannot control their retention.

Security cookie and usage counters

When usage limits are enabled, a signed daily cookie recognizes a returning browser for rate limiting. It is not a person’s identity and is not used for advertising. Shared counters retain only keyed identifiers, counts and expiry timestamps. Counter records become eligible for automatic deletion two days after their window resets; cloud deletion can take additional time. Clearing the cookie does not remove the service-wide allowance.

Operational logs

Application events record request IDs, duration, status, source keys and completeness without bodies, geometry, attributes, cookies or filenames. Google Cloud and network services may separately record connection and request metadata, including IP addresses. Log access and retention must be configured by the operator before public launch.

Diagnostics and contact

The browser diagnostic log stays in memory until reload unless you download it. A contact submission is sent only when you choose Send. Contact text and an optional reply address reach the operator’s mailbox; no geometry or diagnostic file is attached automatically. Bot verification uses Cloudflare Turnstile when the form is enabled.

Use suitable data

Do not submit restricted, confidential or personal data unless your organization has approved this use and the receiving services. Avoid putting private information in names, URLs or support messages.

For privacy questions, use the protected contact form. The operator’s email is not published on the page. This notice should be reviewed against the final hosting and retention configuration before public release.