TASUTASPINN

Information

Privacy Policy

What personal data Tasutaspinn.ee collects, why, and how you can access, correct, or delete it under Estonian and EU data protection law.

Tasutaspinn.ee is a content and comparison site, not a gambling operator, so the amount of personal data we hold is small. This policy covers what we collect, why we collect it, and what you can do about it.

Data collected automatically

When you browse the site, we log standard technical details — browser type, approximate country, pages visited, and how long you stayed on them — through privacy-respecting analytics. None of this identifies you by name, and it's aggregated before we ever look at it.

Data you provide directly

If you use the contact form, we store your name, email address, and message so we can reply. We don't add contact form submissions to a mailing list, use them for marketing, or share them with casino operators under any circumstance.

What we never collect

We don't collect payment card numbers, casino account passwords, or ID documents. Any KYC verification you complete happens on the licensed casino's own platform, entirely outside Tasutaspinn.ee — we have no visibility into that process at all.

Sharing with third parties

We don't sell personal data. Aggregated, anonymised traffic statistics may be shared with our analytics provider. Clicking through to a casino partner takes you to that operator's own site, which sets its own cookies under its own privacy policy from that point on — our policy stops applying the moment you leave.

How long we keep it

Contact form messages are kept only as long as needed to resolve the enquiry and confirm the outcome, then deleted on a routine schedule rather than stored indefinitely.

Your rights

Under Estonian and EU data protection law, you can request access to, correction of, or deletion of any personal data we hold about you. Write to [email protected] and we'll act on the request.

Changes to this policy

If how we handle data changes in a way that matters, we'll update this page and note it rather than making silent edits to a live policy.