A 20 Pound Credit Is What "Buy" Actually Means

A Google Play customer lost access to The Lord of the Rings: Extended Edition Trilogy that they had purchased through Google Movies, after Google's licensing agreement with Warner Bros. ended and the films left the catalogue ^[1][2]. The settlement, according to Polygon, was a set of download links plus a 20 pound credit on the same storefront ^[8], which is a precise statement of what the word "buy" buys in a licensed digital store.

The sequence is worth reading as a support-flow diagram rather than a scandal. The user, posting as ugoindownsaka1 on r/piracy, found the purchase gone ^[1]. Google's support initially refused any refund ^[4]. Google Play's terms of service already covered the case: the company may cease providing access to purchased content if it loses the relevant rights, and if you did not download a copy first, it may offer either a replacement or a full or partial refund, with the refund being "your sole remedy" ^[5][6]. Per Gizmodo, support acted only after the customer quoted that policy back at them ^[7]. Then the Google TV download links did not work, because the user said they demanded "payment to watch" ^[9].

So the escalation path ended with neither working access nor cash: a credit, on the platform that had just demonstrated it cannot guarantee delivery ^[14]. Gizmodo described the credit as an invitation to play another round of "Can I Keep This?" Roulette ^[15]. Note also that the delivered remedy was not the one the contract names as sole remedy; a credit is not a refund, and the source does not state the original purchase price, so whether 20 pounds was full or partial compensation is not determinable ^[17][18].

This is not a Google anomaly. Buyers learned several years ago that iTunes purchases could be pulled by the rights owner at any time ^[10]; Sony said earlier this year that it would remove titles from customer libraries because of changing licensing agreements ^[11]; games have gone the same way when publishers stopped supporting them ^[12]. Gizmodo's point is the operational one: the existence of a removal-and-remedy clause tells you the event is expected to recur ^[13].

For anyone selling licensed content or any entitlement whose supply depends on a third-party contract, there are three separable failures here, and only one of them is legal. The first is disclosure: the purchase surface says buy, and the revocation condition lives in the terms of service ^[5]. The second is remedy design: the clause offers replacement or refund ^[6], but the front line refused a refund until a customer performed contract interpretation on its behalf ^[4][7]. The third is fulfilment integrity: the replacement links shipped without being tested against an entitlement record that no longer existed ^[9]. Any team with a licence expiry date in a spreadsheet has a foreseeable job to do before that date, which is to reconcile catalogue exit against the list of people who paid.

What to watch: whether storefronts move the default remedy from credit to cash, since credit keeps the liability inside the same system that failed; whether licence expiry triggers a proactive notice and refund run rather than a support ticket; and whether replacement links are validated against live entitlements before being sent. The fallback argument, as Gizmodo puts it, remains the disc you can play on your own terms ^[16].