Zoolki is designed to respect your privacy by default. We process data locally whenever possible and never store your form inputs on our servers.
Last updated: February 21, 2026
Security isn't an afterthought; it's the core architecture. When you use Zoolki, you are inviting a guest into your browser, and we respect that boundary.
Your text data stays on your machine during the initial parsing phase.
Once you close the browser tab, any temporary data cached for that session is wiped instantly.
Transparency in how we move bits and bytes.
You paste text into the extension sidebar. This action is manual and triggered only by you.
The text is analyzed to identify entities using local logic and transient secure API calls for complex structures.
Data is mapped to the fields. No data leaves this loop to be stored in a database.
We do not persist your personal data. User accounts only store subscription status and custom mapping rules you explicitly save. The actual content you paste is treated as volatile memory and is discarded immediately after processing.
Any communication between the extension and our servers happens over HTTPS with TLS 1.3 encryption. Internal mapping tokens are hashed. We employ industry-standard practices to ensure your data stays secure.
We collect the absolute minimum required to function. We don't track your browsing history, we don't look at other tabs, and we don't build a profile of your behavior.
While Zoolki is secure, we advise users not to process highly sensitive data like credit card numbers or passwords. The tool is optimized for professional and biographical data.
We operate a responsible disclosure program. If you believe you've found a vulnerability in Zoolki, please let us know immediately.
bug_reportReport a Vulnerability