Privacy Policy

1. Scope of this Privacy Policy

This Privacy Policy applies to:

Broxme website The website at broxme.com and related Broxme product pages.

Support and communications Messages, files, and other information you voluntarily send to Broxme or Nobash LLC.

iShield browser extension The iShield extension distributed for supported browsers including Google Chrome, Microsoft Edge, Mozilla Firefox, Opera, and Chrome-compatible browsers such as Brave.

iShield filter-update service The service used by iShield to retrieve signed filter and network-rule updates from:

https://update.broxme.com/ishield/manifest.json

This policy does not govern the independent privacy practices of browser vendors, browser extension stores, websites you visit, or unrelated third-party services.

2. Privacy summary

iShield is designed so that ordinary browsing protection happens locally on your device.

iShield may locally examine information necessary to provide its protection features, including website addresses, network requests, limited page signals, and filter matches.

iShield does not transmit your browsing history, visited-page content, search history, passwords, form entries, cookies, local activity records, or blocked-domain history to Broxme.

iShield does not include Broxme analytics, advertising trackers, behavioral advertising, crash-reporting telemetry, account tracking, or an extension-generated device or installation identifier.

The only Broxme-operated network service used by the current extension is the filter-update service. It provides signed filter data and does not receive your browsing records.

3. Information processed when you visit our website

When you visit broxme.com, the infrastructure used to deliver and secure the website may automatically process normal technical connection information.

This may include your IP address, request time, requested page, HTTP headers, browser or user-agent information, and security-related request information.

This information may be processed by our hosting, content-delivery, networking, or security providers as part of normal website delivery and protection.

We do not use website connection information to build behavioral advertising profiles.

At the time this policy was last updated, the Broxme website does not intentionally include advertising trackers designed to follow visitors across unrelated websites.

4. Contacting Broxme

If you contact us, we receive the information you choose to provide.

This may include your name, email address, message, subject, diagnostic details, screenshots, files, or other information you voluntarily send.

Please do not send passwords, authentication tokens, private keys, financial credentials, or unrelated sensitive personal information.

Where the Broxme website uses a contact form, submitted form information may be processed by the service provider used to deliver that form.

The current contact form may use FormSubmit to forward the name, email address, topic, and message you provide to:

hello@broxme.com

FormSubmit may also process ordinary network information and may use anti-spam or CAPTCHA technology.

You may contact us directly by email instead of using the form.

Information you voluntarily send for support is separate from iShield's local browsing-protection data.

5. How iShield works

iShield is a browser protection extension designed to block or reduce unwanted advertising, tracking, malicious or deceptive requests, phishing and scam risks, fingerprinting techniques, and other unwanted browsing behavior supported by its protection features.

To provide these features, iShield processes certain information locally inside your browser.

This local processing may include:

• the address or hostname of the current website;
• URLs or domains involved in network requests;
• matches against locally available filter rules;
• limited page structure, text, forms, or other signals needed for supported phishing, scam, cosmetic-filtering, anti-adblock, or protection features;
• locally generated protection events and counts; and
• website-specific settings and exceptions selected by you.

This processing is performed to provide the protection features visible to the user.

Ordinary protection does not upload this browsing information to Broxme.

6. Information iShield stores locally

iShield uses browser-managed extension storage to save settings and information necessary to provide its features.

Depending on the features you use, locally stored information may include:

Where supported by the current release, recent activity retention may be configured for periods such as 1, 7, or 30 days, with the extension's displayed setting determining the applicable period.

Supported blocked-domain activity may contain a hostname, category, timestamp, and count. This information remains in browser-managed local storage and is not uploaded to Broxme by the ordinary protection workflow.

7. Local website and page analysis

Some iShield features need to inspect limited information about the page being viewed.

For example, iShield may locally inspect a page address, hostname, network request, page structure, forms, wording, or other limited signals to determine whether a supported protection rule should apply.

This processing happens inside your browser.

iShield does not send page content, visited URLs, search history, form contents, or the locally maintained blocked-domain ledger to Broxme for ordinary protection.

Local processing is still data handling, and we disclose it here so users understand how the extension provides its protection features.

8. iShield filter-update service

