Updated October 10, 2026. StopSage offers a small business planning pilot and a commute planner.
Firebase Authentication processes sign-in details. We store account email, access and subscription status, Stripe customer identifiers, credit balances, promotional-credit source, payment receipts, and usage records in Firestore. Planning quotes and jobs store entered addresses, service durations, preferences, and execution status. Recent plans show those inputs and receipts, and can start a fresh calculation; they do not retrieve historical Google forecasts. Saved route templates contain inputs you choose to save and are private to your account. We do not store Google route forecasts, calculated legs, or optimized results as history.
Draft inputs are kept in this tab's session storage when browser settings allow it, so refreshing or completing sign-in does not discard an unfinished form. Drafts contain your entered addresses and settings, not calculated route results. Signing out or changing accounts clears the departing account's tab draft. Closing the tab normally clears its session storage.
Addresses and route planning times are sent to Google Maps Platform to resolve locations, optimize a route, and estimate driving times. Route estimates are displayed for the current planning session and are not saved as route history by this app. Stripe handles payment details directly; the app does not receive your full card number. Firebase, Google Cloud, Google Maps Platform, and Stripe process data needed to provide their respective services.
StopSage does not load analytics or advertising tags by default. If the operator later configures a Google Analytics or Google Ads measurement ID, the site will ask for a clear opt-in before loading those tags and will provide a measurement-preferences control to withdraw consent. The optional wrapper sends only aggregate events such as which workflow or page link was used; it does not send addresses, search text, email addresses, authentication identifiers, job identifiers, payment-session values, query strings, or URL fragments. GA4 Enhanced Measurement must remain disabled so automatic outbound-link collection cannot capture address-bearing Maps links. With no configured IDs, there is no analytics or advertising request.
Typed address searches are sent to Google Places for suggestions, including before sign-in. We store usage counters with pseudonymous network/session identifiers or account identifiers to limit requests and costs; we do not save autocomplete search text or suggestions. Suggestions and route results are held in the current browser session. Opening or sharing a Google Maps navigation link sends its locations to Google; anyone receiving the link can see its locations. Email opens your own composer and does not automatically send a message. Protect links because they contain addresses.
A verified account can receive one five-credit welcome grant and can redeem pilot codes shared by an operator. To prevent repeated grants after account recreation, StopSage retains a keyed hash of the verified email used for the one-time eligibility claim; the promotional record does not retain that email in plain text. Credit codes are stored as hashes, never as raw codes. For a code, we retain the grant amount, creation and expiry times, optional recipient restriction, label, redemption or revocation status, and the account and usage event needed to prevent double redemption. Code creation and redemption records are private, and no redemption email is sent automatically. Promotional and provider-attempt counters are used to control abuse and cost; paid-credit-only runs can use a separate paid path.
The early-access form saves your business name, contact email, and question privately so the operator can follow up. No payment is needed to submit a request. You can delete saved templates in the planner. The illustrative demo uses synthetic data and makes no routing requests. Avoid customer names, order contents, health information, or other sensitive details in labels and contact requests.
Account, input, usage, and billing records remain until removed by the operator; a date recorded on a quote or request is not a promise of automatic deletion. Infrastructure logs may record requests and errors. Routing errors do not intentionally log addresses or provider payloads. Self-service account deletion is not yet available. Use the operator contact or contact request form for deletion, privacy questions, or billing help. On a deletion request, eligible account records are removed subject to financial or legal retention; a keyed one-time-offer claim may remain so the same verified identity cannot receive a duplicate welcome grant. Financial records may need to be retained where required.
For support, email support@stopsage.com.
Google Maps features and content are subject to the Google Maps End User Additional Terms of Service and the Google Privacy Policy. The integration is also governed by Google Maps Platform terms. See also Stripe's privacy policy and this app's terms of use.