Cookie Policy

Last updated: 2026-10-25

This policy explains the browser storage and measurement technologies used on hellonod.app. The Nod macOS and iOS apps do not use cookies.

What the site uses

The site sets no cookies and asks for no analytics consent. It counts visits with Vercel Web Analytics, which sets no cookies, stores nothing in your browser, and does not recognise you across days or across sites. It does not load on invite, sign-in, OAuth, checkout, email-preference, waitlist-confirmation, or free-tool pages.

The site no longer loads Google Tag Manager, Google Analytics, or Google Ads measurement.

Storage left by the earlier analytics banner

Until 2026-10-25 the site offered optional analytics. If you allowed it, your browser may still hold the items below. Your next visit removes them, and asks Supabase to delete the visit records kept under the random visitor ID.

Name Type What it was for
nod_analytics_consent_v1 Local storage Your answer to the earlier analytics banner.
nod_visitor_id_v1 Local storage A random first-party ID that joined consented website events.
nod_session_id_v1 Session storage A random ID that counted a browser session.
nod_campaign_v1 Local storage The most recent campaign details, for attribution.
nod_hero_variant_v1 Local storage Which homepage headline you were shown in a page test.
nod_pending_analytics_withdrawal_v1 Local storage Set during that removal: it holds the old visitor ID only until Supabase confirms the deletion, then goes.
_ga, _ga_<container>, _gcl_au, _gcl_aw and other _gcl_ / _gac_ cookies Cookies Set by Google Analytics and Google Ads after consent.

Data already sent to Google before 2026-10-25 is kept under Google's own retention settings.

Other storage

Supabase Auth may use browser storage on connector authorization pages to keep the security state required for sign-in and OAuth grants.

You can clear cookies and local storage at any time in your browser settings.

Questions or privacy requests: dmytro@hellonod.app.