Cautious "what is publicly known" framing. We never invent ownership, CIN, GSTIN, address, or contact details. The owner page carries what can be verified, and labels what can't.
The owner and operator of the PlayerzPot app is identified through the publisher record on the Google Play Store and the Apple App Store. The publisher name listed there is the canonical public-facing identifier for the entity behind the platform.
Beyond the publisher record, public ownership data is thin. We do not invent company registrations, CINs, GSTINs, registered addresses, or individual owner names. Where data isn't published in an authoritative source, the desk labels it as unverified rather than guessing.
The desk treats these as fields to verify through authoritative sources, not to publish on this page.
The operator publishes contact routes inside the PlayerzPot app — the Help menu, the FAQ section, and the email support address. The customer care page walks through those routes and explains why the desk doesn't publish a phone number it can't verify.
The owner page is intentionally cautious. The desk follows a "publish only what is authoritative, label everything else" rule. If PlayerzPot's public-facing record changes, the page updates. The about page carries the editorial standards the desk applies across the site.
The publisher record on the Google Play Store and Apple App Store is the canonical public-facing identifier.
Registered address and company identifiers are not authoritative-published. Verify via official channels if you need them.
The desk doesn't publish corporate structure without authoritative confirmation.
The in-app Help menu is the canonical route. The customer care page walks through it.
The owner page follows a "publish only what is authoritative, label everything else" rule. Inventing company registrations, CINs, GSTINs, addresses, or individual owner names would create liability — both for the desk and for the user, who might rely on the wrong data.
The cautious framing is also defensive against impersonation. Phishing sites sometimes copy ownership details from editorial sites; if the editorial site doesn't publish unverifiable data, there's nothing for phishers to copy.
For users who need to verify PlayerzPot's ownership, the authoritative sources are the Ministry of Corporate Affairs (MCA) portal, the GST Network (for GSTIN), and the Play Store / App Store publisher records. Cross-check the publisher name on the store against the MCA database.
The desk doesn't link to specific MCA records because the records change. Verify through the official portal — that's the right reference.
Ownership transparency is a real signal for a fantasy platform. A platform with a thin public record is harder to hold accountable. The desk treats ownership transparency as one of the four axes of the editorial review — but never invents data to fill the gap.
The PlayerzPot review carries the full editorial frame, including the ownership-transparency read.
The owner page is part of the trust colophon — the section of the site where the desk states what it verifies and what it couldn't confirm. The colophon frames the editorial standard, not the company's record.
For the broader editorial standard, the about PlayerzPot page walks through how the desk reviews claims, sources, and numbers.
"Publicly known" means information published in an authoritative source — the Play Store or App Store publisher record, the MCA database, the GST Network, the platform's own privacy policy or terms of service.
"Not publicly known" means information that the desk couldn't find in an authoritative source. This includes many of the standard corporate identifiers — CIN, GSTIN, registered address — that a user might assume are published.
The desk doesn't invent data to fill the gap. If the data isn't authoritative-published, the page labels it as "not authoritative-published" or "verify via official channels."
PlayerzPot's publisher record on the Google Play Store and Apple App Store is the canonical public-facing identifier for the entity behind the platform. The publisher name is what users should match against the MCA database if they want to verify ownership.
The publisher record is also what the desk uses for the editorial review. The platform's publisher name is a stable identifier — it doesn't change with marketing campaigns or product updates.
For users who want to verify the publisher record, open the Play Store or App Store listing and check the publisher name. Mismatched names between the store listing and the editorial site are a red flag.