Legal
Cookie policy
A short policy, because we use very few cookies. Advertising measurement is off unless you accept it, and there is no retargeting.
Last updated 3 October 2026 · Exinary Technologies Private Limited
The short version
We use cookies and local storage for two things: making the site work, and understanding in aggregate which pages are useful. We do not use them to build a profile of you, to follow you across other websites, or to sell anything about you to anybody.
With your permission, and only then, we also measure how our marketing performs — for example, whether a visit from one of our ads led to an enquiry. You are asked the first time you visit, the answer is no unless you say yes, and you can change it at any time.
If you block all cookies, this site still works. You may lose the assistant remembering your conversation across a page navigation, which is the extent of the degradation.
Marketing measurement
We use optional measurement tools to learn whether our advertising leads to enquiries. The tool we currently use is OpenAI’s measurement pixel. It runs only if you choose Accept in the cookie banner. Until then, and if you choose Reject, it sends no measurement and sets no cookies. Your browser does still download the pixel script from OpenAI’s servers, as it would any file the page loads.
If you accept, the pixel sets two first-party cookies: __oppref, which holds an attribution identifier from the ad link you followed, and __obref, a randomly generated reference for your browser on this site. When you submit a contact, quote or assessment form and we have stored it, we report that a lead was created. That report contains the event type only — not your name, email address, phone number, company or message.
If you change your mind, choose Cookie settings in the footer and then Reject. Measurement stops immediately and the pixel removes both cookies.
What we actually set
| Purpose | Type | Retention |
|---|---|---|
| Assistant conversation state within a visit | Local storage, first-party | Cleared when you close the tab |
| Aggregate analytics — page views, referrer, approximate region | First-party cookie | Up to 12 months |
| Abuse prevention and rate limiting | No cookie — a truncated IP address held server-side for the rate-limit window | Minutes |
| Payment checkout session | Set by our payment provider on their own hosted checkout page | Per their policy |
| Remembering your marketing-measurement choice | Local storage, first-party | Until you change it or clear site data |
Marketing measurement — only if you accept (__oppref, __obref) | First-party cookies set by OpenAI’s pixel | 30 days and 365 days respectively; removed if you withdraw consent |
What we do not use
- Advertising pixels other than the consent-based measurement described above
- Retargeting or audience-building
- Social media tracking widgets
- Data brokers or audience-selling networks
- Session recording of form input
Third parties
Apart from OpenAI's pixel when you have accepted it, the pages that embed a third party — the booking scheduler and the payment checkout — are the only places another party can set a cookie. All three are listed on the sub-processors page, and the booking scheduler is loaded in an iframe so nothing runs before you interact with it. Questions: [email protected].
Questions?
Email [email protected] for anything about data or these policies, or [email protected] for security matters. See also our security page.