County Names & Lines — Privacy Policy

Effective Date: August 10, 2026

County Names & Lines ("the App") is developed by Mobile Card Games & Travel Apps LLC. This Privacy Policy explains what data the App collects, how it is used, and how your privacy is protected.

1. Data We Collect

This policy covers County Names & Lines on both iPhone/iPad and Android. The App is designed to work almost entirely on your device. It collects:

• Your location (while you use the App): used to center the map on you and determine which county you are in. See the Location section below for exactly how this is handled on each platform.
• Visited counties: when the App identifies your county, it saves the county name, state, county FIPS code, and the date of the visit to a local history on your device. Your GPS coordinates are not saved in this history.
• Purchase information: if you buy County Lines Pro, the transaction is processed by Apple on iOS or by Google Play on Android. We never see your payment card details.

The App does not collect your name, email address, photos, contacts, or analytics data, and it does not show ads. On Android the advertising-identifier permission is explicitly removed from the App, so the App cannot read your advertising ID at all. We operate no servers, and the App sends nothing to any backend of ours.

2. Location

The App asks for foreground location only — "While Using the App" on iOS, and the standard location permission on Android. It never requests background location. Here is exactly what happens with your position:

• On your device: your coordinates are used in memory to position the map and match you to a county boundary. Raw coordinates are never written to storage.
• Naming your county (iOS): the App uses Apple's CLGeocoder service, processed by Apple under Apple's privacy policy.
• Naming your county (Android): the App uses the Android platform geocoder, which is provided by Google Play services. This means Google receives your coordinates to return the county and address, handled under Google's privacy policy.
• Working without sending anything (Android): county boundary data ships inside the App, so when the geocoder is unavailable the App identifies your county entirely on your device, with no coordinates leaving it.
• Map tiles: the map itself is drawn by Apple Maps on iOS and by Google Maps on Android, so the corresponding provider receives the map area you are viewing in order to send you map imagery.
• Sharing is your choice: if you tap Share, the share text you send can include your current coordinates. That only happens when you choose to share, and only goes to the people or apps you pick in the share sheet.

How often this happens is deliberately limited: the App only looks up your county after you have moved at least 20 meters, and at most once every few seconds.

You can deny or revoke location permission at any time in iOS Settings or Android Settings; the App's map and county lookup features simply won't have your position.

3. Third-Party Data Sharing

The App shares data with the following third parties, and no others:

• RevenueCat (revenuecat.com): manages your Pro purchase. RevenueCat receives purchase/transaction tokens from Apple or Google Play and a random, anonymous app-user ID — never your name, email, or location.
• Apple (iOS only): processes purchases, draws the map, and performs the county lookups described above, under Apple's privacy policy.
• Google (Android only): processes purchases through Google Play, draws the map through Google Maps, and performs the county lookups described above, under Google's privacy policy.

We do not sell, rent, or share your data with anyone else. The App contains no advertising SDK and no analytics SDK on either platform.

4. Data Storage and Retention

• On your device: your visited-county history (county, state, FIPS code, date) and settings are stored in the App's own private storage — UserDefaults on iOS, SharedPreferences on Android. County boundary reference data ships inside the App and is read-only.
• On our servers: nothing. We do not operate servers and the App makes no network requests to any backend of ours.
• Cloud backup: not used. The App does not use iCloud, and on Android it opts out of Google's automatic app backup, so your visited-county history stays on the device it was recorded on.
• Deletion: uninstalling the App deletes all locally stored data, including your visited-county history.

5. Data Security

Because your data stays on your device, there is no server-side copy of it to secure. Purchase transactions are handled over encrypted connections by Apple, Google Play, and RevenueCat, and the county boundary data bundled inside the App is stored encrypted and decrypted only in memory.

6. Your Rights

You have the right to:

• Deny or revoke location permission at any time in iOS Settings or Android Settings.
• Remove all App data, including your visited-county history, by uninstalling the App.

Depending on where you live, privacy laws such as the European Union's General Data Protection Regulation (GDPR) and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) give you rights over your personal data, including the rights to know, access, correct, and delete it. Because we do not hold your data on servers we operate, there is typically nothing for us to access or delete on request — deleting the App deletes your data. Where the App does process data in transit, or a third-party service described above collects data, you may contact us at the email below to exercise your rights, and we will respond as required by applicable law.

7. Children's Privacy

The App is not directed at children under 13, and we do not knowingly collect data from children under 13. In some regions, including the European Union, a higher minimum age applies to consent for data processing; the same statement applies there — we do not knowingly collect data from anyone under the applicable age.

8. Data Breach Notification

In the unlikely event of a data breach affecting user data on any system we operate, we will notify affected users as required by applicable law.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be reflected by updating the "Effective Date" at the top of this page.

10. Contact Us

If you have questions about this Privacy Policy or your data, please contact us at:

v5cqpsj4e3u4@opayq.com