Data Processing Agreement (DPA)
Version v0.2 · Effective: 20 August 2026
Contents11 sections
- 1. Parties and roles
- 2. Subject-matter, nature, purpose and duration
- 3. Categories of data and subjects
- 4. ZweiHost obligations
- 5. Sub-processors and changes
- 6. International transfers
- 7. Liability
- 8. Precedence
- Annex 1. ZwAI
- Annex 2. Site editor and base themes
- Annex 3. ZwAI - limited "site-only" mode: permitted operations and fields
This Agreement is concluded between Zwei Soft Ltd., UIC 208515196, operator of the ZweiHost platform (hereinafter "ZweiHost"), and the Customer, and supplements the Terms of Service. It governs processing of personal data per Art. 28 GDPR. The previous version v0.2 (effective 20 August 2026) is archived.
1. Parties and roles
- Customer (Controller): the entity registered in ZweiHost whose legal name and UIC (EIK) are recorded on its account.
- ZweiHost (Processor): processes personal data on the Controller's instruction and only for the purpose of the service.
When the Customer's website collects data from its visitors (contact forms, bookings, newsletter, etc.), the Customer is the independent Controller and ZweiHost is the Processor.
2. Subject-matter, nature, purpose and duration
ZweiHost processes personal data on the Customer's behalf to provide, support, secure, host, deliver email for, store files/images for, fulfil orders for (including passing data, on the Customer's instruction, to the couriers it chose for delivery, cash on delivery and - when the courier issues the fiscal receipt in the Customer's name - that receipt), run customer accounts and Facebook/Google sign-in for, back up, and technically administer the Customer's online shop/site.
With a specific authorisation under section 5, ZweiHost provides ZwAI for answers and suggestions in the admin panel, work with the catalogue and the authorised design features: the free-text "Създай сайта ми" (Build my site) description, generating CSS and templates, preparing a design as a draft, visual checks through screenshots and analysis of permitted reference sites. The processing covers the necessary inputs, tool results, replies and temporary work records. Changes become public only after the Customer's "Publish" action. The retention periods for ZwAI data are in Annex 1 and take precedence over the general period below.
Processing runs for the subscription term plus 30 days after termination (error-recovery window), after which the Customer's data is deleted or anonymised, unless applicable law requires longer retention or the Customer has opted to have the data returned in a reasonably maintained format before deletion. During the subscription, an image the Customer deletes is kept in a recycle bin for up to 30 days so that a mistaken deletion can be undone, and is then deleted permanently. Moving an image to the recycle bin is a recoverable removal, not a final erasure: on a data subject's erasure request the Customer can erase the image at once (BackOffice → Settings → "Your data & privacy"), together with its recycle-bin copy, its resized copies and its copies in the content delivery network's cache. Before the Customer's site is permanently deleted from the platform, ZweiHost sends its owners a full electronic export of the invoices and sales-registration documents the Customer issued through the platform, and of the receipt references recorded against its orders, with SHA-256 checksums to verify their authenticity and integrity; the download link works for 30 days. The duty to keep these documents remains the Customer's as their issuer. By accepting this agreement the Customer also instructs ZweiHost to keep a limited archive of the same documents for 10 years from the end of the year of issue: it is kept apart from all other data and used for no other purpose, a copy is given only to the identified former Customer or its duly established legal successor, or to a public authority where the law requires it, and it is deleted when that period ends.
3. Categories of data and subjects
- Visitors and shoppers on the Customer's site/shop: name, email, phone, delivery address, order history, favourite products, marketing consent, contact-form message content, booking time, technical logs, IP address and browser data necessary for the security and operation of the service; for Facebook/Google sign-in - name, email and a stable provider identifier; for product personalisation - shopper-uploaded images and text for printing, plus a small preview of the finished design and its description.
- End customers of the Customer: data per the services the Customer offers.
- The Customer's counterparties and staff (suppliers, customers, landlords, accountants, employees, etc.) named in documents the Customer attaches to its expense and income records: names, contact details, identifiers and amounts contained in the attached receipts, invoices, contracts and other documents.
- Representatives and staff who use ZwAI (only where authorised under section 5): account identifier, messages, descriptions, replies and their link to plans/proposals.
- Persons whose data is contained in the authorised ZwAI input material (only where authorised under section 5): names, contact details, images and other identifiers in the catalogue, free-text descriptions, content read by the tools, and screenshots of the Customer's own site or of a permitted third-party site.
This description of ZwAI data does not automatically authorise every use of the listed data: ZweiHost processes only what the authorised feature needs. Before a screenshot of the Customer's own draft is sent to Anthropic, images, video, frames and background images are blurred, and the recognised names of the team and of review authors, 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. The reference-sites feature is available in the limited "site-only" mode: Cloudflare Browser Run loads the given public page, and abstract style signals (palette, fonts, sizes, spacing, layout) are sent to Anthropic, with no text, images or code from the page, together with the shop's own domain as it is.
The Customer agrees not to upload special-category data (health, political, biometric) without explicit written agreement.
ZwAI is not intended for special categories of personal data or data relating to criminal convictions and offences. Such data is not entered or provided without prior written agreement on a specific permissible operation, the applicable legal basis and the measures. That agreement between the parties does not in itself create a legal basis.
4. ZweiHost obligations
ZweiHost will:
- process data only on the Customer's documented instructions, including as to third-country transfers, unless required to do so by Union or Member State law to which ZweiHost is subject; in that case ZweiHost informs the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
- immediately inform the Customer if, in ZweiHost's view, an instruction infringes the GDPR or other applicable data-protection law;
- ensure confidentiality of persons with access;
- apply appropriate technical and organisational security measures (encryption in transit, tenant_id isolation, encryption of sensitive secrets, password hashing, role-based access, backups, access control and logging);
- assist the Customer with data-subject requests and with security, breach notification, impact assessment and prior-consultation obligations, to the extent applicable. A data-subject request that reaches the Processor directly is forwarded to the Customer within one business day of receipt. The BackOffice records, for each request, the date it was received, its one-month deadline, any extension with its notice to the data subject, and the date it was answered;
- notify the Customer of a personal-data breach without undue delay after becoming aware;
- at the Customer's choice, return or delete the personal data after termination, unless EU or Member State law requires retention;
- provide the information necessary to demonstrate compliance with this DPA and allow audits. Ordinary periodic audits are organised up to once a year on reasonable notice. This does not limit an additional check needed to demonstrate compliance where there is a reasoned suspicion, a material change or a request from a competent authority. Audits run under conditions that do not endanger the security and confidentiality of other customers.
5. Sub-processors and changes
By accepting this Agreement the Customer grants general written authorisation for the use of the listed sub-processors within the scope described for each, except Anthropic Ireland, Limited for ZwAI, to which the separate specific authorisation below applies.
Under the general authorisation, ZweiHost notifies the Customer of any intended addition or replacement of a sub-processor at least 30 days before that sub-processor starts processing, and provides information that allows the Customer to object before the change. Where a shorter period is needed, ZweiHost and the Customer may agree a specific written authorisation before the inclusion.
In case of an urgent security risk, ZweiHost may take protective measures at once, including suspending the affected feature temporarily. Urgency does not permit transferring personal data to a sub-processor that has not been authorised.
ZweiHost imposes by contract on each sub-processor the same applicable data-protection obligations as in this Agreement and remains fully liable to the Customer for the performance of the sub-processor's obligations.
ZwAI - limited "site-only" mode
Until ZweiHost completes its assessment of the international transfer of personal data to Anthropic, ZwAI is offered only in a limited "site-only" mode: work on the site, the theme and the catalogue. ZwAI has no access to the shop's customer data: orders, customer accounts and addresses, bookings, newsletter subscribers, contact-form messages, reviews, returns, invoices and GDPR requests.
Before every request to Anthropic, including retries and fallbacks, the whole request is checked for email addresses, phone numbers, IBANs, card numbers, ЕГН (Bulgarian personal numbers), Bulgarian street addresses (recognised by markers such as "ул.", "бл.", "ж.к." or a postcode) and order numbers next to an order word ("поръчка", "заявка", "order" or "№"). On a match the request is blocked and not sent. The exception: the shop's address and its pick-up address saved in its settings pass only on an exact match (only whitespace, case and Unicode normalisation are ignored; no fuzzy matching). The match runs on ZweiHost's server; the saved addresses are never sent as a field of their own. Any other address is blocked. Names have no shape the check can recognise, and an address written without such markers may not be recognised either.
The permitted operations and fields are listed in Annex 3.
Sent as they are: the shop's own domain, when reference sites are used; the first photo of a product ZwAI works on; the free text staff type to ZwAI, and the catalogue texts. Screenshots of the draft are sent masked: every image is blurred, and phone numbers, email addresses and the names of the team and of review authors are replaced; any other name written in the site's text stays. Personal data in these materials, for example a person in a photo or a name in the domain or the text, is transferred to Anthropic under the Customer's authorisation, under the European Commission's standard contractual clauses (Modules 2 and 3) incorporated in Anthropic's DPA, and is processed in the USA (Annex 1).
ZwAI starts for a particular shop only after three separate ticks on the Customer's behalf: acceptance of this version of the Agreement; authorisation for Anthropic Ireland, Limited to be used as a sub-processor for ZwAI in the shop (Art. 28(2) GDPR), in the manner set out below; and confirmation of the list of permitted operations and fields (Annex 3). Acceptance of the Agreement alone does not switch ZwAI on.
ZwAI - specific written authorisation
The procedure below applies to the authorisation in the second tick. The full mode of ZwAI, beyond the operations and fields in Annex 3, is not yet active and will need a new specific authorisation.
Anthropic Ireland, Limited is used as a sub-processor for ZwAI only for a Customer and shop for which specific written authorisation has been given in advance on the Customer's behalf in the manner set out below.
Before the authorisation, ZweiHost provides the Customer with the applicable version of this Agreement and the ZwAI annex (Annex 1), including the authorised features, the categories of data and data subjects, the recipients, the retention periods and the information on international transfers and safeguards.
The authorisation is recorded as an electronic statement. ZweiHost keeps the exact text shown and accepted and its version, the Customer and the shop, the user account, the person's full name and stated capacity, the date and time and the moment of activation. The IP address and browser data are kept for evidence and security for a separately set and published period. A copy of the statement is sent to the Customer's contractual email address.
The person states that they are duly authorised to give the specific authorisation on the Customer's behalf and to accept the stated deviation from the notice period. ZweiHost does not check the registration and manner of representation in the Commercial Register in advance and does not require a power of attorney or a qualified electronic signature.
The statement and administrative access neither create nor in themselves prove the power of representation. Where there are indications that the authority is missing or insufficient, ZweiHost immediately stops new processing through ZwAI until the Customer duly confirms it in the applicable manner of representation and form. An express refusal to confirm is not treated as an authorisation.
With the specific authorisation, the parties expressly agree that the general 30-day notice does not apply to the inclusion of Anthropic described here. ZwAI may be activated as soon as the valid authorisation has been received and the applicable contractual, technical and international safeguards are in place.
Accepting the Agreement, listing Anthropic, or the absence of an objection does not activate ZwAI on its own. The authorisation does not cover restoring the earlier assistants, processing for model training or any other purpose not described.
A material extension of the authorised features, data or purposes requires updated information and a new specific written authorisation.
For sub-processors that ZweiHost chooses directly, the notice under this section applies.
The Customer gives general written authorisation for Anthropic's applicable onward sub-processors listed in the list provided when ZwAI is authorised. ZweiHost keeps a dated copy of that list and gives access to it and to the current public list. This authorisation does not cover independent controllers as sub-processors.
ZweiHost notifies the Customer without undue delay of a planned change it receives, including a replacement, stating the recipient, the operation, the planned date and the deadline for objecting. ZweiHost allows time for review and passes the objection on promptly. If the deadline or the information does not allow a real objection, the affected processing is suspended before the new recipient gets access. If an objection is not resolved, ZwAI is suspended for the Customer in the affected scope.
Withdrawal. The Customer may withdraw the specific authorisation at any time, through an authorised person in the admin panel or by written notice to ZweiHost. On receipt, new AI requests are blocked, scheduled operations are stopped and running executions are cancelled. A request already transmitted cannot be recalled retroactively.
When the AI service ends, the Customer chooses the return or the deletion of the personal data processed for it. If deletion is chosen, the conversations, descriptions, plans, screenshots and work records are deleted without undue delay. Retention in backups and separate logs is governed by the retention annex.
ZweiHost takes the necessary steps for deletion at Anthropic under the applicable contract and provides information on the specific exceptions and periods. The minimum proof of the authorisation and of its withdrawal is kept separately, on its own defined legal basis and for its own period.
Withdrawal does not automatically delete the catalogue, the orders or a design already published, which remain part of the core service.
Current sub-processors
- Cloudflare, Inc. - R2 object storage for files/images (EU), Workers hosting of the public shops, CDN and traffic protection (global edge, including visitors' IP addresses); inbound email forwarding for customer domains that enable business email forwarding (email content and correspondent addresses - in transit only, no storage on our side). Only where ZwAI is authorised - the Browser Run (Browser Rendering) browser service, which opens the Customer's draft and takes its screenshots, and loads permitted reference sites only to extract design signals, with no screenshot (Cloudflare's global network, no storage of the screenshot after the request).
- Stripe - payments - EU / USA (SCC).
- Amazon Web Services (Amazon SES) - email - EU (eu-central-1) / USA (SCC).
- Railway - hosting of the API, the admin panel and the main PostgreSQL database, including merchant and shopper data - EU West (Amsterdam, Netherlands).
- Functional Software, Inc. (Sentry) - application error tracking and diagnostics; receives technical error data only (message, stack trace, browser/environment type), with request bodies, cookies, credentials and user identifiers stripped before sending - EU (Germany) / USA (SCC).
- Anthropic Ireland, Limited (Claude) - only for ZwAI and only after the activation under section 5: AI processing of the messages, free-text descriptions, catalogue data, tool results and screenshots for the design features (Annex 1). Under its DPA Anthropic is a processor for this data and, under its commercial terms, does not use it to train models; periods and exceptions in Annex 1. Contracting party: Anthropic Ireland, Limited (for customers resident in the EEA). Storage and processing in the USA. EU data residency is not offered. Transfer mechanism outside the EEA - in Annex 1.
- Borica AD - card payments for Bulgarian merchants (planned, inactive as of this version).
Past use of Anthropic
Until 7 October 2026, two earlier assistants were available: the shop assistant on the storefront and the help assistant in the admin panel. A check of the production database found no recorded completed conversation with them; the table that records completed replies, used from the first day, is empty. This result does not in itself establish whether incomplete or failed requests were sent to Anthropic. Neither assistant is offered any more. This authorisation for ZwAI is not a retroactive authorisation.
Independent controllers and couriers
Meta Platforms and Google LLC are not sub-processors: for Facebook/Google sign-in and, with consent, advertising/analytics, they act as independent controllers under their own policies.
Couriers the Customer connects to its own accounts (e.g. Econt, Speedy) are not ZweiHost sub-processors: ZweiHost passes data to them on the Customer's instruction, under the contracts between the Customer and the courier. The courier's role towards the Customer (processor or independent controller) is settled between them; where the courier processes the data on the Customer's behalf, for example when it issues the fiscal receipt in the Customer's name, an Art. 28 GDPR agreement between the Customer and the courier is required.
6. International transfers
ZweiHost makes international transfers, including through onward processing or by giving access to recipients outside the European Economic Area (EEA), only on the Customer's documented instructions and in compliance with Chapter V GDPR.
For each applicable transfer chain, the recipients, countries and activities are identified, as is the specific mechanism: an applicable adequacy decision or appropriate safeguards, including standard data-protection clauses adopted by the European Commission, where applicable.
ZweiHost checks the contractual scope and the effectiveness of the safeguards and applies the supplementary technical and organisational measures the risk requires. If the necessary level of protection cannot be ensured, the transfer concerned does not start or is suspended.
On request, the Customer receives information on the applicable mechanism and a copy of or access to the relevant safeguards. Unrelated confidential information and details whose disclosure creates a specific security risk may be redacted, without preventing compliance from being demonstrated.
7. Liability
Liability towards data subjects is determined under Art. 82 GDPR. ZweiHost remains fully liable to the Customer for the performance of the obligations of its sub-processors under Art. 28(4) GDPR.
Between the parties, the consequences of unlawful data or instructions are determined by the proven infringement, the causal link and the applicable law. The Customer is not liable for acts of ZweiHost outside the Customer's lawful instructions or for ZweiHost's failure to perform its own obligations. This section does not limit the rights of data subjects or liability under Art. 82 GDPR. Liability for intent or gross negligence cannot be excluded or limited in advance.
8. Precedence
In case of conflict between this DPA and the Terms, this DPA prevails on data-processing matters.
The specific authorisation and the ZwAI annex form part of this Agreement. For the authorised AI scope, their special terms take precedence over the general clauses on notice and retention periods. They do not limit the mandatory requirements of the GDPR.
Annex 1. ZwAI
Applies only to a Customer and shop with a valid specific authorisation under section 5.
Features. Answers and suggestions in the admin panel; work with the catalogue; the free-text "Създай сайта ми" (Build my site) description; generating CSS and templates; preparing a design as a draft; visual checks through screenshots of the draft; analysis of permitted reference sites. Changes become public only after the Customer's "Publish".
Data and data subjects. The two ZwAI rows in section 3.
Recipients. Anthropic Ireland, Limited (AI processing); Cloudflare, Inc. (the Browser Run browser service, for the screenshots); Railway (storage of the records at ZweiHost). Details in the table in section 5.
Retention at ZweiHost.
- ZwAI conversation: deleted by the hourly clean-up, at the latest one hour after 30 days from the last message have passed; earlier on deletion or when the AI service ends.
- Description in a confirmed plan ("Build my site"): until the execution ends.
- Plan or proposal: at the latest one hour after 30 days from when it was applied have passed, or, if it is never applied, one hour after 30 days from its creation.
- Execution work record: description, content read by the tools, latest screenshots: while the execution runs; when it ends, including a failed, interrupted or stuck execution, it is replaced by an empty record in the same transaction.
- The two screenshots of the Customer's own draft - 375 and 1280 pixels: with the proposal, visible in the user interface only to its author; deleted with the proposal within 30 days.
- Style characteristics of a reference site: used for that turn; no screenshot is taken. ZweiHost does not keep the extracted characteristics as a separate set after the turn ends. The address given and ZwAI's reply are kept with the conversation until the conversation is deleted. The periods at Anthropic and Cloudflare are separate.
- Logs, backups and proof of the authorisation: separately defined periods; not covered by the periods above. The intended period for backups is up to 30 days from their creation; automatic deletion and actual compliance with this period are still to be confirmed.
Final closure of the shop. When the contractual 30-day period ends and the request has not been withdrawn, the ZwAI content is erased from the active database after the Customer has been given the choice of return or deletion. Copies are erased under a separately described and verified procedure. As an independent controller, ZweiHost keeps only the accounting and tax records the law requires and the separate minimal proof of the authorisation, on the stated grounds and for the stated periods. These exceptions do not include conversations, descriptions, proposals or screenshots.
A "Build my site" execution is expected to take about 30 minutes; this is not a hard maximum. An execution that does not end within its time limit is ended automatically and its work record is replaced by an empty record. Visibility only to the author refers to the user interface and does not exclude the necessary technical access of authorised ZweiHost personnel or processing by the sub-processors.
Retention at Anthropic. Under Anthropic's terms, inputs and outputs are deleted within 30 days of receipt or generation. They may be kept longer where they are flagged as a violation of Anthropic's usage policy (up to 2 years, and its classifier scores up to 7 years) and where the law requires them to be kept. Retention to enforce Anthropic's policies is the provider's own measure, not a legal retention requirement. Anthropic does not use the data to train models, except feedback the customer expressly gives it; ZweiHost sends no such feedback from ZwAI. On termination of the contract, Anthropic returns or deletes the data within 30 days, unless the law, a legal dispute or combating harmful use requires it to be kept. Anthropic notifies ZweiHost of a security breach without undue delay and in any event within 48 hours, and audits of Anthropic run through its annual external audit reports and on the terms of its DPA.
Anthropic is a sub-processor for the commissioned provision of the service. Its public terms provide for separate retention to enforce its usage policy and combat harmful use: flagged inputs and outputs up to two years; safety-system scores up to seven years. The public terms also provide for retention needed to combat harmful use, with no stated overall maximum period.
ZweiHost does not present these independent purposes as its own instruction on the Customer's behalf. Anthropic's role for the relevant operations, the categories of personal data, the legal basis, the periods and the international recipients are established in the transfer assessment (see "International transfers"). If Anthropic determines the purposes and means on its own, that processing is described separately as processing by an independent controller, not as commissioned sub-processing.
International transfers. The contracting provider of the service is Anthropic Ireland, Limited, Ireland. Inputs and outputs are stored and processed in the USA.
Anthropic's DPA incorporates by reference the standard contractual clauses under Decision (EU) 2021/914, to the extent applicable. The specific transfers, recipients, countries, mechanisms and contractual annexes are set out in the international-transfer documentation, available to the Customer on request.
Transfers of personal data through ZwAI to the USA rely on the standard contractual clauses (Modules 2 and 3) incorporated in Anthropic's DPA. ZweiHost's assessment of this transfer, including onward recipients, is not complete: it needs written information from Anthropic that has not yet been received. The result is given to the Customer on request. The sub-processor authorisation does not replace these safeguards. Anthropic's sub-processor list is at trust.anthropic.com/subprocessors.
Reference sites. Cloudflare, Inc., through Browser Run, loads the full public page of the given reference site, including any personal data on it, to extract abstract design signals temporarily. Only the signals are sent to Anthropic, with no screenshot, text or images from the page. ZweiHost keeps none of the content after the request ends. Cloudflare's contractual periods, technical records, locations and international transfers are described separately.
Sources, read on 6 November 2026: Anthropic Commercial Terms (anthropic.com/legal/commercial-terms, effective 17 June 2025); Anthropic DPA (anthropic.com/legal/data-processing-addendum, effective 24 February 2025); Anthropic Privacy Center (privacy.claude.com) - the articles on retention, training and processing locations.
Annex 2. Site editor and base themes
The editor history may contain the values before and after publication, an author identifier and the time. Review requests contain the affected areas, a free note of up to 500 characters, the sender and the person who closed the request. Theme versions contain the settings and section content and author metadata.
The data is processed for editing, review, publication and limited restoration on the Customer's instructions. ZweiHost does not use it to assess staff on its own account. Access depends on the role in the shop. Base themes do not use artificial intelligence, Anthropic or Browser Run.
- Publish history: At most the newest 50 entries, and none older than 12 months. Entries outside the newest 50 are deleted at the next publication; entries older than 12 months at the latest one day after they expire (daily job).
- Earlier theme versions: The same two limits. The current published version, the working draft and a version that a kept history entry can restore are not deleted because of this limit alone; the last of these stays while it is needed for the restore. ZwAI candidates and checked versions are governed by Annex 1.
- Closed review requests: 90 days from closing; deleted at the latest one day after that.
- Author identifier: Removed when the user is deleted, together with the links to it. This does not automatically anonymise the content: names and other personal data may be inside the values or notes themselves.
- Backups: The intended period for backups is up to 30 days from their creation. Automatic deletion and actual compliance with this period are still to be confirmed.
A restore through "Restore" brings back only the shop's content, not deleted records and not withdrawn rights.
Annex 3. ZwAI - limited "site-only" mode: permitted operations and fields
Version 4 of the list, 12 November 2026. Only what is listed here is sent to Anthropic; a tool or field outside the list is not offered and is refused.
Operations:
- Reading the catalogue and proposing changes to it: products, categories, attributes, stock
- Reading and changing the site's draft: design, header (logo and favicon), home page, menu, footer, announcement bar, theme code
- Reading the shop's settings, without changing them: SEO, languages, currency, delivery prices and free-delivery thresholds
- Searching and showing ZweiHost's guides
- Links to BackOffice pages
- Style signals from public reference sites the user pastes
Fields:
- The staff member's messages to ZwAI and the "Build my site" brief (checked before sending; an address passes only when it matches the shop's address or pick-up address in its settings exactly)
- Product and variants: title, description, SKU, prices, stock, characteristics
- The product's first photo, sent as it is: people in it are visible
- Category: name, description, place in the tree
- Attributes and their values
- Site design: colours, fonts, style, home page sections and their texts, header (logo and favicon only from the shop's own uploads), menu, footer (no contact values), announcement bar
- Shop settings, read only: the SEO description and page titles (the shop's and the company's names only as a placeholder), the share image, languages, currency
- Delivery prices: the pricing mode, rate tables by region, free-delivery thresholds, who pays delivery; no sender details, pick-up address or courier passwords
- The theme code (CSS, Liquid)
- Screenshots of the draft at 375 and 1280 px, sent masked: every image blurred, phones, e-mails and the names of the team and of review authors replaced; any other name written in the site's text stays
- The shop's own domain, sent as it is, with reference sites
- ZweiHost's guides
- BackOffice page names and routes
- Abstract style signals from reference sites (no text, images or code from them)
Never permitted: orders, customers and their accounts, addresses and sessions, bookings, staff and users, sent e-mails and their events, newsletter subscribers, contact-form messages, reviews with their authors' names, returns, refunds, withdrawals, invoices, GDPR requests, the sender's details, the pick-up address and courier passwords. The storefront assistant is switched off.