US Cop for iOS — Privacy Policy

Effective date for version 4.1: August 27, 2026. Effective date for version 4.2: October 10, 2026. Effective date for version 4.2.1: October 15, 2026. Last updated: October 15, 2026, to add the version 4.2.1 section below. On October 11, 2026 this policy was updated to add the version 4.2 section. On October 10, 2026 this policy was updated to describe the IP address, approximate location and connection details that the analytics service stores for version 4.1 (see “Stored by the analytics service” below). The copy of this policy built into the version 4.1 app is dated August 27, 2026 and does not include that addition. The copy built into the version 4.2 app is dated October 10, 2026 and includes it. The copy built into the version 4.2.1 app is dated October 15, 2026; it includes that addition and describes the diagnostic information covered in the version 4.2.1 section.

This policy applies only to the iOS app US Cop, Apple ID 394647902, bundle ID com.qbiki.UScop, published through WL Online Marketing LLC.

US Cop is independent and unofficial. It is not affiliated with or endorsed by any government or law-enforcement agency.

Version summary: US Cop 4.0 does not collect or transmit data. US Cop 4.1 adds the limited first-party installation and Apple Search Ads attribution analytics described below. US Cop 4.2 is free to download with a weekly subscription for full access, keeps full access for customers who bought the app before it became free, and adds access and verified-purchase analytics events. The section for the version installed on your device applies. No version uses data for tracking.

Version 4.0

Version 4.0 has no account system, advertising, analytics, tracking, telemetry, push notifications, or third-party SDKs. It requests no protected permissions. Directory records and source descriptions are bundled for offline use, search runs on the device, and the app does not record or transmit searches, viewed records, copied values, or preferences.

Version 4.1 analytics

Version 4.1 has no account, third-party advertising, cross-company tracking, push notifications, subscription feature, or protected permissions. It uses first-party ACAnalytics for two limited event paths:

App installation: a random install-scoped anonymous identifier, identifier for vendor (IDFV), app version, operating-system version, device model, locale, country, and currency.
Apple Search Ads attribution: when Apple makes an attribution token available, that token is sent with the anonymous identifier, IDFV, app version, operating-system version, and device model.

Stored by the analytics service: the analytics service that receives these events runs on Cloudflare. With each event it also stores the device’s IP address and Cloudflare’s estimate of the device’s location based on that IP address (continent, country, region, city, postal code, metro area code, approximate latitude and longitude, and time zone), together with the network provider (autonomous system number and organization). These are saved next to the identifiers listed above. The stored record also keeps technical details of the connection, such as the protocol and encryption (TLS) parameters, connection timing, the names of the request headers, and the Cloudflare data center that handled the request. The location is only an estimate derived from the IP address; the app does not request or access the device’s location. This information is used for analytics only and is not used for tracking.

For App Store privacy disclosures, these fields are represented as Device ID, Advertising Data, Product Interaction, Other Data, and Coarse Location (the location estimate based on the IP address). They are linked to an anonymous/device identifier and used for analytics, which includes measuring whether an install came from one of the developer’s own Apple Search Ads campaigns. US Cop has no account and these events contain no name, contact information, directory search, viewed record, copied value, purchase, or receipt.

These fields are not used to track users across apps or websites owned by other companies, are not shared with a data broker, and are not used for targeted third-party advertising. Version 4.1 does not access IDFA and does not request App Tracking Transparency permission. Purchase History and payment data are not collected.

Version 4.2 subscription, analytics and purchases

Version 4.2 is free to download. Full access to the directory needs an active US Cop Weekly auto-renewable subscription, unless the App Store confirms that the copy on the device was acquired before US Cop became free; those customers keep full access without subscribing. Version 4.2 has no account, third-party advertising, cross-company tracking, push notifications, or protected permissions. It uses first-party ACAnalytics for four limited event paths:

App installation: once each time the app starts, a random install-scoped anonymous identifier, identifier for vendor (IDFV), app version, operating-system version, device model, locale, country, and currency.
Apple Search Ads attribution: when Apple makes an attribution token available, that token is sent with the anonymous identifier, IDFV, app version, operating-system version, and device model.
Access decision: each time the app starts, when it first decides whether this device has access, and again only if that decision changes: the decision (kept from an earlier purchase, subscribed, subscription required, or purchase not confirmed), a coarse group for the app version first acquired (legacy, 4, 5, 6 or later, or unknown), and the App Store environment (production, sandbox, Xcode, or unknown), with the anonymous identifier.
Verified purchase: once for each verified US Cop Weekly transaction: after a purchase, a restore, a renewal, or an approved Ask to Buy request, and also the first time the app finds an active subscription that this installation has not reported yet (for example, after the app is reinstalled). It contains the StoreKit transaction details (transaction and original transaction identifiers, product identifier, App Store environment, purchase and expiration dates, and web order line item identifier when present) and the App Store receipt when present, with the anonymous identifier, IDFV, app version, operating-system version, and device model.

