Security

Encryption in transit and at rest

All traffic to and from Surveyee is encrypted with TLS. Survey and response data is encrypted at rest.

Optional end-to-end encryption

Any survey can turn on end-to-end encryption, free on every plan. When it's on, responses are encrypted in the respondent's browser (RSA-OAEP + AES-GCM) before they're sent — our servers only ever store ciphertext, and we have no technical ability to read encrypted response content. Because of this, encrypted surveys can't be exported as PDF or CSV; instead, you decrypt and view responses directly in the dashboard using your private key, with an option to export the decrypted set as JSON.

Anonymity and IP handling

Surveys created with Anonymous mode on — the default for new surveys — never have respondent IP addresses stored raw: they're hashed or dropped before being written to the database. If you own a survey created before this default was introduced, check its Privacy settings and confirm Anonymous mode is on if you want that protection applied going forward; it does not apply retroactively to responses already stored.

When we resolve a respondent's country for analytics, we use a local, self-hosted lookup that returns only a country code — never the raw IP address or a full geolocation.

Your data, on request

You can export or permanently delete your account data at any time from /account — both are real, self-service operations, not a support ticket you have to file. See our Privacy Policy for the full detail on your rights.

Reporting a vulnerability

If you believe you've found a security issue in Surveyee, please email help@surveyee.com with details and, if possible, steps to reproduce. We don't currently run a paid bug-bounty program, but we take every report seriously and will respond directly. Please report responsibly and don't test against other users' data — see our Fair Use Policy on authorized security testing.