Privacy Policy

Introduction

This Privacy Policy describes how Scott’s TCG Binder (also referred to as Bindovo) handles information. Scott’s TCG Binder is a local-first Pokémon trading-card collection application for Mac, iPhone, and iPad.

Scott’s TCG Binder does not require a Scott’s TCG Binder account. The application stores your collection primarily on your devices. Optional Apple iCloud features use your Apple Account. Optional catalog, artwork, pricing, and competitive-data features communicate with independent data providers.

This policy describes the current shipping application. It does not describe unfinished features.

2. Information Stored by Scott’s TCG Binder

The application stores information in the application’s sandbox on your device, typically in Application Support. The local database is a SQLite file. Images are stored in application-owned folders. Some preferences are stored in device-local settings.

Public catalog information and your personal collection information can exist in the same local database. Catalog records are not your personal information merely because they are stored on your device.

Public catalog information

The application can store Pokémon TCG catalog metadata such as series, sets, cards, variants, languages, rarities, gameplay information, and related reference data. This information comes from the configured catalog provider or from a catalog copy received from another one of your devices.

Personal collection information

The application can store information you create about your collection, including:

• owned cards and quantities
• condition, grade, grading company, and certification number
• language
• storage locations, binder, page, and slot
• favorites, for-trade flags, for-sale flags, and related notes
• purchase price, purchase details, asking price, and estimated values you enter
• wishlist items and tracked-set goals
• saved battle decks and deck notes
• collection activity history
• scan history, OCR text extracted from card images, and recognition results
• photographs you take or import of cards you own
• condition-analysis photos and results
• inventory-audit sessions
• price snapshots and collection valuation snapshots stored for your use

Preferences and acknowledgements

Certain application preferences and acknowledgements may be stored locally on your device. This includes your acceptance of the End User License Agreement. That acknowledgement stays on the device that accepted it. It is not stored in the collection database and is not synchronized through iCloud or local-network collection sync.

Optional eBay or PriceCharting credentials, if you enter them, are stored in the device Keychain. They are not placed in CloudKit or local-network collection sync.

This information remains on the device unless you use a feature that copies, synchronizes, exports, or backs it up.

3. Collection and User-Created Information

Your collection is yours. The application stores it so you can browse, search, value, and manage cards.

Collection information does not leave the device unless you:

• enable iCloud collection synchronization
• synchronize with a trusted Mac, iPhone, or iPad on your local network
• create a backup or export file
• share a backup or export using the operating system share sheet or a location you choose

Catalog providers used for card metadata, artwork, and pricing receive catalog identifiers and request metadata. They do not receive your notes, quantities, grades, storage locations, wishlist, or decks as part of ordinary catalog or pricing requests.

Saved decks are stored locally. If you enable iCloud collection synchronization or local-network collection synchronization, saved decks can be included with other personal collection information. Competitive tournament information that you refresh is public provider data stored locally for deck research; it is not your collection.

Scott’s TCG Binder can mark a card as available for trade. A full trade-history workbench that stores another person’s name, a trade location, or a completed trade log is not part of the current application, so this policy does not describe that kind of record.

You can create a local card record when a scan cannot be matched to the catalog. Those user-created cards stay on your devices. They can be copied over the local network to a trusted paired device. They are not synchronized through CloudKit.

4. Camera, Photos, Scanning, and OCR

Scott’s TCG Binder can identify a Pokémon trading card from a photograph.

Camera and photo library

If you grant permission, the application may:

• use the device camera to photograph a card
• let you choose an existing image from your photo library
• on Mac, import an image file you select
• use a paired iPhone as a remote camera for a Mac on your local network

The application may detect card edges, crop and correct perspective, and prepare a normalized image for recognition.

On-device recognition

Card recognition and optical character recognition run on your device. OCR uses Apple’s Vision framework locally on the device. Using that framework does not send the photograph to Apple merely because the framework is installed on the device.

Recognition may read printed card information such as name, collector number, printed set total, set code, HP, stage, attacks, weakness, resistance, regulation mark, illustrator, and similar text that appears on the card. That printed information is used to match the card against the local catalog. Printed trading-card text is not treated as personal information.

