Principles for Footbar API Developers:

At Footbar, we hold a steadfast commitment to principles that guide our developers in creating applications that not only harness the power of the Footbar API but also respect user rights and privacy. These principles serve as the foundation for responsible and ethical development:

1. Respect for User Data Ownership: Upholding the philosophy of the General Data Protection Regulation (GDPR), we recognize that user data belongs to the player. We emphasize that data collection or storage should never occur without clear and explicit user consent, ensuring transparency in how their data is utilized.
2. Privacy Safeguarding: Footbar user data is never to be employed for prohibited purposes, including the sale or use of data for advertising endeavors. Developers must prioritize safeguarding user privacy and refrain from actions that compromise this fundamental right.
3. Transparency and Clarity: We stress the importance of accurate and comprehensive communication with players. Developers are expected to provide clear explanations regarding the data collected, the purpose of collection, and the intended use. Transparent communication cultivates trust between developers and users.
4. User-Centric Data Control: In line with user rights, developers are obligated to honor requests from users to delete their data. Respecting users' wishes reinforces the idea that data control is ultimately in the hands of those it pertains to.
5. Robust Data Security: Handling user data securely is non-negotiable. Developers are required to implement robust security practices that ensure the integrity and confidentiality of user data. Demonstrating adherence to these security measures is essential in fostering user confidence.
6. Minimal and Relevant Permissions: Developers should request only the data access permissions necessary to deliver the primary functionalities of their applications or services. This approach limits data exposure and fosters a sense of trust by minimizing unnecessary data handling.

These principles underscore our shared commitment to building applications that not only harness 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.

Compliance with policies

This comprehensive policy governs the entire Footbar ecosystem, including but not limited to the terms of sales, privacy policy, and  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 adhere to the provisions outlined in this policy, along with the associated policies and legal documents mentioned above.

Furthermore, as a user of the Footbar API, you are required to comply with all applicable laws and regulations relevant to your use of the API and its associated services. It is your responsibility to stay informed about any legal requirements that pertain to your usage and to ensure ongoing compliance with these conditions. If, for any reason, you find yourself unable to meet 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 be in violation of applicable laws. It is essential to regularly monitor your compliance with these terms to maintain a productive and compliant relationship with Footbar API.

The Footbar API is designed to empower developers in creating applications that enhance the football player's experience while upholding the values and purposes integral to the Footbar ecosystem. Applications built using the Footbar API should align with the following specified purposes:

• Rewarding Football Practice: Applications can enable football players to receive well-deserved rewards for their dedication and performance on the field.
• Community Interaction: Applications can facilitate the sharing of football players' achievements and progress with the broader community, fostering a sense of camaraderie.
• Performance Enhancement: Applications can offer tools for football players to track, measure, and enhance their performance over time, contributing to their personal growth.
• Performance Analysis and Challenges: Applications can provide functionalities for football players to analyze their performance data, set challenges, and engage in friendly competitions to boost their motivation and skills.
• Gameplay Integration: Applications can incorporate gameplay elements inspired by football practice, offering players an entertaining and immersive experience based on their athletic endeavors.

It's important to note that any use case outside of the specified purposes listed above requires explicit validation from the Footbar team. If you have a unique use case in mind that diverges from the predefined purposes, you must seek approval by contacting us via email at [email protected]. We encourage innovation and creativity while ensuring that applications built using the Footbar API maintain alignment with our values and goals.

By adhering to these guidelines, developers contribute to an ecosystem that not only leverages the Footbar API's capabilities but also respects the integrity of its intent. Together, we can shape applications that celebrate football practice while delivering value and enjoyment to players worldwide.

The data gathered through the Footbar API, along with any data aggregated, anonymized, de-identified, or derived from raw data, is subject to the following constraints to ensure responsible data management:

• Your utilization of user data should be confined to furnishing or enhancing your appropriate use case or features that are readily visible and prominent within the requesting application's user interface.
• Data transfers are permissible only under specific circumstances:
• To furnish or enhance your appropriate use case or user-facing features, clearly discernible from the requesting application's user interface, and solely with user consent.
• For security reasons, such as investigating misuse.
• To comply with relevant laws and/or regulations.
• As part of a merger, acquisition, or asset sale of the developer, provided explicit prior consent from the user is obtained.
• Human access to user data should be restricted, unless:
• Explicit user consent has been obtained to access specific data (e.g., aiding password recovery).
• The data (including derived data) is aggregated and anonymized and is utilized for internal operations in adherence to applicable privacy and jurisdictional legal requirements.
• It's essential for security purposes, such as abuse investigation.
• Compliance with relevant 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 such as advertising platforms, data brokers, or information resellers, even when aggregated or anonymized.
• Transferring, selling, or utilizing user data for advertising purposes, including personalized or interest-based advertising.
• Utilizing user data for determining creditworthiness or lending purposes.
• Using user data in conjunction with products or services that may qualify as medical devices.
• Using user data for purposes involving Protected Health Information.
• Employing user data for activities linked to player recruiting.
• Engaging in activities related to Football trafficking.

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

