Self-refund abuse criteria
Last updated: TODO: publish date · Criteria version 1
Many developers on Cassette let buyers refund a purchase themselves for a short time after buying. Developers can choose to use a registry run by Delegas Labs, S.L. ("we") to stop wallets that abuse that convenience. This page sets out how the registry works, the rules we apply and how to appeal. It is part of our Terms of Service.
What a restriction does, and doesn't do
A restricted wallet can't self-refund at storefronts whose developers chose to use the registry, until the restriction ends.
It can still:
- buy anything, from any developer;
- play and keep everything it bought;
- ask any developer for a refund, which the developer can give;
- self-refund at storefronts that don't use the registry, or whose developer has allowed that wallet.
A restriction is never used to block buying or playing, and never against a developer. The developer can always make its own decision for any wallet, which overrides the registry.
The rules
Each rule only opens a case for review. It never restricts a wallet automatically.
| Rule | What we look at | When it opens a case |
|---|---|---|
| 1. Refund rate | Self-refunds against purchases, across all storefronts, from public blockchain data | At least 3 self-refunds in 30 days, and at least half of that wallet's purchases in those 30 days |
| 2. Play, then refund | Time played in a game on Cassette before self-refunding it | At least 2 self-refunds in 30 days, each after at least 60 minutes of play, or, for short games, after at least 80% of the game's typical completion time |
| 3. Linked wallets | Wallets that share a browser with, or were first funded from the same non-exchange address as, a wallet restricted under rule 1 or 2 | The linked wallet has at least 1 self-refund in 30 days |
Developers can also cap self-refunds per wallet in their own storefront, for example to 3 in 30 days across all Cassette storefronts. That cap is arithmetic in the storefront, not a registry decision.
How we decide
- A person reviews every case before any restriction, and can decide not to restrict.
- Length: 30 days for a first restriction, 90 days for a repeat. Each restriction lasts at most 90 days. It is never renewed automatically: a new restriction needs a new review that finds a rule is still met, and comes with its own notice and right to appeal.
- What's recorded on the blockchain: the wallet address, the end date, the rule number and a case reference. No names, reasons in words, or links between wallets. The restriction expires by itself.
- Notice: if you're restricted, Cassette shows you the rule, the end date and how to appeal. A developer's paywall tells you before you buy if self-refund won't be available.
Appeals
Reply to the notice, or write to [email protected] with your wallet address, within six months. Someone who wasn't involved in the decision reviews it and answers within 14 days. If we got it wrong, we lift the restriction on the blockchain. You can also go to the courts, or to an out-of-court dispute settlement body certified under the EU Digital Services Act.
Your data
We use public blockchain data, and for rules 2 and 3 our play records, to prevent fraud, which is our legitimate interest and that of the developers who use the registry. See our Privacy Policy. The record that a restriction existed stays in the blockchain's history even after it ends, because nobody can delete blockchain records.
Changes
We publish each version of these criteria here and record it in the registry contract. A new version applies only to cases opened after it.