The application does not upload scan photographs to a remote recognition or OCR service. During matching, the application may download official catalog artwork so it can compare the local scan with reference images. That download is catalog artwork, not an upload of your photograph.

Saved scan information

Depending on your scan-image retention setting, the application may save original, cropped, and recognition images in application storage, together with OCR text and match results in the local database. You can choose to keep scan images always, only for confirmed cards, only for unidentified cards, or never.

Scan history, OCR results, and scan photographs stay on the device. They are not synchronized through CloudKit, and they are not included in local-network collection synchronization. They can be included in a backup you create if you choose to include images.

If you use the iPhone as a remote camera for a Mac, live preview frames and captured stills travel over your local network to that Mac using Apple’s Multipeer Connectivity. They are not sent to a Scott’s TCG Binder server.

5. Card Catalog and Artwork

Scott’s TCG Binder uses a replaceable catalog-provider architecture. The current production catalog provider is TCGdex.

When catalog information is downloaded, the application requests public catalog resources such as series, sets, cards, languages, taxonomy, and official artwork. Those requests are ordinary HTTPS requests. They can include a product user-agent and may expose technical information that any internet request exposes, such as IP address and standard HTTP request information. They do not include your collection ownership, notes, or scan photographs.

Official catalog artwork is downloaded from the provider’s asset host and cached locally, typically as card image files such as large.webp and small.webp. Those images are provider artwork. They are not photographs you took.

You can clear the catalog image cache in Settings. Clearing that cache does not delete your collection photographs or scan images. Cached official artwork may also be removed automatically if the cache grows too large.

A Mac can also send a local catalog snapshot to a trusted iPhone or iPad over your local network. That snapshot is catalog reference data, not your personal collection.

6. Pricing Information

Pricing uses a replaceable provider architecture. The current production pricing source is the configured catalog provider, presently TCGdex. Pricing requests ask for public card pricing associated with a catalog card identifier, name, set, collector number, language, and variant information. They do not send your quantity, notes, storage location, or other private collection fields.

Returned quotes can be stored locally as price snapshots and used for on-device collection valuation. Those snapshots stay on the device. They are not synchronized through CloudKit or local-network collection sync.

Settings can store optional eBay or PriceCharting credentials in the device Keychain. The current application does not send your collection or live pricing requests to eBay or PriceCharting. The application can build an eBay search link from public catalog information such as card name, set name, and collector number. Opening that link is a user action in the system browser.

If a later release enables additional pricing providers, this policy will be updated before that behavior ships.

7. iCloud and CloudKit Synchronization

iCloud synchronization is optional. If you enable it, selected personal collection information is synchronized using Apple’s CloudKit service in the private CloudKit database associated with your Apple Account.

The application developer does not receive your Apple Account password. CloudKit storage and access are also governed by Apple’s privacy and iCloud policies:

• Apple Privacy Policy
• Apple iCloud Terms

When enabled, CloudKit can synchronize personal collection state such as owned cards, quantities, favorite and trade flags, grades, notes, locations, wishlist items, tracked-set goals, activity, saved decks, and related user-created collection metadata. Personal collection photographs are not uploaded by default. If you enable personal-image synchronization, those photographs can be stored as CloudKit assets in your private database.

Public catalog tables, official artwork caches, pricing snapshots, scan history, OCR results, recognition indexes, and competitive tournament caches are not CloudKit members.

This policy does not claim end-to-end encryption for CloudKit data. Apple provides the CloudKit service and its protections.

You can keep the collection on the device only, pause or disable CloudKit, or delete CloudKit collection data from Settings. Deleting the application without deleting iCloud data may leave synchronized collection information in your iCloud account until you remove it through the application or Apple’s iCloud controls.

8. Local Network Device Synchronization

Scott’s TCG Binder can discover nearby copies of the application using Bonjour on your local network. Local-network access is requested so your Mac, iPhone, and iPad can find one another and communicate directly. No Scott’s TCG Binder server sits in the middle of that connection.

The first connection asks you to allow the nearby device. After you trust a device, later connections can use that trust until you change it.

Local-network communication uses Apple’s Multipeer Connectivity with encryption required by the session. This is transport encryption provided by Apple’s framework, not a separate Scott’s TCG Binder cryptographic product.

