Security and compliance at zeeform

Protection proportional to what these documents hold

Last updated: August 2026

Protection proportional to what these documents hold

Employment paperwork, medical consent and legal agreements carry sensitive personal data, sometimes national ID numbers, bank details and health information. Every product decision starts with how that data is kept.

What's protected, and how

Protection is layered: end-to-end encryption, role-based access control and environment separation. What's listed here is what runs today, no claims about certification still in progress.

What's in place today

The layers active on every account:

Full encryption, TLS 1.3 in transit and AES-256 at rest, backups included.
A complete audit trail, every view, entry and signature recorded with timestamp and IP, and not editable.
Role-based access and two-factor authentication, separating who builds, who sends and who sees the data.

The database and the app run on servers in Israel; documents are stored encrypted on Cloudflare R2. Formal certification (ISO 27001, SOC 2) is in progress and not currently held, we won't display a badge we don't have.

Transparency

We prefer to state plainly what exists and what doesn't. Israeli law recognises three levels of electronic signature; zeeform operates at the secure level. A certified signature requires a licensed Certification Authority, that integration is planned and not currently available.

Where data is stored

The database and the app run on servers in Israel; documents are stored encrypted on Cloudflare R2, with encrypted backups and continuous monitoring.