iOS Application Privacy Addendum v3.3

1. How Ad Blocking Works on iOS

AdBlock360 for iOS blocks ads in Safari through extensions that Apple's Safari loads on your device:

• Content Blocker extensions. AdBlock360 provides Safari with sets of filter rules. Safari compiles these rules and applies them itself while you browse. The Content Blocker extensions do not see the pages you visit, do not receive your browsing activity, and do not communicate with AdBlock360 servers. They communicate with our diagnostics provider only while error reporting is on (Section 6).
• Advanced Blocking extension (Safari Web Extension). If you enable it in Safari, this extension runs on the pages you visit to remove ads and ad-related elements that filter rules alone cannot handle. It runs locally on your device. It does not transmit the pages you visit, their content, or your browsing history to AdBlock360.
• Share extension. When you choose AdBlock360 in Safari's share sheet, the extension reads the address of the page you are sharing, so you can add that site to your allowlist. The address is stored on your device only (see Section 2).

2. Local Data Storage

The app stores certain data locally on your device, in a storage area shared between the app and its Safari extensions:

• Your allowlist (sites where you have turned ad blocking off)
• Preferences and settings
• The current filter rules and the previous known-good set, so the app can fall back if an update fails
• A timestamp of when the Advanced Blocking extension last ran, used only to show you the protection status in the app
• Limited technical logs needed for the app to resume interrupted work (for example an unfinished filter-rule update)

This data stays on your device. It is not synced to AdBlock360 servers and not backed up by AdBlock360. It is included in your device backup according to your iOS backup settings.

Deleting the app deletes this data.

3. Advanced Blocking Extension and Protection Status

The app shows whether the Advanced Blocking extension has recently run in Safari. To do this, the extension writes a timestamp to the shared local storage described in Section 2 whenever it runs. The app reads this timestamp locally. No page addresses or content are recorded.

If you tap "Check in Safari", the app opens an AdBlock360 web page in Safari so the extension can run once and the status can be confirmed. That page visit is a visit to our website and is covered by the Website Addendum.

4. Allowlist

Sites you allow are stored on your device only (Section 2). We do not receive your allowlist.

5. Filter Rule Updates

The app periodically downloads updated filter rules from AdBlock360 servers so that ad blocking stays effective. Downloads may happen in the background when iOS permits, and updated rules are applied the next time you open the app.

Update requests include:

• The address of the rule files requested and, where a file is already present on your device, a fingerprint of that file (the If-None-Match header) so the server can answer "not modified"
• Standard HTTP headers (for example the User-Agent) and the connection data received by our content delivery network (Amazon CloudFront, see the Core Policy, Section 7): IP address, the country derived from it, and timestamp

Rule files are delivered directly by the content delivery network; update requests do not reach our application servers. Update requests do not include a user identifier, device identifier, your allowlist, or any browsing data. The content delivery network's access logs are kept for 30 days and are processed for security and operation of the service under the Core Policy.

Rules are verified on your device before they are applied, and the app keeps the previous known-good set to fall back to.

6. Diagnostics / Crash Reporting (Sentry)

Default setting: ENABLED (opt-out available)

6.1 Data Typically Included

• Error messages and stack traces
• App version, extension version, iOS version, and device model
• Available memory at the time of an error
• Timestamp, device time zone, and device language setting
• Country, derived by our diagnostics provider from the connection at the time the report is received; the IP address itself is not stored with the report
• Sampled performance measurements: timing of app operations for a share of sessions, so we can find slow operations
• Pseudonymous installation identifiers needed to diagnose recurring issues: a random identifier created when the app is first launched, and a hash derived from the app's vendor identifier, the device model, and the app identifier. Both change when the app is deleted and reinstalled. They do not identify you and are not used for tracking.

City and region are not stored. We have configured our diagnostics provider to remove them.

6.2 What We Do NOT Collect

We configure error reporting to avoid collecting direct identifiers such as your name or email address, and we do not collect browsing history, visited websites, page content, or your allowlist for error reporting.

However, crash reports may include pseudonymous technical identifiers and device/app signals needed to diagnose recurring issues. In some cases, stack traces may include technical file paths; we take steps to minimize and redact such data where feasible.

6.3 Daily Status Signal

Once per day, the app sends a single technical status report through the same diagnostics channel. It tells us that the app is installed and which version of the filter rules it is using, so we can see whether rule updates reach our users and withdraw a faulty update if needed. Your device decides when to send it, using a date stored on the device. It contains the app version, the rule set version and date, how many of the AdBlock360 Safari extensions are turned on, whether the app may show notifications, and the pseudonymous installation identifiers described in Section 6.1. It does not contain browsing data, your allowlist, or any identifier that links the report to you. It is sent only while error reporting is enabled (Section 6.5).

6.4 Retention

• Individual reports: typically 90 days (then deleted)
• Aggregated statistics: may be retained longer for trend analysis

6.5 User Control

To disable: Open AdBlock360 → Settings → Privacy → turn off "Send anonymous error reports".

("Anonymous" in the setting name refers to minimizing direct identifiers; reports may still contain pseudonymous technical data as described above.)

Turning the setting off stops error reports from the app and from all of its Safari extensions, and also stops the daily status signal described in Section 6.3. Turning the setting off applies immediately. Turning it on applies the next time you open the app.

7. Purchases

This version of AdBlock360 for iOS is free and has no in-app purchases and no user accounts. If a future version offers paid features, purchases will be processed by Apple through the App Store, and this Addendum will be updated to describe what purchase data we receive.

8. Updates to the App

The app itself is updated through the App Store. Apple's privacy policy applies to the App Store. We do not receive personal data from Apple about app downloads or updates beyond the aggregated statistics Apple provides to developers.

9. Permissions and Notifications

The app requests one iOS permission: notifications. It asks during setup so it can remind you if one of its Safari extensions is still off. The reminders are created on your device and are not sent through any server; no data leaves your device for them. You can decline the permission, turn reminders off under AdBlock360 → Settings → Notifications → "Setup reminders", or turn off notifications for AdBlock360 in iOS Settings at any time. The app requests no other permissions (no location, no contacts, no photos, no camera, no microphone). The Safari extensions are enabled by you in Safari's settings; Safari shows you what each extension can access.

10. Children

See the Core Policy, Section 13. The app is not directed at children.