FAQ

This is the deep version of the FAQ. The short version lives on the marketing FAQ and inside the app on the Support page — both render the same shared question set. This page goes further than those summaries, and where the two disagree, the answer here is the one measured against the shipped product.

DeckScope is in open beta. Anyone can register, paid plans are live, and the product is still changing: features may be added, altered, or withdrawn between releases. Beta does not mean subscriptions are provisional.

Pricing

What plans exist?

Four plans: a free tier plus three paid tiers. The canonical prices are published on the pricing page and mirrored in the app’s subscription screen.

Both surfaces read the amounts from one source (packages/shared-contracts/src/pricing.ts), and a test pins them against the in-app presentation copy so the two cannot drift apart silently. This page deliberately does not restate the amounts — a number copied into documentation is a number that goes stale. Always treat the pricing page and the checkout total as authoritative.

Paid plans are billed monthly, in advance, and renew automatically until you cancel. Prices shown at checkout include tax where your country requires it.

Is there a trial?

Not as a self-serve button today. Trials exist on the entry-level paid tier, but there is no control anywhere in the app that starts one — the activation flow is built and reachable by the API, not yet mounted in the interface. If you want a trial, ask for one through the contact route below, the same way a downgrade is handled.

Once a trial is running, the app does show it: a banner names the tier and counts down the days remaining. Only the entry paid tier is trial-eligible.

How do I upgrade?

Two routes exist, and which one you see depends on the plan you are moving to:

• Self-serve checkout. The app mints a Lemon Squeezy hosted checkout URL and sends you there. Your account and the target plan are stamped into the checkout, so entitlements are provisioned automatically when the payment webhook lands.
• Upgrade request. For plans not opened to self-serve checkout, the app files a request that an operator resolves. You can hold only one open request at a time. While yours is open every plan tile is disabled and reads “Upgrade requested”, so there is no self-serve way to change it, withdraw it, or file a different one — wait for the operator to resolve it, or use the contact route below.

How do I downgrade?

There is no self-serve downgrade path today. The implemented flows are cancel and upgrade, not “switch to a cheaper plan”. If you want to move down a tier, use the contact route below and say which plan you want; treat it as an operator-handled change, not a button.

Cancellation is self-serve and runs in two steps: you give a reason, the app may show a retention offer, and you then either accept the offer or confirm the cancellation. You can back out before confirming. Cancelling stops the next renewal and your plan stays active until the end of the period you have already paid for. Ordinary cancellation is not pro-rated for part-months.

How do refunds work?

Lemon Squeezy is the merchant of record. The payment contract is with them, they issue your invoice, and they account for VAT or sales tax. Refunds are therefore issued by Lemon Squeezy — DeckScope records the refund against your payment once it is processed, but does not process it.

Two specific cases are defined:

• EU / EEA right of withdrawal. You have 14 days from the start of a subscription to withdraw without giving a reason. Because access begins immediately, you pay only for the proportion of the period during which you actually had access; the balance is refunded. Contact us, or use the contact route on your Lemon Squeezy receipt — routing it there is usually fastest.
• Closure not caused by you. If a paid account is closed for any reason other than your own breach of the terms, the unused part of the paid period is refunded.

Outside those cases there is no published blanket refund policy. Payment-method changes are made in the Lemon Squeezy customer portal, reachable from the app.

The withdrawal and refund clauses summarised above are set out in full in the Terms of Service inside the app.

Account and data

Who can see my collection?

Only you. Inventory and decks are scoped to your account. The exceptions are things you publish deliberately — a public profile or a deck you choose to share — and the anonymous deck-analysis tool on the marketing site, which is documented separately under community uploads.

Can I export my data?

Yes. The app exposes a full data export (GDPR Art. 20) that returns a single JSON bundle of everything owned by your account, including:

• your profile row (email, display name, role, account creation date)
• every collection card, with quantity, condition, disposition, storage box, and notes
• every deck, its metadata, and its card lists

Export is available from the data tools in account settings and requires no request or waiting period.

What happens when I delete my account?

Deletion is a real purge (GDPR Art. 17), not a deactivation flag. Concretely:

1. You confirm. Accounts signed in through Clerk confirm by typing their account email; older password-based accounts confirm with their password.
2. For Clerk-backed accounts the Clerk identity is deleted first, and the purge fails closed if that step fails. This is deliberate: a surviving sign-in identity would provision a fresh empty account on the next login, which reads as silent data loss rather than deletion.
3. Your owned rows are deleted across the database.
4. An ACCOUNT_DELETED entry is written to the audit ledger — the record that the deletion happened outlives the data itself, which is what an audit trail is for.

Deletion is immediate. Backups roll off within 7 days.

How long is data kept?

