This policy explains how the Perch website (perch.lxghtblvee.dev) handles
information about its visitors. It does not cover Perch the software when you
run it yourself, see the note at the bottom for that.
The short version: this is a static informational site. We don’t run accounts, analytics, advertising, or tracking, and we don’t sell or share your data.
What we collect
We do not ask you for any personal information, and the site sets no first-party cookies. The only data processed when you visit is what any website necessarily receives or generates:
- Request logs. Our server keeps standard access logs, IP address, user agent, requested page, and timestamp, for security, debugging, and basic operational insight. These are kept for a short period and are not used to profile you.
Third parties
A couple of services are involved in delivering the site to your browser:
- Cloudflare sits in front of the site as a CDN and security proxy. Your
request passes through Cloudflare, which processes connection data (including
your IP) to route traffic and block abuse, and may set a strictly necessary
security cookie (
__cf_bm). See Cloudflare’s privacy policy. - Google Fonts. The site loads its typefaces from Google Fonts, so your browser makes a request to Google’s servers, which receive your IP address as part of that request. See Google’s privacy policy.
We use no analytics, tag managers, advertising pixels, or social trackers.
Your choices
Because we don’t build a profile of you, there’s nothing to opt out of, export, or delete. If you have a question about your data, email [email protected].
About self-hosted Perch
When you deploy Perch on your own infrastructure, all of the data it handles, metrics, container stats, health checks, user accounts, OAuth tokens, stays on your servers. It is never sent to us. You are the data controller for your own instance, and this policy does not apply to it.
Changes
If this policy changes, the “last updated” date above will change with it.