Start free

Cookie Policy

Counsel-review draft. Effective date pending.

Foyercal uses a small number of cookies that are either strictly necessary to run the service or save a user preference. We do not run advertising trackers, third-party analytics that build cross-site profiles, or any cookie that would require an affirmative-consent banner under EU law. This page lists what we set, why, and for how long.

What is a cookie?

A cookie is a small text file that a website asks your browser to store. The browser sends it back on subsequent requests to the same site, which lets the site remember things between page loads (whether you are signed in, which organization you are looking at, whether you prefer light or dark mode).

Strictly necessary cookies

These cookies are required for the service to function. They do not require consent under EU law because the service cannot be delivered without them.

  • NextAuth session cookies(set by the authentication library) — Keep you signed in. Names start with next-auth. or __Secure-next-auth.. They are HTTP-only, Secure, SameSite=Lax, and tied to your authoritative server session record. TTL: thirty days, rolling.
  • foyer_active_org— Remembers which organization you have selected when you belong to more than one. Required so server-rendered pages know which tenant to load. HTTP-only, Secure (in production), SameSite=Lax. TTL: one year.
  • NextAuth CSRF token— Mints and validates a per-request CSRF token for sign-in and account actions. Set automatically by the auth library. HTTP-only, Secure (in production), SameSite=Lax. TTL: session.

Functional cookies

These cookies remember preferences you have set. They are not required for the service to run; if you delete them, the next page load will use the default.

  • foyer-theme— Stores your chosen theme intent (light, dark, or system). Read by the client-side theme provider so the right palette is applied before paint. Not HTTP-only. TTL: one year.
  • foyer-theme-mode— The resolved theme (light or dark) used by server-rendered pages so they produce the correct markup on first paint. Set in tandem with foyer-theme. Not HTTP-only. TTL: one year.

What we do not use

Foyercal does not use any of the following:

  • Advertising or retargeting cookies (no Meta Pixel, no Google Ads, no LinkedIn Insight Tag).
  • Third-party analytics that build cross-site profiles (no Google Analytics).
  • Session-replay or heatmap tools that record user interactions.
  • Affiliate or partner-attribution cookies.

How to control cookies

You can clear or block cookies in your browser settings. If you block the cookies listed under “Strictly necessary,” you will not be able to sign in or use the service. If you block the functional cookies, the app will still work; it will simply forget your theme preference between sessions.

Major browsers also offer “Do Not Track” and Global Privacy Control signals. We honor these signals to the extent they apply to the cookies we set, which (because we do not run trackers) is largely a no-op for us.

Changes to this policy

If we add a new cookie that is not strictly necessary, we will update this page and ask for consent in the product before the cookie is set.

Contact

Questions about cookies can go to support@foyercal.com.

Effective date: pending counsel review. Draft prepared by the Foyercal team for legal review.