How we protect your shopand your customers’ data.
No badges for show. Below is exactly what we do, where the data lives and what we have committed to in writing in the data processing agreement, naming every sub-processor.
GDPR tools
Export and erasure of a customer’s data from the admin panel. Self-service for customers: from Business.
Data in the EU
The shop and the database are in the EU. Transfers outside the EEA run under the Commission’s clauses or an adequacy decision.
Encrypted traffic
TLS everywhere. Passwords are kept hashed and keys encrypted.
Cards never pass through us
The payment goes straight to Stripe or Borica.
Free SSL
Included and renewed on its own, for every domain.
Copies at two providers
A daily copy of the database and a weekly one at a second provider.
GDPR and your customers’ rights
You are the controller of the personal data in your shop, and ZweiHost is your processor. That is not just wording: it is set out in the Data Processing Agreement, which is published and which you can read before you pay rather than on request afterwards.
Tools for your customers’ rights
Data-subject tooling is built in: export of a customer’s data and Article 17 erasure, with an audit record and a grace period.
A request queue
Deletion requests land in a BackOffice queue so you can action them in time. Orders are not deleted but anonymised, so your accounting record stays complete.
Four public documents
Privacy Policy, Terms, DPA and a data-deletion page: all four are public and bilingual.
Breach notification
On a personal-data breach we notify you without undue delay after becoming aware. You also hold an audit right, annually, or upon an incident.
Where the data lives
Your shop, the admin panel and the database are hosted in the European Union: Railway, EU West region (Amsterdam, the Netherlands). Files and the storefront run through Cloudflare (R2 and Workers). We are specific here because "data in the EU" is easy to write and hard to prove.
- Shop, admin panel and databaseRailway, EU West region (Amsterdam)EU
- Files and storefrontCloudflare (R2 and Workers)See the Policy
- PaymentsStripeAlso outside the EEA
- Email deliveryAmazon SESAlso outside the EEA
- Error diagnosticsSentry, technical data onlyAlso outside the EEA
Transfers outside the EEA
Some sub-processors also process data outside the EEA: Stripe (payments), Amazon SES (email delivery) and Sentry (error diagnostics). Those transfers run under the European Commission’s Standard Contractual Clauses or an adequacy decision. We do not claim data never leaves the EU, because that would not be true.
Sentry receives technical data only
Sentry receives technical error data only: request bodies, cookies, credentials and user identifiers are stripped before anything leaves the server.
A change of sub-processor
The full sub-processor list and their locations are in the Privacy Policy. When one changes we notify you at least 30 days in advance, immediately in the case of an urgent security measure.
Meta and Google
Meta and Google are not our sub-processors. For Facebook or Google sign-in they act as independent controllers under their own policies.
Encryption, access and isolation
All traffic runs over TLS, and every shop is isolated at the database level. ZweiHost is a multi-tenant platform: every merchant-scoped table carries a tenant_id and every query filters on it: isolation is a property of the schema, not of good intentions.
Passwords and secrets
Passwords are stored hashed, never in readable form. Sensitive secrets (courier, payment and email provider keys) are kept encrypted.
Two-factor sign-in
Two-factor authentication (TOTP): mandatory for platform administrators and available to shop owners. Sessions can be revoked all at once on suspicion of compromise.
Roles in the admin panel
Role-based access in the BackOffice: your team sees only what its role allows. Access is controlled and logged.
Tracing without secrets
Every API request carries a correlation id, so a single failed checkout can be traced end to end, without secrets or full customer records being written to the log.
Payments and your certificate
Card details never pass through our servers. A card payment happens at Stripe or Borica, on their own hosted forms: we receive the outcome of the payment, not the card number. It therefore cannot leak from us: we do not store it.
Cash on delivery
Cash on delivery is collected by the courier and reconciled against orders, with no card details entered anywhere.
Free SSL
Every shop gets a free SSL certificate for its domain, renewed automatically. No add-on fee, and no renewal reminder in your calendar.
HTTPS and security headers
The storefront is served over HTTPS only, with HSTS and security headers against framing by another site and content-type sniffing.
Backups and continuity
The database is backed up daily by the managed service, and separately we take a weekly copy at a different provider (Cloudflare R2). That second copy exists precisely for the case where the problem is at the first provider.
- DailyThe managed database takes a copy every day
- WeeklyA separate copy at a different provider (Cloudflare R2)
Automatic restart
Services carry a health check and restart automatically on failure, rather than sitting in a broken state.
On termination
On termination we return or delete the personal data (your choice), except where EU or Bulgarian law requires it to be retained.
Start with the plan you need.
30 days free, no card. Change plans later and your data stays.
Solo
€19€16/mo excl. VATexcl. VAT · €19.20 incl. VAT€19.20/mo incl. VAT
Your first shop: catalogue, cash on delivery, newsletter and your own domain.
Pro
€39€34/mo excl. VATexcl. VAT · €40.80 incl. VAT€40.80/mo incl. VAT
Econt and Speedy, customer accounts, promo codes and Meta CAPI.
BusinessPopular
€59€49/mo excl. VATexcl. VAT · €58.80 incl. VAT€58.80/mo incl. VAT
Card payments, all five couriers and automatic promotions.
Everything on this page is in every plan. GDPR self-service for customers (they download and delete their own data themselves) starts on Business.
- 30 days free
- No card
- No contract
- Prices with yearly billing; monthly €19 / €39 / €59 excl. VAT
Do you store bank card details?
No. We never see or record a card number. The payment happens on Stripe’s or Borica’s hosted form and we receive only the outcome: success or failure, and an amount. Card data therefore cannot leak from ZweiHost: it does not pass through us.
Is the online shop secure?
Yes. All traffic runs over TLS with a free, auto-renewing SSL certificate; each shop’s data is isolated by tenant_id at the database level; passwords are stored hashed, and access is role-based with two-factor authentication. Card details are not stored with us at all: the payment happens at Stripe or Borica.
Where is my shop’s data stored?
The database, the API and the admin panel are hosted in the European Union: Railway, EU West region (Amsterdam, the Netherlands). Files and the storefront run through Cloudflare. Some sub-processors (Stripe, Amazon SES, Sentry) also process data outside the EEA under Standard Contractual Clauses; the full list of locations is in the Privacy Policy.
How is GDPR compliance handled for an online shop?
You are the controller, we are the processor, and the relationship is governed by the published Data Processing Agreement. The platform carries the tooling: export and Article 17 erasure of a customer’s data with an audit record, a deletion-request queue in the BackOffice, anonymisation of orders rather than deletion (so accounting stays complete), a cookie banner and policies built into the shop.
Do you take backups, and what happens if I delete something?
The database is backed up daily by the managed service and weekly at a separate provider (Cloudflare R2), so it survives a provider-level problem too. If you delete something by mistake, write to us as soon as possible: recovery is from a point-in-time snapshot, so the sooner you tell us the less is lost.
Do you have ISO 27001 or SOC 2 certification?
No, and we do not pretend otherwise. ZweiHost is a small Bulgarian company and that certification is not yet within our reach. What we do have is a published DPA with specific technical and organisational measures, named sub-processors and a written commitment to notify you of a breach. Payments are handled by certified providers.