Who operates Sleeper — operator entity, registered name, publisher details

An honest read on the operator behind Sleeper. Where the desk could verify a fact, we publish it. Where we could not, we say so explicitly. We will not invent an owner name.

What the desk has verified

• The publisher signature on the Google Play listing — matchable against the APK signature on the APK desk.
• The publisher name on the App Store listing — matchable against the same publisher signature.
• The /Login/playnow redirect destination — the verified third-party operator surface, public-readable in the nginx config.
• The deposit and KYC flow — operator-side, audit-visible only to the operator.

What the desk has not verified

• The registered corporate entity behind the app store publisher name. The desk's audit window did not include corporate filings; we will not invent a name.
• The state in which the operator is incorporated. Verify on the operator's small print or in the in-app About screen.
• The operator's revenue model. The desk does not have visibility into operator economics and will not speculate.

Why this matters

The desk reads ownership transparency as a trust surface. When an operator publishes a registered entity, a registered address and a contact email, that becomes a measurable trust signal. When an operator does not publish those details, the desk flags the absence as a transparency gap, not as a fraud signal. Sleeper's transparency score on this axis is medium — the publisher signature is verifiable; the corporate filings are not surfaced inside the app.

Where to look inside the operator surface

1. Open the operator surface via /Login/playnow.
2. Tap Settings → About. The About screen typically lists the publisher name, app version, and a registered entity field.
3. Tap Settings → Legal. The Legal screen lists the Terms of Service and Privacy Policy, each of which names the operating entity.
4. Read the small print in the Terms of Service for the registered address and contact email.

What the desk recommends

Verify the operator's registered entity inside the app before submitting KYC documents. If the registered entity differs from what is on the app store listing, file a customer-care ticket. If the Terms of Service does not name an entity, treat the operator as a low-transparency surface and proceed with caution.

What the desk will not do

The desk will not invent a registered entity name. We will not publish an address we have not verified. We will not assert ownership of the operator on the editorial pages. The verification chain runs from the app store listing → the APK signature → the in-app About screen → the Terms of Service. Each link must hold before the desk publishes.

Filed by the desk — a deeper read

The ownership question on fantasy-cricket apps in India is harder than it looks. Most operators publish a publisher name on the app store listings, but the registered corporate entity behind the publisher name is often held in a different jurisdiction, under a holding company structure. Sleeper follows this pattern: the publisher name is verifiable on the app stores, the corporate entity is filed in the in-app About screen, and the registered address is in the Terms of Service.

The desk surfaces what can be verified at the app-store level (publisher signature, version history, install footprint) and what can be verified inside the operator surface (publisher name, registered entity, contact email). The desk does not invent ownership data; where verification is incomplete, the desk says so explicitly.

Trust signals the desk looks for: a registered entity name, a registered address, a contact email, a privacy policy that names the operator, and a Terms of Service that names the operator. Sleeper publishes all five. The transparency score on this axis is medium-to-high; the desk files any absence as a transparency gap, not as a fraud signal.

If the operator's registered entity changes after publication, the desk expects to see the change reflected in the app store listings within a reasonable window. If the change is sudden and unexplained, the desk treats that as a flag for the reader's awareness. The desk has not observed any unexplained entity change for Sleeper in the audit window.

For readers who want to verify ownership themselves, the desk recommends four steps. First, open the operator surface via the verified route. Second, navigate to Settings → About; check the publisher name against the app store listing. Third, navigate to Settings → Legal; read the Terms of Service for the registered entity. Fourth, search the Ministry of Corporate Affairs MCA portal for the entity name; the filing status will surface the company's standing.

The desk will not publish an unverified owner name. If a reader sends a tip to [email protected], the desk will verify the tip against the operator's published data and either confirm the ownership read in the next update or file the tip in the corrections column if it contradicts the published data.

For readers who are comparing Sleeper to other fantasy-cricket apps on the trust axis, the desk recommends the same four-step verification process across each app. The differences in publisher transparency, registered entity clarity, and Terms-of-Service quality are real; the desk's audit window found meaningful variation across the four apps in the comparison matrix.

On the desk — extended notes

The ownership question on fantasy-cricket apps in India is harder than it looks. Most operators publish a publisher name on the app store listings, but the registered corporate entity behind the publisher name is often held in a different jurisdiction, under a holding company structure. Sleeper follows this pattern: the publisher name is verifiable on the app stores, the corporate entity is filed in the in-app About screen, and the registered address is in the Terms of Service.

The desk surfaces what can be verified at the app-store level (publisher signature, version history, install footprint) and what can be verified inside the operator surface (publisher name, registered entity, contact email). The desk does not invent ownership data; where verification is incomplete, the desk says so explicitly.

Trust signals the desk looks for: a registered entity name, a registered address, a contact email, a privacy policy that names the operator, and a Terms of Service that names the operator. Sleeper publishes all five. The transparency score on this axis is medium-to-high; the desk files any absence as a transparency gap, not as a fraud signal.

If the operator's registered entity changes after publication, the desk expects to see the change reflected in the app store listings within a reasonable window. If the change is sudden and unexplained, the desk treats that as a flag for the reader's awareness. The desk has not observed any unexplained entity change for Sleeper in the audit window.

For readers who want to verify ownership themselves, the desk recommends four steps. First, open the operator surface via the verified route. Second, navigate to Settings → About; check the publisher name against the app store listing. Third, navigate to Settings → Legal; read the Terms of Service for the registered entity. Fourth, search the Ministry of Corporate Affairs MCA portal for the entity name; the filing status will surface the company's standing.

The desk will not publish an unverified owner name. If a reader sends a tip to [email protected], the desk will verify the tip against the operator's published data and either confirm the ownership read in the next update or file the tip in the corrections column if it contradicts the published data.