YOUR ROUTE IS NOT OUR RECORD.

Effective 11 July 2026. This page describes F Society's operating privacy boundary in plain language.

What we never keep

• Browsing history, destination history, or traffic contents
• DNS request history
• Long-term connection history tied to an account
• WireGuard private keys
• Advertising identifiers or third-party analytics profiles

What the service needs

We retain the minimum records needed to sell and operate access: your verified Google email and subject identifier, optional Google display name and avatar URL, subscription and payment references, device labels and public keys, assigned region, per-member VLESS credential, and support messages you choose to send. If you link Telegram, we also retain that chat identifier.

Who processes data

Google processes member authentication, Stripe processes web payments, and Telegram processes bot messages when you use that channel. Happ processes subscription data on your device; if optional Happ provider telemetry is enabled, Happ may receive a subscription-domain hash, device identifier, operating-system details, and Provider ID. Their own policies apply to data handled on their systems. F Society does not add advertising or behavioral analytics providers.

Retention and security

Google login uses PKCE and a signed state cookie that expires after ten minutes. Telegram portal tokens are stored only as hashes and expire after fifteen minutes. Billing records are retained as needed to operate subscriptions and meet accounting obligations. WireGuard and VLESS access is removed from active nodes when revoked or expired.

Questions

Use the F Society Telegram support command or your member account to ask about account data, correction, or deletion.