Conflx Privacy Policy

The short version

• We collect what the product needs to work: your email, your card inventory, and — if you sell — the minimum needed to route payments and orders. Payment and identity verification data goes to Stripe, not to us.
• Card recognition runs in your browser or on your device. Recognition requests to our servers contain numeric image fingerprints and recognized text, not your camera feed. When you confirm a scan, a cropped image of that card may be uploaded to private storage to improve recognition accuracy (details below).
• We don't run advertising, ad trackers, or third-party analytics, and we don't sell your data.
• You can delete your account (and the data that goes with it) yourself, in-app.

What we collect

Account data. Your email address and a password. Passwords are handled by our authentication provider (Supabase Auth) and stored only as salted hashes — we never see or store your plaintext password. If you sign in with Google (available soon), we receive your name, email, and profile picture from Google instead of a password. You may optionally upload an avatar image.

Collection and inventory data. The cards you catalog: card identities, quantities, conditions, languages, foil status, the storage locations you define (boxes, binders, decks, shelves), prices you record as paid, and the history of changes to all of it (scans, moves, sales, and similar events, with timestamps). This is the core of the product and it is treated as your private data — it is not visible to other users unless you explicitly list items for sale or share something.

Scan data (card recognition). This is the part of the product most worth being precise about, because it involves your camera. Here is exactly what happens.

