PRIVACY POLICY
BrandAtlas collects only the information needed to operate the map placement marketplace, protect it from abuse, measure product placement performance, and meet payment and legal obligations.
Information we process
You can purchase as a guest without a public profile. We store your brand name, logo, destination link, territory activity, transaction references, payout status, and moderation history. Dodo Payments receives the private email and payment information required for checkout, tax, fraud review, and receipts; those details are never displayed publicly.
Visitors and analytics
BrandAtlas records page views, territory impressions, product-link clicks, approximate online activity, and security events. Network address and browser information are converted into a rotating pseudonymous hash; raw network addresses are not stored in marketplace analytics tables.
How information is used
Information is used to provide placements, prevent duplicate or abusive activity, report genuine product engagement, resolve disputes, maintain audit records, and comply with applicable law. BrandAtlas does not sell personal information.
Retention and deletion
Short-lived presence and rate-limit records are periodically removed. Marketplace, audit, payment, payout, dispute, and compliance records may be retained for the period required to operate the service and meet legal obligations. Operators may request access or deletion where applicable, subject to records BrandAtlas must retain.
Service providers and international processing
Hosting, storage, identity, payment, fraud-prevention, analytics, and support providers process information only to deliver their services. Data may be processed in countries other than the visitor's country with appropriate contractual and technical safeguards.
Your choices
You can browse public map information without creating a BrandAtlas profile when public access is enabled. Opening a product link records an aggregated click. Browser privacy controls can limit optional storage, but essential security and transaction records cannot be disabled.
Contact and policy owner
The operating entity, privacy contact, jurisdiction, effective date, and statutory request process must be confirmed by the product owner before public launch. This policy must be reviewed alongside the final payment provider and target-market requirements.