In light of the release of the direct subscriptions and data contribution program we are updating our Terms of Use and Privacy Policy. The most of the changes clarify most common gaps that were questioned on by our subscribers and mostly clarify what has been previously implied, while some changes materially change how some of the existing subscribers may use the API.
Additionally, we are clarifying and adjusting existing marketplace pricing plans provided through RapidAPI and API.Market to harmonize them with the direct subscriptions release.
All changes apply:
- for all new subscribers: immediately; and
- for all existing subscribers: after an increased grace period of 60 days from the publication date of this announcement (the 7th of November, 2026), unless stated otherwise below.
Major Plan and Terms Changes
Attribution required for free plans (Terms, Article 5.4). If you’re subscribed to any free/trial or Basic plan, anything you publish publicly that’s built on our data needs a visible mention of AeroDataBox wherever the data shows up, plus a working link to aerodatabox.com where technically possible. For any paid plan attribution remains optional (not required).
Commercial use now requires a paid plan. (Terms, Article 5.3). It’s no longer allowed on any free/trial or Basic plan. If Basic is powering anything commercial on your side, please upgrade to any paid plan (including Pro).
Commercial use for some B2B cases may require Mega plan or higher. (Terms, Article 5.7). Passing data-derived content to business customers now depends on your plan. If your customer simply uses the result you produced, that’s an ordinary sale: a flight-status app people check their flight on, a paid dashboard showing delay statistics you computed, an on-time performance report an airline reads. That is an ordinary commerical use that is covered any paid plan as mentioned above. But in some B2B-scenarios where your business customer can build and sell on top of what you supply based on our data, for example, by querying your enriched dataset and exporting records into their own system, by embedding your derived dataset in a product they resell, or by taking a feed from you they’re allowed to pass on commercially, that’s is now subject to Commercial Derived Work sublicensing.
Among the marketplace plans, only Mega includes it now. Some direct subscription plans will also include this option.
The FAQ has more details on what may fall under this licensing. To avoid any confusion, it shall be reminded that reselling our API itself or the raw data it returns remains not allowed on any plan.
Caching / Data retention is now capped at 7 days by default. (Terms, Article 5.5) We have got a lot questions about it and now clarified it. Caching the data that you get from AeroDataBox is now firmly capped at 7 days in the most of the cases and solely for the purposes of your application. However, some plans are now coming with longer permissible retention periods. “Ultra-2” (API.Market only) and “Mega” (RapidAPI and API.Market) plans come with extended caching and allow you to retain our data for as long as you have subscription is active. Certain direct subscriptions will allow even longer caching. Certain exceptions apply for your derived works that you build on top of your data (Terms, Article 5.6).
Plan Changes
FIDS endpoint (applies immediately). A single call to a FIDS (airport departures and arrivals) endpoint used to allow 12 hours on all plans. It now permits 24 hours on “Ultra-2” (API.Market only) and “Mega” (RapidAPI and API.Market) plans for the same call price.
Pricing, quota and rate limit adjustments (does NOT apply to existing subscribers until they resubscribe). All marketplace plans had their pricing and quotas adjusted. Rate limit has been increased as well permitting more calls:
On RapidAPI the new limits are:
- 2 requests per second on Pro
- 4 requests per second on Ultra
- 8 requests per second on Mega.
On API.Market:
- 1 request per second on Pro
- 2 requests per second on Pro 2
- 3 requests per second on Ultra
- 4 requests per second Ultra 2
- 5 request per second on Mega
Upcoming direct subscriptions will permit even higher rate limits.
Support levels adjusted (applies immediately). For practicaliy and capacity reasons we will now prioritize requests from the subscribers on the higher plans and will unfortunately limit support to the lower plans.
Other Changes
Other Terms of Use changes. Beyond the points above, the parts that have changed are: Definitions (new), Article 1 (Introduction), Article 2 (Binding), Article 4 (Acknowledgments), Article 5 (General Conditions), Article 6 (Registration and Access Credentials), Article 7 (Billing, Payment, and Refunds), Article 10 (Suspension, Termination and Account Deletion), Article 11 (Force Majeure), Article 12 (Confidentiality), Article 13 (Data Contribution and Idea Submission), Article 15 (Modifications), Article 19 (Limited Relationship), Article 20 (Transfer of Rights), Article 22 (Choice of Law, Disputes and Compliance), Appendix A (Authorized Marketplaces) and Appendix B (Notification Channels, new). These changes largely include clarification of pre-existing processess and terms as well as necessary wording and structural adjustments.
Privacy policy changes. The policy now covers more aspects of our services and not only the website, so it explains what we receive when you call it and how long we hold on to it. We’ve also refreshed the list of third-party services behind the scenes. Your rights under it haven’t changed.
What to do
Please review the Terms of Use, the Privacy Policy and the Pricing page to understand if any adjustment of use of our API is required for you or if you need to change your pricing plan. If so, please implement the changes prior to the date mentioned at the beginning of this page.