Privacy

What the widget collects

When the WagerLayer overlay is shown on a publisher's site, we record that it was shown, which US state the visitor was resolved to, which offers were listed, and whether the visitor clicked one. A click is given a random identifier so a later deposit can be credited to the right publisher.

That is the whole of it: a two-letter state code, a random click identifier, an offer identifier, the publisher's site, and a timestamp.

What it does not collect

The widget sets no cookies. It does not read or write any cookie, on our domain or the publisher's.

We do not store IP addresses, names, email addresses, dates of birth, payment details or any other information that identifies a visitor. We do not fingerprint devices, and we do not build profiles of visitors or track them between sites.

The state a visitor is resolved to comes from the network edge at the moment of the request. The address it was derived from is not written down.

Browser storage

The widget uses two small values in the browser's own storage, both scoped to the publisher's site and neither identifying anyone.

A flag in sessionStorage records that the overlay has already been shown, so a visitor is not shown it twice in one session. It is cleared when the tab closes.

A cached accent colour in localStorage lets the overlay render in the publisher's own styling without a round trip. It contains a colour and nothing else.

When a visitor clicks an offer

Clicking an offer takes the visitor to the operator's own site. From that point the operator's privacy policy governs, not ours.

We pass the random click identifier so the operator can tell us a deposit happened and we can pay the correct publisher. We do not receive the visitor's account details, deposit amounts beyond the commission owed, or any personal information from the operator.

Publisher accounts

Publishers who sign up give us a company name, a contact name, an email address and a password, and later the payout details they want to be paid to. Passwords are stored hashed by our authentication provider and are never visible to us.

Payout details are visible only to the publisher who entered them and to WagerLayer staff who administer payments. Changing them requires the account password again, even in an open session.

Who we share data with

Our infrastructure providers process data on our behalf: hosting, the database, the network edge, and the affiliate tracker that records conversions. They act on our instructions and for no other purpose.

We do not sell data, and we do not share visitor data with advertisers beyond the click identifier needed to credit a conversion.

How long we keep it

Event records are kept while they are needed to calculate and evidence payouts, and to answer a publisher's questions about a statement. Publisher account records are kept for as long as the account is open and afterwards where we are required to retain them for accounting purposes.

Contact

Questions about this page, or about data we hold, can be sent to privacy@wagerlayer.com.