Privacy Policy for Navigation Constellation

This document describes how the Navigation Constellation extension handles information. It is intentionally brief and written in plain language so that you can understand exactly what happens when the extension is enabled.

Data we collect

Only a minimal set of metadata about your browsing is captured:

• Redacted page address – the scheme, hostname and path of the page you visit. By default, query parameters (which can contain search terms) and fragments are removed. Any segment of the path that may reveal sensitive context (for example login, account, profile, cart, payment or similar identifiers) is replaced by ** before it is stored.
• Timestamp – the moment (in milliseconds since the Unix epoch) when the navigation occurred.
• Event type – the type of navigation event. In this demo implementation only navigation committed events are recorded.
• Anonymous identifier – a random UUID combined with a random salt, hashed via SHA‑256. This value is created only after you opt‑in and allows the demo server to group multiple events from the same installation without learning anything about your identity.

We never record page content, cookies, IP addresses, or form data. Search queries are only collected if you explicitly enable a separate, privacy-warned setting. Navigations to internal pages (such as chrome://), local files, private network addresses and domains you choose to exclude are ignored.

How we use the data

Your redacted navigation metadata is stored in your browser’s extension storage. It is used to build a constellation graph that helps you visualise how your browsing session evolves over time. You can view, export or delete this graph at any moment via the extension’s options page.

Sending data to the demo server is optional. If you enable this feature, the extension will batch a few events at a time and transmit only the hashed identifier, redacted URL, timestamp and event type. This allows you (and the reviewers) to verify that the remote ingestion endpoint functions correctly. The server does not store IP addresses or raw URLs.

Storage and retention

Graph data is stored locally using a fixed‑size buffer of 500 entries. When the buffer is full the oldest entries are discarded to make room for new ones. You may delete all stored data at any time from the options page. On the server side, data is kept only for the duration of the demonstration and is not shared with third parties.

Your choices

The extension is disabled by default. When you install it for the first time a consent page is displayed explaining what will be collected. You may choose to:

• Enable local collection and visualisation.
• Additionally allow sending the minimal metadata to the demo server.
• Decline collection entirely. You can still enable it later from the options page.
• Revoke your consent and delete all stored data at any time.