Cookies

Draft status

This cookies page is a draft policy pending legal review. It describes the product as it exists today and should not be read as a final compliance statement.

Cookie categories on Troubadour

Troubadour currently treats browser storage in four practical categories: strictly necessary, analytics, marketing, and embedded media or third-party content.

Strictly necessary cookies or storage stay enabled because they support sign-in, Supabase session continuity, role-aware routing, security, and stable workspace behavior across artist, act, agent, venue, and admin areas.

Optional categories should remain opt-in. If analytics, marketing, or third-party embedded tracking are introduced or expanded later, this page will need formal legal review before it becomes final.

• Strictly necessary: authentication, session continuity, security, and core navigation state.
• Analytics: optional measurement or product analytics, if later enabled.
• Marketing: optional advertising or retargeting tools, if later enabled.
• Embedded media / third-party content: optional YouTube, Vimeo, Google Maps, Spotify, SoundCloud, Apple Podcasts, or similar embeds that may set third-party cookies.

What Troubadour appears to use today

Troubadour currently appears to rely on necessary cookies for Supabase authentication and session handling, plus local browser storage for a mix of drafts, settings, dev-mode helpers, and other interface state.

At the time of this draft, the app does not appear to enable a live analytics script by default, and it does not appear to enable a live marketing tracker by default. That should be re-checked before making any final legal statement.

Some public and workspace surfaces do use optional third-party embeds such as music/video players or maps. Those should stay blocked until a visitor opts in to embedded media.

What the platform is not promising yet

Troubadour is not yet making a final legal statement about cookie durations, retention periods, jurisdiction-specific consent rules, or every third-party service that may appear later. Those details still need formal legal review.

Examples of why necessary storage matters here

• Keeping a signed-in user connected to the correct dashboard or role context.
• Remembering the difference between direct and protected relationship paths.
• Supporting message, thread, and workflow state in a stable way during navigation.
• Helping moderation/admin review screens load safely and consistently for approved reviewers.

Questions

Questions about this draft cookie policy can be sent to [CONTACT EMAIL]. Company identity and address details remain placeholders: [LEGAL ENTITY NAME], [COMPANY ADDRESS].

Cookie Settings

You can review or change optional categories here at any time. Strictly necessary cookies remain enabled so Troubadour can keep sign-in and routing stable.