Cookie Policy

1. Technologies we use

• Authentication and security cookies: Auth.js session, callback, and anti-forgery values used to sign you in, maintain a session, complete an identity-provider flow, and protect requests. Names, security prefixes, and expiry can vary by environment and authentication method.
• Local storage: the browser key cookie-consent records acknowledgement of the cookie notice. Interface preferences such as theme may also be stored locally.
• Operational storage: short-lived browser state may be used to maintain navigation, uploads, selected tools, and other functions requested during a session.

2. Third-party authentication and payments

If you choose Google sign-in or open Razorpay checkout, those providers may set or read cookies, device identifiers, or similar technologies for authentication, fraud prevention, security, payment completion, and their own legally permitted purposes. Those technologies are controlled by the provider and governed by its privacy and cookie notices. We do not control their names or retention periods.

3. Advertising and analytics

We do not currently configure third-party behavioural-advertising cookies, cross-site advertising pixels, or user-level analytics cookies on the Service. If this changes, we will update this Policy and provide any choice or consent mechanism required by applicable law. Basic server logs and security telemetry are not browser cookies and may still record requests as described in the Privacy Policy.

4. Duration

Session technologies expire when the session ends or according to their configured security lifetime. Persistent authentication and local-preference values remain until their expiry, sign-out, account or application action, browser cleanup, or manual deletion. Provider-controlled technologies follow the provider's retention rules.

5. Your controls

Browser settings can block or delete cookies and site storage. Blocking essential authentication, anti-forgery, or local-storage functions may sign you out, prevent checkout or identity-provider sign-in, repeatedly display notices, or make parts of the Service unavailable. Because currently configured first-party cookies are essential, the Service does not provide a separate opt-out that preserves the same signed-in functionality.

6. Changes and contact

We may update this Policy as technologies, providers, or legal requirements change. The revised date will be shown above, and additional notice may be provided where required.

Questions about cookies may be sent to contact@deepsoch.ai.