The askFRED.net API is an extension of askFRED.net. FRED API applications and developers are required to comply with, and are subject to, this Terms of Service, as well as the askFRED.net website Terms of Service. This Terms of Service forms an agreement between you, the developer or user of the FRED API, and Acetylene Solutions, the operator of askFRED.net and its related services.
Create a great user experience.
- Give easy access to information in FRED.
- Give users choice and control.
- Help users organize and participate in sporting activities and events.
- Respect privacy
- Don't mislead, confuse, defraud, or surprise users
- Don't spam - encourage authentic communications
Build businesses without compromising FRED.
- Build on FRED’s service, providing new features that FRED doesn’t offer.
- Don’t build a product that degrades or competes directly with FRED’s core products.
I. Features and Functionality
- You must not violate any law or the rights of any individual or entity, and must not expose FRED, FRED’s operator (Acetylene Solutions) or FRED’s users to harm or legal liability as determined by us in our sole discretion.
- You must respect and protect the privacy of FRED’s users. You must not build any feature or service that could be used to “stalk” a FRED user or otherwise violate their privacy or security. You must not expose information to the public that the askFRED.net website restricts from public view. Please see the examples below.
- You must not use the FRED API or FRED data to build a product that substantially replaces or competes with FRED’s existing features, functionality, or service. Again, please see the examples below.
- You must not circumvent (or claim to circumvent) our intended limitations on core FRED features and functionality.
- You must make it clear to users that although your product is integrated with FRED, it is an independent product. This includes your product’s UI, and all published material describing your product. Your product must not claim to be an official product of FRED, askFRED.net, or Acetylene Solutions.
- To ensure users are not confused, any use you make of FRED’s name, icons, or identifying marks must be reviewed by Acetylene Solutions. If you plan on such use, inquire about its review when applying for API access keys.
II. Storing and Using Data You Receive From Us
- You will only request the data you need to operate your application.
- You may cache data you receive through use of the FRED API in order to improve your application’s user experience, but you should try to keep the data up to date. This permission does not give you any rights to such data.
- You will not sell any data. If you are acquired by or merge with a third party, you can continue to use FRED data within your application, but you cannot transfer data outside your application.
- If you stop using the FRED API or we disable your application, you must delete all data you have received through use of the FRED API.
- You will delete all data you receive from us concerning a user if the user asks you to do so, and will provide an easily accessible mechanism for users to make such a request. We may require you to delete data you receive from the FRED API if you violate our terms.
- You must not give your API key to another party, unless that party is an agent acting on your behalf as an operator of your application. You are responsible for all activities that occur under your account identifiers.
III. Application Content
- Responsibility for Content - You are responsible for all content of and within your application, including advertisements, user-generated content, and any content hosted, streamed or otherwise delivered to users by third parties. You must make it clear that this content is not provided by FRED.
- Prohibited Content - You agree that you will not use FRED data to promote, or provide content referencing, facilitating, containing or using, the following:
- Alcohol-related content or sale of tobacco products, ammunition and/or firearms;
- Content that infringes upon the rights of any third party, including intellectual property rights, privacy, publicity, moral or other personal or proprietary right, or that is deceptive or fraudulent;
- Online gambling, games of skill or lotteries, including online casinos, sports books, bingo, or poker.
- Content that is hateful, threatening, defamatory, or pornographic; incites violence; or contains nudity or graphic or gratuitous violence.
We can take enforcement action against you and any or all of your applications if we determine in our sole judgment that you or your application violates askFRED.net API Terms of Service. Enforcement action is both automated and manual, and can include disabling your application, restricting you and your application's access to API functionality, terminating our agreements with you, or any other action as we in our sole discretion deem appropriate.
Communication with developers takes place via an email sent from the askfred.net, acetylenesolutions.com or countersix.com domains to the developer contact email address you provided via http://support.askfred.net. To stay in touch, please ensure that your email address is current and that you do not filter out any such messages.
We can change this Terms of Service at any time without prior notice as we deem necessary. Your continued use of the API constitutes acceptance of those changes.
Examples and Explanations
Sometimes an example is the best way to understand what’s ok and what’s not ok. We hope these examples will be helpful, but they do not limit or define in any way the provisions of the actual Terms of Service.
The FRED API allows you to expose the names of preregistrants for tournaments on FRED. OK: It is ok to publicly display the names of fencers preregistered for a certain tournament. NOT OK: However, it would not be ok to use the API to publicize all the future preregistrations of individual fencers. This could be used as a tool to “stalk” a fencer.
The FRED API provides access to FRED's whole database of fencers. OK: It would be ok to show all a fencer's results and bouts, which might help a coach keep track of her fencers' performance, and plan their training. NOT OK: It would not be ok to copy the whole fencer database and then use that data to target fencers for marketing purposes, or to give their names to another company who might do the same.
The FRED API provides lists of tournaments and their organizers' contact information. OK: It would be ok to list the organizers' contact information to help your users get in touch with organizers to ask about fencing in their tournaments. NOT OK: It would not be ok to harvest organizers' contact information from the API and then contact them to solicit them to use a competing competition hosting service instead of FRED.
The FRED API provides access to results data. OK: It would be ok to extract the results for your club's tournaments and display them on the club website. NOT OK: It would not be ok to copy the whole FRED results database and then publicize a full mirror of the FRED results listings, thereby diverting traffic from the FRED website.