What are cookies
A cookie is a small value stored by your browser for a website. Reacast uses cookies for authentication and your chosen website language. Local storage and session storage also retain interface choices, drafts and request identifiers; these technologies are described below.
Cookies are not programs and cannot execute code. Some are deleted when you close your browser (session cookies), others stay for a defined duration (persistent cookies).
Why Reacast uses them
The current application uses storage needed for authentication, requested interface preferences and safe workflow recovery. No advertising, retargeting or audience-measurement cookie is integrated. Merely opening this page does not request optional consent.
- Keep you securely signed in to your workspace
- Complete secure sign-in and password-recovery exchanges
- Remember your interface preferences
- Recover requested drafts and avoid duplicate submissions
Categories
Strictly necessary
Authentication and sign-in security cookies are used when you access an account or start a sign-in flow. They are needed for that service and are not advertising cookies.
Analytics
No audience-measurement tracker is integrated in the current application. Operational job records and quotas are stored on the server and are distinct from audience-measurement cookies.
Preferences
The selected website language and portal theme are stored for the interface you request. Drafts and recovery identifiers support actions you start. These are necessary preferences and workflow storage, not optional tracking.
Marketing
No advertising or retargeting cookie is integrated in the current application. A future optional tracker would require prior information and consent where required before it starts.
Cookies & browser storage
| Cookie | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
| reacast_public_language | Reacast (first-party) | Chosen website language; set when you change language | 365 days | Necessary preference |
| sb-<project-ref>-auth-token (including numbered chunks) | Supabase Auth on Reacast | Stores the authentication session; refreshed during use and cleared on sign-out | Up to 400 days per cookie write; session validity is controlled separately | Strictly necessary |
| sb-<project-ref>-auth-token-…-code-verifier | Supabase Auth on Reacast | PKCE verifier and pending-flow index for sign-in or password recovery; removed when consumed | Up to 400 days if a flow is abandoned; not a 400-day sign-in authorization | Strictly necessary |
| reacast-theme (localStorage) | Reacast (first-party) | Portal theme selected by you | Until changed or browser storage is cleared | Necessary preference |
| reacast:studio-request:* / reacast:replacement:* (localStorage) | Reacast (first-party) | Recover a creative request and prevent duplicate submission | Until acknowledged or browser storage is cleared; no fixed browser expiry | Necessary workflow |
| reacast:onboarding:v2:* / reacast:duplicate:v1:* / generation and render IDs (sessionStorage) | Reacast (first-party) | Onboarding drafts, project duplication, scene generation and render recovery | Tab session, or earlier removal after completion | Necessary workflow |
No optional tracker is integrated. Cookie expiry is different from the validity of an authentication token or server session.
Manage your preferences
There are no optional cookies to accept or refuse in the current application. The panel below shows this configuration and records no consent. You can block or delete cookies and site storage in your browser; blocking authentication storage can prevent sign-in, and clearing workflow storage can remove drafts or recovery identifiers.
Cookie preferences
View necessary storage and inactive optional categories.
Change language from the website language selector and theme in the portal. Sign out to clear the active authentication session. Google sign-in redirects to Google, whose own cookies and settings apply on its domain. See also our Privacy Policy.
Other technologies
Local and session storage serve the purposes listed above. Server-side records cover security, task status, quotas and credit reconciliation; they are described in the Privacy Policy. No fingerprinting or cross-site advertising pixel is integrated in the application. External source images, thumbnails or links can contact their own host, which receives network information such as an IP address; they are distinct from a Reacast analytics tracker.
Pending legal review
Before adding an optional tracker, this notice and the actual consent controls must be updated to identify its provider, purpose and duration. Optional trackers must stay off until valid consent where required; changing this text alone does not authorize them.
Contact
Questions about cookies
Other legal documents