This document describes the terms and conditions governing the use of the Footbar API, covering both developer policy and terms of sale. It provides a comprehensive framework for developers and companies wishing to integrate the Footbar API into their projects. By accessing or using the Footbar API, you agree to abide by the guidelines and provisions set out in this document.

Principles 

At Footbar, we are firmly committed to the principles that guide developers in creating applications that not only harness the power of the Footbar API, but also respect the rights and privacy of users. These principles serve as the basis for responsible and ethical development:

1. Respect for user data ownership: Respecting the philosophy of the General Data Protection Regulation (GDPR), we recognize that player data belongs to the player. We insist that the collection or storage of data must never take place without the clear and explicit consent of the user, ensuring transparency in the use of their data.
2. Privacy Policy: Footbar user data must never be used for prohibited purposes, including the sale or use of data for advertising purposes. Developers must give priority to protecting the privacy of users and refrain from any action that might compromise this fundamental right.
3. Transparency and clarity: We stress the importance of accurate and complete communication with players. Developers must provide clear explanations of what data is collected, for what purpose and for what purpose. Transparent communication helps cultivate trust between developers and users.
4. Data control offered to the user: In line with users' rights, developers are obliged to honor users' requests for data deletion. Respecting users' wishes reinforces the idea that control of data is ultimately in the hands of those it concerns.
5. Data security : The secure handling of user data is non-negotiable. Developers are required to implement robust security practices that guarantee the integrity and confidentiality of user data. Demonstrating compliance with these security measures is essential to building user confidence.
6. Minimum and relevant authorizations: Developers should only request the data access authorizations needed to realize the main functionalities of their applications or services. This approach limits data exposure and fosters a sense of trust by minimizing unnecessary data manipulation.

These principles underscore our shared commitment to creating applications that not only leverage the capabilities of the Footbar API, but also align with ethical data practices and prioritize user privacy. By adhering to these principles, developers can create experiences that empower users while maintaining the highest standards of responsibility and respect.

Access and use policies 

The entire Footbar ecosystem is governed by this policy as well as by the conditions générales de ventethe privacy policy and the legal information of the Footbar online store, as well as the privacy policy of our mobile application. By using the Footbar API, you acknowledge and agree to adhere to the provisions set forth in this policy, as well as the associated policies and legal documents referenced above.

In addition, as a user of the Footbar API, you are responsible for complying with all laws and regulations applicable to your use of the API and its associated services. It is your responsibility to keep yourself informed of all legal requirements relating to your use and to ensure that you comply with these terms at all times. If, for any reason, you find yourself unable to comply with these conditions, it is imperative that you cease 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 found to violate applicable law. Regular monitoring of your compliance with these terms is essential to maintaining a productive and compliant relationship with the Footbar API.

Appropriate use of the Footbar API  

The Footbar API is designed to enable developers to create applications that enhance the soccer player's experience while respecting the values and objectives of the Footbar ecosystem. Applications created using the Footbar API must align with one of the following objectives: 

• Rewarding soccer practice: Apps can enable soccer players to receive well-deserved rewards for their dedication and performance on the pitch.
• Community interaction: Apps can make it easier for soccer players to share their achievements and progress with the wider community, fostering a sense of camaraderie.
• Performance enhancement: Applications can provide soccer players with tools to track, measure and improve their performance over time, contributing to their personal development.
• Performance analysis and challenges: Applications can offer features that enable soccer players to analyze their performance data, set themselves challenges and take part in friendly competitions to boost their motivation and skills.
• Game integration: Applications can integrate game elements inspired by soccer training, offering players an entertaining and immersive experience based on their athletic endeavors.

It is important to note that any use case outside the objectives specified above requires explicit approval from the Footbar team. If you have a unique use case in mind that deviates from the predefined objectives, you must request approval by contacting us by e-mail at [email protected]. We encourage innovation and creativity, while ensuring that applications created using the Footbar API remain in line with our values and objectives.

By adhering to these guidelines, developers contribute to an ecosystem that not only leverages the capabilities of the Footbar API, but also respects the integrity of its intent. Together, we can create applications that celebrate the game of soccer 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, anonymized, de-identified or derived from raw data, are subject to the following constraints to ensure responsible data management:

• Your use of user data must be limited to providing or enhancing 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 enhance your appropriate use case or user-oriented features, clearly discernible in the user interface of the requesting application, and only with the user's consent.
• For safety reasons, e.g. to investigate abuse.
• To comply with applicable laws and/or regulations.
• In the context of a merger, acquisition or sale of the developer's assets, provided that the prior explicit consent of the user 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 facilitate password recovery).
• Data (including derived data) is aggregated and anonymized and is used for internal operations in compliance with applicable legal requirements regarding confidentiality and jurisdiction.
• It is essential for security purposes, such as abuse investigations.
• 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, the transfer or sale of user data to third parties:

