PUPMKTMarketplace
Cart
Theme

Public evaluation draft

Cookie and Storage Notice

Optional technology must not load before required consent. Deployment configuration, processor terms, retention, and jurisdiction rules must be verified before activation.

Status: Draft for counsel review before production activation.

Operator
Dravara, LLC
Policy ID
pupmkt-cookies
Version
0.1.0-draft
Publication date
Effective date
Not effective — pre-launch draft
Status
DRAFTED — COUNSEL_APPROVAL_REQUIRED
Jurisdiction
United States; applicability must be determined before activation
Audience
Public visitors and prospective marketplace participants
Applicable property
https://pupmkt.netlify.app
Approval
Not approved; counsel, owner, provider, and operational review as applicable
Acceptance
Not required while this document remains an evaluation draft

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.

Inventory status

  • Necessary/security: session and anti-abuse identifiers may be used only when the corresponding service is active; exact names, domains, providers, and durations remain provider-gated.
  • Functional source storage includes theme, walkthrough, synthetic guided-site state, presentation-only cart and saved items, connected-session presentation, listing draft, checkout-return, and bounded idempotency state; exact use depends on the property and route.
  • Privacy choices use the bounded first-party PUPMKTPrivacyChoices.v2 record. A legacy PUPMKTAnalyticsConsent.v1 record is read only for controlled migration or invalidation.
  • Optional Google Tag Manager or GA4 analytics can load only for an exact allowlisted property after analytics consent. The default has no public identifier. Advertising, affiliate-attribution, and session-replay loaders remain unavailable.
  • For every activated identifier, the registry must record name, provider, category, purpose, domain, duration, first/third-party status, consent rule, jurisdiction rule, tag dependency, and provider privacy link.

Choice rules

  • Optional categories must be off by default where prior consent applies. Rejection must be as easy as acceptance, withdrawal must be available, and silence or scrolling is not consent.
  • If jurisdiction cannot be resolved reliably, optional tracking uses the more privacy-protective configuration. GPS is not requested for cookie compliance.

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.