TeenPattiHomes — Privacy Policy

Effective: May 11, 2026  |  Page version: 1.0

1. What This Page Covers

This Privacy Policy applies to the website teenpattihomes.com, including the home page index, the hub pages (Ludo APK Hub, Teen Patti APK Hub), the community guide, the individual notes pages, the editorial pages, and the contact-form flow. It applies to readers anywhere who visit teenpattihomes.com, with primary focus on Pakistani Android readers.

It does not apply to the Ludo, Teen Patti, 3 Patti, Dragon Tiger, BountyClash, Lucky Jackpot, or any other publisher APKs that TeenPattiHomes indexes. Each indexed APK is operated by a separate company; once you install an APK, the publisher of that APK becomes a separate data controller and the publisher's privacy policy governs everything inside the app.

2. Information We Actually Collect

For an aggregator, the honest list is short.

What we collect (from teenpattihomes.com visitors):

• Server access logs — IP address, user-agent, requested URL, timestamp, response code. Standard web-server logs; collected automatically when a browser requests any page.
• First-party cookies — small text strings that remember your cookie-consent state and your hub-page sort preference. They are set only by teenpattihomes.com and are not shared with any third party.
• Aggregate analytics — visit counts, geographic city-level region (Karachi, Lahore, Islamabad, Faisalabad, Rawalpindi typically lead), device class, on-page event counts. Currently provided by Google Analytics 4 with IP anonymisation enabled.
• Community submission content — when a reader emails [email protected] to file a device-fit report or a wallet observation, we receive the email address, the message body, and any voluntarily-included device or region detail.
• Editorial email content — when a reader emails [email protected] with a correction or a publisher correspondence, we receive the email address and the message body.

What we do not collect:

• We do not run reader account login on teenpattihomes.com; there is no username or password to lose.
• We do not collect JazzCash or Easypaisa account numbers or balances at any indexed publisher.
• We do not collect CNIC, passport, or other Pakistani identity documents.
• We do not collect device-level identifiers such as Android Advertising ID or IMEI.
• We do not require any reader to share precise geolocation; we read the city-level region from anonymous analytics.
• We do not host any commerce flow on teenpattihomes.com — there is no shopping cart, no in-site payment, no checkout.

3. Cookies, Analytics & Browser Data

Cookies on teenpattihomes.com fall into two short groups.

Strictly necessary first-party cookies. These remember your cookie-consent state, your hub-page sort preference, and similar non-tracking preferences. Set only by teenpattihomes.com. Cannot be disabled without breaking basic site behaviour.

Optional analytics cookies. Set by Google Analytics 4 to count visits and on-page interactions in aggregate. IP anonymisation is enabled, advertising signals are disabled, and we do not connect analytics data to any reader identity. You may decline analytics cookies on first visit, change your decision at any time through the cookie banner, or block them at the browser level (any modern Pakistani Android browser supports cookie blocking).

We do not currently run any advertising network on teenpattihomes.com — no third-party ad cookies, no remarketing pixels, no audience-builder tags. If that ever changes, the change will be announced on this page first, and the new cookie group will be added to the list above before any new cookies are set.

