You can track a Pokémon card collection without creating an account by using a local phone app, a spreadsheet stored where you choose, or a paper checklist. The tradeoff is responsibility: without cloud sync, you need a clear plan for backup, export, device loss, and moving the collection later.
Choose the record before the tool
Decide what each row or saved card needs to contain. A useful minimum is:
- card name;
- set name and code when available;
- full collector number;
- language;
- finish and edition;
- quantity;
- condition chosen by you;
- your own photo or a reference image policy;
- date added; and
- any price source, currency, type, and observation date.
Capturing the exact printing prevents the catalog from becoming a list of ambiguous Pokémon names.
Four no-account approaches
| Method | Strength | Tradeoff |
|---|---|---|
| Paper checklist | Fully offline, durable, simple | Hard to search, duplicate, total, or update across many sets |
| Local spreadsheet | Flexible fields and easy bulk editing | Photos and exact-printing lookup require more setup |
| Local phone app | Fast photo-first workflow and collection view | May lack export, backup, or multi-device sync |
| Self-hosted database | Maximum control and customization | Requires technical maintenance and security decisions |
“No account” describes sign-in. It does not, by itself, explain network use, photo processing, analytics, payments, backup, or data retention. Review those separately.
A photo-first catalog workflow
For each physical card:
- Photograph one complete card with the bottom identifiers readable.
- Identify the likely set, collector number, language, finish, and edition.
- Verify those fields against the physical card.
- Choose condition rather than accepting an automatic grade.
- Record quantity.
- Save the source and date of any marketplace context.
- Put the physical card into its intended binder, box, or sleeve system.
The exact-printing identification guide covers step two. The record should reflect what you verified, not only what software guessed.
Foily’s current storage model
Foily does not require a Foily account. Saved card records, managed card-photo copies, condition, quantity, price snapshots, and currency preference are stored locally on the device. You can remove individual cards or clear the collection.
Identification is online: the selected scan photo is sent to Foily’s identification service, and marketplace context is fetched online. Subscription status is handled through the device’s app-store account. Read what happens to a scanner photo for the full distinction.
Foily currently has no cloud sync, multi-device collection, import, export, or automatic price refresh. A saved price is a scan-time snapshot, not a continuously updated portfolio.
Plan for device loss before cataloging hundreds of cards
Local storage can be a deliberate privacy and simplicity choice, but it concentrates the record on one device. Before investing time, ask:
- Is the app included in my device backup?
- Can I export the records in a format I control?
- Can I restore the collection after reinstalling?
- Can I move it between iOS and Android?
- Are original photos stored elsewhere?
- What happens if the app is discontinued?
Pokémon’s retired Card Dex is a useful reminder that collection tools can disappear and data transfer may not be available. Choose a workflow whose exit path matches the importance of your catalog.
Keep prices as dated notes
A no-account collection does not need a live portfolio number to be useful. If you save price context, label it with:
- active asking or completed sold evidence;
- marketplace and query;
- currency;
- sample size when known; and
- date observed.
This keeps an old amount interpretable instead of presenting it as current value months later.
The best tool is the one with an honest failure mode
A paper list survives a dead service but cannot scan. A local app removes account friction but may not sync. A cloud tracker offers convenience but depends on an account and the provider’s policies.
Choose the failure mode you can tolerate, then keep the card identity precise enough that you can move the record later.