As a means to combat annoying and intrusive advertisements in Safari, Apple added native support for content blockers on the iPhone. Instead of being bombarded by notifications, banners, and pop-ups, content blockers prevent them from opening, which can also be said about those annoying cookie consent notices that many websites now have.
Anytime you visit a website, a cookie file is saved on your device that contains information about the website and you, including a unique ID and personally identifiable information such as your name, email address, and phone number. The website then uses this cookie whenever you visit the next time so that they can uniquely tailor this experience to you. For example, if you've placed a few things in your shopping cart, this information is stored in your cookies, so the next time you go to the website, these products may still be in your cart.
Not everyone is okay with how companies track important information via cookies. So the European Union passed a law called the GDPR, which essentially requires websites to get your consent before collecting your data. That's why you may see websites asking for permission to your cookies with annoying banners that sometimes take up the entire page.
- Don't Miss: How to Block Popups in Safari on Your iPhone
If you don't care about cookie policies, you probably ignore these banners. And if you do, content blockers can help you block these banners so that they don't appear in the first place. Although the website may still collect your information, you no longer have to worry about these cookie consent notices filling up your page. And as a bonus, it won't block ads so that you can continue to support the sites you visit.
Step 1: Install the 'Hush for Safari' App
"Hush for Safari," created by developer Oblador AB, is a simple yet powerful service that blocks those annoying consent notices asking you to accept cookies whenever you visit a new website. The app works as a content blocker (without blocking ads), so it simply guides Safari to hide these notifications without asking for access to your private information, unlike other blockers.
You can check out its App Store listing or even its source code to ensure that they're not tracking or collecting your data.
- App Store Link: Hush for Safari (free)
Step 2: Add It to Safari's Content Blockers
Before you can use Hush for Safari, you must first toggle it on as a Safari content blocker. To do so, launch the Settings app and go into "Safari." Next, scroll down and tap on "Content Blockers" under General. If you don't see "Content Blockers," it's because you don't have a content blocker installed on your iPhone (so make sure Hush has downloaded all the way).
In Content Blockers, you should see Hush for Safari listed as "Hush." Tap on its toggle to enable it. You don't even need to open the app itself, although you should see whether it's enabled or disabled if you do.
Step 3: Browse Safari Without Cookie Consent Notices
Now, whenever you visit a new website, i.e., a website you have never visited before, you should no longer see cookie consent notices. Below you can see the European Space Agency website with a cookie consent notice (left) and without one when Hush for Safari is enabled (right).
In case you want cookie consent notices back, to see which websites track your cookies, go back to Settings –> Safari –> Content Blockers, then toggle off Hush.
Keep Your Connection Secure Without a Monthly Bill. Get a lifetime subscription to VPN Unlimited for all your devices with a one-time purchase from the new Gadget Hacks Shop, and watch Hulu or Netflix without regional restrictions, increase security when browsing on public networks, and more.
Other worthwhile deals to check out:
Hush blocks this webpage. ??
Why didn't the bureaucrats who dream up their wonderful-make-our-lives-better-by-making-them-more-complicated-and-insufferable stuff make an exception for having websites that have THREE cookies only - username and password and a third one that I suppose might be useful for this - a "areYouRegisted" flag, a "doYouWantTwoFactorAuthenticationAndWhichEmailAddressToUseForIt", "preferredDisplayName", "preferredLanguage" - something. Limit these to whatever a reasonable length would be (20 Unicode characters probably - make that 64 or 128 bytes). I guess you might want to require the "sign up page" to include a warning, "This website will use a cookie to store your username and password ONLY".
Yes, it could maybe be abused. But the system already CAN be abused (that's why the GDRF exists, right?) Of course, Liberals (capital L only) don't seem to understand the phrase "compliance cost". And the fact that it applies to BOTH "producers" and "consumers" - an "annoyance factor". And before "they" say, "that doesn't matter".. Aren't they the same ones starting to finally whine about screen-time and distractions and such? (Don't get me started on over-signage on US streets possibly CAUSING more accidents.)
(Though it should already have a preferred display name and language. I suppose this would be if you had a website that could function with only making ONE server request - on login, that's it. But the people who hire web programmers don't care about efficiency, and must assume we ALL have OC-768 lines directly into the companies' server farm - and no one else on that farm when your accessing it)
Share Your Thoughts