Security
Anonymity only means something if the data behind it is protected. Here's how WhisperLink handles security.
Encrypted connections
Everything you send and receive on WhisperLink travels over an encrypted HTTPS connection, so messages can't be read in transit.
Strict database rules
Messages live in a managed cloud database protected by row-level access rules: the app only reads or writes messages through the narrow paths it defines, and background systems use least-privilege access.
No passwords to leak
There are no accounts and no passwords. Your inbox is identified by your username, and your session lives only in your own browser — there's no password database for anyone to steal.
Anonymous by design
Senders give no name, email or phone number, and we don't log their IP addresses or email addresses. The only sender clues we store are a country and a device/browser type, and those stay locked until the inbox owner pays for them.
Payment security
The R35 hint unlock is processed entirely by Paystack, a PCI-DSS compliant payment provider. Card details never touch WhisperLink's servers — we only see the payment result.
Abuse prevention
Every message is validated on the server: length limits are enforced server-side, usernames follow a strict format, and payment results are verified against the payment provider before a hint unlocks.
Report a vulnerability
Found something we should know about? Contact the WhisperLink team with the details and we'll investigate and fix it as a priority.
Last updated 29 October 2026 · WhisperLink