Visualized Routes
Privacy policy
How Visualized Routes handles account, route, image, and usage information.
Draft for operator and legal review. This policy is not ready to publish until the items listed in docs/privacy-terms-content.md are completed. In particular, the service operator's legal identity and privacy contact, retention periods, and applicable governing jurisdictions have not been confirmed.
Who operates Visualized Routes
Visualized Routes is operated by [operator's full legal name] (“we”, “us”, or “our”). Our business address is [business address]. For privacy questions or requests, contact [monitored privacy email or working contact channel]. Replace these fields before publication.
Information we handle
- Account and sign-in information: When you sign in with Google, we receive your Google account's stable account identifier, verified email address, and basic profile information such as your name. We use these details to create and secure your account. We request the
openid,email, andprofileidentity scopes only; we do not request Gmail access. Google's temporary sign-in credentials are used to verify your identity and are not saved as your app session or database credentials. - Profile and workspace information: The first and second names, country, and city you enter in your profile, plus information you add to projects and your workspace.
- Routes and saved content: Route and animation titles, descriptions, stop names, stop order, coordinates, travel modes, map settings, source links, and publication settings that you create or import.
- Images and other media: Images uploaded to My Images or attached to a route. The service converts uploaded images to WebP, resizes them, and removes source metadata such as EXIF data before storage. Depending on deployment configuration, files are stored in an S3-compatible object store (which may be Cloudflare R2) or local development storage. Images added to a public App Gallery or to a published route may be visible to others.
- AI and place-search inputs: If you use AI itinerary or description features, relevant route text, stop names and coordinates, and any page content you ask the service to process may be sent to the configured AI provider. Stop-description research may also send a stop name, category, and approximate coordinates to Exa. Place lookup and map features may send search terms or coordinates to Google Maps Platform. Route geometry may send stop coordinates to the configured OSRM-compatible routing service. These services may be self-hosted or changed by the operator; identify the production providers and review their own privacy terms before launch.
- Visualization usage events: When enabled, an embedded visualization can send limited usage events such as a view, playback start, progress, completion, pauses, and seeks. Events include generated identifiers for a visit and playback, visualization/project IDs, event times, and bounded engagement measurements. The collector records the publisher hostname. It does not intentionally collect a viewer's name, email, full page URL, or cookie. If the deployment explicitly enables trusted country headers, a two-letter country value supplied by its trusted proxy may also be recorded. Analytics can be disabled by the publisher or is skipped when the browser sends Do Not Track or Global Privacy Control signals.
- Technical and security information: The service and its hosting, reverse proxy, and infrastructure providers may process request metadata such as IP address, timestamps, and error details to deliver, secure, and troubleshoot the service. The application excludes the analytics event collector from its IP-bearing access log, but infrastructure outside the application may still log requests.
- Browser storage: Sign-in uses a signed, HttpOnly session cookie. The route-import forms can save a Google Maps or itinerary URL in local browser storage so it remains available when switching forms or reloading. Visualization analytics itself does not use an analytics cookie or local storage.
How we use information
We use information to provide sign-in, save and display routes and media, publish visualizations you choose to share, run place lookup and route geometry, provide requested AI features, measure aggregate visualization engagement, protect the service, and respond to support or legal requests. We do not use Google account credentials to access Gmail.
When information is shared
We share information with service providers only as needed to operate features you use, including hosting and database providers, object storage, Google sign-in and Maps Platform, the configured AI provider, Exa search, and the configured routing service. Those providers may process information under their own terms. The operator must identify production vendors and configure appropriate contractual and international-transfer safeguards before launch.
When you publish a route, embed a visualization, or add media to a shared gallery, the selected content can be accessed by the people and sites to which it is made available. Do not publish information you intend to keep private. We may also disclose information when required by law or when reasonably necessary to protect users, the service, or others.
The application's analytics implementation does not include an advertising profile or third-party advertising tracker.
Cookies and similar storage
The sign-in session cookie is used to maintain your authenticated session and protect account actions. The application configures it as HttpOnly and SameSite=Lax, and marks it Secure in production. The route-import URL memory is stored in your browser's local storage and can be removed by clearing the relevant form value or browser storage. The embedded-player analytics code does not set cookies.
How long information is kept
We keep account, workspace, route, and image information while it remains in the service or is needed to provide the feature you requested. You can delete saved animations and personal images through available product controls; removing an image from a stop may only detach it and leave it in My Images. Deleting an animation does not delete reusable personal or App Gallery images. The application currently has no published account-closure flow or documented fixed retention period for analytics, backups, logs, or deleted records. The operator must set and publish those retention and backup-deletion periods before this policy is made public.
Your choices and privacy rights
You can edit route information and personal image names, delete personal images, and delete saved animations using the controls provided in the service. Some controls remove an item from a route without deleting its reusable library copy.
Depending on where you live and which privacy laws apply, you may have rights to request access to, correction of, or deletion of personal information, to object to or restrict certain processing, or to complain to a regulator. We will need a working privacy contact and a process to verify and answer requests before publishing this policy. In Kenya, the Office of the Data Protection Commissioner describes data-subject rights including being informed, access, objection, correction, and deletion of false or misleading data; other rights and requirements may apply under the law relevant to you. Kenya ODPC: Rights of a Data Subject. For people covered by EU data-protection law, the rights available depend on the circumstances; see the European Commission's information on data-protection rights.
Children
Before publication, the operator must set the minimum age for account holders and a process for handling reports about a child's information. This service does not currently publish an age rule.
Security and international processing
We use technical and organizational safeguards appropriate to operating an online route service. No internet service can promise absolute security. The service and its providers may process information in countries different from yours. The operator must document the production hosting locations and safeguards for any transfers required by applicable law.
Changes to this policy
We may revise this policy as the service changes. The effective date and a way to receive notice of material changes must be added before publication. If a change materially affects how information is used, we will provide notice where required by law.
Effective date: [add date before publication].