Privacy and contact

Last updated: October 2, 2026

Ultimate Roads is provided by Two Towers Incorporated. This notice covers the owner-only trial of the iPhone app and its routing service. It explains what information the service receives, what stays on your phone, and the limits of our current hosting information.

For privacy questions or requests, email privacy@solarperspectives.com with “Ultimate Roads” in the subject. You can also reach Matt Schneider at matt.schneider@solarperspectives.com.

Before you request a drive

When routing is available and you choose Find my drive, your starting coordinates, destination coordinates and intermediate route points go from your phone to our routing service, then to HERE, which calculates routes. Requests also include departure time and routing preferences. Route results return through our service to your phone. Recovery and return-route requests use the same path.

Our routing application processes these coordinates and route results without storing their contents in its application database or deliberately recording them in application caches, logs or analytics. It does retain the access and usage records described below. Hosting infrastructure and HERE have separate processing and retention practices.

You do not need an account, invitation or provider key. Necessary routing access and usage processing is separate from optional sensor recording; declining recording does not prevent navigation or optional post-drive feedback.

Information used to run the service

The app creates a random installation identifier and security keys. Our service uses the identifier, public verification keys, verification status and expiring access-token records to recognize that installation, secure access and enforce routing limits. Apple App Attest helps verify the app where available. Private installation keys stay on your phone; the service stores hashes of access tokens rather than the raw tokens.

We keep request identifiers, request type, time, outcome, call counts, capacity reservations, cost estimates and performance information to provide routing, manage availability, reconcile spending and diagnose failures. These records are linked to an installation, even though you have not supplied a name or created an account. They do not contain route coordinates, place names, returned route contents, drive recordings or feedback.

How long application records are kept

These are the application's cleanup periods. A scheduled maintenance process removes eligible records; service or maintenance failures can delay cleanup. These periods do not promise immediate deletion of every hosting backup or records held independently by HERE or Apple.

Hosting and service providers

The routing service uses Replit for application hosting, a PostgreSQL database, App Storage for maintenance records and scheduled maintenance. The database holds the access and usage records described above. App Storage holds maintenance deadlines, random marker identifiers and service-status timestamps. These markers do not contain installation identifiers, coordinates, routes or recordings. Our routing API does not offer a public download route for these objects. Due markers are removed when processed; status markers and markers from retired service versions can remain until they are replaced or cleaned up.

We selected North America in the project's publishing settings. The settings inspected for this trial do not identify the precise underlying country or cloud region. That selection does not establish where every hosting, security or support operation occurs. Replit uses infrastructure and service providers under its own privacy policy.

We have turned off Replit's optional project analytics for the routing API. Hosting operational and security records are separate. Replit also processes network and operational information to provide and secure hosting. This can include IP addresses, request timing, status and infrastructure logs. Our application operators may inspect operational records to maintain the service and investigate problems. Replit's hosting documentation states that deployment logs are retained for 30 days. That period does not establish the retention of every security, support, analytics or diagnostic record held by the host. We have not independently verified all host-owned logging and retention practices for this trial.

Database backups and recovery copies, and recoverable copies of storage objects, can outlast deletion from the active service. We have not yet verified a complete retention schedule for those hosting copies, so we do not promise a seven-day or 90-day maximum for them. Their availability and expiry depend on the configured recovery options and Replit's practices. Restoring our application records must reapply expiry and access-revocation rules before normal service resumes.

HERE receives routing inputs to calculate routes. Apple provides maps, destination search and app verification. Their processing is distinct from our application's storage rules. Our seven-day and 90-day periods do not describe HERE's or Apple's retention. See HERE privacy information, Apple privacy information and Replit privacy information.

What stays on your phone

The app keeps local route-linked drive history and routing diagnostics, which can contain locations, selected routes, destination details and guidance information. After a guided drive, you can choose Save feedback or Skip feedback. Feedback you save is linked to that drive, independently of whether sensor recording was enabled. Local speech processing and device diagnostics are separate from our routing-service records; the service's seven-day expiry does not delete them.

Optional sensor recording covers detected guided and unguided drives. It can include precise locations, motion observations and route context. It is off until you enable Automatic collection in Drive recording and grant the required permissions. Recordings are stored on your phone without automatic upload to the routing service.

The recording area has a 1 GB content limit, shared by recordings, recording diagnostics, trial logs and recovery files. Collection stops when that limit is reached or a storage error occurs; the app does not automatically delete older recordings to make room or restart collection after space is freed. There is no age-based automatic deletion of these recordings. Exporting can require additional temporary space and does not delete originals.

Use Delete recording in Drive recording to remove a completed recording. Turn Automatic collection off before deleting an active recording. Turning collection off stops new sensor collection but does not erase earlier data. Recording diagnostics and trial logs have a separate deletion control. These recording-storage rules do not set the retention of ordinary route history or feedback.

If you export and share history, recordings or diagnostics, recipients receive those copies. Deleting the original in the app does not delete copies you shared elsewhere.

Your choices and requests

You can manage Ultimate Roads location and motion permissions in iPhone Settings and turn Automatic collection off in Drive recording. Limiting location access may prevent location-dependent features from working. Ending guidance stops that drive's routing activity; optional sensor recording has its own control.

Contact us to ask about information we hold, request access or correction, or request deletion. Because service records use installation identifiers rather than a named account, we may need help identifying relevant records and verifying your request. We will explain any limits, including backups and unresolved financial totals. Please do not email access tokens, private keys or full driving exports unless needed for a request and specifically arranged with us.

This notice covers the Ultimate Roads app and routing service. We will update it when the app's data handling changes.