KarasuCSKARASUCS
Back homeLogin
GDPR rights

EU data rights without weakening fair play.

How KarasuCS handles access, correction, deletion, export, objection, consent withdrawal, and verification for EU/EEA/UK users while preserving anti-cheat, moderation, payment, and security evidence where needed.

Last updated: 2026-05-28

01

Purpose of this GDPR notice

This notice explains how KarasuCS handles data rights for users in the European Union, European Economic Area, United Kingdom, and other places with similar privacy rights. It works together with the Privacy Policy, Cookie Policy, and Terms of Service.

KarasuCS is a competitive CS2 platform, so privacy rights are handled in a way that also protects match integrity, anti-cheat investigations, moderation evidence, payment records, and platform security.

02

Controller and contact route

For GDPR-style requests, contact vlad@karasu.live and include GDPR Request in the subject. Send the request from the email or account context connected to your KarasuCS account where possible, and include your Steam ID or KarasuCS username so we can identify the correct account.

We may ask for verification before acting on a request. This protects accounts from someone else requesting export, deletion, or changes to data they do not own.

03

Your rights

  • Access: ask what personal data we hold about your account and how it is used.
  • Correction: ask us to correct inaccurate account, contact, or profile data where the platform does not already let you update it yourself.
  • Deletion: ask us to delete data that no longer needs to be kept, subject to safety, legal, payment, dispute, moderation, anti-cheat, and security limits.
  • Portability: ask for a copy of data you provided or data generated through your use of the platform where portability applies.
  • Restriction: ask us to limit certain processing while a dispute, correction, or objection is reviewed.
  • Objection: object to processing based on legitimate interests, including some safety or analytics processing, where the law gives you that right.
  • Consent withdrawal: withdraw consent for optional cookies or optional features where consent is the basis for processing.
04

How to make a request

  • Email vlad@karasu.live with the request type, your Steam ID or KarasuCS username, and enough context for us to verify ownership.
  • Use a clear subject such as GDPR Access Request, GDPR Deletion Request, GDPR Correction Request, or GDPR Objection.
  • Do not send passwords, payment card numbers, private keys, Steam Guard codes, or unrelated sensitive documents. If verification is needed, we will ask for the minimum practical proof.
  • If the request involves a support ticket, match, ban, appeal, payment, or security event, include the relevant ticket ID, match ID, invoice reference, or date range if you know it.
05

Response time

We aim to respond to GDPR-style requests within one month where required by law. Complex requests, repeated requests, requests involving large match or moderation histories, or requests that require careful security review may take longer where the law allows an extension.

If we cannot complete a request immediately, we may explain what is still being reviewed, what verification is needed, or why a legal exception applies.

06

What may be included in an export

  • Account and Steam identity records connected to your KarasuCS account.
  • Profile, settings, roles, subscription entitlement state, and account status information.
  • Queue, party, match, tournament, demo, stats, and leaderboard records connected to your account where export is practical and lawful.
  • Support tickets, reports, appeals, and user-submitted messages or attachments where disclosure does not expose another person’s data or compromise an investigation.
  • Payment references and billing status metadata held by KarasuCS. Full payment card details are handled by payment providers and are not intended to be stored by KarasuCS.
07

Limits on deletion and objection

Some data cannot be deleted or stopped immediately just because a request is made. KarasuCS may keep records where needed for legal obligations, accounting, chargeback defense, dispute handling, fraud prevention, anti-cheat, ban-evasion prevention, moderation continuity, account security, infrastructure security, or protection of players and staff.

For example, deleting every match log, ban record, report, or payment record could let malicious users reset history, evade enforcement, abuse refunds, or attack the service without accountability. Where possible, we may remove or anonymize profile-facing information while keeping restricted internal evidence for legitimate safety or legal reasons.

08

Automated signals and human review

KarasuCS may use automated or semi-automated signals for queue eligibility, client compliance, anti-abuse checks, rate limits, suspicious login patterns, payment risk, and security monitoring. Important moderation or enforcement decisions may also involve staff review, available evidence, server logs, demos, reports, and appeal context.

If you believe an automated or evidence-based decision is wrong, use the support or appeal route and provide specific context such as match ID, demo timestamp, client issue, payment reference, or account event.

09

International processing

KarasuCS, its infrastructure providers, payment providers, Steam-related services, support tooling, analytics, monitoring, and staff may operate in different countries. Where GDPR transfer rules apply, we rely on appropriate contractual, technical, organizational, and provider safeguards.

10

Complaints

If you are in the EU, EEA, or UK and believe your privacy rights have not been handled properly, you may have the right to complain to your local data protection authority. We ask that you contact us first when practical so we can try to understand and resolve the issue.

11

Changes to this notice

We may update this GDPR notice when KarasuCS changes, when vendors change, when data rights workflows change, or when legal requirements change. Material updates may be announced on the site or in-platform where practical.