A Pokémon card scanner can identify an image on the device or send it to an online service. The app may then save a copy locally, retain it remotely, pass it to another processor, or discard it after the request. “No account” only means there is no app-specific sign-in; it does not answer any of those data questions.
Four separate stages to check
1. Capture
The app receives a camera photo or an image selected from your library. Check whether it asks for the whole library or only the photo you choose. Modern platform permission flows can support limited selection, but the app’s implementation matters.
2. Identification
An on-device model can analyze the image without sending it to a server. An online model requires transmission. Some apps combine both approaches—for example, local cropping followed by online recognition.
3. Saved collection
The identification result and photo may be stored locally, synced to a cloud account, or both. This is a different question from how the scan was processed.
4. Supporting services
Subscription providers, analytics, crash reporting, advertising, and marketplace integrations can process other information even when the collection itself stays local.
Questions worth asking before scanning
- Does the selected photo leave the device?
- Which service receives it, and for what purpose?
- Is the image retained after identification? For how long?
- Is it used to train a model?
- Are card photos saved locally, in a provider account, or both?
- Can I delete individual photos and the entire collection?
- Does deleting the app remove the only copy?
- Is an account required?
- Are analytics or advertising identifiers involved?
- Does the privacy policy match the App Store privacy label?
Apple’s privacy guidance distinguishes data processed only on-device from data transmitted off-device. It also requires developers to account for relevant third-party partner behavior in App Store privacy disclosures. The label is a useful starting point, not a substitute for the privacy policy and actual app behavior.
Foily’s current data flow
Foily has no Foily account or sign-in flow. Its current scan path works like this:
- You take a card photo or choose one from your library.
- The app prepares a smaller JPEG for identification.
- The selected image, display currency, and device-region code are sent to Foily’s online identification service.
- The service uses a third-party image model to propose a likely printing and alternatives.
- Foily fetches a current general market value when one is available for the exact matched printing.
- If you save the card, its record and managed photo copy live in local app storage on your device.
The current service code has no database or object-storage binding for scan photos, but infrastructure and third-party processing still exist. Do not summarize this as “everything stays on your phone.” The accurate statement is:
Your saved collection and card photos are stored on your device. A selected scan photo is sent online for identification.
No account: useful, but not the same as offline
Removing an app-specific account can reduce setup and eliminate one cloud identity. It can also mean no cross-device sync, web access, or account-based recovery.
Foily currently has no cloud collection sync, import, or export. Subscription access uses the Apple or Google store account associated with the device. Identification and marketplace context need a network connection.
See how to track a Pokémon card collection without an account for the backup and portability tradeoffs.
Photo privacy and card privacy are different
A card photo usually does not contain the same information as a portrait or identity document, but the surrounding image can reveal a desk, room, labels, hands, mail, or other objects. Frame only the card and use a plain background. That also improves identification quality.
The card-scanning photo guide shows how to keep the full card visible without capturing unnecessary surroundings.
Recheck after meaningful app changes
Data behavior can change when an app adds cloud sync, a new recognition provider, analytics, account features, or exports. Treat privacy claims as versioned product facts, not permanent slogans. Review the current store label and privacy policy after major updates.