Last updated
Privacy policy
warden is a command-line tool that leases simulators to coding agents, and this site documents it. Neither has accounts, adverts or tracking across other companies' sites. This page lists everything that leaves your device, where it goes and why.
At a glance
- No accounts, sign-in or profiles. Nothing we receive has your name or email address on it.
- No adverts, no tracking across other companies' sites, and nothing is sold.
- The website counts visits with PostHog without cookies. PostHog sets a cookie and records your session only if you accept.
- The
wardenCLI sends nothing about you. It talks to npm and GitHub only to update itself. - Your settings, the site's light or dark choice and your answer to the cookie banner, stay on your device.
Who we are
Delacour Limited, a company registered in New Zealand, runs warden.co.nz and the warden command-line tool, and is responsible for the personal information they handle. Write to chris@delacour.co.nz about anything on this page.
This page covers warden only. The studio site, delacour.co.nz, has its own policy.
The website
warden.co.nz counts visits with PostHog, reached through our own address, i.delacour.co.nz. Until you choose Accept in the banner, PostHog stores nothing on your device and counts you without cookies. Choose Accept and PostHog keeps an identifier in a cookie and your browser's local storage, so a later visit is recognised as yours, and records your session: the pages you see, where you click and scroll, and what you type into search. Anything typed into a form field is masked before it leaves your browser.
The site's fonts are served from our own address, so loading a page involves only the parties below.
- What
- Each request: your IP address, your browser's user agent, the address of the page and the time
- Goes to
- Railway, which hosts the site
- Why
- To serve the page and keep the site running. Railway keeps these request logs for a limited period set by its plan.
- What
- What you type into search, once you stop typing, and how many pages it found
- Goes to
- Our own server to answer it, and PostHog to count it
- Why
- Answered from an index held in memory, which does not log it. The query and its result count go to PostHog so we can see what people look for and what the docs are missing. Do not type anything personal into it.
- What
- The pages you visit and what you do on them: where you click and move the mouse and how far you scroll, links you follow to other sites, files you open such as
llms.txt, and when you copy a command, a prompt or a code sample; the page you came from, your browser, operating system, device type, screen size and language, and your IP address - Goes to
- PostHog, through our reverse proxy at
i.delacour.co.nz - Why
- To count visits, see how people use the docs and draw heatmaps of where they click. PostHog uses your IP address to work out an approximate location and, until you accept, to count you with a hash that changes every day instead of a cookie. If you accept, it also stores a random identifier in a cookie and in local storage (
ph_…) that recognises your browser on a later visit; decline later and it deletes them.
- What
- Only if you accept: a recording of your visit, as the page's structure and your clicks, scrolling and typing over time, with every form field masked
- Goes to
- PostHog, through our reverse proxy at
i.delacour.co.nz - Why
- To watch how a reader moves through the docs and where they get stuck. Nothing is recorded until you choose Accept, and choosing Decline later stops it. The recording is of this site only.
- What
- When a program rather than a browser reads
llms.txt,llms-full.txtor a documentation page's Markdown: the address read and the program's user agent, for exampleClaudeBot/1.0orcurl/8.7.1 - Goes to
- PostHog, sent by our own server
- Why
- Coding agents run no scripts and see no banner, so our server counts these reads itself. It sends no IP address; PostHog sees only our server's.
- What
- Your light or dark choice, and your answer to the cookie banner
- Goes to
- Your browser's local storage
- Why
- So the site remembers them. They are never sent to us.
A documentation page's Open menu can send that page to ChatGPT, Claude or another assistant. Nothing is sent unless you choose one, and then that service's own policy applies.
The command-line tool
The warden CLI collects no telemetry and has no account. It runs on your own Mac or CI runner, and the only requests it makes beyond your machine are the ones below.
- What
- A version check and, if you update, a download: your IP address and the package requested
- Goes to
- npm,
registry.npmjs.org, or whichever registry your package manager uses - Why
warden updateasks the registry for the latest version and downloads it. The check runs only when you run the command.
- What
- A download of the simulator helper: your IP address and the release asset requested
- Goes to
- GitHub,
github.com/delacournz/warden/releases - Why
warden updateandwarden doctor --fetch-helperfetch the native helper that drives iOS simulators, and check it against the release's published checksum.
- What
- Simulator, emulator and app traffic
- Goes to
- Apple's and Google's tooling on your own machine, and your own app's servers
- Why
- warden runs
simctl,adband your app's dev server locally. What your app sends while it runs is governed by your app, not by warden.
- What
- Leases, device records, build caches and e2e evidence
- Goes to
- Your own machine, under
~/.warden - Why
- So every agent and shell on the machine claims from one registry, and a failed spec leaves a screenshot and the screen tree to read. Delete the folder at any time.
warden install edits the configuration of the coding agents it finds on your machine, after showing a diff and asking. Those edits stay on your machine. What an agent then sends to its own provider is governed by that provider's policy.
Who else handles it
The companies above process this information for us under their own terms. They are based in the United States, so it is processed there:
Railway for hosting the website, PostHog for the website's visit counts and recordings, npm for the CLI's updates, and GitHub for the helper download.
We do not sell or rent anything to anyone, and we do not share it with anyone else unless the law requires us to.
Why we use it
Only to run the website and the CLI, to count how many people use them, to see which pages and searches get used and where readers get stuck, and to fix what breaks. We do not combine it with anything else, and we do not use it to identify, profile or advertise to anyone.
If UK or EU data protection law applies to you, our lawful basis is our legitimate interest in running and improving these services, which we have weighed against your interests given how little is collected. That covers PostHog's cookieless counting. For PostHog's cookie, local storage and session recording, it is your consent, which you can withdraw at any time from Cookie settings at the foot of the home page.
How long it is kept
What stays on your device is there until you clear it. Railway, PostHog, npm and GitHub keep what they receive for the periods their own policies set, linked above.
Your rights
Under New Zealand's Privacy Act 2020 you can ask to see personal information we hold about you and to have it corrected. If you are in the UK or the EU you can also ask us to delete it, to restrict or object to how it is used, or to give you a copy. Write to chris@delacour.co.nz.
Nothing we receive has your name on it, so we may not be able to find information about you in particular. Declining in the cookie banner is the surest way to stop a recording.
If you are unhappy with how we have handled a request, you can complain to New Zealand's Office of the Privacy Commissioner, the UK's Information Commissioner's Office or the data protection authority where you live.
Children
warden is a tool for software developers and is not directed at children. We do not knowingly collect information from anyone under 16.
Changes to this page
When this page changes, the date at the top changes with it. Every earlier version is public in the repository's history.