1. Why an Operator Bothers With Editorial Standards

Most "editorial standards" pages on the Pakistani real-cash card-game web belong to review sites: aggregators ranking operators against one another, declaring methodology and affiliate splits. That is a useful editorial discipline for a review site. It is the wrong discipline for an Operator.

An Operator has a different editorial problem. We do not rank anyone. We do not review anyone. What we publish are claims about our own product — "Easypaisa withdrawals settle within 3 business hours during 8 AM–11 PM PKT", "first-time payouts above 10,000 PKR require a CNIC photo", "the RNG seed is logged and weekly-audited". Those are not opinions. They are testable, falsifiable statements about a real software product that takes real PKR from real Pakistani players. The editorial discipline we need is the discipline that stops an Operator from quietly drifting away from claims that used to be true.

This page is that discipline written down. It tells a Pakistani player, a journalist, a regulator and a future version of our own team exactly how a number on this site gets there and what happens when it stops being correct.

2. Who Writes and Who Reviews

Six people touch anything that goes on this site. We name the roles below; the people behind the roles rotate but the roles do not.

No single person publishes alone. The Editorial lead and one other named role have to sign off, in writing, on the internal page changelog before a deploy. This is not bureaucracy — it is what stops a tired late-night edit from drifting a withdrawal-window number from "3 business hours" to "3 hours" and quietly breaking a published claim.

3. What We Publish — and What We Refuse to Publish

The shortlist of things you will find on this site:

• In-app product reference: game rules, payout tables, bonus terms, RG tools — mirrored from the live build, not aspirational
• Trust pages: About, Terms, Privacy, Responsible Gaming, Contact, this Editorial Standards page
• Blog / educational: guides to Teen Patti, Dragon Tiger, Andar Bahar variants — written for Pakistani Android players, no "winning system" claims
• Compliance disclosures: 18+ policy, geo-fencing to Pakistan, wallet rails, helpline number

The shortlist of things this site will not publish, ever:

• Rankings or comparisons of other Teen Patti operators (we are an Operator, not an aggregator)
• Sponsored "best app in Pakistan" lists, in either direction (paid by us or paid by others)
• "Winning system" or "guaranteed strategy" copy for any real-cash game — the house edge is published and that is the truth
• Testimonials we cannot verify — if a quote is on this site, the author has signed off in writing
• Affiliate links, including masked ones — outbound links go only to independent helplines, government portals, payment-wallet rails or original-source documents
• "Limited time" countdown timers in the in-app bonus copy or anywhere on this site — pressure tactics are not editorial integrity

4. The Fact-Check Ladder for a Product Claim

Any number on this site that describes our own product passes the four steps below before publish. A "product claim" means anything testable: payout time, KYC duration, RNG audit interval, monthly active player count, withdrawal volume.

1. Step 1 · Source the number from a primary log. The Editorial lead pulls the number from the in-app system itself — the withdrawal ledger, the KYC queue dashboard, the audit log. Not from memory, not from last quarter’s slide deck, not from a Slack message.
2. Step 2 · Cross-check against a second source. A second internal view (a wallet partner’s reconciliation report, an SBP-required quarterly file, a third-party audit summary). If the two disagree by more than 5%, the claim does not get published until the disagreement is reconciled.
3. Step 3 · Phrase it conservatively. If the median is 2 hours 40 minutes, we publish "within 3 business hours", not "within 2 hours". The published number is always the slower of the two reasonable interpretations.
4. Step 4 · Date-stamp it. Every product claim that gets a number gets a "Last reviewed" date on the page footer. The next-review trigger is set in our internal queue at +30 days for product claims and +180 days for trust-page structural claims.

The ladder is conservative on purpose. An Operator that publishes its best number is one drift away from being wrong. An Operator that publishes its safe number can almost always keep its claim true.

5. Source Rules — What Counts and What Does Not

For product claims about our own service, only four source types count:

• Primary internal log. The actual database row, queue entry or ledger that records the event we are claiming about. Highest weight.
• Wallet-partner reconciliation file. Easypaisa and JazzCash send us a daily settlement file that we keep for SBP audit. This is the second-strongest source for any deposit-or-withdrawal claim.
• Independent audit summary. Our quarterly game-integrity audit, posted publicly on the blog. This is the source for RNG and hand-resolution claims.
• Public regulator notice. SBP, PTA or PECA-related letters that change rails or compliance obligations. This is the source for compliance claims on the Terms and Privacy pages.

What is not a source: a player’s review on a third-party forum, a marketing claim from a different operator, an AI summary of "industry standards", a screenshot from a competitor’s app, anything that begins with "we have always done it this way".

For background pages that are not product claims — a guide to Teen Patti history, a primer on Dragon Tiger card rules — we cite primary game rules from established card-game references and we do not invent rule variants. Where Pakistani regional rule variations exist, we say so plainly and we name the variant region (Karachi household rules, Lahore tournament rules, common rural Punjab variants).

6. Corrections — How a Wrong Page Gets Fixed

We will get pages wrong. The discipline is how fast we fix and how visibly.

The changelog itself lives on the blog, dated, and is editable only by the Editorial lead. We do not silently edit pages and pretend the old version did not exist. The "Last reviewed" line at the bottom of every trust page is the single date a player should look at if they suspect a number is stale — if it is older than 9 months, write to [email protected] and we will re-check on a priority queue.

