Check out our privacy policy at https://webpass.io/privacy for a detailed explanation of what we do with your data. If there are any scenarios that aren't clearly explained that concern you, please let me know and I can have the policy updated.
Mind you, since the service acts as a tracker in its own right, people wanting to avoid being tracked are unlikely to use it in the first place...
With that said, here is MY implementation. Other publishers may do it differently.
Our site is a discussion forum. People can browse at will but only logged in users can post and reply to topics.
We run advertising with Google DFP. A few years back we started offering a subscription where users pay us a recurring fee and they have the option to turn ads on/off in their profile.
I myself thought of using a micro-payment service but I wanted something easy.
The way webpass works is by their add-on sending a unique token on every page request. If there's a token my code checks with their server if it's a valid token. If yes we then have two options:
- if you are not logged in then we completely remove the ad scripts BEFORE sending the page to the browser client.
- if you are logged in we treat your session as a subscriber session and will send or not the ad scripts based on your profile preferences. This means you can go to your profile page and turn ads on/off.
Using webpass made the experience better for our users because even those people who don't want to create another web profile and pay another subscription can still get to our site ad free.
Does it make sense now?
I'm out.
The Firefox addon has never sent that information, and (though not recorded anyway) we'll be removing it from the Chrome extension and updating our privacy policy shortly.