Privacy Policy

1. Information you provide

When you register, the application stores your email address, display name and a salted password hash. It stores saved places, planned drives, submitted reports, report confirmations and support tickets with your account. If you explicitly save settings to your account, it stores those settings. Passwords are hashed rather than stored as readable passwords.

2. Location, searches and navigation

With your permission, your device uses foreground location for positioning, speed and navigation. Coordinates are sent to the application and configured routing provider when you request or recalculate a route. Destination queries are sent through the application to the configured geocoder. Route responses may be cached temporarily in server memory for about one minute. Geocoding results are cached in a bounded server database for up to 24 hours; cache keys are hashes of provider request URLs, and cached results may contain address labels and coordinates.

The application does not create a continuous GPS trail. If you submit a road report, its coordinates are stored and displayed publicly. Optional navigation history stores selected navigation destinations, not a continuous location trace. Sharing a destination link discloses the destination coordinates and label to anyone who receives that link.

3. Cookies, browser storage and technical data

An essential, secure session cookie keeps you signed in and normally expires after seven days. Browser storage holds interface, sound, language and map preferences. Clear site data to remove browser preferences and cookies. You can also sign out through Account.

The application uses request IP addresses temporarily for abuse rate limits. Hosting and reverse-proxy systems may also record IP addresses, request URLs, timestamps and errors in operational logs. Such URLs may contain search terms or requested route coordinates. Administrators control operational log configuration and retention.

4. Why data is used and who can access it

Data is used to authenticate accounts, provide navigation requests and saved content, display community reports, synchronize chosen settings, respond to support tickets, moderate abuse and maintain service security. Authorized administrators can manage accounts, review reports and support tickets, and view administrative audit records. Saved places, trips, settings and history are restricted to the account through the user API.

Data may also be disclosed when required by applicable law or reasonably necessary to address security incidents or protect legal rights. The current application contains no advertising tracker or personal-data sales feature.

5. External providers

Map tiles load from OpenStreetMap and reveal your IP address and the map regions requested. Leaflet software loads from unpkg; Google Fonts supplies fonts on certain pages. These providers receive connection information. Configured routing and geocoding providers receive the request information described above. If no geocoder was configured, the update deployment selects the public Photon service at photon.komoot.io for low-volume address searches. Search terms are sent to that service. Their privacy practices and hosting locations may differ from ours.

See Photon service information, OpenStreetMap Foundation privacy information, Google privacy information and unpkg. The current build does not connect to Waze accounts or a Waze traffic feed.

6. Retention and deletion

Community reports are displayed for two hours; the scheduled maintenance worker deletes expired reports and sessions. Optional navigation history is limited to the latest 100 destinations for your account. Other account records remain until you remove them or delete your account.

Account deletion removes active account records, sessions, saved places, trips, reports, confirmations, preferences, history and support tickets. Administrative audit entries may remain to document security and moderation actions. Database backups are configured to rotate after seven days when the maintenance timer is operating; deleted records may remain in those backups until they expire. Operational logs are separate from account deletion.

7. Your controls and requests

Location permission can be refused or revoked in your browser or Android settings. History is off by default. Menu → Privacy & map lets you choose local preferences, explicitly save supported settings to your account, restore account settings and clear history. Turning off history and saving that choice to your account also deletes server history. Saved places and planned drives can be deleted separately. Account lets you change your password, sign out or delete your account.

For access, correction, a copy of information, deletion questions, an objection or another applicable privacy-rights request, email dobcalldemo@gmail.com. We may need to verify your identity before providing account information. Rights and available complaint procedures depend on applicable law; this policy does not limit them.

8. Android permissions, children and security

The Android build requests foreground location permission. It does not request background location access; navigation stops when the app pauses. Speech voices depend on the device. The service is not designed for children to create accounts independently. If you believe a child supplied information without the required permission, contact us to request review and removal.

HTTPS, password hashing, access checks and restricted sessions help protect information. No service can guarantee complete security. Contact us if you suspect unauthorized account access.

9. International use and updates

When you use the service across borders, requests may be processed by hosting or external providers outside your country. Do not assume that all data remains in your country. We will update the date on this policy when practices change, provide notice of material changes where appropriate and obtain consent where required.