Cookie Policy

1. What this site stores in your browser

The developer tools on DevSnap run entirely in your browser and do not set any cookies. They use your browser's local storage for two things, and local storage is not a cookie: it is never sent to a server and does not travel with a request.

• devsnap-theme — whether you chose the light or the dark interface. Used so the site does not flash the wrong colours on your next visit.
• devsnap-consent — your answer to the advertising consent banner, so it is not shown again on every page.

Clearing your browser's site data removes both. Nothing else is stored, and no identifier of any kind is created for you by the tools.

2. Cookies set by the advertising

This site is funded by advertising, and the ad networks involved set their own cookies and similar technologies. They are set by Google AdSense and its partners, not by us, and they are used to serve advertising and to measure how effective it is.

The full list of cookies Google may set is documented by Google itself, and the list changes over time. The table above covers the ones that apply to a site of this kind.

3. Consent

The first time you arrive, a banner asks whether you accept advertising cookies. Until you answer, the answer is treated as no, and the site behaves differently depending on where you are.

Outside the European Economic Area, the United Kingdom and Switzerland, the ad slots load with non-personalised advertising: the impression is measured, but it is not based on a profile of your interests and the profiling cookies in the table above are not set.

Inside those regions, no advertising request is made at all until you press Accept. The slot is withheld rather than filled, because the ePrivacy rules require consent before an advertising cookie is written, and "we only set the non-profiling ones" is not an exception that exists in the text.

If you accept, the page reloads once and advertising becomes personalised. If you reject, the banner does not come back and the site keeps working exactly as before. You can change your answer at any time using the "Cookie choices" link in the footer.

Google requires a consent platform certified under its EU user consent policy for personalised advertising in those regions. When the site serves advertising, that platform (Google's own, Funding Choices) takes over the prompt and this site's banner steps aside, so you are never asked the same question twice.

3a. How the region is decided

Without a server there is no IP address to look up, so the region is inferred from your browser's timezone. The test treats every Europe/* and Atlantic/* zone as the regulated region. That deliberately over-includes a few countries outside the EEA, which means some visitors are asked for consent when the law would not require it. The alternative — under-including a country — would mean setting cookies without consent, so the error goes in the safe direction.

4. How to control cookies

• Use the "Cookie choices" link in the footer to change your answer.
• Delete cookies in your browser settings. Every major browser can block or clear cookies for a single site.
• Opt out of personalised advertising from Google at adssettings.google.com.
• Opt out of third-party vendor cookies at aboutads.info.
• Use Google's Do Not Track control, which is honoured by Google advertising.

5. Do Not Track

Some browsers send a Do Not Track header. The site honours it: when the header is present, the advertising is never personalised, even if you previously pressed Accept. You do not have to trust that sentence — the check is in the page source and it runs before any ad slot is requested.

6. Third-party embeds

The tools do not embed third-party content, so no other site receives information about your visit. Outbound links to other sites are ordinary links, and those sites have their own policies.

7. Changes and contact

If this policy changes, the date at the top changes with it. Questions: [email protected].