Privacy Policy
Last updated: November 2026
What we collect
For your account: name, email address, and — if paid plans are open — billing identifiers handled by Stripe (we never store card numbers). For monitoring: the URLs you configure, the events your SDKs send us, and the results of HTTP checks. For audits: the submitted URL, the crawled pages, and the computed findings.
Telemetry may contain personal data
Error payloads are produced by your application. Depending on your SDK configuration they may contain user identifiers, request URLs, headers, cookies or breadcrumbs. You control what your SDK sends; we recommend disabling request bodies, cookies and headers in production. We do not sell this data, and access is limited to operating the service.
What we keep, and for how long
- Account data: until you close your account.
- Logs, uptime checks, incidents and traces: up to 90 days (ClickHouse TTL), then deleted automatically.
- Audit findings: while your account is active; raw crawled HTML is not retained after scoring.
- Billing records: as required by applicable accounting law.
What we do not collect
We do not track the visitors of audited sites, we do not set cookies on audited domains, and we do not sell your data.
Where data lives
The service runs on EU-hosted infrastructure. Monitoring state lives in PostgreSQL, telemetry in ClickHouse; backups are operated by the service operator (see the deployment documentation).
Your rights
You can request export or deletion of your data at any time by emailing privacy@logswire.com. Requests are processed within 30 days. Self-service account deletion is not available during the public beta.
Sub-processors
- Stripe — payment processing (only when paid plans are enabled)
- Mailgun — transactional email
- Netcup — EU infrastructure
Changes to this policy
Material changes will be announced by email at least 14 days in advance and shown in-product on next login.