๐†‘music-forte
Legal

Cookies and local storage

The short answer: we use a session cookie for sign-in and localStorage for your interface preferences. No advertising or analytics cookies.

Last updated ยท May 2026

Cookies we use

forte_session
HTTP-only, Secure, SameSite=Lax. Set when you sign in; carries the session token that identifies you on subsequent requests. Required โ€” without it the platform can't keep you signed in. Lifetime: 30 days from last activity, then auto-expired. You can revoke it from /account โ†’ Devices.

localStorage / IndexedDB

These are not cookies but they sit in the same family. We use them for things that need to survive a refresh but don't need to be sent on every request:

  • Layout preferences โ€” chat-shell rail width, canvas size, panel mode for FORTE Notation. Survives a refresh; you can clear it from your browser's site data.
  • Notation drafts (offline) โ€” when collaboration is unavailable, drafts cache locally so you can keep editing.
  • Comment threads (offline) โ€” comments mirror to localStorage when not connected to a collab room.
  • On-device polyphonic engine โ€” the polyphonic detector caches its compiled binary in your browser's HTTP cache after the first practice session, so subsequent runs don't re-download it.

What we don't use

  • No third-party advertising cookies.
  • No third-party analytics cookies (no Google Analytics, no Mixpanel, no Segment).
  • No tracking pixels in transactional emails.
  • No fingerprinting.

Controlling cookies and storage

You can clear cookies and local storage at any time through your browser's site-data controls. If you clear the session cookie, you'll be signed out โ€” sign in again to restore. Clearing localStorage will reset your interface preferences and may delete offline draft caches; cloud-saved drafts and recordings are unaffected.

We don't show a cookie consent banner because we don't use any cookies that require consent under UDPPA, GDPR, or equivalent frameworks. The session cookie is "strictly necessary" โ€” it carries authentication. If we ever introduce a cookie outside that category, we'll add a consent flow before doing so.

Questions

For more on data handling, see /privacy. Email support@music-forte.app with anything else.