PUPMKTMarketplace
Cart
Theme

Public evaluation draft

Notice at Collection

A specific notice must appear at or before each actual collection. This registry is a launch checklist, not proof that a collection flow is active.

Status: Draft for counsel review before production activation.

Operator
Dravara, LLC
Policy ID
pupmkt-privacy-notice-at-collection
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.

Collection contexts

  • Account registration: identifiers, credentials, and account preferences for access and security.
  • Seller onboarding: identity, business, tax, payout-provider, and compliance information for eligibility and operations.
  • Contact, support, partnership, affiliate, security, accessibility, privacy, and suspicious-activity forms: contact details and message content for routing and response.
  • Location permission: only minimum location needed for a user-requested nearby feature. Media upload: file content and metadata for listings or evidence. Employee authentication: workforce identifiers and security events.
  • Marketing signup: contact and preference information only after the applicable choice.

Required contextual details

  • Every live notice must state categories, purpose, retention summary, sensitive-data status, current sale/share/targeted-advertising position, and links to the Privacy Notice and Privacy Choices.
  • Retention and sharing differ by context and must be configured before collection. Do not submit sensitive information through a flow still marked evaluation-only.

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.