Privacy Policy for your beppk account
beppk keeps your privacy choices clear before you open an account: what we collect, why we need it, and how payment checks work in supported regions. Read this...
How we handle your account data
This Privacy Policy explains how beppk collects and uses personal data when you create an account, browse our lobby, use live casino streams, check sportsbook markets or request a withdrawal where local law permits. We collect only the details needed to run your account flow, verify payment activity, protect access, answer support messages and meet record-keeping duties that apply to supported regions.
Payment references may include wallet name, transfer time, masked sender details and settlement status; we do not publish your personal payment data. We also use device and session signals to detect unusual access and keep your login safer. If this policy changes, we update the page date and keep the wording plain so you can understand what changed before continuing with beppk.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact paths for privacy questions
When your question is about privacy, our support team separates it from routine lobby help so the right staff can respond. You can ask about data access, correction, withdrawal records, device sessions or account closure. We may request account matching details before sharing anything sensitive.
Live chat privacy queue
Use chat from your logged-in account for quick privacy routing. We verify account ownership first, then pass your request to staff who handle data access, correction and session questions.
Email privacy request
Email is useful for longer requests, such as payment record checks or account data copies. Include your registered mobile number and wallet reference so we can match the request safely.
Security alert route
If a login, device or wallet activity looks unfamiliar, contact us through chat or email. We can place extra checks on access while we assess session logs and payment references.
How we keep this policy reliable
Our privacy wording is written from the way beppk actually operates: account checks, payment records, live session data and support handling. We do not add claims that we cannot apply in your...
Policy owner
A named internal team maintains this Privacy Policy and checks it against account flows, payment handling and support practice before updates are published on the beppk site.
Plain update dates
When wording changes, we show the effective date near the policy. That helps you connect a change with how account, device or payment data may be handled.
Data mapping
We map each data type to a purpose, such as login security, wallet verification, support replies or withdrawal processing, so collection does not drift beyond account needs.
Payment records
JazzCash, Easypaisa, SadaPay and Raast references are treated as account records. We use them for matching, settlement checks and dispute handling, not public display.
Access control
Internal access to personal data is limited by role. Support staff see the details needed for your request, while sensitive account checks require stronger permission.
Change log
Material privacy changes are tracked internally before publication. That record helps us answer why a wording change was made and which account process it affects.
How this policy matches related pages
This Privacy Policy sits beside our other legal pages, but it has a different job. It focuses on personal data, privacy choices and account records only. Where another...
| Terms page alignment | The terms page sets account rules, while this Privacy Policy explains the data needed to apply those rules, including identity checks, access logs and payment matching. |
|---|---|
| Cookie page alignment | Cookie wording explains browser storage separately. This page connects cookie-like signals with privacy purposes, such as session continuity, fraud detection and account preference handling. |
| Security page alignment | Security wording covers account protection practice. The Privacy Policy explains which data supports that practice, including device fingerprints, login time and unusual access signals. |
| Account page alignment | Account pages show what you enter or change. This policy explains how those details are stored, corrected, used for support and removed where deletion is available. |
| Wallet page alignment | Wallet pages describe transaction steps. This policy explains the privacy side: masked wallet identifiers, transfer references, payout checks and retention for account disputes. |
| Promo page alignment | Any offer-related page may use account eligibility data. This policy explains how we handle that data and how contact preferences affect messages you receive. |
| Contact page alignment | The contact page gives channels, while this Privacy Policy explains what support messages may contain, how long we keep them and who can access them. |
Privacy layout you can read quickly
We design the privacy page so you can scan the important points without losing the legal meaning. The layout separates account data, payment records, security signals and contact...