Cookie Policy
What cookies and similar technologies CADialogue uses, which categories are actually active today, and how to change your choices. Last updated: 21 September 2026 What a cookie is A cookie…
What cookies and similar technologies CADialogue uses, which categories are actually active today, and how to change your choices.
Last updated: 21 September 2026
What a cookie is
A cookie is a small text file a website asks your browser to store. Related technologies do a similar job by other means — local storage keeps data in the browser, a web beacon or tracking pixel is a tiny invisible image whose loading can be recorded, and a device identifier can be read by software on your phone. This policy covers all of them, and uses “cookie” loosely to mean any of them.
The honest summary
This is a small, independent publication. As this policy is written, CADialogue sets no cookies at all for a reader who simply arrives and reads an article — we checked. The only cookies that exist are the ones listed under “Strictly necessary” below, and each of them is created by a specific action you take.
We would rather say that plainly than publish a long table of trackers we do not run.
Categories
1. Strictly necessary — in use
These make the site work. They cannot be switched off through a consent tool because without them the thing you asked for does not happen.
| Cookie | Set by | Purpose | Lifetime |
|---|---|---|---|
cad_seen |
CADialogue (first party) | Records which articles your view has already been counted against, so one reader does not inflate an article’s read count. Contains article IDs, nothing that identifies you. | 1 hour |
wordpress_logged_in_*, wordpress_sec_*, wp-settings-* |
WordPress (first party) | Keeps you signed in and remembers your preferences. Created only if you register or log in. | Session to 1 year |
wp-wpml_*, Ultimate Member session cookies |
Site software (first party) | Session handling for reader accounts and forms. Created only when you use those features. | Session |
| Anti-spam / form tokens | First party | Protects the contact and newsletter forms from automated abuse. | Session |
2. Functional — limited use
These remember choices you make so the site behaves better, without tracking you.
| Technology | Set by | Purpose | Lifetime |
|---|---|---|---|
cad_v3_* local storage entries |
CADialogue (first party) | Caches the market figures shown on the homepage so they are not re-fetched on every page view. Holds prices only — nothing about you, and it is never sent to our server. | 15 minutes |
| Google Maps cookies | Google (third party) | Set only by the office map embedded on our contact page. If you do not open that page, they are never created. | Google’s own periods |
3. Analytics — not in use
CADialogue does not currently run Google Analytics, Microsoft Clarity, Hotjar, Meta Pixel, or any other third-party analytics or tag-management product. There is no analytics cookie on this site to list.
If we introduce one, we will name it here before it is switched on, and it will be placed in the analytics consent category rather than loaded automatically.
4. Advertising — not in use
No advertising cookie, pixel or advertising identifier is present on CADialogue today. We are preparing to work with Google Ad Manager, and this section describes what will apply once that happens — not what is happening now.
When advertising is live:
- Google and its advertising partners may use cookies, device identifiers, IP addresses, web beacons and similar technologies to select and deliver advertisements, to cap how often you see the same one, and to measure performance and detect fraud.
- Advertising cookies will be placed only in line with the consent you give, and personalised advertising only where you have consented to it and it is lawful where you are.
- This table will be filled in with the actual cookie names once the ad stack is live, rather than pre-populated with names we have copied from somewhere else.
For how Google itself uses data from sites that use its advertising services, see policies.google.com/technologies/partner-sites. You can change Google’s ad personalisation for your own account at adssettings.google.com.
Requests that are not cookies but still reveal your IP address
Some things your browser loads from other companies do not set a cookie but do tell that company your IP address, because your browser has to ask them for the file. On CADialogue these are: Google Fonts (our typefaces), Pexels (some stock photographs), and the market-data APIs CoinGecko, jsDelivr currency-api, Frankfurter and mfapi.in. Our stock index, metals and crude figures are fetched by our own server instead, so those providers never see you.
Changing your choices
In your browser
Every major browser lets you see the cookies a site has stored, delete them, and block new ones. Look under Settings, then Privacy. Blocking strictly necessary cookies will stop sign-in and form submission from working.
On this site
The footer of every page carries a permanent “Privacy & Cookie Settings” link.
Because there is currently no advertising and no analytics on CADialogue, there is no consent to collect and therefore no consent dialog — showing one would ask you to agree to something that is not happening. That link therefore brings you to this page today. Once a Google-certified consent management platform is live alongside advertising, the same link will reopen that platform’s own dialog, where you will be able to accept, refuse, or change and withdraw any choice you previously made.
Questions
Write to [PRIVACY CONTACT EMAIL REQUIRED] or use our contact form. Our full Privacy Policy explains what we do with personal information generally.
Bhavik Vaid
Bhavik Vaid writes on Indian markets, taxation, banking and personal finance for CADialogue. He covers RBI policy, GST and income-tax changes, mutual funds and market moves, translating them into practical guidance for retail investors, salaried professionals and business owners in India.