• Creating applications designed for practicing sports other than Football or encouraging unconventional usage of Meteor devices contrary to Footbar's recommendations.
• Utilizing Footbar APIs for applications, services, or features geared towards collecting or amalgamating user data for research involving human subjects, medical research, or analogous endeavors.

Furthermore, your application must adhere to the design guidelines furnished by Footbar and display the phrase "stats powered by Footbar" in a prominent location.

Finally, it's important to note that utilizing the API does not grant permission to exploit the Footbar brand or logo, become a Footbar product reseller, or embark on any activity that may infringe upon Footbar's intellectual property rights.

Given that the Footbar API deals with football practice data, encompassing personal and sensitive information, it is imperative for all applications and services to incorporate a comprehensive privacy policy. This policy must meticulously elucidate how your application or service gathers, employs, and shares user data. This encompasses detailing the specific entities with which user data is shared, the purpose for data utilization, data storage procedures, security measures, and the protocol in place when an account is deactivated or deleted.

Additionally, applications and services must solicit access to user data within the appropriate context. This approach facilitates user understanding of the data to be provided, the rationale behind data requisition, and the intended data usage. In alignment with applicable laws, the following requisites must be observed:

• A Disclosure Requirement: Your data access, collection, use, and sharing practices must be disclosed in a manner that:
• Accurately identifies the application or service seeking user data access.
• Resides within the application itself for app-based interactions or within a separate dialog window for web-based interactions.
• Presents the disclosure seamlessly during regular app or website usage without necessitating users to navigate through menus or settings.
• Furnishes clear and precise information delineating the categories of data being accessed, requested, and/or collected.
• Explicates the means by which the data will be employed 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.
• Remains distinct from unrelated disclosures 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 solicitation:
• Presents the consent dialog in a lucid and unequivocal manner.
• Mandates an affirmative user action (e.g., tapping to accept, checking a checkbox, verbal confirmation) for consent to be granted.
• Avoids construing actions like navigating away from the disclosure (e.g., tapping elsewhere, using the back or home button) as consent.
• Abstains from using auto-dismissing or expiring messages as a consent mechanism.
• User Help Documentation: It is incumbent upon you to provide user-friendly documentation that outlines procedures for users to manage and delete their data from your application.

These measures bolster transparency and control over user data, fostering an environment of trust and accountability between developers and users. By adhering to these guidelines, developers play an essential role in cultivating a secure and respectful digital landscape.

The sanctity of user data is of paramount importance to us. As such, we require stringent measures to ensure that all Footbar user data remains secure both in transit and at rest. Developers are expected to exercise reasonable and appropriate precautions to shield applications or systems leveraging Footbar user data from unauthorized access, misuse, destruction, loss, alteration, or disclosure.

Outlined below are recommended and mandated security practices to fortify data protection:

Recommended Security Practices:

• Information Security Management System (ISMS): Developers are encouraged to adopt and uphold an Information Security Management System aligned with standards such as ISO/IEC 27001. This framework establishes a comprehensive approach to safeguarding information assets.
• Robust Application Architecture: Implementing a robust application or web service structure, free from common security vulnerabilities listed in the OWASP Top 10, enhances data integrity and fortifies against potential threats.

Required Security Measures:

• Encryption Standards: Employ an industry-recognized encryption standard to encrypt user data in the following instances:
• Data stored on portable devices or portable electronic media.
• Data retained beyond Footbar's or your systems.
• Data transmitted across external networks not exclusively under your administration.
• Data at rest on your systems.
• Secure Data Transmission: Utilize secure contemporary protocols (e.g., HTTPS) when transmitting data to ensure data integrity during transit.
• Credential Encryption: Ensure user data and credentials, particularly tokens like OAuth access and refresh tokens, are encrypted when at rest.
• Key Management: Manage keys and key material judiciously, possibly storing them in a hardware security module or an equivalently robust key management system.

Furthermore, developers are obligated 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, referred to as a "Security Breach." Developers must also collaborate fully with Footbar to rectify any confirmed or suspected Security Breach. In such instances, it is expected that developers communicate with Footbar before making any public statements concerning the breach.

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