Weezbe

Weezbe sets strictly necessary first party cookies for the visitor session, the cart, the checkout funnel, the language and currency, the CSRF token and the customer account when logged in. Optional integrations enabled by the merchant (Google Analytics, Meta Pixel, email marketing, embedded reviews and videos) load their own non essential cookies. The exact list depends on which apps you have installed from the Weezbe marketplace.

Consent is required for non essential cookies activated on a Weezbe storefront, including analytics, marketing, personalisation and embedded third party content. Strictly necessary cookies for the cart, the session and the checkout benefit from the Article 5(3) ePrivacy exemption. Newsletter signups and any direct marketing also require their own consent, ideally collected with a double opt in mechanism.

The legal basis is the performance of the contract under Article 6(1)(b) GDPR for order management, delivery and customer accounts. Legal obligation applies to invoicing, accounting and consumer protection retention rules. Consent under Article 6(1)(a) covers marketing communications, newsletters and non essential cookies. Legitimate interest can support fraud prevention, subject to a documented assessment.

The Weezbe platform hosts the storefront and the back office data in the European Union. Transfers to the United States happen mainly through optional integrations such as Google Analytics, Meta Pixel, US based payment providers or shipping carriers. The merchant must list each US recipient in the privacy notice and rely on the EU US Data Privacy Framework certification or Standard Contractual Clauses, with a Transfer Impact Assessment for high risk recipients.

A DPIA is generally not required for a basic Weezbe store with a small catalog, a guest or simple account checkout and a tokenised payment integration. Conduct a DPIA when you enable large scale personalisation, when the catalog reveals sensitive preferences (health, religion, political opinions), when the store targets children or when you onboard external data into the Weezbe customer database for advertising purposes.

Sign the Weezbe DPA, review subprocessors, deactivate unused integrations and only enable apps you actually need. Configure a tokenised payment provider, set retention rules for orders, abandoned carts and inactive accounts, separate marketing consent from terms of sale acceptance and connect a consent management platform to control all non essential cookies. Maintain a record of processing activities and publish a clear privacy notice with the list of subprocessors.

For comparable all in one online store builders, evaluate Shopify, Wix Stores, Squarespace Commerce, BigCommerce, Ecwid, PrestaShop Cloud, WooCommerce or Magento Open Source. Each one has its own data residency, marketplace of apps and pricing. The compliance profile depends mostly on the integrations and marketing tools you activate, rather than on the platform itself.

List the strictly necessary cookies set by Weezbe (session, cart, checkout, CSRF, language, currency, customer account) and explain their role. Add a separate section for the analytics, personalisation and marketing cookies enabled by your installed apps, with names, hosts, durations and purposes. Mention Weezbe and its subprocessors in the privacy notice, document the lawful bases and refresh the page each time you add or remove a marketplace app.