Government Customer Addendum

RotorLab.app: Government Customer Addendum

Effective date: October 4, 2026

This Addendum applies where the Customer is a public body: a federal, state, provincial, tribal, county or municipal government, an agency, a public safety department, a public university or school, or another entity that is subject to public records, procurement or sovereign-immunity law ("Government Customer"). It modifies the Terms of Service as stated below and controls where the two conflict. Nothing in it is a waiver of a Government Customer's sovereign immunity.

1. Governing law and venue. Section 17 of the Terms does not apply. The agreement is governed by the law of the Government Customer's own jurisdiction, and any dispute is heard in the courts, or by the process, that jurisdiction's law provides for claims against it. The one-year limitation on claims applies only where that law allows it.

2. Indemnification. Section 14 of the Terms applies to a Government Customer only to the extent its law allows it to indemnify a private party; where it does not, Section 14 does not apply and each party bears its own liability as the law provides.

3. Public records. The Government Customer may be required to disclose this agreement, its fees and the Records it keeps in the Service under public records law, and RotorLab does not object; RotorLab asks only to be told of a request for RotorLab's own confidential material (source, security detail beyond the trust page) so it may assert an exemption where one exists. Records the Government Customer keeps in the Service are its public records where its law says so; the Service's export, audit package and activity log exist to answer such a request from the Customer's own copy.

4. Records retention and litigation hold. The Government Customer's records-retention schedule governs how long it keeps Records in the Service; the Service's retention controls, "keep for life" and legal hold are the tools it uses to comply. RotorLab does not delete a Government Customer's Records during the term except at its written instruction, where the organization is recorded in the Service as a public body: an administrator ticks "We are a public body" on the Records page, or the organization holds the Public Safety Ops add-on. For a public body, the windows for precise flight positions and stored flight-log files are kept until the Government Customer sets them, and a window it sets is its written instruction. On a litigation hold or a preservation request, the Government Customer places the affected Records on hold in the Service and RotorLab preserves them in the Service until the hold is lifted in writing. RotorLab's database backups carry a copy of the Records held in the database; stored flight-log files are kept in the Service's file store and are not in those backups, so a held flight's log file is preserved in the Service itself.

5. Appropriations and termination for convenience. Where the Government Customer's law makes its payment obligations subject to appropriation, the agreement is so subject, and the Government Customer may terminate on written notice at the end of any fiscal period for which funds are not appropriated, without penalty; fees are owed only for the period the Service was available. The Government Customer may also terminate for convenience on thirty days' written notice; prepaid fees for the unused period are refunded. Either way, Section 15 of the Terms (when a plan ends) applies from termination: ninety days read-only with export, then twelve months retained with no access, then deletion after an alert and a final notice. Where the Government Customer's records-retention law requires Records to be kept longer, it exports them during the ninety days or places them on legal hold, and RotorLab does not delete a Record on hold while the hold stands.

6. Data location and access. Records are stored and processed in the United States. RotorLab does not access a Government Customer's Records except to provide the Service at its request or to the extent the law requires, and tells the Customer of a legal demand for them unless the law forbids it. For a Government Customer, the emergency access in Section 3 of the Data Processing Addendum is used only at its request or where the law requires it. RotorLab does not claim CJIS, FedRAMP or GovRAMP (formerly StateRAMP) authorization; a Government Customer whose data requires one does not keep that data in the Service. A Government Customer chooses what its flights keep of where they flew (the exact position, only a rounded area, or no position) and can switch off outside map, weather and lookup services and usage analytics for its members, as Sections 2(e) and 4A of the Privacy Policy describe; where the Service runs with its encryption key, positions, flight log files, live recordings, saved missions and area outlines are sealed at rest as they are written, as Section 2(e) of the Privacy Policy and Section 4 of the Data Processing Addendum describe.

6A. A copy inside the Government Customer's own network. Where a Government Customer must keep its Records inside its own network, RotorLab may provide it with a copy of the Service's release to run there, in offline mode. That copy makes no connection outside the Government Customer's network: it has no independent timestamps, map imagery from outside services, DJI log reading, weather or airspace downloads, or card payments, and every signed-in page says that offline mode is on. Its maps and terrain can come from a tile server inside the same network, and its single sign-on, email and webhooks can reach only the hosts inside that network its operator lists. The Government Customer runs, secures and backs up that copy itself and decides whether it holds an encryption key; RotorLab does not hold, reach or process the Records kept in it, so the Data Processing Addendum's sections on RotorLab's hosting, subprocessors, support access and deletion do not apply to them.

7. Accessibility. RotorLab targets WCAG 2.1 AA for the Service and for the public transparency page, and states an accessibility contact on that page; a Government Customer may ask RotorLab for the current conformance statement and RotorLab answers a reported barrier within thirty days.

8. Payment terms. A Government Customer may pay by purchase order on the terms in Section 5 of the Terms: each invoice is due thirty days after its invoice date unless the Government Customer has agreed other payment terms with RotorLab (for example, a term its prompt-payment law sets), in which case its invoices state them, and no late fee applies beyond what its prompt-payment law provides. Tax is charged only where RotorLab is required to collect it, at the rate shown on the invoice; a Government Customer that is exempt records its exemption certificate in its billing details, and an invoice to it then charges none.

9. Publicity. RotorLab does not use the Government Customer's name or seal in marketing without its written consent, except to state that it is a customer where the Customer's own public records already say so.

10. Order of precedence. Where this Addendum, the Terms and the Data Processing Addendum conflict, this Addendum controls, then the Data Processing Addendum, then the Terms; a signed agreement between the parties controls over all three.

11. Notices. Notices to RotorLab under this Addendum go in writing to RotorLab, Inc., Dubuque, Iowa, and by email to legal@rotorlab.app.

These documents have changed since you last accepted them. Read the ones that matter to you from the list, then confirm to continue to RotorLab.