Cookie & Storage Policy

One cookie: dg_consent, which records whether you accepted or declined the two optional categories. It is set only once you have answered the banner, it contains your answer, its version and the date you gave it, and it identifies nobody. If you never answer, no cookie is written at all.

There is nothing else, because there is nothing else to serve. This site has no login, no basket, no server-side session, no analytics, no tag manager, no advertising pixel, no embedded video, no embedded map and no social widget. Every page is a static file built in advance; the photographs and the typefaces are served from this same origin, so loading a page does not call out to anybody.

Four further items are kept in your own browser rather than in a cookie. One of them is a copy of that same consent answer, in case your browser refuses cookies; the other three belong to the planner, the game and the opening animation. None of them travels to us — no server here receives them — but they are still your storage on your device, so they are listed below by name in exactly the same way.

Three different things, often lumped together, and the difference matters:

• A cookie is a small named value your browser stores and then sends back to the website with every request. That is what makes cookies useful for recognising a returning visitor — and what makes them worth asking about.
• Local storage is a box in your browser that a page can read and write, and which is never sent anywhere on its own. A site has to deliberately transmit it, and this one does not.
• Session storage is the same box, emptied when you close the tab.

Everything on this site that is not the consent cookie is the second or third kind: written by the page you are looking at, read by the same page, and deleted the moment you clear your browser data. The planner draft and the game score exist because you started using the planner or the game, and they hold only what you typed or scored.

• Strictly necessary — in use. The consent cookie itself, and the flag that stops the opening animation replaying. A site cannot honour your choice without remembering it.
• Functional — in use, on your device only. The planner draft and the game score. They improve the two features they belong to and nothing else; neither is transmitted, neither identifies you, and neither is read by any other page.
• Analytics or performance — not in use. There is no measurement tool on this site of any kind, first party or third. If that changes it will appear in the table above, with its real name and lifetime, before it is switched on.
• Marketing — a switch with nothing behind it. The consent panel offers a Marketing category so that your answer is on record before anything could ever exist. There is no ad network, no remarketing tag, no conversion pixel and no share widget that phones home on this site, and none is planned. We do not run advertising, so there is nothing to measure and nobody to sell an audience to.

One difference worth explaining. The consent panel lists all five items above under Strictly necessary, because none of them is optional in the sense a panel means: there is no switch that turns them off, and clearing your browser data is how you remove them. This page draws the finer line, because it can — two of the five are there to make a feature work rather than to make the site work, and you deserve to know which is which.

The consent banner on this site is a switch, not a decoration. Its answer is what would decide whether an optional script is fetched at all — not a preference we record and then ignore. Because nothing optional is loaded today, saying no changes nothing you can see, which is the honest state of affairs and the reason we say so on the banner itself.

• Declining is one click, the same size as accepting, and closing the banner is not taken as consent.
• There are two optional switches — Analytics and Marketing — and both are off until you turn them on. Today neither of them has anything behind it.
• Your answer is stored in the dg_consent cookie for 180 days, then the banner asks again.
• Nothing optional loads before you answer. There is no “we assume you agree if you keep scrolling”.

Use the Cookie settings button in the footer, at the bottom of every page on this site. It reopens the banner with your current answer showing, and a new answer replaces the old one immediately. Withdrawing consent is exactly as easy as giving it, which is the law and also just good manners.

You can also simply clear this site’s data in your browser, which removes both dg_consent and its local copy. The banner will then ask you again on your next visit, as though you had never answered.

Everything on this page lives in your browser, so your browser can remove all of it — the consent cookie and its copy, the planner draft, the game score and the animation flag — in one go. Look for the option to clear “cookies and site data” for this site:

• Chrome or Edge: click the icon at the left of the address bar, then Cookies and site data → Manage on-device site data → delete.
• Safari on a Mac: Settings → Privacy → Manage Website Data, search for this site, remove.
• Safari on iPhone or iPad: Settings → Safari → Advanced → Website Data, then swipe to delete this site.
• Firefox: click the padlock in the address bar → Clear cookies and site data.
• Any browser: a private or incognito window keeps none of it after you close the window.

Clearing site data will also forget your unfinished planner answers and your best score in the game. That is the trade, and it is the right one to be able to make.

Blocking cookies for this site entirely is fine too. Every page still works; the banner will simply ask again each visit, because it has nowhere to write your answer down.

None. No third party sets a cookie on this site, because no third party runs code on it. That is a design decision, and it is why this page can be so short:

• the photographs are stored and served from this site, not fetched from an image host;
• the four typefaces are built into the site rather than requested from a font service;
• the map of Jaipur on our contact page is drawn in SVG rather than embedded from a map provider;
• the WhatsApp and Telegram links are ordinary links — nothing from either company loads here.

Follow one of those links, of course, and you are on their site under their rules. Which companies then see what is set out in our Privacy Policy.

Some browsers send a Do Not Track header or a Global Privacy Control signal. There is nothing on this site for either of them to switch off today, because we run no tracking at all. If analytics is ever enabled, a Global Privacy Control signal will be treated as a refusal, and we will not ask you again over the top of it.

We may one day want to know which journeys people actually read about, and how they reached them. If that happens, this page changes before anything else does:

• the table above gains a row naming the tool, the cookie or key it sets, and how long it lasts;
• the row is in the Analytics category, which means it is off until you say yes;
• the script is not on the page in any form until consent is recorded — declining means it is never fetched, not merely told to keep quiet;
• your existing answer is re-asked, because consent to something that did not exist when you answered is not consent.

Advertising and cross-site tracking are not on that list and never will be. See our Privacy Policy for what we would and would not do with the numbers.

This page is kept in step with the code, not with an industry template. When the site starts or stops setting something, the table changes on the same day and the date at the top moves with it. If you think the table is wrong — you found a cookie we have not listed — please tell us at hello@devgaman.com and we will fix the page or the code, whichever turns out to be at fault.

Version 1 · 6 September 2026 · first publication