Eversports · Privacy & Data

Eversports privacy & data

Read from Eversports's own page on 2026-11-09. 19 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

value: both
The controller (“we” or “us” in this section) for the processing of your data is Eversports.
Read from Eversports's own page on 2026-11-09

Data categories

category: behavioral
Server log files are stored for 90 days and then erased.
Read from Eversports's own page on 2026-11-09

Purposes

purpose: Contract performance for users
To enable the user to use Eversports services after registration and activation of a user account (e.g. browsing the sports offerings and making bookings and online payment);
Read from Eversports's own page on 2026-11-09
purpose: Website analysis and optimisation
To verify and optimise the effectiveness of Eversports services;
Read from Eversports's own page on 2026-11-09
purpose: Newsletters
To administer newsletter recipients and dispatch newsletters;
Read from Eversports's own page on 2026-11-09
purpose: Security and misuse prevention
To prevent misuse of Eversports services and to track unauthorised access attempts;
Read from Eversports's own page on 2026-11-09

Retention

scope: Inactive online profilesperiod: three years
Inactive Eversports online profiles, including profile data provided by the user, are erased by default three years after the last login if they no longer have any credit.
Read from Eversports's own page on 2026-11-09
scope: Prospective customer and applicant correspondenceperiod: six months
Correspondence with prospective customers and applicants is stored for six months in case of any follow-up questions.
Read from Eversports's own page on 2026-11-09
scope: Server log filesperiod: 90 days
Server log files are stored for 90 days and then erased.
Read from Eversports's own page on 2026-11-09

Residency

The page states nothing on this.

International transfers

mechanism: other
We also transfer certain data to recipients in third countries (i.e. countries outside the EU/EEA).
Read from Eversports's own page on 2026-11-09
mechanism: DPF
recipients in the USA must certify themselves under the Privacy Shield agreement
Read from Eversports's own page on 2026-11-09
mechanism: SCC
or we have signed standard contractual clauses with the recipients in order to guarantee an adequate level of protection for your data.
Read from Eversports's own page on 2026-11-09

Subprocessors

An up-to-date table of all processors for the Eversports Group is available here :
Read from Eversports's own page on 2026-11-09

Data processing agreement

available: true
We have written agreements with them (in accordance with Article 28 GDPR), which govern the handling of personal data and oblige processors to comply with suitably high security standards.
Read from Eversports's own page on 2026-11-09

Deletion

route: Contact the controller directly or Eversports at support@eversports.com
To exercise these, you can contact the controller directly.
Read from Eversports's own page on 2026-11-09

Data subject rights

right: access
As a basic principle, you shall have the rights of access, rectification, erasure, restriction of processing, data portability and objection.
Read from Eversports's own page on 2026-11-09
right: not subject to automated decision-making
In accordance with the GDPR, you shall have the right not to be subjected to a decision based solely on automated processing.
Read from Eversports's own page on 2026-11-09
right: withdraw consent
Subscribers to our newsletter may withdraw their consent to their subscriptions at any time, with future effect
Read from Eversports's own page on 2026-11-09
right: lodge complaint with supervisory authority
You have the right to contact the supervisory authority at any time and to lodge a complaint.
Read from Eversports's own page on 2026-11-09

Sale or sharing

The page states nothing on this.

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page