OpenCricket API logo
OpenCricketAPI
[Docs][MCP][Coverage][Play][Pricing][Blog][Sign in]
English
Englishहिन्दीবাংলাاردوதமிழ்EspañolPortuguês (Brasil)
Get a free key
Legal

Privacy Policy

This policy explains what personal data we process when you use our website, API, MCP server, dashboard, checkout and support channels.

Effective and last updated: 19 October 2026

PrivacyTermsRefunds

1. Who we are

OpenCricketAPI is the controller for the personal data in this policy, except where a provider acts as an independent controller. Send questions and privacy requests to opencricket@proton.me.

2. Data we collect

  • Account: your email address, your plan and the date you signed up. We have no passwords. To sign in, we email you a one-time link. We store your email address and a hash of the link's code. The link expires after 15 minutes. If you sign in with GitHub or Google instead, they tell us your verified email address and your account's permanent ID there; we keep the ID, and how the connection was confirmed, so that account keeps signing in to the same OpenCricket account. We keep nothing else from them, not even their access token. Each time you sign in, we record when and how (email link, GitHub or Google) and the country Cloudflare places your connection in (a two-letter code, not your IP address), so we can see whether people come back and help with sign-in problems. Your account also keeps the country it was last used from, by sign-in or API request.
  • API keys: a secure hash of each key, its first characters, the name you give it, and when it was created and last used. We cannot recover a key from what we store.
  • API and MCP usage: for each key, the number of requests and errors per endpoint per day, and the number of requests per month for each key and account. We also keep daily successful and failed API response counts per account, including plan and quota refusals for recognised active keys, and the first and latest successful request times. Dashboard key tests count as API requests. We record the endpoint pattern only (for example /v1/matches/{id}). Usage records contain no query parameters, request contents or IP addresses. We use them for quotas, your dashboard, abuse prevention and understanding whether new users get started and return.
  • Payments: Dodo Payments is our Merchant of Record and processes your card. We never receive your full card number. We store your Dodo customer and subscription IDs, your plan, the subscription status and its renewal or cancellation dates. We also store a copy of each event Dodo sends us. It can contain your name, email address, phone number, billing address, tax ID and business name. Payment events also contain the cardholder name, card brand, card type, issuing country and the last four digits of the card.
  • Waitlist: if you join the waitlist, we store your email address, the time, the page you joined from, the referring website and your country (from Cloudflare). We use it only to send your API key and launch news.
  • Cookieless analytics: for each page view, the page path without query parameters, the referring website, the campaign source, your country, your device type and a visitor ID. The visitor ID is a hash of your IP address, your browser, the date and a secret value. We cannot recover your IP address from it, and it changes every day, so we cannot follow you from one day to the next.
  • Optional analytics: only if you click Accept on the cookie banner, Microsoft Clarity records how you use the site. Microsoft Clarity records page views, clicks, scrolling and mouse movement, and makes session recordings and heatmaps. Numbers and email addresses are masked, text you type is always masked, and your signed-in dashboard is masked completely.
  • Abuse limits: to limit sign-in emails, failed admin sign-ins, waitlist sign-ups and analytics events, we count attempts per hour (or shorter) for an email address, an IP address or the whole site. Each counter stores only a hash of the address made with a secret value, the time window and the number of attempts; it does not contain the address itself.
  • Technical and security data: Cloudflare processes IP addresses and request details to host and protect the service. Our error logs, kept by Cloudflare for a short time, can contain the request path and error details.
  • Support: the emails you send us and our replies.

3. Why we use personal data

We use personal data to provide accounts, API and MCP access, subscriptions and support; to secure the service and prevent fraud and abuse; to find and fix failures; to understand which pages help developers; to send service emails; and to meet legal, tax and accounting duties.

Our legal bases are the performance of our contract with you, our legitimate interest in running and protecting the service, legal obligations, and your consent for optional analytics. You can withdraw consent at any time. This does not affect processing that happened before.

4. Providers

