DataSportsAPI provides live sports data across 24 sports, offering real-time scores, fixtures, lineups, statistics and standings via a simple JSON API and WebSocket streams. The platform supports football, tennis, basketball, ice hockey, esports, volleyball, handball, baseball, American football, rugby, cricket, MMA, table tennis, darts, snooker, futsal, badminton, water polo, cycling, motorsport and more, enabling developers to build live score apps, media integrations, fantasy platforms, AI data products, and website widgets.
DataSportsAPI publishes 15 API contracts indexed on the APIs.io network, including Catalog API, Discovery API, Exports API, and 12 more. Tagged areas include Sports, Live Data, Real-Time, and JSON.
The DataSportsAPI catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
DataSportsAPI’s developer surface includes sandbox, changelog, API reference, authentication, documentation, pricing, support, and 19 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/datasportsapi/"><img src="https://apis.io/badge/datasportsapi/card.svg" alt="DataSportsAPI on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Bulk exports. For the Business and Enterprise plans. Get a whole league season as files: create an export, poll its status, then download. Exports are generated in the backgroun...
Live scores. Fixtures that are in play right now. If you are building a live feature, the WebSocket is the better fit: it delivers the same objects and then pushes deltas.
Betting odds. Prices from a single bookmaker (bet365, supplied through our data source), both before kick-off and in play, available since 2026-11-04. Odds live exclusively on d...
Referees & managers. Fixture.referee carries referee ids; TeamDetail.manager and Fixture.homeManager / awayManager carry manager ids. Both kinds can also be found through /v2/se...
Race sports. Motorsport and cycling — the sports with kind races in /v2/sports. Here a series takes the place of a league (Formula 1, MotoGP; in cycling, the full men’s or women...
Tracking data. Positional data for a match, available since 2026-11-12 with history back to 2026-11-07. Football gets a live ball track and live events — goals, shots, cards, su...
WebSocket. Live deltas for scores and statuses. Obtain a single-use ticket via REST and then open the connection, so your API key never appears in a WebSocket URL. Offered on Bu...
aid: datasportsapi
name: DataSportsAPI
accessModel:
pricing: freemium
onboarding: self-serve
trial: false
try_now: true
public: false
gated: none
gated_source:
- onboarding
label: Freemium · Self-serve signup
confidence: medium
source:
- plans
- authentication
- security
generated: '2026-11-13'
method: derived
image: https://datasportsapi.com/opengraph-image?38edc71c77436faa
description: DataSportsAPI provides live sports data across 24 sports, offering real-time scores, fixtures, lineups, statistics
and standings via a simple JSON API and WebSocket streams. The platform supports football, tennis, basketball, ice hockey,
esports, volleyball, handball, baseball, American football, rugby, cricket, MMA, table tennis, darts, snooker, futsal, badminton,
water polo, cycling, motorsport and more, enabling developers to build live score apps, media integrations, fantasy platforms,
AI data products, and website widgets.
url: https://artifacts.apis.io/datasportsapi/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-12 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-12'
modified: '2026-11-12'
tags:
- Sports
- Live Data
- Real-Time
- JSON
tags_raw:
- Sports
- LiveData
- API
- RealTime
- JSON
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: AgenticAccess
url: agentic-access/datasportsapi-agentic-access.yml
- type: Plans
url: plans/datasportsapi-plans-pricing.yml
- type: Spectral
url: rules/datasportsapi-rules.yml
- type: JSONLD
url: json-ld/datasportsapi-context.jsonld
- type: Vocabulary
url: vocabulary/datasportsapi-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: Webhooks
url: asyncapi/datasportsapi-webhooks.yml
- type: DataModel
url: data-model/datasportsapi-data-model.yml
- type: ErrorCatalog
url: errors/datasportsapi-problem-types.yml
- type: Conformance
url: conformance/datasportsapi-conformance.yml
- type: LLMsTxt
url: llms/datasportsapi-llms.txt
- type: Hosts
url: hosts/datasportsapi-hosts.yml
- type: StatusPage
url: https://datasportsapi.com/status/
- type: Sandbox
url: https://datasportsapi.com/playground/
- type: SDKs
url: https://datasportsapi.com/sdks/
- type: Newsroom
url: https://datasportsapi.com/use-cases/media/
- type: Login
url: https://datasportsapi.com/login/
- type: ChangeLog
url: https://datasportsapi.com/changelog/
- type: DeveloperPortal
url: https://api.datasportsapi.com
- type: APIReference
url: https://datasportsapi.com/docs/reference/
- type: Authentication
url: authentication/datasportsapi-authentication.yml
- type: DomainSecurity
url: security/datasportsapi-domain-security.yml
- type: Website
url: https://datasportsapi.com
- type: Documentation
url: https://datasportsapi.com/docs
- type: Pricing
url: https://datasportsapi.com/pricing
- type: Support
url: https://datasportsapi.com/contact
apis:
- aid: datasportsapi:datasportsapi-catalog-api
name: DataSportsAPI Catalog API
description: Catalog
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Catalog
tags_raw:
- catalog
properties:
- type: OpenAPI
url: openapi/datasportsapi-catalog-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-discovery-api
name: DataSportsAPI Discovery API
description: 'Discovery. Starting points for finding ids: world rankings, plus the full set of a sport’s leagues by country
or by category.'
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Discovery
tags_raw:
- discovery
properties:
- type: OpenAPI
url: openapi/datasportsapi-discovery-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-exports-api
name: DataSportsAPI Exports API
description: 'Bulk exports. For the Business and Enterprise plans. Get a whole league season as files: create an export,
poll its status, then download. Exports are generated in the background from the same data the endpoints above serve;
each account may create up to 20 per UTC day, and each one is kept for 7 days. Business reads one year back, so a season
that ended before that window is refused (403 history_not_in_plan) on that plan.'
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Export
tags_raw:
- exports
properties:
- type: OpenAPI
url: openapi/datasportsapi-exports-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-fixtures-api
name: DataSportsAPI Fixtures API
description: Fixtures. Look up fixtures by date, or fetch one match together with its detail sub-resources.
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Fixtures
tags_raw:
- fixtures
properties:
- type: OpenAPI
url: openapi/datasportsapi-fixtures-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-leagues-api
name: DataSportsAPI Leagues API
description: Leagues
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- League
tags_raw:
- leagues
properties:
- type: OpenAPI
url: openapi/datasportsapi-leagues-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-livescores-api
name: DataSportsAPI Livescores API
description: 'Live scores. Fixtures that are in play right now. If you are building a live feature, the WebSocket is the
better fit: it delivers the same objects and then pushes deltas.'
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Live Scores
tags_raw:
- livescores
properties:
- type: OpenAPI
url: openapi/datasportsapi-livescores-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-odds-api
name: DataSportsAPI Odds API
description: 'Betting odds. Prices from a single bookmaker (bet365, supplied through our data source), both before kick-off
and in play, available since 2026-11-04. Odds live exclusively on dedicated endpoints and a dedicated WebSocket channel:
fixtures, lists and deltas never include betting fields, so your match data contains no odds unless you request them.
Included in the Pro, Business and Enterprise plans, with live prices on odds:{id} for Business and Enterprise accounts.
Odds are third-party prices provided for information only — neither betting advice nor an offer to place a bet; make sure
you follow the rules on displaying betting odds wherever your users are.'
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Odds
tags_raw:
- odds
properties:
- type: OpenAPI
url: openapi/datasportsapi-odds-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-people-api
name: DataSportsAPI People API
description: Referees & managers. Fixture.referee carries referee ids; TeamDetail.manager and Fixture.homeManager / awayManager
carry manager ids. Both kinds can also be found through /v2/search.
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- People
tags_raw:
- people
properties:
- type: OpenAPI
url: openapi/datasportsapi-people-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-players-api
name: DataSportsAPI Players API
description: Players
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Player
tags_raw:
- players
properties:
- type: OpenAPI
url: openapi/datasportsapi-players-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-races-api
name: DataSportsAPI Races API
description: Race sports. Motorsport and cycling — the sports with kind races in /v2/sports. Here a series takes the place
of a league (Formula 1, MotoGP; in cycling, the full men’s or women’s calendar). Each race is either a Grand Prix weekend
or one cycling race, split into sessions — the timed parts such as practice, qualifying, a sprint, the race itself or
a cycling stage. Drivers and riders, like their teams, are TeamRefs, which /v2/teams/{id} resolves. Times are always in
milliseconds and distances in metres. The WebSocket does not carry these sports yet; while a session runs, poll /v2/races/{id}
and its /results.
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Races
tags_raw:
- races
properties:
- type: OpenAPI
url: openapi/datasportsapi-races-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-search-api
name: DataSportsAPI Search API
description: Search
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Search
tags_raw:
- search
properties:
- type: OpenAPI
url: openapi/datasportsapi-search-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-teams-api
name: DataSportsAPI Teams API
description: Teams
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Team
tags_raw:
- teams
properties:
- type: OpenAPI
url: openapi/datasportsapi-teams-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-tracking-api
name: DataSportsAPI Tracking API
description: 'Tracking data. Positional data for a match, available since 2026-11-12 with history back to 2026-11-07. Football
gets a live ball track and live events — goals, shots, cards, substitutions and set pieces seconds after they happen,
plus the flow of play (ball safe, attack, dangerous attack, change of possession) — and, after the match, the full event
list with positions and passes. Tennis gets every serve and point plus live positions of the ball and the players, basketball
its post-match events and shot spots, ice hockey a match timeline. Enterprise plan only: the REST endpoints are below,
and the tracking:{id} WebSocket channel streams the same data live. Every position is in the fixture’s coordinate frame
(TrackingSummary.coordinates) — 0–100 for football, basketball and ice hockey, with the home side attacking towards x
= 100 for the whole match, and millimetres from the middle of the net for tennis. Players are identified by name from
the match squad, without an id.'
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Tracking
tags_raw:
- tracking
properties:
- type: OpenAPI
url: openapi/datasportsapi-tracking-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-venues-api
name: DataSportsAPI Venues API
description: Venues. Venue ids appear on Fixture.venue and TeamDetail.venue, and /v2/search can look venues up too.
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- Venues
tags_raw:
- venues
properties:
- type: OpenAPI
url: openapi/datasportsapi-venues-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
- aid: datasportsapi:datasportsapi-websocket-api
name: DataSportsAPI WebSocket API
description: WebSocket. Live deltas for scores and statuses. Obtain a single-use ticket via REST and then open the connection,
so your API key never appears in a WebSocket URL. Offered on Business (three simultaneous connections per account) and
Enterprise (five), with the tracking:{id} channel kept for Enterprise.
humanURL: https://datasportsapi.com/docs
baseURL: https://api.datasportsapi.com
tags:
- WebSocket
tags_raw:
- websocket
properties:
- type: OpenAPI
url: openapi/datasportsapi-websocket-api-openapi.yml
- type: JSONSchema
url: json-schema/datasportsapi-player-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fixture-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-fighter-career-statistics-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-incident-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-tracked-event-schema.json
- type: JSONSchema
url: json-schema/datasportsapi-race-result-schema.json
x-submission-notes: 'Sports data API, pre-launch: OpenAPI 3.1 (1.6MB) live, api.datasportsapi.com not resolving yet -- profile
from the published spec; Kin approved queueing 2026-11-12'
x-submission-probe: site/docs/OpenAPI 200, invented 404, API host unresolved
x-enrichment:
date: '2026-11-12'
status: enriched
artifacts_added: 29
pass: modular-v1
engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local
DataSportsAPI — frequently asked questions
Does DataSportsAPI have an API?
Yes. APIs.io lists 15 APIs from DataSportsAPI, including DataSportsAPI Catalog API, DataSportsAPI Discovery API and DataSportsAPI Exports API, and 12 more.
Is there an OpenAPI specification for the DataSportsAPI?
Yes. APIs.io indexes 15 OpenAPI specifications for DataSportsAPI, each linked for download from this page.
How do I authenticate with the DataSportsAPI?
DataSportsAPI uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as DataSportsAPI Authentication.
How much does the DataSportsAPI cost?
DataSportsAPI publishes its prices; its Free plan is $0/ mo as of 2026-11-12. APIs.io lists 5 pricing plans for DataSportsAPI, with each plan's price, limits and inclusions under Pricing on this page.
Is the DataSportsAPI ready for AI agents?
DataSportsAPI has a Kin Score of 51.7 out of 100 (developing) and an Agent Readiness score of 33.5 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.