Information used
Accounts store username, email, password hash, verification status, credit balance and session tokens. Domain ownership checks and submitted banner/site data are also processed.
Accounts store username, email, password hash, verification status, credit balance and session tokens. Domain ownership checks and submitted banner/site data are also processed.
For fraud prevention, the exchange creates a keyed hash from the visitor IP address and browser user-agent. It keeps serve, verified impression, click and rejection records. Hashing is pseudonymization, not full anonymization.
The site uses a session cookie and, when explicitly selected, a 30-day authentication cookie. Display features also use browser requests to record eligible impressions.
Data supports authentication, advertising delivery, credit accounting, site moderation, support and abuse prevention. Participants see their own data; administrators can access the records needed to run the network.
Moderation updates and support replies can be sent by email to verified accounts. Delivery depends on server mail configuration. Support messages are visible to support staff; please avoid putting secrets in them.
Technical records are currently stored in the database; automated event cleanup is planned for a future update. Contact support for access/correction requests or questions about records and retention.
This is a working service policy, not a legal compliance certification. Before public launch it should be reviewed for the locations and audiences where the network operates.