Cookies & your browser
Last updated: 16 September 2026
This policy explains how ODIN VISION, a brand of Kitsune AI Pvt Ltd, uses cookies and browser storage on odinvision.net.
Your choice comes first.
Essential storage supports your privacy choices, enquiry draft and invoice request. Our optional Meta integration measures advertising performance and conversions. It runs only when configured and after you allow Advertising. Microsoft Clarity helps us understand website use through heatmaps and masked session recordings, and runs only after you allow Analytics. Rejecting optional tracking does not prevent you from enquiring or requesting an invoice.
Choose Accept all, Reject optional, or Preferences. Browsing, scrolling or leaving the banner unanswered does not grant consent. A previous choice made before a provider was disclosed does not enable the new provider. Analytics and Advertising can be chosen separately.
What is stored on your device?
| Storage | Purpose | Duration |
|---|---|---|
ov.cookie-consent.v1 | Your consent choice and policy version. | 180 days, or until withdrawn or the disclosed scope changes. |
| Enquiry draft and request identity | Preserves draft answers and avoids duplicate invoice or enquiry requests. | Browser tab session. |
ov.meta.visitor | Random identifier linking advertising consent to a request, so future server events can be stopped on withdrawal. | Until withdrawal or consent expiry is processed on a subsequent visit. |
ov.meta.attribution and ov.meta.events | Consent-controlled campaign attribution and prevention of duplicate browser conversion events. | Browser tab session; attribution is removed on withdrawal. |
Meta _fbp and _fbc, when set | Browser and ad-click identifiers used for advertising measurement. | Typically up to 90 days; browser restrictions may shorten this. Our withdrawal handler removes accessible first-party copies. |
ov.meta.withdrawals | Remembers an undelivered opt-out request so it can be retried when the connection returns. | Until our server acknowledges the withdrawal. |
Microsoft Clarity analytics.
With Analytics consent, Microsoft Clarity collects website interactions such as clicks, scrolling, page views and device/browser information to create heatmaps and session recordings. We use this to understand where visitors have difficulty and improve our pages and checkout journeys. We send only generic service, package and journey events, not customer IDs, email addresses or billing details as event values.
Checkout forms, enquiry content and invoice references are masked before recording. The private invoice desk, private briefs and payment routes are excluded. Clarity is not loaded on our development or preview sites. We keep Clarity advertising storage denied, independently of the separate Meta advertising choice.
Clarity may set _clck (up to one year) to recognise the same browser and _clsk (up to one day) to connect page views into a session. _cltk keeps a tab identifier in session storage until the tab closes or Analytics is withdrawn. Browser restrictions may shorten these periods. Microsoft endpoints may also receive or set their own cookies; see Microsoft’s Clarity cookie documentation and Privacy Statement for its processing and retention practices.
Withdrawing Analytics stops Clarity recording and removes accessible first-party Clarity cookies. A final in-flight request may finish; withdrawal cannot undo information already sent. No Clarity script loads on subsequent pages unless Analytics is allowed again.
Meta advertising measurement.
With advertising consent, the Meta Pixel can report page and service views, the start of invoice checkout and successful submissions. Meta's Conversions API can report a saved lead, a lead marked qualified by our team, and a verified payment. An invoice request is not reported as a purchase.
Campaign parameters, landing-page paths and available Meta click/browser identifiers may be saved with your enquiry or invoice record in Supabase. For server conversion matching, we may send Meta a SHA-256 hash of your email and a record identifier, together with the relevant service, event time and paid amount/currency. Hashing supports matching; it does not make this data anonymous. We do not send your billing address, tax ID, project brief or uploaded business documents in these event payloads.
The private invoice desk does not load the advertising integration. Ordinary links to social profiles are not embedded tracking widgets. Meta's own processing is described in its Privacy Policy and Cookies Policy.
Changing or withdrawing consent.
Use Cookie settings in the footer. Withdrawal stops future browser events, removes local attribution and requests suppression of queued and future server advertising events associated with this browser's identifier. If offline, the withdrawal request is retried on a later connected visit. It cannot undo events already transmitted. A request already in transit may finish.
We respect Global Privacy Control by keeping optional tracking off. Choices are specific to this browser and device. If you clear all browser storage before withdrawing, we may no longer be able to link that browser to an earlier record; contact us for help with an earlier submission. Re-enabling advertising creates a new consent identifier rather than reactivating previously revoked records.
Website delivery and submitted requests.
Cloudflare delivers and protects the website. Supabase stores submitted records and serves the client film; Resend sends operational emails. These services continue to support your requested service when advertising is rejected. Invoice and enquiry records remain available for handling your request independently of optional advertising consent.
See our privacy notice for broader information, or contact us through the enquiry page.