Privacy Policy
Version v0.6 · Last updated: 20 August 2026
Contents12 sections
- 1. Who we are
- 2. Sign in with Facebook & Google (for shoppers)
- 3. Data we process about merchants
- 4. Purposes and legal bases (GDPR Art. 6)
- 5. Recipients
- 6. International transfers
- 7. Retention
- 8. Whether data is required, and automated decision-making
- 9. Your rights
- 10. Cookies
- 11. Customer testimonials and references
- 12. Changes
ZweiHost is a Website-as-a-Service (WaaS) platform: small businesses run online shops and sites on our infrastructure. This Policy describes how ZweiHost processes personal data of two groups: shoppers who sign in with Facebook or Google on a shop built with ZweiHost (section 2), and our direct customers - the merchants (sections 3 onwards).
1. Who we are
The ZweiHost platform is operated by Zwei Soft Ltd. („Цвай Софт" ЕООД), the company that acts as data controller for the personal data described in this Policy.
Zwei Soft Ltd. (operator of the ZweiHost platform)
Registered seat: 2 Asenovgradsko shose St., entr. E, apt. 52, Plovdiv 4004, Bulgaria
UIC (ЕИК): 208515196 · VAT: BG208515196 · Manager: Ivaylo Ivov Ivanov
Contact: support@zweisoft.com
2. Sign in with Facebook & Google (for shoppers)
Some shops built with ZweiHost let shoppers sign in with Facebook or Google. ZweiHost operates a single, central sign-in integration on behalf of all those shops - which is why the Facebook and Google consent screens show the name “ZweiHost”.
When you choose “Continue with Facebook” or “Continue with Google”, we receive from the provider only:
- your name;
- your email address;
- and a stable provider user identifier (your Facebook/Google user ID).
We use this data solely to create or sign you in to your customer account on the specific shop where you used the button. We do not receive your password, your friends/contacts, your posts, or any other profile data, and we do not post anything on your behalf.
Your account (together with the data above) is stored separately for each shop you sign in to: the shop is the controller of that account, and ZweiHost acts as its processor. We keep it for as long as your account on that shop exists, and you can delete it at any time - see Data deletion. Questions about social login: support@zweisoft.com.
3. Data we process about merchants
- Account data: email, name, phone.
- Business data: legal entity name, EIK, address.
- Payment data: handled by Stripe - we only receive an identifier and status, never card numbers.
- Usage data: login logs, IP, browser, BackOffice actions.
- Communications: emails and support messages.
Newsletter subscribers (zweihost.com visitors): if you subscribe to our newsletter, we process your email address and the site language on the basis of your consent, to send you news, articles and advice on selling online. Tsvai Soft Ltd is the controller of this data; delivery is via Amazon SES (see section 5). You can unsubscribe at any time with one click from any email.
4. Purposes and legal bases (GDPR Art. 6)
| Purpose | Basis |
|---|---|
| Service delivery (incl. shopper sign-in) | Contract (Art. 6(1)(b)) |
| Invoicing and accounting | Legal obligation (c) |
| Security and abuse prevention | Legitimate interest (f) |
| Marketing newsletter | Consent (a) |
| Customer testimonials and references (section 11) | Consent (a) |
| Honouring an unsubscribe (suppression record) | Legitimate interest (f) |
5. Recipients
- Stripe (payments) - Ireland / USA (SCC).
- Cloudflare (R2 file storage, Workers hosting and CDN, traffic protection and IP addresses; inbound email forwarding for shops that enable business email forwarding - email content passes through in transit only, no storage on our side; in shops that have authorised ZwAI - the Browser Run browser service, which opens the site draft and takes its screenshots, without keeping them after the request, and loads permitted reference sites only to extract design signals, with no screenshot) - EU / global edge.
- Amazon Web Services (Amazon SES) (email) - EU (eu-central-1) / USA (SCC).
- Railway (API, admin panel and PostgreSQL database) - EU West (Amsterdam, Netherlands).
- Functional Software, Inc. (Sentry) (error tracking and diagnostics - technical error data only; request bodies, cookies, credentials and user identifiers are stripped before sending) - EU (Germany) / USA (SCC).
- Anthropic Ireland, Limited (Claude) (ZwAI and Anthropic). ZwAI is an AI assistant in the admin panel. It uses Claude through Anthropic Ireland, Limited. Until the assessment of the international transfer of personal data to Anthropic is complete, ZwAI works only in a limited "site-only" mode and is switched on for a particular shop only after three separate ticks on the merchant's behalf: acceptance of the Data Processing Agreement, authorisation for Anthropic to be used as a sub-processor, and confirmation of the list of permitted operations and fields. ZwAI has no access to the shop's customer data: orders, customer accounts and addresses, bookings, newsletter subscribers, contact-form messages, reviews, returns and invoices. Only the permitted operations and fields in Annex 3 to the Agreement are sent to Anthropic: staff messages and catalogue texts (checked for email addresses, phone numbers, IBANs, card numbers, ЕГН, Bulgarian street addresses and order numbers, but not for names), design data (including the logo and favicon) and the theme code, the shop's settings read only (SEO, languages, currency, delivery prices), masked screenshots of the draft, and, as they are, the product's first photo and the shop's own domain with reference sites. Personal data in them, for example a person in a photo or a name in the domain or the text, is transferred to Anthropic under the merchant's authorisation. Before a screenshot of the shop's own draft is sent, images are blurred and recognised names, phone numbers and email addresses are replaced; if the masking is not confirmed, no screenshot is sent. Cloudflare processes the unmasked page when it opens it. For the data processed on the shop's behalf, the shop is the controller and Zwei Soft Ltd. the processor. The periods for conversations, plans, work records and screenshots are set out in the ZwAI annex to the Data Processing Agreement. Ending the authorisation stops new transfers and triggers the agreed return or deletion procedure. Under Anthropic's terms, read on 6 November 2026, Anthropic does not use this data to train models and deletes it within 30 days of receipt, except data flagged as a violation of its usage policy (up to 2 years) and data the law requires to be kept. The data is stored and processed in the USA; the transfers rely on the European Commission's standard contractual clauses (Modules 2 and 3) incorporated in Anthropic's DPA. Our assessment of the transfer, including onward recipients, is not complete: it needs written information from Anthropic that has not yet been received; until then ZwAI works only in the limited mode described. Until 7 October 2026 the shop assistant on storefronts and the help assistant in the BackOffice were also available; they are no longer offered, and our records show no completed conversation with them.
- Meta Platforms and Google LLC - for Facebook/Google sign-in and, with consent, advertising/analytics; they act as independent controllers under their own policies - USA (EU–US Data Privacy Framework).
- Borica AD - card payments for Bulgarian merchants, once activated.
- Government bodies where legally required.
6. International transfers
Where data is transferred outside the European Economic Area (EEA), we use an applicable GDPR mechanism: an adequacy decision, the European Commission's Standard Contractual Clauses, or another mechanism permitted under Art. 46 GDPR. Information on the specific safeguards can be requested at support@zweisoft.com, to the extent that providing it does not breach trade secrecy or the security of the service.
7. Retention
- Shopper account (incl. Facebook/Google sign-in data): for as long as the account exists on that shop.
- Custom-print uploads (a photo or image you upload to personalise a product): if you never place the order, the file is deleted after 7 days. If you do order, the shop needs it to produce your item, and it is deleted 90 days after the order. A small preview of your finished design and its text description are kept with the order so your order history and the shop's records stay complete.
- Support messages (storefront chat): the email you give in order to message a shop, your name if you add it, and the content of the conversation - including a snapshot of any preceding chat with the shop's assistant. The shop is the controller of these messages and ZweiHost acts as its processor; the basis is responding to your enquiry (Art. 6(1)(b)/(f)) - no marketing and no separate consent. A conversation is deleted 30 days after its last message; the customer record it is attached to is kept under the account rule above.
- Marketing-recipient record, created when you subscribe to a newsletter or otherwise give marketing consent: it holds only your email address (and your name, if you gave one). If you withdraw consent and that record has no orders and no registered account attached, it is deleted. If it has orders or a registration, the record is kept and the marketing consent is marked as withdrawn.
- After you unsubscribe we keep a minimal suppression record (your email address and the fact that you unsubscribed) so that we do not send you marketing again. Legal basis: legitimate interest (Art. 6(1)(f)) - specifically, honouring your opt-out.
- Merchant account data: until contract termination + 30 days.
- ZwAI data (the AI assistant in the BackOffice, in shops that have authorised it): the shop is the controller and ZweiHost acts as its processor. A conversation is deleted by the hourly clean-up, at the latest one hour after 30 days from its last message have passed, or earlier if the user deletes it. A plan or proposal is deleted at the latest one hour after 30 days from when it was applied (if never applied, from when it was created), together with the two screenshots of the draft attached to it. The work record of a "Създай сайта ми" (Build my site) run is cleared when the run ends. No screenshot is taken of a reference site, and the extracted style characteristics are not kept as a separate set after that turn. The two screenshots are visible in the interface only to their author, which does not exclude the necessary technical access. When the authorisation for ZwAI is withdrawn, new requests stop, and if deletion is chosen, the conversations, descriptions, plans, screenshots and work records are deleted without undue delay. When a shop asks to close its account and the request is not withdrawn within the contractual 30-day period, ZwAI's conversations, descriptions, plans, proposals, screenshots and runs are deleted from the active database at the final closure. Before the irreversible erasure, the agreed choice of return or deletion is offered. Only the accounting and tax records required for AI spend, budget movements and payments are kept separately, without message content, for the applicable legal periods. Unneeded links to staff members are removed. The proof of the authorisation is kept separately for the stated internal period. Backups and data at external providers are handled separately. Individual rights requests are handled without undue delay and are not automatically subject to the period for withdrawing the closure.
- Deleted images (a product photo, a team member's photo or any other image a shop removes): kept in a recycle bin for up to 30 days so that a mistaken deletion can be undone, then deleted permanently. The recycle bin is a recoverable removal, not a final erasure: when someone asks for an image of them to be erased, the shop can erase it at once, together with its recycle-bin copy, its resized copies and its cached copies.
- Accounting documents: 10 years (Bulgarian Accounting Act).
- Invoices and sales documents of a shop that is deleted from the platform: before the deletion the shop gets a full electronic export by a link that works for 30 days; on the shop's instruction a copy is also kept apart from all other data for 10 years from the end of the year of issue, then deleted.
- Security logs: 12 months.
- Email delivery records (whether an email from a shop or from us was delivered, bounced or marked as spam, with the recipient's address): deleted after 90 days. A complaint or a permanent bounce also adds the address to the minimal suppression record described above, so that it is not mailed again.
- Shopper activity log (sign-ins and page views of a signed-in shopper, with the language and the type of device): after 90 days the link to the shopper is removed. What remains names no one and only feeds the shop's visit statistics.
- Records of data requests (that an access or erasure request was received, when, and when and how it was answered): kept for 2 years after the request was answered, as proof that it was handled, then deleted. They do not contain the data that was erased.
- Operational request logs - technical records of the requests to and from our API, kept for security, debugging and abuse prevention. Personal data in them is masked and credentials are removed before anything is written; they are retained only for our hosting provider's (Railway) log-retention window and then rotated out automatically.
Site editor. The site editor keeps a shared draft and a publish history with the values before and after the change, the author and the time. Review requests contain the areas, a note of up to 500 characters, the sender and the person who closed the request. Access depends on the role in the shop.
The history and earlier theme versions are kept until the earlier limit: 12 months from creation, or dropping out of the newest 50. The current published version and the necessary working draft are not erased because of this limit alone. Entries outside the newest 50 are deleted at the next publication, and entries older than 12 months at the latest one day after they expire. A theme version that a kept history entry can restore stays while it is needed for that. Closed requests are deleted at the latest one day after 90 days from closing have passed.
When a user is deleted, their author identifier and the links to it are removed. This does not automatically anonymise the historical content: names and other personal data may be inside the values or notes themselves.
For the editing work the Merchant commissions, the Merchant is the controller and Zwei Soft Ltd. ("Цвай Софт" ЕООД), through ZweiHost, is the processor. ZweiHost's own purposes, if any, are described separately.
8. Whether data is required, and automated decision-making
Account, business, payment and technical-security data are necessary to conclude and perform the contract and to comply with legal obligations; if not provided, the service may be unavailable. ZweiHost does not use automated decision-making that produces legal effects or similarly significantly affects you, unless expressly stated in a separate module or policy.
9. Your rights
You may access, correct, delete, restrict, port, or object to processing, and withdraw consent, without affecting the lawfulness of processing before withdrawal. You have the right to complain to the Bulgarian Data Protection Authority (CPDP), 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, cpdp.bg.
Shoppers can export or delete their own data from their account on the relevant shop - see Data deletion. Merchants can do so from BackOffice → Settings → “Your data & privacy”. For anything else: support@zweisoft.com (we answer within one month of receiving your request; if a request is complex, this can be extended by two more months, and we tell you why within the first month). ZweiHost has not currently appointed a Data Protection Officer; this will be reviewed if the scale, risk or nature of processing changes.
10. Cookies
ZweiHost uses strictly necessary cookies and similar technologies (session, CSRF, language) needed to provide the service and for security. We do not place marketing or analytics cookies on zweihost.com without prior consent and an opt-out. Where an individual merchant's shop uses additional cookies, the merchant is responsible for its own notice and consent, unless ZweiHost expressly provides a central consent-management module. On a shop that has enabled storefront chat, a strictly-necessary cookie (about 180 days) remembers your open conversation so you can continue it on the same device; it carries no marketing or analytics data and needs no consent.
Measurement tools on zweihost.com. Only after your explicit consent via the cookie banner do we load:
- Google Analytics 4 (“statistics” category) - pages visited, referral source, approximate location from IP, device and browser type.
- Meta Pixel and the Meta Conversions API(“advertising” category) - pages visited and enquiry-form submissions. When you submit the form we additionally send Meta your cryptographically hashed (SHA-256) name and phone number from our server, so Meta can connect the enquiry to the ad you saw. Meta receives only the irreversibly hashed values, never the phone number or name itself.
- Google Ads (“advertising” category) - records a submitted form as a conversion from an ad campaign.
Legal basis: consent (GDPR Art. 6(1)(a)). If you decline, none of the above loads and no request is made to Google and Meta. Withdrawal: clear this site’s cookies in your browser - the banner reappears and you can choose again. Withdrawal takes effect going forward. Retention: your choice is stored for up to 12 months; retention at Google and Meta is governed by their own policies - for this data they act as independent controllers (see section 5).
Site editor. The following cookies are set only on the shop's preview host, when a staff member uses the site editor. All are HttpOnly and Secure. They are not used for advertising, analytics or tracking.
- __Host-zw_editor: Set when a staff member opens the site editor. Gives access to the draft preview. Valid for up to 15 minutes and renewed while the editor is open. Strictly necessary for the preview the staff member asked for.
- __Host-zw_editor_view: Remembers what the preview shows when it is not the whole draft: the chosen areas in a pre-publication review, or an earlier version from the history. Gives no access on its own. Period: 12 hours.
- __Host-zw_editor_card_state: Remembers which stock state (for example, sold out) the product card designer shows the products in, in the preview. Only in the preview. Gives no access on its own. Period: 12 hours.
The view and state cookies are created only when the matching feature is used and serve only its preview. They give no access on their own and are read only beside a valid access cookie.
11. Customer testimonials and references
With the merchant's explicit written consent we publish customer testimonials on zweihost.com (the landing page and the “Reviews” page): the shop's trade name, its business category, a link to the shop, the testimonial text, a screenshot of the storefront and, where provided, a logo; if the testimonial is personally signed, the person's name as well. Only where the merchant has separately ticked this in the consent form may the same content also be used on ZweiHost's social media profiles and in our advertising.
Legal basis: consent (GDPR Art. 6(1)(a)); the final wording of the testimonial is agreed with the merchant before publication. Retention: the publication stays up until consent is withdrawn or our relationship ends. Withdrawal: at any time, free of charge, at support@zweisoft.com - we take the testimonial down from the site and our social profiles without undue delay (within 14 days) and stop including it in new advertising; ad impressions already served cannot be recalled retroactively. Withdrawal does not affect the lawfulness of publication before it.
12. Changes
Changes are posted on this page and take effect 14 days after publication.