We share only the data each provider needs:

  • Cloudflare hosts the site and API, stores our database (Cloudflare D1) and protects the network.
  • Resend sends our sign-in emails.
  • GitHub and Google, if you choose to sign in with them, confirm your email address.
  • Dodo Payments, our Merchant of Record, handles payments, tax, invoices, fraud checks, refunds and chargebacks. Dodo is an independent controller for these activities.
  • Microsoft Clarity provides optional website analytics, only after you accept.

Live scores and fixtures come from ESPN. Our server fetches them; your browser does not contact ESPN, and we send ESPN no data about you.

We may also disclose data when the law requires it, to protect users or the service, or in a business reorganisation with appropriate safeguards. We do not sell personal data.

5. Cookies and storage on your device

  • oc_session: keeps you signed in for 30 days. It is needed for the service to work.
  • oc_oauth: set for up to 10 minutes while you sign in with GitHub or Google, to check that the reply belongs to your sign-in. It is needed for that sign-in to work.
  • oc_signed_in: set with oc_session and removed with it, so the site header can show Dashboard instead of Sign in. It holds only the value 1, not a credential, and the server never uses it to let anyone in.
  • Browser storage: your cookie choice and your light or dark theme. This stays on your device.
  • Microsoft Clarity, after you accept: the cookies _clck and _clsk connect your page views into sessions. Microsoft can also set its own cookies on its domains.

To change your choice, use Cookie settings at the bottom of any page. If you reject, the optional analytics stop and their cookies are removed.

6. How long we keep data

  • Sign-in link records: 24 hours.
  • Records of when and how you signed in: 90 days.
  • Abuse-limit counters: 24 hours.
  • Cookieless analytics: 90 days.
  • Daily usage records: 13 months.
  • Account, API key, monthly usage, subscription and payment event records: while your account exists, and afterwards only as long as needed for security, disputes, legal duties or accounting. Account records include first and latest successful API request times and the first time we observed paid access, used to measure onboarding. These milestones are deleted with your account; daily response counts follow the daily usage retention period. Dodo Payments keeps its own payment records under its own legal duties.
  • Waitlist entries: until you ask us to delete them, or until we no longer need them for the launch.
  • Support emails: as long as needed to help you and keep a record of the request.

To delete your account, use Delete account on your dashboard. It deletes your account, API keys, usage records, sign-in links, sign-in records and GitHub or Google connections at once, and stops any subscription from renewing. Subscription and payment records are kept as described above. You can also email opencricket@proton.me from the address on your account.

7. International transfers

Our providers can process data outside your country. Where the law requires it, these transfers rely on an adequacy decision, standard contractual clauses or another lawful safeguard. Contact us for details.

8. Your rights

Depending on where you live, you can ask to see, correct, delete or export your data, to restrict its use, or to object to it. You can withdraw consent at any time. You can also complain to your local data protection authority.

Send requests from the email address on your account to opencricket@proton.me. We may ask for information to confirm your identity, and we reply within the time the law requires.

9. Security, children and changes

We protect data with reasonable technical and organisational measures, but no internet service is completely secure. Keep your API keys private, and tell us at once if you think one was misused.

The service is for developers and businesses. It is not for children under 16. Only adults or authorised business representatives may buy a plan.

We may update this policy when the service or the law changes. A changed policy shows a new date at the top, and we give extra notice of important changes.

OpenCricket API logo
OpenCricketAPI

Open ball-by-ball cricket data and match intelligence, engineered for developers and AI agents.

Cloudflare Edge · Ball-by-ball since 2001 · Open data provenance
Platform
DocumentationMCPPlayCoverage Explorer
Developers
Pricing & QuotasOpenAPI 3.1 SpecLLMs.txt GuideAPI Changelog
Resources
Engineering BlogCompare Cricket APIsCricket GlossaryFree Cricket ToolsData: Cricsheetopencricket@proton.me
Legal
Privacy PolicyTerms of ServiceRefunds
© 2026 OpenCricketAPI. Match data from Cricsheet (ODC-By 1.0) and ESPN.Zero synthetic data · Verified sports data provenance