Aloodo helps you alert vulnerable users and ask them to run tracking protection. More info on the Aloodo home page.
Want to give your users a quick reminder? Add the script to your site.
Users won't see the warning until they visit the third site that runs the iframe. This feature is needed in order to get accurate results with Privacy Badger.
Your own tracking warnings
By default, the above script will load and
display a warning pop-up. If you prefer to
supply your own warning, add an element
with one of the following
ids to the page:
style="display: none". Instead of
displaying the popup, the script will set the existing
element to block or inline.
This is how the
cheesy ad and footer warning
here on blog.aloodo.org work.
Elements hidden from known vulnerable users
If the page has an element with an
tracking-safety, the ad.js script will hide it (set
its display property to none) if it detects tracking.
Please do not use this feature to tell users that they
are safe from tracking, since not all tracking
technologies are detectable from the client. This
feature is just to let you remove generic copy that
would not be needed if showing one of the tracking
Reverse tracking wall
A simple way to encourage tracking protection is a “reverse tracking wall” that makes some pages unavailable to tracked users. A simple client-side reverse tracking wall is built in.
trackingAlternateLocation to the URL of the page to which users should
be redirected if tracking is detected.
Just put https://ad.aloodo.com/track/ in an iframe. Vulnerable users will see a notification later, on other sites.
If you prefer to use your own action to notify tracked users, you can also include https://ad.aloodo.com/track/ in an iframe, and handle the “tracking detected” message in your own script.
<iframe style="display: none" src="https://ad.aloodo.com/track/"></iframe>
This can be useful for gathering information on how many of your users are vulnerable to third-party tracking.
How it works
The main part is inline on this page:
That script will send a "tracking detected" message
if it detects that it has been able to modify a
cookie and/or localStorage, on three different pages.
It relies on
document.referrer which, inside an
iframe, is the containing page.
ad.js adds the iframe to the page and
listens for the "tracking detected" message. It then
tries the following.
trackingAlternateLocationis set, blank the page and refresh to it.
if any elements with the
tracking-warning-table-cellare present, set their
displayto the appropriate value and finish.
Otherwise, attempt to load jQuery if not already present, then Toastr, and show a Toastr warning.
ad.js script will not attempt to load additional
- Post an issue on the project on GitHub.