Cookie / Tracking Policy

This policy covers cookies, localStorage, sessionStorage, Supabase authentication storage, anonymous/session identifiers, referral or campaign attribution, analytics events, quality-assurance identifiers, and diagnostic records used by Noteese during beta.

Noteese uses Supabase Auth and browser/session storage to keep users signed in, process account recovery, support OAuth login, protect account sessions, and route users to the correct dashboard or admin area.

Without this required storage, signup, sign-in, password reset, Google login, and secure account workflows may not work correctly.

Noteese may use localStorage or similar browser storage for product preferences such as light/dark mode, attribution session data, beta QA mode, and user-interface settings.

Noteese tracks product events such as landing views, signup started/completed, sign-in completed, OAuth started, password reset events, achievement started, proof uploaded, achievement submitted, card ready, card viewed, card shared, report submitted, report action taken, legal consent completed, profile photo uploaded/removed, and QA validation events.

These events help Noteese understand whether the product is working, where users drop off, and whether beta safety and review workflows are operating properly.

When available, Noteese may record source, referral code, school/campus code, UTM source, UTM medium, UTM campaign, UTM content, UTM term, referrer, anonymous ID, and session ID.

This helps Noteese understand which channels lead to real achievement submissions, proof uploads, Card Ready events, and beta adoption.

Admins may use analytics QA tools that tag a controlled test run with a QA run ID. These tags are used to confirm that analytics events and dashboard formulas work correctly after code changes.

Noteese should not sell student achievement data to advertisers. If Noteese later shows sponsored opportunities, they should be clearly labeled and handled in a privacy-first, guardian-aware manner.

You can control some browser storage by using browser privacy settings, clearing site data, or using private browsing. Some product features may stop working if required authentication/session storage is blocked.

For broader privacy choices, review the Privacy Policy and account settings.

This policy may be updated as Noteese adds production analytics, organization accounts, AI features, paid plans, opportunity matching, or mobile apps.