Privacy policy

The short version

This Privacy Policy explains how Formentia LLC (“we,” “us”) handles information when you use Astray (astray.to, app.astray.to, and related services).

There are no Astray accounts. We do not sell your location or trip history. We are not in the ad-targeting business. Privacy is baked into how the product works.

No account, nothing to sign up for

You can open the app and plan without creating a username or password. We do not maintain a user profile database of “you.”

What stays on your device

Preferences (engine mode, text size, route colors, equalizer presets, legal acceptance, navigation-handoff consent, and similar) live in your browser’s local storage.

Saved routes and favorite-trip style history live in IndexedDB on your device. On-device map tiles and places data, when you download them, live in device storage (including Origin Private File System where supported).

Clearing site data, uninstalling the PWA, or using private browsing can erase this. We cannot restore it from our side because we do not hold a cloud copy of your saved trips.

When planning talks to the server

In server mode, the app sends trip planning requests (endpoints, time budget, mode, and related parameters) to our routing API (api.astray.to) so we can return a scenic-vs-baseline comparison. Place search in server mode similarly queries our geocoder.

The service is designed to be stateless for trip content: we do not operate Astray as a trip diary or surveillance product, and we do not sell where you go. Operational infrastructure (load balancers, anti-abuse, TLS) may process request metadata the way any HTTPS service does.

We aim not to retain trip logs as a product feature. Absolute guarantees about every hop of infrastructure are hard; the product intent is: solve the request, return the answer, move on.

When planning stays in your pocket

In on-device mode, routing and geocoding can run in your browser after you download map/places data. Those planning computations do not need to leave your device for the solve itself.

Downloading tiles and places still uses our content CDN (for example tiles.astray.to / object storage). That is content delivery: fetching map bytes. Your trip history stays on the device.

Optional handoff to Google Maps (or similar)

If you choose to send a route to an external navigation app, that app receives the trip endpoints (and whatever else the deep link includes). That is your choice, remembered locally after you consent in the app. Google’s (or another provider’s) privacy policy applies to what they do with that information.

Analytics (off unless you turn it on)

Astray does not enable product analytics by default. If you explicitly opt in (for example via the engine panel or an analytics query flag), the app may send anonymous performance samples (timings / coarse diagnostics) to help us keep the service healthy. That path is opt-in and can be turned off again.

The marketing site does not hitch a ride with third-party ad trackers for “who you are.”

Tiles, CDN, and the boring network stuff

Static assets, the PWA, and map tiles are served via normal web infrastructure (including Cloudflare and object storage). Those systems see IP addresses and standard request logs the way CDNs do. We use that for delivery, security, and abuse prevention. We do not use it to build a dossier of your road trips.

Kids

Astray is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you think that happened, email us and we will help sort it out.

Policy changes

We may update this Privacy Policy. The version (2026-07-21) and effective date will change when we do. Material changes that affect how the app treats your data will be reflected in the product and, where we bump the Terms version, may require re-acceptance in the app.

Talk to a human

Operator: Formentia LLC, a Wyoming LLC. Email: hello@astray.to.

If you have a privacy question, ask. We are small enough that the inbox still reaches a person.