AdBar privacy policy
A small app.
A clear boundary.
AdBar follows a simple rule: measure only what is needed to operate a voluntary sponsor placement and settle its accounting. This page describes the service boundary; the legal entity and processors will be identified before paid launch.
What we need
We process your email and account preferences, a random device installation identifier, pairing and session events, app version, coarse eligibility signals, accepted or rejected placement reasons, and account-linked earnings and payout records. We do not need your Mac serial number.
What we never read
AdBar does not collect screen contents or screenshots, keystrokes, browser history, files, active application names, raw mouse events, meeting content, or a cross-app activity timeline. The native app does not request Screen Recording, Accessibility, or Input Monitoring permissions.
Why we process it
We use these records to link one approved device, apply the counting rule, prevent duplicate settlement, show your own history, review safety and fraud signals, deliver account email, and meet financial or security obligations. Advertisers receive aggregate reporting; they do not receive your device identity.
Your choices and retention
You can pause, revoke a device, withdraw optional marketing consent, request access or correction, request deletion where retention duties allow, and ask for support. Pairing codes expire quickly. Detailed operational measurement is retained for a short window; financial, tax, consent, security, and provider records may need longer retention. We will publish the actual inventory and processors before paid launch.
India and processors
AdBar is India-first, but an India database region alone does not mean every processor is in India. The final policy will identify Supabase, email, hosting, payment, payout, and support processors and their relevant processing locations. Counsel will review the applicable Indian privacy and tax obligations before live money.