BrightPath Collect privacy

Updated October 22, 2026 · BrightPath Collect 1.1

Local collection data

BrightPath Collect stores collection records, personal photos, goals, wishlist entries and manual sale/trade/reversal history in local app storage. The app has no account, advertising, analytics or automatic collection synchronization.

Optional Pokémon catalog lookup

When you choose Search, the app sends your search term to TCGdex. Choosing a printing requests its record ID. The provider receives ordinary network information such as your IP address and the app’s request header. Your collection, personal photos, grading certificates, acquisition costs and notes are not sent by this lookup. Use collectible names only, and avoid entering private information into the catalog search box. Manual entry remains available without using this service.

Provider handling

TCGdex’s published website privacy policy (effective July 15, 2024) states that it collects no personal information and describes non-personal website analytics through Plausible with EU processing. That policy does not explicitly describe public API request logging or retention. This app’s native API lookup does not load the provider’s website analytics scripts. TCGdex supplies community text metadata. BrightPath Collect uses temporary network sessions without app cookies, credential storage or a persistent response cache. These app settings do not determine whether TCGdex or its infrastructure retains requests. TCGdex’s published API server code includes request-path and query logging and optional error reporting; its live configuration and retention periods remain unconfirmed. TCGdex’s published privacy policy does not explicitly describe API log retention. Search terms, selected record IDs and ordinary connection metadata reach its infrastructure; its live logging configuration and retention are not verified. We conservatively disclose that search terms and request metadata may be retained and linked to you for app functionality. Live retention and identity linkage remain unverified; no tracking use is evidenced.

Personal photos

Camera permission is requested only when you choose camera capture. The system Photos picker lets you select individual images. Saved images are resized/oriented JPEGs with original location and EXIF metadata omitted. Keep originals separately if you need them.

Backups and recovery

At your direction, Files exports complete unencrypted .collecthistory backups containing retained copies, photos, plans and history. Your selected storage provider may apply its own protection or synchronization. Review its policies and keep exports private. Recovery snapshots remain on the same device; keep a private off-device export too. Reviewed migrations retain original legacy files.

Removal and retention

Removal controls can remove eligible copies/photos from the current collection after review. They do not erase prior recovery snapshots, legacy files or separately exported backups. Copies/photos referenced by history cannot be removed using those controls, even after reversal. A history reversal restores ownership; it does not delete the original event. Removing the app can remove its local records and recovery files; separately exported files remain at their chosen destinations and device/provider backups follow those services’ settings. Export what you want to keep before uninstalling.

Support

Contact pedro.ignacio@brightpathventuresgroup.com. Email support is separate from the app’s local collection storage. Information you choose to send in email is handled through Google Workspace and Outlook, which can synchronize copies through Microsoft’s cloud; avoid sending complete backups, personal photos, certificates or private notes. No fixed support-email deletion schedule is currently in effect. A proposed retention schedule is awaiting verification of mailbox-provider deletion, recovery and backup behavior; it has not been implemented. Do not send sensitive collection data for routine support.

Selected recovery removal

In Recovery snapshots, Review removal identifies one file before a separate permanent-delete confirmation. Export original file is available before removal. This removes only the selected recovery payload; the current collection, migration originals, other snapshots, external backups and operation records remain. A removal receipt remains visible if refreshing the file list fails. Refresh before selecting another removal. Interrupted retained files can be inspected and exported. Removal does not guarantee secure erasure or reclaimed storage. No automatic pruning occurs.

Retained recovery retry

A verified file retained after an earlier removal can be reviewed again using Review removal retry. A fresh review and separate permanent confirmation authorize one attempt. Unknown, partial or changed operation records block retry and remain preserved; verified bytes can still be exported. Repeated refresh failures preserve the recorded outcome and require successful refresh before another removal. No automatic retry or operation-record cleanup occurs.