Terms se rabt
Terms batate hain ke account kaise chalna chahiye; Privacy Policy batati hai ke us account se nikalne wala data kaise handle hota hai. Dono safhe mil kar record ki bunyad banate hain.
LEGAL REFERENCE
393 Privacy Policy aap ke data ke liye
393 par account kholte waqt aap ka naam, rabta number, device nishan aur transaction hawale hamari raazdari policy ke mutabiq sambhale jate hain. Hum is safhe par wazeh...
Account dataJazzCash hawalaEasypaisa nishanSadaPay recordRaast tasdeeq
Jahan qanoon ijazat de wahan data ka rawaiya
393 supported ilaqon mein aap ki maloomat sirf account chalane, login ko mehfooz rakhne, payout tasdeeq karne, aur service sawalat ka jawab dene ke liye istemal karta hai. Jahan local qanoon ijazat deta hai, hum KYC, transaction history, IP nishan, device record, aur wallet hawala apne system mein rakhte hain taake account dispute ya ghalat access ki soorat mein sahih faisla ho
sake. JazzCash, Easypaisa, SadaPay aur Raast se aane wale hawale sirf reconciliation, fraud roktham, aur audit trail ke liye milaye jate hain. Hum aap ka data be-maqsad bechne ke liye share nahi karte; zaroori vendor, payment processor, ya qanooni darkhwast par hi mehdood sharing hoti hai.
Service ki dastiyabi jurisdiction par depend karti hai. Access se pehle local qanoon check karna user ki zimmedari hai.
JAANCH NISHAN
Policy par hamari andarooni jaanch
393 ki Privacy Policy static lafzon ka safha nahi; isay hamari operations, support aur security teams waqtan waqtan check karti hain. Jab payment rail ka flow badalta hai, naya verification step lagta...
Data mapping
Hum account fields ko purpose ke saath map karte hain: login ke liye phone, payout ke liye wallet hawala, aur security ke liye device nishan. Har field ka maqsad policy mein match hona chahiye.
Access control
Support ya finance staff ko poora data khula nahi hota. Role ke hisab se screen mehdood hoti hai, is liye payment hawala dekhne wala agent password ya private document nahi dekh sakta.
Change log
Policy mein bari tabdeeli aaye to hum internal change log rakhte hain. Is se maloom hota hai ke kis process, vendor, ya payment reconciliation ki wajah se lafzon mein tabdeeli ki gayi.
Retention check
Purane records ko hamesha ke liye be-wajah nahi rakha jata. Finance, dispute, security aur qanooni zaroorat ke hisab se retention period dekha jata hai, phir removal queue chalti hai.
Vendor screening
Jis vendor ko account ya payment data tak mehdood access chahiye, us ke role ko pehle assess kiya jata hai. Contract mein confidentiality, access scope, aur incident reporting ki shartein rakhi jati hain.
Incident path
Agar unusual access ya data issue nazar aaye to security team login, device, aur payment trails milati hai. Zaroori hua to affected account ko seedha paigham bheja jata hai.
POLICY MILAN
Doosre policy safhon se rabt
Privacy Policy ko alag se samajhna asan hai, lekin 393 ke kuch aur legal safhe bhi isi data flow se jurte hain. Terms account istemal ka frame dete hain, cookie safha browser...
Cookie safha
Cookie safha browser storage aur session nishan par focus karta hai. Privacy Policy us nishan ko account, login security, aur analytics purpose se jor kar batati hai ke data kahan istemal hota hai.
Bonus shartein
Promo board ki shartein reward eligibility ko record se milati hain. Privacy Policy wazeh karti hai ke activity logs, wallet hawale, aur account status sirf verification ke liye kaise dekhe jate hain.
KYC process
Verification process identity documents ya phone matching maang sakta hai. Privacy Policy batati hai ke ye documents kis purpose se liye jate hain, kis ko access milta hai, aur kab removal possible hota hai.
Security rules
Security rules suspicious login, duplicate account signal, aur device pattern ko cover karte hain. Privacy Policy unhi signals ke data angle ko samjhati hai, taake aap ko monitoring ka maqsad maloom rahe.
Support records
Support policy response time aur ticket handling ko define karti hai. Privacy Policy batati hai ke chat transcript, email paigham, aur issue screenshots kitni zaroorat tak store kiye ja sakte hain.
Payment terms
Payment terms transaction acceptance aur processing steps batate hain. Privacy Policy sirf data side ko cover karti hai: wallet number, reference ID, bank rail signal, aur reconciliation record ka use.
Privacy safhe ke wazeh nishan
Is safhe ka layout is liye banaya gaya hai ke aap jaldi samajh saken data kahan se aata hai, kis se share hota hai, aur kaunsi...
Short badges
Hero ke neeche chips aap ko turant dikhate hain ke policy kin data qisamon par chalti hai. Ye badges legal jumlon ko chhote nishanon mein tod kar pehli nazar mein context dete hain.
Plain headings
Har section ka heading seedha purpose batata hai, taake aap ko lambi legal language mein data topic dhoondhna na pade. Hum headings ko account, payment, support, aur retention ke gird rakhte hain.
Local context
Pakistan ke payment rails aur phone-based accounts policy mein naam se likhe jate hain. Is se aap ko andaza hota hai ke JazzCash, Easypaisa, SadaPay, NayaPay ya Raast hawale kahan fit hote hain.
Action wording
Jahan aap data copy, correction, ya deletion pooch sakte hain, wahan wording ko request ke qareeb rakha gaya hai. Is approach se support ko bhi maloom rehta hai kis process par kaam karna hai.
Retention markers
Policy mein record rakhne ki wajah alag alag likhi jati hai: finance reconciliation, dispute handling, security check, ya qanooni zaroorat. Har reason data storage ko behtar samajhne mein madad deta hai.
Update signal
Jab privacy wording mein bari tabdeeli ho, hum safhe ke content ko account process ke saath milate hain. Is se purani aur nayi handling ke darmiyan farq samajhna asan rehta hai.
Privacy Policy par aam sawal
Account banate waqt hum phone, login detail, device nishan, region signal, aur zaroori profile fields lete hain. Ye data account access, security check, aur support response ke liye use hota hai.
Wallet hawala transaction ko aap ke account se milane ke liye zaroori hota hai. Hum reference ID, raqam status, aur time stamp rakhte hain taake payout ya dispute ka record clear rahe.
Haan, agar phone, naam spelling, ya profile field ghalat ho to support ko darkhwast bhejen. Hum pehle account tasdeeq karte hain, phir allowed field ko update ya correction queue mein daalte hain.
Retention data type par depend karta hai. Login trails security ke liye, payment records reconciliation ke liye, aur support tickets dispute history ke liye rakhe ja sakte hain jab tak policy aur qanoon zaroorat samjhen.
Hum data sirf zaroori vendor, payment processor, security tool, ya qanooni darkhwast ke saath mehdood taur par share karte hain. Sharing ka purpose account service, verification, ya risk control se juda hota hai.
Account closure ke baad bhi kuch records finance, dispute, ya qanooni wajah se reh sakte hain. Aap privacy inbox par closure reference bhejen; hum batayenge kaunsa data remove, mask, ya retain hota hai.