> STATUS: LAUNCH-PREPARATION DRAFT, version 0.2 (14 August 2026). > This policy is designed for the ZELIVOA UK marketplace product model. It must be reviewed against the final operator identity, payment/KYC providers, actual launch categories and the law then in force before public real-money launch. > Nothing in this policy removes statutory rights or liability that cannot lawfully be excluded. # ZELIVOA Privacy Policy — Draft v0.2 ## 1. Controller [OPERATOR LEGAL NAME], trading as ZELIVOA, is controller for marketplace data except where another provider has its own independent legal role. Contact: [PRIVACY CONTACT]. ## 2. Data categories Account/contact data; profile/seller information; addresses/delivery information; verification/KYC references; listings/images; orders/offers/messages/reviews/reports; payment status/references but not raw card/CVV; device/security/audit data; support/dispute evidence; language/theme/cookie choices. A delivery address collected during registration is private account data: it is used for checkout and delivery operations and is not displayed as a public listing field. ## 3. Purposes and lawful bases Before launch, the data map must identify the lawful basis for each purpose, including marketplace contract/service delivery, security/fraud prevention, legal compliance, seller reporting, support, disputes, payments/payouts, delivery, product-safety recalls and consent-based marketing where used. ## 4. Product safety and recalls Where necessary and lawful, order/contact information may be used to identify and warn users who bought a product later subject to a credible safety notice or recall. ## 5. Sharing Data may be shared with payment/KYC providers, carriers, hosting/security vendors, professional advisers and authorities where appropriate and lawful. The final provider/subprocessor list and international-transfer safeguards must be documented. ## 6. Retention ZELIVOA must maintain a documented retention schedule. Account content that is no longer needed should be removed/anonymised, while financial, fraud, audit, safety and legal records may require longer retention. ## 7. Rights Depending on the processing, rights can include access, correction, erasure, restriction, objection and portability, plus withdrawal of consent where consent is relied on. Identity verification may be required before sensitive requests are fulfilled. ## 8. Automated signals ZELIVOA may use automated risk/trust signals to prioritise moderation or detect suspicious activity. Current moderation automation does not permanently ban solely from a score. The final notice must describe any automated decision-making/profiling that has legal or similarly significant effects if introduced. ## 9. Security Controls include access restrictions, TLS, password hashing, MFA support, secret separation, audit logs and backups. Security incidents must follow an incident-response process and applicable notification duties. Email verification is used to confirm control of the registration address before account access is used for marketplace activity. Verification links are time-limited and should never be forwarded or shared. ## 10. Complaints Privacy contact: [PRIVACY CONTACT]. Before public launch add correct Information Commissioner's Office complaint information and all mandatory controller details. ## FIX110: optional shopping personalisation The /privacy page and footer Cookie settings control language/appearance storage, recently viewed items and personalised recommendations separately. Optional features start off. Search/view collection requires the current browser's signed permission for the current account. Updating an account choice invalidates previous browser permissions for that account. Browsing history cannot cross between signed-in accounts through these recommendation flows. Recommendations use recent opted-in searches/views, categories of intentionally saved products, followed sellers, freshness, similar item price ranges, a small smoothed seller-quality signal and stated dispatch time. They exclude unavailable items and respect seller-plan public visibility. The feed limits one seller to three products per set. Prices themselves do not change according to browsing history. There is no paid placement in this feed. These rules do not describe or claim to reproduce a competitor's private model. Optional account search/view history is used for up to 30 days, then removed in bounded maintenance batches; view interests influence ranking for up to 14 days. Clear browsing history and withdrawal controls are available in /privacy. Orders, messages, deliberate saves and security records follow their separate service and retention purposes. Cookie choices last up to 180 days; the Cookie Policy gives the implementation inventory and cross-browser limitations. ## FIX111 — optional first-party measurement and discovery controls The optional measurement purpose (`analytics`) is independent of personalisation and starts off. Previous valid three-purpose choices keep their original permissions and do not grant measurement. There is no additional tracking cookie: the signed, host-only `z_privacy` choice receipt carries the explicit fourth choice. Accept optional or the individual measurement checkbox can grant it. Reject, withdrawal, browser GPC and receipt/account validation disable it. Shopping, messages and support remain usable with it off. While signed in and opted in, the service may record item impressions, item clicks and search-result counts. A visible impression requires at least half the item card to be visible for 0.6 seconds; an explicit product click also establishes an impression. A signed result context expires after 15 minutes and is bound to the account and current choice revision. Repeated account/item/source actions are counted once per 15 minutes. Own-item activity is excluded. These are a partial consented sample; rates are withheld until 20 observations. Completed sales and proceeds are reported separately, not attributed to clicks. Measurement records use an internal account reference for consent enforcement and deletion. They do not contain raw search text, email, IP, fingerprint or third-party identifier. A query-group key is a server-keyed hash. Seller reports contain only aggregate own-listing totals; admin reports do not expose customer search text or identities. Measurements expire after 30 days through bounded maintenance on the existing timer, and each account is capped at 3,000 measurement records. Withdraw measurement or clear browsing history deletes that account's measurement records. Orders, messages, security events and financial records are retained separately. Not interested/Undo are explicit signed-in recommendation choices. Up to 100 currently hidden items affect recommendations for 30 days; up to 300 recent preference actions are retained. Withdraw personalisation or clear history removes these choices. New interest matching can use opted-in brand, size, colour and condition signals. Discovery quality uses moderation-visible 12-month reviews (automatic feedback discovery weight 0.25, member feedback weight 1), and saved-deadline 90-day recorded dispatch history. Fewer than five eligible dispatches are neutral; adjustment is capped at two points. Seller-recorded handovers are not represented as independent carrier verification. Public star ratings are unchanged. No paid placement, personalised prices, purchase attribution, advertising tracker or sensitive-interest inference is introduced.