Cookie Policy
Last updated: August 3, 2026
This Cookie Policy explains what Skyble Lab stores on your device when you visit landscapedesign.io, why, and how to stop it. It is a companion to our Privacy Policy — that document covers what we do with the data once it reaches us, and section 1g of it describes our analytics in full. This page is narrower: it is the list of the actual files.
The short version. This website sets three cookies, all of them first-party, all of them analytics. It sets no advertising or marketing cookies, loads no third-party cookie, and contacts no advertising network. There is no consent banner — see section 6, which explains what that means if you are reading this from the EU or the UK.
1. What a cookie is here
A cookie is a small text file a website asks your browser to keep and hand back on your next visit. A first-party cookie is one set under the address in your URL bar — landscapedesign.io — and is readable only by this site. A third-party cookie is set under someone else’s domain and is what makes cross-site tracking possible. Every cookie listed below is first-party. We set no third-party cookies.
Cookies are not the only way to store something in a browser, and this policy does not pretend otherwise. Section 4 covers the non-cookie storage our analytics also uses.
2. The cookies this website sets
Observed on landscapedesign.io in a clean browser on August 3, 2026. This is the complete list, not a representative sample.
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
_ga | Google Analytics 4 | Tells one browser apart from another, so ten visits from you are counted as one person rather than ten. | 400 days |
_ga_9DJS6D5LFR | Google Analytics 4 | Holds session state for this specific property — when the current visit started and whether it is your first. The suffix is our measurement ID. | 400 days |
mp_46a411ebc8564d29271ba9c9196f2786_mixpanel | Mixpanel | Holds an anonymous device identifier and how you first arrived. Our own server reads it too, so that a click on a download button is joined to the pages that led to it instead of being recorded as an unrelated stranger. The suffix is our public Mixpanel project token. | 365 days |
On the lifetimes. These are the expiry dates the cookies actually carried when we read them, rounded to the day. They are set by Google’s and Mixpanel’s own libraries rather than by us, and either vendor can change its default in a future release without telling us. The lifetime also resets each time you visit, so a cookie on an active reader’s machine is effectively 400 or 365 days from their last visit rather than their first.
On the names. Two of the three names are generated rather than fixed: the suffix on the second cookie is our Google Analytics measurement ID (G-9DJS6D5LFR), and the middle segment of the Mixpanel cookie is our public Mixpanel project token. If we ever move to a different analytics property the names change with it, so treat the exact strings as subject to change and the pattern — _ga_<measurement id>, mp_<token>_mixpanel — as the stable part.
3. Categories
Strictly necessary. These are cookies without which a site cannot do what you asked it to — keeping you logged in, holding a shopping basket, carrying a security token through a form. As of the date at the top of this page, this website sets none of them. It has no accounts, no basket, no payment form and no file upload, so there is nothing for a necessary cookie to hold. Everything in the table above is analytics. We are stating this plainly rather than padding the category, because “strictly necessary” is the label most often used to smuggle analytics past a consent prompt.
Privacy Policy §1f summarises this website as using cookies “for essential functionality and aggregate analytics” and notes that essential cookies cannot be disabled. That is the general form of the statement; this page is the specific one, and it wins where the two differ. Today the essential half of that sentence is empty. If a strictly necessary cookie is ever added — to remember a preference you set, for instance — it will appear in the table above, and disabling it really would break the thing it exists for.
Analytics. All three cookies. They exist so we can count how many people read a page, which links get clicked, and where readers give up — the information that decides what gets written next. Our providers are Google Analytics and Mixpanel; what each one records, including Mixpanel’s session replay, is set out in Privacy Policy §1g.
Advertising and marketing. None. We run no retargeting pixel, no conversion tag, no ad network tag and no social tracking pixel, and we do not sell or share personal information for cross-context behavioural advertising. This is a claim you can check yourself: open your browser’s developer tools on any page of this site and look at the network requests. The only third-party hosts contacted are googletagmanager.com, google-analytics.com and api-js.mixpanel.com.
4. Similar technologies
Mixpanel also uses two kinds of browser storage that are not cookies, and the law in several places treats them the same way, so they belong on this page:
- Local storage — one key holding a short queue of events that have not yet been sent, so a click is not lost if you navigate away before the network request finishes. It persists until cleared.
- Session storage — two keys identifying the browser tab, discarded the moment you close it.
Neither is used for advertising and neither leaves your browser except as the analytics events already described in Privacy Policy §1g. Clearing site data in your browser clears both, along with the cookies.
5. How to refuse them
a. Your browser. Every major browser can block cookies or delete them, for all sites or for this one specifically, under Settings → Privacy. You can also block third-party cookies alone, though on this site that changes nothing, because we do not set any. Blocking or clearing our cookies breaks nothing you can see: no feature on this website depends on one. What it costs is on our side — your repeat visits are counted as separate people.
b. Do Not Track. Most browsers can send a Do Not Track signal. There is no industry standard for how a site should respond, and most ignore it. This one does not, and it is worth being precise about what it changes.
If your browser sends the signal, we still measure the visit in aggregate — pages viewed, links clicked — because that is what the site is instrumented for. What stops is storage and identity: no analytics cookie is written at all, no identifier survives the tab, and Google Signals and ad personalisation are switched off. Concretely: Mixpanel runs with persistence disabled, so no mp_ cookie is created, and Google Analytics runs with client storage set to none, so neither of the two _ga cookies is created. The visit is counted, and it cannot be linked to any previous or subsequent visit, or used to build an advertising profile. This is the same behaviour described in Privacy Policy §10.
So Do Not Track does stop the cookies on this website. It does not stop the counting, and we are not going to describe it as though it did.
c. Opting out at the source. Google publishes a browser add-on that opts you out of Google Analytics on every site that uses it, at tools.google.com/dlpage/gaoptout.
d. The mobile app. The AI Landscape Design app is not a browser and sets no cookies. It does collect device and usage data through the same analytics providers — see Privacy Policy §1e. As stated in §10 of that policy, the app does not currently change its behaviour in response to a Do Not Track signal.
6. There is no consent banner, and what that means
This website does not show a cookie consent banner. The three analytics cookies are set when the page loads, unless your browser sends a Do Not Track signal, in which case none of them are set.
We are not going to dress that up as compliance. In the EU and the UK, the ePrivacy rules and the GDPR require prior, freely given, informed consent before a non-essential cookie is stored on your device. Analytics cookies are non-essential. Consent is what governs them there — not a Do Not Track signal, not a legitimate-interest argument, and not a policy page like this one. Honouring Do Not Track is a choice we made because it is the right default, but it is not a legal substitute for asking, and an EU or UK visitor who has not enabled it will have these cookies set without having been asked first.
We are stating the position rather than claiming a compliance we do not have, so you can decide for yourself. If you are in the EU or the UK and you would rather not have these cookies, section 5 tells you how to prevent them, and both routes work: turn on Do Not Track, or block cookies for this domain. Neither costs you anything on this site.
Elsewhere the rules differ — in the United States, for example, Do Not Track has no legal force and the relevant question is usually sale or sharing of personal information rather than consent to storage. We do neither; see Privacy Policy §9 for the California-specific detail.
7. Changes to this policy
Analytics tooling changes, and when it does the table in section 2 changes with it. The current version of this policy is always posted here with its “Last updated” date. If we ever add a cookie in a category that does not appear above — an advertising cookie in particular — we will say so here before it ships, not after.
8. Contact
Questions about anything on this page, or about a cookie you have found that is not listed here, go to hello@skyblelab.ai. If you have found one we have missed, we want to know.