iShield periodically checks for updated protection filters.

The current extension uses the following Broxme-operated update endpoint:

https://update.broxme.com/ishield/manifest.json

Update checks may occur automatically on a schedule and when you manually request an update from the extension.

The purpose of this connection is only to retrieve filter and network-rule updates.

The current extension does not use this service to upload browsing history, visited URLs, page content, searches, local activity records, allowed-site lists, passwords, form contents, or other browsing records.

9. Information sent during filter-update requests

iShield does not intentionally attach an account, user profile, browsing URL, page content, extension-generated tracking identifier, device identifier, or installation identifier to a filter-update request.

It does not send a browsing-data request body to the update service.

Like any normal internet connection, infrastructure delivering the update files may receive standard network information automatically.

This may include:

• your public IP address;
• request date and time;
• browser or HTTP user-agent information;
• requested update resource;
• protocol and security information; and
• technical information generated by hosting, CDN, firewall, or abuse-prevention systems.

This ordinary network metadata is used to operate, secure, troubleshoot, and protect the update infrastructure.

We do not use filter-update request metadata for behavioral advertising or to build profiles of the websites you visit.

We do not claim a fixed server-log retention period unless the actual hosting and CDN configuration supports that statement.

10. Signed filter data

Filter updates are treated as data, not executable program code.

iShield verifies supported update data before applying it.

The update mechanism is designed to accept the supported signed filter or network-rule format used by the extension.

Unsigned, invalid, altered, unsupported, or expired update data is rejected according to the extension's verification rules.

Remote filter updates do not provide JavaScript, WebAssembly, remote feature logic, remotely hosted executable code, account policy, managed-device commands, or arbitrary executable instructions.

All executable extension logic is packaged with the extension distributed through the applicable browser or extension store.

11. No browsing telemetry

The current iShield release does not send Broxme:

• browsing history;
• a list of websites you visit;
• page content;
• search queries;
• form entries;
• passwords;
• cookies;
• authentication credentials;
• local allowed-site lists;
• custom user rules;
• local activity history;
• the blocked-domain activity ledger;
• advertising identifiers;
• an iShield account identifier;
• an extension-generated device identifier;
• an extension-generated installation identifier;
• behavioral analytics; or
• crash-reporting telemetry.

iShield does not require an iShield account for its ordinary protection features.

12. No advertising profiling or sale of browsing data

Broxme does not sell iShield browsing information.

We do not use iShield browsing information for personalized advertising, retargeting, creditworthiness decisions, lending decisions, data brokerage, or unrelated user profiling.

We do not transfer locally processed browsing information to advertising networks or data brokers.

Because ordinary browsing data remains local, Broxme employees do not routinely receive or review it.

Information you voluntarily send to us for support is different and may be reviewed by the people necessary to respond to your request.

13. No managed-device or remote-control system

The current public iShield browser extension does not include a Broxme managed-device enrollment system.

It does not enroll your browser with Broxme for central administration.

It does not transmit a device label or platform identity to Broxme for management purposes.

It does not receive remote browsing policies or administrator-assigned protection settings from Broxme.

It does not provide family-management, enterprise-management, or remote-control functionality through Broxme servers.

14. No remote executable code

iShield does not download JavaScript or other executable extension logic from Broxme servers for execution as extension functionality.

Protection logic, content scripts, scriptlets, and other executable components used by the extension are included in the distributed extension package.

Remote filter updates contain supported filter data only.

15. Why iShield requests browser permissions

iShield requests browser permissions only where they are needed for its current protection features.

declarativeNetRequest

Used to apply supported network-filtering rules, including blocking or modifying unwanted advertising, tracker, and dangerous requests.

The browser applies these declarative rules.

storage

Used to keep settings, allowed sites, custom rules, local protection statistics, filter information, and other supported extension state in browser-managed storage.

activeTab

Used for supported user-initiated interactions with the current browser tab, including current-page protection information and controls where applicable.

scripting

Used to register or execute packaged extension scripts needed for supported page-level protection, cosmetic filtering, fingerprinting protection, anti-adblock handling, or related functionality.

This permission does not allow iShield to download arbitrary remote JavaScript for execution.

alarms

