Contact Prime Card Rummy

1. Primary channel

Electronic mail remains the authoritative channel:

support@primecardrummy.org

Use a descriptive subject line (e.g. “Routing drift — {AppName} — {ticket ID internal}”). Body text should articulate:

1. Listing slug or definitive URL presently shown on primecardrummy.org.
2. Target HTTPS destination you believe should replace an outdated hop.
3. Evidence bundle: storefront screenshots, registrar/WHOIS artefacts if public, press releases naming compliance jurisdictions, escalation phone trees, AML registration excerpts when published, influencer codes if they alter routing parity, storefront bundle IDs aligning with APK signing certs.
4. Your relationship to the request (authorised operator liaison, regulated affiliate network compliance officer, forensic researcher, impacted player—please disclose bias candidly).

We endeavour to acknowledge eligible queue items within reasonable editorial windows. No SLA is promised; static rebuild cadence dominates.

2. Operational scope handled via inbox

• Outbound hyperlink hygiene corrections.
• Trademark usage disputes where nominative fairness is misunderstood.
• Material misstatements anchored to verifiable artefacts (bonus math that changed fleet-wide vs. nuanced cohort deltas—please distinguish).
• Lawful data protection requests enumerated under Clause 9 of our Privacy Policy (privacy@ alias not provisioned separately; mailbox above triages jurisdictional merges).

Not handled:

• Ledger disputes—chargebacks, freezes, dormant sweeps—route through operator ticketing and banking rails.
• Urgent compulsive gambling crises—consult local crisis hotlines/emergency authorities; inbox staff are not clinically trained responders.

3. Telephone / messenger policy

Desk workflow is deliberately asynchronous email-first. Messaging apps, voice bursts, voicemail drops without written trails, unsolicited calendar invites—these modalities are discouraged because audit trails degrade. Regulatory-grade escalations referencing docket identifiers may attach PDF pleadings separately; zipped malware-laden artefacts are quarantined.

4. Physical correspondence

Postal handling is sporadic unless contractually mandated. Email before shipping certified mail—the registered address rotates with hosting counsel. Omit until requested.

5. Spam, phishing, BEC

Emails mimicking @primecardrummy.org with homoglyphs, cousin domains (prime-cards-rummy.co, Unicode confusables)—treat anything soliciting prepaid cards, OTP codes, APK side loads, Telegram “recovery agents”—as fraudulent. Authentic desk correspondence never demands cryptographic seed phrases.

6. Responsible disclosure — security / abuse

Suspected subdomain takeover, dangling DNS proofs, dangling GitHub PATs scraped from forks, dangling Cloudflare Tunnel identifiers—email support@ with CVE-style summary, reproducible curls (redact secrets), and optional PGP public key fingerprint if rotating sensitive artefacts. Honour coordinated disclosure etiquette; reckless public dumps prior to remediation may disqualify goodwill crediting unless imminent mass harm dictates otherwise.

7. Media & speaking

Interview requests—including podcast spots, investigative journalism pairings, conference panels debating India’s offshore licensing grey zones—pitch via inbox with distribution channels, embargo expectations, attributable vs. deep-background constraints, indemnity regimes, clipping rights. Principal researchers may decline if itineraries conflict with audit lockdown windows.

---

We read carefully. Verbosity correlates with seriousness.