Cookies & Browser Storage

01What this policy covers

Cookies are small values stored by a website in your browser. Similar technologies include local storage, session storage, and IndexedDB. A site can use these technologies even when it does not set a traditional cookie.

Salaysay Studio uses Firebase Authentication to keep you signed in. The storage mechanism can vary by browser and provider version. Hosting and checkout providers also use technologies to secure and deliver their services.

02How we use storage

Storage supports the following parts of your experience.

• Authentication: Firebase stores sign-in state so you can access your account and make authorized requests. State may persist across browser sessions until you sign out, clear site data, or the provider invalidates it.
• Security and delivery: hosting and payment providers may use storage or connection information to protect and deliver their services. PayMongo’s hosted checkout has its own notices and controls.
• Studio settings: your script and controls stay in page memory while you work. They are not automatically saved for your next visit. Your browser may cache static assets such as recorded previews.
• Advertising placements: selected public pages show Salaysay’s own advertising-opportunity cards, linking to our partnership enquiry page. These cards do not load third-party advertising scripts, use tracking pixels, or store an advertising identifier. They are hidden from signed-in visitors.
• Optional analytics and ad networks are not enabled. Our hosting and payment providers have separate notices describing their own services.

03Storage names and duration

We use browser storage for account sign-in and service security. The storage mechanism can vary by browser. Hosted checkout and provider security pages may use additional storage described in their own notices. The information below explains the main storage used by the studio and the controls available to you.

• Cloudflare __cf_bm: a security cookie used for bot protection on our chatgpt.site website. It expires after 30 minutes of continuous inactivity. Additional security challenges may use separate cookies described in Cloudflare’s cookie notice.
• Firebase Authentication: sign-in information can be stored in IndexedDB (firebaseLocalStorageDb, store firebaseLocalStorage), localStorage, or sessionStorage. Account entries use a firebase:authUser key scoped to the app. Persistent sign-in survives browser closure until you sign out or clear site data. Session storage lasts for the relevant browser session.
• Studio workspace and playback: scripts, controls, and generated-audio previews are held in page memory during use. Downloaded MP3s remain on your device until you remove them. Cached static resources follow your browser’s cache behavior and the server’s cache instructions.
• PayMongo checkout: payment and security storage on the hosted checkout follows PayMongo’s notices. Its names and lifetimes can vary with the payment method and security checks used. Links to provider notices are available on Contact & Requests.

04Your controls

Sign out through your account to end your studio session. You can remove site data or change storage permissions in your browser settings. This may sign you out and affect access; clearing browser data does not delete server-side account or payment records.

There are no optional advertising or analytics preferences to select in the studio. If we introduce optional tracking that requires consent, we will explain its purpose and provide a choice before enabling it. You will be able to reject it or withdraw consent through the relevant controls.

Privacy and storage questions can be directed through Contact & Requests. Account deletion is handled separately from clearing cookies.