Residency posture / explicit
EU-resident agent telemetry, by architecture — not by badge.
EU-native is an architecture constraint, not a badge. Telemeter is designed around regional storage, explicit sub-processors, exportable telemetry, and a self-hosting path.
Web hostVercel
Data storeSupabase planned
TelemetryRegional target
StatusArchitecture commitment · not certified
What the commitment means—and does not mean.
Current providers and planned controls are stated separately. This page does not claim GDPR compliance, certification, or a deployed EU telemetry region before verification.
Residency
Choose the region intentionally
Production telemetry storage is planned with EU residency as a first-class deployment choice, including regional backups and restore drills.
Planned: verify before launchPortability
Keep open interfaces at the boundary
OpenTelemetry ingestion and documented export paths reduce the cost of moving data or operating a self-hosted deployment.
Current: architecture commitmentTransparency
Publish the actual processing chain
The legal surface will list sub-processors, purposes, regions, and change dates based on the deployed system.
Current: draft register