Privacy Policy

What we collect

When you sign in to the website, RChecker may receive sensitive login data such as your email address, OAuth name if provided, sign-in IP address, and user agent.

RChecker Client transfers hashed HWID, detected Steam IDs, detected Steam account data, Steam name history, limited Steam app activity, report time, and client IP address. We use this only for cheat prevention, ban-evasion prevention, and report integrity. Project data is isolated and not shared between projects.

RChecker may also show public Steam data and data from third-party services for Steam IDs shown in reports.

Local searches may show program launch activity/history, documents or recent files, registry artifacts, system/device signals, and other sensitive local data locally on the device. This local search data is never transferred to RChecker. RChecker does not collect local tokens, emails, document contents, or similar private local content.

Payments

When a project owner starts checkout, RChecker sends the payment provider the account email and name, internal user and project identifiers, the selected billing interval, and the checkout return context. The provider may independently receive IP address, browser or device data, billing address, tax information, and payment-method data through its hosted checkout.

The payment provider sends RChecker signed checkout and subscription events. RChecker uses those events, provider customer and subscription identifiers, product and price identifiers, payment status, billing dates, and limited checkout metadata to grant access, prevent duplicate processing, reconcile failures, support customers, and maintain billing audit history.

RChecker does not receive or store full card details. The payment provider processes payment data under its own terms and privacy policy, which are presented or linked during hosted checkout.

Why we use it

We use data to run moderation checks, show project reports, link account signals, detect ban evasion, secure RChecker, fix problems, and maintain audit history.

Project staff use RChecker data under their own server rules. They are responsible for their moderation decisions.

Who can see it

Checks and moderation data are shown to authorized server staff based on access settings.

Some data may be processed by infrastructure providers that help run RChecker.

We do not sell personal data. We may disclose data if required by law, to protect users or the service, or to investigate abuse.

How long we keep it

We keep data while needed for moderation history, audit logs, service operation, security, or legal reasons.

Completed payment webhook records and minimized event data are normally removed after 30 days. Failed or dead-letter billing events may be retained for up to 90 days for secure recovery and audit; provider customer, checkout, and subscription identifiers may be kept longer while needed for accounting, disputes, fraud prevention, or legal obligations.

Some data may stay in backups or logs for a limited time after it is removed from active product views.

Your choices

You can manage your account in the web app.

If your data comes from a server check, the server staff who requested the check may be the right first contact.

You can also contact admin@rchecker.com or use the links in the footer for privacy questions or requests.

Security

We use access controls and operational safeguards to protect data.

No system is perfectly secure. Please report suspected security issues to admin@rchecker.com or through the links in the footer.

Changes and questions

We may update this policy. The date above shows the latest version.

Privacy questions can be sent to admin@rchecker.com or through the links in the footer.