Privacy Policy
Overview
This Privacy Policy explains how Traffic Sonar ("we," "us," or "our") collects, uses, discloses, and safeguards your information when you use our mobile application and related services (the "Service"). We are committed to protecting the privacy of all users in the United States.
Last updated: November 18, 2026
Information We Collect
Account Information
When you create an account, we collect the name and email address you provide. If you choose Google or Apple sign-in, Base44 handles authentication and receives the account information authorized by that provider, such as your name, email address, and provider account identifier. Apple may supply a private relay email address. We use Base44 account identifiers and session credentials to sign you in and connect your saved destinations, alert preferences, and reports to your account.
Location Data
To show nearby traffic and trip alerts, we collect your device's precise geolocation (latitude and longitude) when you grant permission. We use it to find nearby incidents, calculate a fresh trip from your current location, and check traffic ahead. Saved destinations retain the name and address you type, your schedules and alert settings, and an optional starting address for scheduled alerts or briefings. These may include your home or work address. If you explicitly save your current position as a starting place, we retain those device coordinates for your schedules. Live search matches are a temporary preview and do not replace the address saved from your input. We do not sell your location data.
On iPhone, Start Drive enables background location updates for that drive so we can check traffic ahead while you use another app or lock your phone. iOS displays a location indicator. Tracking stops at arrival, End Drive, permission removal, or session expiry. We send your latest position to our server for route alerts; we do not keep a drive-location history. That drive's stored coordinates are cleared when the server receives End Drive or processes an expired drive. Background tracking uses some battery and does not start automatically.
Monitor With Me is a separate, user-started iPhone session that follows your alert area in the background without a destination. Community-only following has no session timer; live traffic monitoring lasts up to 30 minutes. It stops when you end it, remove location permission, or the session expires. Only your latest device position is updated; no movement history is saved. Your last position remains your saved alert center for separately enabled Community Alerts. Force-closing the app stops native tracking.
User-Generated Content
When you report a traffic incident, we store the report type, severity, road name, description, and the coordinates you provide. Incident reports may be visible to other users on the shared map. Your account is linked to reports you create.
Feedback & Usage
If you submit feedback, we store your rating, message, and any contact email you provide. We also collect usage and diagnostic data to improve the Service. Base44 records page views and navigation in production. Some usage data may be linked to your account or device identifiers.
Push Notifications and CarPlay
When you allow iPhone notifications, we store the device push token, platform, delivery environment, registration time, enabled status, and associated account identifier to send alerts to your device. The token is also stored locally on your device. We use these records to deliver notifications and reduce duplicate or misdirected alerts.
To reduce duplicate alerts, we also store a hashed delivery identifier, delivery status, timestamps, and an expiration time. The identifier is generated from the delivery destination and notification event identifier; the receipt does not contain the device push token, notification text, or traffic measurements. These identifiers are used for delivery bookkeeping, not as a record of your movements.
For troubleshooting, we store notification failure records that may include a community report identifier, recipient account identifier, processing stage, error reason, and timestamp. These records are restricted to administrative access in the app. Base44 also processes server diagnostic logs, which may include account, route, or device-registration identifiers and delivery errors.
We send the push token and notification payload to Apple Push Notification service (APNs). Payloads include the alert title and text and an in-app destination link; traffic alerts or briefings may reveal road names, destination labels, or other trip-related information. Apple processes delivery information under its own privacy terms. Base44 hosts our push registration records and provides push delivery for supported non-native clients.
On supported iPhones, we also request permission to show notifications in CarPlay. CarPlay is optional. Allow Notifications and, where available, Show in CarPlay are controlled in iPhone Settings under Notifications for Traffic Sonar. Accepting our Terms does not grant device notification permission. Notification content may be visible on your lock screen or connected vehicle display and to passengers or others nearby, depending on your settings. CarPlay support does not itself start location tracking or add collection of vehicle data.
Disabling notifications changes delivery permission; it does not automatically delete your stored push registration or stop a separately started Drive or Monitor session. Signing out attempts to disable this device's app-managed push registration, and account deletion removes its app-managed registration records. You can contact us to request deletion. Apple and other providers manage separately retained delivery data under their own policies.
Optional Voice Alerts and Siri Announcements
If you enable Speak traffic alerts in the app, we save that preference locally on your device and pass eligible notification text to Apple's on-device speech system for playback. This feature does not require microphone access and does not record your voice. Traffic Sonar does not send this text to AWS Polly, ElevenLabs, or another external text-to-speech provider.
Apple's Announce Notifications is a separate, optional system feature controlled in iPhone Settings. If enabled for Traffic Sonar, Siri may read notification content through the speaker, supported headphones, or CarPlay, including while your phone is locked where supported. Apple manages Siri processing under its own privacy terms. Traffic Sonar does not receive recordings or transcripts of Siri announcements.
Spoken notifications may reveal road names, destination labels, or other trip information to passengers or others nearby. You can disable in-app speech in Traffic Sonar and Siri announcements separately in iPhone Settings. Changing either speech setting does not stop a separately started Drive or Monitor session or delete notification records.
Request Counts and Service Limits
We store account-linked request counters and usage records to enforce service limits and monitor reliability. Records include the account identifier, request category, counts, error counts, and timing information. These usage records do not contain address queries, coordinates, route paths, traffic measurements, or provider response bodies. Usage logs are separate from the location and saved-destination records described above. Prior-day allowance counters are removed when their storage bucket is next used; aggregated usage logs have no automatic age-based deletion period and may remain after account deletion. You may contact us to request deletion of records associated with your account.
How We Use Your Information
- Display real-time traffic conditions and incidents near you.
- Calculate fresh trips to saved destinations, send scheduled briefings, and alert you to nearby hazards.
- Allow you to report and view crowd-sourced traffic incidents.
- Send notifications about incidents within your alert radius.
- Maintain and secure your account.
- Improve and analyze the performance of the Service.
How We Share Your Information
We do not sell your personal information. We share data only as follows:
- Service providers: Base44 provides account authentication, hosting, data storage, and usage analytics. Google and Apple process sign-in requests when you choose those methods. TomTom receives address queries and the location or trip endpoints needed to provide address matches, routes, estimated arrival times, and traffic. These services process data under their applicable privacy policies.
- Government road data: We download traffic and road information from state transportation agencies to our own servers. We do not send your location or other personal information to those agencies.
- Optional navigation: If you choose to open Apple Maps, Google Maps, or Waze, we pass the destination address or location needed to open your trip. The navigation app calculates its own route and handles information under its own privacy policy. Opening an external navigation app is optional.
- Advertising: The iOS app requests non-personalized banner ads through Google AdMob. Our public web guide may display Google AdSense ads. Google may process device identifiers, approximate location derived from IP addresses, ad interactions, usage, and diagnostic data to serve, measure, and protect ads. The iOS app provides Ad privacy choices in this policy when required. Where displayed on the public website, Google’s U.S. state privacy message provides eligible visitors with a “Do Not Sell or Share My Personal Information” link to submit an opt-out where applicable. Non-personalized ads may still use identifiers for fraud prevention and measurement.
- Other users: Traffic incident reports you submit are visible on the shared map to other users.
- Legal compliance: We may disclose information when required by law or to protect rights, safety, or property.
Data Retention
Saved destination inputs, explicitly saved device places, schedules, and alert preferences remain until you edit or delete them or delete your account. One-time trip sessions are temporary: End Drive, arrival, or server cleanup after expiry removes the session. Native tracking stops on the phone before a successful server cleanup is necessarily received. Fresh TomTom address matches, calculated route paths, geocoded endpoints, distance, and ETA are used for the current request or session and are not saved in the destination record. Slowdown checks for a monitored area are made live for that request and are not saved; only the time of the last check and last slowdown alert is kept. Community reports can remain stored after they stop appearing as active incidents, until removed by their owner, moderation, or account deletion. Marking a report cleared does not necessarily delete its record. You can initiate account deletion from the Alerts settings screen or contact us using the email below. Account deletion removes app-managed account records; third-party providers manage any separately retained data under their own policies.
Notification Record Retention
Successful delivery receipts expire for duplicate suppression 24 hours after the delivery is recorded. Pending receipts normally expire after two minutes; failed receipts may expire sooner. Expired receipts are eligible for deletion by our scheduled cleanup, so expiration does not mean the stored record has already been deleted. Receipts are not directly indexed by your account identifier and may remain until that cleanup after account deletion.
Notification failure records do not currently have an automatic age-based deletion period. They remain until administratively removed; account deletion removes failure records whose recipient account identifier matches your account. You may contact us to request deletion of diagnostic records associated with you. Base44 and Apple manage separately retained platform and delivery logs under their own retention policies.
Your Privacy Rights (U.S. Residents)
Depending on your state of residence, you may have the following rights under laws such as the California Consumer Privacy Act (CCPA), the California Privacy Rights Act (CPRA), and other state privacy laws:
- Know: Request what personal information we have collected about you.
- Delete: Request deletion of your personal information.
- Opt out of sale/sharing: We do not sell your personal information. Where displayed on our public website, Google’s AdSense U.S. state privacy message lets eligible visitors use its “Do Not Sell or Share My Personal Information” link to submit an opt-out where applicable. If you cannot access the message, contact us using the information below.
- Limit use of sensitive data: You may limit the use of sensitive personal information for certain purposes.
- Non-discrimination: We will not discriminate against you for exercising your privacy rights.
- Authorized agents: You may designate an authorized agent to make requests on your behalf.
To exercise any of these rights, contact us using the information below. We will verify your identity before processing your request and respond within the timeframe required by applicable law.
Children's Privacy
The Service is not directed to children under 13 (or the applicable age in your state), and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, please contact us and we will delete it.
Data Security
We use reasonable administrative, technical, and physical safeguards to protect your information. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Changes to This Policy
We may update this Privacy Policy from time to time. We will post the updated version in the app and revise the "Last updated" date above. Material changes will be communicated within the app.
Open the app Privacy Policy to manage available ad privacy choices.
Contact Us
For support, to report objectionable content or abusive behavior, or to ask questions about this Privacy Policy and exercise your privacy rights, email admin@trafficsonar.net. You do not need an account or to log in to contact us.
© 2026 Traffic Sonar. All rights reserved.