Cookie Policy

1. What cookies and browser storage are

Cookies are small text records a website asks your browser to store and return with later requests. Some cookies are needed for secure sessions; others support measurement or advertising.

Local storage stores preferences and selected app data in your browser. IndexedDB is a browser database that can hold larger local data such as editor drafts. These are similar technologies, but they are not cookies and are not automatically sent with every web request.

2. How Poster Kaaran uses them

3. Technologies and services involved

Poster Kaaran session cookie

The web editor uses an HTTP-only session cookie named pk_session to authenticate signed-in requests. HTTP-only means page scripts cannot directly read its contents. Removing or blocking it signs you out or prevents signed-in features from working.

Google and Firebase authentication

Google and Firebase may use cookies or browser storage during Google sign-in, fraud prevention and account-session management. Their behavior is controlled by Google and may vary by browser, account and region.

Google Analytics 4

Google Analytics helps measure traffic, interactions and technical performance. It may use cookies or identifiers to distinguish visits and generate aggregated reports.

Microsoft Clarity

Microsoft Clarity helps diagnose usability and performance. Sensitive editor areas are configured for masking. Clarity may use cookies or identifiers to connect activity within a visit or across visits.

Google AdSense

Google and its advertising partners may use cookies or similar technologies to serve and measure ads, limit repeated ads and, where permitted, personalize advertising based on visits to this and other sites. Manage Google advertising preferences through My Ad Center.

Poster Kaaran browser storage

The editor uses local storage for preferences such as theme, typing mode, dismissed prompts and selected locally uploaded assets. It uses IndexedDB for local drafts that may be too large for ordinary local storage. This information remains on that browser/device unless the product or user removes it.

4. How long information remains

• Session storage: usually ends when the browser session or authenticated session ends.
• Persistent storage: remains until its configured expiry, product cleanup, provider cleanup or manual deletion.
• Local storage and IndexedDB: generally remain until you clear site data, delete relevant data, or the browser removes it.

Exact durations may differ by provider, browser, consent choice and service configuration. Providers may change cookie names or durations over time.

5. Your controls

You can view, block or delete cookies and site data through browser settings. For Chrome, see Google's cookie controls guide. Other browsers provide similar privacy or site-data settings.

Blocking all storage may stop Google sign-in, saved preferences, local drafts or other editor functions from working. Clearing data may permanently remove drafts stored only on that device.

Where a consent message is shown, use its options to manage consent. This policy explains storage; viewing this page does not itself grant, refuse or withdraw consent.

6. Related privacy information

See our Privacy Policy for collected information, uses, sharing, retention and account-deletion choices.

7. Changes to this policy

We may update this policy when our technologies, providers or legal requirements change. The latest version and update date will remain here.