A Data Protection Officer (DPO) is an independent role responsible for overseeing data-protection duties, advising on impact assessments, and acting as a contact point for supervisory authorities and data subjects. This guide is an engineering reading for that review. It is not legal advice and not a settled rule.
How to use this guide
Qusto sits in the analytics layer of a merchant's stack. On Shopify, a visit is linked to an order only after the shopper says yes. In Germany, traffic counts wait for a yes. The analytics layer is not described here as independent of consent. Ask us about consent in your market.
For day-to-day dashboard use, see the operator guide. For installation mechanics on Shopify, see the Shopify guide.
Architectural commitments
These properties are structural — not configuration toggles merchants enable after legal review:
- No tracking cookies — no persistent cross-site identifiers for analytics measurement; coarse geo derived at ingest (country, region, city). A raw IP is not kept for that purpose.
- Open-core verifiability — Community Edition source is inspectable; managed hosting is optional
- EU data residency — analytics processing hosted in Europe
Qusto sets no tracking cookies. On Shopify, the checkout pixel follows the store's customer-privacy settings. Advertising pixels, marketing cookies, and other tags the store still runs keep their own consent step. In Germany, traffic counts wait for a yes. This is an engineering reading, not a legal conclusion. Ask us about consent in your market.
Capability boundaries by tier
When approving external copy or sales materials, these boundaries matter:
| Topic | What to verify |
|---|---|
| Cart abandonment | Analytics visibility only. Not an email to the shopper, and not an outbound message. |
| Channel → revenue attribution | Available on Growth tier and above |
| Location intelligence | Visitor geography on all tiers; revenue and cart-abandonment by region on Growth+ |
Regulatory context
Tags that fire before a shopper answers a banner are a common enforcement category. Qusto does not treat the analytics layer as independent of consent. On Shopify, a channel is attached when the shopper says yes. In Germany, traffic counts wait for a yes. This is an engineering reading, not a legal conclusion. Ask us about consent in your market.
Shopify GDPR webhooks
For App Store distribution, Shopify requires mandatory compliance webhooks. Qusto implements handlers for:
customers/data_request— processed: export bundle + Data Monitor audit rowcustomers/redact— processed: token-scoped erasure + audit rowshop/redact— processed: full site commerce data redaction
Vendor-review checklist
Before sign-off, we suggest confirming:
- Which subscription tier the merchant will use — feature claims should match tier (Core vs Growth+)
- Whether any non-Qusto tags still require a separate consent management platform
- That the Data Processing Agreement and subprocessor list are acceptable for your organisation
- That location-related claims distinguish visitor geography from revenue-by-region (Growth+ only)