How CrowdRoute handles information

1. Information we handle

Account identity

When you use Sign in with ChatGPT, CrowdRoute receives the account identifier, email address and display name made available for the signed-in session. We use that information to authenticate you, associate your subscription and usage allowance, and display account status.

Subscription and route usage

For PayPal subscriptions, we store the PayPal subscription and plan identifiers, payer identifier when supplied, subscription status, billing-period dates and CrowdRoute plan. PayPal processes payment credentials; CrowdRoute does not receive or store your card or bank-account details. We also record route-calculation quantities, the CrowdRoute Project ID supplied with the calculation, the usage month and timestamps so we can enforce and audit plan allowances.

Project content and browser settings

CrowdRoute project models—including nodes, routes, gates, evidence and operational records—are stored locally in your browser through browser storage and IndexedDB. The device-local project library and autosave are not uploaded to CrowdRoute by the current product. Project JSON and reports leave the browser only when you choose to export, save or share them outside CrowdRoute. If you enter your own Google Maps browser key, it is stored in that browser and sent to Google when Maps services are requested.

Service and security data

Our hosting, authentication and security providers may process ordinary web-request information such as IP address, browser and device information, request times, requested pages, cookies and security signals to deliver and protect the service.

2. Google Maps Platform

CrowdRoute uses Google Maps Platform for maps, place and mobility discovery, geocoding, route matrices, walking-route geometry and static-map exports. When you use those features, your browser sends relevant searches, coordinates, route endpoints, waypoints and the applicable browser API key to Google. Google handles that information under the Google Privacy Policy and Google Maps/Google Earth Additional Terms. Google Maps content is subject to Google’s use, attribution and caching restrictions.

3. How we use information

• Authenticate users and protect workspace access.
• Activate, administer and verify subscriptions.
• Authorize and audit route-calculation allowances.
• Operate, secure, troubleshoot and improve CrowdRoute.
• Respond to support, legal and safety-related requests.
• Comply with law and enforce our terms.

We do not sell CrowdRoute project content or payment information.

4. When information is shared

Information is shared only as needed with service providers that help us provide CrowdRoute, including hosting and security infrastructure, Sign in with ChatGPT, Google Maps Platform and PayPal; with professional advisers; when required by law or necessary to protect rights, safety and the service; or as part of a business reorganization subject to appropriate safeguards. Each third-party service handles information under its own terms and privacy practices.

5. Retention and your choices

User-entered browser-local project data is isolated by the signed-in CrowdRoute account within that browser profile and remains on the device until you delete projects, clear CrowdRoute site data or the browser removes it. This isolation reduces accidental crossover on a shared browser profile, but it is not a substitute for separate operating-system accounts and appropriate device access controls. Google Maps content within a project is governed separately by Google’s caching rules. Google Places result names and addresses are shown in the live result set but are not written into newly created project records; operator-controlled labels are saved instead. Newly calculated Routes geometry and newly retrieved Places coordinates are timestamped and stop qualifying as controlled CrowdRoute content after 30 days. CrowdRoute then removes the licensed coordinates and route geometry, retains the stable Place ID where Google permits, and requires a refresh and route recalculation before controlled use. Operator-authored IDs and fields are preserved. Export important projects before clearing browser storage or changing devices, and do not retain exported Google content longer than its permitted period.

Account, billing, webhook and usage records are retained for as long as needed to provide the service, administer subscriptions, maintain audit and financial records, resolve disputes and meet legal obligations. You can export your editable project JSON, remove device-local projects, clear browser site data, manage or cancel PayPal automatic payments from your PayPal account, and contact us about applicable privacy rights. Some records may need to be retained where law, fraud prevention, billing reconciliation or legitimate audit needs require it.

6. Security and professional use

Google route distances, durations and matrix metrics remain in the open session rather than saved project snapshots. Reloaded or imported projects require a walking-distance refresh before modelling or closest-gate verification. Saved Place IDs let you refresh expired locations without recreating your operator records. Project JSON and route-choice CSV exports omit raw Google distance and duration values; any exported permitted Google coordinates retain the same retrieval-based expiry and must be deleted within that period.

We use technical and organizational safeguards appropriate to the service, but no browser storage, transmission or online system is completely secure. Protect access to your device, CrowdRoute account, exported project files and any browser API key. CrowdRoute is intended for professional and organizational use and is not directed to children.

7. Changes and contact

We may update this policy as CrowdRoute changes. The date above identifies the current version. Material changes will be presented through the service or another appropriate channel.

Questions or privacy requests: info@crowdsafe.group.