Security
How Email Finder Verifier protects the service, your account and your API keys, and how to report a security issue.
How we protect the service
- Encrypted in transit. All traffic runs over TLS. TLS is transport layer security. It scrambles data as it travels so others can't read it.
- API keys are stored hashed. Hashed means scrambled so nobody can read it back. We can't read your full key after you create it. That's why the dashboard shows it only once.
- Limited production access. Production servers are the live ones that run the service. Only named people can reach them. They use key-based authentication (a long secret file instead of a password).
- Sign-in by Clerk. Clerk is a company that handles sign-in and account security for us. That includes Google sign-in.
- Cloudflare in front. Cloudflare is a company that serves and protects websites. It serves and protects our site.
- Servers in Germany and Finland. Hetzner and Contabo host them. Both are companies that rent out servers.
How you can protect your account
- Make one API key (a secret password for your tools) for each tool. Then a leak only affects one tool.
- Call the API from a server or a workflow tool. Never call it from a web page or a mobile app.
- Delete a key the moment you think it leaked. Then create a new one.
If something goes wrong
If a breach (a case where data is exposed) affects your data, we will tell you without undue delay, and within seventy two hours of confirming it. We also tell the right regulator where the law requires us to.
Report a security issue
Email kaushik@up.one with the details. Please give us a chance to fix it before you share it in public.
Words you don't know? See the Glossary.
Last updated 16 November 2026