LukyTrackThis notice explains how LukyTrack by LukyTCG handles information used to run a shared trading-card convention ledger.
Information the tracker handles
The app may handle a team member’s email address and authentication account, plus business ledger data entered into the tracker: show details, sales, purchases, trades, expenses, item descriptions, optional customer notes, values, and payment methods.
Transaction photos are saved on the originating device. Compressed copies attached to saved transactions may be synced to protected storage for authorized team members. Scanner text, image matching and barcode reading run on-device. The external Match by artwork feature has been removed; the scanner does not upload card photos to TCGTracking. Scanner learning photos are retained only if you explicitly enable the separate optional library described below.
Each scanner photo automatically creates a private scan-history entry for your signed-in account, even if you do not select a card. It stores candidate public card IDs, any selected card ID, short detected name/number, scan time, aspect ratio, a small visual fingerprint and, when enabled, pretrained visual features. Unselected results stay unconfirmed and are not used as trusted recognition labels. Selecting the exact catalogue card automatically makes that scan a trusted reference. No separate Remember action is required. This history does not store photos, full recognized text, certification numbers, grades or prices and does not fine-tune an AI model. A device cache and pending changes support offline use and cloud sync through Supabase. Other signed-in devices on your account can load the history; other team members cannot read it. Recent history and trusted references are cached on each device. You can Forget individual entries in My scan history. Forget removes their contents and suggestions across your devices after sync; a small identifier/revision marker prevents an old offline copy restoring them. Earlier confirmed corrections remain available, and their deletion identifiers can include the earlier fingerprint. Clearing browser storage removes only the device cache, not cloud history.
Visual matching starts automatically when you use the scanner. Its first use downloads about 110 MB of public runtime and full-precision pretrained DINOv2 model files from jsDelivr and Hugging Face. The model runs in a background worker on your device and compares the card with your confirmed visual references. No scanner photo is sent to these model hosts. The download may be cached by your browser; initial setup and processing time depend on the device and connection. You can stop the current scan without deleting scan history; visual matching remains enabled for future scans. If the model cannot load, the app reports this and text recognition remains available.
The optional Pokémon and One Piece scanner downloads public catalogue data and on-device text, barcode and contour-recognition libraries. Opening the scanner or camera may prepare these same libraries ahead of capture to reduce waiting; it does not upload a photo. Pricing lookups send the selected public product ID to TCGTracking for a TCGplayer reference. When configured, sold-history lookups send the public card details, condition, language and grade through a server-only SoldComps connection. Official PSA database lookup sends the entered certification number through a server-only PSA connection. Provider credentials never enter the browser. Opening an eBay sold-search link sends the card description and selected grade to eBay. Opening an official grader verification link sends the certification number to that grader. Scans suggest matches and require your review; they do not verify physical authenticity.
How information is used
Scanner learning in Settings is optional and off by default for each account/device. When enabled, selecting an exact card may retain a confidently detected inner card-front crop, its public identity, visual features, a source-photo hash and scan time on this device. The original photo and slab label are not retained by this library; uncertain crops are skipped. Check crops for accidental personal information before approving them. Only explicitly approved examples can train a small local matching layer or be exported as a private dataset. No learning photos are uploaded, and the separate cloud scan-history behaviour above is unchanged. Learning does not predict prices, grades or authenticity. You can remove individual examples, reset the matching layer, export approved crops, or delete this device’s entire learning library. Clearing browser storage loses the library unless exported. Imported authorized reference packs contain public product IDs and features, not executable models. Importing them does not authorize third-party image reuse. Device acceleration is tested against the full-precision default before use and falls back if unsupported or unsuccessful.
LukyTCG uses this information to record convention activity, calculate show performance, manage inventory and cost tracking, and let approved team members work on the current show.
Where information is stored and shared
- The app keeps an offline copy in the browser on the device in use.
- When a signed-in user reconnects, the shared ledger syncs to Supabase, which provides authentication and hosted database services.
- Google may process account information when a user chooses Google sign-in.
- If the owner enables the reporting bridge, ledger updates may be sent one-way to the LukyTCG Google Sheets reporting workbook.
LukyTCG does not sell this information. Shared-ledger access is limited to the owner and staff emails approved by the owner; staff access is restricted to the active show.
Security and retention
The shared ledger uses database access rules to limit what each approved role can view or change. No method of storage or transmission is completely secure. The owner controls the records in the ledger and may export or remove business data as needed.
Your choices and contact
You can choose email/password sign-in instead of Google sign-in. For access, correction, or privacy questions about this tracker, contact lukytcg@gmail.com.
This plain-language notice describes the current tracker. LukyTCG may update it when the app’s data practices change.