Formal Technical Dispute: Evidence of Dynamic RTP Manipulation & Non-Random Hit Frequency

[Hellridah]

As a 20-year veteran of the iGaming industry with a long-standing reputation on this platform, I am filing this formal dispute against Winz.io (SoftSwiss). This is not a complaint regarding "losses," but a documented Technical Audit revealing a breach of RNG independence following a successful withdrawal.

To test the hypothesis of Account Profiling, I conducted a controlled experiment using three separate accounts playing Money Cart 3 (Relax Gaming) at the same bet level ($0.20) during a 48-hour window.

 

Experimental Data Table (March 18-20, 2026):

 

Account Profile	Session Time (UTC)	Total Spins	Bonus/Feature Triggers	Avg. Dead Spin Streak
Account A (New/Unverified)	Mar 18, 14:00 - 14:30	100	18 (1 every 5.5 spins)	3-4
Account B (New/Unverified)	Mar 18, 14:45 - 15:15	100	22 (1 every 4.5 spins)	2-5
Account C (Veteran/Post-Cashout)	Mar 19, 10:00 - 11:30	100	2 (1 every 50 spins)	25-40

Technical Violations Identified:

 

1. Breach of RNG Neutrality: Under Curacao and Relax Gaming certification, the PRNG must be "blind" to player identity. My data shows a 400% discrepancy in hit frequency between "New" and "Winner" profiles—a statistical impossibility under a standard random distribution.
2. Illegal Dynamic RTP (vRTP): While Relax Gaming offers multiple static RTP settings, the evidence suggests Winz.io/SoftSwiss utilizes an AI-driven Yield Management API to swap RTP profiles in real-time based on a player's risk/profit score.
3. Algorithmic Retention (The "Two-Scatter" Loop): Account C experienced a "Near-Miss" rate (2 scatters) significantly higher than Accounts A and B, suggesting a hard-coded retention algorithm designed to keep "at-risk" players spinning while the RTP is throttled.

Requested Action:
I request that Winz.io provide the full JSON game logs for these specific timestamps, including the RTP Configuration ID assigned to each session. I am also escalating this data to Relax Gaming’s Compliance Department to determine if their software is being modified by the aggregator's back-end AI.

 

---