DuckyLuck

Privacy policy

This site is a test log: our team deposited and withdrew real money at DuckyLuck and published the timings. We do not run the casino, accept bets or hold player balances, so the personal data we handle is small in scope. This policy explains what we collect, why we collect it and what you can ask us to do.

Data we collect

Like most websites, our server records technical details for every visit: IP address, browser and device type, the pages you open and the time you open them. We use these records to keep the site running and to spot misuse.

If you email us, for example to report that a payout took longer than our log shows, we keep your address and your message so we can reply and, where useful, recheck the figure.

What we never ask for

We never request card numbers, crypto wallet addresses, passwords or identity documents. Anything you hand to DuckyLuck during sign up, deposits or verification goes straight to the casino, and we have no access to it.

Cookies and analytics

A few cookies keep pages loading correctly and let us count visits in aggregate. The numbers tell us which sections people read most, such as the withdrawal table, so we know what to retest first. You can block or clear cookies in your browser and the site will still work.

Links to the casino

Buttons on this site open DuckyLuck in a new page. From that point the casino's own privacy policy applies. A link may tell us that a visit came from our site, but never who made it.

How long we keep it

Raw server logs are wiped automatically once they are a few months old. Emails stay with us while the conversation about a test result is open and are removed afterwards. Our testers' notes from the three-week trial hold only their own account data, never details about readers.

Your rights

You may ask what we hold about you, ask for a correction or ask us to delete it by writing to the contact address on this site. We reply within a reasonable time, and we do not sell, rent or swap personal data with anyone.

Changes

When our tools or testing routine change, this policy may change too, and the wording published here reflects the latest revision.