Your data is sensitive. We treat it that way. See our features for privacy controls.
Last updated: March 26, 2026
Four principles guide every decision we make about your data.
Built in from day one, not bolted on after.
Access only what's needed, nothing more.
Multiple layers, not single points of failure.
We tell you what we do and how.
Multiple layers of protection keep your information safe at every stage.
All data encrypted via TLS 1.3.
Infrastructure-level encryption (AWS). Field-level encryption via Supabase Vault for sensitive data.
Sensitive data stored separately, never exposed to AI.
Highest sensitivity data lives in Supabase Vault.
Your data is yours. Complete workspace separation.
Whether you need GDPR, HIPAA, or SOC 2 compliance, ioZen has you covered.
Privacy by design, data subject rights, DPA available, jurisdiction-specific disclosures. Working toward full compliance.
Private and encrypted fields available for handling sensitive health data. BAA and full certification planned.
Built on SOC 2 Type II certified infrastructure (Supabase, Vercel, Cloudflare). Platform-level audit planned.
Do Not Sell policy, data access and deletion supported. Working toward full compliance.
Need a BAA or specific compliance documentation? Contact [email protected]
Every layer of our stack is backed by providers with proven security track records.
| Layer | Provider | Certification |
|---|---|---|
| Database | Supabase (PostgreSQL) | SOC 2 Type II |
| Authentication | Supabase Auth | SOC 2 Type II |
| Storage | Supabase Storage | SOC 2 Type II |
| Application & AI | Vercel (Hosting, AI Gateway, Blob Storage) | SOC 2 Type II |
| CDN | Cloudflare | SOC 2 Type II, ISO 27001 |
March 2026 and later releases ship the controls below.
Credits reset per billing period in one atomic operation. Concurrent requests cannot double-reset usage.
The public credit status endpoint is rate limited to reduce automated scraping and enumeration.
Unauthenticated requests do not receive exact credit counts or full plan details.
IDs are validated with Zod and CUID rules. Malformed input is rejected before it reaches the database.
A submission stays bound to the IntakeBot that received it. Another bot cannot update it.
Validation error responses do not expose internal schema structure.
Permissions-Policy and iframe allow attributes define how geolocation works in embedded, cross-origin contexts.
For every field in your FlowApp, you decide how it's stored and whether AI can access it.
AI access
Full
Storage
Normal database
Best for
Most fields
AI access
Never
Storage
Separate table
Best for
PII, sensitive info
AI access
Never
Storage
Encrypted vault
Best for
SSN, medical, financial
Our architecture supports HIPAA requirements through private and encrypted fields. Contact us to discuss your specific compliance needs and BAA arrangements.
Data is stored in Supabase's infrastructure (AWS, US regions by default). Contact us if you have specific region requirements.
No. Private fields are never sent to AI models. AI requests are routed through Vercel AI Gateway to providers like OpenAI, Anthropic, Google, and xAI, but only for fields you choose. You control which fields use AI and which stay completely isolated.
Yes. Full data deletion is available at any time. Contact support for workspace-level deletion.
No. Never. Your data is yours. Period.
Our team is here to help with security reviews, compliance documentation, and BAA requests.