Catalog synchronization

Catalog sync copies a public Pokémon catalog snapshot from a Mac to a nearby iPhone or iPad. It does not copy your owned cards, notes, wishlist, decks, or personal photographs.

Collection synchronization

Collection sync copies personal collection information between trusted devices, including owned cards, locations, flags, wishlist items, tracked sets, activity, saved decks, user-created cards, and collection photographs. Scan history and OCR results are not part of this transfer.

Remote camera

A trusted iPhone can send live camera preview frames and still photographs to a Mac over the same local-network session so the Mac can scan cards.

Temporary transfer files are removed after a session. Information that was applied to the receiving device remains there as local application data.

9. Backups and Restore

You can create a personal backup from the application. A backup can include the collection database and, if you choose, personal images such as collection photographs, scan images, condition images, and user-created card images. Official catalog artwork caches are not included.

On Mac, you choose the destination folder. On iPhone and iPad, the backup is prepared locally and you can share it through the system share sheet to a location you control.

Backups are not encrypted by Scott’s TCG Binder. They use checksums to verify that files copied completely. After a backup leaves the application, you are responsible for where it is stored, who can open it, and when it is deleted.

A backup can contain collection information, notes, decks, scan history, and images if those records existed on the device and you included images. Optional provider credentials are not intended to be stored in backups.

Restoring a backup replaces the local collection database with the backup you select. Existing backup files are not deleted when you later purge personal data inside the application.

10. Third-Party Services

Scott’s TCG Binder may contact independent services when you use catalog, artwork, pricing, competitive-deck, or Apple cloud features. Those services have their own privacy policies.

Current catalog and artwork provider

The current catalog provider is TCGdex. The application requests catalog metadata and official artwork from TCGdex systems such as api.tcgdex.net and assets.tcgdex.net.

• TCGdex
• TCGdex API documentation
• TCGdex Terms and Conditions

The catalog provider can be replaced in a later release. If that happens, this policy will be updated to name the new provider.

Competitive tournament data

If you refresh competitive deck information, the application can request public tournament and standings data from Limitless TCG. Those requests include game and format information. They do not include your collection.

• Limitless TCG Privacy Policy

Apple services

Optional iCloud synchronization uses Apple CloudKit. Operating-system components such as Vision, Multipeer Connectivity, and Apple crash reporting are provided by Apple on the device or through Apple’s platforms.

• Apple Privacy Policy

When the application contacts a third-party service, that service can receive the technical information that normally accompanies an internet request, such as IP address and HTTP headers. Scott’s TCG Binder does not send your private collection notes or ownership records to catalog, artwork, pricing, or competitive-data providers as part of those requests.

11. Analytics, Advertising, and Tracking

We do not use third-party advertising or behavioral analytics SDKs.

Scott’s TCG Binder does not display advertising. It does not sell personal information. It does not use advertising identifiers for cross-app or cross-website behavioral tracking. It does not include App Tracking Transparency tracking for advertising.

The application includes on-device collection summaries and charts. Those screens use your local collection data so you can see your own inventory and value. They are not advertising analytics and are not sent to an analytics company.

12. Diagnostics and Crash Information

The application writes diagnostic messages locally using the operating system’s logging facilities. Those logs stay on the device unless you export them or unless the operating system includes them in a report you choose to send.

Scott’s TCG Binder does not include a third-party crash-reporting SDK such as Firebase Crashlytics or Sentry.

If you install the application from the App Store or TestFlight, Apple may collect crash and diagnostic information according to your device settings and Apple’s policies. The application developer receives Apple crash reports only if Apple makes them available through App Store Connect and you have not disabled sharing. This policy does not claim that the developer automatically receives Apple diagnostic data.

13. Data Retention

Because Scott’s TCG Binder is local-first, retention is controlled mainly by your devices and by the features you use:

• Local collection data remains until you remove it, purge personal data, delete the application, or restore a different backup.
• Cached catalog artwork remains until you clear the image cache, the application evicts old artwork, or the application data is removed.
• Scan images remain according to your scan-image retention setting and whether you later delete scan history or purge personal data.
• CloudKit data remains according to the application’s deletion behavior and Apple’s CloudKit and iCloud systems.
• Local-network copies remain on each device that received them until removed on that device.
• Backup files remain wherever you chose to store them.
• License acceptance and similar acknowledgements remain in device-local settings until the application data is removed or a later agreement requires a new acknowledgement.

