About Guru11 India: who runs the desk and what the site is for

Guru11 India is run by a single editor and a single reviewer working on a weekly schedule. The site exists to give a reader a careful, slow read of the Guru11 fantasy app before any tap that touches a download, an OTP, a coupon field, a referral link, an APK file, or a payment step. This page explains who writes the pages, how the writing routine is structured, where the money to keep the site running comes from, and which editorial principles the desk refuses to compromise on.

The two-person desk

Guru11 India is not a content operation, an agency, or a media group. The desk has two named roles. The editor drafts every hub page from a working outline, walks the page through the operator's published terms, and ships the page once the reviewer signs off. The reviewer reads the same page with fresh eyes, marks anything that reads as a guess rather than a sourced claim, and either approves the page or sends it back with a short list of corrections. There is no third author, no ghostwriter, no AI-generated first draft, and no marketing team that rewrites the headlines after the editorial sign-off.

Because the desk has only two roles, the writing routine is slow on purpose. A typical hub page takes between four and six working sessions to move from outline to live page, with the reviewer joining on the third session. The bottleneck is the reviewer, not the editor, and the reviewer has the right to send a page back as many times as needed until every quoted figure, every date, and every operator term has been verified against a public source. That habit is the reason the site reads as careful rather than fast.

The desk is small by design. Two editors review each piece, and the second review is the one that catches the things the first review missed. A larger desk would have more capacity, but it would also have more drift in the editorial voice, and the drift would degrade the consistency that the readers have come to expect. The two-person structure is the smallest unit that supports a second review, and the second review is the unit that supports the editorial standard.

The weekly re-read habit

Every hub page on Guru11 India is re-read by the editor once a week. The re-read is a quiet pass with two goals: catch any drift in the operator's published terms since the last read, and catch any new question a reader might have after a tournament update or a payment-method change. The re-read does not always produce a published update; sometimes the only output of a re-read is a private note saying "still current as of date X". When the re-read does produce a change, the change is dated and the section that moved is flagged briefly so a returning reader can see what shifted without re-reading the entire page.

The re-read habit covers the about, contact, privacy-policy, and terms pages too, although those move less often than the operational hubs. The privacy policy is reviewed on the same weekly cycle, the terms page is reviewed whenever the editorial scope changes, and the contact page is reviewed whenever the inbox workflow changes. The reviewer reads those pages for tone and accuracy in the same way they read a coupon hub for tone and accuracy.

The weekly re-read is the habit of reading the published content as if encountering it for the first time, with a fresh reader's eyes. The re-read catches the sentences that the original draft got right but the original review didn't push back on, and the sentences that the original draft got wrong but the original review didn't notice. The re-read is the desk's quality control mechanism, and it's the mechanism that makes the editorial standard sustainable over time.

How the writing routine is structured

The editor works from a brief that lists the reader's likely question, the public source the answer should be tied to, the verification steps that need to run before publication, and the stop-point the page should leave the reader with. The brief is written before the page is drafted, and the brief is the document the reviewer reads first. If the brief is weak, the page goes back to the outline stage. If the brief is solid, the page is drafted, and the reviewer reads the draft against the brief rather than against the editor's prose.

The draft stage is followed by a verification pass. Every quoted offer, every quoted number, every quoted date, and every quoted operator policy is checked against the operator's published page on the same day the draft is finalised. Screenshots of those operator pages are archived in a private folder with a timestamp. If a source is paywalled, behind a region block, or otherwise inaccessible to the reviewer, the page is rewritten to remove the claim rather than relying on a partial quote, because a partial quote on a payment step is the most expensive kind of editorial mistake.

The writing routine is structured around the weekly re-read. Monday is the re-read day; Tuesday through Thursday is the writing days; Friday is the review day. The structure is loose enough to allow for breaking news, but tight enough that the published content always has at least one reviewer pass before it goes live. The structure has been refined over a year of running the desk, and the refinement is ongoing.

How the site is funded

Guru11 India is funded out of pocket by the editor. There is no investor, no sponsor, no agency retainer, and no commercial relationship with the Guru11 operator or with any peer fantasy app. The site does not run display advertising, does not host sponsored posts, does not sell newsletter slots, does not accept paid links, and does not earn an affiliate fee when a reader downloads the Guru11 app, claims a coupon, claims a referral bonus, or moves money through a payment gateway.

Because the site does not earn referral fees, the editor has no reason to push a reader toward a tap the reader did not plan. The page can stay neutral on whether the reader should deposit, on whether the reader should claim a particular offer, or on whether the reader should accept a forwarded APK from a group chat. The neutrality is structural, not just an editorial promise; it is what the funding model buys, and changing the funding model would force a rewrite of the about page before any other change shipped.

The site is funded through display advertising and affiliate links, with the affiliate links disclosed on the relevant pages. The display advertising is the primary revenue stream, and the affiliate links are a secondary stream. The desk does not accept payment for editorial coverage, and any operator that offers payment for coverage is referred to the contact channel for a polite decline. The funding model is the same as the editorial standard: transparent, consistent, and subject to the same review process as the content itself.

What the desk covers and what it does not

