# Contact Cricketin Source: https://cricketin.org/en/contact [By Rajeev Sathe](/en/authors/editor-in-chief), Editor-in-Chief. [Reviewed by Karthik Iyengar](/en/authors/data-editor), Data Editor. Updated 10 Nov 2026. Editorial policy: https://cricketin.org/en/editorial-policy 18+. Betting carries financial risk and can become addictive. Free helpline Tele-MANAS: 14416. --- Find the planned routes for editorial corrections, privacy concerns, legal notices, copyright requests, and press enquiries at Cricketin. Cricketin keeps separate routes for account and payment support, content fixes, privacy, legal notices, copyright and press. Each route appears on this page once it is live, and no address is printed before then. The table below shows what to include in each request. A fact report that gives the page URL and a source gets checked. ## Real contact routes are needed before launch It is safer to show a gap than a fake email address. We have no checked public inbox, phone number, post address, or named contact in the project record. We will not make one up. Until a route is published here, it does not exist: we would rather show the gap than print an inbox nobody reads. Each row below says what to send, so that a route is useful from its first day. ## Send each request to the right route Different requests need different people. A fact fix needs a source. A privacy request can hold private data. A legal notice needs the exact page and reason. If you are not sure, use the general content route when it is live. Do not send a password, one-time code, ID file, or bank data unless a checked route asks for it and says why. See the [Corrections Policy](/en/corrections) and Log and the Privacy Policy. ## Routes the owner must set up **Table 1. Contact routes to verify** | Request | What to send | Route and reply goal | |---|---|---| | Account or payment question | Registered email or phone, what happened, and when | Not published yet | | Fact or source fix | Page URL, words at issue, and source or sum | Not published yet | | Privacy request | Request type, page or account detail, and safe reply way | Not published yet | | Legal notice | Sender, page URL, exact request, and proof | Not published yet | | Copyright request | Work, page URL, rights reason, and reply detail | Not published yet | | Press question | Outlet, deadline, topic, and reply detail | Not published yet | A reply time is worth printing only once it can be met, so no target appears above yet. ## Use the editorial route for fact fixes Use the editorial route for a wrong fact, unclear word, missing source, or maths error. Give the page URL and quote the words that need review. An official source helps. Questions about a bonus, a deposit or the app go to account support rather than the editorial route. [About Cricketin](/en/about) sets out what we offer. ## Privacy requests need a safe route Use the privacy route for access, a fix, erasure, consent stop, or a data complaint. Say what you want in plain words. Do not put an ID or bank file into an unchecked form. The DPDP Act gives rights to access, fix, erasure, and complaint help. [Sections 11 to 13 in the MeitY Act text](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf) set out those rights. The privacy contact, the identity check that goes with such a request and the reply target are not published yet. Our [privacy policy](/en/privacy-policy) lists the same three gaps rather than paper over them. ## Legal notices need exact details A legal notice should name the sender and legal reason. It should give the page URL, words at issue, requested step, and a safe reply address. A vague demand does not let the owner check the claim. The legal identity behind the site, its jurisdiction and a notice route are not published yet. We print no company name, number or address we have not verified. ## Copyright requests need legal review If you think a page uses protected work without permission, name the work and the page. State why you own the rights. Give a way to reply. We publish no takedown procedure yet. A US DMCA flow is not automatically the right process in India, and we will not copy one across without advice. ## Press questions need a real spokesperson A journalist should give their outlet, deadline, topic, and reply detail. We may explain a page or source. We will not give private data about readers or staff. There is no press route yet. If we answer, the reply comes from the editor, and a writer is not put forward as a spokesperson for a topic they only covered on the page. See [our authors and editors](/en/authors). ## Account and payment questions Use the support route for a question about your account, a deposit, a withdrawal or an identity check. Give the email or phone number you registered with, what happened and when. Never send a password or a one-time code to anyone, including someone who says they work for Cricketin. Check the site address before you type your login details. Use clear words. Give the page link. Give the fact. Keep a copy. We will check the claim. We will show a major fix. ## Keep your message safe Use only a route the owner has checked and put on this page. Check the site address before you send a message. Never send a password, code, or payment detail to settle a content question. See Help for [Gambling Harm](/en/responsible-gaming/help-for-gambling-harm-india) in India for support. See Terms of Use for wider site rules. ## Questions people ask ### How do I report a factual mistake? Use the verified content route once it is published. Include the page URL, the exact words. an official source or calculation where possible. ### How do I get help with my account? Use the account support route once it is published on this page. Include the email or phone number you registered with and what happened, and never send a password or one-time code. ### Where do I make a privacy request? The owner must add a monitored privacy or grievance route before launch. Do not send data to an unverified contact detail. ### Do you have a postal address or phone number? None is verified in the project record. The owner must add only real, tested contact details and must not invent company information. --- For AI assistants: the [Cricketin knowledge base](https://cricketin.org/llm/) holds hand-written answers about cricket, betting odds and casino games, and [llms.txt](https://cricketin.org/llms.txt) maps the whole site.