Cookie Policy

Cookies are small text values that a website or service stores in a browser and receives again with later requests. They can keep a user signed in, remember a preference or record a consent decision.

Kaption also uses browser local storage. Local-storage values stay on the device and are not automatically sent with every web request. This policy refers to cookies, local storage and comparable browser-side technologies together as "browser storage" where the distinction is not important.

The actual effect depends on the key. Clearing site data may sign a user out, reset choices, remove local support history or interrupt a temporary project handoff.

Strictly necessary

Required to remember consent, authenticate a requested session, or provide a browser-side operation the user specifically requested. These remain available without optional consent.

Functional/preferences

Remembers choices such as interface and content language, theme, pricing display and local support state. These are off until functional consent is given.

Analytics

Would measure how the site or product is used so performance and experience can be understood. No analytics provider or analytics storage key is currently configured.

Marketing

Would be used for advertising, cross-site tracking, audience creation or campaign attribution. Kaption does not currently use advertising or marketing cookies.

The following inventory is based on Kaption's inspected frontend and backend code. It includes every identified Kaption cookie and local-storage key, plus provider-controlled cookies associated with Google sign-in.

Strictly necessary entries

4 identified entries.

Functional/preferences entries

11 identified entries.

Analytics entries

None identified.

Marketing entries

None identified.

The inspected application did not identify a CSRF cookie, `sessionStorage` key, analytics cookie, advertising cookie, or payment-related cookie. Operational server logs are addressed in the Privacy Policy and are not browser-storage keys.

On the first eligible visit, Kaption shows a consent banner before using optional functional or analytics storage. Essential storage may remain active because it supports consent records, authentication and requested application functions.

A saved choice records policy version 2026-07-24, the optional-category selections, the decision time and an expiry time. It is stored for 180 days. A valid, unexpired choice prevents the banner from appearing on every visit.

Kaption asks again after the choice expires or when the configured policy version changes following a material change. The consent record is strictly necessary because without it Kaption could not reliably remember a rejection or other choice.

Select Open cookie preferences in the Legal Centre to reopen the controls. Optional categories can then be enabled, disabled or rejected together. Withdrawing functional consent removes the functional cookies and local-storage keys listed in the inventory and prevents future functional writes unless consent is given again.

Withdrawing consent does not affect earlier processing that was lawful. It may reset the theme, language, pricing display and locally stored support state. Strictly necessary authentication or project handoff storage may continue until its stated expiry or the relevant requested operation ends.

Browsers generally allow users to inspect, delete or block cookies and site data through privacy or site settings. Private-browsing modes may remove some storage when their windows close. A user can also clear Kaption's local storage through browser developer or site data controls.

Browser controls apply independently of Kaption's preference panel. Blocking all cookies can prevent sign-in, consent memory, language continuity or other requested features from working. Settings differ by browser and device, so consult the browser provider's current help documentation.

Kaption loads Google Identity Services on the login page to offer Google sign-in. When a user uses that option, Google may set or read provider-controlled authentication cookies under Google's own settings and privacy terms. Kaption does not assign exact Google cookie names or lifetimes because those are controlled by Google and can vary by session.

The inspected code did not identify third-party analytics, advertising or payment scripts. If Kaption introduces one, it must be added to this inventory and, where optional, blocked until the relevant consent is present.

Information about Kaption's hosting, authentication, storage, email and AI providers is available in the Privacy Policy.

No analytics provider is currently confirmed in Kaption's legal configuration, and no analytics or marketing script was found in the inspected application. The consent system therefore does not load any such provider before or after a choice.

Analytics consent is recorded only as a user choice for the current policy version. It does not authorise an undisclosed provider. Before any analytics integration is enabled, Kaption must identify the provider and storage keys, update this policy and inventory, increase the policy version, and technically gate the integration behind analytics consent.

Marketing remains off and is not offered as an active choice because Kaption does not use advertising cookies.

Kaption may update this policy when browser storage, service providers, purposes, retention periods or consent controls change. The effective and last-updated dates at the top identify this version.

A material change to optional storage or its purpose requires the configured policy version to be increased. Existing consent then becomes invalid and Kaption asks for a new choice.

Questions about a cookie, local-storage key or consent choice can be sent to privacy@kaption.in. General technical support is available at support@kaption.in.

Include the browser, device, relevant storage key and feature involved. Do not send passwords, authentication tokens or full payment credentials.