Skip to content
CardFit Scanner logo

CardFit Scanner

Ginylil • Privacy

  • Home
  • Privacy
  • Support
  • Terms
Get the app
← Back to home

Privacy

Privacy Policy

Last updated: June 6, 2026

CardFit Scanner • Ginylil

Release boundary

The normal release flow matches locally first.

CardFit is designed to keep the card photo on your device during the standard match flow. A limited lookup is only requested after a supported match needs live listing evidence.

At a glance

Card photo
Stays on your device during the standard match flow.
Collection data
Saved copies, notes, condition, and Binder placements stay on this device.
Live lookup
Uses matched card ID and finish only when listings are needed.
Accounts
No sign-in is required for the public release flow.

No account

Use CardFit without sign-in

The current release does not ask you to create an account to scan a supported card.

Collection data

Saved copies stay on your device in this release

Photos, notes, condition buckets, saved-copy timestamps, and Binder page or pocket placements are stored locally on your device in the current release.

Who we are

CardFit Scanner is a trading-card scanner operated by Ginylil. You can contact us at support@ginylil.com.

What stays on your device

In the normal release flow, CardFit Scanner processes the card match on-device. The standard path is designed so that the card photo is not uploaded to Ginylil just to identify the card. When you save a matched card to Collection, the saved copy photo, note, condition bucket, saved timestamp, and Binder placement stay on your device in this release.

Standard release flow

If CardFit cannot continue confidently, it should stop instead of silently sending the card photo or your saved collection details to Ginylil.

What may reach Ginylil

If CardFit finds a supported match and needs live listings, it may send the matched card ID, the supported scope, and the matched finish so the service can load current listings. Collection photos, notes, condition buckets, and Binder placements are not part of that lookup.

What may be sent

A card-keyed lookup request for the already matched card.

What it is for

To request live listing evidence for that matched card. CardFit does not use that lookup to build account history because this release has no accounts and no cloud collection sync.

Third-party listing content and outbound links

When current-listing evidence is available, CardFit may display listing content and images sourced from external marketplaces. If you choose to open an outbound link, you leave CardFit and continue on the marketplace site under that site’s own terms and privacy policy.

Accounts, analytics, and tracking

CardFit does not require an account and this release does not include third-party analytics or advertising SDKs.

Network and transport

In store-release builds, live listing lookups are intended to use an HTTPS API. Local HTTP exceptions in this repo exist for development builds only.

Support email and privacy requests

If you email support, we receive the information you include in the message and any attachments you send us. We use that information to answer the request and keep a support record. If you want us to delete information you sent directly by email, ask us at support@ginylil.com.

Developer-only test flows

During local development, Ginylil may use explicit test or proof flows that differ from the public release flow. Those workflows are for validation and are not the normal product behavior described on this page.

Changes and contact

We may update this policy when the product changes. For privacy questions, email support@ginylil.com.

Operated by Ginylil

  • Privacy
  • Support
  • Terms