Verification
Reading the verification chain the way the editor reads it
The verification chain is the editorial layer the broadcast can't carry. The desk's read on the login page's verification chain.
Read the policy →How to access your Odds account from the web
Odds is the editorial desk for the esports competition network. The desk does not publish betting lines, fantasy-pick cards, or fabricated statistics. The editorial desk is separate from the operator account flow, and the login page is the one place where the editorial read and the operator account flow meet. Use this page to understand what the login page does, what it doesn't do, and how the editorial verification chain confirms the access workflow.
What the login page does
The login page is the entry point to the operator account flow. The login page accepts the username, the password, and the two-factor authentication code, then runs the standard verification chain. The login page is set up to work with the operator's primary account flow, the regional-language coverage, and the editorial verification chain. The login page does not require a subscription, does not publish betting lines, and does not promote a particular team's chances.
The login page is open to all readers aged 18 and over. The login page does not collect any information beyond the username, the password, and the two-factor authentication code. The login page does not share any information with the editorial desk, and the editorial desk does not share any information with the login page. The two are separate by design.
How the login page works
The login page runs the standard verification chain. The username is checked against the operator's account database. The password is checked against the operator's authentication system. The two-factor authentication code is checked against the operator's two-factor authentication system. The verification chain is logged with the operator's account workflow, and the verification chain is published with the editorial verification chain.
The login page is built to be accessible from every major browser, every major device, and every major regional-language coverage. The login page is built to be accessible to readers aged 18 and over, and to readers using screen readers, keyboard navigation, and touch devices. The login page is built to be accessible to readers using the editorial desk's accessibility layer.
Account access without a web login
Not every operator account flow has a web login. Some operators run entirely through the mobile app, with the operator's mobile app serving as the primary account flow. For readers who use the mobile app, the login page is the entry point to the operator's mobile app verification chain. The login page is built to redirect the reader to the operator's mobile app store, where the reader can download the app and complete the verification chain.
The login page is built to be accessible from every major browser, every major device, and every major regional-language coverage. The login page is built to be accessible to readers aged 18 and over, and to readers using screen readers, keyboard navigation, and touch devices. The login page is built to be accessible to readers using the editorial desk's accessibility layer.
Two-factor authentication
The login page supports two-factor authentication. The two-factor authentication code is generated by the operator's two-factor authentication app, then entered into the login page. The two-factor authentication code is checked against the operator's two-factor authentication system, and the verification chain is logged with the operator's account workflow.
The two-factor authentication is optional, but the editorial desk strongly recommends it. The two-factor authentication adds an extra layer of verification to the login page, and the verification chain is published with the editorial verification chain. Readers who do not use two-factor authentication can still access the login page, but the editorial verification chain will note the absence of the two-factor authentication layer.
Account recovery
The login page supports account recovery. The account recovery flow runs through the operator's account recovery system, with the verification chain and the verification date both published in the editorial verification chain. The account recovery flow is built to be accessible to readers aged 18 and over, and to readers using screen readers, keyboard navigation, and touch devices.
The account recovery flow is initiated by the reader, with the operator's account recovery system sending a recovery code to the reader's registered email or phone. The recovery code is checked against the operator's account recovery system, and the verification chain is logged with the operator's account workflow. The account recovery flow is built to be accessible to readers using the standard accessibility layer.
Editorial verification chain
The login page is published with the editorial verification chain. The editorial verification chain documents the source, the verification date, the verification result, and the editorial context. The editorial verification chain is published with the login page footer, and the editorial verification chain is available on request through the contact desk.
The login page is open to all readers aged 18 and over. The login page does not require a subscription, does not publish betting lines, and does not promote a particular team's chances. The editorial read is published with the verification chain documented in the page footer, and the source dossier is available on request through the contact desk.
From the desk
What the editorial desk recommends
Three working notes from the editorial desk on the login page. The verification chain, the two-factor authentication, and the account recovery flow — together they read the login page the way the editor reads the script.
Access
Two-factor authentication and the editorial workflow
The two-factor authentication is the editorial layer the broadcast can't carry. The desk's read on the two-factor authentication and the editorial workflow.
Read the guide →
Editorial standards
What the editorial desk reads on this page
The editorial desk reads three working documents on every page the desk publishes. The published record is the editorial layer the broadcast can't carry — the source, the verification date, the verification result, and the editorial context. The editorial analysis is the editorial timing the broadcast can't carry — the editorial read, the editorial verification chain, the editorial context. The editorial coverage is the editorial follow-up the broadcast can't carry — the editorial window, the editorial cadence, the editorial follow-up.
The editorial read pairs the published record with the editorial analysis and the editorial coverage. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer. The editorial read is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
The broadcast studio carries the editorial layer
The broadcast studio is the editorial layer the broadcast can't carry. The studio carries the editorial read, the editorial verification chain, and the editorial context. The editorial read is published with the editorial verification chain, and the editorial verification chain is published with the page footer.
The verification chain is the editorial record
The verification chain is the editorial layer the operator's marketing channel can't carry. The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.
Editorial chain
How the editorial verification chain is documented
The editorial verification chain is documented across four layers. The source layer identifies the official channel the editorial desk cross-checked against — typically the operator's official documentation, the league's official channel, the team's official social media, or the broadcast partner's official bracket. The verification date layer identifies when the editorial desk cross-checked the source. The verification result layer identifies the editorial desk's conclusion — confirmed, refuted, or unresolved. The editorial context layer identifies the editorial reasoning behind the result.
The editorial verification chain is built to be transparent. The chain is published with the page footer, and the chair is available on request through the contact desk. The chain is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
Editor's note
What the page covers in three working documents
First, the published record — the source, the verification date, the verification result, and the editorial context. Second, the editorial analysis — the editorial read, the editorial verification chain, the editorial context. Third, the editorial coverage — the editorial window, the editorial cadence, the editorial follow-up. The three documents are the editorial layer the broadcast can't carry, and the editorial read is published with the editorial verification chain.
The editorial desk's read on the broadcast
The editorial desk reads the broadcast the way the casters read the script. The desk reads the editorial layer, the editorial verification chain, and the editorial context. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer.
Verification
What the editorial desk signs up to
The desk verifies every login page workflow against the operator's official account recovery system, the operator's official two-factor authentication system, and at least one independent source. The verification chain is published with the page footer.
Frequently asked
What readers ask the desk most
How does the Odds login page work?
The login page accepts the username, the password, and the two-factor authentication code, then runs the standard verification chain. The verification chain is logged with the operator's account workflow.
What if I don't have a web login?
Some operators run entirely through the mobile app. The login page redirects to the operator's mobile app store, where the reader can download the app and complete the verification chain.
Should I use two-factor authentication?
The editorial desk strongly recommends two-factor authentication. The verification chain is published with the login page footer.
How does account recovery work?
The account recovery flow is initiated by the reader, with the operator's account recovery system sending a recovery code to the reader's registered email or phone. The verification chain is published with the page footer.