YOUR CARDS. YOUR CHOICES.

Privacy Policy

Cardalog keeps your collection on your device. That does not mean every part of the app is offline or telemetry-free.

Effective date: October 11, 2026. This policy describes Cardalog 1.0.0 for iOS and Android, provided by Leech Labs. For privacy questions, contact support@leechlabs.io.

1. Your collection and card photos

Collection records, binders, pocket assignments, notes, tags, purchase details, user-entered value estimates, activity, and saved card photos are stored in the app on your device. Cardalog does not create a Cardalog account, synchronize your vault to our servers, or automatically upload your card photos in this release. The app does not collect your device's geographic location. Locations you enter for cards are collection labels, not GPS readings.

The camera and system photo picker are used when you choose to capture or select a card image. Recognition and the included reference pack run on your device. Cardalog's OCR integration does not send the image or its recognized text to Google for recognition. The operating system may manage backups or photo-library copies separately from Cardalog.

2. Google ML Kit diagnostics and usage data

The app uses Google's ML Kit text-recognition SDK on iOS and Android. Although recognition is local, Google documents collection of device model and operating-system information, available machine-learning hardware, app identifier and version, per-installation identifiers, performance measurements, recognition configuration, feature events, and error codes for diagnostics and usage analytics. These SDK events can be transmitted to Google; Cardalog does not provide an in-app switch that disables all ML Kit telemetry. This diagnostic information is distinct from your card photos and recognized card text.

Google's documented practices and retention controls apply to information handled by Google. See the iOS disclosure, Android disclosure, ML Kit terms and privacy information, and Google Privacy Policy. Cardalog does not represent this data as ephemeral or promise that deleting the local vault removes Google's diagnostic records.

3. Requested market lookups and external links

If you request a supported market estimate, Cardalog sends a card identifier to the Pokémon TCG API or a card-name/set-printing query to YGOPRODeck. The providers receive the request and normal network information, such as your IP address. These requests support the result you requested; your complete collection, notes, purchase history, and photos are not attached to the market request. Provider prices may originate from other catalog or marketplace sources.

Catalog providers control their own request handling and logs. We do not claim they process every request without retaining data. Information about their services is available from Pokémon TCG API and YGOPRODeck's privacy policy.

Opening an eBay sold-listing search sends its search terms to eBay in an external browser or app. Other external links, including published card checklists, are handled by their destinations. Those services' own privacy and cookie practices apply; Cardalog does not control external websites or provide an integrated eBay transaction feed.

4. Exports, sharing, and support

When you use the system share sheet, collection information in your CSV export is sent to the app, person, or service you choose. Review the export before sharing; it can contain notes, locations, and purchase information. Cardalog does not automatically send that export to Leech Labs.

If you email support, your email address, message, and any attachments you choose to send are handled by our email provider and Leech Labs to respond to your request, investigate the issue, and manage related correspondence. Do not send passwords, payment-card details, signing keys, or images containing unrelated personal information. Contact us to request access to or deletion of support correspondence; we will review the request and any applicable obligations. No fixed response time or automatic mailbox deletion interval is promised.

5. Ads, accounts, purchases, and cloud services

This release does not contain advertising, an advertising SDK, paid subscriptions, or in-app purchases. It does not ask you to sign in. Collection purchase amounts are records you enter; Cardalog does not process a card purchase or collect your payment credentials. Backend and model-development tools used during development are not a cloud upload or sign-in feature of this release. Later features that change these practices require an updated policy and store disclosures.

6. Retention, deletion, and your choices

Your local vault remains on your device until you delete it, remove the app's stored data, or otherwise remove those files. To remove the full local vault and saved app photos, open Settings → Delete all local data and confirm. Export a backup first if you need to retain your records. You can also remove individual collection copies through the app; this is not a promise that every previously saved image file or backup is removed.

Deleting local data does not delete your original photo-library images, device/cloud backups, files shared with others, support emails, or records independently held by Google, catalog providers, or external websites. Manage these copies with the relevant operating-system or service controls, or contact the applicable provider. Cardalog has no account to close and no account-deletion login flow in this release.

You can deny or revoke camera/photo permissions in the device's settings, use manual entry instead of scanning, and avoid optional market requests and external links. The app does not offer a guaranteed opt-out of all SDK network diagnostics. Device backup behavior depends on your operating-system and backup settings.

7. Security and service providers

The app uses its operating-system application storage for local files. Market endpoints, this website, and Google's documented SDK telemetry use HTTPS. These measures do not guarantee absolute security, end-to-end encryption, or protection on a compromised device. Use device access controls and take care when sharing exports.

Google handles OCR SDK diagnostics; public catalog services handle requested lookups; your selected sharing destination handles exports; our hosting and email providers handle website requests and support correspondence. Website requests can produce normal hosting/security logs containing request and network information. This policy website adds no advertising, analytics scripts, account form, or visitor-editing feature. Provider-specific retention is governed by their practices and is not represented as a universal fixed period by Leech Labs.

Information sent to these providers may be processed in countries other than your own. Leech Labs does not sell your local vault or use the app to target advertising. This statement does not replace the independently applicable policies of an external site you choose to visit.

8. Changes and contact

We will update this page and its effective date when Cardalog's relevant practices change. Depending on the change and applicable requirements, additional in-app information or consent may be needed. This policy does not claim support for an unimplemented cloud, deletion, or privacy-control feature.

Privacy and support contact: support@leechlabs.io. Visit Cardalog Support for backup and local-data deletion instructions.