This document sets out the terms and conditions governing the use of the Footbar API, covering both the developer policy and the terms of sale. It provides a complete framework for developers and businesses wishing to integrate the Footbar API into their projects. By accessing or using the Footbar API, you agree to comply with the guidelines and provisions set out in this document.
Principles
At Footbar, we are firmly committed to upholding the principles that guide developers in building applications that not only harness the power of the Footbar API but also respect the rights and privacy of users. These principles are the foundation of responsible, ethical development:
- Respect for user data ownership: In keeping with the philosophy of the General Data Protection Regulation (GDPR), we recognise that a player's data belongs to the player. We stress that data must never be collected or stored without the user's clear and explicit consent, which ensures transparency about how their data is used.
- Privacy protection: Footbar user data must never be used for prohibited purposes, including selling it or using it for advertising. Developers must prioritise the protection of users' privacy and refrain from any action that could undermine this fundamental right.
- Transparency and clarity: We stress the importance of accurate and complete communication with players. Developers must provide clear explanations of the data collected, the purpose of the collection and the intended use. Transparent communication helps build trust between developers and users.
- User control over data: In line with users' rights, developers are required to honour requests to delete user data. Respecting users' wishes reinforces the idea that control over data ultimately rests in the hands of the people it concerns.
- Data security: Handling user data securely is non-negotiable. Developers are required to implement strong security practices that guarantee the integrity and confidentiality of user data. Demonstrating compliance with these security measures is essential to strengthening user trust.
- Minimal and relevant permissions: Developers must only request the data access permissions needed to deliver the core features of their applications or services. This approach limits data exposure and fosters a sense of trust by minimising unnecessary data handling.
These principles underline our shared commitment to creating applications that not only harness the capabilities of the Footbar API, but also align with ethical data practices and prioritise the protection of users' privacy. By adhering to these principles, developers can create experiences that empower users while upholding the highest standards of responsibility and respect.
Access and usage policies
The entire Footbar ecosystem is governed by this policy as well as by the Terms and conditions of sale, the privacy policy and the legal notice of the Footbar online shop, as well as the privacy policy of our mobile app. By using the Footbar API, you acknowledge and agree to abide by the provisions set out in this policy, as well as the related policies and legal documents mentioned above.
In addition, as a user of the Footbar API, you are required to comply with all laws and regulations applicable to your use of the API and its associated services. It is your responsibility to stay informed of all legal requirements relating to your use and to ensure ongoing compliance with these terms. If, for any reason, you are unable to comply with these terms, you must stop using our services immediately.
We reserve the right to suspend and/or terminate your access to the Footbar API and its services if you fail to comply with this policy or if your actions are deemed to be contrary to applicable laws. It is essential to check regularly that you are complying with these terms in order to maintain a productive and compliant relationship with the Footbar API.
Appropriate use of the Footbar API
The Footbar API is designed to enable developers to build applications that enhance the football player's experience while respecting the values and objectives of the Footbar ecosystem. Applications built using the Footbar API must align with one of the following objectives:
- Rewarding football play: Applications can let football players receive well-deserved rewards for their dedication and performance on the pitch.
- Interacting with a community: Applications can make it easier to share football players' achievements and progress with the wider community, fostering a sense of camaraderie.
- Improving performance: Applications can give football players tools to track, measure and improve their performance over time, contributing to their personal development.
- Performance analysis and challenges: Applications can offer features that let football players analyse their performance data, set themselves challenges and take part in friendly competitions to boost their motivation and skills.
- Gamification: Applications can incorporate game elements inspired by football training, giving players an entertaining and immersive experience based on their athletic efforts.
Please note that any use case outside the objectives specified above requires explicit validation from the Footbar team. If you have a unique use case in mind that departs from the predefined objectives, you must request approval by contacting us by email at contact@footbar.com. We encourage innovation and creativity while making sure that applications built using the Footbar API remain consistent with our values and objectives.
By adhering to these guidelines, developers contribute to an ecosystem that not only harnesses the capabilities of the Footbar API, but also respects the integrity of its intent. Together, we can create applications that celebrate the practice of football while bringing value and enjoyment to players around the world.
Limited use of user data
Data collected through the Footbar API, as well as any data aggregated, anonymised, de-identified or derived from the raw data, is subject to the following restrictions to ensure responsible data management:
- Your use of user data must be limited to providing or improving your appropriate use case or features that are readily visible and prominent in the user interface of the requesting application.
- Data transfers are only permitted in specific circumstances:
- To provide or improve your appropriate use case or user-facing features, clearly discernible in the user interface of the requesting application, and only with the user's consent.
- For security purposes, for example to investigate abuse.
- To comply with applicable laws and/or regulations.
- As part of a merger, acquisition or sale of the developer's assets, provided that the user's explicit prior consent is obtained.
- Human access to user data must be limited, unless:
- The user's explicit consent has been obtained to access specific data (for example, to help with password recovery).
- The data (including derived data) is aggregated and anonymised and is used for internal operations in compliance with applicable privacy and jurisdictional legal requirements.
- It is essential for security purposes, such as investigating abuse.
- Compliance with applicable laws and/or regulations is required.
All other transfers, uses or sales of user data are strictly prohibited, including, but not limited to, transferring or selling user data to third parties:
- Transferring or selling user data to third parties such as advertising platforms, data brokers or information resellers, even when aggregated or anonymised.
- Transferring, selling or using user data for advertising purposes, including personalised or interest-based advertising.
- Using user data to determine creditworthiness or for lending purposes.
- Using user data in connection with products or services that may be considered medical devices.
- Using user data for purposes involving protected health information.
- Using user data for activities related to player recruitment.
- Engaging in activities related to football player trafficking.
Access to Footbar user data may not be exploited in violation of this Policy or other applicable Footbar terms or policies, including the following:
- Creating applications designed for sports other than football, or encouraging unconventional use of the Footbar Tracker that goes against Footbar's recommendations.
- Using Footbar's APIs for applications, services or features intended to collect or merge user data for research involving human subjects, medical research or other similar activities.
In addition, your application must comply with the design guidelines and brand guidelines provided by Footbar and display the phrase "stats powered by Footbar" in a clearly visible place.
Finally, please note that use of the API does not give you permission to exploit the Footbar brand or logo, to become a reseller of Footbar products, or to engage in any activity that could infringe Footbar's intellectual property rights.
User transparency and control
Because the Footbar API handles data relating to the practice of football, which includes personal and sensitive information, it is essential that all applications and services include a comprehensive privacy policy. This policy must accurately explain how your application or service collects, uses and shares user data. This means detailing the specific entities with which user data is shared, the purpose of the data use, data storage procedures, security measures, and the protocol in place when an account is deactivated or deleted.
In addition, applications and services must request access to user data in the appropriate context. This approach helps users understand what data they are being asked to provide, why it is being requested and how it will be used. In accordance with applicable laws, the following conditions must be met:
- A disclosure requirement: Your practices for accessing, collecting, using and sharing data must be disclosed in a way that:
- Accurately identifies the application or service requesting access to user data.
- Resides within the application itself for app-based interactions, or in a separate dialogue window for web-based interactions.
- Presents the disclosure transparently during normal use of the application or website, without requiring users to navigate through menus or settings.
- Provides clear and accurate information setting out the categories of data being accessed, requested and/or collected.
- Explains the ways in which the data will be used and/or shared. If data is requested for one purpose but is also intended for secondary use, both use cases must be communicated to users.
- Remains distinct from unrelated information and cannot be relegated solely to privacy policies or terms of service.
- Consent request: The disclosure must accompany and immediately precede a request for user consent. The consent request must:
- Present the consent dialogue in a clear and unambiguous way.
- Require a positive action from the user (for example, tapping to accept, ticking a box, confirming verbally) for consent to be granted.
- Avoid treating actions such as navigating away from the disclosure (for example, tapping elsewhere, or using the "back" or "home" button) as consent.
- Refrain from using auto-dismissing or expiring messages as a consent mechanism.
- User help documentation: It is your responsibility to provide user-friendly documentation describing the procedures that let users manage and delete their data from your application.
These measures strengthen transparency and user control over data, fostering an environment of trust and accountability between developers and users. By adhering to these guidelines, developers play an essential role in creating a safe and respectful digital landscape.
Secure data handling
The sanctity of user data is of paramount importance to us. That is why we require strict measures to ensure that all Footbar user data remains secure both in transit and at rest. Developers must take reasonable and appropriate precautions to protect applications or systems that use Footbar user data against unauthorised access, misuse, destruction, loss, alteration or disclosure.
The recommended and mandatory security practices for strengthening data protection are described below:
Recommended security practices:
- Information Security Management System (ISMS): developers are encouraged to adopt and maintain an information security management system that complies with standards such as ISO/IEC 27001. This framework establishes a comprehensive approach to protecting information assets.
- Robust application architecture: Implementing a robust application or web service structure, free from the common security vulnerabilities listed in the OWASP Top 10, strengthens data integrity and protection against potential threats.
Required security measures:
- Encryption standards: Use an industry-recognised encryption standard to encrypt user data in the following cases:
- Data stored on portable devices or portable electronic media.
- Data held outside Footbar's systems or your own.
- Data transmitted over external networks not under your exclusive administration.
- Data at rest on your systems.
- Secure data transmission: Use modern secure protocols (for example, HTTPS) when transmitting data to ensure data integrity in transit.
- Credential encryption: Make sure that user data and credentials, in particular tokens such as OAuth access and refresh tokens, are encrypted when at rest.
- Key management: Manage keys and key material prudently, ideally by storing them in a hardware security module or a key management system of equivalent strength.
In addition, developers are required to promptly notify Footbar, at contact@footbar.com, of any known or suspected unauthorised access to systems, networks, accounts or other places where Footbar user data is stored, known as a "security breach". Developers must also cooperate fully with Footbar to remedy any confirmed or suspected security breach. In such cases, developers are expected to communicate with Footbar before making any public statement about the breach.
By adhering to these secure data handling practices, developers play a crucial role in preserving user trust and upholding the sanctity of data within the Footbar ecosystem.
Access and throttling flexibility
At Footbar, we understand that every developer's needs are unique. To cater for this diversity, the Footbar API offers a two-tier access approach designed to suit the preferences of free and paid members. This approach combines flexibility and resource optimisation, ensuring an efficient experience tailored to all users. In addition, detailed information on throttling values and pricing can be found in the API specifications.
For those exploring the capabilities of the Footbar API or looking to integrate it into smaller-scale projects, our free version is an ideal starting point. This version comes with predefined throttling limits that guarantee a fair distribution of resources among users. These limits help maintain a high level of service quality while preventing abuse.
For developers with ambitious projects or larger user bases, our paid membership option offers extended access and higher limits. By subscribing to this option, developers unlock increased API usage capabilities, enabling more frequent and more comprehensive API requests.