7. Affiliate, Sponsored Content, Gifts

The longer version is that an Operator with even a small affiliate stream develops an editorial bias toward whichever app pays more, and the bias creeps into the writing in ways the team itself stops noticing. We chose to not have that stream — not as a marketing posture, but because the alternative is a corruption we cannot reliably detect inside our own copy.

Gifts received from anywhere — wallet partners, conference organisers, regulators’ offices, journalists, players — are logged in an internal gifts register if they exceed 5,000 PKR retail value, and either declined or donated to Karwan-e-Hayat. The register is reviewed by the compliance reader quarterly.

If a writer joins the team from another Pakistani operator, they declare the prior relationship and do not edit any page that mentions wallets, bonuses or KYC for the first 6 months. This is in the internal HR contract, not just here.

8. Conflicts of Interest

The conflicts an Operator’s editorial team can have are narrower than a review site’s, but they are real.

• Team members may not gamble on the 3 Patti Blue app. Editorial, SLA owner, RG owner, compliance reader, game-integrity engineer and Urdu reviewer accounts are blocked from real-cash play, automatically, against their registered CNIC numbers. We tested this internally before publishing the rule.
• Direct family relationships to other Pakistani Teen Patti operators must be declared. If a writer’s sibling, spouse or parent works at a competing app, that writer cannot publish comparative content (though as § 3 already explains, we do not publish comparative content at all — so the rule is currently a belt-and-braces measure).
• Investments in payment-wallet companies must be disclosed. If a team member holds equity or paid options in a JazzCash- or Easypaisa-affiliated entity above 0.1% of personal net worth, it goes in the conflicts register and they recuse from the SLA-owner role.

The conflicts register is internal and reviewed by the compliance reader quarterly. We do not publish individual entries (those have personal-data implications under our Privacy Policy), but we will confirm to a regulator or journalist on written request that the register exists and is non-empty.

9. AI Use Disclosure

Where AI assists us

• Initial draft outlining for blog and guide pages — an AI tool may suggest a section order, which the Editorial lead then rewrites by hand from primary sources.
• English-to-Roman-Urdu phrasing checks — an AI tool helps the Urdu reviewer rough-pass a translation, but the final Urdu copy is read and signed off by the human Urdu reviewer.
• Cross-site consistency checks — we run AI-assisted similarity scans to make sure two of our own pages do not silently duplicate each other’s wording.

Where AI is forbidden

• Any number on a product claim — withdrawal times, KYC turnaround, bonus percentages, RG cooling-off durations, helpline opening hours. These come from primary logs only.
• Any wording on the Responsible Gaming page, the helpline section of any page, or any 18+ language — AI tools have a known habit of softening these and we will not allow that drift.
• Any legal or compliance statement on Terms, Privacy or this page — these are read and signed off by human counsel before publish.
• Any user testimonial, case study or "real player story" — if a quote is on this site it was given by a real named human who saw and approved the wording.

If you read a paragraph on this site that sounds like a generic gambling-industry AI summary — the kind of sentence that talks vaguely about "today’s rapidly shifting Pakistani gaming sector" without naming a single Karachi neighbourhood, wallet, regulator or actual rule — please write to [email protected] with the page URL and the offending paragraph. That is a drift we will treat as a serious editorial bug.

10. How a Pakistani Player Can Challenge Anything On This Site

The whole point of an editorial standards page is to make this step usable.

1. Write to [email protected] with the URL of the page, the paragraph you think is wrong, and one sentence on why. You do not need to be a journalist or have any credential. A Faisalabad player who thinks a withdrawal-time claim does not match their last three payouts is a valid challenger.
2. Expect a written first reply within 2 business days. The reply will say either "we have re-checked and the page is correct, here is the source" or "you are right, the fix will be live by [date]". We do not bury the reply in a "we will investigate" non-answer.
3. If the fix is material, expect a public note in the changelog on the blog within 14 days. Your name will not be in the public note unless you ask for it to be.
4. Escalation if step 2 is unsatisfactory: use the Contact page’s 5-step complaint escalation ladder — the director-level review at step 3 covers editorial accuracy disputes as well.

We treat editorial challenges from players the way an Operator should: not as PR threats, but as free quality-assurance work that we did not pay for. The challenger is doing us a favour. We try to write the response in that spirit.

11. Review Cadence — When We Re-Check Ourselves

Three different schedules run in parallel.

• Daily. Customer-support tickets are read for any phrase like "the page says X but I got Y". Recurring patterns are surfaced to the Editorial lead the same week.
• Monthly. Every published product-claim number is re-pulled from primary logs and compared to the page. Any drift > 5% triggers the corrections ladder in § 6.
• Every six months. Every trust page (this page, About, Terms, Privacy, Responsible Gaming, Contact) is read end-to-end by the Editorial lead plus one of the other six roles. The "Last reviewed" line is updated on publish — not on the read, but on the publish, so a stamped date always reflects a real re-read.

Last reviewed: 15 May 2026 · Page maintainer: Editorial team, 3 Patti Blue Pakistan · Reviewed on a 6-month cadence · corrections via [email protected].