Privacy for station discovery and reports.

• You can browse BlueEV station data without creating a public user account.
• We collect app and device metadata needed to operate the service, debug issues, and understand directions usage.
• Station reports, feedback, optional photos, and optional email addresses are used to fix station data and reply to you.
• We do not sell your data, use it for advertising, or use it to train models.

BlueEV serves public charging-station data such as provider name, location, connector details, power, availability, pricing when available, images, and app or map links. This station data is about chargers and providers, not about you.

When the iOS app talks to the BlueEV API, it may send an install ID, vendor ID, device model, device model identifier, OS name and version, app version, build number, bundle ID, locale, and time zone. We use this to keep the API working, understand compatibility issues, and associate directions cache usage with an app install.

For feedback, reports, and rate limiting, we may also store app metadata you submit with the message and hashed versions of your IP address and user agent.

If you ask BlueEV for directions, the app sends an origin and destination. The origin can be your current coordinate or another station, and the destination is the station you selected.

BlueEV uses that request to return a route. For driver-to-station routes, we round the driver origin to a small grid cell for route lookup and caching. When a route is not already cached and Google Directions is available, the rounded origin and station destination are sent to Google to calculate the route. If Google Directions capacity is unavailable, BlueEV may use OpenRouteService for the route instead.

When you submit feedback or a station report, we store what you send so we can review it and improve BlueEV. That can include:

• Message text and report category.
• An optional email address if you want a reply.
• Optional photos, screenshots, or uploaded files.
• App version, build number, platform, OS version, device model, locale, and time zone when provided by the app.
• For station reports, the station ID connected to the issue you reported.

We use a small set of services to operate the app and API:

• Cloudflare for hosting the API, database, cache, and uploaded report files.
• Google Maps Directions API for route calculation when a route is not served from BlueEV cache.
• OpenRouteService as a fallback for route calculation when Google Directions capacity is unavailable.
• Supported charging providers for station, connector, status, pricing, and image data that appears in BlueEV.

• You can choose not to include an email address in feedback or station reports.
• You can control location permission for BlueEV in iOS settings.
• You can ask us to delete or de-identify support and report data associated with your email or device where we can reasonably identify it.

We keep operational records, station reports, feedback, and uploaded files for as long as they are useful to operate BlueEV, fix station data, prevent abuse, or satisfy legal obligations. We delete or de-identify data when it is no longer needed.

If we make material changes to this policy, we'll let you know in the app before the changes take effect.

Questions about this policy? Write to privacy@picktek.com.