lecram
Privacy & analytics
What this site measures.
The short version. lecrams.com (this marketing site) uses self-hosted Umami analytics. No cookies are sold, no data leaves our infra, and there's no third-party telemetry. The lecram operator app at lecram.lecrams.com remains zero-telemetry, this disclosure applies only to the public marketing pages.
What we measure on lecrams.com
We're running an A/B/C/D landing-page split test (backlog #92) to figure out which design converts best. To do that, the apex sets one cookie and a self-hosted analytics service records a few events.
lc_v, split-test bucket assignment (0,1,2, or3). Path/,SameSite=Lax,Secure, 30-day lifetime. No personal information.- Pageviews, time on page, scroll depth (25 / 50 / 75 / 100%), and clicks on the “Self-host the console” CTA, broken down by variant.
Where the data lives
A self-hosted Umami sidecar runs on the same host as the marketing site, behind analytics.lecrams.com. Data sits in a private Postgres volume on our infrastructure. There is no Google Analytics, no Plausible Cloud, no Mixpanel, no Segment, no third-party pixel.
What the operator app does NOT measure
The lecram operator console at lecram.lecrams.com ships with zero analytics. No marketing-site script is injected there, by design, operator workflows on real engagements stay private. That is the brand promise; it is enforced at the Caddy vhost level (the analytics tracker is only loaded by the marketing apex).
Opting out
The split-test bucket cookie can be deleted from your browser at any time; you'll be reassigned on next visit. To skip analytics entirely, browser-level “do not track” / extensions like uBlock Origin or NoScript will prevent the Umami beacon from firing, the page still works.
Contact
Questions, corrections, takedown requests: hello@lecrams.com. Security disclosures: security@lecrams.com (see /.well-known/security.txt).