This document describes the terms and conditions that govern the use of the Footbar API, covering both the developer policy and the terms of sale. It provides a comprehensive framework for developers and businesses looking 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 forth herein.

Principles

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

1. Respecting Ownership of User Data: 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 should never be done without the clear and explicit consent of the user, which guarantees transparency in the use of their data.
2. Privacy Protection: Footbar user data should never be used for prohibited purposes, including the sale or use of data for advertising purposes. Developers must prioritize the protection of user privacy and refrain from any actions that could compromise this fundamental right.
3. Transparency and clarity: We emphasize the importance of precise and complete communication with players. Developers must provide clear explanations of the data collected, the purpose of collection, and intended use. Transparent communication helps cultivate trust between developers and users.
4. Data Control Offered to User: In accordance with user rights, developers are required to honor requests to delete user data. Respecting user wishes reinforces the idea that control of data is ultimately in the hands of those it affects.
5. Data security: The secure processing of user data is non-negotiable. Developers are required to implement strong security practices that ensure the integrity and confidentiality of user data. Demonstrating compliance with these security measures is essential to building user confidence.
6. Minimum and Relevant Permissions: Developers should only request data access permissions necessary to achieve the core functionality of their apps or services. This approach limits data exposure and promotes a sense of trust by minimizing unnecessary data manipulation.

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

Access and Use Policies

The entire Footbar ecosystem is governed by this policy as well as the general conditions of sale , the privacy policy and the legal notices 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.

Additionally, 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 informed of all legal requirements relating to your use and to ensure continued compliance with these terms. If, for any reason, you find yourself unable to comply with these terms, it is imperative that you immediately stop using our services.

We reserve the right to suspend and/or terminate your access to the Footbar API and its services if you violate this policy or if your actions are deemed to violate applicable laws. It is essential to regularly monitor your compliance with these Terms in order to maintain a productive and compliant relationship with the Footbar API.

Proper use of the Footbar API

The Footbar API is designed to enable developers to create applications that enhance the soccer player experience while respecting the values ​​and goals of the Footbar ecosystem. Apps built using the Footbar API must align with one of the following goals:

• Rewarding soccer practice: Apps can enable soccer players to receive well-deserved rewards for their dedication and performance on the field.
• Interaction with a community: Apps can make it easier to share the achievements and progress of soccer players with the broader community, fostering a sense of camaraderie.
• Performance Improvement: Apps can provide football players with tools to track, measure and improve their performance over time, thereby contributing to their personal development.
• Performance Analysis and Challenges: Applications may provide functionality that allows soccer players to analyze their performance data, set challenges, and participate in friendly competitions to enhance their motivation and skills.
• In-Game Integration: Apps can integrate game elements inspired by soccer training, providing players with an entertaining and immersive experience based on their athletic efforts.

It is important to note that any use cases outside of the purposes specified above require explicit validation from the Footbar team. If you have a unique use case in mind that deviates from the predefined goals, you should request approval by contacting us by email at contact@footbar.com. We encourage innovation and creativity while ensuring that applications built using the Footbar API remain aligned with our values ​​and goals.

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 apps that celebrate the game of football while providing value and enjoyment to players around the world.

Limited use of user data

Data collected through the Footbar API, as well as any data that is aggregated, anonymized, de-identified or derived from raw data, is subject to the following constraints to ensure responsible data management:

• Your use of User Data shall be limited to providing or enhancing your appropriate use case or functionality that is 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 functionality, clearly discernible in the user interface of the requesting application, and only with the user's consent.
• For security reasons, for example to investigate abuse.
• To comply with applicable laws and/or regulations.
• In the context of a merger, acquisition or sale of assets of the developer, provided that the prior explicit consent of the user is obtained.

• Human access to user data should be limited unless
• Explicit user consent was obtained to access specific data (e.g. 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 privacy 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 medical devices.
• Use of user data for purposes involving protected health information.
• Use user data for activities related to player recruitment.
• Participate in activities related to the trafficking of football players.

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

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

Additionally, your app must follow the design guidelines and style guide provided by Footbar and display the phrase "stats provided by Footbar" in a prominent location.

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

Transparency and user control 

As the Footbar API processes football playing data, which includes personal and sensitive information, it is imperative that all applications and services include a comprehensive privacy policy. This policy should accurately explain how your app or service collects, uses, and shares user data. This involves detailing the specific entities with which user data is shared, the purpose of using the data, the data storage procedures, security measures, and the protocol put in place when an account is deactivated or deleted.

Additionally, applications and services must request access to user data in the appropriate context. This approach makes it easier for the user to understand the data to be provided, the rationale for the data request, and the intended use of the data. In accordance with applicable laws, the following conditions must be respected:

• An obligation to disclose: Your practices regarding access, collection, use and sharing of data must be disclosed in order to:
• Precisely identify the application or service that requests access to user data.
• Reside within 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 app or website, without requiring users to navigate menus or settings.
• Provide clear and precise information delineating the categories of data accessed, requested and/or collected.
• Explain the ways in which the data will be used and/or shared. If the data is requested for one purpose, but is also intended for a secondary use, both use cases must be communicated to users.
• Remain separate from unrelated information and cannot be relegated solely to privacy policies or terms of service.

• Request for Consent: The 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.
• Require the user to take a positive action (e.g. press the button to accept, check a box, confirm verbally) for consent to be granted.
• Avoid interpreting actions such as navigating away from the disclosure as consent (e.g., typing elsewhere, using the “back” or “home” button).
• Refrain from using automatic deletion or expiration messages as a consent mechanism.

• User Help Documentation: It is your responsibility to provide user-friendly documentation that describes procedures for users to manage and delete their data from your application.

These measures increase transparency and control over user data, fostering an environment of trust and accountability between developers and users. By adhering to these guidelines, developers play a vital 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, modification or disclosure.

Recommended and required security practices to enhance 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 an approach overall protection of information assets.
• Robust application architecture: Implementing a robust application or web service structure, free from common OWASP Top 10 security vulnerabilities, strengthens 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 systems or yours.
• Data transmitted on external networks not falling exclusively under your administration.
• Data at rest on your systems.
• Secure Data Transmission: Use secure contemporary protocols (e.g., HTTPS) when transmitting data to ensure data integrity during transit.

• Credential encryption: Ensure that user data and credentials, especially tokens such as OAuth access and refresh tokens, are encrypted when at rest.
• Key management: Manage keys and key hardware wisely, 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 contact@footbar.com of any known or suspected unauthorized access to systems, networks, accounts or other locations where Footbar user data is stored. called a "security breach". Developers must also fully cooperate with Footbar to rectify any confirmed or suspected security vulnerabilities. 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.

Flexibility of access and blocking

At Footbar, we understand that each developer's needs are unique. To accommodate this diversity, the Footbar API features a two-tiered access approach designed to meet the preferences of both free and paid members. This approach combines flexibility and resource optimization, ensuring an efficient and tailored experience for all users. Additionally, 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 has predefined throttling limits that ensure fair distribution of resources among users. These limits make it possible to maintain a high level of quality of service while avoiding abuse.

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