Trust Centre
Where your data lives
Every service we rely on, plotted by where it physically processes your data. Almost all run inside the EU. Two run in the United States under EU Standard Contractual Clauses: OpenAI, which processes prompts with zero data retention and receives only the limited context needed for AI responses, and hCaptcha, which only checks for bots on the sign-up and login pages and never sees your project data.
Hosting, database & auth (Germany)
Content delivery network
Payment processing & billing
Product analytics
Knowledge base, changelog & feedback
Transactional & product email
AI assistant processing
Bot protection at sign-up & login
All sub-processors are bound by Data Processing Agreements. The current list is published at vaizy.com/subprocessors and mirrored in our DPA. See the full sub-processor list
How your data is protected
Concrete measures, not slogans. Each one is enforced today and documented in our Privacy Policy.
The AI never sees sensitive data
AI requests pass through a server-side gateway that minimises and masks sensitive context before model processing. Client code never calls the AI provider directly.
About Vaizy AIEncrypted, always
TLS 1.2+ on everything in transit. Stored data and backups are encrypted at rest.
You see only your own data
Row Level Security is enforced on every database table, and role-based access controls govern what each member can do.
Sign in with a second factor
Authentication runs on Supabase Auth with multi-factor (TOTP) support, so a password alone is not enough.
Your identity provider stays in charge
Enterprise workspaces can sign in through SAML single sign-on, create and remove users automatically with SCIM, and require MFA for everyone. The security center shows each member's MFA status, active sessions and recent sign-ins, and can sign a session out.
AI apps get your access, nothing more
An AI app you connect acts as you, in one workspace, with exactly your access. You approve each app and can disconnect it any time. Nothing can be deleted through a connector, team members' email addresses are never shared, and connectors stay off until a workspace owner or admin turns them on.
About Vaizy MCPSecrets stay on the server
API keys and provider credentials live in server-managed secrets. They are never shipped to the browser.
Hardened in production
Production builds and database access paths are reviewed and hardened to reduce accidental exposure and common misconfiguration risks.
Browser-level defences
HSTS, X-Frame-Options DENY, a strict Content Security Policy, and a locked-down permissions policy ship with every page.
EU AI Act transparency
AI features are labelled wherever they appear, a person stays in charge of every decision, and the assistant is never used for decisions with legal or similarly significant effects on a person, consistent with the EU AI Act (Regulation (EU) 2024/1689).
A searchable audit log
Pro plans and above get a searchable, filterable audit log covering key workspace and project events, including actions performed on the server such as ownership transfers, member invites and removals, sharing changes, and billing actions. Filter by actor, date range, and project, and export to CSV. Email addresses, raw identifiers, and other personal data are masked before display or export.
If something goes wrong
No system is risk-free, and we will not pretend otherwise. If a breach affects your data, we notify you and the Dutch supervisory authority (Autoriteit Persoonsgegevens) without undue delay, and within 72 hours of becoming aware, as GDPR requires.
What we don't claim yet
We don't hold SOC 2 or ISO 27001 certification today. We'd rather tell you that than imply a badge we haven't earned. Our security posture is built on GDPR compliance, EU data residency, and the measures above. Formal certification is on our roadmap as we grow.
Read the fine print
Every claim on this page is backed by our legal documents. Read them in full, or ask us anything.