1. The Editorial Site Data Boundary
This is the single most important section of this Privacy Policy for any reader who has read a Card Khaadi review on this site.
The data the editorial guide site holds is small, bounded, and described below.
What an editorial guide site at 3pattikhaadi.com actually stores — and what we do not. The Editorial Site Data Boundary, in plain English. Effective 11 May 2026.
3pattikhaadi.comThis is the single most important section of this Privacy Policy for any reader who has read a Card Khaadi review on this site.
The data the editorial guide site holds is small, bounded, and described below.
If you read a review of Card Khaadi on our site and you are worried about what data Card Khaadi (the operator) holds about you, please consult Card Khaadi's own privacy policy. We link to it on the Card Khaadi review page. The same applies to Teen Patti Gold, 3 Patti Blue, and every other operator we cover.
| Data type | Lawful basis |
|---|---|
| Newsletter email | Reader consent (opt-in form, with double-confirm email) |
| Editorial correspondence | Necessary for delivering the editorial service the reader has initiated |
| GA4 analytics | Legitimate interest in measuring site reach, with browser-side opt-out honoured |
| Server logs | Legitimate interest in abuse prevention, retained 7 days |
None of these categories are held for "future product use" speculatively. If we cannot point to a current operational reason, we delete.
The site uses a small set of first-party cookies for session and preference storage, plus the GA4 measurement cookie. That is the full list. We do not use:
The page weight stays light on purpose — a Karachi or Lahore reader on a 4G evening connection should not have to wait for advertising scripts to load before reading a Card Khaadi review.
The newsletter is hosted on a US-based email-marketing provider with EU-grade encryption at rest and TLS in transit. The web side and GA4 transit Cloudflare edges, which for Pakistani readers typically resolve to Karachi or Lahore points-of-presence and onward to Singapore for non-cached content. Email correspondence with our four mailboxes ending in @3pattikhaadi.com is hosted on a US-based email provider.
Pakistan does not yet have a unified data-protection statute equivalent to the EU's GDPR. Until such a statute passes, we voluntarily apply GDPR-equivalent transfer safeguards (Standard Contractual Clauses) for any provider whose servers sit outside Pakistan.
The quarterly editorial newsletter is opt-in only. We confirm a subscription with a double-opt-in email — meaning the email is not added to our list until you click the confirmation link in the first email we send. This stops other people from signing your email address up.
Unsubscribe is in the footer of every newsletter. One click. No "are you sure" loop. The unsubscribe is honoured immediately, the email is removed from our list within 24 hours, and we do not send a "we are sad to see you go" message afterwards.
| Data type | Retention |
|---|---|
| Newsletter email (active) | Until you unsubscribe |
| Newsletter email (after unsubscribe) | 30 days then deleted (we keep a hash for the same window to prevent accidental re-add) |
| Editorial correspondence | 14 months from the last reply |
| GA4 analytics | 14 months (Google's setting; we cannot extend) |
| Cloudflare server logs | 7 days |
"Deleted" means cryptographically erased — not soft-deleted, not flagged.
Under PECA 2016 consumer-protection rules and our voluntary GDPR-style framework, every reader has these six rights. Honoured free of charge, with one written reply within 7 business days.
Practical, not theatrical. The site sits behind Cloudflare with TLS 1.3. The newsletter list is held by the email-marketing provider with their published security posture (we do not host the list ourselves). Editorial correspondence sits on the email provider's standard-security tier with two-factor authentication enforced on every editorial mailbox.
We have not had a reader-data breach since launch in 2024 — and we will publish the fact, with the affected count and what we did, within 7 days of any future breach.
Material changes to this Privacy Policy (anything that affects what we collect, why, or for how long) are announced 14 days in advance on the blog. Cosmetic edits are made silently and the "Last reviewed" date is updated.