Privacy

Privacy policy

Delacour UI is a component library, the site that documents it, an app for trying the components on a phone, and a command-line tool that copies them into your project. None of them has accounts, adverts or tracking across other companies' apps and sites. This page lists everything that leaves your device, where it goes and why.

Last updated

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' apps or websites, and nothing is sold.
  • The app tells Expo each time it starts, checks with Expo for updates, and sends Expo reports on its speed, the screens you open and any errors.
  • The website counts visits with PostHog without cookies. PostHog and Google Analytics set cookies only if you accept them. Fonts load from Google.
  • Your settings — the site's light or dark choice, the app's theme — stay on your device.

Who we are

Delacour Limited, a company registered in New Zealand, runs ui.delacour.co.nz, the Delacour UI app and the delacour 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 Delacour UI only. The studio site, delacour.co.nz, has its own policy.

The website

ui.delacour.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.

The site also runs Google Analytics, and only if you choose Accept. Until then its script is not even loaded, so Google receives nothing. The site shows no adverts, so the advertising settings stay off whatever you choose.

Loading a page also involves the parties below.

What
Each request: your IP address, your browser's user agent, the address of the page — including any ?preset= theme code in it — 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
Font requests: your IP address, your browser's user agent and the page they came from
Goes to
Google Fonts — fonts.googleapis.com and fonts.gstatic.com
Why
To draw the site's typefaces. The theme builder at /theme loads more families when you try its Font axis.
What
What you type into search, once you stop typing, and how many pages it found
Goes to
Our own server to answer it, PostHog to count it, and Google Analytics to count it if you accept
Why
Answered from an index held in memory, which does not log it. The query and its result count go to PostHog, and to Google Analytics if you accept, 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 — links you follow to other sites, files you open such as llms.txt, and when you copy a command, a theme 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 and see how people use the docs. 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. It records no sessions, clicks or mouse movements.
What
When a program rather than a browser reads llms.txt, a documentation page's Markdown or a skill file: the address read and the program's user agent — for example ClaudeBot/1.0 or curl/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
Only if you accept: the pages you visit and what you do on them — links you follow to other sites, files you open such as llms.txt, and when you copy a command, a theme or a code sample — your device and browser, and a random identifier stored in a cookie (_ga) that recognises your browser on a later visit
Goes to
Google — Google Analytics, loaded from googletagmanager.com
Why
To understand how people move through the docs over time. Decline, or never answer, and Google Analytics sets no cookies and receives nothing. Change your mind with Cookie settings at the foot of the home page.
What
Your light or dark choice, scroll positions, and your answer to the cookie banner
Goes to
Your browser's local and session 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, Cursor or Scira. Nothing is sent unless you choose one, and then that service's own policy applies.

The app

The Delacour UI app has no account and asks for no permissions — no camera, photos, contacts, location or notifications. It reports to Expo, the company whose tools it is built with, in three ways.

What
A launch ping: a random install ID, the app version, the platform (iOS or Android) and the operating system version
Goes to
Expo — EAS Insights, i.expo.dev
Why
To count how many installs open the app, and on which versions.
What
An update check: the same install ID, the platform and the app's build and release identifiers. If the app crashed the last time it ran, the crash's error message goes with it
Goes to
Expo — EAS Update, u.expo.dev
Why
To deliver fixes without a new store release, and to roll back an update that crashes.
What
Performance and error reports: the same install ID and a session ID; the app version and its build and release identifiers; the device model, operating system and language setting; how long the app takes to start and to draw each of the screens you open, with their parameters — such as which demo is showing — and how long you use it; battery level and charging, power-saving mode, device temperature, network connection and dropped frames; the number, size, failures and timing of the app's network requests, and the host of the slowest; and, when something goes wrong, the error message and where in the code it happened
Goes to
Expo — EAS Observe, o.expo.dev
Why
To see how quickly the app starts and draws each screen, which demos get opened, and what breaks. Reports are sent when the app goes to the background, and the app keeps its own copy for up to seven days.
What
The theme you build in the customiser, and your light or dark choice
Goes to
Your device only
Why
So the app opens the way you left it. Deleting the app deletes them.

The install ID is a random number the app makes the first time it runs. It is not your name, your email address or your device's advertising identifier, and it is not linked to any of them. Deleting the app discards it, and reinstalling makes a new one. The session ID is another random number, made each time you open the app, which only groups one visit's reports together.

The app cannot ask before sending the launch ping: it goes out as the app starts, before anything is on screen. The app has no setting that turns off the launch ping or the performance reports. If you would rather neither were sent, the way to stop them is to delete the app.

Two buttons open the website in your browser — Generate CSS, which puts your theme into the page address as a short code, and Privacy policy, which opens this page. The website section above then applies.

If you have chosen to share analytics with app developers in your device's settings, Apple or Google may also show us summary statistics about the app, such as crash counts. Their policies cover that sharing, and you can turn it off there.

The command-line tool

The delacour CLI collects no telemetry. It only makes the requests its commands need.

What
Requests for component source: your IP address and the files requested
Goes to
GitHub — raw.githubusercontent.com — or a registry you configure
Why
To download the components you asked it to add.
What
Package installs
Goes to
npm, or whichever registry your package manager uses
Why
The CLI runs your own package manager, which makes these requests under its own policy.
What
Downloaded component source
Goes to
A cache in your home folder, ~/.cache/delacour
Why
So a second run does not download the same files again. Delete the folder at any time.

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:

Expo for the app's launch pings, performance reports and updates, Railway for hosting the website, PostHog for the website's visit counts, Google for its fonts and Google Analytics, and GitHub for the CLI's downloads.

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, the app and the CLI, to count how many people use them and on which versions, to see which pages, searches and demos get used, to see how fast the app is, 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 Google Analytics, and for PostHog's cookie and local storage, it is your consent, which you can withdraw at any time from Cookie settings.

How long it is kept

What stays on your device is there until you clear it or delete the app, except the app's copy of its performance reports, which it deletes after seven days. Railway, Expo, PostHog and Google 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. Deleting the app is the surest way to stop it sending anything.

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

Delacour UI 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.