Local-first by design
Shieldly stores preferences, counters, fixes history and per-site rules locally in Chrome storage where possible. This keeps the everyday ad blocking experience simple and reduces reliance on remote dashboards.
No advertising profiles
Shieldly's privacy policy and Chrome disclosure explain that extension data is not sold and is not used for unrelated advertising purposes. The extension's purpose is blocking ads, trackers and distractions.
Practical privacy controls
Privacy is easier to trust when controls are clear. Shieldly includes protection modes, temporary pause and per-site preferences so you can adjust behavior without exposing more data than necessary.
Separate local configuration from online activity
Local-first describes where Shieldly keeps settings and counters for everyday protection. It does not mean that browsing stops producing network requests. Websites still receive connections, extension distribution can involve the browser's store, and optional services may require their own requests. Read the privacy policy for the scope of the product's data practices. Treat a local configuration file as private, particularly when it contains site exceptions or custom domains.
Build a small, understandable protection setup
Begin with the modules you need and check the pages you use frequently. More enabled options do not automatically create a better outcome if they prevent you from completing normal tasks. Use site controls to handle a specific incompatibility instead of switching protection off globally. Revisit old exceptions occasionally, especially after an update, so an exception created for a temporary issue does not become an unexplained permanent setting.
Review the limits before relying on a privacy claim
Ad and tracker filtering do not replace account security, browser updates or careful permission choices. WebRTC controls address a particular browser connection behavior and do not provide a VPN. SafeClick targets supported deceptive interactions and cannot verify every destination. Understanding those boundaries helps you choose which features are useful and prevents a single protection indicator from being mistaken for a guarantee of anonymity or safety.
Frequently asked questions
Do I need an account for local filtering?
Core local protection does not require a cloud account. Optional Advanced activation is a separate workflow; check the current controls and terms for that feature.
Are exported settings public information?
No. A backup can reveal configured websites and preferences. Store it privately and review it before sharing it with anyone.
Related pages
Read tracker blocker, data deletion and Chrome disclosure.