Public evaluation draft
Privacy Choices
The shared browser control stores and enforces available local choices; jurisdictional rights intake and downstream processor enforcement remain separately gated.
Status: Draft for counsel review before production activation.
Pre-launch and no-agreement notice
PUPMKT is a pre-launch product. Features, policies, listings, workflows, pricing, availability, and technical capabilities may be incomplete or change. Marketplace content and activity may be demonstration, curated, synthetic, or connector-ready and may not represent real transactions or operating services.
Access, review, testing, linking, or communication does not by itself create an agreement, partnership, agency, joint venture, confidentiality obligation, license, offer, commitment, exclusivity, acquisition arrangement, pilot, or other commercial relationship with Dravara, LLC. Any such relationship requires a separate written agreement executed by authorized representatives.
What this draft covers
- Review current necessary, security, functional, analytics, advertising, affiliate-attribution, and session-replay choices.
- Accept or reject available optional categories and later withdraw consent.
- Opt out of applicable sale, sharing, targeted advertising, or qualifying profiling; limit sensitive-data use where applicable.
- Review detected GPC or other recognized universal opt-out status.
- Request access, correction, deletion, portability, appeal, or authorized-agent handling.
Activation status
- The shared browser control persists a bounded versioned choice, defaults optional categories off, blocks optional analytics until consent, clears analytics cookies on denial, and treats detected Global Privacy Control as an effective optional-category denial. Google analytics also requires an exact allowlisted property configuration; advertising, affiliate-attribution, and session-replay loaders remain unavailable.
- The server consent/jurisdiction foundation, account-linked enforcement, privacy-rights delivery and verification workflow, processor propagation, and counsel-approved applicability rules are source-only or uncomposed. The static page therefore does not claim that every listed legal right is operational.
- Use the Data Request Form route to review request types. Do not send sensitive identity documents through an unverified channel.
Review and activation gates
- Qualified counsel must approve the text, jurisdiction coverage, and release configuration.
- A published page does not activate a marketplace capability; matching technical and operational controls must be verified.
- Any provider, retailer, publisher, store, or other third-party relationship requires direct written authorization before it is described as active.