← Back to Infracis

Transparency

Data & privacy

Infracis investigates a location using public data sources. This page explains the current source-code behavior; it is not a substitute for an approved legal privacy notice for a future hosted service.

Information you submit

When you investigate a place, the location text or selected coordinates are sent to the Infracis server route to retrieve relevant location data. A location can be sensitive: submit only what is needed for your investigation, and avoid adding names, phone numbers, apartment access details, or other personal information to the search field.

External data providers

To produce a report, Infracis sends the necessary query or coordinates to the providers below when the relevant source is enabled. Their own terms, privacy practices, availability, and data policies apply. Provider failures and disabled sources are shown as unavailable rather than being replaced with invented data.

  • OpenStreetMap Nominatim

    Resolves the location text you submit into a place label and coordinates.

  • Open-Meteo

    Provides weather and air-quality model output for the resolved coordinates.

  • OpenStreetMap Overpass

    Returns mapped amenities around the selected location through a bounded best-effort public Overpass endpoint list, unless an operator configures alternatives. Public service availability is not guaranteed; mapped features may be incomplete.

Temporary server-side cache and request limits

When the shared Redis service is configured, Infracis temporarily caches provider results to reduce repeat requests and comply with provider limits. The cache key for geocoding includes the normalized location text and its result may be retained for up to 24 hours; weather results are cached for up to 5 minutes, air-quality results for up to 10 minutes, and mapped amenities for up to 1 hour. In local development, geocoding and amenity results can also be cached in per-process memory for up to 24 hours and 1 hour respectively. These are operational caches, not saved reports or user accounts.

The analysis route also keeps a per-instance in-memory copy of a generated report for up to 15 minutes to reduce repeat provider calls. This cache is volatile and is not a saved-report feature, but the query and report data remain in server memory during that window.

The shared rate limiter also temporarily stores a client-IP-derived request counter and a global geocoding-slot timestamp. Avoid putting names or other personal information into location searches. Production requests fail closed if the shared rate limiter is not configured or cannot be reached. The eventual hosting operator must verify access controls, retention, and deletion behavior for the configured cache service before public launch.

Saved reports and exports

The current product stores saved reports in this browser on this device using browser storage. Cloud sync, user accounts, and server-side report persistence are not available. Anyone with access to this browser profile may be able to access those saved reports. You can delete saved reports inside Infracis or clear this site's browser storage.

Exporting a report downloads a JSON file to your device. After export, that file is under your device's storage and sharing controls.

Limits and operational transparency

Weather and air-quality values are model estimates, not on-site sensor readings. OpenStreetMap features are community-mapped and may be missing or outdated. A missing mapped feature does not prove that a service is absent.

Infracis has not been deployed as part of this work. Before any public launch, the operator must verify the actual hosting environment's access logs, telemetry, backups, retention, and deletion settings and publish a final policy that reflects those settings.

Questions or corrections

For source-code questions or to report a data-transparency issue, use the project repository.

Open a GitHub issue