Routora, Inc. ("Routora", "we", "us") makes route planning and field execution software for businesses. This policy explains what we collect when you use the Routora mobile app, the Routora web app at routora.com, and our website, and what we do with it.
Routora is a business tool. It is for users 18 and older. We do not sell personal information and we do not show advertising inside the app.
Questions: legal@routora.com.
1. The short version
| What | Why | Where it goes |
|---|---|---|
| Your name, email, and phone number | To create and secure your account | Our servers, Google Firebase Authentication |
| Addresses and coordinates you add as stops | To plan, optimize, and run your routes | Our servers, Google Maps Platform for geocoding and optimization |
| Contact numbers and notes you add as stops | To organize and carry out your visits | Our servers |
| Photos and notes you capture at a stop | To document the visit | Our servers |
| Your device location, in the foreground only, when you ask for it | To set a route start or confirm you have arrived | The arrival check stays on your device. A route start is converted to an address first. |
| Subscription status | To unlock the plan you paid for | Apple, Google, Stripe, RevenueCat |
| Crash reports | To fix bugs | Sentry |
We do not collect your device location in the background. Foreground location features handle your location as described in section 4. Photos you upload may contain GPS coordinates, which are stored with the photo. We never sell your data. We use your routes, photos, and customer addresses to provide the service as described in this policy.
2. Information you give us
Account. When you sign up we collect your name, your email address, or your mobile phone number, depending on how you sign in. Sign in options are Google, Apple, email and password, and a one time code sent by SMS to your US mobile number. Passwords are handled by Google Firebase Authentication and are never stored on our servers. If you sign in with Google or Apple, we receive the name and email those services share with us.
Profile photo. Optional. Stored with any location data your camera embedded in the file.
Routes and stops. Every address, contact phone number, note, schedule, time window, custom field, and outcome you enter or import. Addresses can be typed, picked on a map, read from a shipping label with your camera, spoken, or imported from a CSV file on the web app. These entries usually describe other people, such as your customers or the properties you inspect. Section 5 covers your responsibilities for that data.
Visit evidence. Photos, captions, drawn annotations, and notes you attach to a stop. Uploaded photos retain metadata present in the file, which may include GPS coordinates, capture time, and device orientation. This information provides context for your records; it does not independently prove where or when a photo was taken, that a visit occurred, or that an inspection was completed correctly. If you do not want location in new photos, turn off location access for the camera before taking them. Check existing photos and remove unwanted location metadata before uploading them.
Support. Anything you send us when you contact support.
3. Information collected automatically
Device and session. A device identifier your operating system assigns to the app, the device model name, your app version, and your platform. We use these to enforce one active mobile session per account and to show you which device is signed in. If you allow notifications, we store the push token your device issues. We do not currently send push notifications.
Network. Your IP address is used at sign up and during phone verification to stop abuse. Routora's sign up and verification abuse records store a one way hash of that address. This does not mean that all network processing is anonymous: our hosting, authentication, mapping, and website analytics providers may receive and process your IP address when your device connects to their services.
Usage counters. How many stops you route, routes you create, and optimizations you run each period. These enforce your plan limits and are shown to you on the subscription screen.
Crash and error reports. We use Sentry to monitor errors in the mobile app. Reports may include error details, the screen involved, and internal record identifiers. We apply filtering designed to remove email addresses, phone numbers, street addresses, tokens, and coordinates. Identifiers that remain can link a report to your account, so these reports are not anonymous. Reports are kept for 30 days.
Mobile analytics. Analytics collection through Google Analytics for Firebase is disabled in the current Routora 2.0 mobile apps distributed through the Apple App Store and Google Play. These apps do not transmit product usage events to Google Analytics for Firebase, including after a fresh installation or an upgrade from the original Routora app. This does not disable the account, subscription, usage counter, and diagnostic processing described elsewhere in this policy. Website and web app analytics are described separately in section 8.
4. Location
Routora is a route planning tool, so location is central. Here is exactly what happens.
| Situation | What we do with the location |
|---|---|
| You set your route start to "current location" | Your device converts its GPS fix to a street address on the device. Only the address is sent to our servers. |
| You tap "Mark arrived" at a stop | Your device checks whether you are within about 250 feet of the stop. The result is yes or no. The GPS coordinates stay on your device and are discarded. |
| You upload a photo at a stop or as your profile photo | If the file contains GPS coordinates or other metadata, we store that information with the photo. |
| You pick a point on the map | The coordinates become the stop location. |
| You open navigation | We hand the destination address or coordinates to Google Maps, Waze, or Apple Maps. Those apps have their own privacy policies. |
Location access is foreground only and optional. The app works with typed addresses if you decline. We have no background location code in the app and no geofencing that runs when the app is closed.
5. Information about people who are not Routora users
Most of the addresses, phone numbers, and names in your routes belong to your customers, tenants, property owners, or other people who have no relationship with Routora. For that data:
- You are responsible for having a lawful basis to collect it and to give it to a service provider like us.
- We process it only to deliver the service to you. We do not contact those people. We do not combine it with data from other customers. We do not use it to build profiles or train models.
- We send addresses and coordinates to Google Maps Platform for address lookup, maps, and route optimization. Addresses can themselves identify a person or property. Google may also receive device, network, and usage information when your device connects directly to its services, as described in section 7. Google's processing is governed by the applicable Google Maps terms and Google Privacy Policy.
- When you delete a route or your account, the associated data is deleted according to the deletion process and retention periods in sections 10 and 11.
- If someone contacts us about data you entered about them, we will refer them to you and may ask you to resolve the request.
6. How we use information
We use your information to:
- Create your account, sign you in, and keep one active mobile session per account
- Geocode addresses, optimize routes, calculate ETAs, and draw routes on a map
- Store and display your visit evidence
- Manage your subscription and enforce plan limits
- Fix bugs, keep the service running, and prevent abuse
- Measure website traffic as described in sections 8 and 9
- Respond to you when you contact us
- Send you service emails, such as a password reset or a change to these terms
- Send you product updates by email, which you can opt out of at any time
We do not use your data to target advertising. We do not sell it. We do not share it with data brokers.
7. Who we share information with
We share data only with the companies that help us run the service, in the ways listed here, under contracts that limit what they may do with it.
| Provider | What they receive | Why |
|---|---|---|
| Google Cloud | Everything we store. Our application servers, databases, and file storage run in Google Cloud in the United States (Dallas region). | Hosting, databases, file storage, logging |
| Google Firebase Authentication | Name, email, phone number, password, and sign in tokens, processed in the United States | Sign in and account security |
| Google Identity Platform | Your phone number | Sending your SMS sign in code and Google's spam and abuse prevention across its services |
| Google reCAPTCHA Enterprise | Device and browser signals collected by Google's SDK | Blocking automated sign ups |
| Google Maps Platform (Geocoding API, Places API, Routes API, Route Optimization API, Time Zone API, Maps SDK) | Addresses and coordinates from your routes, autocomplete text, and device, network, and usage information processed by the relevant Google service, including your IP address when the app calls Google directly | Address lookup, geocoding, optimization, ETAs, map display |
| Apple App Store and Google Play | Your purchase through their billing systems | In app subscriptions |
| RevenueCat | An app user identifier linked to your Routora account, and purchase events from Apple and Google | Subscription management for the mobile app |
| Stripe | Your email address, and the card details you enter on Stripe's hosted checkout page. We never see your card number. | Web subscriptions |
| Sentry | Filtered error reports from the mobile app, including internal record identifiers. Reports are stored in the United States. | Error monitoring and troubleshooting |
| Heroku | Traffic to routora.com and the web app, served from Heroku's United States region | Web hosting |
| Google Analytics (GA4) | Marketing website activity, page addresses, cookie identifiers, and browser and connection information, as described in section 8 | Measuring website traffic |
| Amplitude | Account identifiers and usage information from the legacy web planner only, as described in section 9 | Understanding use of the legacy web planner |
| Expo | App update checks from your device | App delivery |
| Apple and Google speech services | Audio when you use voice input, processed by your operating system | Speech to text |
We may also share information when the law requires it, to protect our rights or the safety of users, or as part of a merger or sale of the business. If Routora is acquired, your data transfers with the business under this policy.
8. Website analytics and cookies
We use Google Analytics 4 (GA4) on our marketing website to measure traffic. GA4 does not load on signed in Routora 2.0 web app pages or on our dedicated NYC agency subdomains. GA4 uses cookies and receives information such as your IP address, browser and device information, cookie identifiers, page addresses, and interactions. This is separate from the disabled Firebase Analytics collection in the mobile apps.
We no longer use Microsoft Clarity session recording or the Meta Pixel on our website or the Routora 2.0 web app. Removing these integrations does not automatically erase information previously collected through them. Previously collected information may remain with those providers until deleted or until the applicable retention period expires. Contact legal@routora.com about access or deletion requests.
9. The legacy Routora platform
Routora 2.0 replaces the original Routora app and web planner. During the transition:
- Shared route links created in the original app are still served by our legacy system at api.routora.com. Anyone with a link can view the stops on that route, as before.
- Subscriptions purchased on the original platform are honored and attributed to your new account when you sign in.
- Your original account data stays on the legacy platform under the policy it was collected under. When we retire the legacy platform we will announce the date at least 30 days in advance, and remaining legacy data will be deleted 90 days after that date.
- Nothing is copied from the legacy platform to Routora 2.0 until you sign in to Routora 2.0 and accept the current terms.
Legacy analytics. While the original web planner remains available, it uses Amplitude to process account and usage information. This includes the account identifier, name, and email address, and events that may include route coordinates, shared route links containing addresses, subscription identifiers, and cancellation feedback. This information can be linked to your account and is not anonymous. Legacy shared route page addresses can also contain stop addresses and coordinates that are received by the website's GA4 integration.
The legacy Amplitude integration is not used in the Routora 2.0 mobile apps distributed through the Apple App Store and Google Play, or in the Routora 2.0 web app. GA4 use on the marketing website is described separately in section 8. Updating to Routora 2.0 does not itself delete information previously collected by legacy analytics providers.
Previous versions of this policy are available at routora.com/legal/archive.
10. How long we keep information
Routora 2.0 content after a subscription or trial ends. Continued storage of your routes, stops, inspection records, photos, notes, imported files and parsed import contents, and saved or recent addresses is part of your subscription or trial. When access to paid features ends, a 30 calendar day retention window begins. Cancelling renewal does not start this window while you still have paid access. If a billing grace period continues your access to paid features, the window begins when that access ends.
During this window, you have read only access to your remaining content and can download reports available in the Service or contact us about an export. We display the deletion deadline and provide advance notice through the Service or your account contact details. If you restore paid access before the deadline, the scheduled deletion is cancelled. Otherwise, we permanently delete this content from active systems by the end of the 30 day window, except for specific information we are legally required to retain. Resubscribing after deletion does not restore the deleted content. Requests to delete content or your account earlier are handled under section 11.
This content deletion does not itself close your sign in account or erase payment records. Basic account, security, and billing information follows the separate periods below. The rule applies to Routora 2.0 content; section 9 describes the separate legacy platform. For accounts whose paid access has already ended when this rule first takes effect, we provide at least 30 days' notice before deleting content under the new rule.
| Data | Kept until |
|---|---|
| Account, profile, settings | You delete your account |
| Routes, stops, outcomes, notes | You delete the route or your account, or the 30 day retention window above ends, whichever occurs first |
| Visit photos and evidence | You delete the photo, the route, or your account, or the 30 day retention window above ends, whichever occurs first. Content purged at the retention deadline is removed from active file storage as well as the application database. |
| CSV files you import and parsed import contents | Pending imports expire 30 days after upload. Imported files and their parsed contents are otherwise deleted with your account or when the 30 day retention window above ends, whichever occurs first. |
| Recent and saved addresses | You delete them or your account, or the 30 day retention window above ends, whichever occurs first. Recent addresses are capped at the 50 most recent. |
| Subscription records held by Routora | Your account is deleted, except for limited records that must be retained by law |
| Stripe customer profile for Routora 2.0 | We request deletion as part of account deletion and follow up on failed requests until completed. Separate retention of historical payment records is explained in section 11. |
| RevenueCat customer profile | We request deletion as part of account deletion and follow up on failed requests until completed, as explained in section 11. No separate request is required. |
| Sign up and verification abuse records | 90 days, stored as hashes only |
| Server logs | 30 days. Security audit logs that record administrative actions on our infrastructure are kept 400 days and contain no customer content. |
| Crash reports | 30 days |
| Routora database backups | Automated backups, point in time recovery logs, and manual backups are retained for up to 30 days. Copies of deleted data may remain in these backups for up to 30 days after deletion. |
| Account deletion record | 7 days after deletion completes, so we can confirm it finished |
Backups after content deletion. Routora's backup copies may remain for up to 30 additional days after content is deleted from active systems. This backup period is separate from the 30 day retention window for active content. These backup copies are not available for customer retrieval or restoration by resubscribing. The limited legal and payment record exceptions in section 11 apply separately.
11. Deleting your account and your data
You can delete your account in the app under Profile, or on the web under Settings. We begin processing your request when it is submitted. We use automated retries and follow up on failed steps until deletion is completed, subject to applicable legal requirements. Subject to the backup periods and the provider records explained below, account deletion removes the following information from Routora's active systems:
- Your account and sign in credentials
- Every route, stop, outcome, and note
- Every photo and piece of evidence
- Imported files and their contents
- Saved and recent addresses
- Device and session records
- Subscription records associated with your Routora account
Backups. Copies of deleted data may remain in Routora's automated backups, point in time recovery logs, and manual backups for up to 30 days after deletion. Nothing is restored from a backup except to recover from a system failure. This 30 day period applies to Routora's backups. Our service providers may have separate retention periods under their applicable agreements and legal obligations.
Stripe customer profile. When you delete your Routora 2.0 account, we request deletion of the Stripe customer profile associated with your Routora 2.0 web subscription, if one exists. We follow up on failed requests until profile deletion is completed. Deleting that profile removes its stored card details and prevents it from being used for new charges or subscriptions. Stripe may retain historical payment records as explained below. Deleting a customer profile does not erase the history of transactions that already occurred.
RevenueCat customer profile. RevenueCat profiles contain account identifiers, purchase history, and subscription status. When you delete your Routora 2.0 account, we request deletion of the associated RevenueCat customer profile, if one exists. We track the request and follow up on failed steps until profile deletion is completed, subject to applicable legal retention requirements. You do not need to submit a separate request. Deleting a RevenueCat profile does not cancel an App Store or Google Play subscription. The separate retention of payment records is explained below.
Retained payment records. Payment processors and app stores, including Stripe, Apple, and Google, may independently retain certain transaction, billing, tax, refund, dispute, and fraud prevention records even after a customer profile is deleted. Their retention depends on applicable law, payment network requirements, and their privacy policies; it is not governed by Routora's 30 day backup period. Routora may also retain limited records where required by law. These payment records are separate from your routes, photos, and inspection notes.
Subscriptions. Your Routora 2.0 web subscription is cancelled as part of account deletion. If a technical problem delays cancellation, we continue following up until cancellation is confirmed. Deleting your Routora account does not cancel a subscription bought through the App Store or Google Play. Cancel those in your Apple or Google account settings to stop future renewals.
Data on your device. Signing out or deleting your account removes your routes, photo drafts, and cached data from that device.
Export. You can download a PDF report of any completed route from the app. For a copy of everything else we hold about you, email legal@routora.com and we will provide it within 30 days.
Subscription status and privacy requests. An active subscription is not required to submit an access, export, or deletion request. We handle requests under applicable law, including any obligation to preserve information needed to complete a pending request. A privacy request does not otherwise renew paid access or create an indefinite storage entitlement.
12. Your choices and rights
Email. Unsubscribe from product updates with the link in any email. Service emails about your account continue.
Location, camera, microphone, notifications. Control these in your device settings. The app explains what it needs before asking.
Access, correction, deletion, portability. You can view and edit your profile in the app, delete routes and photos in the app, and delete your account in the app. For anything else, email legal@routora.com. We will verify the request from the email or phone number on your account and respond within 30 days.
State privacy laws. If you live in a state with a consumer privacy law, you have the right to know what we collect, to delete it, to correct it, to obtain a copy, and to opt out of sale, sharing, or targeted advertising. We do not sell personal information, we do not share it for advertising, and we do not use it for targeted advertising, so there is nothing to opt out of. We will not treat you differently for exercising any right. You may use an authorized agent; we will ask the agent for proof of your permission. If we deny a request, you may appeal by replying to our response.
13. Security
Data is encrypted in transit. Databases and file storage are encrypted at rest by Google Cloud. Photos are reachable only through short lived signed links that expire in 15 minutes. Access to production systems is limited to named individuals. Passwords are never stored on our servers. We review access and dependencies regularly.
No system is perfectly secure. If we learn of a breach affecting your data, we will tell you without undue delay.
14. Where data is stored
Our database and photo storage are in the Google Cloud Dallas region. Database backups are stored in Google Cloud's United States multi region. Firebase Authentication, our website and web app on Heroku, RevenueCat, and Sentry all process data in the United States. Our other providers listed in section 7 may process data in other regions under their own agreements with us.
15. Age
Routora is for adults using it for work. You must be 18 or older. We do not knowingly collect information from anyone under 18. If you believe we have, email legal@routora.com and we will delete it.
16. Changes to this policy
When we change this policy in a way that matters, the app will ask you to review and accept the new version the next time you sign in. Minor edits take effect when posted with a new effective date. Prior versions stay available at routora.com/legal/archive.
17. Contact
Routora, Inc. legal@routora.com