RoleCall Cookie Policy

Effective Date: April 14, 2026

Last Updated: April 14, 2026

This policy explains how RoleCall (rolecallstudios.com), operated by RoleCall Studios LLC, uses cookies, localStorage, sessionStorage, and IndexedDB (collectively, "cookies and similar technologies") when you use our service.

---

•1. What This Policy Covers

This policy covers all forms of browser storage used by RoleCall, including:

• — Cookies — small data files stored by your browser
• — localStorage — persistent browser-side key-value storage
• — sessionStorage — temporary browser-side storage cleared when you close the tab
• — IndexedDB — structured browser-side database storage

Data stored in localStorage, sessionStorage, and IndexedDB never leaves your browser and is not transmitted to our servers unless explicitly stated otherwise.

---

•2. Cookies We Use

Name	Type	Purpose	Duration	Required?
sb-*-auth-token	Cookie	Supabase authentication session	Session / 7 days	Yes (strictly necessary)
sb-*-auth-token-code-verifier	Cookie	PKCE authentication flow verification	Session	Yes (strictly necessary)

Auth cookies are set by Supabase, our authentication provider. They are strictly necessary for login and account access. Blocking them will prevent you from using RoleCall.

---

•3. Local Storage and IndexedDB

These are browser-side storage mechanisms. Data stored here remains on your device and is not transmitted to our servers.

Storage	Purpose	Required?
Encryption key cache (IndexedDB)	Your derived encryption key from your Recovery Phrase, wrapped with a device-specific key, so you do not need to re-enter your phrase each visit	Yes (strictly necessary for encryption)
User preferences (localStorage)	Theme settings, sidebar state, editor preferences, UI state	Functional
Immersion tracker cache (localStorage)	Roleplay tracker state for faster restore between page loads	Functional
Draft content (localStorage)	Unsaved editor drafts to prevent data loss	Functional

All of these are either strictly necessary for the service to function or serve a functional purpose directly requested by the user. Under the ePrivacy Directive, strictly necessary and functional storage is exempt from consent requirements.

---

•4. Session Storage (Analytics)

Storage	Purpose	Required?
rc_session_id (sessionStorage)	Anonymous session identifier for first-party analytics	No

RoleCall uses a custom first-party analytics system. Analytics data is stored in our own database. We do not use any third-party analytics service. This system tracks:

• — Page views and feature usage
• — Search queries
• — Referrer URLs

Each session receives a random anonymous ID. We do not link this ID to your account or identity. We do not build advertising profiles. We do not share analytics data with third parties.

We honor Do Not Track (DNT) browser signals. If your browser sends a DNT signal, analytics tracking is disabled entirely.

---

•5. What We Do NOT Use

• — No Google Analytics or third-party analytics services
• — No advertising cookies or tracking pixels
• — No social media tracking cookies
• — No browser fingerprinting

---

•6. Managing Your Browser Storage

You have full control over the storage described in this policy:

• — Cookies: You can block or delete cookies through your browser settings. Blocking essential cookies will prevent login.
• — IndexedDB: Clearing IndexedDB will remove your cached encryption key. You will need to re-enter your Recovery Phrase on your next visit.
• — localStorage: Clearing localStorage will reset your UI preferences, editor drafts, and tracker cache.
• — All site data: You can clear everything at once through your browser's "Clear Site Data" option for rolecallstudios.com.

---

•7. Changes to This Policy

We will update this policy if our use of cookies or similar technologies changes. The effective date at the top of this page will be updated accordingly.

---

•8. Contact

If you have questions about this policy, contact us at boxoffice@rolecallstudios.com.