Privacy

Data stored

Your instance stores user accounts, connected provider credentials, and application data such as preferences and usage snapshots in its local SQLite database. The server operator is responsible for protecting database files and backups.

Provider API keys and OAuth secrets are encrypted at rest using AES-256-GCM. The encryption key is derived from USAGE_MASTER_KEY. This does not mean every database field or backup is encrypted; protect file and backup access separately.

Passwords are hashed with Argon2id, and session token hashes are stored instead of the session tokens themselves.

Retention and deletion

Usage snapshots are retained for 7 days by default. The server operator can change this period with SNAPSHOT_RETENTION_DAYS.

Deleting a provider credential removes its associated usage snapshots through SQLite ON DELETE CASCADE constraints. Deleting an account also removes its sessions, credentials, usage records, password-reset records, and invitations created by that user. Previously created backups are managed separately and may not be affected by these deletions.

Provider requests and sharing

useMeter does not sell telemetry or account data. To collect usage data, your instance sends requests to the API endpoints of providers you connect; a provider-issued access token or API key may be included as authentication. Providers process those requests under their own privacy notices and terms.