Data	Retention
Account and collection data	While the account is active; deleted on request
Backups after deletion	Expire within 7 days
Sessions / refresh tokens	30 days from last seen
Audit-ledger entries	365 days
Sync conflicts	90 days
Telemetry traces	30 days
Application logs	14 days
Tax and accounting records for paid plans	10 years (legally required)

The full matrix is maintained alongside the privacy notice.

Is DeckScope official?

No. DeckScope is an independent tool and is not affiliated with, endorsed by, or sponsored by Konami Digital Entertainment. See Data sources and affiliation for the full posture and the official references to check card text and legality against.

Product

What can I import?

The deck importer accepts .ydk, .csv, and .txt files, and you can paste a deck directly instead of uploading one.

.ydk is the format EDOPro and YGOPRODECK export. DeckScope reads the standard section markers — #main, #extra, !side — and expects one card passcode per line. Lines starting with # or ! that are not one of those markers are treated as comments and skipped, and — this is the part worth knowing — any other line that is not a valid passcode is also skipped silently. There is no rejection, no error, and no list of the values that were dropped: a malformed .ydk imports whatever passcodes it could parse and quietly leaves the rest out. Check the resulting card count and the parsed-card preview against what you expected before trusting the result, since a corrupted or hand-edited file will not tell you it lost lines.

Card names are resolved for CSV imports only. A CSV goes through a column mapper where you tell DeckScope which column holds the card name, the passcode, and the quantity; names are then looked up against the card catalogue and any that cannot be matched are listed back to you rather than silently dropped. The .ydk, .txt, and paste routes have no name lookup — they need passcodes. Pasting a plain name list into the text box (3 Ash Blossom & Joyous Spring) is not a supported route: DeckScope shows a validation message pointing you to the CSV import instead of trying to resolve the names there. If you have a plain name list, save it as a CSV with a name column and import it that way.

Which formats are supported?

Seven formats are modelled: Advanced, Traditional, GOAT, Edison, Genesys, Master Duel, and Speed Duel. Each carries its own banlist and card pool. Genesys is points-based, so it carries a card-points table in addition to a banlist; GOAT and Edison also constrain the card pool by a set-release cutoff.

Version history depends on the format: those backed by official Konami banlist snapshots (Advanced and Traditional) expose the historical versions of the list alongside the current one. The rest are served from their format definition rather than a snapshot history, so they currently expose a single current list.

Legality is evaluated against the format a deck is assigned to — copy limits and legality for the same card differ between formats, which is the usual reason a deck that looks fine in one format flags cards in another.

How should I read the analysis?

Some caveats worth internalising:

• Main and Extra Deck are analysed together, not separately. The main-to-extra pairs are what encode an actual combo line, so scoring them in isolation would misread most modern decks.
• Readiness measures buildability, not deck strength. It answers “how much of this can I sleeve up from cards I own”, weighted by how central each card is — not “will this win”.
• Benchmark comparisons are corpus-relative. Coverage deltas and suggestions are calibrated against tournament meta lists joined to current banlist state. They reflect what that corpus does, not an absolute verdict.
• Prices are indicative. Pricing data can be incomplete, stale, estimated, or placeholder depending on source availability. Verify any expensive purchase against the actual seller total, including shipping, language, and condition.

Where a score or figure is derived from incomplete data, the interface says so rather than presenting an estimate as a fact. If a result still looks wrong, work through Troubleshooting before assuming a bug.

What does “beta” label mean here?

DeckScope as a whole is in open beta — that is the label, and it is stated in the Terms of Service and privacy notice rather than attached to individual features. There is no per-feature beta badge in the interface today. The practical consequence is the same for every surface: features may change or be withdrawn between releases, and interfaces may change too.

Support

How do I get help or report a bug?

Use the Contact tab on the app’s Support page. You pick a category — bug, feature, feedback, or general — describe the issue, and send. Your account email is attached automatically, so there is nothing to fill in twice.

For rights-holder or legal matters, write to hello@deck-scope.com.

Will I get a reply, and how fast?

Yes. Replies appear under the My tickets tab on the same Support page, and the ticket is marked as answered when we respond.

We do not publish a response-time target. DeckScope is run by a small team and tickets are answered as capacity allows. Rather than promise hours we cannot guarantee, we keep every ticket visible in your account so you can see its state instead of wondering whether it arrived.

What should I include?

Anything that makes the problem reproducible: what you were doing, what you expected, what happened instead, and the deck or card involved if it is specific to one. If the issue is a wrong number, say which number and what you expected it to be — the answer is often the caveats above rather than a defect, and naming the figure gets you a straight answer faster.

What if my issue is with a payment?

Billing questions where the answer is “who charged me and can it be refunded” belong with Lemon Squeezy as merchant of record, via the contact route on your receipt. Questions about which plan you are on, what it unlocks, or an entitlement that did not apply after payment belong here — that side is ours.