Encryption

MeetLogin uses industry-standard encryption to protect your profile data at rest and in transit.

Profile Data Encryption

All profile data — cookies, local storage, sessions — is encrypted with AES-256-GCM before being uploaded to the cloud. The encryption key is derived from your account credentials and is never sent to our servers in plain text.

Zero-Knowledge Architecture

MeetLogin servers store only encrypted blobs. We cannot decrypt or read your profile data. Even in the event of a server breach, your data remains protected.

Transport Security

All API communication uses TLS 1.3. Proxy credentials are encrypted in the database with AES-256-GCM using a server-side key. API keys and JWT tokens are hashed before storage.

Two-Factor Authentication

Enable TOTP-based 2FA in Settings → Security to add a second layer of protection to your account. Even if your password is compromised, an attacker cannot log in without your authenticator app code.

Session Security

Sessions are stored in Redis with a 7-day TTL. Logging out immediately invalidates the session token. You can revoke all active sessions from Settings → Security.