Outbound publisher download links carry an attribution parameter (for example, an aggregator-specific suffix on the publisher's own URL). The parameter is read by the publisher's site after a tap and is what tells the publisher that the install came via TeenPattiHomes — useful for the publisher's analytics, irrelevant for any reader-side tracking. It is not a tracking cookie that follows you around the web.

4. How We Use Your Information

Aggregate analytics and server logs help us answer four small editorial questions, in service of the index:

• Which Pakistani regions are reading the index most heavily? Karachi, Lahore, and Islamabad lead in our existing logs; Faisalabad, Rawalpindi, Multan, and Peshawar follow at a smaller scale.
• Which APK notes pages are referenced most often? Useful for prioritising the next quarterly re-review (Editorial Standards Section 3, Step 6).
• Are server response codes healthy? 4xx and 5xx errors trigger an editorial check.
• Are publisher download links pointing to a working URL? Publisher-side URL changes are caught here first.

Community submission email — device-fit reports, wallet observation submissions — is read by the wallet observer and the editorial reviewer; the relevant aggregated facts may end up on the indexed APK's notes page (for example, "Easypaisa observed window 8-15 minutes during 8-11 PM PKT for small amounts"). The submitter's email address is not published, not shared with the publisher, and not added to any marketing list.

Editorial email — corrections, publisher correspondence, press requests — is read by the editorial reviewer and used only for the purpose stated in the message.

5. Cross-Border Data Transfer & Where Data Lives

teenpattihomes.com is hosted on infrastructure that may store or route data through jurisdictions outside Pakistan. The honest practical situation today:

• Static and dynamic content sits behind a global CDN. Edge caches may live in Singapore, Mumbai, Frankfurt, or other regional points of presence; the cached content is the public website, not personal data.
• Server access logs are held by the hosting provider in the region nearest the request, then aggregated for short-term operational purposes.
• Google Analytics 4 processes anonymised analytics in Google's regional infrastructure; Pakistan is currently routed through Google's Asia-Pacific region.
• Editorial and community email is delivered through a standard mail service whose servers may sit in the European Union or the United States.
• Indexed publisher data — your in-app balance, your deposit history, your KYC — never reaches TeenPattiHomes infrastructure at all (see the Aggregator Data Boundary at the top of this page). Cross-border treatment of that data is governed by the relevant publisher's privacy policy, not by ours.

Where personal data is transferred outside Pakistan by us, we rely on the standard contractual safeguards published by the relevant providers. We do not sell, lease, or barter personal data with any third party in any jurisdiction.

6. Under-18 Policy & Minor Protection

teenpattihomes.com is not directed at users under the age of 18 and we do not knowingly collect data that would identify a Pakistani reader as a minor. The APKs we index are real-cash apps for adults aged 18 and over only, in alignment with PECA 2016 and the underlying publisher rules.

If you are a parent, guardian, or school administrator and you believe a minor in your household has used a teenpattihomes.com link to install a real-cash APK:

• Open the device's Google Play parental controls and review installed apps. APKs installed via sideload still appear in the standard installed-app list.
• Check the device's recent JazzCash or Easypaisa transaction history. Repeated small transfers to a single merchant identifier are the most common pattern.
• Email [email protected] with the APK name (not the minor's name). We will refer the request to the relevant publisher's compliance team for account-level self-exclusion at the operator side. Publisher account closure is normally completed within three to five business days; we follow up if it is not.

The Responsible Gaming page carries additional minor-protection guidance and resources.

7. Retention Periods & Deletion

"How long do you keep my data?" depends on what the data is. The retention defaults:

• Server access logs: 30 days rolling. Sufficient for operational debugging; long enough to catch a slow-burning bot pattern; short enough to limit retention exposure.
• Analytics aggregate data: 14 months (the Google Analytics 4 default). Lets us compare year-on-year reader patterns without holding raw event data indefinitely.
• Community submissions: 24 months from last related action. Long enough to handle a quarterly re-review cycle plus one follow-up; short enough to not accumulate stale reader data.
• Editorial email: 24 months from last reply.
• First-party cookies: 12 months from last visit. Resets a quiet reader's consent state on a sensible cadence.
• Publisher correspondence: 5 years from last action. Useful for the editorial backlog and for any later index removal review.

If you want any of the data above deleted before its retention default, email [email protected] with a clear deletion request. We acknowledge within one to two business days and complete deletion within 30 calendar days, except where retention is required by law (for example, an active legal-hold request).

8. Reader Rights (GDPR-Style, Pakistan-Aware)

Pakistan does not yet have a single unified data-protection statute equivalent to the European GDPR. We have chosen to apply GDPR-style reader rights as a baseline anyway — partly because doing so is simpler than running two policies in parallel, partly because the rights are the rights any reasonable Pakistani reader should have.

You may, at any time, ask us to:

• Confirm what we hold about you. A short email summary of any data linked to your address.
• Correct inaccurate information. A misspelled email on a community submission, a wrong region tag, anything similar.
• Delete data subject to the retention rules above. Subject to legal-retention exceptions.
• Object to processing. For example, decline analytics cookies; decline community-submission follow-up; ask us to forget your previous device-fit report.
• Lodge a complaint. With the editorial team first, and — if relevant in future — with whichever Pakistani data-protection authority emerges from the legislative process currently under way.

Requests go to [email protected] with the words "Privacy request" in the subject line. We do not require formal legal language; a one-paragraph plain-English message is enough.

Rights requests about data held by an indexed publisher (your in-app account, your wallet history, your KYC) need to be sent to that publisher directly — those data are governed by the publisher's privacy policy, and we cannot act on them on the publisher's behalf. The publisher's contact path, where known, is listed on the relevant APK notes page.

9. Security Practice & Honest Limits

teenpattihomes.com uses HTTPS for every page, has HSTS enabled, runs behind a managed CDN that filters common attack patterns, and applies standard server hardening on the origin host. Editorial and community email is held on a provider that runs at-rest encryption.

We will not claim 100% security. No system on the public internet is. What we will claim: an aggregator holds far less personal data than a real-cash publisher, the data we do hold is protected by standard industry safeguards, and we will tell readers honestly if a relevant security incident occurs. A security incident notice would appear on this page within a reasonable time of the incident being confirmed, and we would email any affected community submitter directly.

10. Updates to This Policy

We update this policy when something material changes — a new analytics provider, a new community-submission flow, a Pakistani regulatory change, a new indexing-related data flow. When we update, we:

• Update the effective date and page version at the top of this page.
• Note the change in the editorial standards page if the change affects reader data flow.
• Honour the policy in force at the time of any earlier reader data submission.

Continued use of teenpattihomes.com after the effective date of an update means you accept the updated policy.

11. Contact & Privacy Officer

For privacy-related questions, deletion requests, GDPR-style rights requests, or security reports:

• Privacy & data requests: [email protected] (subject line "Privacy request")
• Security disclosures: [email protected] (subject line "Security disclosure")
• Community submissions, device-fit reports, wallet observations: [email protected]

The role of "Data Protection Officer" is currently performed by the editorial reviewer; if and when Pakistani law formalises a DPO requirement, we will appoint a named officer and update this section.

Page version: 1.0  |  Effective Date: May 11, 2026  |  Last Reviewed: May 10, 2026  |  Next scheduled review: May 2027

← Back to community home