Recognition runs on your device. When you scan, your camera feed is processed locally — in your browser on the web, or on your device in the mobile app. The live video is never streamed or uploaded to us. The app turns what the camera sees into a numeric embedding (a mathematical fingerprint of the card's art) and reads the card's text (name, set code, collector number) on-device.

What reaches our servers during recognition. To identify a card, the app sends the derived embedding and the recognized text to our recognition service, which matches them against our card catalog and returns candidates. This derived data describes the card, not you; the embedding cannot be turned back into the original photo. It is used to answer "which card is this?" and is not built into a profile of you.

The one place an image is stored. When you confirm a scan, the app uploads a single cropped still image (JPEG) of that card, together with a record of the recognition result and which card you confirmed, to a private storage area tied to your account. We do this to measure and improve recognition accuracy — including evaluating and training the recognition models that make scanning work. Being fully honest: these images are of trading cards, but they come from your camera, so a frame can incidentally include your fingers, desk, or surroundings at the edges.

How that scan data is handled:

• Private. Stored in a non-public bucket, access-scoped to your account. Not shown to other users, not shared with third parties, not sold.
• Retained while your account exists, so the recognition quality data accumulates. Deleting your account deletes these images and their records (our account-deletion function purges the scan storage before removing the account — see "Deleting your account"). Copies already added to our de-identified training corpus (described next) may be kept after that.
• Purpose-limited to making recognition work and improving it. We do not use scan images for advertising or sell them.

The de-identified training corpus. To keep improving recognition, confirmed scan images may be copied into an internal training and evaluation corpus in de-identified form: the corpus stores the image and which card it shows — never your name, email, or account ID. When you delete your account, the server-side records that could link a corpus image back to you are destroyed, so corpus copies made before deletion become permanently unlinkable to you and may be retained and used for model training and evaluation after your account is gone. We do not attempt to re-identify corpus images, and the corpus is internal — not shared, published, or sold. Recognition models trained on the corpus do not contain your images, so account deletion does not affect previously trained models.

Your control over scan data.Today, confirmed-scan images are saved automatically to your private area and used to improve recognition. If you'd prefer we not keep yours, email legal@conflx.appand we'll delete the images tied to your account and stop saving new ones; deleting your account removes all account-linked images. Corpus copies that have already been de-identified can no longer be traced back to you and may be retained as described above. We're building a self-serve setting to turn scan-image saving on or off, and this policy will be updated when it ships.

Offline scans. If you scan without a connection, frames are queued locally on your device and identified when you reconnect — nothing leaves the device until then.

Sharing decks. Decks are private by default— nothing about your collection is visible to anyone unless you choose to share it. If you set a deck to "unlisted" or "public," that deck — its name, format, card list, cover image, and your display nameas the author — becomes visible to anyone who has its link (an unguessable web address under conflx.app/d/). Unlisted decks are reachable only by the link and are excluded from search engines; today, public decks are excluded from search engines too, because in-app deck discovery hasn't launched — we'll update this policy if that changes. You can switch a shared deck back to private at any time, which immediately stops the link from working. Your display name is a handle you choose — it does not have to be your real name. Sharing a deck shares only that deck: not your inventory, quantities you own, prices, locations, or anything else in your account.

Seller data. If you connect payments to sell through Conflx, you onboard with Stripe(see "Processors" below). Your identity verification (KYC), bank details, and tax information go directly to Stripe under Stripe's privacy policy — we never receive or store them. What we store is your Stripe account identifier and status flags (e.g., whether charges are enabled). If you connect an external marketplace (such as eBay or CardTrader), we store the access credentials needed to act on your behalf there (an OAuth token, or an API token you generate), your listings, and your order data. These credentials are encrypted at rest, never displayed or shared, and deleted when you disconnect the marketplace or delete your account.

Buyer and order data. If you buy from a seller on Conflx, your payment is processed by Stripe; we never see your card number. We store the order itself: what was bought, from whom, for how much, and the shipping details needed for the seller to fulfill it. Order details are shared with the other party to the transaction — that's what they're for.

Technical data. Like almost every web service, our hosting and backend providers keep standard server logs (IP address, browser type, timestamps, requested URLs) for security and debugging. We do not use these to profile you. We currently run no third-party analytics, advertising trackers, or session-recording tools.

Cookies

We use cookies only for authentication — keeping you signed in to app.conflx.app (set by our auth provider, Supabase). These are strictly necessary cookies; there are no advertising, analytics, or cross-site tracking cookies. That is why you don't see a cookie consent banner: there is nothing optional to consent to. If we ever add optional cookies, we will add a consent mechanism first and update this policy.

Who processes your data

We are a small operation and use established providers rather than running our own infrastructure. Our application data is hosted in the United States. Each of these providers acts as our processor under a data processing agreement and may only use your data to provide their service to us — not for their own purposes.

We do not sell personal data, and we do not share it with third parties for their own marketing.

We may disclose data if legally required (e.g., a valid subpoena), to prevent fraud or abuse, or as part of a business transfer (e.g., if Conflx is acquired — in which case this policy would continue to apply to data collected under it, and we would notify you).

How long we keep it

• Account and inventory data: for as long as your account exists.
• Scan images and recognition records:images and records tied to your account — for as long as the account exists, then deleted with it. (If you opt out or delete individual scans once those controls ship, they go sooner.) De-identified corpus copies, which cannot be linked back to you, may be retained indefinitely (see "The de-identified training corpus").
• Order and transaction records: retained after account deletion where we have a legal obligation to keep them (tax and accounting records), and then deleted.
• Fraud and abuse records: where an account has been flagged for abuse, we may retain the minimum records needed to detect and prevent further abuse (a recognized exception to deletion rights under the CCPA and GDPR).
• Server logs:kept on our providers' standard short retention schedules.

Deleting your account

You can delete your account from within the app. Your account is deactivated immediately — you are signed out and the account and its data are no longer accessible. Permanent deletion completes within 30 days. During that window we may run routine anti-abuse and data-integrity checks (a recognized purpose under the CCPA and GDPR), and if you deleted by mistake, email legal@conflx.apppromptly — where the data has not yet been permanently deleted, we can restore the account. After the window, deletion is permanent and not recoverable: it removes your authentication record, profile, inventory, locations, scan history, uploaded images, and marketplace connections. Transaction records that we must keep for tax or legal reasons are retained per the section above; records needed to prevent fraud or abuse may be retained where the law allows; and de-identified scan images in the training corpus — which can no longer be linked to you once your account records are destroyed — may be retained per "The de-identified training corpus" above. You can also email legal@conflx.app to request deletion.

Your rights

Depending on where you live (including under the EU/UK GDPR and the California CCPA/CPRA), you have the right to:

• Access the personal data we hold about you, and get a copy of it;
• Correct inaccurate data (most of your data — your inventory — is directly editable in-app);
• Delete your data (see above — self-service, no justification needed);
• Port your data (collection export tools are part of the product; anything not exportable in-app, ask us);
• Object to or restrict certain processing.

To exercise any of these, email legal@conflx.app. We will respond within the timeframe the applicable law requires (30 days under GDPR, 45 under CCPA). We do not discriminate against you for exercising privacy rights.

For California residents:we do not "sell" or "share" personal information as the CCPA defines those terms, and we have not done so in the preceding 12 months. We collect the categories described in "What we collect" for the purposes described there.

For EU/UK residents: our legal bases are performance of contract (running the service you signed up for), legitimate interests (security, preventing abuse, and improving recognition accuracy), and consent where required. You may lodge a complaint with your local supervisory authority.

Where your data is processed

Conflx is based in the United States and processes data on US-based infrastructure. If you use Conflx from the European Economic Area, the United Kingdom, or elsewhere outside the US, your data is transferred to and processed in the United States. Where the law requires a transfer safeguard, we rely on the Standard Contractual Clausesincluded in our providers' data processing agreements (for example, Supabase and Stripe), which contractually extend protections to your data when it is processed in the US. If you have questions about these safeguards, email legal@conflx.app.

Children

Conflx is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child under 13 has created an account, contact legal@conflx.app and we will delete it.

Changes

We will update this policy as the product evolves (for example, when mobile apps ship or new integrations launch). Material changes will be announced in-app or by email before they take effect, with the effective date updated above.