1. Current approach
Navurex uses strictly necessary authentication cookies and short-lived browser storage for account and saved-content features. It also offers optional first-party analytics to understand page use, match engagement, sign-up flows and Pro interest.
Optional analytics is not activated until you choose “Allow analytics”. Navurex does not currently install Google Analytics, Meta Pixel, TikTok Pixel or advertising/profiling pixels. Analytics events are sent to Navurex's own API and stored in its Supabase database.
Analytics preference
Current choice: Not chosen yet.
2. Authentication cookies
| Name | Purpose | Typical duration | Type |
|---|---|---|---|
navurex_access_token | Keeps an authenticated session active and allows authorized account requests. | Short-lived; follows the authentication token lifetime. | Strictly necessary, HttpOnly |
navurex_refresh_token | Allows a signed-in session to be securely refreshed without requiring a login on every page. | Up to 30 days | Strictly necessary, HttpOnly |
navurex_locale | Remembers the language you selected so Navurex can open future pages in the same language. | Up to 12 months | Preference / functional |
navurex_beta_notice | Remembers that you acknowledged the current testing-stage notice, so the same notice does not interrupt every page visit. | Up to 6 months, or until the notice version changes | Functional |
In production, these cookies are configured with Secure, HttpOnly and SameSite=Lax protections and are scoped to the Navurex site.
3. Necessary browser storage
| Key | Purpose | Duration |
|---|---|---|
navurex:favorites-summary:v2 | Temporarily caches the signed-in user's saved-item summary to reduce duplicate requests. | Approximately 30 seconds within the browser session |
navurex:pending-favorite:v1 | Remembers a Save action while an unsigned user completes sign-in/sign-up, so Navurex can finish the requested save afterward. | Browser session; removed after the save completes |
navurex:analytics-consent:v1 | Remembers whether you chose optional analytics or Essential only. | Persistent until you change/delete the preference |
navurex_theme | Remembers whether you selected Day or Night appearance. | Persistent until you change/delete the preference |
4. Optional analytics storage
The following entries are created only after you allow analytics:
| Key | Purpose | Duration |
|---|---|---|
navurex:analytics-anonymous:v1 | Provides a random browser identifier so Navurex can estimate unique and returning visitors. It is not derived from your name or email. | Rotated after approximately 13 months; removed if you choose Essential only |
navurex:analytics-session:v1 | Provides a random identifier for the current browser session so Navurex can measure product funnels. | Browser session |
navurex:analytics-attribution:v1 | Temporarily remembers UTM campaign information for the current session, where present. | Browser session |
5. What optional analytics records
When allowed, Navurex may record page views, match-page opens, Save/Follow actions, account creation or login completion, Pricing visits and Pro waitlist joins/leaves. Events can include the page pathname (without query-string parameters), random browser/session identifiers, external referrer host and campaign parameters such as utm_source. Analytics V1 does not attach your account email or account identifier to these optional analytics events. Navurex does not intentionally store full IP addresses or browser user-agent strings in its analytics-events table.
6. Managing your choice
You can change the analytics choice at any time using the controls above. Choosing Essential only stops new optional analytics events and removes the analytics browser/session identifiers stored by the Navurex application. You can also clear cookies or site storage through your browser settings. Removing authentication cookies will sign you out.
7. Marketing technologies
Navurex does not currently use advertising or profiling pixels. If such technologies are introduced later, this policy and the consent controls will be updated before they are activated where consent is required.
8. Contact
Questions about cookies, browser storage or analytics can be submitted through the Contact page.