Privacy Policy

This policy describes data handled by this local installation of Selat. It does not claim anonymity or a certified no-logs service.

Data we store

The SQLite database holds names, email addresses, password hashes, session-token hashes, plan and subscription records, coupon redemptions, manual payment references and notes, user-entered device labels, encrypted VPN credentials, traffic volume, connection timestamps and administrative audit events. Rate-limit keys are hashed; when a trusted proxy is enabled, its forwarded client address may contribute to these short-lived keys.

Data we do not collect

The application does not collect browsing history, website history, DNS query history or packet contents. Traffic accounting stores upload and download byte counts. Development telemetry and connections are simulated and clearly labelled.

Why we use it

We use account and entitlement data to authenticate users, deliver configurations, apply quotas and device registration limits, manage manual payment requests, and review administrative activity. Device labels are supplied by users; there is no invasive device fingerprinting.

Storage and access

Data is stored locally in SQLite. Session cookies are HTTP-only. Reversible VPN credentials and subscription tokens are encrypted with an environment-provided key. Administrators can access operational account data. No analytics SDK, paid payment processor or cloud receipt storage is included.

Retention and deletion

Expired sessions and rate-limit entries are removed opportunistically. Development telemetry is bounded to seven days after refresh; accounting, billing and audit records otherwise remain until the installation administrator applies a retention or deletion procedure. Request account data access or deletion from your installation administrator. Backups, if made, need their own deletion schedule.

Subscription links and infrastructure logs

Your subscription URL is a bearer secret. Anyone with it may retrieve an eligible profile. Regenerate it if exposed. The application avoids logging it; development request, server-function argument and browser-log forwarding are disabled. Do not share local logs. Future reverse proxies and VPN adapters must redact subscription URLs and avoid browsing, DNS and packet logs before deployment.