Routing terms and privacy

Routing terms

When enabled, an authorized Owner or crew leader can request and review a suggested route for assigned visits. Suggestions, travel times and arrival estimates are advisory. They do not reschedule customer appointments, guarantee traffic conditions, or replace safe driving decisions. An authorized person must review an order before accepting it.

Directions to an individual stop opens Google Maps. Appointment windows, service durations and breaks recorded in RLS are not transferred as scheduling constraints to that navigation session. Do not operate route controls while driving.

Google map and routing features are also subject to the Google Maps/Google Earth Additional Terms of Service. Google Maps attribution remains visible with Google content. Independently entered business information is separate from Google map content.

Routing privacy

When an authorized user requests Google route planning, RLS sends Google the selected start/end and visit coordinates, opaque visit identifiers, service durations, permitted arrival windows, shift and break constraints, stop-order rules and aggregate operating-cost inputs. This routing request does not include customer names, email addresses, phone numbers, photos, property-access notes or individual employee pay rates.

Routing requests pass through the authenticated RLS backend, hosted on Supabase and Google Cloud Run. Current account, organization and crew permissions determine who may calculate, accept or read a route. Aggregate planning rates and monetary comparisons are restricted to the Owner in RLS.

Google Maps SDK and Google Maps navigation may process information under Google’s Privacy Policy. Opening external directions shares the selected destination with Google Maps. RLS does not enable background employee location tracking or request the device’s current location for this routing feature.

Google route previews are temporary and are removed when dismissed or expired. RLS does not persist route polylines, Google travel distances, estimated arrival times or raw Google routing responses. Independently entered job and scheduling information belongs to the business’s operational records. When an authorized person accepts an order, RLS retains the sequence of its own visit identifiers and an acceptance record as the business’s dispatch instruction. Google travel estimates and map geometry are not included in that retained record.

Operational usage records contain identifiers, request fingerprints, timestamps, counts and completion status. Routine routing logs exclude customer addresses, precise coordinate histories, credentials and raw provider responses.

For questions about business-held routing information or requests to correct it, contact the business that collected your request or provided your RLS account. This notice covers routing; it does not replace Google’s policies for its services.