The developer does not operate a separate Scott’s TCG Binder account database of your collection.

14. Your Data and Deletion

You can remove information inside the application. There is not a single button labeled “Delete All My Data.” The available controls are:

• Individual collection cards: edit or delete owned cards in Collection.
• Wishlist and tracked sets: remove items in Wishlist and Tracked Sets.
• Decks: delete saved decks in Decks.
• Scan history and scan images: manage scans in Scan History and choose a scan-image retention setting in Settings.
• Cached official artwork: use Clear Image Cache in Settings.
• Personal collection bulk removal: Settings → Advanced → Personal Data → Purge My Collection. This removes ownership and related personal data from the device and can optionally include wishlist, tracked sets, saved decks, and scan history. It preserves the downloaded public catalog. You can apply the purge to this device only, or to this device and iCloud.
• iCloud copy: disable CloudKit, delete CloudKit collection data in Cloud Sync settings, or include iCloud in a personal-data purge.
• Local-network copies: after a purge, local collection sync is paused until you resume it. Delete or purge data on each device that still holds a copy.
• Backups: delete backup folders or shared files in the location where you stored them. The application does not delete those files for you.
• Entire local application data: delete the application, or remove the application’s data using the operating system.

Purging personal collection data does not delete existing backup archives, official catalog metadata, or cached official artwork unless you clear or delete those separately.

15. Data Security

Scott’s TCG Binder uses the protections provided by Apple platforms, including application sandboxing on iOS, iPadOS, and the sandboxed Mac application. The local SQLite database and images live inside the application’s container.

External catalog, artwork, pricing, and competitive-data requests use HTTPS.

Optional CloudKit synchronization uses Apple’s CloudKit service and the user’s Apple Account.

Local-network synchronization requires user approval of the nearby device and uses Multipeer Connectivity with encryption required. Trusted-device names are stored locally so you do not have to approve the same device every time.

No method of storage or transmission is perfectly secure. If you export or back up collection information, protect those files as you would any other personal document.

16. Children’s Privacy

Scott’s TCG Binder is a trading-card collection utility. It does not include social networking, public profiles, advertising, or behavioral tracking. It does not ask for a child’s name, email address, or similar contact information in order to use the collection features.

A parent or guardian can use the same on-device deletion, backup, and permission controls described in this policy. Camera, photo-library, local-network, and iCloud access are controlled by the operating system’s permission prompts.

App Store age rating is configured separately in App Store Connect. This policy describes the application’s data practices rather than a legal age gate.

17. International Users

Scott’s TCG Binder is a local-first application. The developer does not operate a centralized Scott’s TCG Binder service that stores your collection. Information that leaves the device does so through Apple services you enable, local-network connections you approve, backups or exports you create, or third-party catalog, artwork, pricing, and competitive-data requests described above.

If those third-party or Apple services process information in other countries, their policies apply to that processing. You can use the deletion and permission controls in this policy regardless of where you use the application.

18. Changes to This Privacy Policy

This Privacy Policy will be updated when the application’s data practices change, including new network services, analytics, accounts, cloud synchronization, or personal-data handling. The Last Updated date at the top of this page will change when the policy changes.

This Privacy Policy is published at https://phpscott.github.io/ScottsTCGBinderLicenses/privacy/.

19. Contact Us

Privacy questions about Scott’s TCG Binder can be sent through the support page for this application:

https://phpscott.github.io/ScottsTCGBinderLicenses/support/

You may also use the support contact listed with Scott’s TCG Binder on the App Store.

20. Pokémon and Third-Party Trademarks

Pokémon and related names and images are trademarks of their respective owners. Scott’s TCG Binder is an independent application and is not affiliated with, endorsed, sponsored, or approved by The Pokémon Company, Nintendo, Game Freak, or Creatures.

TCGdex, Limitless TCG, eBay, PriceCharting, Apple, iCloud, CloudKit, and other product names are trademarks of their respective owners.