Used to schedule filter-update checks and local extension maintenance tasks.

It is not used for remote device-policy synchronization.

Access to websites

iShield requires access to supported HTTP and HTTPS pages because advertising, tracking, phishing, scam, fingerprinting, cosmetic filtering, and other protection features need to operate on the websites you visit.

Website information accessed through this permission is used for the extension's disclosed protection features and is processed locally unless this policy explicitly states otherwise.

declarativeNetRequestFeedback, where available and granted

Some browser distributions may support optional rule-match feedback for protection counters and supported local activity features.

Ordinary network blocking does not depend on transmitting this information to Broxme.

16. Google Chrome

The Chrome version of iShield handles browser information only as necessary to provide its disclosed protection features.

iShield's handling of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

iShield does not use browsing-related information for personalized advertising, data brokerage, lending or credit decisions, or unrelated purposes.

Browsing-related information processed by the extension is not transmitted to Broxme except where this policy explicitly describes normal technical metadata associated with the filter-update connection.

Chrome and the Chrome Web Store may separately process information related to extension installation, updates, store usage, reviews, or browser functionality under Google's own terms and privacy policies.

Broxme does not control Google's independent processing.

17. Brave

iShield may be used in Brave through the Chrome-compatible version of the extension.

The iShield privacy behavior described in this policy remains the same when the Chrome-compatible build is used in Brave.

Brave may independently process browser, extension-installation, or update information under Brave's own policies.

Broxme does not control Brave's independent processing.

18. Microsoft Edge

The Microsoft Edge build of iShield follows the same local-first privacy model described in this policy.

Browsing information accessed by the extension is used only as necessary for the extension's disclosed protection features.

iShield does not transmit ordinary browsing history or page content to Broxme.

Microsoft Edge and the Microsoft Edge Add-ons service may independently process installation, update, performance, store, or browser information under Microsoft's own privacy policies.

Broxme does not control Microsoft's independent processing.

A dedicated Microsoft Edge privacy notice may be provided with the Microsoft Edge Add-ons listing to present the same practices in an Edge-specific format.

19. Mozilla Firefox

The Firefox version of iShield follows the same local-first protection model.

The current public Firefox build is designed so that personal browsing data used for ordinary protection is processed locally rather than transmitted to Broxme.

Its Broxme-operated network connection is limited to retrieving signed filter updates as described in this policy.

Mozilla Firefox and addons.mozilla.org may independently process extension installation, signing, update, review, or browser information under Mozilla's own privacy policies.

Broxme does not control Mozilla's independent processing.

20. Opera

The Opera version of iShield follows the same privacy model described in this policy.

Ordinary protection runs locally, and browsing records are not transmitted to Broxme.

Opera and Opera Addons may independently process information related to browser operation, extension installation, distribution, updates, or store activity under Opera's own policies.

Broxme does not control Opera's independent processing.

21. Service providers

Broxme may use service providers to operate its website, email, contact forms, hosting, content delivery, security, and filter-update infrastructure.

These providers may process technical information necessary to provide their services.

For example, infrastructure providers may process IP addresses and network request metadata when delivering the website or filter-update files.

Where the Broxme contact form uses FormSubmit, FormSubmit processes information submitted through that form according to its own service and privacy practices.

Service providers are not authorized by Broxme to use iShield browsing records for behavioral advertising or unrelated profiling.

iShield does not transmit your ordinary browsing records to these providers.

22. Browser vendors and extension stores

Browser vendors and extension stores may independently collect information relating to browser usage, extension installation, store accounts, reviews, automatic extension updates, crash reporting, security, or other platform functions.

Such processing is performed by those companies under their own privacy policies and is separate from Broxme's processing.

This policy describes what Broxme and the iShield extension itself handle.

23. Legal disclosures

We may disclose information that we actually possess when reasonably necessary to comply with applicable law, legal process, court orders, or valid governmental requests, or where necessary to investigate fraud, abuse, or threats to security or legal rights.

Because iShield's ordinary browsing records are kept locally and are not routinely transmitted to Broxme, we generally do not possess those records to disclose.

We may also disclose business or support information with your authorization or as part of a corporate transaction, such as a merger, acquisition, restructuring, or sale of assets, subject to applicable legal requirements.

