Privacy
No accounts, no cookies, no telemetry, and analytics that cannot identify you. This page exists to say what that leaves, rather than to imply it leaves nothing.
Last updated 2026-08-24.
What this website stores
One value, in your browser's localStorage, under the key lamintra-theme. It records whether you chose the dark or light scheme so the page does not flash the wrong one on your next visit. It never leaves your device, it is not a cookie, and clearing site data removes it.
There is nothing else on your device. No cookies are set, no session is created, there are no forms to submit, and there is no account to make. Nothing on this site asks who you are.
Analytics
Since 2026-08-11 this site counts page views using Plausible, which was chosen over Google Analytics specifically so that the paragraph above stays true.
It sets no cookie and stores nothing on your device. It records the page you were on, the referrer, and coarse device and country information derived from your IP address and user agent. It does not store your IP address, does not create a profile, does not follow you between sites, and cannot single you out. There is no identifier that persists past the day, so there is no way to link two of your visits together, including for us.
The data is stored on servers in the EU. It is not sold, not shared with advertisers, and there is no advertising network involved at any point.
One thing is deliberately measured beyond page views: pressing the Copy button next to an install command records that a command was copied. It records the event and nothing about who copied it.
This is why there is still no cookie banner. Consent attaches to storing or reading information on your device and to processing personal data; this does neither, so there is nothing to consent to. A banner here would be theatre. If you block it anyway, with a content blocker or by refusing the script, every part of this site works exactly the same.
Who else sees your visit
Naming them is the honest version of "we collect nothing".Two third-party servers are contacted when you load a page here: the analytics script described above, and the host's performance beacon described below. The typefaces are served from this domain, and there is no CDN, no embed, no tag manager and no advertising network.
Until 2026-08-11 the fonts loaded from Google's servers, which disclosed your IP address to Google before you interacted with anything. A German court has held that arrangement to be processing personal data without a lawful basis. The font files are now served from here, so that transfer no longer happens.
Plausible
The analytics script is served from Plausible and reports a page view back to it. That request necessarily discloses your IP address to Plausible in transit, the same as any request to any server. Plausible does not store it: it is used to derive a country and then discarded. See the section above for what is kept.
The host
The site is static files served by a hosting provider, which keeps ordinary server logs including IP addresses, for delivery and abuse prevention. Every website has this; it is not specific to Lamintra.
That host is Cloudflare, and its Web Analytics beacon is injected into each page automatically. It reports page-load timings - the Core Web Vitals - so that this site's speed can be measured with real visits rather than guessed at. It sets no cookie and stores nothing on your device, and Cloudflare already receives your IP address as the server delivering this page, so the beacon discloses it to nobody new.
Added to this page on 2026-08-21, after the beacon was found running and undeclared. It had been enabled at the hosting layer rather than added to the site's code, so it appeared without a change to this repository, and both this page and the compliance page said for some time that exactly one third-party server was contacted. That was wrong, and it was found by opening the browser console on the live site rather than by reading the source - which is the only place it could have been found.
GitHub
Links to the source, the registry and the releases go to GitHub. If you follow one, or download the jar, GitHub sees that request under its own privacy policy.
What the CLI does on your machine
lamintra init reads your project layout off disk and writes .lamintra/config.json into your project. That file stays on your machine and is never transmitted.
lamintra add makes ordinary HTTPS GET requests to raw.githubusercontent.com to fetch component sources. GitHub therefore sees your IP address and which files you requested, the same as if you had opened the registry in a browser.
The CLI sends nothing back. There is no POST anywhere in it, no telemetry, no usage counter, no crash reporting and no update check. It does not know your project name, your package name, or that you exist. You can confirm this rather than trust it: the CLI is open source, and its only network calls are the GET requests in Registry.kt.
Your rights, practically
Rights of access, correction, erasure and portability all attach to personal data held about you. Nothing here holds any: there is no database, no account and no record of your visit beyond the host's own logs. There is consequently nothing to export and nothing to delete.
If you believe that is wrong, or something on this page has stopped being true, email [email protected] - a data question is not always something you want to post publicly - or open an issue if you'd rather. Either way it gets corrected.