checkra1n - Privacy Policy for your account
Your checkra1n account privacy starts before you join: we explain what data we collect, why we need it, and how it supports account access in Pakistan where local...
How we treat personal data
This Privacy Policy explains how checkra1n handles data connected with your account, device, wallet activity, support requests, and security checks in supported regions. We collect only the details needed to create and protect your account, process local payment references, manage access, respond to your messages, and meet record-keeping duties where local law permits. Payment context may include the rail name, transaction reference,
amount, time stamp, status, and the account identifier you provide, but we do not ask you to share wallet PINs or banking passwords. We also use technical logs to detect suspicious sign-ins, protect balances, and keep your session stable across mobile browser and larger screens. If this policy changes, we publish the updated wording on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions and account help
If you need to ask about your data, start with the contact path linked inside your account area. We separate privacy questions from routine lobby support so your request reaches the right team with less back and forth. Include your account name, the date of the issue, and the data topic you want us to check.
Account message
Send a privacy request from your signed-in account when possible. That route helps us match your message to the correct record without asking for extra identity details over open channels.
Email request
Use the privacy email shown in the account area if you cannot sign in. Share only what is needed: account name, contact address, and the privacy action you want us to assess.
Wallet query
For JazzCash, Easypaisa, SadaPay, or Raast references, send the transaction time and reference number. Never send wallet PINs, one-time codes, card images, or full banking passwords.
How we keep policy wording current
Our privacy wording is maintained by the team that handles account access, security checks, payment references, and support records. That matters because the policy reflects real account flows...
Account flow mapping
We link each privacy clause to an account step, such as joining, signing in, verifying a wallet reference, or contacting...
Security log checks
We describe technical logs in plain language because sign-in time, device signals, and IP patterns help us protect access and...
Payment reference handling
Local rail records are treated as account support data. We use transaction status and reference details to reconcile wallet activity...
Support record control
Messages you send to us are stored with the account issue they relate to. This helps us answer privacy questions...
Access request process
When you ask to access, correct, or remove eligible account data, we check identity first. That step protects your record...
Change tracking
When the policy wording changes, we keep the page focused on data use, retention, security, and contact routes rather than...
How privacy fits related pages
This page works with our account terms, cookie wording, and contact details, but it has a separate role. The Privacy Policy explains personal data handling only. If another...
| Account terms | Terms explain account rules; this policy explains the data connected with those rules, including sign-in records, identity checks, and account actions that may create a privacy record. |
|---|---|
| Cookie wording | Cookie wording covers browser storage and similar tools. This Privacy Policy connects those signals to account security, session stability, and preference handling where they apply. |
| Support page | Support contact details tell you where to ask for help. This policy explains how we store your message, verify the account, and manage privacy requests after contact. |
| Wallet records | Payment screens show rail status and references. This policy explains why those records are kept, who may handle them, and why wallet passwords are never requested. |
| Security notices | Security prompts may appear during unusual sign-ins. This policy explains the technical data behind those prompts and how it supports account protection. |
| Promo board | If you check what is running this week, we may record eligibility and display status. This policy explains how those account-linked details are handled. |
| Region access | Access may vary by supported region and local law. This policy explains how region signals are used for availability, security, and account administration. |
Visible privacy signals on this page
We designed this Privacy Policy to be read before you open your account, not hidden after the fact. The layout highlights the data points you are most likely...