Privacy
This page explains the limited data getpixel.bid processes to operate the public wall, complete payments, count visits, and prevent abuse.
Last updated:
Public placement data
A completed purchase publishes the normalized destination, display name, resolved favicon or public profile image, pixel count, click count, and placement dates. This information is intentionally public and may be indexed by search engines.
Payments
Stripe processes payments. getpixel.bid stores the checkout and payment identifiers, amount, status, and customer email needed to verify delivery, handle support, prevent duplicate fulfillment, and reflect refunds or payment disputes. Card details never pass through getpixel.bid servers.
Analytics and click counting
The site uses a self-hosted Umami instance for privacy-focused aggregate traffic statistics. A secure first-party visitor cookie and short-lived hashed network identifiers are used to avoid counting the same placement click repeatedly and to limit abuse.
Service providers and retention
Infrastructure providers include Stripe for payments, Koyeb for hosting, Neon for the database, Umami for analytics, and Unavatar for public website or social images. Operational records are retained only as long as needed for accounting, fraud prevention, support, legal obligations, and reliable wall operation.
Contact
For a privacy request, contact [email protected].