The desk covers the editorial questions a reader is most likely to type into a search box after seeing the Guru11 app for the first time: where to download it without falling for a forwarded APK, how the OTP login flow behaves, how to read the T&C of a coupon or a referral offer, what to screenshot before raising a payment dispute, and how to think through a fantasy cricket team selection. The desk covers those questions through stand-alone hub pages and through deeper blog posts that walk a single scenario end to end.

The desk does not sell Guru11 accounts. The desk does not invent coupon codes, does not publish welcome bonuses that the operator has not announced on its own page, and does not run giveaways that ask the reader to deposit money before claiming a prize. The desk does not operate a customer-support channel, does not recover locked accounts on the reader's behalf, and does not step between the reader and the operator once the reader has tapped the action button on the operator's side.

The desk covers: the Guru11 app, the payment flows on the app, the offer mechanics, the login flow, the APK distribution, the responsible-play tools, and the cross-hub scenarios that come up in the contact channel. The desk does not cover: the operator's financial performance, the operator's internal team, the operator's relationship with regulators, or any other topic that requires the operator to share information that the operator has not already published.

Editorial principles the desk refuses to compromise on

The desk has a written short list of principles that governs every page. The desk does not target minors in its content, does not promote guaranteed prediction services or paid tipster channels, and does not run sponsored posts or swap links for money. Those three refusals are non-negotiable and are checked before every publication. A page that violates any of them is removed, regardless of how much traffic it would attract.

The desk also has three positive principles. Every claim is linked to a public source so the reader can verify. Every page ends with a responsible-play reminder so the reader leaves with a stop point in mind. Every warning sign on a hub page is paired with a better sign so the comparison is concrete. Those three positive principles are what give the editorial pages their texture, and the reviewer is the final reader on whether a draft has met all three before publication.

The principles are: factual accuracy first, reader trust second, operator relationships third. The order matters because the three priorities are sometimes in tension, and the order determines which one gives way when they conflict. The desk has never had a situation where factual accuracy and reader trust conflicted, and the desk has had several situations where operator relationships and reader trust conflicted. The order has held in all of them.

Independence, disclosure, and accountability

Guru11 India is not affiliated with the Guru11 operator, with any sponsor, or with any marketing partner. The site does not earn a referral fee on a download, a deposit, or a bonus claim, and the about page exists partly so that statement is on the record rather than buried in a privacy footnote. If the funding model ever changes, this page is the first place the change is announced, and the announcement is dated so a returning reader can see when the shift happened.

Accountability runs through the contact channel. A reader who spots an inaccuracy, a broken link, a missing responsible-play reminder, or a fact that has drifted since publication can write in, and the desk reads the message, verifies the report against the operator's public terms, and ships a correction when the report is confirmed. The desk treats corrections as a public artefact of the editorial work, not as a private email exchange, and the reviewer reads every correction note the same way they read a draft.

The desk is independent of the operator, and the independence is disclosed in the editorial page. The disclosure is not a legal formality - it's a statement of fact, and the statement is enforced by the editorial standard. The accountability for the editorial standard rests with the two editors, and the contact channel is the place to flag any failure of the standard. The flag is read, the failure is investigated, and the correction is published if the investigation confirms the flag.

How updates and corrections are handled

Updates fall into two categories. Drift updates happen when the operator's published terms have moved since the page was last re-read; the drift update ships within a few working days, with the changed section flagged at the top of the page for at least 30 days. Reader-reported updates happen when a reader sends a note through the contact channel and the report is verified; the reader-reported update ships with a brief credit line such as "reader-reported, verified against the operator's public terms" unless the reader has asked to remain anonymous.

The desk does not promise to reply to every message, but every message is read. Where the topic falls inside the editorial scope, the reply includes the next step and, where relevant, the page the desk is going to update. Where the topic falls outside the editorial scope, the reply points the reader to the operator's published support route or to the responsible-play hub so the reader can keep moving without the contact channel turning into a queue.

Updates and corrections are handled through the same review process as the original content. The update or correction is drafted, reviewed, and published with a date stamp. The date stamp is visible on the page, and the date stamp is the signal to the reader that the content has been updated since the original publication. The signal is important because the content might have been correct when it was published but is no longer correct, and the date stamp is the reader's way of knowing that.

What the desk will not write about

The desk will not publish predictions for specific matches, captain picks for specific fixtures, or dream-team combinations for specific games. The desk treats the operator as the data source for team announcements and the BCCI feed as the data source for confirmed XIs; speculative team selection is out of scope. A post that walks through a generic captain-pick decision tree is fine; a post that names a specific player as the "must-pick captain" for a specific match is not.

The desk will not publish winner testimonials, prize-claim stories, or content that looks like an advertisement for any specific fantasy app. The hub pages already cover the operator-facing details; the editorial coverage exists for the reader-facing analysis. A line that reads like marketing copy gets cut during the reviewer pass, even if the underlying claim is factually accurate.

The desk will not name a specific competitor in a way that implies a head-to-head ranking. The compare-options hub handles the side-by-side treatment in a measured format; the editorial coverage refers back to that hub rather than restating the comparison in a more sensational form. This is a deliberate boundary, and the contact channel will redirect a request that crosses it back to the relevant hub.