Privacy Policy

Last updated: March 2026

Overview

TripRisk is designed with privacy in mind. We do not require accounts, we do not run ads, and we do not sell or share your data with third parties. This policy explains what information we collect and why.

What We Collect

Route requests

When you plan a route, we log the origin and destination addresses, the routing strategy chosen, response time, and any error information. This helps us monitor service health and improve performance. We do not associate route requests with individual identities.

IP addresses

Your IP address is processed to detect automated traffic (bots) and for basic analytics (unique visitor counts). We do not use IP addresses to identify or track individual users across sessions.

Bug reports & contact messages

If you submit a bug report or contact message, we store the information you provide (description, email if given, browser user-agent). Email addresses submitted via these forms are used only to respond to your message.

What We Don't Collect

  • No user accounts or passwords
  • No real-time GPS or location tracking
  • No advertising identifiers or tracking pixels
  • No personal information beyond what you voluntarily submit

Cookies & Local Storage

TripRisk uses a session cookie for administrative functions and localStorage to remember your map preferences (e.g., crash icon style, settings). These are strictly functional — we do not use tracking cookies or third-party analytics cookies.

External Services

To provide routing and weather features, TripRisk makes server-side requests to the following external services:

  • OpenStreetMap / Nominatim — address geocoding (converting addresses to coordinates). Your origin and destination addresses are sent to this service.
  • Open-Meteo — weather data along the route. Only geographic coordinates are sent, not addresses or personal information.
  • MapLibre / map tiles — the base map is loaded in your browser from a tile server. Standard web requests (IP, user-agent) apply.

These services have their own privacy policies. We encourage you to review them if you have concerns.

Data Retention

Request logs are retained for operational monitoring and may be periodically purged. Bug reports and contact messages are retained until resolved or deleted by an administrator. We do not maintain long-term archives of individual user activity.

Changes to This Policy

We may update this policy as the service evolves. The “last updated” date at the top reflects the most recent revision.

Questions?

If you have questions about this privacy policy, please reach out via our contact page.