DexyPlay

DexyPlay’s August 19, 2026 reward-ladder email advertised three weekly maximums: up to 1.1 million GC, 65 SC, and 110 Free Plays. It explicitly warned that breaking the login streak would reset progress. Those maxima were not described as rewards credited on a single login.

The three weekly maxima cannot be added

Dividing the 65-SC weekly maximum by seven would produce about 9.29 SC, but that would be an arithmetic average of an advertised maximum, not a documented daily reward. A broken streak also changes the claimed progression. The email does not contain enough daily detail to reconstruct what a missed day costs.

The message did not supply a complete ladder

We reviewed the original email, including the reset condition. It did not itemize each day’s reward, identify which days contributed the SC maximum, or establish that all three maxima could be collected by our account without additional conditions.

We have not completed or reconstructed the ladder from that message. The reviewed first-hand section contains a support interaction but no detailed daily-claim sequence to reconcile against the promotion. Assigning the weekly maximum to each day would invent account outcomes rather than explain the offer.

Free Plays can have their own game and winnings limits

The DexyPlay terms, version 2.0 read September 8, let the operator select the games and play level for Free Plays. Section 7.7 allows them to be awarded instead of other promotional prizes and permits an aggregate winnings cap, unless the specific promotion says otherwise. Winnings above a cap are not credited.

The ladder’s Free Play count therefore does not identify a cash value or prove how much could become eligible for redemption. We have not observed a substitution or a cap applied to our account, and the ladder email alone does not answer those questions.

The historical enquiry was redirected

On August 24, we asked support for the first public day of DexyPlay’s U.S. prize-redemption product and a supporting record. The original enquiry was sent at 15:09:44 UTC; the reply arrived at 16:16:56, an interval of one hour, seven minutes, and 12 seconds.

The support reply described its role as customer service and directed advertising, affiliate, or partnership enquiries to MediaDunk. It did not provide the requested launch date, identify a launch record, or confirm that the historical enquiry had actually been forwarded.

That referral is the observed support outcome. We have not treated MediaDunk as the platform owner on that basis, and we did not contact it during this research. A routing suggestion is not proof of ownership or a historical date.