For App Store privacy disclosures, these fields are represented as Device ID, Advertising Data, Product Interaction, Purchase History (the access decision and the verified-purchase details and receipt), Other Data, and Coarse Location (the location estimate based on the IP address). They are linked to an anonymous/device identifier and used for analytics only, which includes measuring the developer’s own Apple Search Ads campaigns and subscription purchases. US Cop has no account, and these events contain no name, contact information, payment details, directory search, viewed record, or copied value.

These fields are not used to track users across apps or websites owned by other companies, are not shared with a data broker, and are not used for targeted third-party advertising. Version 4.2 does not access IDFA and does not request App Tracking Transparency permission.

Purchases: Apple processes subscription payments, and US Cop never receives payment details. The app checks the download and the subscription with Apple’s StoreKit on the device. If the App Store confirms that the copy was acquired before US Cop became free, the app keeps a small marker in the device’s keychain so that access continues offline. The marker stays on that device: it is not sent to the analytics service and is not synced or restored to another device. The app also keeps its random anonymous identifier and the identifiers of transactions it has already reported on the device, so events are not sent twice.

Network and failures: Version 4.2 makes app-owned requests only to ACAnalytics at analytics2.appchair.com and to Apple’s App Store through StoreKit. Missing configuration, unavailable attribution, serialization failure, network failure, timeouts, and server errors are ignored; a verified purchase that could not be reported is tried again the next time the app finds it. Analytics problems never delay, grant, or restrict access to the directory.

Version 4.2.1 diagnostics

Everything in the version 4.2 section above still applies to version 4.2.1 (effective October 15, 2026), with the following additions.

When the purchase record cannot be confirmed: if the app cannot confirm the App Store purchase record for the copy on the device (for example, because StoreKit reports an error, does not answer in time, or cannot verify the record), version 4.2.1 opens the directory anyway. The access event reports this decision as “purchase not confirmed”, and the app saves nothing on the device for it: it does not write or remove the keychain marker described in the version 4.2 section.

Diagnostic information: the access event also carries diagnostic information about that check:

how the check ended (verified, StoreKit reported an error, no answer in time, the record could not be verified, the record belongs to a different app, or the record was not read);
the type of any error StoreKit reported and its numeric code, and the type and numeric code of the error underneath it;
whether the record could be verified and, if it could not, the kind of verification failure;
the App Store environment named in the record (production, sandbox, Xcode, or other) and whether the record names this app’s Apple ID;
when a record was returned but could not be confirmed, a coarse group for the app version first acquired named in it (legacy, 4, 5, or 6 or later);
whether a receipt file exists on the device, and whether the system names it as an App Store or a sandbox receipt;
the app version.

This diagnostic information contains no receipt, no transaction or purchase identifiers, no dates, no names, and no free text. For App Store privacy disclosures it is represented as Other Diagnostic Data. Like the other events, it is linked to the anonymous or device identifier, is used for analytics only, and is not used to track users across apps or websites owned by other companies.

On-device data

In every version, directory records and source descriptions are bundled for offline use. Search runs on the device. Search text, viewed records, copied values, and preferences are not included in analytics. Version 4.1 stores its random anonymous identifier on the device for future analytics events.

External actions

When you explicitly choose and confirm an external action, iOS may pass the selected phone number, email address, street address, or HTTPS link to Phone, Mail, Apple Maps, or Safari. Those apps and services operate under their own terms and privacy policies. Copying a value places it on the system clipboard, which is managed by iOS.

Network and failure behavior

Version 4.0 performs no app-owned network requests. Version 4.1 makes app-owned requests only to the first-party ACAnalytics service at analytics2.appchair.com. Missing configuration, unavailable attribution, serialization failure, network failure, and server errors are ignored. Analytics never delays, hides, or restricts directory access. US Cop does not sell or rent analytics data.

Changes

If a future version changes these practices, this policy and the App Store privacy disclosures will be updated before that version is distributed.

Contact

For privacy questions about US Cop, email support@appholdings.org.