How 3838 fun Handles Your Account Privacy
Our privacy policy sets out what account data 3838 fun collects, why we keep each record, and how you can check or change it. Read on for your...
Where This Policy Applies To You
3838 fun runs one privacy policy across supported regions, and where local law permits we follow the stricter of the two standards whenever they differ. If you open your account from Pakistan, our handling of your details follows the data rules that apply to Pakistani residents, including how long records stay with us and how fast we answer a deletion request. Some
services are simply not offered in regions where a regulator has restricted them, and we say that in plain language rather than burying it in small print. Payment entries are the clearest example: JazzCash, Easypaisa, SadaPay, NayaPay and Raast references sit in your statement, so we treat those logs as personal data and limit which colleagues can open them. Where access depends
on local law, we tell you before any transfer clears rather than afterwards.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Raise A Privacy Request
You do not need to hunt through menus to ask about your data. Write to our privacy desk from the email on your account and we log the request under your profile, so one thread stays open until it is closed. Chat and email both reach the same team.
Privacy Email Desk
Write from the address on your account profile and our desk replies in writing, keeping the whole thread attached to your record so nothing is lost between shifts.
Live Chat Window
Open live chat inside your account for a data copy or a correction, and the agent sees your ticket history without you repeating the same story again.
Account Data Panel
Check your stored details, marketing preferences and signed-in device list from your account panel, then change anything routine without emailing our team for every small update.
Who Writes And Checks This Policy
The wording on this page is drafted by the team that runs your account flow, then read again by the group handling payments and security. When something changes inside the product, the...
Drafted In-House
Written by the people who run your account flow, so the wording matches what the product actually does rather than describing a system we do not operate.
Payment Team Sign-Off
Colleagues who handle JazzCash, Easypaisa, SadaPay, NayaPay and Raast settlement read the transaction sections, because those records touch your money and your identity at the same time.
Security Check
Our account-security group checks how login data, device records and verification files are stored, then confirms the policy text matches the retention windows we actually apply across the platform.
Version Dates
Every revision carries the date it took effect, so you can see when a section changed and compare it against the notice sent to your registered email address.
Plain Language Pass
We rewrite legal phrasing into everyday English before publishing while leaving the same meaning in place, because a policy you cannot read is not much use to you.
Support Feedback Loop
Questions raised on chat and email feed straight into the next revision, so repeated confusion about one clause usually ends with clearer wording on this page.
Same Standard As Our Other Policy Pages
The policy you are reading uses the same structure as our terms, payment and account pages, so you can move between them without relearning the layout. Definitions match...
What Sits On This Policy Page
The page is built so you can find a clause fast. A chip row names the local rails, short cards summarise each commitment, and the question...
Local Rail Chips
The chip row names JazzCash, Easypaisa, SadaPay, NayaPay and Raast, marking exactly which transaction references we treat as personal data inside your monthly statement.
Commitment Cards
Each card carries one promise in plain English covering collection, storage, sharing and deletion, so you can read a single block instead of the full legal document.
Question Block
Six common questions sit at the end of the page and answer the points readers raise most, from device records to how quickly we act on a correction request.
Revision Stamp
A dated revision line sits near the top, so you can confirm which version of the policy you are reading before you act on anything written below it.
Contact Panel
A short contact block repeats the privacy desk, chat window and account panel, so you can act on a question the moment it occurs without scrolling back up.
Plain Headings
Section headings describe their contents directly, which keeps the page easy to scan for anyone reading on a phone between other errands during a busy working day.