• The transfer or sale of user data to third parties such as advertising platforms, data brokers or information resellers, even when aggregated or anonymized.
• The transfer, sale or use of user data for advertising purposes, including personalized or interest-based advertising.
• Use user data to determine creditworthiness or for lending purposes.
• The use of user data in connection with products or services that may be considered as medical devices.
• The use of user data for purposes involving protected health information.
• Use user data for player recruitment activities.
• Participate in activities linked to the trafficking of soccer players.

Access to Footbar user data may not be used in violation of this Policy or other applicable Footbar terms or policies, including the following:

• Create applications designed for sports other than soccer, or encourage unconventional use of the Meteor tracker contrary to Footbar's recommendations.
• The use of Footbar's APIs for applications, services or functionalities designed to collect or merge user data for research involving human subjects, medical research or other similar activities.

In addition, your application must follow the design guidelines and graphic guidelines provided by Footbar, and display the phrase "stats provided by Footbar" in a prominent place.

Finally, it is important to note that use of the API does not grant permission to exploit the Footbar trademark or logo, to become a reseller of Footbar products, or to engage in any activity that may infringe Footbar's intellectual property rights.

Transparency and user control 

Since the Footbar API handles soccer-related data, which includes personal and sensitive information, it is imperative that all applications and services include a comprehensive privacy policy. This policy must explain precisely 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 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 the user's data in the appropriate context. This approach facilitates the user's understanding of the data to be provided, the justification for the data request and the intended use of the data. In accordance with applicable laws, the following conditions must be met:

• An obligation to disclose: Your data access, collection, use and sharing practices must be disclosed in a way that :
• Precisely identify the application or service requesting access to user data.
• Reside in the application itself for application-based interactions, or in a separate dialog window for web-based interactions.
• Present the disclosure transparently during normal use of the application or website, without forcing users to navigate through menus or settings.
• Provide clear, precise information delimiting the categories of data accessed, requested and/or collected.
• Explain the means by which data will be used and/or shared. If data is requested for one purpose, but is also intended for a secondary use, both use cases must be communicated to users.
• Remain distinct from unrelated information and cannot be relegated solely to privacy policies or terms of service.

• Request for consent: Disclosure must accompany and immediately precede a request for consent from the user. The request for consent must :
• Present the consent dialogue in a lucid and unequivocal manner.
• Impose a positive action on the user (e.g. press to accept, tick a box, verbally confirm) to obtain consent.
• Avoid interpreting as consent actions such as navigating away from the disclosure (e.g. typing elsewhere, using the "back" or "home" button).
• Refrain from using automatic deletion or expiration messages as a consent mechanism.

• User support documentation: It is your responsibility to provide user-friendly documentation describing the procedures for users to manage and delete their data from your application.

These measures strengthen transparency and control over user data, fostering an environment of trust and responsibility between developers and users. By adhering to these guidelines, developers play an essential role in creating a safe and respectful digital landscape.

Secure data management 

The sanctity of user data is of paramount importance to us. That's 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 from unauthorized access, misuse, destruction, loss, alteration or disclosure.

Recommended and mandatory security practices to enhance data protection are described below:

Recommended safety practices :

• Information Security Management System (ISMS): developers are encouraged to adopt and maintain an information security management system compliant 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, enhances data integrity and protection against potential threats.

Required safety measures :

• Encryption standards: Use an industry-recognized encryption standard to encrypt user data in the following cases:
• Data stored on portable devices or portable electronic media.
• Data stored outside of Footbar's or your systems.
• Data transmitted over external networks not under the exclusive control of your administration.
• Data at rest on your systems.
• Secure data transmission: Use contemporary secure protocols (e.g. HTTPS) when transmitting data to ensure data integrity in transit.

• Encryption of credentials: Ensure that user credentials and data, especially tokens such as OAuth access and refresh tokens, are encrypted when at rest.
• Key management: Manage keys and key material judiciously, possibly by storing them in a hardware security module or in a key management system of equivalent robustness.

In addition, developers are required to promptly notify Footbar at [email protected] of any known or suspected unauthorized access to systems, networks, accounts or other locations where Footbar user data is stored, a so-called "security breach". Developers must also cooperate fully with Footbar to rectify any confirmed or suspected security breach. In such cases, developers are expected to communicate with Footbar before making any public statement regarding the flaw.

By adhering to these secure data management practices, developers play a crucial role in preserving user trust and maintaining the sanctity of data within the Footbar ecosystem.

Flexible access and blocking

At Footbar, we understand that every developer's needs are unique. To address this diversity, the Footbar API features a two-tiered access approach designed to meet the preferences of both free and paying members. This approach combines flexibility and value for money, ensuring an efficient experience for 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 includes predefined limitation limits that ensure a fair distribution of resources between users. These limits help to maintain a high level of service quality while avoiding abuse.

For developers with ambitious projects or larger user bases, our paid membership option offers extended access and more extensive limitations. By subscribing to this option, developers unlock increased API usage capabilities, facilitating more frequent and comprehensive API requests.