We do not sell personal information to data brokers.

24. Local iShield data

Most iShield product information is stored locally in browser-managed extension storage.

You can manage supported activity data through iShield's settings and data controls.

Where available, you can clear activity information, remove website exceptions, remove custom rules, or perform a supported reset.

Removing iShield from the browser normally removes its browser-managed extension storage, subject to the browser's own backup, synchronization, recovery, or storage behavior.

Broxme cannot remotely delete local extension information that was never transmitted to us.

25. Website and support information

Support messages and other information you voluntarily send to us are retained only as reasonably necessary for support, security, recordkeeping, dispute resolution, legal obligations, or the purpose for which the information was supplied.

Website, CDN, security, and server log retention may depend on the infrastructure provider and configuration in use.

We do not promise a fixed deletion period for infrastructure logs unless such a period has been verified against the actual service configuration.

26. Security practices

We use reasonable technical and organizational safeguards appropriate to the information we process.

iShield's filter-update service uses HTTPS.

Supported filter updates are subject to signed-data verification before application.

The extension does not use the filter-update channel to download executable extension code.

Local extension data is stored using browser-managed storage.

iShield does not claim that browser extension storage has separate end-to-end encryption provided by iShield.

No system or storage mechanism can guarantee absolute security.

Users should protect their device, operating-system account, browser profile, and browser-store account.

27. Security reports

If you believe you have found a security vulnerability in Broxme or iShield, contact:

hello@broxme.com

Please include enough technical information for us to investigate the issue, but do not include passwords, authentication tokens, private keys, unrelated personal information, or other unnecessary secrets.

28. Access, correction, and deletion requests

Depending on where you live, applicable privacy law may give you rights regarding personal information we hold about you.

These rights may include access, correction, deletion, restriction, objection, portability, or withdrawal of consent where consent is the applicable legal basis.

To make a privacy request, contact:

hello@broxme.com

We may need reasonable information to verify the request.

Because most iShield browsing and activity information remains only on your device, Broxme may not possess that local information and therefore may not be able to provide or delete it remotely.

You can manage locally stored iShield information through the extension's supported controls or by removing the extension.

29. Legal bases where applicable

Where a legal basis for processing is required, we may process information based on:

providing a service or responding to a request you made;

our legitimate interests in operating, maintaining, supporting, and securing Broxme and iShield, where those interests are not overridden by applicable rights;

compliance with legal obligations; or

your consent where consent is required.

You may withdraw consent where processing relies on consent, without affecting processing that was lawful before the withdrawal.

30. International processing

Our service providers or infrastructure may operate in countries different from the country where you live.

As a result, information such as website connection metadata or support communications may be processed internationally.

Where required, we take reasonable steps to use appropriate legal and contractual protections for such processing.

31. Children

Broxme and iShield are not directed to children under 13, or a higher minimum age where required by applicable law.

We do not knowingly solicit personal information from children in violation of applicable law.

If you believe a child has provided personal information to Broxme without required authorization, contact us so that we can review the situation.

32. Changes

We may update this Privacy Policy as Broxme, iShield, applicable laws, infrastructure, or browser-store requirements change.

When we make changes, we will update the date at the top of this policy.

If a future iShield release materially changes how user data is handled, collected, used, transmitted, or shared, we will update this policy and provide additional disclosure or consent where required before applying the new practice.

Store declarations and extension disclosures should always correspond to the behavior of the version actually distributed.

33. Contact information

Broxme is operated by:

Nobash LLC

Privacy and security inquiries:

hello@broxme.com

Website:

https://broxme.com

Contact page:

https://broxme.com/contact

When contacting us about privacy, you may use the subject line:

Privacy Request — Broxme / iShield

34. Final privacy commitment

iShield is designed around a simple principle:

Protection should not require sending your browsing life to us.

iShield processes the website and network information necessary for its protection features locally in your browser.

The public extension does not send Broxme your browsing history, page content, searches, passwords, form entries, local activity history, or user-specific browsing profile.

Its Broxme-operated remote connection is limited to retrieving signed filter data needed to keep protection rules current.

We will update this policy if that model materially changes.