Terms of Use

1. Acceptance of Terms

By accessing or using ADSBiq services, including our website, API, live map, and feeder network (collectively, the "Service"), you agree to these Terms of Use. If you do not agree, please do not use the Service.

2. Description of Service

ADSBiq operates a community-powered ADS-B (Automatic Dependent Surveillance-Broadcast) aggregator network. We collect unencrypted, publicly broadcast ADS-B transmissions from volunteer feeders who run radio receivers, aggregate this data in real time, and make it available through a live map and API.

ADS-B signals are broadcast openly by aircraft on the 1090 MHz frequency as required by aviation regulators worldwide. Receiving these signals is lawful in most jurisdictions.

3. Feeder Participation

Volunteer feeders contribute ADS-B data by running receiver equipment (typically a Raspberry Pi with an RTL-SDR dongle) at their location. By joining the feeder network, you agree that:

• You are providing data voluntarily and may stop feeding at any time.
• You have the legal right to operate radio receiving equipment at your location.
• The approximate location of your receiver may be used internally for MLAT (multilateration) calculations and coverage analysis. Your precise location is not displayed publicly unless you opt in.
• You grant ADSBiq a worldwide, non-exclusive, royalty-free license to use, process, store, aggregate, and redistribute the ADS-B data you contribute, including in combined or derivative datasets, for the duration of your participation. Data already contributed prior to withdrawal may be retained in historical archives.
• Active feeders receive enhanced API access as a benefit of participation.
• Your feeder UUID is embedded in the data stream sent to our server for per-feeder attribution and network health monitoring.
• The feeder software sends periodic heartbeat signals (approximately every 5 minutes) containing your feeder UUID and originating IP address to confirm connectivity and update online status.

3a. Location Auto-Discovery

During installation, the feeder script may offer to detect your receiver's geographic coordinates from existing ADS-B feeder configurations on the same device (such as readsb, dump1090, PiAware, FlightRadar24, or other feeder software). This is used solely for MLAT positioning. In interactive mode, you are prompted before any config files are read. You may decline auto-detection or bypass it entirely by passing --no-location-scan to the install script. You may also set or update your location at any time on the ADSBiq website.

3b. Automatic Updates

The feeder install script includes an optional automatic update mechanism (via systemd timer) that contacts the ADSBiq server daily to determine if a newer version of the feeder software is available. If an update is found, the new script is downloaded from adsbiq.com over HTTPS, verified via SHA256 checksum, and executed automatically. This ensures feeders receive security patches, bug fixes, and protocol improvements without manual intervention.

Automatic updates are disabled by default (opt-in). To enable: install with --enable-auto-update flag, or run sudo systemctl enable --now adsbiq-update.timer after installation. To disable: sudo systemctl disable --now adsbiq-update.timer. You may audit the feeder script at any time: curl -sL adsbiq.com/feed.sh | less.

4. API Usage

ADSBiq provides an API for accessing real-time aircraft data. API usage is subject to the following conditions:

• Active feeders (those whose receiver has sent data within the last 24 hours) have included API access, subject to reasonable rate limits (see API documentation).
• Non-feeder API users have no API access. Only active feeders may use the API.
• API access is tied to your feeder's IP address and is non-transferable.
• You may not use the API for bulk scraping or systematic mirroring of the data feed for redistribution.
• Removal or circumvention of anti-abuse mechanisms (rate limits, authentication) is prohibited.
• ADSBiq reserves the right to revoke API access for abuse or violation of these terms.

5. Data Accuracy

ADS-B data is provided "as is" from aircraft transponder broadcasts. ADSBiq does not guarantee the accuracy, completeness, or timeliness of any data. Route data is sourced from FAA flight plans and may contain errors or omissions.

The Service is not intended for use in air traffic control, flight safety, navigation, or any safety-critical application. Do not make safety decisions based on data from ADSBiq.

6. Intellectual Property

Raw ADS-B transmissions are uncopyrightable publicly broadcast signals. ADSBiq's software, website design, and branding are proprietary. You may use API data for personal, research, or commercial projects subject to these terms, but you may not republish the aggregated feed in its entirety.

7. Acceptable Use

You agree not to:

• Attempt to interfere with, compromise, or disrupt the Service or its infrastructure.
• Use the Service to track individuals without their consent or for stalking, harassment, or surveillance purposes.
• Use the watchlist or alert features to monitor specific aircraft for the purpose of tracking the movements, location, or activities of any individual.
• Reverse-engineer or probe the Service's internal systems beyond what the API provides.
• Circumvent rate limiting or authentication mechanisms.
• Use ADSBiq data to spoof, impersonate, or falsify aircraft identification, or to create synthetic flight data intended to deceive.
• Violate any applicable local, national, or international law in your use of the Service.

7a. Watchlist & Alerts Policy

The watchlist feature allows feeders to receive notifications when specific aircraft types, callsigns, or transponder codes appear in the network. This feature is intended for aviation enthusiasts monitoring interesting traffic (military, medical, fire, rare types) — not for tracking individuals.

ADSBiq reserves the right to disable watchlist entries, suspend alert delivery, or terminate feeder accounts that abuse this feature. Aircraft owners or operators may request removal of their aircraft from watchlist tracking by contacting [email protected] with proof of ownership or operational authority.

7b. Abuse Reporting

To report misuse of ADSBiq services, including suspected harassment, unauthorized tracking, or other violations of these Terms, contact [email protected] with:

• A description of the suspected abuse
• Any relevant aircraft registration, hex code, or feeder identifier
• Evidence supporting the report (screenshots, timestamps, etc.)
• Proof of ownership or authority, if requesting aircraft removal

ADSBiq will acknowledge reports within 48 hours and take appropriate action within 5 business days, which may include disabling watchlist entries, suspending alerts, or terminating accounts.

8. Limitation of Liability

To the fullest extent permitted by law, ADSBiq and its operators shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits or revenues, arising from your use of the Service. Our total liability for any claim related to the Service shall not exceed the amount you have paid us in the 12 months preceding the claim (if any).

9. Service Availability

ADSBiq is provided on a best-effort basis. We do not guarantee uptime, availability, or uninterrupted service. We may modify, suspend, or discontinue any part of the Service at any time without notice.

10. Indemnification

You agree to indemnify, defend, and hold harmless ADSBiq and its operators, affiliates, and service providers from and against any claims, liabilities, damages, losses, and expenses (including reasonable attorneys' fees) arising out of or related to:

• (a) your use of the Service or API,
• (b) your violation of these Terms,
• (c) your misuse of ADS-B data, or
• (d) your violation of any applicable law or third-party rights.

11. Governing Law

These Terms are governed by the laws of the State of Florida, United States, without regard to conflict-of-law principles. Any litigation arising from these Terms shall be brought exclusively in the state or federal courts located in Palm Beach County, Florida.

12. Dispute Resolution

The parties agree to attempt to resolve any dispute informally before initiating legal proceedings. If informal resolution is unsuccessful within 30 days, either party may pursue remedies available under applicable law in the courts described in Section 11.

13. Changes to These Terms

We may update these Terms from time to time. Material changes will be posted on this page with an updated date. Continued use of the Service after changes constitutes acceptance of the revised Terms.

14. Contact

Questions about these Terms may be directed to: [email protected]