How Ziqme protects your data
One multi-tenant platform, one security model. This page describes what is actually in place today, who processes your data, and what is still in progress.
Architecture and tenant isolation
Every Ziqme product runs on the same microservice platform behind a single authenticated gateway, so isolation is a property of the platform rather than something each feature has to remember.
Infrastructure
Services run in isolated containers behind a hardened gateway with rate limiting, TLS termination, and centralized authentication.
Data protection
Every record is scoped to your workspace. Multi-tenant isolation is enforced at the database layer, with encrypted backups.
Access control
Role-based access control, OAuth2 for machine access, and JWT-based sessions across every product.
Compliance
GDPR tooling for export, deletion, and consent. EU hosting available.
How isolation actually works
Three independent mechanisms, so a mistake in one place does not expose another workspace.
- Per-service schema isolation
- Each service owns its own database schema and reads only the data it is responsible for. There is no shared table that every service can write to.
- Tenant-scoped queries
- Every record carries the workspace it belongs to. Data access filters on that workspace in the query itself, and a global filter is applied on top as a second line of defence.
- One identity model
- Authentication is centralised: short-lived tokens issued by the auth service, role-based permissions, and separate machine credentials for service-to-service calls.
Where your data lives
We would rather name the providers involved than imply that we run every layer ourselves.
EU hosting
The platform runs on European infrastructure and production databases stay in the EU. Attachments and exports are kept in EU object storage.
Encryption in transit
All public traffic is served over TLS. Service-to-service calls stay on the internal cluster network and are authenticated.
Backups and deletion
Databases are backed up on a schedule and backups are stored encrypted at rest. Deleted records are soft-deleted first, so an accidental deletion is recoverable inside the retention window.
Subprocessors
These third parties can process customer data on our behalf. The list changes as the platform evolves, so ask us for the current version before you sign.
| Provider | Purpose | Processing location |
|---|---|---|
| Contabo | Compute, the Kubernetes cluster and the production databases | Germany (EU) |
| Amazon Web Services | Object storage for attachments, exports and backups | EU region |
| Cloudflare | DNS, CDN, TLS termination and bot protection | Global edge network |
| Stripe | Subscription billing and payment processing | EU and US |
| OpenAI | AI replies, summaries and knowledge-base answers, only when AI features are switched on | US |
| Twilio | Telephony for Ziqme Voice, unless you connect your own carrier | EU and US |
AI features are opt-in per workspace. If you leave them off, no conversation content is sent to a model provider. Ziqme Voice can run entirely against your own PBX and carrier.
Compliance posture
We would rather be useful than impressive, so here is exactly where we stand.
GDPR tooling is in place
Export and erasure requests can be fulfilled from the product, consent is recorded for the public forms and widgets, and hosting is in the EU.
No SOC 2 or ISO 27001 today
We hold no third-party security certification and we will not imply one. If your procurement process requires an audited report, we are not the right fit yet, and we will tell you so.
In progress
Formalising internal policies, access reviews, logging and evidence collection is ongoing work. We will publish a certification only once an auditor has issued it.
Data processing agreement
We sign a DPA, with standard contractual clauses where a transfer requires them. Ask us and we will send the current version together with the subprocessor list above.
Responsible disclosure
Found something? Tell us directly and we will work through it with you.
Send security reports to security@ziqme.com
What to expect
We acknowledge reports within three working days, keep you updated while we investigate, and credit you when the fix ships if you would like to be named.
Scope and ground rules
Please test only against your own workspace or a trial workspace. Do not run automated scans against production, access another customer data, or degrade the service for anyone else.
Still have security questions?
Send us the specifics — architecture, data flows, or your vendor questionnaire — and you will get a direct answer from someone who works on the platform.
Talk to us