Privacy
Known Compass works without an account. Most personalisation stays in your browser, and optional product analytics remain off until you allow them.
Explore and compare without signing up. There is no public profile, and saved plans do not sync between devices. Your saved setup stays in this browser unless you choose to share a setup link; load or remove it in the setup planner.
Your checklist is saved on this device, not uploaded to an account. Clearing site storage or using the checklist reset control removes that saved progress.
Saved discovery records, vehicle favorites, activity stops and atlas locations use the same device-only approach. My Leonida reads those existing lists into one local plan; nothing is uploaded and the plan does not sync between devices.
Named Collections and your route order stay in this browser unless you choose to share selected records. Clearing a route or deleting a collection leaves the individual My Leonida saves in place. Clearing site storage removes all of these local lists.
A shareable link includes only the selected public record identifiers and their order. It excludes custom names, collection identifiers, timestamps, other saved lists and checklist progress. No hosted plan or public profile is created.
The selection is encoded in the link fragment, which browsers do not send in the page request. It is not encrypted: anyone with the full link can read or forward it, and links cannot be revoked. Treat a shared selection as public. Opening it shows a preview; saving a copy requires a separate action. Links capture a snapshot, and unavailable records are omitted from the current public index.
Choosing “Copy my setup link” includes your selected country, console, setup style, spending limit and equipment marked as already owned. Other saved plans, names and analytics identifiers are excluded. Anyone with the link can read and forward these choices; it is not encrypted and cannot be revoked.
The choices are encoded in the link fragment, which is not sent in the page request. Opening a link shows a preview. Loading it and saving a local copy are separate actions. Estimates are recalculated from the current shortlist, so prices and recommendations can change.
“Allow analytics” enables limited website counters in Supabase: visits to broad tool categories, successful saves, comparisons, completed checklist actions, saved-plan opens and shopping clicks. We record a broad arrival source such as Google or Instagram, not a full referring URL. We do not send your search text, saved items, edition choice, budget or equipment list.
A random per-tab token expires after 30 minutes of inactivity and becomes a daily keyed hash on the server. Duplicate-control receipts expire after two days; daily totals after 180 days, on the next event. Local timestamps tell us whether this browser visited or used the same tool on a different day within the last 30 days. Only the resulting yes/no signals are sent, not the timestamps. These counts cover consenting browser sessions, not identified people or cross-device activity. Privacy settings lets you stop this collection and clear its local measurement state.
The setup planner has a separate, optional “Allow setup analytics” switch. It sends limited counts of visits, saved setups and shopping-link clicks to our server and Supabase. The counts include the chosen country, console, setup style, clicked product and whether the visit came from Instagram. Your spending limit, owned equipment and saved shopping list are not sent.
A random session token, kept in session storage, is transformed into a daily keyed hash by our server to limit duplicate counts. We do not store your IP address or full referring URL in these metrics. Duplicate-control records older than two days and aggregate counts older than 180 days are removed on the next received event. Hosting providers may process network information in their ordinary access logs. You can turn this measurement off at any time in the setup planner; it starts off by default.
Vercel provides privacy-conscious, aggregate page-view analytics so we can understand which public pages are useful and how the site performs. This does not use cookies or create advertising profiles.
If you allow analytics, PostHog receives limited events such as a search being performed, a comparison being completed, or a checklist item changing. We do not send search text, saved list contents, names, email addresses, automatic click recordings, or session replays. PostHog personal profiles are disabled. You can change your choice at any time with the Privacy settings link in the footer.
When configured, Sentry receives technical error and performance information needed to diagnose broken pages. We do not intentionally send account details or the contents of your device-only plans. This monitoring is treated as essential to keep the service secure and reliable.
The site uses Vercel for hosting and aggregate page-view analytics, and Supabase for the verified public data layer. Optional product events use PostHog, and technical monitoring may use Sentry. These providers process network and device information under their own privacy terms. Retention is kept to the shortest practical period supported by each configured service.
This notice was last updated on 28 September 2026. Material changes will be reflected on this page before the related collection is activated.