Cookie Policy

Frontage tries to be unusually quiet about browser storage. We use the minimum needed to keep agents signed in and to remember a few UI preferences. We do not run third-party advertising cookies and we do not embed tracking pixels.

What we set

Strictly necessary

• Clerk session — keeps the agent signed in. Cleared on sign-out.
• Supabase session — paired with the Clerk session for database row-level security.

Functional (no tracking)

• Theme preference — light or dark, stored in localStorage. No login required.
• Onboarding completion flag — a single localStorage key so we don't re-show the first-run onboarding.
• Studio queue cache — the agent's in-progress draft queue, stored in localStorage as a fast cache while we wait for the Supabase round trip. Source of truth lives server-side.

Analytics

None at the moment. If we add analytics, we will update this policy and add a disclosure at first login.

Advertising

None. Frontage does not place advertising cookies and does not participate in cross-context behavioral advertising. See Do Not Sell My Info.

Your choices

• You can clear cookies and localStorage in your browser at any time. Doing so will sign you out.
• The agent landing pages at /site/<slug> are explicitly cookie-free — they're what your potential clients see, and they should be lightweight and privacy-clean.

Contact

privacy@frontage.app