Terms of Service

Last updated: March 2, 2026 (Round 25 Hardening)  |  Effective: March 2, 2026

1. Acceptance of Terms

These Terms of Service ("Terms") constitute a legally binding agreement between you (individually or on behalf of an entity, collectively "you," "Customer," or "User") and Country Road Drone Services, LLC, an Iowa limited liability company ("Company," "we," "us," or "our"), governing your access to and use of the DroneCommand spray operations management platform, including all related websites, applications, features, content, and services (collectively, the "Service").

By accessing or using the Service in any way — including but not limited to creating an account, beginning a free trial, entering payment information, clicking any "Agree," "Accept," or "Sign Up" button, or otherwise manifesting assent — you agree to these Terms and our Privacy Policy, which is incorporated herein by reference.

If you are entering into these Terms on behalf of a business, organization, or other legal entity, you represent and warrant that you have full legal authority to bind that entity to these Terms. If you do not have such authority, you may not use the Service on behalf of that entity.

These Terms apply to all users of the Service, including account administrators, pilots, managers, accountants, and any other role accessing the Service under a Customer account.

2. Definitions

As used throughout these Terms:

• "Service" means the DroneCommand cloud-based spray operations management platform, including all features, APIs, integrations, documentation, and updates.
• "Customer" or "Account Holder" means the individual or legal entity that registers for and maintains the DroneCommand account and bears responsibility for all use and payment obligations under these Terms.
• "Authorized User" means any individual (employee, contractor, pilot, or staff member) granted access to the Service by the Customer.
• "User Data" means all data, records, files, content, and information submitted, uploaded, entered, or generated through the Service by Customer or its Authorized Users, including spray operation records, field boundary data, customer information, chemical records, inventory records, time logs, and payroll data.
• "Subscription" means paid access to the Service under a selected billing plan.
• "Billing Cycle" means the recurring period for which Customer pays (monthly, annual, two-year, or four-year as labeled, per Section 6).
• "Regulatory Records" means spray application records required to be retained under applicable law, including but not limited to Iowa Administrative Code Chapter 45.26 and equivalent provisions of all U.S. states and jurisdictions in which you conduct agricultural spray operations.
• "Stripe" means Stripe, Inc., our third-party payment processor.
• "DriftWatch" means the FieldWatch/DriftWatch sensitive crop and apiary mapping service operated by Purdue University.
• "Iowa BeeCheck" means the Iowa Honey Producers Association's beekeeper registry integrated into the Service.
• "Mix Calculator" means the chemical batch sizing and application rate calculation tools within the Service.
• "Geospatial Data" means GPS coordinates, field boundary polygons, acreage calculations, mapping layers, and location-based information within the Service.

3. Eligibility and Account Registration

To register for and use the Service, you must:

• Be at least 18 years of age;
• Have the legal capacity and authority to enter into a binding contract;
• If acting on behalf of an entity, have proper authority to bind that entity;
• Provide accurate, complete, and current registration information;
• Maintain and promptly update your account information as necessary to keep it accurate and current;
• Agree to these Terms and our Privacy Policy.

You represent and warrant that all information you provide during registration and thereafter is truthful, accurate, and complete. Providing false or misleading information is a material breach of these Terms and grounds for immediate account termination without refund.

We reserve the right to reject any registration, suspend or terminate any account, or refuse service to any person or entity for any reason or no reason, in our sole discretion.

4. Account Security

You are solely responsible for maintaining the confidentiality and security of your account credentials, including usernames and passwords. You agree to:

• Use a strong, unique password for your DroneCommand account;
• Not share your login credentials with any person who is not an Authorized User under your account;
• Not allow any single set of credentials to be used by multiple individuals;
• Log out of your account at the end of each session, particularly on shared devices;
• Immediately notify us at [email protected] upon discovering or suspecting any unauthorized access to or use of your account, or any other security breach.

You are fully responsible for all activities, transactions, records, and actions that occur under your account, whether or not authorized by you. We are not liable for any loss, damage, or liability arising from your failure to maintain account security, including losses resulting from unauthorized access due to compromised credentials.

In the event of suspected unauthorized access, we may, in our sole discretion, suspend your account, require a password reset, or take other security measures. We will not be liable for any consequences of such protective actions.

4.0a Password Reset and Account Recovery

Password reset emails are sent to the email address stored in your account profile. We are not liable for unauthorized account access resulting from a password reset email being delivered to an incorrect email address where: (a) we stored the email address exactly as you provided it at registration or as you subsequently updated it; and (b) any error in the stored address was caused by your own input. It is your responsibility to verify that the email address in your account profile is accurate before initiating a password reset. If you believe your account email address was stored incorrectly in our system through no fault of your own (e.g., a technical error on our side), contact us immediately at [email protected]. For high-security accounts, consider using the two-factor authentication feature described in Section 4.1 to provide an additional layer of protection beyond email-based recovery.

4.1 Two-Factor Authentication (2FA)

Where we offer two-factor authentication ("2FA") as an optional account security feature, you are solely responsible for deciding whether to enable it. We strongly recommend enabling 2FA. However: (a) your decision not to enable available 2FA does not shift any responsibility for unauthorized account access to us — you remain fully responsible for account security regardless of which optional security features you choose to enable; (b) we are not liable for account breaches, data theft, record alteration, unauthorized transactions, or any other harm resulting from unauthorized access that 2FA would have prevented if it had been enabled; (c) the availability of 2FA is not a warranty or guarantee of account security, and even with 2FA enabled we cannot guarantee prevention of all unauthorized access; and (d) if your account is accessed without authorization because 2FA was not enabled, any resulting harm, costs, or regulatory consequences are your sole responsibility.

4.2 Never Share Credentials With Our Support Team

Our support team will never ask for your password. We can assist with your account without knowing your password — we have administrative tools for legitimate support purposes that do not require your credentials. If you share your password, account credentials, or 2FA codes with anyone — including a person claiming to be our support staff — you have compromised your account security.

• If you email, text, or otherwise transmit your DroneCommand password or 2FA code to any party, including to [email protected] or any other email claiming to be ours, change your password immediately. Do not wait to see whether anything bad happens — change it now;
• We are not liable for any unauthorized access, data theft, record alteration, or other harm arising from or following your transmission of your credentials to any party, including to us, whether intentionally or inadvertently (e.g., included in a support request email, screenshot, or copy-paste error);
• If you receive a message from any party claiming to be DroneCommand support and requesting your password, API key, 2FA code, or any similar credentials, treat it as a phishing attempt. Report it to us at [email protected] and do not respond to the request;
• The fact that you sent your credentials to our actual support email address does not make us responsible for security consequences — we do not need your password to assist you, and any message requesting it from our domain should be reported as a potential compromise of our communications.

4.3 Your Account Email Address Is the Master Key to Your Account

Whoever controls the email address registered to your DroneCommand account controls your account. The password reset function sends a reset link to your registered email address. Anyone with access to your registered email account — whether a hacker, a current employee, a former employee who still has access to your business email, or any other party — can trigger a password reset and take full control of your DroneCommand account without knowing your current password.

• Compromised email = compromised DroneCommand: If your business email account is hacked, phished, or otherwise compromised, the attacker can immediately use password reset to take over your DroneCommand account. We have no way to distinguish a legitimate password reset from one initiated by an unauthorized party who has gained access to your email. We are not liable for account takeover, data theft, record alteration, or any other harm resulting from an unauthorized password reset initiated through your compromised email account;
• Former employee email access: If a terminated employee retains access to your business email account — because you failed to revoke their email access at termination — that person can use password reset to take over your DroneCommand account even after you've removed them as an Authorized User. Revoking DroneCommand access WITHOUT revoking email access is insufficient protection. You must revoke both;
• Shared email accounts: If your DroneCommand account is registered to a shared mailbox (e.g., [email protected], [email protected]) accessible by multiple people, any of those people can trigger a password reset. We strongly recommend using an individual, access-controlled email address as your DroneCommand account email — not a shared mailbox;
• Keeping your account email current: If your registered email address is no longer monitored, becomes inaccessible, or is associated with a domain you no longer control, you may lose the ability to recover your own account while simultaneously being unable to prevent others with access to that address from recovering it. You are solely responsible for keeping your account email address current, secure, and access-controlled;
• We are not liable for any loss, data breach, unauthorized access, or harm arising from account takeover through the password reset function, regardless of how the attacker gained access to your email.

4.4 Concurrent Sessions — Multiple Users Logged In Simultaneously; Last Write Wins

DroneCommand allows multiple Authorized Users to be logged into the same account simultaneously from different devices. There is no conflict detection, version locking, optimistic concurrency, or merge mechanism for simultaneous edits. If two users are editing the same record at the same time, the last save overwrites all earlier saves with no warning to either user and no record of what was overwritten.

• Silent data loss: If User A is editing a spray record and User B saves a different version of the same record moments later, User A's work is permanently gone — no notification, no version history, no recovery. We are not liable for data loss caused by concurrent session conflicts;
• Regulatory record overwrite: If a concurrent edit replaces accurate regulatory data with inaccurate data — or vice versa — the surviving version is the last save, regardless of accuracy. You are responsible for operational protocols that prevent concurrent editing of the same record by multiple users;
• No record locking or check-out: We do not offer record locking, check-out/check-in workflows, or any mechanism that prevents two users from editing the same record simultaneously. The absence of a warning message does not mean no conflict occurred — it means the last write won silently;
• Recommended mitigation: Assign specific Authorized Users to specific record types or time periods; use role-based access controls to limit who can edit finalized records; and implement operational protocols requiring users to confirm before saving records that another user may have open;
• We are not liable for any regulatory violation, compliance failure, data corruption, insurance denial, or operational harm arising from concurrent session overwrites, regardless of who initiated the conflicting saves or what was permanently lost.

4.5 Session Timeout and Auto-Logout — Unsaved Data Is Lost Without Warning

DroneCommand sessions may time out due to inactivity, browser closure, network interruption, or other causes. When a session expires or you are automatically logged out, any unsaved work in an open form — including in-progress spray records, job records, time entries, or any other data not yet submitted to our servers — is permanently lost. There is no auto-save feature, no draft recovery, and no session restore mechanism that will recover unsaved form data after logout or timeout.

• No warning before timeout: DroneCommand may not provide a visible countdown or "you are about to be logged out" warning before session expiration. If you are entering a complex spray record and are interrupted — by a phone call, physical task, internet outage, or simply leaving your device unattended — and the session expires in the interim, you will return to a login screen and the in-progress record will be gone;
• Browser refresh or tab close: Closing the browser tab, refreshing the page, or navigating away from a form before submitting it will discard all unsaved data in that form. This is standard web application behavior. We are not liable for data loss caused by unintended page navigation, accidental browser closure, or device shutdown while a form is open;
• Regulatory record entry strategy: For spray records and other regulatory records that must be complete and accurate, we strongly recommend entering records promptly after each spray event rather than accumulating several records at once. Entering records while the event is fresh also reduces the risk of time and detail inaccuracy. A partial record lost to session timeout is not a regulatory record — it is an incomplete draft that was never submitted;
• Device and network factors: Mobile devices, tablets, and laptops may aggressively terminate browser sessions to conserve battery or when entering sleep mode. Enterprise network environments may have session timeout settings that terminate sessions independent of browser activity. We are not liable for session loss caused by device-level or network-level session management outside our control;
• We are not liable for any loss of in-progress data, incomplete records, regulatory gaps, or operational harm arising from session timeout, auto-logout, browser behavior, or any other cause of unsaved form data loss.

4.6 SMS-Based Two-Factor Authentication — SIM Swap and SS7 Vulnerability

Where DroneCommand offers SMS-based two-factor authentication (2FA) — in which a one-time code is delivered to your mobile phone number by text message — you should understand that SMS-based 2FA is less secure than app-based 2FA methods and is vulnerable to SIM swap attacks and SS7 network interception. We provide SMS-based 2FA as a convenience option and make no representation that it is immune to these attack vectors.

• SIM swap attacks: A SIM swap attack occurs when a criminal contacts your mobile carrier and — through social engineering, fraudulent documentation, or a compromised carrier employee — convinces the carrier to transfer your phone number to a SIM card controlled by the attacker. Once transferred, the attacker receives all SMS messages intended for your number, including 2FA codes sent to your DroneCommand account. We have no ability to detect or prevent SIM swap attacks at your carrier;
• SS7 network vulnerabilities: The SS7 telecommunications protocol, which underlies the global telephone network, has known security vulnerabilities that sophisticated attackers have exploited to intercept SMS messages including 2FA codes in transit. We have no control over SS7 network security, which is an infrastructure issue at the telecommunications carrier level;
• Stronger alternatives: If available, we recommend using authenticator app-based 2FA (e.g., Google Authenticator, Authy, or similar TOTP-based apps) rather than SMS-based 2FA for your DroneCommand account. App-based TOTP codes are not transmitted over the telephone network and are therefore not vulnerable to SIM swap or SS7 interception;
• Your carrier security is your responsibility: Setting a carrier-level PIN or passcode that prevents unauthorized SIM transfers is the most effective defense against SIM swap attacks. Contact your mobile carrier to set a port/SIM transfer PIN. We cannot set this for you;
• We are not liable for any unauthorized account access, data theft, spray record alteration, financial loss, or regulatory consequence arising from a SIM swap attack, SS7 interception, or any other attack that compromised your SMS-based 2FA codes.

4.7 Shared Devices and Persistent Browser Sessions — Other Household or Farm Members Can Access Your Account

Many agricultural operations are run from a shared office computer, farm shop tablet, or home device that multiple household or business members use. Browsers that are configured to remember logins — through "Remember me" checkboxes, saved passwords, or persistent session cookies — may keep your DroneCommand account logged in between your sessions. If another person uses the same device and browser, they may access your DroneCommand account without your password and without any notification to you.

• Persistent sessions are a security choice, not an error: Choosing to stay logged in on a shared device is a deliberate security tradeoff. We provide the option; your choice to use it on a shared device transfers the access risk to you. We are not liable for account access, record creation, record deletion, or any other action taken by a family member, farm employee, or other person who accessed your account through a persistent session on a shared device;
• Browser password managers: If your browser is configured to auto-fill your DroneCommand credentials and your device is left unlocked, any person with physical access to your device can access your account. This applies to family members, repair technicians, housekeepers, farm workers, and anyone else who has physical access to your unlocked device;
• Farmworker and contractor access via device: If a pilot, seasonal worker, or contractor uses your office computer or tablet during their work and your DroneCommand session is active, they may access, view, or alter your records. Physical device security is your responsibility;
• Best practice: Log out of DroneCommand at the end of each session, particularly on shared devices. Use a device-level PIN or password to prevent unauthorized access when the device is unattended. Do not save your DroneCommand credentials in a shared browser profile;
• We are not liable for any record alteration, data theft, unauthorized spray record creation, account modification, or other consequence arising from shared device access by any person who did not require your password because your session was persistent or your credentials were saved in a shared browser.

4.8 Credential Stuffing and Third-Party Data Breach Account Compromise

Third-party data breaches — at retailers, banks, email providers, social media platforms, and other online services — routinely expose usernames and password combinations that criminals then test against other services in automated "credential stuffing" attacks. If you reuse an email address and password combination across multiple online accounts, a breach of any one of those other services creates a direct risk that those same credentials will be tested against DroneCommand. DroneCommand cannot protect your account from credential stuffing attacks if you use a password for DroneCommand that you have also used on any other service that has been breached — and we have no way to know whether or when that has occurred.

• Password reuse is the primary credential stuffing attack vector: The most common account takeover method in modern internet fraud is not hacking our systems — it is obtaining credentials from a breached third-party service and testing them automatically against thousands of other services. We are not responsible for account takeovers that result from credential stuffing using passwords you have reused from another platform, regardless of how secure our own systems are;
• Breach notification monitoring is your responsibility: Services that suffer data breaches are required in many states to notify affected users, but notification timing and completeness vary significantly. You are responsible for monitoring breach notification services (such as haveibeenpwned.com or similar), responding promptly to breach notifications from services where you have used the same credentials as DroneCommand, and changing your DroneCommand password whenever a credential reuse risk arises;
• No cross-service breach monitoring: DroneCommand does not subscribe to breach intelligence feeds, does not monitor whether your email address appears in known data breach databases, and does not send you alerts when your credentials may have been exposed through a third-party breach. Our security monitoring is limited to our own systems and infrastructure;
• Unique password and MFA strongly recommended: Using a unique password for DroneCommand — one that is not used on any other service — eliminates credential stuffing risk. We strongly encourage enabling multi-factor authentication (MFA) when available. However, as described in Section 4.6, SMS-based MFA has known vulnerabilities. If you enable any form of MFA, you are responsible for maintaining secure access to your verification method and keeping recovery codes in a secure location;
• We are not liable for any unauthorized account access, spray record alteration, data theft, account modification, subscription charge, or other harm resulting from a credential stuffing attack or other account compromise that exploited credentials you had previously used on another service that was breached, regardless of any security features we have implemented on our platform.

4.9 API Access Tokens and Third-Party Application Integrations

DroneCommand may offer API access, webhook integrations, or connections to third-party software platforms. When you generate an API access token or authorize a third-party application to connect to your DroneCommand account, you are creating a credential that permits that token or application to act on your behalf — reading, writing, or modifying records — without requiring your password for each action. API tokens and third-party application authorizations are functionally equivalent to granting account access, and any action taken by an authorized API token or integrated third-party application is your account action regardless of which software initiated it.

• Token security is your responsibility: API access tokens are secrets. If you store a token in an insecure location — an unencrypted file, a code repository, a shared document, or a location accessible to unauthorized parties — and that token is used to access or alter your DroneCommand data, the access is attributable to your credential mismanagement. We do not monitor how you store tokens or whether token storage is secure;
• Third-party application conduct is not our conduct: If you authorize a third-party farm management application, ERP system, or other software to connect to DroneCommand via API, that application's behavior — including what data it reads, writes, modifies, or deletes — is governed by that application's own terms and the authorization you granted. We are not responsible for errors, data overwrites, deletions, or other actions taken by third-party software you have authorized to access your account;
• Revoke unused tokens promptly: Tokens that are generated and not revoked remain valid until their expiration or until you explicitly revoke them. An unused but valid token is a standing authorization that persists even if the person or system that requested it is no longer part of your business. Best practice: audit and revoke all API tokens that are no longer in active use;
• Data written via API is your data: Records created or modified via API integration are legally your spray records. A spray record created by a third-party application using your API token is not that application's record — it is your record, subject to Iowa record-keeping requirements and all provisions of these Terms governing record accuracy and finalization;
• We are not liable for any data loss, record alteration, unauthorized access, regulatory citation, or other harm arising from API token misuse, third-party application errors, unauthorized API access resulting from token exposure, or any other consequence of API or integration access you authorized or failed to revoke.

4.10 Mobile App vs. Web App — Version Discrepancies and Feature Parity Gaps

DroneCommand may be available through multiple access methods — a web browser interface, a mobile app for iOS or Android, or both — and these versions may not maintain identical feature sets, data synchronization speed, or user interface behavior at all times. Mobile apps require user-initiated updates and are subject to app store review delays that can lag behind web interface updates by days or weeks. If you use different DroneCommand access methods interchangeably — entering some records on the web and others on the mobile app — discrepancies between versions may cause unexpected behavior, including records entered on one platform not immediately appearing on another, features available on one platform not available on the other, or validation rules that differ between platforms.

• Update lag on mobile apps: Mobile app updates require submission to and approval by Apple's App Store or Google's Play Store. During the review period, the mobile app may operate on an older version while the web interface has already received an update. Features, validation rules, required fields, and form behavior may differ between an outdated mobile app and the current web interface during this lag period;
• You are responsible for updating the mobile app: Mobile apps do not self-update unless automatic updates are enabled in your device's app store settings. Operating on an outdated mobile app version is your responsibility. We are not responsible for record-keeping errors or compliance failures arising from use of an outdated mobile app version that lacked current field requirements or validation rules;
• Offline mobile entry and sync conflicts: Some mobile app implementations allow offline record entry that is synced when connectivity is restored. Records entered offline may sync in an order different from the order entered, and sync conflicts may arise if the same record was also modified on the web interface during the offline period. Sync conflict resolution behavior may result in record data loss that is not immediately visible;
• Feature availability parity is not guaranteed: Features available in the web interface may not be available in the mobile app, and vice versa. We do not guarantee feature parity between access methods. If a compliance-critical feature is unavailable in the access method you are using, it is your responsibility to use an access method that provides the required feature;
• We are not liable for any record-keeping error, compliance failure, data loss, or sync conflict arising from differences between DroneCommand's web and mobile interfaces, version update lag, offline entry sync behavior, or your use of an outdated mobile app version.

4.11 Password Reset via Email — Email Account Security Is Your Responsibility

DroneCommand's account recovery process relies on the email address associated with your account. Password reset links are sent to that email address. If your email account is compromised — through phishing, credential stuffing, a security breach at your email provider, or any other method — an attacker with access to your inbox can use the password reset function to gain full control of your DroneCommand account without ever knowing your DroneCommand password. The security of your DroneCommand account is only as strong as the security of the email account associated with it — we cannot protect your DroneCommand account from attackers who have access to your email inbox.

• Email-based account takeover is the most common SaaS attack vector: More cloud software accounts are taken over through compromised email inboxes than through direct password attacks. An attacker with access to your email — whether through phishing, a breached email provider, or a device with an open email session — can reset your DroneCommand password and lock you out of your own account within minutes;
• Secure your email account first: Protecting your DroneCommand account begins with protecting your email account. Use a strong, unique password for your email account. Enable multi-factor authentication on your email account. Review your email account's connected app authorizations and remove any apps you no longer use. These steps protect DroneCommand access by protecting the email account that controls it;
• Recovery email address currency: If the email address associated with your DroneCommand account is from a former employer, a discontinued email provider, or any account you no longer control, you may be permanently locked out of your DroneCommand account if you forget your password and cannot receive a reset link. Keep your account email address current and under your control;
• Shared email addresses: If your DroneCommand account is associated with a shared business email address — one that multiple employees monitor — any person who can access that inbox can initiate a password reset for your DroneCommand account. Shared email addresses provide reduced security for account recovery purposes;
• We are not liable for any unauthorized account access, spray record alteration, data theft, or other harm arising from an attacker's use of the password reset function after gaining access to the email address associated with your DroneCommand account, regardless of how the email account was compromised.

4.12 Account Lockout, Brute Force Protection, and Rate Limiting

DroneCommand implements security measures such as account lockout, login rate limiting, and multi-factor authentication options to reduce the risk of unauthorized access. These security features are provided on an "as-is" basis and do not constitute a service level commitment or guarantee that your account will not be compromised.

• Lockout thresholds: Account lockout policies may not trigger in every attack scenario, including distributed brute force attacks originating from multiple IP addresses, credential stuffing using valid username-password pairs from other breaches, or session token attacks that do not involve the login form;
• Rate limiting gaps: Rate limiting on login attempts and API calls may not cover all endpoint vectors, and sophisticated attackers may circumvent rate limits through distributed infrastructure, delayed retry patterns, or targeting endpoints not subject to throttling;
• MFA not mandatory: Multi-factor authentication is available but may not be required by your account configuration; failure to enable available MFA features is entirely your responsibility;
• Security feature changes: We may modify, disable, or replace security features at any time without notice, and do not represent that any particular security feature will remain available for the duration of your subscription;
• We are not liable for any unauthorized account access, spray record exposure, data manipulation, or other harm arising from the failure of any account lockout, rate limiting, brute force protection, or other security feature to prevent or detect an intrusion into your account.

4.13 SIM Swap, Phone Number Hijacking, and SMS-Based Authentication Vulnerabilities

When DroneCommand uses SMS text messages or phone calls to deliver one-time passcodes or account verification codes, the security of that authentication factor depends entirely on the security of your mobile carrier account and phone number. A SIM swap attack — in which an attacker convinces your mobile carrier to transfer your phone number to a SIM card under their control — can defeat SMS-based two-factor authentication and allow full account access.

• Carrier security not our responsibility: The security practices of your mobile carrier, including its identity verification procedures for SIM changes and number ports, are entirely outside our control and are not our responsibility;
• Phone number portability risk: Number porting to a different carrier can be initiated by an attacker with limited personal information; once ported, all SMS messages and calls to your number are redirected to the attacker's device;
• Authenticator app alternative: Time-based one-time password (TOTP) authenticator apps are more resistant to SIM swap attacks than SMS-based codes; if available, use an authenticator app rather than SMS for two-factor authentication;
• Account recovery vectors: If your account recovery options include SMS verification, a successful SIM swap can allow an attacker to bypass all other security measures and take full control of your account and its records;
• We are not liable for any unauthorized account access, spray record exposure, data theft, or other harm arising from a SIM swap attack, phone number hijacking, or other compromise of the phone number or mobile device associated with your DroneCommand account.

4.14 OAuth, Single Sign-On, and Third-Party Identity Provider Security

If DroneCommand offers or supports sign-in via third-party identity providers (such as Google, Microsoft, or other OAuth-based services), the security of your DroneCommand account becomes partially dependent on the security of your account with that third-party provider. A breach, compromise, or unauthorized access to your identity provider account can result in full access to your DroneCommand account and all records stored therein.

• Identity provider security is your responsibility: The security practices you maintain for your Google, Microsoft, or other identity provider account — including password strength, two-factor authentication, and recovery method security — directly affect your DroneCommand account security;
• Provider security incidents: A security incident at a third-party identity provider affecting your account is entirely outside our control; we cannot prevent or detect unauthorized access to DroneCommand resulting from a compromised identity provider session;
• Session token persistence: OAuth sessions may persist across devices and browsers; failure to revoke active sessions after using a shared device may allow subsequent users of that device to access your DroneCommand account;
• Provider account termination: If your identity provider account is terminated or suspended, your access to DroneCommand via that provider will be affected; you are responsible for maintaining an alternative login method or recovering access through customer support;
• We are not liable for any unauthorized account access, record exposure, data theft, or other harm arising from a compromise of your third-party identity provider account, an unauthorized OAuth session, or the termination of your identity provider account.

5. Free Trial

New Customers may be offered a free trial period of fourteen (14) days with full access to all Service features ("Trial Period"). The Trial Period begins upon account creation.

During the Trial Period:

• No credit card or payment method is required to begin;
• Full access to all features is provided with no functional limitations;
• No charges are incurred during the Trial Period;
• The trial does not automatically convert to a paid subscription — no charges are applied unless you affirmatively select a plan and enter payment information.

After the Trial Period:

• If you have not subscribed, your account automatically transitions to read-only status;
• You may view and export existing data but may not create, edit, or delete records;
• Your data is retained for sixty (60) days from the trial expiration date;
• You may upgrade to a paid subscription at any time during the 60-day retention window to restore full access;
• After 60 days without upgrading, all User Data is permanently deleted and is irrecoverable.

We reserve the right to modify, extend, or discontinue free trial offers at any time without notice. One free trial per legal entity; creating multiple accounts to obtain additional free trials is a violation of these Terms and may result in permanent suspension of all associated accounts.

5.1 Accidental Charge During Trial Period — Automatic Refund Commitment

The free trial is designed to require no payment method and to incur no charges. If, due to a technical error on our part or in our payment processor's systems, you are charged any amount during a documented free trial period (i.e., before your trial expiration date and before you have affirmatively selected a paid subscription plan), that charge is erroneous and you are entitled to a full refund without needing to initiate a formal dispute.

• If you believe you were charged during your free trial period, contact us immediately at [email protected] with subject "Trial Charge Error" — include the charge date, amount, and last four digits of the card charged;
• We will investigate within three (3) business days. If confirmed as a technical error occurring during a valid, undisclosed trial period, we will issue a full refund to your original payment method via Stripe within five (5) business days of confirmation, with no formal dispute process required;
• This refund commitment applies only to charges that occur during an active trial period, before trial expiration, and before you affirmatively selected a paid plan. It does not apply to: charges you authorized by selecting a plan; charges processed after your trial expired; or charges resulting from you adding a payment method and selecting a subscription before the trial ended;
• The trial-period no-charge design is enforced at the Stripe subscription level — our system is not configured to charge trial accounts. A charge during a valid trial period would reflect a Stripe configuration error, and we take responsibility for confirming and correcting it promptly;
• If you cannot reach us and a trial-period charge is your first charge, you have the right under applicable law to dispute the charge as unauthorized through your card issuer — we will not contest a good-faith chargeback for a documented trial-period accidental charge.

6. Subscription Plans and Pricing

DroneCommand is offered on a flat-rate, unlimited-use subscription model. All plans include unlimited users, pilots, spray records, acres, drones, and equipment.

6.1 Available Plans

• Monthly Plan: $249.00 per month. Billed monthly. Cancel anytime; access continues through end of current billing month.
• Annual Plan: $2,499.00 per year (approximately 16% savings vs. monthly). Billed annually in advance.
• 2-Year Plan: $4,499.00 total, billed once every two years (approximately 25% savings vs. monthly).
• 4-Year Plan: $5,999.00 total (approximately 33% savings vs. monthly). IMPORTANT BILLING CLARIFICATION: Despite being labeled the "4-Year Plan," this plan is billed every thirty-six (36) months — that is, once every THREE (3) years, not every four (4) years. The "4-Year" promotional label reflects the approximate value savings compared to paying monthly for four years; it does NOT describe the billing interval. The billing interval is 36 months. This discrepancy between the plan label and the billing interval is a known limitation of our payment processor's maximum subscription period. By selecting this plan, you expressly acknowledge that: (a) you will be charged $5,999.00 every 36 months (not every 48 months); (b) the "4-Year" label is a value comparison label, not a billing period label; and (c) this disclosure was prominently stated before you subscribed. We make this disclosure as prominently as practicable to prevent any misunderstanding. If you are uncertain about the billing interval, contact us at [email protected] before subscribing. The 36-month billing interval, not the "4-Year" label, controls all billing, renewal, and cancellation timing calculations.

6.2 Included Features

All subscription plans include: unlimited users and pilots; unlimited spray records and acreage tracking; GIS-grade field intelligence with DriftWatch and Iowa BeeCheck integration; enterprise inventory management; built-in time tracking and payroll reporting; customer portal and invoicing; Iowa Administrative Code 45.26 compliance tools; weather integration; priority email support; regular feature updates; and all features included in the standard DroneCommand subscription tier and released during the Subscription term at no additional charge.

Scope of "Future Features" Commitment: The commitment to include future features at no additional charge applies to features we add to the standard DroneCommand subscription tier. It does not: (a) prevent us from launching distinctly new products, companion apps, or services as separate offerings with separate pricing; (b) obligate us to maintain or continue any specific existing feature (subject to Section 15.5 and 33.2); (c) prevent us from restructuring how features are organized or accessed within the Service; or (d) create any obligation to add any specific feature you request. If a feature that was previously included in your subscription is discontinued and we do not offer a comparable replacement, that discontinuation may constitute a Material Adverse Change under Section 33.1 entitling qualifying prepaid subscribers to the prorated refund described therein.

6.3 Pricing Changes

We reserve the right to change our pricing at any time. For existing subscribers, price changes will take effect at the next renewal following sixty (60) days' written notice delivered to the email address on file. Price changes do not affect prepaid subscription terms already in progress. If you disagree with a price change, you may cancel your subscription before the price change takes effect and retain access through the end of your prepaid period.

Pricing Display Accuracy — Checkout Is Authoritative: We make commercially reasonable efforts to ensure that pricing displayed on our marketing website and pricing pages is accurate and current. However, if a pricing display error on any page of our website (including promotional pages, blog posts, or cached pages) shows a price different from the price displayed at the checkout/payment screen:

• The price displayed at the checkout/payment confirmation screen at the time you submitted payment is the authoritative price for that transaction. By completing the checkout process, you confirm your acceptance of the price shown at checkout;
• We are not bound by incorrect prices displayed on marketing or informational pages that differ from the checkout price — these are display errors, not offers;
• If you complete checkout and are charged a price you believe differs from what was displayed at the checkout screen itself (not a marketing page), contact us at [email protected] within ten (10) days and we will investigate. If confirmed as our error at the checkout level, we will issue the appropriate refund or credit;
• We are not responsible for prices displayed in third-party reviews, cached copies of our website, search engine results, or any page other than our live checkout screen.

6.4 Taxes and Tax Exemptions

All prices are stated in U.S. dollars (USD) and exclude applicable taxes. Sales tax is automatically calculated and collected at checkout by Stripe Tax based on your billing address and applicable state and local tax law. You are responsible for all applicable taxes on your subscription. We are not responsible for any tax authority disputes, penalties, or assessments related to your tax obligations; consult a tax professional for guidance.

Tax Exemptions: If you believe your subscription is exempt from sales tax (e.g., agricultural exemption, government entity, non-profit), you must: (a) contact us at [email protected] before subscribing; (b) provide a valid, current, executed tax exemption certificate for each applicable state; and (c) receive written confirmation from us that the exemption has been applied to your account. Tax exemptions are not retroactive — we will not refund sales tax already collected and remitted before a valid exemption certificate is received and confirmed. We reserve the right to reject exemption certificates that are incomplete, expired, or not applicable to our service. Tax exemption determinations are made by Stripe Tax based on applicable law; disputes regarding tax exemption eligibility must be directed to the applicable taxing authority. Processing Timeline: Once we receive a valid, complete, and applicable tax exemption certificate, we will process it within three (3) business days and send you written email confirmation. The exemption will apply to any subscription charge processed on or after the date we send written confirmation. We are not liable for tax collected on charges processed before our written confirmation, provided we processed the exemption certificate within three (3) business days of receipt. If you submit a certificate and do not receive confirmation within five (5) business days, contact us at [email protected].

6.5 Single Legal Entity — One Account Per Business; Shared Accounts Between Separate Entities Prohibited

Each DroneCommand account is licensed to a single legal entity — the Customer identified at account registration. A single DroneCommand account may not be shared between or simultaneously used by two or more separate legal entities, even if those entities are commonly owned, affiliated, operate on adjacent properties, or share personnel. Each separate legal entity that uses DroneCommand must have its own account.

• Co-ownership does not merge entities: If two individuals co-own two separate farming operations — one as a family farm corporation and one as a limited liability company — and both operations spray crops, each entity must have its own DroneCommand subscription. Co-ownership of the entities does not permit a single subscription to serve both entities' regulatory records;
• Regulatory record integrity: Iowa Administrative Code Chapter 45.26 spray records are maintained at the licensed applicator entity level. If records from two legally separate entities are commingled in a single DroneCommand account, those records may not satisfy regulatory requirements for either entity. The fact that records were stored in a single account does not make them the records of a single operator if the underlying operations were conducted by separate licensed entities;
• Liability isolation: Commingling two entities' operational records in one account can expose one entity's records to legal process directed at the other entity. Records from Entity A stored in Account XYZ may be produced in litigation against Entity B if Entity B also used Account XYZ. We are not responsible for this exposure and are not a party to disputes about which entity's records belong where when records are commingled;
• Indicia of single entity: If you are uncertain whether your operations constitute one legal entity or two, consult your attorney or accountant. The question of how many entities are using the Service is a legal and accounting question, not one we resolve;
• We reserve the right to require separate subscriptions for entities that we determine are using a single account in violation of this provision, and to suspend accounts where the single-entity requirement cannot be verified.

6.6 Promotional Pricing, Discount Codes, and "Grandfathered" Rates — Not Perpetual Entitlements

We may from time to time offer promotional pricing, limited-time discount codes, early-adopter rates, or launch pricing for new subscribers. Promotional pricing applies only to the subscription term for which it was expressly offered. It does not create a perpetual right to that pricing, a guarantee against future price increases, or any entitlement to the same promotional rate at renewal.

• Renewal at standard rate: When a subscription purchased at a promotional rate renews, it will renew at the then-current standard rate unless we expressly state in writing at the time of the promotional offer that the promotional rate is guaranteed for a specific number of renewal terms. Promotional communications that describe a price without specifying renewal terms do not constitute a perpetual pricing guarantee;
• "Grandfathered" pricing: If we have communicated to you that your specific subscription rate will be "locked in," "grandfathered," or "guaranteed for life" as part of a promotional offer, that commitment is valid for the period specified. If no period was specified, a "grandfathered" rate commitment extends for the current subscription term only unless we provide a durable written guarantee with a specific end date. We honor our explicit written pricing commitments — but verbal representations about "lifetime" pricing from marketing materials or support communications, without a formal written commitment, are subject to Section 69;
• Discount codes are one-time use: Promotional discount codes applied to a subscription are applied to the initial subscription period. They do not carry forward to renewals automatically unless the code was expressly described as a recurring discount at the time of application;
• 60-day pricing change notice applies: Any price change at renewal — including the removal of a promotional rate that was not expressly guaranteed beyond the initial term — is subject to the 60-day advance notice requirement in Section 6.3. You will receive notice before your rate changes and have the opportunity to cancel before the new rate takes effect;
• We are not liable for any expectation of continued promotional pricing based on informal representations that were not reduced to a formal written pricing commitment as described in this Section.

6.9 Subscription Downgrade and Feature Restriction — Data Retention and Access Limitations

Operators may downgrade their subscription to a lower tier at any time. Downgrading may restrict access to features, data views, or export capabilities available on higher tiers — operators are solely responsible for ensuring their regulatory record-keeping obligations are satisfied before restricting their account tier.

• Data retained but access may be restricted: Downgrading to a lower subscription tier may restrict access to features, data views, or export capabilities available on higher tiers — downgraded accounts retain underlying data but may not be able to view, export, or interact with all data until the account is upgraded again;
• Export records before downgrading: Operators who downgrade are solely responsible for ensuring their record-keeping obligations under Iowa Administrative Code Chapter 45.26 and other applicable law are satisfied before restricting their account tier — if regulatory records or compliance features are accessible only on a higher tier, operators should export all required records before completing the downgrade;
• Compliance gaps are operator's responsibility: DroneCommand is not responsible for regulatory compliance gaps arising from an operator's decision to downgrade their subscription to a tier that restricts access to regulatory record features or compliance tools;
• Downgrade is a plan selection, not a service failure: A downgrade that restricts record access or feature availability does not constitute a service failure, service interruption, or breach of these Terms — it is a consequence of the operator's plan selection;
• We are not liable for any enforcement action, record-keeping violation, compliance gap, or other harm arising from inaccessibility of records or features following a subscription downgrade.

7. Payment Processing

All payment processing is performed by Stripe, Inc. By providing payment information, you also agree to Stripe's Terms of Service and Stripe's Privacy Policy.

7.1 Payment Methods

We accept payment via: Visa, Mastercard, American Express, and Discover credit and debit cards; U.S. bank accounts via ACH transfer; and any other payment methods offered at checkout through Stripe.

7.2 Payment Data Security

We do not collect, store, process, or transmit your full credit card numbers, card security codes (CVV/CVC), bank account numbers, or routing numbers. All payment data is transmitted directly to and stored by Stripe, which is a PCI DSS Level 1 Service Provider. We are not responsible for the security of payment data stored by Stripe.

7.3 Authorization

By entering a payment method, you authorize us (through Stripe) to charge the applicable subscription fees on a recurring basis at the frequency of your selected billing cycle, plus any applicable taxes. This authorization remains in effect until you cancel your subscription or update your payment method.

7.4 Receipts and Invoices

You will receive an email receipt for each successful payment. All invoices and billing history are accessible through the Stripe Customer Portal, accessible via your account settings under "Manage Billing." We are not responsible for invoice disputes arising from Stripe's systems; contact Stripe directly for payment dispute resolution.

7.5 Billing Page Display — Informational Only

• The billing and subscription information displayed in the DroneCommand account portal is informational and is derived from your Stripe subscription record. It may not reflect real-time Stripe subscription state due to processing delays, display rendering, or data synchronization timing between Stripe's systems and our application;
• The authoritative record of all charges, subscription terms, and billing history is Stripe's payment processing system, not the DroneCommand billing page display. In any discrepancy between the DroneCommand billing display and Stripe's records, Stripe's records govern;
• Apparent discrepancies between the billing page display and your actual Stripe charges should be resolved by reviewing your Stripe-issued receipts (delivered by email or accessible in the Stripe Customer Portal) or by contacting support at [email protected]. We are not liable for any business decisions made in reliance on billing page display values that differ from actual Stripe charge amounts.

8. Automatic Renewal and Billing

8.1 Preauthorized Recurring Charges — Required Disclosure

PREAUTHORIZED RECURRING CHARGES: By providing a payment method and selecting a subscription plan, you expressly and affirmatively authorize Country Road Drone Services, LLC (processed through Stripe) to initiate recurring preauthorized charges to your payment method at the frequency and amount corresponding to your selected plan, plus any applicable taxes, as follows:

• Monthly Plan: $249.00 (plus tax) charged on the same day of each calendar month;
• Annual Plan: $2,499.00 (plus tax) charged once per year on the anniversary of your first payment date;
• 2-Year Plan: $4,499.00 (plus tax) charged once every two years;
• 4-Year Plan: $5,999.00 (plus tax) charged once every three (3) years (see Section 6.1).

Your authorization to charge your payment method on a recurring basis remains in effect until you cancel your subscription as described in Section 12. You have the right to stop payment of preauthorized recurring transfers by contacting your bank, credit card issuer, or by canceling your subscription through the Stripe Customer Portal before the next scheduled billing date. To cancel recurring charges, follow the cancellation procedure in Section 12.

8.2 Renewal Notice

We will send a reminder email to your account's email address before each renewal charge according to the following schedule, based on plan type:

• Monthly Plan: At least seven (7) days before each monthly renewal;
• Annual Plan ($2,499.00): At least thirty (30) days before each annual renewal;
• 2-Year Plan ($4,499.00): At least thirty (30) days before each 2-year renewal;
• 4-Year Plan / 36-Month Plan ($5,999.00): At least thirty (30) days before each 36-month renewal. Because this plan renews only once every three years, it is especially important that you keep your billing email address current and review your account settings periodically so you are not surprised by the renewal charge after a long period of non-renewal.

Failure to receive a renewal reminder email — including due to email filtering, spam folder routing, changed email address, or email delivery failures — does not relieve you of the obligation to pay renewal fees and does not constitute a basis for a chargeback or refund. It is your sole responsibility to keep your billing email address current and to monitor your account's renewal date in your account settings. The renewal date is always visible in your account settings and the Stripe Customer Portal. For plans renewing after a gap of 1 year or more, we strongly recommend proactively reviewing your renewal date rather than relying solely on our reminder email.

Important — Email Address Alignment: Your DroneCommand account email and the email address associated with your Stripe billing record may be different if you updated one but not the other. Stripe billing notifications (receipts, payment failure notices) are sent by Stripe to the email address stored in Stripe, while DroneCommand renewal reminders are sent to the email stored in your DroneCommand account. If these email addresses differ, you may miss either our renewal reminder or Stripe's payment receipt. You are responsible for ensuring that both your DroneCommand account email (under Account Settings) and your Stripe billing email (accessible via the Stripe Customer Portal → Manage Billing) are current and the same. We are not liable for missed communications caused by a discrepancy between your DroneCommand account email and your Stripe billing email.

You may update your payment method at any time via the Stripe Customer Portal in your account settings.

8.3 Card Account Updater Services

Our payment processor, Stripe, participates in card network account updater programs through which card issuers automatically transmit updated card numbers, expiration dates, and card credentials to Stripe when your physical card is replaced due to loss, theft, expiration, or compromise. By providing a payment method and authorizing recurring charges, you authorize us and Stripe to accept and process updated card credentials received through card network account updater programs without additional notification to you. This means:

• Your subscription may continue to be charged to a replacement card even if you were not aware the card update had been processed;
• We are not liable for subscription charges processed to a replacement card that you did not know had been issued, provided Stripe received those credentials through a legitimate account updater program;
• If you do not wish to allow account updater programs to continue your subscription automatically, you must cancel your subscription before the next renewal date;
• If you believe a charge was processed to a card you did not intend to use, contact us at [email protected] — we will investigate and, if appropriate, process a refund under Section 11;
• To disable account updater participation for your card, contact your card issuer directly — we do not control card issuer participation in account updater programs.

8.4 Service Interruption Resulting from Payment Method Failure — No Operational Liability

If your account is suspended under Section 10 due to a failed payment — whether caused by an expired card, insufficient funds, card cancellation, bank-initiated decline, account updater failure, or any other cause related to your payment method — and that suspension results in your inability to access DroneCommand records or complete operational tasks during any spray window, harvest window, or other time-sensitive period, we are not liable for any operational losses, missed spray contracts, missed revenue, regulatory compliance gaps, or other damages arising from the suspension, regardless of the importance of the timing to your business.

• You are responsible for monitoring your payment method's validity and ensuring it will not expire or be cancelled before your next renewal date;
• The grace period under Section 10 exists to give you time to update your payment method — it does not eliminate the possibility of suspension;
• We recommend maintaining an updated backup payment method in your Stripe Customer Portal, particularly during peak operating seasons (April–October);
• We are not responsible for delays by your bank or card network in processing payment method updates or in transmitting account updater information to Stripe;
• Any claim that our billing system "failed" because Stripe or your card network declined a charge is a claim against your payment provider, not us — we do not control bank or card network decisions.

8.5 ACH Debit Payments — Return Timing and NSF Risk

If you pay via ACH bank debit (directly from a bank account), ACH transactions operate on different timing rules than credit card charges and carry unique risks you should understand:

• Delayed Return Window: Unlike credit card transactions, ACH transactions can be returned (reversed) by your bank for up to two (2) business days after submission for most return reasons, and up to five (5) business days for NSF (non-sufficient funds) returns. This means that an ACH payment that initially appears successful — and that causes Stripe to show your payment as "paid" — may subsequently be reversed by your bank up to five business days later;
• Account Access During Pending ACH Return: DroneCommand activates subscription access upon Stripe's initial notification of ACH payment submission, not upon final settlement. If your ACH payment is subsequently returned, your account will be treated as having a failed payment under Section 10, and the grace period and retry schedule will apply from the date we receive notice of the return. Access granted during the period between submission and return is not a refund-eligible service period for purposes of Section 11;
• NSF Fees and Bank Charges: If your bank returns an ACH debit as NSF, your bank may charge you returned-item fees. We are not responsible for any NSF fees, bank charges, overdraft fees, or other costs charged by your financial institution in connection with a returned ACH transaction;
• Fraudulent ACH Initiations: If someone gains unauthorized access to your bank account credentials and uses them to initiate a fraudulent ACH debit for a DroneCommand subscription, you must report the unauthorized ACH to your bank under EFTA/Regulation E unauthorized debit protections. We are not a party to ACH fraud claims between you and your bank and have no independent ability to prevent ACH fraud at the bank account level;
• ACH Authorization: By selecting ACH debit as your payment method, you provide a written ACH debit authorization as required by Stripe's payment flow and NACHA rules. That authorization, once completed, constitutes a signed written authorization under Regulation E. Retain a copy of your ACH authorization confirmation;
• We recommend using a credit or debit card rather than ACH bank debit if you want real-time payment status certainty, faster dispute rights under TILA, and no exposure to the multi-day ACH return window.

8.6 Email Unsubscribe — Effect on Critical Account Notifications

DroneCommand sends various email communications including: renewal reminder notices, payment failure alerts, security notifications, Terms update notices, and support responses. If you click the "unsubscribe" link in any DroneCommand email, your email preferences in our email delivery system may be updated in ways that affect delivery of critical account notifications — not just marketing emails.

• Email category limitations: Our email delivery system attempts to categorize emails as "transactional" (required for account function) vs. "marketing" (promotional). However, email clients and spam filters may not correctly classify categories, and some unsubscribe actions affect all emails from our domain regardless of category. If you unsubscribe and subsequently miss a renewal reminder, payment failure alert, or security notice, we are not liable for the consequences of that missed communication;
• Your responsibility to stay informed: If you unsubscribe from DroneCommand emails for any reason, you take on sole responsibility for proactively monitoring your account status, renewal dates, and payment status through your account dashboard and the Stripe Customer Portal — do not rely on email as your primary notification mechanism once you've reduced or eliminated email notifications;
• To re-subscribe to critical notices: Contact [email protected] with subject "Re-enable email notifications" to restore email delivery. However, we cannot guarantee immediate restoration of delivery if your email address has been flagged at the email provider level;
• Spam filters and domain-level blocking: If your organization's email security (spam filter, domain block, corporate email gateway) blocks emails from our sending domain, the effect is the same as unsubscribing — you will not receive renewal reminders, payment alerts, or security notices. Configuring your email infrastructure to receive emails from our domain is your responsibility, not ours;
• The obligation to pay renewal charges, comply with these Terms, and maintain account security is not reduced or eliminated by your failure to receive email notifications for any reason, including your own unsubscribe action.

8.7 Chargeback Fraud — Consequences of Initiating Unauthorized Chargebacks

A chargeback — also known as "friendly fraud" — occurs when a subscriber disputes a legitimate charge with their card issuer after knowingly receiving the subscribed service, with the intention of avoiding payment while retaining access benefits or obtaining a refund outside the contractual process. Initiating a chargeback for a charge that you authorized, for a period when you received access to the Service, after the 30-day Money-Back Guarantee period, is a breach of these Terms and may be treated as an attempted fraud.

• Our response to chargebacks: Upon receiving a chargeback notification from Stripe, we will contest any chargeback that: (a) relates to a charge you authorized; (b) covers a period when your account was active and accessible; (c) was not timely disputed through our 30-day Money-Back Guarantee or billing error process; and (d) does not involve a genuinely unauthorized transaction. We maintain records of account activity, access logs, and charge authorizations that we will submit to the card network in the dispute process;
• Account suspension: Upon initiation of a chargeback, we may immediately suspend your account pending resolution of the dispute. Access to DroneCommand records during the dispute period is not guaranteed;
• Recovery of chargeback fees: If a chargeback is determined to be unfounded by the card network — or if the chargeback results in us incurring chargeback processing fees even if we ultimately prevail — we reserve the right to seek recovery of those fees plus the original amount as a breach of contract claim. Stripe may pass through chargeback fees regardless of dispute outcome;
• Reporting: We reserve the right to report fraudulent chargeback activity to Stripe's fraud reporting systems, card networks, and, where applicable, appropriate legal authorities. Repeated fraudulent chargebacks may result in permanent account termination and a bar from future use of the Service;
• These consequences do not apply to: chargebacks initiated in good faith for genuinely unauthorized transactions; chargebacks for verified billing errors; or chargebacks resulting from card issuer error. Our chargeback dispute policy does not override any right you have under EFTA, TILA, or applicable consumer protection law to dispute unauthorized transactions.

9. Trial-to-Paid Conversion

If you select a subscription plan and add a payment method before or at the expiration of your free trial:

• Your first payment will be processed immediately upon plan selection;
• Your Subscription commences on the date of your first payment;
• There is no proration or credit for any portion of the trial period;
• The 30-day money-back guarantee (Section 11) begins on the date of first payment.

Mid-Cycle Plan Upgrades: If you upgrade from a lower-tier plan to a higher-tier plan mid-Billing Cycle, you will receive a prorated credit for the unused portion of the current plan, applied toward the cost of the new plan. Downgrades take effect at the next renewal date.

10. Failed Payments and Grace Period

If a recurring payment fails, we will attempt automatic retries and provide a fourteen (14) day grace period before account suspension.

10.1 Retry Schedule

• Day 1: Payment fails; email notification sent;
• Day 3: First automatic retry; email notification sent;
• Day 5: Second automatic retry; email notification sent;
• Day 7: Third automatic retry; escalating email notification sent;
• Day 14: Final email notification; account suspended if payment not resolved.

10.2 During Grace Period

Your account remains fully active for fourteen (14) days following the initial payment failure. You may resolve the issue at any time by updating your payment method via the Stripe Customer Portal.

10.3 After Grace Period

If the outstanding payment is not resolved within fourteen (14) days, your account will be suspended and placed in read-only mode. Upon suspension: you may view but not create, edit, or delete records; your data is retained for sixty (60) days from the date of suspension; you may reactivate full access at any time by updating your payment method and paying the outstanding balance; after 60 days of continued non-payment, all User Data is permanently deleted.

We are not liable for any losses, missed spray windows, regulatory compliance gaps, or other damages resulting from account suspension due to non-payment.

11. Refunds and Money-Back Guarantee

11.1 30-Day Money-Back Guarantee

All paid subscriptions include a thirty (30) day money-back guarantee beginning on the date of your first payment ("Guarantee Period"). If you are not satisfied with the Service for any reason, you may request a full refund of your subscription fee within the Guarantee Period by emailing us directly at [email protected] with the subject line "Refund Request." We — not Stripe — process refund requests; please contact us directly and do not attempt to initiate a refund through the Stripe Customer Portal without first contacting us. Approved refunds will be returned to your original payment method within five (5) to ten (10) business days via Stripe.

To be eligible, your refund request must be received by us within the 30-day Guarantee Period. The 30-day period runs from your first payment date and is measured by when we receive your written request — not by when processing completes. A request received on day 29 is timely. A request received on day 31 is not eligible, regardless of the reason for the delay. We are not responsible for email delivery failures causing your request to arrive after the Guarantee Period; if you are concerned about timely delivery, use the phone number in Section 49 to confirm receipt before the deadline. The Guarantee Period begins on first payment, not on the expiration of the free trial; the trial period does not count toward or against the Guarantee Period.

11.2 Refund Exclusions

The following are not eligible for refunds:

• Refund requests made after the 30-day Guarantee Period has expired;
• Accounts terminated for violation of these Terms;
• Accounts where fraudulent activity has been detected;
• Taxes collected and remitted on your behalf (Stripe Tax).

11.3 No Prorated Refunds

After the 30-day Guarantee Period, we do not offer prorated refunds for mid-cycle cancellations. Upon cancellation, you retain full access through the end of your current prepaid Billing Cycle, after which your account transitions to read-only and then deletion as described in Section 12.

11.4 Chargebacks

Nothing in these Terms limits your statutory rights under the Electronic Fund Transfer Act (EFTA), Regulation E, Truth in Lending Act (TILA), or any other applicable consumer protection statute to dispute a transaction with your bank or card issuer. Those statutory rights are expressly preserved. However, we ask that you contact us first at [email protected] before initiating a chargeback so we can investigate and resolve the issue directly, which is typically faster than a bank dispute process.

If you initiate a chargeback for a charge that you agree was authorized but dispute on other grounds (e.g., dissatisfaction with the Service) without first contacting us, we reserve the right to suspend your account pending resolution and dispute the chargeback. If your chargeback is ultimately determined by your card issuer to be unfounded, we may: (a) seek recovery of the charged-back amount plus any chargeback processing fees passed through by Stripe; and (b) treat the unfounded chargeback as a breach of these Terms. We will not penalize you for chargebacks that are upheld as valid by your card issuer, for chargebacks arising from genuinely unauthorized transactions, or for exercising rights under EFTA, TILA, or equivalent law.

12. Cancellation

You may cancel your subscription at any time with no cancellation fee. Cancellation can be effected through: your account settings under "Manage Billing" → "Stripe Customer Portal" → "Cancel Subscription"; or by contacting us at [email protected].

12.1 Effect of Cancellation

• Monthly Plans: Access continues through the last day of your current billing month; no further charges;
• Annual and Multi-Year Plans: Access continues through the last day of your prepaid term; no prorated refunds after the 30-day Guarantee Period;
• Auto-renewal is disabled upon cancellation; no future charges;
• Your account transitions to read-only status at the end of the paid period;
• User Data is retained for sixty (60) days after the end of the paid period, during which you may export your data;
• After 60 days, all User Data that is not required to be retained by law is permanently and irreversibly deleted.

12.2 Effective Cancellation — Method Required

Cancellation is effective only when completed through the Stripe Customer Portal (Account Settings → Manage Billing → Cancel Subscription) or when we send you written email confirmation of cancellation in response to your request. Email requests to cancel sent to [email protected] are processed during business hours (Monday–Friday, 8 AM–5 PM Central) and are not self-executing — your subscription is not cancelled until we confirm receipt and process the request, or until you complete cancellation through the Stripe Customer Portal. We will endeavor to send written email confirmation of email cancellation requests within two (2) business days of receipt. If you do not receive written email confirmation within three (3) business days of sending your cancellation request, contact us by phone at (712) 420-0871 to verify receipt. Sending an email requesting cancellation does not immediately stop recurring charges; your subscription continues until we send written email confirmation of cancellation or until you complete cancellation through the Stripe Customer Portal. We are not liable for renewal charges incurred between an unconfirmed email cancellation request and our confirmation. To cancel immediately and receive instant confirmation, use the Stripe Customer Portal.

12.2a Data Export Verification After Cancellation

We strongly recommend that you download and verify the integrity of all exported data before your account is deleted. Specifically: (a) confirm that all exported files open and are readable; (b) verify that spray records and regulatory records are complete and legible; (c) do not cancel your account and rely on an unverified export. Once your account is deleted at the end of the 60-day retention window, we cannot recover, re-export, or certify the integrity of any data — including data that may have been corrupted in the export file itself. We are not liable for losses arising from corrupted, incomplete, or unreadable export files that were not verified before the deletion of your account. If you experience an export error, contact us at [email protected] while your account is still active.

12.2c Charges Incurred During Cancellation Processing Window Are Valid

If you submit a cancellation request by email (rather than through the Stripe Customer Portal) and a renewal charge is processed after your email was sent but before we send our written email confirmation of cancellation, the following applies:

• Any renewal charge processed before we send written email confirmation of your cancellation is a valid authorized charge under the recurring payment authorization you granted under Section 8.1;
• We will use commercially reasonable efforts to cancel your subscription within two (2) business days of receiving your email request, but we cannot guarantee processing before a scheduled renewal that falls within that window;
• If your renewal falls within the two (2) business day processing window and we charge before confirming your cancellation, we will refund the renewal charge if: (a) your email clearly expressed intent to cancel and was received by us; (b) we confirm your email was received before the renewal date; and (c) you contact us within ten (10) days of the charge at [email protected] requesting the refund based on this provision;
• To guarantee your subscription is cancelled before any scheduled renewal, use the Stripe Customer Portal — cancellation through the Portal is immediate and automatic, does not require our manual confirmation, and takes effect the moment you complete the Portal cancellation flow.
• We are not responsible for a renewal charge processed before we could reasonably have processed your email request — email submissions are not self-executing cancellations. If timing is critical, use the Portal.

12.2d Cancellation Proof — Burden of Evidence and Stripe Records

In any dispute about whether a subscription was cancelled before a charge was processed, the following evidentiary rules apply:

• Stripe Customer Portal cancellations: Cancellations completed through the Stripe Customer Portal are automatically recorded by Stripe with a timestamp. The Stripe cancellation record — including the date and time Stripe recorded the cancellation — is the authoritative evidence of Portal cancellations. If you cancelled through the Portal, Stripe's records will confirm it. You bear the burden of demonstrating that a Portal cancellation was completed if you claim a charge was unauthorized post-cancellation;
• Email cancellation requests: You bear the burden of demonstrating that a cancellation email was received by us. Evidence of sending is not evidence of receipt; an email delivery receipt or read receipt is stronger evidence than a sent-folder timestamp. We will rely on our email records to demonstrate whether and when we received your cancellation request;
• Steps to protect yourself: After completing a Portal cancellation, Stripe sends an email confirmation — save that email as evidence of cancellation. After sending an email cancellation request, follow up by phone at (712) 420-0871 to verbally confirm receipt if your renewal date is within 72 hours;
• Disputed charges after claimed cancellation: If you claim a charge was unauthorized because you had already cancelled, the burden is on you to provide evidence of cancellation (Stripe confirmation email, our written email confirmation, or phone confirmation record). Absent such evidence, charges processed by Stripe are presumed authorized under the recurring billing authorization you granted in Section 8.1;
• If Stripe records confirm that your subscription was cancelled before a charge was processed, we will promptly refund the charge. If Stripe records show the subscription was active at the time of the charge, the charge is presumed valid and you must pursue any dispute through the process in Section 11.4.

12.3 Data Export Before Cancellation

We strongly recommend exporting all User Data before or promptly after cancellation. Export tools are available under Settings → Export Data and support PDF, CSV, and Excel formats. We are not responsible for any User Data lost due to your failure to export within the 60-day retention window. Especially for regulatory spray records: export before canceling. Do not assume archived records will be available to you after your account is deleted.

12.4 Advance Notice for Non-Emergency Suspensions

For account suspensions related to Terms violations (not payment failures, not security emergencies, not active fraud investigations), we will use commercially reasonable efforts to provide at least twenty-four (24) hours' advance notice by email before suspending access. During the Iowa growing season (April 1 through October 31), we will use commercially reasonable efforts to provide at least five (5) business days' advance notice for non-emergency, non-fraud suspensions to minimize operational disruption. These notice provisions are not applicable to: payment-related suspensions (which follow the retry schedule in Section 10); security emergencies requiring immediate action; accounts where advance notice would enable the violation to continue or worsen; or situations where a court order or legal process requires immediate action.

13. Account Suspension and Termination

13.1 Suspension by Us

We reserve the right to suspend your account at any time, with or without prior notice, in the following circumstances:

• Non-payment as described in Section 10;
• Violation or suspected violation of these Terms;
• Illegal activity or conduct that exposes us or others to liability;
• Suspected fraud or identity theft;
• Receiving a subpoena, court order, or legal directive requiring account suspension;
• Technical or security emergencies requiring immediate action;
• As required to comply with applicable law.

13.2 Termination by Us

We reserve the right to permanently terminate your account and deny all future access to the Service for: egregious, repeated, or willful violations of these Terms; fraudulent use of the Service; criminal conduct; harassment, abuse, or threats directed at our staff; or any conduct that is harmful to us, other users, or third parties. In the event of termination for cause, no refunds will be issued, and we may pursue any available legal remedies.

Data Access After Termination for Cause: Even in cases of termination for cause — except where termination results from fraud, illegal activity, active security threats, or a court order prohibiting access — we will provide thirty (30) days of read-only account access solely to allow you to export your User Data. This 30-day export window is a binding obligation, not a courtesy. During this period: your read-only access will not be revoked except for the exceptions noted above; we will not delete your data before the 30-day window closes; and the data export features (Settings → Export Data) will remain functional. This provision does not waive any claim we may have against you, does not constitute reinstatement of your account, and does not entitle you to any refund. If you dispute our basis for termination, the dispute shall be resolved under Section 31, and we will maintain read-only access pending resolution unless the termination was for active fraud or illegal activity.

13.2a Definition of "Active Security Threat" and "Fraud or Illegal Activity"

For purposes of the exceptions to the 30-day read-only export window in Section 13.2, the following definitions apply:

• "Active security threat" means a situation where: (a) the terminated account is actively being exploited in an ongoing cyberattack, intrusion, or security incident at the time of termination; (b) a law enforcement court order or legal process issued at the time of termination specifically prohibits restoration of access; or (c) your account is actively being used in real time to harm the platform's infrastructure or other customers. The following do NOT constitute an "active security threat": past violations of these Terms that have already occurred and stopped; your filing of a complaint or dispute about the termination decision; a general belief that you may violate Terms in the future; payment failure; or inability to contact you;
• "Fraud or illegal activity" as an exception to the export window means: (a) circumstances where we have been ordered by a court or law enforcement authority not to grant access; or (b) where granting read-only access would directly enable ongoing, active fraud or illegal activity (not completed past violations). A dispute about whether your conduct constituted a violation of these Terms is not, by itself, a basis for invoking the fraud/illegal activity exception.

If we invoke the "active security threat" or "fraud/illegal activity" exception to deny the 30-day export window, we will document our specific basis in writing upon your written request, unless applicable law prohibits disclosure.

13.3 Termination by You

You may terminate your account at any time by canceling your subscription (Section 12) and requesting account deletion by contacting us at [email protected]. Account deletion removes all User Data subject to our data retention obligations under Section 14.

13.4 Post-Termination Obligations

Sections 14 (Data Retention), 17 (Regulatory Compliance), 22 (Intellectual Property), 25 (Disclaimer of Warranties), 26 (Limitation of Liability), 27 (Indemnification), 31 (Dispute Resolution), 32 (Statute of Limitations), and 34 (General Provisions) survive termination of these Terms.

13.5 Business Dissolution, Bankruptcy, or Cessation of Operations Does Not Auto-Cancel Subscription

The dissolution, winding-up, bankruptcy filing, receivership, or cessation of operations of your business entity does not automatically cancel your DroneCommand subscription or stop recurring charges. Recurring charges to your payment method will continue until the subscription is affirmatively cancelled through the process in Section 12 by a person with actual authority to act on the account.

• Dissolution: Filing articles of dissolution with the Iowa Secretary of State (or equivalent in your state) for your LLC, corporation, or other entity does not notify us of the dissolution or trigger any account action on our part. We have no mechanism to detect business dissolution filings. The subscription continues until cancelled;
• Bankruptcy: The filing of a voluntary bankruptcy petition by you or your business entity does not automatically constitute a cancellation of your DroneCommand subscription. If your subscription is subject to a bankruptcy estate, the bankruptcy trustee has the authority to either assume or reject the subscription contract; until the trustee takes action, recurring charges may continue. You should consult bankruptcy counsel about treatment of SaaS subscriptions in your specific proceeding;
• Automatic Stay: While an automatic stay in bankruptcy proceedings may, depending on the jurisdiction and circumstances, pause collection actions, it does not necessarily mean we are required to continue providing Service without payment. Consult your bankruptcy attorney regarding your specific obligations;
• Payment method remains on file: If your business dissolves but the payment method on file (business credit card, ACH bank account) remains active, we will continue charging it on the renewal schedule until the subscription is cancelled. You are responsible for ensuring a wind-down plan includes cancelling all SaaS subscriptions;
• Regulatory records after dissolution: Even after your business dissolves, Iowa IAC 45.26 may require retention of spray records for the applicable 3-year period. Those obligations run with the individuals who performed the spray operations, not solely with the dissolved entity. Consult legal counsel regarding record-keeping obligations that survive dissolution.

13.6 Business Partner and Co-Owner Account Control Disputes

DroneCommand accounts are registered to a single account holder. If your business has multiple owners, partners, members, or shareholders who dispute who has the right to control the DroneCommand account, we will not adjudicate that dispute. We will honor the instructions of whoever controls the registered account email address and credentials until we receive a final court order establishing rightful control.

• We act on the account of record: Any action taken on the account by whoever currently controls the login credentials — including cancellation, data export, plan changes, adding or removing Authorized Users, or any other account action — is valid from our perspective. We are not liable for account actions taken by a party whose authority is disputed by another co-owner;
• Court order required for contested transfer: We will only override the account holder of record and transfer control to a different party upon receipt of: (a) a final, enforceable court order; (b) a valid partnership dissolution agreement executed by all partners; or (c) another document whose legal authority is unambiguous on its face. We will not evaluate competing factual claims about who is the "real" account owner;
• Data as a strategic asset in partner disputes: The party controlling the account email can export, view, and — for non-immutable records — delete data. You are solely responsible for ensuring account access controls reflect your business's governance structure before a dispute arises, including adding a secondary administrator and documenting account credentials in your entity's governance documents;
• Preserving data for litigation: If you are in a business dispute and believe the other party may tamper with DroneCommand records, contact us at [email protected] immediately. While we cannot restrict account access without valid legal process, we may be able to preserve access logs or assist with a documented litigation hold upon receipt of proper legal documentation;
• We are not liable for any loss or harm arising from account actions taken during a business control dispute, including data deletion, data export to a competitor, subscription cancellation, or any other action taken by a party whose authority was subsequently contested or denied.

13.7 Account Access After Business Dissolution — Winding Up Records Before Deletion Clock Starts

When a business entity that holds a DroneCommand account is dissolved, wound up, or placed into receivership or bankruptcy, the remaining regulatory, legal, and financial obligations associated with the account do not dissolve with the business. The person or persons responsible for winding up the dissolved entity must take affirmative action to cancel the DroneCommand subscription, export required records, and address the account before the deletion clock begins — the account does not self-manage after dissolution.

• Regulatory records belong to the winding-up estate: Iowa IAC 45.26 spray records maintained during the entity's operations are assets of the dissolving business — they may be required to be preserved and available during the retention period that runs from each application date, regardless of whether the business entity continues to exist. The dissolution of the entity does not satisfy the record-keeping obligation; it transfers it to whoever is responsible for completing the wind-down;
• Subscription charges continue during wind-down: Consistent with Section 13.5, recurring charges will continue until the subscription is affirmatively cancelled. During a business wind-down, the person handling affairs must address all recurring subscriptions — including DroneCommand — to prevent unnecessary ongoing charges against the estate or remaining assets;
• Who has authority to act on the account: During wind-down, authority to act on the account follows the legal structure of the dissolution — typically the member manager of an LLC, the authorized officer of a corporation, or the appointed trustee or receiver. We will honor instructions from anyone who can demonstrate authority under the applicable dissolution or insolvency process. If authority is disputed, we apply the same process as Section 13.6;
• Export before account deletion: During the wind-down period, the responsible party must export all records needed for regulatory retention, pending litigation, insurance purposes, or estate administration before the account enters the deletion window under Section 14. The deletion clock does not pause for dissolution proceedings;
• We are not liable for any regulatory citation, loss of business records, estate administration complication, or other consequence arising from the failure of a dissolved entity's wind-up representative to properly manage, cancel, and export records from the DroneCommand account before the applicable deletion window closes.

14. Data Ownership, Export, and Retention

14.1 Your Data Ownership

You retain all right, title, and interest in and to your User Data. We claim no ownership interest in your User Data. Our access to your User Data is solely for the purpose of providing the Service as described in these Terms and our Privacy Policy.

14.2 License to Us

By using the Service, you grant us a limited, non-exclusive, royalty-free, worldwide license to host, store, process, transmit, display, and otherwise use your User Data solely as necessary to provide, maintain, improve, and support the Service. This license terminates when your User Data is deleted in accordance with our retention policy. This license does not authorize the use of your User Data to train, fine-tune, or develop artificial intelligence or machine learning models — that use is separately governed by Section 36 and requires express opt-in consent as defined therein. The phrase "improve the Service" in this license means operational improvement such as debugging, performance optimization, and feature development generally — it does not override the restrictions in Section 36.

14.3 Data Export

You may export your User Data at any time through Settings → Export Data in available formats (PDF, CSV, Excel). We encourage you to maintain your own copies of all critical records. We are not responsible for any losses arising from your reliance solely on the Service as your records system without maintaining independent backups.

14.3a Export Format Compatibility and Portability

We provide data export in PDF, CSV, and Excel (.xlsx) formats. We make no warranty or representation that our export formats are compatible with any third-party software, competing platform, or other import tool. Specifically:

• Export format specifications may change as we update the Service; we will maintain standard, industry-common formats (standard CSV, standard .xlsx) but are not obligated to customize export formats for any specific third-party platform's import requirements;
• We are not responsible for data loss, formatting errors, field mapping errors, or any other issues arising from importing our exports into third-party systems;
• If you are migrating to another platform, verify that your exported data successfully imports into your target platform before canceling your DroneCommand subscription — do not assume compatibility;
• The format of our exports does not reflect any intent to prevent portability — the use of standard CSV and Excel formats is designed to maximize compatibility; any incompatibility is a function of differences in how different platforms structure their import schemas, not intentional obstruction;
• We are not liable for any migration costs, data re-entry costs, or operational disruption arising from format incompatibilities between our exports and any third-party system.

14.3b Export Document Rendering Fidelity — PDF and Printed Output

When you export records in PDF format, the rendered PDF document may differ visually from how those records appear on-screen in the Service. Differences between on-screen display and exported PDF documents are foreseeable and not a defect in your underlying records — they are a function of PDF rendering, font substitution, page layout, and similar technical factors. Specifically:

• Long text fields (notes, descriptions, addresses) may be truncated in PDF exports if the content exceeds the rendered field width — verify that all field content is fully visible in the exported document before submitting it to any party;
• Font rendering, character encoding, and special character display may differ between browsers, operating systems, and PDF viewers;
• Page breaks in multi-page PDF exports may split tables or records in ways that could make them harder to read when printed;
• Column widths in exported reports are optimized for standard U.S. Letter paper and may not render correctly on other paper sizes;
• Before submitting any exported DroneCommand document to a regulatory authority (IDALS, EPA, FAA), insurance adjuster, court, or any other official party, you are responsible for reviewing the exported document in its final rendered form — not just the on-screen version — to confirm that all required fields are present, fully visible, and legible;
• We are not liable for any regulatory citation, insurance claim denial, legal objection, or other adverse outcome arising from a PDF or printed export that was illegible, truncated, formatted incorrectly, or otherwise rejected by a receiving party, where the underlying data in the Service was complete and accurate;
• If you discover a consistent rendering problem in our PDF exports, report it to [email protected] — we will investigate and address it as a bug fix, but pending resolution, you may export in CSV or Excel format and convert to PDF using your own tools to control the formatting.

14.4 Retention Schedule

• Active Accounts: All User Data is retained for the duration of your active subscription;
• Post-Cancellation/Suspension: Non-regulatory User Data is retained for sixty (60) days after cancellation or suspension, then permanently deleted;
• Regulatory Records: Spray application records and related compliance data required to be retained under applicable law (including Iowa Administrative Code Chapter 45.26 and equivalent state statutes) are retained for a minimum of three (3) years, regardless of account status, to the extent required by law. These records are archived and are not accessible to you after your account is deleted; they are maintained solely for legal compliance purposes;
• Payment Records: Transaction history and invoices are retained for seven (7) years for tax and accounting purposes.

14.5 No Liability for Retained Records

The retention of Regulatory Records as described above is performed solely for our own legal compliance purposes and does not constitute an ongoing service, data storage service, or records management service to you. We make no representation that retained records will be accessible, complete, or usable for any purpose, including regulatory audits, after your account is deleted. We are not a records custodian or records management service. Do not cancel your account and assume your records are safe — they are not accessible to you after cancellation and data deletion.

14.6 Regulatory Audit Cooperation

If, after your account has been cancelled and your User Data deleted, you receive a regulatory audit, inspection, or records request from a government authority (such as IDALS, EPA, or FAA) requiring production of records that were stored in DroneCommand, you should: (1) immediately contact us at [email protected] with the regulatory authority's request; and (2) understand that we will cooperate with valid regulatory authority requests to the extent required by law but we cannot guarantee that archived Regulatory Records will be in a format, completeness, or condition sufficient to satisfy any specific regulatory requirement. The provision of archived records to a regulatory authority upon lawful request does not restore your account access, does not create a service relationship, and is at our sole discretion and subject to applicable law. The only reliable way to ensure you have access to your records for regulatory purposes is to export them regularly and maintain independent archives.

14.7 No Guarantee of Suitability as Primary Record System

THE SERVICE IS A TOOL TO ASSIST WITH RECORD-KEEPING AND IS NOT GUARANTEED TO SERVE AS YOUR SOLE OR PRIMARY RECORDS SYSTEM FOR REGULATORY COMPLIANCE PURPOSES. YOU ARE SOLELY RESPONSIBLE FOR ENSURING THAT YOUR RECORDS ARE COMPLETE, ACCURATE, AND MAINTAINED IN A MANNER THAT SATISFIES ALL APPLICABLE REGULATORY REQUIREMENTS. WE STRONGLY RECOMMEND EXPORTING AND INDEPENDENTLY ARCHIVING ALL REGULATORY RECORDS ON A REGULAR BASIS, AND NOT LESS THAN ONCE PER SPRAY SEASON.

14.8 What "Immutable" Spray Records Means

Where our marketing materials, documentation, or the Service itself describe spray records as "immutable," this term has a specific, limited meaning: spray records, once finalized by an Authorized User, cannot be edited, altered, or deleted by any user within the Service during an active subscription. This immutability feature is an audit trail protection designed to prevent after-the-fact alteration of records — it is not a promise of permanent preservation of your records. "Immutable" records are still subject to deletion under the retention schedule in Section 14.4. The "immutable" designation does not mean: (a) records are preserved forever; (b) records will survive account cancellation beyond the 60-day retention window; (c) records have been certified or validated as compliant with any regulatory requirement; or (d) records cannot be deleted by us pursuant to our data retention schedule or legal obligations.

14.9 Exported Records Are Not Immutable — Immutability Is a Platform Protection Only

The immutability protection described in Section 14.8 applies exclusively to spray records within the DroneCommand platform. Once you export records in any format — PDF, CSV, Excel, or any other — those records leave our platform and the immutability protection does not travel with them. Exported records can be edited, altered, or deleted using any standard word processor, spreadsheet application, or PDF editor. We have no control over exported records once they leave the Service.

• Legal Implications of Altered Exports: If you submit an exported DroneCommand record to a regulatory authority, court, insurance company, or any other official party, that party is relying on the document you submit — not on our in-platform records. If someone alters an exported record before submission, the submitted document may not match our records. We are not responsible for the submission of altered exported records by you, your employees, or any party to whom you provided an export;
• Export Authenticity Verification: If a dispute arises about whether an exported document accurately reflects the underlying DroneCommand record, a regulatory authority or court may seek our cooperation in comparing the submitted document against our platform records. We will cooperate with valid legal process for this purpose. However, we cannot proactively monitor how exported documents are used or altered after leaving the platform;
• Chain of Custody for Regulatory Submissions: If you intend to use exported DroneCommand records as regulatory evidence, treat them with chain-of-custody discipline: export directly at the time of submission rather than in advance, do not pass the file through multiple individuals or devices before submission, and retain a separate copy showing the original export date and contents;
• PDF Integrity: DroneCommand-generated PDFs are not cryptographically signed in a tamper-evident way. If you need tamper-evident records for a legal or regulatory purpose requiring cryptographic integrity verification, consult an attorney about appropriate document authentication methods for your specific purpose;
• We are not liable for any regulatory violation, legal consequence, insurance denial, or other harm arising from an exported record that was altered, tampered with, or misrepresented after leaving our platform, regardless of who made the alterations or for what purpose.

15. Service Availability

15.1 Service Availability — No Uptime Warranty

We make commercially reasonable efforts to maintain high availability of the Service. Any uptime figures stated in our marketing materials, product documentation, sales communications, or elsewhere (such as "99.5% uptime" or similar) are aspirational goals only. They do NOT constitute a warranty, service level agreement (SLA), guarantee, contractual commitment, or binding obligation of any kind. No stated availability figure creates any right to service credits, compensation, or damages in the event of downtime, regardless of whether actual availability falls below any stated figure. We do not offer service credits for downtime of any duration. The sole remedy for persistent, severe service unavailability is cancellation under Section 12.

Status Page Metrics Are Historical Displays Only: If we maintain a public status page displaying current or historical uptime metrics, response times, incident logs, or availability percentages, those displays are informational only. Historical uptime data displayed on a status page: (a) does not constitute a warranty or guarantee of future availability; (b) does not create any binding performance commitment; (c) does not establish an implied SLA based on past performance; and (d) does not entitle you to compensation if future availability falls below any historically displayed figure. A status page is a transparency tool, not a contractual promise.

15.2 Scheduled Maintenance

Scheduled maintenance windows will be announced at least forty-eight (48) hours in advance via email and our status page. Maintenance is typically performed during low-usage hours (late night, U.S. Central Time) and during agricultural off-season periods where practicable.

15.3 Unplanned Outages

We will make commercially reasonable efforts to restore service promptly following unplanned outages and will post status updates at our status page. We are not liable for losses arising from unplanned outages.

15.4 No Liability for Downtime

WE ARE NOT LIABLE FOR ANY LOSSES, DAMAGES, MISSED SPRAY WINDOWS, CROP DAMAGE, REGULATORY COMPLIANCE FAILURES, LOST REVENUE, OR ANY OTHER HARM ARISING FROM SERVICE UNAVAILABILITY, DOWNTIME, SLOWNESS, OR ERRORS, WHETHER PLANNED OR UNPLANNED. It is your responsibility to plan operations with appropriate contingencies and not to rely solely on the Service for time-sensitive agricultural operations.

15.4a Account Inaccessibility During Regulatory Inspections, Audits, or Enforcement Actions

CRITICAL — REGULATORY AUDIT RISK: Your DroneCommand account may be inaccessible during a regulatory inspection or audit for any number of reasons, including: account suspension for non-payment (Section 10); account suspension for Terms violation (Section 13); scheduled or unscheduled maintenance; an unplanned service outage; internet connectivity failure at your location; or any other cause. We are not liable for any regulatory inspection failure, citation, fine, penalty, license revocation proceeding, or other adverse regulatory outcome arising from your inability to access your DroneCommand account during a regulatory inspection or audit, regardless of the cause of the inaccessibility.

• You are solely responsible for having independent access to your regulatory spray records outside of the DroneCommand platform — specifically, physically exported copies of your records that do not require live internet access to your account to view;
• Regulatory inspectors are not required to accommodate the unavailability of cloud-based systems; your inability to produce records because an app is unavailable is a compliance failure on your part, not ours;
• We strongly recommend: (a) exporting your regulatory records at least at the end of every spray season and storing them locally or in printed form; (b) not relying exclusively on real-time cloud access to produce records during an inspection; and (c) being prepared to produce records without live internet access;
• If your account is currently suspended due to non-payment and you have an active regulatory inspection, contact us immediately at [email protected] and (712) 420-0871 — while we cannot guarantee immediate restoration of access, we will make commercially reasonable efforts to provide read-only access during a documented active regulatory inspection, provided you can demonstrate the inspection is ongoing and your past-due balance situation is being resolved;
• This Section does not limit your right to seek cancellation under Section 12 if persistent service unavailability makes the Service unusable for its intended purpose.

15.5 Modification of Service

We reserve the right to modify, update, enhance, or discontinue any feature or aspect of the Service at any time, with or without notice. We will use commercially reasonable efforts to provide advance notice of significant changes. We are not liable for any disruption or harm resulting from Service modifications.

15.5a Change Management During Active Spray Season

We recognize that agricultural drone spray operations follow a seasonal pattern with a defined peak operating period (approximately April through October for most Iowa operations). During peak spray season, unexpected changes to core operational workflows are particularly disruptive. We commit to the following change management practices during peak spray season, subject to the exceptions below:

• No Breaking Interface Changes During Peak Season Without Advance Notice: We will use commercially reasonable efforts to avoid deploying changes to core spray-record entry workflows, required field structures, or the primary operational interface during peak spray season (April 1 – October 31) without providing at least fourteen (14) days' written notice to your account email before the change takes effect. This is a commercially reasonable effort commitment, not a warranty or absolute guarantee;
• Exceptions — Security and Legal Compliance: This commitment does not apply to: (a) security patches required to address active vulnerabilities or data security threats, which may be deployed immediately without advance notice; (b) changes required by applicable law, court order, or regulatory requirement that cannot be delayed; (c) emergency fixes to critical bugs that are causing data loss, corruption, or service unavailability;
• What "Breaking Change" Means: For purposes of this Section, a "breaking change" means a modification that: removes a field required by Iowa IAC 45.26 from a spray record form; changes the format of exported regulatory records in a way that makes previously valid records no longer match required formats; or removes access to a feature essential to completing a spray record. Style changes, layout changes, new features, and non-essential workflow improvements are not "breaking changes" under this Section;
• No Right to Compensation: Even if we fail to provide the advance notice described above, this Section does not create any right to compensation, service credits, or damages beyond the cancellation rights in Section 12. Failure to provide advance notice is addressed by offering you the right to cancel rather than by creating monetary damages;
• Nothing in this Section constitutes an SLA, warranty, or guarantee of any specific functionality — our general right to modify the Service under Section 15.5 is not altered by this Section, which addresses notice timing only.

16. Acceptable Use Policy

You agree to use the Service only for lawful purposes and in accordance with these Terms. You agree not to:

• Use the Service for any illegal purpose or in violation of any applicable federal, state, or local law or regulation;
• Falsify, misrepresent, or omit required regulatory records, including spray application records;
• Enter fraudulent, inaccurate, or deliberately misleading data into the Service;
• Attempt to gain unauthorized access to any portion of the Service, any other account, or any system or network connected to the Service;
• Upload, transmit, or introduce malware, viruses, worms, Trojan horses, ransomware, or any other malicious or harmful code;
• Interfere with, disrupt, or impair the integrity or performance of the Service, its servers, or any networks connected to the Service;
• Scrape, data mine, or use automated means to access, collect, or extract data from the Service without our prior written permission;
• Reverse engineer, decompile, disassemble, or otherwise attempt to derive the source code, algorithms, or trade secrets of the Service;
• Reproduce, duplicate, copy, sell, resell, or exploit any portion of the Service without our prior written permission;
• Use the Service to spam, harass, threaten, or abuse other users or third parties;
• Permit any third party to use your account credentials to access the Service without our prior written consent;
• Create multiple accounts to circumvent restrictions, including free trial limitations;
• Use the Service in any manner that could damage, disable, overburden, or impair our infrastructure;
• Use the Service to build a competing product or service or to provide data to any competitor;
• Circumvent any security features, access controls, or authentication mechanisms of the Service;
• Access or use the Service for competitive intelligence purposes — including creating or using an account for the primary purpose of researching our platform's features, capabilities, pricing structure, user interface, or workflows for use in developing, benchmarking, or advising a competing product or service;
• Allow any employee, agent, contractor, investor, or representative of a company that offers a competing agricultural operations management software product to access your account, observe sessions, or review exported data for competitive purposes;
• Claim or assert any verbal, informal, or implied referral fee, affiliate commission, revenue share, or finder's fee arrangement with us unless such arrangement is set forth in a separate signed written agreement executed by a member or manager of Country Road Drone Services, LLC — no employee or contractor of ours has authority to promise compensation arrangements orally or informally.

You also agree not to make any of the following misrepresentations about DroneCommand to your customers, landowners, regulators, or any third party:

• That DroneCommand is "certified," "approved," "endorsed," or "accredited" by IDALS, EPA, FAA, or any other government authority — we have not sought or received certification, approval, or endorsement from any regulatory body;
• That using DroneCommand guarantees, ensures, or certifies regulatory compliance with Iowa IAC 45.26, FIFRA, FAA Part 107, or any other law;
• That DroneCommand records have been reviewed, validated, or certified by us for any regulatory, legal, or insurance purpose;
• That DroneCommand provides any legal, agronomic, or regulatory advice or guidance specific to their situation.

If your customers, landowners, or clients rely on a misrepresentation you made about DroneCommand's certification, approval, or regulatory guarantee status and suffer harm as a result, you are solely responsible for those claims. We are not liable for third-party reliance on false representations about our product that we did not make. You agree to indemnify us for any claim, demand, or regulatory action arising from your misrepresentation of DroneCommand's certification or regulatory approval status to any third party.

Violations of this Acceptable Use Policy may result in immediate account suspension or termination without refund, and may subject you to civil and/or criminal liability. We reserve the right, but are not obligated, to monitor accounts for compliance.

16.1 Free Trial Accounts — Legitimate Evaluation Only

Free trial accounts are offered exclusively for genuine prospective customers to evaluate whether DroneCommand meets their operational needs. Creating a free trial account for any of the following purposes is a violation of these Terms and may result in immediate termination of the trial and permanent prohibition from accessing the Service:

• Competitive Intelligence Research: Creating a trial account for the primary purpose of systematically documenting DroneCommand's features, workflows, pricing structure, data entry forms, UI design, export formats, or any other aspect of the Service for use in designing, marketing, positioning, or advising on a competing product — regardless of whether you also have a genuine evaluation purpose;
• Investor or Acquisition Due Diligence Without Disclosure: Using a trial account to conduct platform due diligence on behalf of a potential acquirer, investor, or strategic partner that competes with us, without prior written disclosure to us of that purpose — contact [email protected] if your evaluation is for due diligence purposes so we can discuss appropriate access arrangements;
• Third-Party Market Research: Using a trial account to generate reports, assessments, feature comparisons, or other market research deliverables for any third party — including agricultural technology consultants, venture capital firms, or industry analysts — where the primary beneficiary of the research is not your own operational evaluation decision;
• Subscription Avoidance Through Cycling: Creating new accounts or new identities to maintain free access without subscribing — prohibited under the "one free trial per legal entity" rule and constituting fraud against us;
• We are not required to prove competitive intent before terminating a trial account — unusual usage patterns, systematic documentation behavior, or a known connection to a competing entity may be grounds for termination at our sole discretion.

16.2 Subcontractor Authorized Users — Their Records Are Your Records

If you add a subcontractor, independent contractor, or third-party operator as an Authorized User under your DroneCommand account, every spray record, job entry, time record, and other data item that person enters is entered under your account and becomes your regulatory and legal record. We do not distinguish between records entered by your employees and records entered by your subcontractors — all records in your account bear your account identity.

• Your regulatory records, your compliance: If a subcontractor enters a spray record under your account that contains inaccurate data — wrong chemical, wrong rate, wrong field, wrong applicator license number — that record is in your regulatory history. Regulators reviewing your records see your account; they do not see whether a particular record was entered by your employee vs. your subcontractor. You bear full regulatory responsibility for all records in your account regardless of who entered them;
• Unlicensed subcontractor spray operations: If you use DroneCommand to log spray operations performed by a subcontractor who lacks the required Iowa commercial pesticide applicator license, those records document unlicensed applications under your account. We are not responsible for any regulatory consequences of subcontractor operations logged in your account;
• Subcontractor access scope: Authorized Users have access to your entire account within the permissions you configure. A subcontractor Authorized User may be able to see your customer list, field coordinates, pricing, and other sensitive business data — not just the jobs you assign to them. You are solely responsible for configuring appropriate permission levels and for any disclosure of business data to a subcontractor through their account access;
• No master subcontractor agreement implied: Adding a subcontractor as an Authorized User does not create any master subcontractor agreement between us and that person. They are accessing DroneCommand as your Authorized User; our relationship is with you, not with them;
• If a subcontractor enters false or fraudulent records in your account, your remedies are against them — not us. We are not liable for records entered by any party you authorized to access your account, regardless of that party's employment or contractor relationship with you.

17. Regulatory Compliance — Your Sole Responsibility

DroneCommand is a software tool designed to assist agricultural drone operators with operational record-keeping and workflow management. The Service is not a compliance management service and does not guarantee that your use of the Service will result in compliance with any applicable law or regulation.

You are solely and exclusively responsible for ensuring your own compliance with all applicable federal, state, and local laws and regulations, including but not limited to:

17.1 Federal Regulations

• Federal Aviation Administration (FAA): You are solely responsible for obtaining and maintaining all required FAA certifications, including Part 107 Remote Pilot Certificates for all drone operators; registering all unmanned aircraft systems (drones) with the FAA; complying with all FAA airspace restrictions, flight altitude limits, and operational rules; obtaining required airspace authorizations (LAANC or waiver) before each flight; and ensuring all pilots under your account hold current, valid FAA certificates;
• Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA): You are solely responsible for applying all pesticides, herbicides, insecticides, and other agricultural chemicals strictly in accordance with the product label, which is the law; complying with all EPA pesticide registration requirements; maintaining required records under FIFRA; and using only EPA-registered products;
• Worker Protection Standard (WPS): Compliance with all EPA Worker Protection Standard requirements applicable to your operations;
• Clean Water Act and Clean Air Act: Compliance with all buffer zone requirements, setback distances from waterways, and restrictions on pesticide application near bodies of water;
• Department of Transportation (DOT): Compliance with any applicable hazardous materials transport regulations applicable to your chemical inventory.

17.2 Iowa State Regulations

• Iowa Administrative Code Chapter 45.26: Maintaining all required spray operation records in the format and detail required by the Iowa Department of Agriculture and Land Stewardship (IDALS); DroneCommand provides tools designed to assist with record-keeping but does not guarantee that records entered through the Service will satisfy every inspector's requirements — you are responsible for verifying completeness and accuracy;
• Iowa Pesticide Applicator License: Obtaining and maintaining a valid Iowa commercial pesticide applicator license in all applicable categories for yourself and any licensed operators under your account;
• Iowa Code Chapter 206 (Iowa Pesticide Act): Full compliance with all provisions;
• Iowa Code Chapter 206A (Groundwater Protection): Compliance with all groundwater protection requirements applicable to pesticide application;
• IDALS Registration: Maintaining current registration with IDALS as required for commercial pesticide application operations.

17.3 Nebraska State Regulations

If operating in Nebraska, you are solely responsible for compliance with all Nebraska Department of Agriculture requirements, including the Nebraska Pesticide Act (Neb. Rev. Stat. § 2-2635 et seq.), Nebraska commercial pesticide applicator licensing, and all related regulations.

17.4 South Dakota State Regulations

If operating in South Dakota, you are solely responsible for compliance with all South Dakota Department of Agriculture and Natural Resources requirements, including all provisions of SDCL Chapter 38-21 (South Dakota Pesticide Act), South Dakota commercial pesticide applicator licensing, and all related regulations.

17.5 Other Jurisdictions

If operating in any jurisdiction other than Iowa, Nebraska, or South Dakota, you are solely responsible for determining and complying with all applicable laws and regulations of that jurisdiction.

17.6 No Legal or Regulatory Advice

NOTHING IN THE SERVICE, THESE TERMS, OR ANY DOCUMENTATION, SUPPORT COMMUNICATIONS, OR MARKETING MATERIALS CONSTITUTES LEGAL, REGULATORY, AGRONOMIC, OR PROFESSIONAL ADVICE. WE MAKE NO REPRESENTATION THAT THE SERVICE WILL SATISFY ANY SPECIFIC REGULATORY REQUIREMENT OR THAT RECORDS CREATED THROUGH THE SERVICE WILL BE DEEMED ADEQUATE BY ANY REGULATORY AUTHORITY. CONSULT A LICENSED ATTORNEY AND THE APPLICABLE REGULATORY AUTHORITY FOR GUIDANCE ON YOUR COMPLIANCE OBLIGATIONS.

17.7 "Iowa IAC 45.26 Compliant" — Tools Only, Not a Compliance Guarantee

Our marketing materials and Service documentation reference Iowa Administrative Code Chapter 45.26 compliance. This means DroneCommand includes record-keeping fields, data structures, and workflows designed to assist with the record-keeping requirements of Iowa IAC 45.26. This does not mean:

• That any records you create through the Service will automatically satisfy the requirements of an IDALS compliance inspection;
• That your use of DroneCommand constitutes compliance with Iowa IAC 45.26 or any other law;
• That we have reviewed, certified, or validated any of your specific records for regulatory compliance;
• That DroneCommand has been approved, endorsed, or certified by IDALS or any other government authority;
• That records exported from DroneCommand will meet the recordkeeping format requirements of any specific inspector or enforcement proceeding;
• That using DroneCommand relieves you of any obligation to independently verify the completeness and accuracy of your regulatory records.

Regulatory compliance — including verifying that records created in DroneCommand satisfy every applicable requirement — remains your sole responsibility. We strongly recommend consulting with a licensed Iowa pesticide applicator compliance specialist and reviewing the current IDALS guidance for Chapter 45.26 compliance.

17.8 Regulatory Changes — No Obligation to Update

Applicable laws and regulations governing drone operations, pesticide application, and record-keeping requirements change over time. We are not obligated to modify the Service in response to any regulatory change, and we make no representation that the Service will remain compliant with regulatory record-keeping requirements as they evolve. Specifically:

• If a regulatory authority adopts new requirements for spray records — such as mandatory digital signatures, cryptographic timestamps, specific file formats, chain-of-custody documentation, or any other requirement not currently part of the Service — you are solely responsible for determining whether DroneCommand records satisfy those requirements;
• If DroneCommand records no longer satisfy applicable regulatory requirements due to a regulatory change, you are responsible for supplementing, converting, or replacing your record-keeping practices accordingly — this may include supplementing DroneCommand with additional documentation or migrating to a different system;
• We will make commercially reasonable efforts to update the Service to track significant regulatory changes affecting our primary market, but we do not warrant that the Service will always be current with all applicable regulatory requirements. "Commercially reasonable efforts" does not mean we will guarantee timely updates for every regulatory change in every jurisdiction;
• You should monitor regulatory guidance from IDALS, EPA, FAA, and other applicable authorities directly and not rely solely on DroneCommand to alert you to regulatory changes.

17.9 Cross-State Operations — Iowa Defaults Are Not Universal Compliance

DroneCommand's record-keeping fields, workflow prompts, compliance reminders, and regulatory guidance are calibrated primarily to Iowa regulatory requirements — specifically Iowa Administrative Code Chapter 45.26 and related Iowa pesticide applicator and commercial drone operator regulations. If you operate in Nebraska, South Dakota, or any other state, the following critical limitations apply:

• Iowa-default record fields, prompts, and compliance tools may not capture all information required by Nebraska or South Dakota regulations for a complete regulatory record — even if a record appears complete within DroneCommand's Iowa-focused workflow;
• Using DroneCommand and following its Iowa-based record-keeping workflow does not guarantee compliance with the specific, potentially different record-keeping requirements of Nebraska, South Dakota, or any other state;
• Nebraska and South Dakota regulatory authorities (Nebraska Department of Agriculture, South Dakota Department of Agriculture and Natural Resources) may have field requirements, record formats, retention periods, or submission requirements that differ from Iowa's requirements — you are solely responsible for verifying and satisfying those state-specific requirements;
• We do not update DroneCommand in real time to reflect regulatory changes in Nebraska or South Dakota — our primary regulatory update focus is Iowa law;
• If you hold a commercial pesticide applicator license in Nebraska or South Dakota, you are responsible for verifying that records you create in DroneCommand satisfy those states' specific requirements before relying on them in any regulatory context in those states. Do not assume Iowa compliance = Nebraska compliance = South Dakota compliance. These are separate regulatory regimes;
• We are not liable for any regulatory citation, fine, license action, or other adverse outcome resulting from records that satisfied Iowa standards but did not satisfy Nebraska, South Dakota, or another state's specific requirements.

17.10 Pilot License, Certificate, and Credential Tracking — Informational Display Only

DroneCommand may allow you to enter and display FAA Part 107 Remote Pilot Certificate numbers, Iowa pesticide applicator license numbers, license expiration dates, and other professional credentials for pilots and staff associated with your account. Any display of credential information in DroneCommand — including expiration dates, license numbers, or certification status — is solely a reflection of the data you entered. We do not verify, validate, or confirm the accuracy of any credential information. Specifically:

• We do not query the FAA's Airmen Inquiry system, IDALS licensing database, or any other official registry to verify that a displayed license number is valid, current, or accurately assigned to the named individual;
• A DroneCommand profile showing a pilot's FAA certificate number and a future expiration date does NOT mean we have confirmed the certificate exists, is active, or belongs to that person — it means you or someone on your team entered those values;
• If a pilot's license is revoked, suspended, or expired and your account still shows it as active, that is because the information in the system reflects what was entered — we have no mechanism to detect real-time changes in license status;
• You are solely responsible for independently verifying that every pilot operating under your account holds a current, valid FAA Part 107 Remote Pilot Certificate and all applicable state pesticide applicator licenses before each flight operation — do not rely on what DroneCommand displays as a substitute for that verification;
• We are not liable for any regulatory violation, enforcement action, insurance denial, or other consequence arising from operations conducted by a pilot whose credentials were displayed in DroneCommand as current but were in fact expired, suspended, revoked, or never validly held.

17.11 No Expiration Alerts — DroneCommand Does Not Notify You When Licenses Expire

DroneCommand may store pilot certificate expiration dates, pesticide applicator license expiration dates, insurance certificate expiration dates, and other credential dates that you or your staff enter. We do not send proactive email alerts, in-app warnings, dashboard notifications, or any other notification when a stored expiration date approaches or passes. If a pilot's FAA Part 107 expires tomorrow and that date is stored in DroneCommand, you will not receive any notice from us.

• Your calendar, your responsibility: You are solely responsible for tracking license expiration dates and ensuring all pilots maintain current credentials at all times. Set your own calendar reminders, operational checklists, or compliance management systems for credential tracking. DroneCommand's storage of an expiration date is a data record, not a compliance monitoring service;
• No liability for expired-license operations: We are not liable for any FAA enforcement action, IDALS action, insurance denial, regulatory citation, or other consequence arising from a flight or spray operation conducted after a pilot's license expired, even if that expiration date was stored and visible in DroneCommand and we did not alert you to it;
• Stale data risk: Expiration dates in DroneCommand are only as current as what was entered. If a license was renewed and the new expiration date was not updated in DroneCommand, the system will show the old date. If a license was revoked after an expiration date was entered, the system has no way to reflect that revocation. Data in DroneCommand is what you put there — nothing more.

17.12 Multi-State Operations — Iowa Compliance Tools Only

DroneCommand's compliance record-keeping tools, field templates, required-field structures, and record format guidance are designed around Iowa Administrative Code Chapter 45.26 as the primary reference regulatory framework. If you conduct commercial drone spray operations in any state other than Iowa — including but not limited to Minnesota, Illinois, Nebraska, Missouri, South Dakota, Wisconsin, or any other state — the record-keeping and licensing requirements in those states may differ materially from Iowa's requirements, and we make no representation that DroneCommand-generated records satisfy those states' requirements.

• No multi-state compliance guarantee: We have not analyzed, engineered, or validated DroneCommand against the pesticide application record-keeping laws of any state other than Iowa. Records that comply with Iowa IAC 45.26 may be missing required fields, using incorrect terminology, or omitting required disclosures under another state's law;
• State licensing: If you operate commercially in another state, that state may require a separate commercial pesticide applicator license in its jurisdiction. DroneCommand does not track multi-state licensing requirements, notify you of out-of-state licensing obligations, or verify that you hold the required license for each state where you operate;
• Your obligation: Before conducting spray operations in any state, you are solely responsible for identifying and complying with that state's pesticide application law, record-keeping requirements, applicator licensing requirements, and reporting obligations. Consult that state's department of agriculture or a compliance attorney familiar with that state's pesticide law;
• If a state regulatory authority cites you for record-keeping violations because your DroneCommand records do not meet that state's specific requirements, that is your compliance failure, not ours. We are not liable for out-of-state regulatory violations arising from reliance on DroneCommand records that were designed for Iowa compliance.

17.13 Time of Application Must Be Accurate — Not the Time You Entered the Record

Iowa Administrative Code Chapter 45.26 and equivalent pesticide record-keeping regulations require that spray records accurately reflect the time the pesticide application actually occurred — not the time the record was entered into the Service. DroneCommand may auto-populate a date/time field with the current system time when you open a new record form. If you are entering a record after the fact, you must manually correct the date and time fields to show when the application actually took place.

• Automatic timestamp ≠ application time: Any auto-populated "created at" timestamp reflects when you opened the form, not when the spray occurred. Failing to correct this creates a record documenting the wrong application time — a potential violation of record-keeping requirements that specify the time of application must be accurate;
• Delayed entry timestamps are internally inconsistent: If you spray a field at 7:00 AM and enter the record at 6:00 PM, the auto-populated time shows 6:00 PM. A regulatory inspector may find this inconsistent with weather records, neighboring observations, or other spray records for the same day. You are solely responsible for this impression;
• Intentional falsification prohibition: While you must enter the accurate actual application time, you must not enter a deliberately false time — for example, a time that predates a regulatory deadline you missed, or a time when conditions appeared more favorable than when the application actually occurred. Entering a deliberately false application time in a regulatory spray record may constitute falsification of official records under applicable pesticide law;
• Why application time matters legally: Application time is material to regulatory compliance — it determines whether you complied with label application windows, restricted-entry intervals, beekeeper notification timing requirements, and label-required weather condition windows. A record showing the wrong time has regulatory consequences regardless of whether the error was intentional;
• We are not liable for any regulatory citation, license action, insurance denial, or other enforcement consequence arising from spray records that show an inaccurate application time because you failed to correct the auto-populated timestamp.

17.14 Restricted-Use Pesticides (RUPs) — Certification Not Tracked or Verified

Certain pesticides are classified by the EPA as Restricted-Use Pesticides (RUPs) because of their potential for unreasonable adverse effects to the environment and to humans when not properly applied. Under FIFRA, RUPs may only be applied by or under the direct supervision of a certified pesticide applicator. DroneCommand does not distinguish between general-use and restricted-use pesticide products, does not track whether you hold the required RUP certification category for each product you document applying, and does not prevent you from creating a spray record for an RUP product regardless of your certification status.

• No RUP classification database: DroneCommand's product inventory and spray record fields accept any product name you enter. We do not cross-reference product names against EPA's RUP list in real time or at any other time. A product entry for an RUP does not trigger any warning, restriction, or certification check within our system;
• No certification category matching: Iowa commercial pesticide applicator licenses are issued with specific category designations. Applying an RUP in a category for which you are not certified is a FIFRA violation regardless of whether you hold a general-category certification. DroneCommand does not store certification category details at a level that would allow it to detect a category mismatch between your license and an RUP product application;
• Regulatory consequence: Applying an RUP without the required certification — or failing to maintain documentation of certification as required by EPA and IDALS — is a FIFRA violation that can result in civil penalties, criminal prosecution, and license revocation. The existence of a DroneCommand spray record documenting the application does not establish that your certification was current or applicable;
• Your verification obligation: Before applying any pesticide, you are responsible for: (a) determining whether the product is classified as an RUP; (b) confirming that your Iowa commercial pesticide applicator certification covers the applicable category; (c) ensuring all applicable supervisory requirements are met if the applicator is not certified; and (d) maintaining the required RUP purchase and use records independently from DroneCommand if required by your state's RUP recordkeeping regulations;
• We are not liable for any regulatory citation, license action, civil penalty, criminal prosecution, or other consequence arising from RUP applications documented in DroneCommand where the applicator lacked the required certification.

17.15 Pesticide Label Updates — Product Data Stored in DroneCommand May Not Reflect Current Registered Label

Pesticide product registrations are maintained by the EPA and state lead agencies. Registered product labels are legally binding documents that govern how a pesticide may be used. Labels are amended, supplemented, and replaced by registrants over time — and DroneCommand has no mechanism to detect, incorporate, or alert you to label changes for products you have stored in your inventory or referenced in historical spray records.

• Product data you entered may be stale: If you entered a product's application rate, REI, or other parameters into DroneCommand based on a label you reviewed at some prior time, and that label has since been amended to reduce or change those parameters, DroneCommand will continue to display the values you entered — which may no longer be consistent with the current legal label. We do not maintain a live connection to EPA's pesticide registration database;
• Label supersession: When a new label version is approved by EPA for a registered pesticide, the new label supersedes the old one. Applications made after the effective date of a new label must comply with the new label's conditions, not the prior version. DroneCommand records referencing conditions from a superseded label may document a non-compliant application if the conditions changed between the label you used and the current registered label;
• Emergency Exemptions and Special Local Needs registrations: EPA and state agencies may authorize the use of pesticides under Emergency Exemptions (Section 18) or Special Local Needs (Section 24(c)) registrations, which may have different conditions than the standard label. DroneCommand does not track or display these special use authorizations. You are responsible for verifying that your application complies with the specific registration under which you are operating;
• Your obligation to verify current label before each application: Before applying any pesticide, you are legally required to comply with the current registered label. You must review the current label — not rely on what was entered in DroneCommand at some prior time — before each application. The current registered label is available from the product manufacturer, your distributor, and EPA's pesticide registration database;
• We are not liable for any regulatory citation, crop damage, environmental harm, personal injury, or other consequence arising from your reliance on product data stored in DroneCommand that did not accurately reflect the current registered pesticide label at the time of application.

17.16 License Revocation Mid-Cycle — DroneCommand Does Not Receive Revocation Notices

State pesticide regulatory authorities (such as Iowa IDALS) may revoke, suspend, or restrict a commercial pesticide applicator license at any time during the license period — not only at renewal. Similarly, the FAA may take enforcement action against a Remote Pilot Certificate between biennial renewal dates. DroneCommand has no connection to IDALS, the FAA, or any other licensing authority's live database and does not receive notification when a license is revoked, suspended, modified, or restricted.

• No real-time license status: If a pilot's license is revoked tomorrow, your DroneCommand profile for that pilot will continue to show the license number and expiration date that were entered when their credentials were originally recorded — because we have no mechanism to receive or reflect real-time license changes. The profile will appear "current" in DroneCommand regardless of actual license status;
• Mid-cycle enforcement actions: Regulatory enforcement actions that revoke or restrict a license mid-cycle typically arise from: pesticide misuse complaints, inspection violations, criminal convictions, fraud, failure to pay civil penalties, or other license-affecting conduct. These events can occur at any time — the two-year or other multi-year license period does not immunize a license from revocation during that period;
• Continued operations after revocation: If a pilot operates under your account after their license is revoked — because you were not aware of the revocation and DroneCommand showed no indication of it — any operations conducted during that post-revocation period may constitute unlicensed commercial pesticide application. The penalties for employing or directing an unlicensed applicator can fall on you as the account holder and business operator;
• Your obligation to verify: You are solely responsible for independently verifying the current license status of all pilots operating under your account before each operating season and, for high-volume operations, more frequently. IDALS maintains a public license lookup tool. Do not rely on DroneCommand's display as a substitute for direct IDALS verification;
• We are not liable for any regulatory citation, enforcement action, license proceeding, civil penalty, or other consequence arising from spray operations conducted by an individual whose license was revoked, suspended, or restricted during a period when DroneCommand showed their credentials as current.

17.17 Drone Airframe Modifications and Weight Class Compliance

The FAA classifies unmanned aircraft systems (drones) by weight for registration and operational purposes. Adding components to a drone — such as spray tanks, pumps, GPS modules, signal repeaters, or larger battery packs — increases the aircraft's all-up weight and may change its FAA weight class, trigger registration requirements, affect its Part 107 operational limitations, or affect the scope of your liability insurance coverage. DroneCommand does not calculate, track, or validate the current all-up weight of any aircraft registered in your account, and does not alert you when component additions may have changed your aircraft's regulatory weight classification.

• Registration thresholds: FAA requires registration of unmanned aircraft weighing between 0.55 lbs and 55 lbs (0.25 kg and 25 kg) for recreational and commercial operations. Adding components may push an aircraft over the 0.55 lb threshold requiring registration, or over the 55 lb threshold where different regulatory requirements apply. DroneCommand equipment records reflect what you enter — not calculated maximum takeoff weight;
• Part 107 operational limits: FAA Part 107 limits small UAS operations (under 55 lbs). Aircraft modifications that cause an aircraft to exceed 55 lbs at maximum takeoff weight may require a waiver or a different regulatory pathway. DroneCommand does not calculate whether a modification brings your aircraft outside Part 107's weight limit;
• Insurance implications: Your aviation liability insurance policy may be issued for a specifically described aircraft configuration at a specific weight. Material modifications that increase all-up weight, add spray equipment, or change the aircraft's function may constitute a material change that requires your insurer to be notified. An insurance claim involving an undisclosed material aircraft modification may be denied. We are not your insurance advisor;
• Manufacturer certification and airworthiness: Modifications that deviate from manufacturer specifications may void manufacturer warranties and affect the airworthiness of the aircraft. We are not responsible for determining whether any modification to an aircraft registered in DroneCommand is within manufacturer specifications or FAA-compliant;
• We are not liable for any FAA enforcement action, insurance denial, accident, injury, property damage, or other consequence arising from aircraft modifications that changed weight classification, operational limitations, or insurance coverage in ways that DroneCommand did not detect or alert you about.

17.18 Local Noise Ordinances and Nuisance Law — Not Our Compliance Problem

Agricultural drone spraying operations generate significant noise — electric motors, spinning propellers, pump systems, and low-altitude flight all contribute to noise levels that neighbors, residents, and local governments may find objectionable. Local counties, cities, and townships in Iowa increasingly regulate drone noise through nuisance ordinances, time-of-day restrictions, and decibel limits that interact unpredictably with Iowa's general agricultural noise exemptions. DroneCommand does not screen spray plans against local noise ordinances, provide curfew or quiet-hour information, calculate decibel levels, or alert you when a planned operation may violate a local nuisance law or conflict with an agricultural exemption's time limits.

• Agricultural noise exemptions have limits: Many state agricultural noise exemptions — including Iowa Code provisions governing normal farm operations — have specific time windows, equipment type limits, or decibel thresholds. Operating outside those windows (before sunrise, after 10 PM, or on noise-complaint holidays in certain municipalities) may not be covered by the agricultural exemption and may expose you to civil nuisance claims or municipal code violations;
• Local ordinances vary by jurisdiction: County, city, and township nuisance ordinances vary significantly across Iowa and are not centrally published or machine-readable. We do not maintain a database of local noise ordinances, and we do not have the ability to alert you when your spray area falls within a jurisdiction with particular noise restrictions or drone-specific use regulations;
• Neighbor relations and nuisance litigation: Drone spray operations near residences, livestock operations, wedding venues, golf courses, campgrounds, or other noise-sensitive properties create a realistic risk of nuisance claims under Iowa common law, regardless of whether the operation falls within an agricultural noise exemption. We are not responsible for mediating neighbor disputes, providing noise modeling, or advising you on your civil nuisance exposure under Iowa law;
• Sensitive location proximity: Operating agricultural drones within audible range of schools during class hours, churches during services, or outdoor community events may generate complaints, adverse publicity, or civil claims that are not precluded by any agricultural exemption. You are responsible for assessing proximity to noise-sensitive locations before each operation;
• We are not liable for any nuisance claim, noise ordinance violation, municipal citation, neighbor dispute, civil litigation, or reputational harm arising from the noise generated by drone operations recorded, planned, or scheduled in DroneCommand, regardless of whether a spray operation appears compliant with the boundaries and timing reflected in the Service.

17.19 Endangered Species Act Compliance — Not Evaluated by DroneCommand

The federal Endangered Species Act (ESA) prohibits the "take" of any species listed as endangered or threatened, including harm through habitat modification, direct poisoning, and indirect exposure through spray drift or chemical contamination of habitat. EPA increasingly conditions pesticide registrations on compliance with ESA consultation requirements and imposes mitigation measures applicable to specific geographic areas where listed species habitat exists — these mitigation measures are part of the product label and binding under FIFRA. DroneCommand does not maintain data on the locations of ESA-listed species, their designated critical habitat, or EPA's geographic pesticide mitigation areas — it does not screen spray plans against ESA-protected areas, and does not alert you when a planned application may violate ESA take prohibitions or label-imposed ESA mitigation requirements.

• Endangered species distribution is not mapped in DroneCommand: The U.S. Fish & Wildlife Service (USFWS) publishes ESA critical habitat designations through the Information for Planning and Consultation (IPaC) mapping tool and in the Code of Federal Regulations. These designations are not integrated into DroneCommand. You are responsible for consulting USFWS and EPA resources to determine whether ESA-listed species or critical habitat is present in or near your planned spray areas before conducting each application;
• EPA label ESA mitigation measures: Many pesticide product labels now include ESA mitigation measures — specific buffer zones, application rate limits, timing restrictions, or geographic area restrictions tied to listed species protection. These mitigation measures are part of the registered label and are legally binding under FIFRA independently of any ESA analysis you may or may not have conducted. DroneCommand does not display or enforce label ESA mitigation requirements;
• Iowa ESA context: Iowa has a number of ESA-listed species including the Iowa Pleistocene Snail, northern long-eared bat, Higgins eye pearlymussel, and pallid sturgeon that occupy habitats in or near agricultural areas. Pesticide applications near cave systems, cold springs, river corridors, and native habitat remnants may implicate listed species. You are responsible for knowing what listed species may be present in your operational area and what mitigation measures apply;
• Federal enforcement consequences are severe: ESA violations carry significant federal enforcement consequences including criminal penalties of up to $50,000 per violation and one year imprisonment, civil fines, and injunctive relief from federal courts. The fact that you used DroneCommand to record the application does not create any ESA defense or compliance presumption;
• We are not liable for any ESA violation, USFWS enforcement action, EPA stop-use order, civil penalty, criminal prosecution, or other consequence arising from a pesticide application that harmed or took an ESA-listed species or damaged designated critical habitat in an area that was not identified, flagged, or excluded by DroneCommand's mapping or record-keeping features.

17.20 LAANC Authorization and Temporary Flight Restrictions — Real-Time Airspace Status Not Checked

FAA Part 107 commercial drone operations in controlled airspace require authorization before flight. The Low Altitude Authorization and Notification Capability (LAANC) system allows operators to obtain near-real-time authorization for operations in certain controlled airspace at or below specific altitudes. Temporary Flight Restrictions (TFRs) — issued for events, wildfires, presidential movements, disasters, and other reasons — prohibit drone operations in defined airspace windows regardless of LAANC status and can be issued with very little advance notice. DroneCommand does not display current LAANC authorization grids, real-time TFR boundaries, NOTAM-based flight restriction data, or any other dynamic airspace information that changes between when you plan an operation and when you fly it.

• LAANC grids change and are time-limited: LAANC authorization for a specific location and altitude may be available one day and unavailable the next, depending on facility-level adjustments by the relevant TRACON or tower. Authorization obtained through LAANC for a prior flight does not authorize a subsequent flight at the same location. Each flight in controlled airspace requires its own authorization. DroneCommand spray records do not record, confirm, or verify LAANC authorization status for any flight;
• TFRs can appear overnight: TFRs are issued continuously by FAA in response to dynamic events. A spray field that was in completely unrestricted airspace when you scheduled an operation may be under a TFR the morning you arrive to fly. DroneCommand has no real-time TFR data feed and will not alert you to a TFR issued after your operation was scheduled. You must check the FAA's official TFR map at tfr.faa.gov before each flight, regardless of what DroneCommand shows;
• FAA enforcement consequences: Flying in a TFR without authorization is a serious FAA violation that can result in certificate suspension or revocation, civil penalties up to $32,666 per violation, and in some cases criminal prosecution. The existence of a DroneCommand spray record for the flight does not constitute evidence of airspace authorization and provides no defense to an FAA enforcement action;
• Use dedicated preflight airspace tools: FAA-approved preflight airspace planning apps — including the B4UFLY app, ArcGIS, Kittyhawk, or the FAA's own DroneZone — are the appropriate tools for verifying airspace status before flight. DroneCommand is a spray record and operations management platform, not an airspace planning tool;
• We are not liable for any FAA enforcement action, certificate action, civil penalty, criminal prosecution, airspace incursion consequence, or other harm arising from flight in a TFR, controlled airspace without authorization, or other restricted airspace that was not displayed, flagged, or blocked by DroneCommand.

17.21 Night Operations, Visual Line of Sight Waivers, and Remote ID — Waiver Status Not Tracked

FAA Part 107 imposes several operational restrictions on commercial UAS operations that require FAA waivers or remote pilot certificates for specific operations — including flight at night (civil twilight to civil twilight), flight beyond visual line of sight (BVLOS), operations over people, and operations from a moving vehicle. Remote ID, which became required for most commercial UAS, mandates broadcast of identification and location information during flight. DroneCommand does not track whether you hold valid Part 107 waivers for non-standard operations, does not verify Remote ID compliance, and does not restrict you from recording operations that would require waivered authority you may not possess.

• Night operations without a waiver: Prior to the 2021 FAA rule change, night operations required a Part 107 waiver. Under current Part 107 rules, night operations are permitted with anti-collision lighting — but operations conducted without the required lighting remain violations. DroneCommand does not require you to confirm anti-collision lighting when recording a night operation, and does not alert you to nighttime operational requirements;
• Waiver expiration not tracked: Part 107 waivers are issued for specific operations, locations, and time periods and expire on a stated date. An operator who holds a waiver for a specific location may conduct a subsequent operation at the same location after the waiver expires — believing the waiver is still valid — and record that operation in DroneCommand without any indication that waiver authority has lapsed. DroneCommand does not store, track, or validate Part 107 waiver status or expiration dates;
• Remote ID compliance: FAA Remote ID rules require most commercially operated UAS to broadcast identification and location data during flight. Operating a drone without functioning Remote ID when it is required — or operating under a Remote ID declaration of compliance that has lapsed — is an FAA violation. DroneCommand does not verify Remote ID compliance for any aircraft registered in your account;
• BVLOS operations: Beyond Visual Line of Sight operations require explicit FAA waiver authority. Recording a BVLOS spray operation in DroneCommand without a valid BVLOS waiver documents a regulatory violation in your own records. DroneCommand does not require BVLOS waiver confirmation before allowing you to create a spray record for a long-distance operation;
• We are not liable for any FAA enforcement action, certificate suspension, civil penalty, or other consequence arising from an operation recorded in DroneCommand that required Part 107 waiver authority you did not possess, Remote ID compliance you did not have, or any other operational authorization requirement that we did not verify or enforce.

17.22 Part 107 Remote Pilot Certificate Expiration — Not Tracked by DroneCommand

FAA Part 107 Remote Pilot Certificates are valid for 24 calendar months from the month of issuance. Recurrent knowledge testing or an online training course must be completed before expiration to maintain certificate currency. Commercial drone operations conducted after a Part 107 certificate has expired are illegal under FAA regulations, regardless of whether the pilot was unaware of the expiration. DroneCommand does not store your Part 107 Remote Pilot Certificate number, expiration date, or currency status, and does not alert you when your certificate is approaching expiration or has expired — it records operations you report without verifying that you held a current, valid certificate at the time of each recorded flight.

• Expired certificate means illegal commercial operation: Every commercial drone spray operation must be conducted by or under the direct supervision of a person holding a current, valid Part 107 Remote Pilot Certificate. A spray record in DroneCommand for an operation conducted after certificate expiration documents an illegal commercial flight regardless of the operator's intent or awareness;
• Certificate currency vs. certificate possession: Holding a Part 107 certificate does not mean the certificate is current. A certificate issued 26 months ago that has not been renewed is expired. DroneCommand's aircraft registration and applicator fields accept whatever you enter — we do not validate certificate currency against FAA airman records;
• FAA enforcement consequences: Operating as a commercial remote pilot with an expired Part 107 certificate is a regulatory violation that can result in civil penalties and, in egregious cases, more serious consequences. The fact that the operation was recorded in DroneCommand does not provide any evidence that the certificate was current — it only proves the operation was logged;
• Monitor your own certificate expiration: FAA sends expiration reminders to the address on file with FAA's Integrated Airman Certification and Rating Application (IACRA) system. You are responsible for monitoring your certificate currency, scheduling recurrent testing before expiration, and maintaining a current, valid certificate for every commercial operation you conduct;
• We are not liable for any FAA enforcement action, civil penalty, certificate action, or other consequence arising from commercial drone operations conducted after your Part 107 Remote Pilot Certificate expired, where the expiration was not tracked, flagged, or disclosed by DroneCommand.

17.23 Hull Insurance vs. Liability Insurance — Coverage Structure Not Assessed

Commercial drone operators typically carry both hull insurance covering physical damage to the aircraft and third-party liability insurance covering bodily injury and property damage to others. DroneCommand does not evaluate your insurance program, assess whether your coverage is appropriate for your operations, or verify that any certificate of insurance on file reflects your actual policy terms.

• Hull vs. liability distinction: Hull coverage and liability coverage are separate policies or endorsements with separate deductibles, limits, and exclusions; a gap in one does not mean coverage exists under the other;
• Coverage exclusions not reviewed: Common exclusions such as operations below minimum altitude, operations without required waivers, use of modified aircraft, or operations in excluded geographic areas are not evaluated by DroneCommand;
• Certificate of insurance currency: A certificate of insurance uploaded or referenced in DroneCommand may have expired or been cancelled without our knowledge, and we do not verify or monitor policy status;
• Subrogation risk: Your insurer may subrogate against third parties involved in a loss; DroneCommand records may be requested in subrogation proceedings without your involvement;
• We are not liable for any uninsured loss, denied claim, coverage gap, subrogation action, or other insurance-related consequence arising from your failure to maintain appropriate hull and liability insurance for your drone operations, regardless of what insurance information you have entered into DroneCommand.

17.24 Drone Operator Fatigue, Consecutive Flight Days, and Human Factors Not Monitored

Drone operator fatigue is a recognized aviation safety factor that can impair judgment, reaction time, and situational awareness during flight operations. DroneCommand does not track operator hours flown, consecutive days of operation, time since last rest period, or any other fatigue indicator, and does not provide warnings when an operator may be flying while fatigued.

• No flight hour tracking: DroneCommand records spray applications but does not track cumulative flight hours per operator per day or per week; fatigue risk assessment based on flight hours is entirely your responsibility;
• FAA fatigue guidance: Although Part 107 does not impose mandatory rest requirements equivalent to manned aviation rules, FAA guidance acknowledges that fatigue impairs performance and that remote pilots must ensure they are physically and mentally fit for operations;
• Consecutive day operations: Peak spray season may involve consecutive days of early-morning or late-evening operations; DroneCommand does not flag when an operator's scheduling pattern creates elevated fatigue risk;
• Incident investigation: In the event of an incident, investigation may examine operator scheduling and fatigue; DroneCommand flight records may be used as evidence of operational tempo but do not contain fatigue assessments;
• We are not liable for any drone incident, property damage, personal injury, FAA enforcement action, or other consequence arising from drone operations conducted by a fatigued operator, regardless of whether the operations were recorded in DroneCommand.

17.25 Airspace Authorization Grid Cell Changes, LAANS Expiration, and UAS Facility Map Updates

Low Altitude Authorization and Notification Capability (LAANC) authorizations are grid-cell-specific, altitude-limited, and time-limited approvals that may expire, be revoked, or become invalid if underlying UAS Facility Map (UASFM) data changes after the authorization is granted. DroneCommand does not monitor the status of your LAANC authorizations after they are issued, does not notify you when an authorization expires or is revoked, and does not alert you when UASFM grid cell maximum altitudes change.

• LAANC authorization expiration: LAANC authorizations are time-limited; operating in controlled airspace after a LAANC authorization expires constitutes an unauthorized airspace incursion regardless of whether you originally held a valid authorization;
• UASFM grid cell changes: The FAA periodically updates UASFM data, which can reduce maximum authorized altitudes in grid cells previously authorized for higher operations; DroneCommand does not track these changes or notify you when they affect areas where you have operated;
• TFR conflicts with existing LAANC: A Temporary Flight Restriction issued after a LAANC authorization was granted supersedes the LAANC authorization; DroneCommand does not monitor for TFRs issued after you received a prior authorization;
• Part 107 waiver geographic limitations: FAA waivers authorizing operations beyond standard Part 107 limitations are geographically and temporally specific; DroneCommand does not store or monitor waiver validity;
• We are not liable for any FAA enforcement action, airspace incursion, civil penalty, or other consequence arising from operating in controlled airspace after a LAANC authorization expired, after UASFM data changed, or after a TFR was issued, regardless of whether the operation was recorded in DroneCommand.

18. Agricultural Operations Disclaimer

DroneCommand is an operations management and record-keeping software platform. It is not an agronomic advisory service, crop protection consultant, or certified precision agriculture provider. The following disclaimers apply to all agricultural-related use of the Service:

18.1 Operational Decisions

ALL OPERATIONAL DECISIONS — INCLUDING BUT NOT LIMITED TO WHETHER, WHEN, WHERE, AND HOW TO APPLY PESTICIDES, HERBICIDES, FERTILIZERS, OR ANY OTHER AGRICULTURAL CHEMICALS — ARE MADE SOLELY BY YOU. The Service provides tools to record and manage operations; it does not direct, recommend, or approve any specific agricultural operation. We are not responsible for any operational decision made with or without reference to information contained in the Service.

18.2 Crop Damage and Loss

WE ARE NOT LIABLE FOR ANY CROP DAMAGE, CROP LOSS, CROP FAILURE, YIELD REDUCTION, OR ANY OTHER AGRICULTURAL HARM ARISING FROM:

• Your use of information or records from the Service;
• Application of chemicals at rates suggested, calculated, or recorded in the Service;
• Timing of applications based on weather data or information available through the Service;
• Reliance on field boundaries, acreage calculations, or other Geospatial Data from the Service;
• Service unavailability, data errors, or system failures occurring during or prior to application operations;
• Inaccurate, incomplete, or missing records in the Service due to user error, data entry mistakes, or system issues.

18.3 Chemical Drift and Environmental Liability

You are solely responsible for all consequences of chemical drift, off-target application, and environmental contamination arising from your drone spray operations, regardless of whether DriftWatch, Iowa BeeCheck, weather data, or any other information or tool available through the Service was consulted. The Service's DriftWatch and beekeeping registry integrations are informational tools only and do not substitute for your independent pre-application scouting, neighbor notification, and compliance with all applicable buffer zone and notification requirements. We are not liable for any claims by neighboring landowners, beekeepers, wildlife agencies, environmental regulators, or any other third party arising from your spray operations.

18.4 Weather Data

Weather data integrated into the Service is provided by third-party providers and is for informational and planning purposes only. Weather data may be inaccurate, delayed, or unavailable. You are solely responsible for observing actual field conditions before and during any spray operation and for making all spray/no-spray decisions. We are not liable for any losses arising from inaccurate or unavailable weather data.

18.4a Weather Display as Spray Decision Basis — Specific Disclaimer

IMPORTANT: Weather data displayed in DroneCommand — including on the dedicated Weather Lookup page and in all other weather display contexts within the Service — including current conditions, forecasts, wind speed/direction, temperature, humidity, dew point, inversion indicators, and any visual indicators suggesting conditions are "favorable," "acceptable," or appropriate for spraying — is sourced from third-party meteorological providers and has the following critical limitations:

• Displayed conditions may not reflect actual conditions at your specific spray site. Weather stations and forecast models use data from measurement points that may be miles from your field; microclimatic conditions (localized inversions, terrain effects, field-level wind patterns) may differ substantially from what any model shows;
• Weather conditions can change rapidly. A display showing favorable conditions at the time you plan a job is not a guarantee or representation that conditions will remain favorable during the entire application window — conditions may change between when you check the app and when you complete the spray;
• Any "favorable," "acceptable," or similar indicator in DroneCommand is a data display, not advice. We are not agronomists, licensed pesticide advisors, or meteorologists. No display in DroneCommand constitutes a recommendation to spray. The decision to spray — including the final assessment of actual wind, temperature, inversion, and environmental conditions — rests entirely with you, the licensed pesticide applicator on site;
• Screenshots of DroneCommand weather displays are not evidence that conditions were safe or legally compliant at the time of application. Regulatory compliance with wind speed limits, application conditions, and environmental requirements is determined by actual measured conditions at the time of application, not by what a third-party data model showed beforehand;
• We are not liable for any chemical drift, environmental damage, crop damage, regulatory citation, or any other consequence arising from your reliance on DroneCommand weather data in making spray/no-spray decisions.

18.5 Equipment Malfunction

We are not responsible for the performance, maintenance, calibration, or malfunction of any drone, spray system, nozzle, GPS unit, or other physical equipment used in your operations. The Service does not control, monitor, or interface with physical equipment in any way that could affect application rates, coverage, or any other operational parameter.

18.6 Personal Injury, Bodily Harm, and Occupational Exposure

WE ARE NOT LIABLE FOR ANY PERSONAL INJURY, BODILY HARM, ILLNESS, DISEASE, DEATH, OR OCCUPATIONAL CHEMICAL EXPOSURE SUFFERED BY ANY PERSON — INCLUDING THIRD PARTIES, NEIGHBORING LANDOWNERS, BYSTANDERS, FARMWORKERS, BEEKEEPERS, OR YOUR OWN EMPLOYEES AND PILOTS — ARISING FROM YOUR DRONE SPRAY OPERATIONS, REGARDLESS OF WHETHER DRONECOMMAND WAS USED TO PLAN, RECORD, OR MANAGE THOSE OPERATIONS.

• Chemical Drift Personal Injury: If pesticide drift from your operations causes injury, illness, or health harm to a neighboring landowner, bystander, beekeeper, farmworker, or any other person, that claim is between you and the injured party. The fact that you used DroneCommand to plan, dispatch, or record the operation does not make us a party to any personal injury claim arising from that operation;
• Buffer Zone and Applicator License Compliance: Personal injury claims from pesticide drift frequently arise from failure to observe required buffer zones, restricted-entry intervals (REI), personal protective equipment requirements, or pesticide label conditions. You are solely responsible for compliance with all applicable buffer zones, setback distances, REI requirements, and label conditions — DroneCommand tools do not substitute for compliance with these requirements, do not calculate legally required buffer zones, and do not alert you to all applicable restrictions;
• Employee Pesticide Exposure: Occupational pesticide exposure claims by your pilots, spray technicians, or any other employees or contractors are claims against you as their employer or contracting party. Compliance with EPA Worker Protection Standard requirements — including safety training, PPE provision, restricted-entry interval enforcement, and emergency decontamination access — is solely your responsibility. DroneCommand does not track, remind, or enforce WPS compliance;
• DriftWatch and Sensitive Site Registrations — Not a Legal Safe Harbor: The fact that a beekeeper's location is visible in DriftWatch, or is not visible in DriftWatch because they are unregistered, does not create any legal protection for you. You are required to comply with all applicable Iowa BeeCheck notification requirements, pesticide label restrictions regarding bee hazard, and all other laws governing drift impacts on sensitive sites — regardless of what the Service shows or does not show;
• Indemnification: You agree to defend, indemnify, and hold harmless Country Road Drone Services, LLC, its members, managers, employees, and agents from any and all personal injury, wrongful death, toxic tort, or occupational exposure claims brought by any person arising from your spray operations, to the fullest extent permitted by applicable law. This indemnification obligation is in addition to and not limited by the general indemnification in Section 27.

18.7 Restricted-Entry Interval (REI) Tracking — Not Provided

EPA Worker Protection Standard (WPS) regulations at 40 CFR Part 170 require that workers and handlers do not enter treated areas during the Restricted Entry Interval (REI) specified on each pesticide product label. REIs range from four (4) hours to several days depending on the pesticide and application method. DroneCommand records when spray jobs occur. It does NOT calculate, display, track, enforce, or alert you or your workers to active Restricted Entry Intervals for any pesticide applied through the Service.

• No REI calculation from product data: Even if you enter the pesticide product name and label rate into a spray record, DroneCommand does not retrieve or display the REI for that product. We do not maintain a database of pesticide product labels or REI data. The REI for any product is found on the product label and in EPA's pesticide registration database — not in DroneCommand;
• No worker notification or alert system: DroneCommand does not send notifications to workers, pilots, or any other person warning them that a field is within its REI. There is no REI countdown timer, no treated-field warning overlay on maps, and no mechanism to prevent an Authorized User from dispatching a worker to a field that is within its REI;
• Your WPS compliance obligations: You are solely responsible for: (a) determining the applicable REI for each pesticide you apply; (b) establishing and enforcing REI compliance procedures for all workers and handlers; (c) posting required WPS notices and warning signs; (d) providing required WPS safety training; and (e) maintaining all records required by the WPS. These obligations exist independently of DroneCommand and are not affected by your use of the Service;
• REI violations and liability: EPA and state agricultural agencies enforce WPS REI requirements. Penalties for REI violations can include significant civil fines and, in cases involving serious worker injury, criminal prosecution. We are not liable for any REI violation, worker illness, worker injury, EPA citation, or other consequence arising from your failure to comply with REI requirements, regardless of whether the spray event was recorded in DroneCommand;
• If a worker enters a treated field during the REI and suffers pesticide exposure, that is an occupational health and safety failure on your part — not a failure of the record-keeping software you use. Do not mistake having a good record-keeping system for having a complete worker safety program.

18.8 Tank Mix Chemical Compatibility — Not Validated by DroneCommand

DroneCommand's job record and mix calculator features may allow you to document multiple pesticide or agricultural chemical products applied in a single spray operation. We do not validate tank mixes in any way — DroneCommand accepts any combination of products you enter without evaluating chemical compatibility, combined application rates, label restrictions, efficacy, or safety.

• Physical compatibility: Certain product combinations cause physical incompatibility — oil separation, crystallization, precipitation, or flocculation — rendering the mix ineffective or damaging to your spray equipment. DroneCommand has no compatibility database and will not warn you of incompatible combinations;
• Combined label rate compliance: When two or more products are mixed, combined application rates and interaction effects must be evaluated against each product's label and applicable EPA guidance. DroneCommand does not calculate or evaluate combined label rate compliance for multi-product mixes;
• Label-specific tank mix restrictions: Many pesticide labels include specific restrictions on tank mixing — required adjuvants, pH requirements, prohibited co-applications, and tank mix partner limitations. DroneCommand does not have access to or evaluate these label-specific restrictions;
• Phytotoxicity and crop injury: Even products that are each individually safe at their labeled rates may cause crop injury when combined, particularly at elevated temperatures or on sensitive crop varieties. We are not responsible for crop injury arising from tank mix phytotoxicity;
• Your responsibility under FIFRA: All tank mix decisions must be independently evaluated by a qualified licensed pesticide applicator with reference to each product's current registered label. Applying products in a manner inconsistent with their label directions — including in prohibited tank mix combinations — is a federal violation under FIFRA. We are not liable for any crop damage, equipment damage, regulatory violation, or other harm arising from a tank mix documented in DroneCommand.

18.9 Chemical Emergency Response — Call 911; DroneCommand Is Not an Emergency Response System

DroneCommand is a record-keeping and operations management platform. It is not an emergency response system, poison control system, safety data sheet repository, or hazardous materials incident management tool. In any pesticide exposure, spill, drift incident, equipment failure involving hazardous chemicals, or any other agricultural chemical emergency:

• Call 911 first. For any emergency involving human exposure to pesticides, chemical spills, fires involving stored chemicals, or any situation posing immediate risk to human health or safety, call 911 immediately. Do not attempt to look up product information in DroneCommand as a first response to a chemical emergency — call for emergency services first;
• Poison Control: For pesticide exposure and poisoning, contact the National Pesticide Information Center (NPIC) at 1-800-858-7378, or the Poison Control Center at 1-800-222-1222. These resources provide immediate expert guidance for chemical exposure incidents. DroneCommand's product records do not substitute for professional poison control guidance;
• Safety Data Sheets are not in DroneCommand: Safety Data Sheets (SDS), formerly Material Safety Data Sheets (MSDS), are required to be physically present at your operations site under OSHA's Hazard Communication Standard (29 CFR 1910.1200). DroneCommand does not store or display SDS documents. First responders and medical personnel need SDS information from the actual product documents — not from a spray record in our software;
• No emergency notification feature: DroneCommand has no mechanism to alert emergency services, notify neighboring property owners, alert beekeepers, or contact regulatory authorities in the event of a chemical incident. All emergency notifications are your responsibility and must be made through appropriate emergency services and regulatory channels;
• Post-incident records: After an emergency has been handled, you may use DroneCommand's spray record and notes features to document the incident for regulatory compliance and insurance purposes. But documentation is a post-emergency activity — it is not an emergency response tool. We are not liable for any harm, injury, death, environmental damage, or regulatory consequence arising from reliance on DroneCommand during or instead of appropriate emergency response.

18.10 Buffer Zone Calculations — Not Provided by DroneCommand

Federal and state pesticide law, individual pesticide product labels, and EPA Worker Protection Standard regulations impose mandatory buffer zones, setback distances, and no-spray zones around water bodies, structures, organic operations, school grounds, and other sensitive areas. DroneCommand does not calculate, display, enforce, or warn you about legally required buffer zones for any pesticide product, application method, or geographic location.

• Buffer zones are label-specific: Required buffer zones vary dramatically by pesticide product, formulation, application rate, application method, wind speed, geographic terrain, and proximity to sensitive features. Only the current registered label and applicable EPA guidance documents specify the legally required buffer for a given application. DroneCommand does not have access to or display this label-specific buffer zone information;
• No sensitive site distance calculator: DroneCommand's field mapping tools display field boundaries. They do not calculate, show, or warn about required setback distances from water bodies, irrigation systems, residential areas, school property, playgrounds, certified organic operations, or any other sensitive site. The field boundary displayed on our map does not account for any required buffer — you must apply that buffer independently and reduce your effective spray area accordingly;
• DriftWatch and BeeCheck are notification tools, not buffer calculators: DriftWatch and Iowa BeeCheck integrations show you the locations of registered sensitive sites. They do not calculate required notification distances, required buffer zones, or required pre-notification timing for any specific pesticide product. The obligation to calculate appropriate buffers and timing under each product's label remains yours;
• Aquatic buffer zones under Clean Water Act: Pesticide applications near water bodies are subject to aquatic buffer zone requirements under the National Pollutant Discharge Elimination System (NPDES) pesticide general permit. These requirements are application-specific and may require buffers of varying widths depending on water body type, application rate, and product. DroneCommand does not evaluate or display NPDES buffer requirements;
• We are not liable for any regulatory citation, environmental enforcement action, neighbor damage claim, beekeeper loss claim, or other consequence arising from your failure to maintain required buffer zones for any pesticide application documented in DroneCommand.

18.11 Aerial Spray Drift onto Organic-Certified Fields — Loss of Certification Not Our Liability

USDA National Organic Program (NOP) and accredited certifying agency regulations require that certified organic operations maintain documented practices to avoid contact with prohibited substances, including synthetic pesticides. A single pesticide drift incident onto a certified organic field can trigger a certifying agency investigation and may result in suspension or revocation of the affected field's organic certification. DroneCommand does not display the locations of certified organic operations, does not warn you before or during spray operations about proximity to certified organic fields, and does not calculate required buffer distances from certified organic operations for any specific pesticide product.

• No organic certification database: Unlike DriftWatch and Iowa BeeCheck, which provide a voluntary registry of sensitive sites, there is no equivalent publicly accessible registry of certified organic field locations that we could integrate. Certified organic operations are identified through USDA NOP certification records maintained by accredited certifiers — not through a geospatial API available to software developers;
• Catastrophic financial consequence: Loss of organic certification for even a single field season can eliminate the organic price premium on the entire year's crop yield from the affected acreage. This premium can represent a substantial portion of the grower's annual income. The financial exposure from a drift-onto-organics claim can be severe and may significantly exceed the value of the spray contract that caused the incident;
• Your pre-application investigation obligation: Before conducting aerial spray operations in any area where organic operations may be present, you are responsible for: (a) consulting USDA's organic operator database; (b) conducting neighbor outreach with surrounding landowners; (c) reviewing any known organic farm locations in the area; (d) following applicable pesticide label buffer requirements; and (e) choosing products and conditions that minimize drift risk consistent with your certification exposure under applicable law;
• Weather-based drift planning: Aerial spray drift is highly weather-dependent. You are responsible for choosing appropriate conditions — including wind speed, wind direction, temperature, humidity, and thermal inversion status — that minimize the probability of off-target deposition. DroneCommand weather data is informational; the operational decision to fly or not fly based on drift risk to neighboring certified organic operations is yours alone;
• We are not liable for any organic certification loss, lost organic price premium, crop damage claim, neighbor lawsuit, or regulatory enforcement arising from aerial spray drift from your operations onto any certified organic field, regardless of whether the spray event was documented in DroneCommand.

18.12 Thermal Inversion and Temperature Inversion Conditions — Not Detected or Displayed

Thermal inversions — atmospheric conditions in which a layer of warm air traps cooler air and associated pesticide droplets near the surface — are one of the most significant factors contributing to long-range pesticide drift and off-target deposition. Under thermal inversion conditions, pesticide droplets can travel miles from the application site. Most pesticide labels prohibit application during or when conditions could lead to a temperature inversion. DroneCommand does not detect, display, forecast, or warn about thermal inversion conditions at or around your spray sites.

• Weather data does not include inversion indicators: The weather data integrated into DroneCommand — which is sourced from third-party meteorological providers — may include temperature, humidity, wind speed, and wind direction. It does not include thermal inversion detection, boundary layer depth information, atmospheric stability class, or any other parameter that would indicate whether inversion conditions are present at your specific spray altitude and location;
• Label prohibition on inversion conditions: Many herbicide and insecticide labels — particularly dicamba-formulated products — explicitly prohibit application when a temperature inversion is present or is likely to form. Applying in violation of this label condition is a FIFRA violation. The absence of any inversion indicator in DroneCommand does not mean inversion conditions are absent — it means we do not display that information;
• Your independent assessment obligation: Detecting thermal inversion conditions requires observational skill and site-specific assessment that no remote weather data service can substitute for. Indicators include: smoke or odors lying flat and not dispersing, minimal surface wind with calm aloft, nighttime spray conditions or operations during early morning hours when the boundary layer has not yet mixed. You are responsible for conducting this independent assessment before application;
• Regulatory and civil exposure: Inversion-related drift claims are among the most serious and costly in the pesticide application industry. Dicamba drift under inversion conditions has resulted in multi-million-dollar jury verdicts against applicators and manufacturers in several high-profile cases. We are not a party to such claims and are not liable for drift damage arising from your operation under inversion conditions that DroneCommand did not detect or warn about;
• We are not liable for any crop damage, neighbor property damage, loss of organic certification, regulatory citation, civil judgment, or other consequence arising from pesticide application under thermal inversion conditions, regardless of whether the application was documented in DroneCommand.

18.13 Crop Variety Sensitivity — Not Tracked or Warned About

Different crop varieties within the same species can exhibit dramatically different sensitivity to pesticide products, including products that are labeled for use on that crop species generally. High-oleic soybeans, specialty corn hybrids, soft red winter wheat, and many other specialty varieties may be significantly more sensitive to drift or direct application from pesticide products that are labeled as safe for the corresponding commodity crop. DroneCommand does not track crop varieties planted in your customers' or landowners' fields, does not maintain a database of variety-specific sensitivity data, and does not warn you when a product you are planning to apply may be harmful to a specialty variety planted in or near your target field.

• Your agronomic responsibility: Before applying any pesticide to a field, you are responsible for knowing what crop and variety is planted in that field, in adjacent fields within drift range, and in any nearby fields where off-target deposition is possible. Many specialty variety growers are acutely aware of their sensitivity concerns and can inform you if you ask before spraying;
• Label limitations do not capture all variety sensitivity: Pesticide labels are registered for crop species — they cannot anticipate every proprietary variety's individual response. Varietal sensitivity that is not reflected on the label is not a label error — it is an agronomic condition you must assess through grower consultation, extension guidance, and pre-application investigation;
• Neighbor specialty crops: You may be applying a labeled product on a correctly identified crop at the correct rate, and still cause damage to a neighboring field if an ultra-sensitive specialty variety is planted nearby and drift reaches it. "The label allowed it" is not necessarily a complete defense when specialty variety damage is alleged;
• Seed company and product stewardship programs: Many seed companies maintain product stewardship programs with specific guidance on pesticide compatibility for their varieties. You are responsible for consulting these resources before applying products to or near fields planted with specialty varieties for which stewardship guidance exists;
• We are not liable for any crop damage, lost specialty crop premium, contract breach, or other consequence arising from variety-specific pesticide sensitivity that was not reflected on the product label and that we did not warn you about in DroneCommand, regardless of whether the spray event was recorded in our system.

18.14 Herbicide Soil Carryover and Rotational Crop Injury — Not Tracked or Predicted

Certain herbicide active ingredients — including but not limited to dicamba, aminopyralid, clopyralid, fluroxypyr, chlorsulfuron, metsulfuron, and other soil-persistent herbicides — can remain biologically active in the soil for periods extending from several months to multiple growing seasons. Rotational crops planted after a treated field may be injured by residual herbicide activity if minimum recrop intervals specified on the label are not observed, or if soil carryover exceeds typical predictions due to drought, low organic matter, low soil pH, or below-normal temperatures. DroneCommand does not track herbicide soil persistence data, calculate carryover risk, display minimum recrop intervals for any registered product, or alert you that a field scheduled for herbicide application may create rotational crop injury risk for the following season.

• Label recrop restrictions are the law: Under FIFRA, pesticide labels specify minimum intervals before planting a rotational crop. These intervals vary by rotational crop species, application rate, soil type, and geographic region. DroneCommand does not display label recrop intervals in the spray record interface and does not prevent you from recording an application without acknowledging recrop obligations to future tenants or landowners;
• Environmental conditions amplify carryover: Herbicide dissipation rates are significantly affected by soil moisture, temperature, microbial activity, pH, and organic matter content. In drought years or on low organic matter soils, carryover of soil-persistent herbicides can extend well beyond label-stated intervals. We do not display any environmental carryover risk factors or adjustment guidance in DroneCommand;
• Neighbor field carryover via runoff or wind erosion: Soil-active herbicides can move off-field through water erosion, wind erosion, and field drain tile outlets, potentially injuring neighboring fields planted to sensitive rotational crops. We are not responsible for tracking or modeling off-site carryover pathways or alerting you to neighbor field vulnerability;
• Bioassay testing and agronomic consultation: Growers concerned about herbicide carryover are responsible for conducting soil bioassay tests or consulting with a certified crop advisor before replanting fields treated with persistent herbicides. DroneCommand does not provide bioassay testing, carryover calculators, or soil persistence data for any registered pesticide product;
• We are not liable for any rotational crop injury, yield loss, specialty crop certification loss, lease dispute, contract breach, or other consequence arising from herbicide soil carryover that was not predicted, tracked, or warned about by DroneCommand, regardless of whether the original herbicide application was recorded in the Service.

18.15 Spray Drift onto Neighboring Livestock Operations — Special Liability Considerations

Agricultural drone spray operations on fields adjacent to livestock operations — including cattle feedlots, hog confinements, poultry barns, dairies, and pasture-grazed livestock — create a distinct category of pesticide drift liability. Livestock may be acutely sensitive to certain pesticide active ingredients, and exposure through contaminated feed, water, or pasture can cause illness, death, or detectable residue violations that prevent livestock from entering the food supply. In the worst cases, USDA residue violations trigger condemnations, buyer rejections, and contract claims that far exceed the value of any single spray application. DroneCommand does not display the locations of neighboring livestock operations, does not screen spray plans for proximity to livestock facilities, and does not provide livestock sensitivity data for any registered pesticide product.

• Livestock feed contamination risk: Pesticide drift onto neighboring hay fields, pastures, silage crops, grain crops destined for on-farm feeding, or stockpiled feed — and subsequent consumption by livestock — can trigger USDA Food Safety and Inspection Service (FSIS) residue violations. Livestock with detectable pesticide residues above applicable tolerances may be condemned at slaughter, causing losses that dwarf the economic value of the spray operation. We are not responsible for modeling drift pathways or predicting contamination risk to neighboring feed sources;
• Pesticide label livestock restrictions: Many pesticide product labels include specific requirements, restrictions, or buffer zones for applications near livestock, livestock housing, livestock watering sources, and feed storage. These label requirements are the law under FIFRA. DroneCommand does not display label livestock buffer requirements in the spray record interface and does not alert you when a product's label includes livestock proximity conditions;
• Spray buffer considerations for confinement facilities: Drift of insecticides, herbicides, or fungicides into open-air livestock confinements, poultry facilities, or open-sided cattle buildings can create acute toxicity events that kill or injure large numbers of animals in a short timeframe. The fact that a spray field appears within your DroneCommand account and a neighboring livestock facility does not is irrelevant — the physical proximity in the real world controls your buffer obligation, not the depiction of features in DroneCommand;
• Specialty market program residue consequences: Livestock produced under USDA Certified Organic programs, branded natural beef programs, or other market programs with specific input restrictions may be disqualified from those programs by any detectable prohibited pesticide residue — regardless of whether the residue level triggers an FSIS regulatory action. The market consequence can substantially exceed the regulatory consequence, and DroneCommand does not provide any information about which products may create residue risks under any specific market program;
• We are not liable for any livestock illness or death, FSIS residue violation, USDA condemnation, market program disqualification, feed contamination claim, contract breach, or other consequence arising from spray drift from operations recorded, planned, or scheduled in DroneCommand onto neighboring livestock, livestock confinement facilities, or livestock feed sources.

18.16 Pollinator Protection and Bee Kill Risk — Not Displayed or Calculated

Many pesticide products registered for use on Iowa field crops are acutely toxic to honey bees and other managed and wild pollinators. EPA and IDALS have established label requirements and best management practices for reducing bee kill risk, including application timing restrictions (do not apply to blooming crops when bees are foraging), re-entry interval requirements, and in some cases, mandatory pre-application notification to beekeepers within a defined radius of the spray area. Iowa BeeCheck is a voluntary registry system that allows beekeepers to register hive locations so spray operators can identify nearby hive sites. DroneCommand's display of Iowa BeeCheck registry data — where available — is subject to caching delays, voluntary registry participation, and all limitations described in Section 21. Bee kill risk is not calculated, modeled, or displayed by DroneCommand for any spray plan or chemical combination.

• Label pollinator protection requirements are binding: Many pesticide labels — particularly for neonicotinoids, pyrethroids, and organophosphates — include mandatory pollinator protection language with specific application timing restrictions, required pre-application notifications, and buffer zone requirements around known bee colonies. These label requirements are the law under FIFRA. DroneCommand does not display or enforce label-level pollinator protection requirements for any registered product;
• Iowa BeeCheck is voluntary and incomplete: Iowa BeeCheck registry participation is voluntary. Many beekeepers — particularly small-scale or hobby beekeepers — do not register their hive locations. A DroneCommand display showing no registered hives near your spray area does not mean there are no hives — it means no registered hives appeared in the last cache refresh. You are responsible for independent awareness of nearby bee colonies regardless of what the registry shows;
• Drift onto registered and unregistered apiaries: Bee kill caused by pesticide drift onto registered or unregistered apiary sites can result in significant civil liability — including the value of dead colonies, lost honey production value, and, in egregious cases, punitive damages under Iowa common law. DroneCommand does not calculate drift trajectories or predict downwind exposure risk to apiary sites;
• Applicator notification obligations: Iowa law and certain product labels may require you to notify registered beekeepers before making certain applications within a defined distance. You are responsible for determining whether any notification obligation applies to your specific application, product, and spray location, and for fulfilling that obligation before applying;
• We are not liable for any bee colony loss, civil liability to a beekeeper, IDALS investigation, FIFRA label violation finding, or other consequence arising from a pesticide application that harmed pollinators where the risk was not displayed, modeled, or warned about by DroneCommand, including applications made near hives that were not registered in Iowa BeeCheck at the time of the application.

18.17 Worker Protection Standard Re-Entry Intervals — Not Tracked or Enforced by DroneCommand

EPA's Worker Protection Standard (WPS), codified at 40 CFR Part 170, establishes re-entry intervals (REIs) — minimum time periods that agricultural workers must stay out of treated areas after a pesticide application — as well as notification requirements, posting obligations, decontamination facilities, and emergency assistance requirements. REIs vary by product and can range from 4 hours to several days. Agricultural employers who violate WPS REIs — by allowing workers to enter a treated area before the REI expires — face significant EPA civil penalties and potential criminal liability if a worker is injured. DroneCommand records the date and time of pesticide applications, but does not calculate REI expiration times for any recorded application, does not display REI information from product labels, and does not alert farm supervisors or workers when an REI for a specific field application has not yet expired.

• REI calculation requires label data we do not have: REIs are specified on individual pesticide product labels and vary by active ingredient, formulation, and application method. Calculating when an REI expires for a specific application requires knowing the specific product applied, the REI from the current label, and the exact completion time of the application. While DroneCommand records application time and product, it does not fetch or store REI data from product labels and does not calculate REI expiration times;
• Multiple overlapping REIs in tank mixes: When a tank mix application involves multiple products with different REIs, the controlling REI is the longest one. A supervisor managing worker access after a tank mix application must identify the longest REI among all products applied — a calculation that DroneCommand does not perform;
• Posting and notification obligations: WPS requires that treated areas be posted with WPS warning signs when REIs are longer than 30 days, and that central posting locations display specific information about recent pesticide applications including the REI. DroneCommand does not generate WPS posting materials, does not alert you to WPS posting obligations triggered by specific applications, and does not track compliance with WPS posting requirements;
• Iowa agricultural employer WPS obligations: Iowa agricultural employers — including drone spray operators who employ workers who enter treated areas — are subject to WPS requirements independently of whether DroneCommand records exist for a specific application. WPS compliance is your operational responsibility, not a function that DroneCommand performs or verifies;
• We are not liable for any WPS violation, EPA civil penalty, worker injury, workers' compensation claim, or other consequence arising from a worker entering a treated area before the applicable REI had expired, where that REI was not calculated, displayed, or enforced by DroneCommand.

18.18 Tank Residue Contamination from Prior Applications — Not Tracked or Warned About

Spray tanks, lines, nozzles, and mixing equipment used in agricultural drone spray operations retain residues of previously applied products. If a tank is not thoroughly rinsed and cleaned between product changes — or if cleaning is insufficient to remove traces of the prior product — the subsequent application may contain phytotoxic concentrations of the prior product or chemical combinations that the label of either product prohibits. Tank contamination events have caused significant crop damage and have resulted in FIFRA enforcement actions for off-label applications. DroneCommand records what product you intend to apply and what you enter into the spray record — it does not track what product was last loaded in a specific tank, does not warn you when a tank was last used with a phytotoxic product, and does not alert you when product combinations or tank sequence may create contamination risk.

• Dicamba and phenoxy acid carryover: Dicamba, 2,4-D, and other phenoxy acid herbicides are notorious for causing severe phytotoxicity to sensitive crops at extremely low concentrations. These compounds adhere to tank surfaces and rubber components and resist removal by water rinse alone. A tank that was used for dicamba application and is rinsed with only water before loading a fungicide or insecticide may still contain phytotoxic dicamba residue. Crop damage from tank carryover can occur at concentrations far below what is detectable by smell or visual inspection;
• Label cleaning requirements: Pesticide labels for phytotoxic products typically specify cleaning procedures — including rinsate volume, detergent requirements, and rinsate disposal instructions — that must be followed between applications of incompatible products. These cleaning requirements are part of the label and binding under FIFRA. DroneCommand does not display label cleaning requirements for products recorded in the system;
• Multi-operator tank sharing: When multiple operators share a drone or spray tank — common in custom application services — the previous operator's product residue may contaminate the subsequent operator's application. Neither operator may know what the other used the tank for, and DroneCommand has no record of what product was loaded by a different user if records were created under different accounts;
• Triple rinse and sprayout protocols: Industry standard triple rinse and sprayout protocols for tank cleaning between sensitive product changes require specific volumes of rinse water and specific rinsate management procedures. Compliance with these protocols is a field practice issue entirely outside the scope of DroneCommand's record-keeping function;
• We are not liable for any crop damage, FIFRA enforcement action, neighbor claim, or other consequence arising from tank residue contamination from a prior application that was not tracked, flagged, or warned about by DroneCommand, regardless of whether both the prior and current applications were recorded in the Service.

18.19 Pesticide Runoff, Leaching, and Major Storm Event Risk Not Predicted

Pesticide applications create residues in soil and vegetation that may be mobilized by precipitation events, particularly major storms, flash flooding, or snowmelt occurring after application. DroneCommand does not assess post-application precipitation risk, predict pesticide runoff or leaching potential, or provide any warning when weather conditions following an application create risk of pesticide movement into surface water or groundwater.

• Runoff potential not calculated: Pesticide runoff risk depends on soil type, slope, product label runoff language, proximity to surface water, and precipitation intensity — none of which are evaluated or integrated into DroneCommand's recordkeeping interface;
• Label runoff restrictions not enforced: Many pesticide labels contain runoff restriction language, setback requirements from water bodies, and application timing restrictions relative to forecasted precipitation; compliance with these requirements is your responsibility;
• Clean Water Act exposure: Pesticide movement into navigable waters, wetlands, or waters of the United States may trigger Clean Water Act liability regardless of label compliance; DroneCommand does not assess this risk;
• NPDES permit requirements: Some pesticide applications may require coverage under a National Pollutant Discharge Elimination System (NPDES) permit; DroneCommand does not evaluate or track NPDES permit requirements;
• We are not liable for any crop damage, surface water contamination, regulatory violation, Clean Water Act penalty, or other consequence arising from pesticide runoff, leaching, or movement following a major storm event or other precipitation, regardless of whether the application was recorded in DroneCommand.

18.20 Dicamba Volatilization, Temperature Inversion, and Secondary Movement Risk

Dicamba and certain other synthetic auxin herbicides are subject to secondary movement through volatilization — the conversion of the herbicide from liquid or solid form into vapor that can then drift to sensitive crops — separate from and in addition to spray drift at the time of application. DroneCommand does not assess volatilization risk, temperature inversion conditions, or secondary movement potential for any pesticide, and does not warn applicators when atmospheric conditions are conducive to post-application herbicide movement.

• Volatilization distinct from spray drift: Volatilization-related crop damage can occur hours or days after application under temperature inversion conditions that trap volatilized herbicide near the ground and allow it to move laterally to sensitive areas; DroneCommand has no mechanism to assess or warn about this risk;
• Label restrictions on temperature: Dicamba labels impose application restrictions based on temperature, including maximum application temperatures and requirements to avoid applications when inversions are likely; compliance with these restrictions is entirely your responsibility;
• Sensitive crop proximity: Dicamba-susceptible crops including soybeans, vegetables, and specialty crops may be present in surrounding fields; DroneCommand does not map sensitive crop locations or calculate proximity risk;
• EPA registration restrictions: Dicamba registrations have been subject to repeated regulatory action including label amendments, use restrictions, and revocations; current label status must be independently verified before each application;
• We are not liable for any off-target crop damage, neighbor claim, EPA enforcement action, or other consequence arising from dicamba or other herbicide volatilization, temperature inversion conditions, or secondary movement following application, regardless of whether the application was recorded in DroneCommand.

18.21 Honeybee Colony Loss, Managed Pollinator Kill, and Civil Liability to Beekeepers

Pesticide applications in agricultural settings create risk of harm to managed honeybee colonies and other pollinators, including colonies owned by commercial beekeepers operating in proximity to treated fields. A single pesticide application event can result in catastrophic colony losses costing thousands of dollars per colony, and civil liability to affected beekeepers may arise under Iowa Code and common law regardless of label compliance.

• Iowa BeeCheck registry limitations: The Iowa BeeCheck voluntary registry allows beekeepers to register hive locations to receive applicator notifications; however, not all beekeepers participate, registry data may be outdated, and hive locations may change seasonally without registry update;
• Notification obligations not enforced: DroneCommand does not automatically notify registered beekeepers of your upcoming applications, send BeeCheck notifications on your behalf, or verify that required notifications were sent before application;
• Label pollinator protection language: Many pesticide labels include mandatory pollinator protection language including application timing restrictions, notification requirements, and prohibitions on applications to flowering crops; compliance with this language is your responsibility;
• Civil liability independent of label compliance: A beekeeper may have a viable civil claim for colony losses caused by your pesticide application even where you complied with all label requirements, if reasonable care under the circumstances required additional precautions;
• We are not liable for any honeybee colony loss, beekeeper claim, regulatory citation, or other consequence arising from pesticide applications that harmed managed pollinators, regardless of whether BeeCheck notifications were sent, whether the application was recorded in DroneCommand, or whether you complied with all applicable label requirements.

19. Geospatial Data and Field Boundaries Disclaimer

The Geospatial Data features of DroneCommand, including field boundary mapping, acreage calculation, and GPS-based location tools, are subject to the following limitations and disclaimers:

19.1 Accuracy Limitations

GEOSPATIAL DATA IN THE SERVICE, INCLUDING FIELD BOUNDARIES AND ACREAGE CALCULATIONS, MAY BE INACCURATE DUE TO FACTORS INCLUDING BUT NOT LIMITED TO GPS SIGNAL LIMITATIONS, MAP PROJECTION ERRORS, BASE MAP INACCURACIES, DIGITIZATION ERRORS, AND DATUM DIFFERENCES. Calculated acreages are estimates and may differ from official survey measurements or government records. Do not rely solely on Service-generated acreage calculations for legal, regulatory, or payment purposes.

19.2 Field Boundary Verification

YOU ARE SOLELY RESPONSIBLE FOR VERIFYING THAT ALL FIELD BOUNDARIES ENTERED INTO THE SERVICE ACCURATELY REPRESENT THE ACTUAL PROPERTY YOU ARE AUTHORIZED TO SPRAY BEFORE COMMENCING ANY APPLICATION. We are not liable for any application on incorrect, neighboring, or unauthorized property arising from inaccurate field boundaries entered by you or your Authorized Users.

19.3 Third-Party Mapping Data

Base maps and satellite imagery available in the Service are provided by third-party mapping services. Their accuracy, currency, and coverage are not guaranteed. We are not responsible for errors in third-party mapping data.

19.4 No Survey Replacement

The geospatial tools in the Service do not constitute a professional land survey. For legally binding acreage determinations, property boundary disputes, or any purpose requiring certified survey data, consult a licensed land surveyor.

19.5 Field Boundary Displays Are Not Drone Flight Path Controllers

Field boundary polygons displayed in DroneCommand are visual reference tools for record-keeping and planning purposes. They are not flight control systems, autopilot inputs, geofencing barriers, or any form of active drone guidance. DroneCommand does not interface with, send commands to, or control any unmanned aircraft system. Specifically:

• A field boundary displayed in DroneCommand does not cause a drone to follow that boundary in flight — the drone's actual flight path is determined entirely by the drone's own systems, your pilot inputs, and any autonomous flight planning software you use;
• If you use a DroneCommand field boundary as a visual reference during flight planning in a separate drone mission planning application, any errors in the DroneCommand boundary (including GPS inaccuracy, digitization error, datum mismatch, or boundary errors you entered) will propagate into your flight plan — we are not responsible for off-target flight paths caused by inaccurate boundaries displayed in our app;
• We are not liable for any application to unauthorized property, neighboring property, organic fields, water bodies, structures, or any other location resulting from the drone's actual flight path deviating from a field boundary displayed in DroneCommand, whether due to GPS drift, pilot error, wind displacement, equipment malfunction, or any other cause;
• Before conducting any spray operation, you are responsible for physically verifying the field boundaries on the ground, confirming property lines with a licensed surveyor if necessary, and using your own professional judgment about the actual extent of property you are authorized to spray — not relying solely on a digital boundary displayed in an app;
• The use of DroneCommand boundary data in any third-party drone mission planning or autonomous flight control application is outside the scope of our Service and is done entirely at your risk.

19.6 Unauthorized Property — No Authorization Implied by Entering a Field

DroneCommand allows you to enter field boundary data, landowner names, GPS coordinates, and other information for any geographic location. The ability to enter a field into DroneCommand does not represent, imply, or certify in any way that you are authorized to access, enter, fly over, or spray that field. We do not verify property ownership, landowner consent, or operator authorization before allowing field data to be entered into the Service. Specifically:

• You are solely responsible for obtaining all legally required authorization — including landowner permission, written spray agreements, and any applicable right-of-entry — before conducting any spray operation on any field, regardless of whether that field is mapped in DroneCommand;
• Entering a field boundary into DroneCommand does not constitute evidence of your authorization to spray that field — it is simply a data entry reflecting a location you have chosen to record;
• If you spray a field without the landowner's authorization, you may be liable for trespass, unauthorized pesticide application, property damage, and related claims — that is your liability entirely, not ours;
• We are not liable for any trespass claim, unauthorized application claim, property damage claim, or regulatory violation arising from your spray operation on a field that was mapped in DroneCommand but for which you lacked authorization;
• If a landowner or property owner contacts us claiming that unauthorized spray records exist in our system for their property, we will cooperate with lawful inquiries and direct you to our subpoena process under Section 40 — we cannot unilaterally delete spray records at an unverified third party's request, but we will treat such a contact seriously and may notify you of the inquiry.

19.7 Landowner Authorization — Not Documented or Verified in DroneCommand

DroneCommand does not include a built-in feature for capturing, storing, or verifying landowner authorization to conduct spray operations. If you obtain verbal or written permission from a landowner before spraying, that authorization exists in your own records — not in DroneCommand. We strongly recommend obtaining written landowner authorization for all spray operations and retaining those documents outside DroneCommand.

• Verbal permission disputes: If a landowner later denies having authorized a spray operation that you conducted based on verbal permission, your DroneCommand spray record documents when and what was sprayed — it does not document that authorization was given. We cannot provide evidence of verbal authorization; we can only produce records of what was entered into our system;
• Spray authorization forms: A simple written spray authorization or service agreement executed by the landowner before each season's operations is the most reliable way to document authorization. These forms should be retained in your own records management system — we are not a document management platform for authorization agreements;
• Agent and tenant authorization: Authorization may come from a tenant farmer rather than the fee owner of the land. In some circumstances, a tenant's authority to authorize spray operations may be limited by the terms of the lease. You are responsible for ensuring that the authorizing party has legal authority to authorize spray operations on the property;
• Revocation of authorization: A landowner who previously authorized spray operations may revoke that authorization at any time, orally or in writing. DroneCommand has no mechanism to receive or record revocations. You are solely responsible for maintaining current communication with landowners and acting promptly on any revocation;
• We are not liable for any trespass claim, unauthorized application claim, property damage claim, regulatory violation, or other legal consequence arising from a dispute about whether landowner authorization existed at the time of any spray operation documented in DroneCommand.

19.8 Overhead Utilities, Structures, and Physical Obstructions — Not Shown on DroneCommand Maps

DroneCommand's field boundary mapping tools display satellite and aerial imagery and allow you to draw field boundaries. DroneCommand does not display, mark, or warn about overhead power lines, telecommunications cables, guy wires, antenna towers, grain bins, irrigation pivots, fences, tree lines, drainage tile locations, underground utilities, or any other physical obstructions that may be present within or around a field.

• Power lines are invisible on maps: High-voltage transmission lines and distribution lines are typically not visible on aerial or satellite imagery used in mapping applications, or may be extremely difficult to identify. Low-sag spans over fields are a known fatal hazard for low-altitude aerial operations. You are solely responsible for conducting a thorough physical ground survey of each field before flight to identify all overhead wire hazards;
• Third-party utility map limitations: Even third-party utility location services (such as Iowa 811) identify underground utilities for excavation safety — they do not exhaustively map overhead wire locations, private electric service drops, or temporary wiring. You must independently verify overhead hazards through physical site inspection and landowner consultation;
• Irrigation pivots and moving equipment: Irrigation pivots may be in different positions on aerial imagery than during your actual flight. Aerial imagery is static and may be months or years old. Equipment, vehicles, livestock, and people that are present in a field during your actual flight may not appear in the imagery you used for planning. Field conditions change — physical pre-flight inspection is required;
• FAA Part 107 pilot responsibility: FAA Part 107 requires the remote pilot-in-command to conduct a pre-flight assessment of the operating area including potential hazards. This obligation is yours as the remote pilot — it cannot be delegated to a mapping application or satisfied by reviewing a digital map. Ground-level and aerial hazards must be assessed through physical presence at the site;
• We are not liable for any aircraft collision, equipment damage, personal injury, death, property damage, or regulatory violation arising from contact with overhead utilities, structures, obstructions, or any other physical feature of a field that was not visible or displayed in DroneCommand maps.

19.9 Property Boundary vs. Physical Terrain — Maps Are Not Trespass Guides

DroneCommand's mapping tools display field boundaries and satellite imagery. Physical terrain features — such as drainage ditches, creeks, fence lines, berms, tree lines, shelter belts, and road rights-of-way — may fall within or along a property boundary, may traverse a field, or may mark the boundary between your authorized spray area and an adjacent property you are not authorized to enter. A field boundary polygon displayed in DroneCommand reflects the boundary as drawn by you or your staff — it does not account for physical features of the land that may modify the effective spray boundary, the practical access boundary, or the legal property boundary.

• Ditches and waterways as no-spray zones: Drainage ditches, tile outlet areas, and natural waterways carry buffer zone requirements under federal and state pesticide law. These features may run through the interior of a mapped field polygon. The fact that a ditch runs through your field polygon does not mean the polygon's full area is sprayable — you are responsible for knowing the location of waterways within your mapped field boundaries and applying required buffers;
• Fence lines and easements: Property boundaries and fence lines do not always coincide. Legal easements — road easements, utility easements, drainage easements — may cross or run along a field boundary in ways that restrict your right to spray to the edge of the fence. We are not responsible for providing legal survey data, easement information, or any other title-grade information about property boundaries;
• Aerial imagery resolution: Base map imagery provided by third-party mapping services may not have sufficient resolution to reveal narrow ditches, tile outlet areas, or other terrain features relevant to your buffer zone obligations. Do not rely on base map imagery as a definitive topographic map of your spray area;
• Physical scouting cannot be replaced by mapping: Pre-application physical scouting of field boundaries — walking the edges, identifying waterways, locating fence lines, and confirming access points — is an irreplaceable step in pre-spray planning. No digital map, however detailed, substitutes for ground-level knowledge of the area you are operating in;
• We are not liable for any application to unauthorized property, buffer zone violation, trespass claim, environmental violation, or other consequence arising from a discrepancy between a field boundary displayed in DroneCommand and the actual physical terrain, easements, waterways, or legal boundary of the spray area.

19.10 Conservation Reserve Program, Wetlands, and Native Prairie — Not Identifiable from Satellite Imagery

Federal and state conservation programs — including the Conservation Reserve Program (CRP), Wetland Reserve Easements (WRE), Grassland Reserve Program (GRP), Iowa STRIPS prairie restorations, and other enrolled conservation contracts — restrict or prohibit pesticide applications on enrolled acres. Native prairie remnants and protected wetlands also carry legal protections under federal and Iowa law that prohibit or limit pesticide applications in and around them. Satellite imagery and base maps displayed in DroneCommand may not allow you to visually identify CRP-enrolled ground, wetland reserve easements, native prairie remnants, or other conservation-enrolled acres — these areas may appear identical to commodity crop fields or grass waterways in aerial imagery.

• CRP contract terms prohibit most pesticide applications: CRP contracts prohibit the application of pesticides on enrolled acres except in specific circumstances approved in advance by the FSA county office, and only for insect or disease infestations that threaten adjacent crops. You are responsible for knowing which acres in your field portfolio are CRP-enrolled and for obtaining FSA approval before recording or performing any pesticide application on enrolled acres;
• Wetlands carry federal and state protections: Section 404 of the Clean Water Act, the USDA Wetland Conservation Provision ("Swampbuster"), and Iowa's Wetland Protection Act each impose restrictions on activities in and near jurisdictional wetlands. Pesticide applications to wetlands or within buffer zones of jurisdictional wetlands may violate these protections independently of any product label buffer zone requirement. DroneCommand's field boundary maps do not display wetland delineation boundaries or jurisdictional wetland determinations;
• Native prairie remnants may carry contractual and legal protections: Iowa native prairie remnants are subject to Iowa DNR stewardship programs and, in some cases, contractual easements that restrict all pesticide applications regardless of the applicator's intent or the product's label. Satellite imagery does not reliably distinguish native prairie from CRP grass acres, grass waterways, or other non-crop cover that might be legally sprayable under a different land use scenario;
• FSA and NRCS records are the authoritative source: The authoritative records for conservation program enrollment, wetland delineation, easement boundaries, and acreage eligibility are maintained by USDA's Farm Service Agency (FSA) and Natural Resources Conservation Service (NRCS) at the county level. You are responsible for consulting these records before planning, scheduling, or recording any application on or adjacent to conservation-enrolled, conservation-eligible, or wetland-adjacent land;
• We are not liable for any CRP contract violation, FSA penalty, Swampbuster consequence, wetland enforcement action, state conservation law violation, or other consequence arising from a pesticide application on or near conservation-enrolled, wetland, or native prairie land that was not identified, flagged, or excluded by DroneCommand's mapping features.

19.11 Schools, Churches, Hospitals, and Residential Areas — No Proximity Warnings Issued

Pesticide applications near schools, churches, hospitals, residential neighborhoods, daycares, nursing homes, and other sensitive receptor locations are subject to state and local notification requirements, buffer zones under certain product labels, and heightened regulatory and public scrutiny that extends well beyond basic label compliance. Drift from an agricultural drone application onto a school playground, church parking lot, or residential yard — even if within normal operational parameters — can trigger state regulatory investigations, adverse media coverage, civil litigation, and reputational harm that far exceeds any agronomic benefit of the application. DroneCommand does not maintain data on the locations of schools, churches, hospitals, residential zones, daycares, or other sensitive receptor locations, does not screen spray plans for proximity to sensitive receptors, and does not alert you when a planned application is near a location that triggers additional notification, buffer zone, or public awareness obligations.

• State notification requirements near schools and childcare facilities: Some states and localities require pesticide applicators to provide advance notice to schools and childcare facilities before making applications in the surrounding area. Iowa may impose notification requirements through IDALS administrative rules or through specific label conditions that apply to individual products. You are responsible for determining what pre-notification obligations apply to each specific application location and for fulfilling those obligations before spraying;
• Label buffer zone requirements for sensitive receptor sites: Some pesticide product labels include specific buffer zones around residential areas, school grounds, recreational areas, playgrounds, and other occupied non-agricultural sites. These buffer zones are part of the registered label and are legally binding under FIFRA. DroneCommand does not display label buffer zone requirements for sensitive receptor sites and does not alert you when a mapped field polygon is within a label-required buffer zone of a sensitive location;
• Public perception and media risk: An agricultural drone spray application visible to, or drifting toward, a school, church, or neighborhood is a high-profile public event regardless of the application's technical compliance with the product label. Complaint calls, social media, local news coverage, and IDALS complaint filings can result from technically lawful applications that nonetheless create negative community relations. This reputational and complaint risk is yours to manage;
• Scheduled community events create elevated exposure populations: Churches, schools, fairgrounds, athletic fields, and community facilities host scheduled events during which populations of children, elderly persons, and medically vulnerable individuals are present in elevated numbers. Spray operations scheduled near these facilities during event times create heightened exposure risk and complaint probability that DroneCommand has no way to detect or warn you about;
• We are not liable for any state notification violation, label buffer zone violation, civil complaint, IDALS investigation, adverse media consequence, or other harm arising from a spray application conducted near a school, church, hospital, residential zone, daycare, or other sensitive receptor location that was not identified, flagged, or excluded by DroneCommand's mapping or scheduling features.

19.12 Tile Drain Outlets and Surface Water Inlets — Not Shown on Field Maps

Iowa agricultural fields are extensively tiled — subsurface drainage tile networks underlie a significant portion of Iowa cropland and discharge through tile outlets to open ditches, streams, and drainage channels. Surface water inlets — including intakes on tile systems that accept surface water directly from the field — concentrate pesticide-laden runoff and direct it rapidly into drainage networks. Both tile outlets and surface water inlets carry buffer zone requirements under many pesticide product labels and create non-point source pollution pathways that trigger state and federal water quality obligations. DroneCommand's field boundary maps and satellite imagery do not display the locations of subsurface tile outlets, surface water inlets, intake risers, or other drainage infrastructure features that may affect your label compliance obligations or your contribution to pesticide loading in Iowa's drainage networks.

• Tile outlet buffer zones on pesticide labels: Many pesticide product labels include buffer zone requirements specifically for tile outlets and surface water inlets, which are treated as "water bodies" or "drainage features" for label compliance purposes. These label buffer zones are binding under FIFRA. DroneCommand does not display tile outlet locations or enforce label buffer zones around drainage infrastructure features that do not appear on our maps;
• Iowa water quality law: Iowa's Nutrient Reduction Strategy and EPA's NPDES stormwater requirements impose obligations on agricultural operations that contribute pollutants to water of the United States through drainage tile systems. Pesticide applications that reach drainage tile through preferential flow pathways — particularly in sandy soils or immediately after heavy rainfall — can constitute a point source discharge regulated under the Clean Water Act, independent of label buffer zone compliance;
• Intake risers and concentrated surface runoff: Tile intake risers — vertical standpipes that accept surface water from depressions in the field — can funnel pesticide-laden water directly into drainage networks. The location of intake risers is not visible in satellite imagery of sufficient resolution to enable identification from DroneCommand's map interface. You are responsible for physically locating intake risers and drainage structures in your fields and applying appropriate buffers;
• Post-application rainfall intensifies risk: The pesticide loading risk from tile drainage is highest during and immediately after rainfall following a spray application. DroneCommand does not integrate precipitation forecast data with your spray record to assess post-application tile drainage risk for any specific product, soil type, or drainage system configuration;
• We are not liable for any pesticide tile drainage event, Clean Water Act violation, IDALS water quality enforcement action, neighbor or downstream party claim, or other consequence arising from pesticide reaching drainage infrastructure that was not displayed, buffered, or identified in DroneCommand's field mapping features.

19.13 FEMA Floodplain Designations and 100-Year Flood Zones — Not Displayed on Field Maps

FEMA's National Flood Insurance Program (NFIP) designates Special Flood Hazard Areas (SFHAs) — commonly called the "100-year floodplain" — that are subject to specific federal development, insurance, and land use restrictions. Portions of Iowa agricultural fields that fall within SFHA designations may be subject to crop insurance coverage limitations, FSA program eligibility restrictions, and local floodplain ordinance requirements that affect how those areas can be farmed. Additionally, pesticide applications to SFHA areas create heightened water quality risk because floodplain soils are periodically inundated, creating direct pathways for pesticide-laden floodwater to reach waterways. DroneCommand field boundary maps and satellite imagery do not display FEMA SFHA designations, floodplain boundaries, or flood zone classifications — and do not alert you when a mapped field polygon includes or is adjacent to a Special Flood Hazard Area.

• FSA program eligibility and floodplain: USDA farm programs — including ARC, PLC, and crop insurance — may have eligibility restrictions or premium adjustments for acres within designated floodplains. Fields that are partially within the SFHA may have coverage limitations on flooded acres. You are responsible for understanding how SFHA designations affect FSA program eligibility and crop insurance coverage for each field in your operation;
• Local floodplain ordinances: Iowa counties and municipalities with NFIP participation have adopted floodplain management ordinances that restrict certain activities within the SFHA. While agricultural operations generally receive more permissive treatment than development activities, specific activities in the floodplain — including permanent structure installation, fill placement, and in some cases the installation of irrigation or drainage infrastructure — may require permits. DroneCommand does not display or cross-reference local floodplain ordinances;
• Pesticide application in floodplains and water quality risk: Pesticide applications to fields within or adjacent to SFHA areas carry elevated water quality risk during and after flood events. Pesticide-laden floodwater reaching navigable waters may trigger Clean Water Act enforcement independently of whether the application was label-compliant. We do not provide floodplain-specific application risk information in DroneCommand;
• FEMA FIRM maps are the authoritative source: The authoritative source for floodplain designations is FEMA's Flood Insurance Rate Map (FIRM), available through FEMA's Flood Map Service Center at msc.fema.gov. Before conducting operations in low-lying areas adjacent to waterways, consult the current FIRM to determine whether your spray area includes SFHA-designated acres;
• We are not liable for any FSA program eligibility consequence, crop insurance coverage limitation, floodplain ordinance violation, Clean Water Act enforcement action, or other consequence arising from a pesticide application on SFHA-designated or floodplain-adjacent land that was not identified, flagged, or excluded by DroneCommand's mapping features.

19.14 Overhead Power Lines, High-Voltage Transmission Corridors, and Pipeline Easements — Not Shown on Field Maps

Agricultural fields frequently contain or adjoin overhead power lines, high-voltage transmission corridors, and buried pipeline easements. For drone spray operations, overhead power lines present a direct collision and electrocution hazard — agricultural drones operating at typical spray altitudes of 10–30 feet can encounter distribution lines that are not visible from a distance or in low-light conditions. Buried pipeline easements may also impose surface use restrictions, including restrictions on aerial pesticide applications, that are contained in recorded easement documents rather than in any publicly accessible digital database. DroneCommand field boundary maps and satellite imagery do not display overhead power line locations, transmission corridor boundaries, buried pipeline easements, or other utility infrastructure that may affect drone flight safety or your surface use rights within a mapped field.

• Aerial collision and electrocution hazard: Contact between a drone and an energized power line can result in equipment destruction, power outages, fire, and in some circumstances electrocution of nearby individuals. Distribution lines serving rural farmsteads are frequently strung across field interiors and at varying heights — satellite imagery may not reveal their presence, particularly when imaged in summer canopy conditions. Ground-level pre-flight scouting to identify all overhead obstacles is your responsibility before each operation;
• Transmission line buffer zones: High-voltage transmission corridors maintained by investor-owned utilities and rural electric cooperatives may have buffer zones under which aerial pesticide applications are restricted by easement agreement, utility policy, or state PUC regulation. These restrictions are property record matters — they are not displayed in DroneCommand and are not accessible through satellite imagery;
• Pipeline easement surface restrictions: Recorded pipeline easements — including natural gas, petroleum, and anhydrous ammonia pipelines — may contain surface use restrictions limiting aerial applications directly above the pipeline corridor. These restrictions appear in recorded easement documents at the county recorder's office and are not available in any publicly accessible geospatial database that DroneCommand connects to;
• Call before you fly: Identifying underground infrastructure in your spray area requires contacting Iowa One Call (811) for buried utility marking. Identifying overhead power line locations requires direct scouting or contact with the relevant utility. Neither service is integrated with or substituted by DroneCommand;
• We are not liable for any drone collision, power outage, fire, property damage, personal injury, pipeline rupture, easement violation, or other consequence arising from the presence of overhead power lines, utility infrastructure, or pipeline easements in or near a spray area that were not displayed, flagged, or identified by DroneCommand's mapping features.

19.15 Tribal Lands, Treaty-Protected Areas, and Native American Sacred Sites

Agricultural operations in proximity to tribal trust lands, treaty-protected areas, or sites of cultural or religious significance to Native American tribes may be subject to federal consultation requirements, treaty rights, or tribal jurisdiction that differ from standard state and federal agricultural regulations. DroneCommand does not identify tribal land boundaries, treaty-protected areas, or Native American sacred sites, and does not flag when a proposed spray operation may be near or within such areas.

• Tribal sovereignty: Tribal nations have sovereign authority over their trust lands; drone operations over or near tribal lands may be subject to tribal ordinances, permits, or restrictions that are separate from FAA Part 107 authorization;
• Treaty rights: Treaty-protected hunting, fishing, gathering, and water rights may create liability exposure for pesticide drift or water contamination in treaty cession areas, even where the spray location is on non-tribal land;
• NHPA Section 106 consultation: Projects affecting areas of significance to Native American tribes may require tribal consultation under Section 106 of the National Historic Preservation Act; DroneCommand does not evaluate these requirements;
• NEPA and federal nexus: If your operation involves federal land, federal permits, or federal funding, tribal consultation may be required under NEPA or other federal statutes before activities affecting tribally significant areas;
• We are not liable for any treaty rights violation, tribal sovereignty issue, Section 106 consultation failure, or other consequence arising from drone operations near or affecting tribal lands, treaty-protected areas, or Native American sacred sites that were not identified or flagged by DroneCommand.

19.16 Irrigation District Rights-of-Way, Canal Setbacks, and Water Delivery Infrastructure

Irrigation districts and drainage districts hold easements, rights-of-way, and setback requirements over agricultural land that may restrict pesticide applications in proximity to canals, ditches, laterals, and other water delivery infrastructure. DroneCommand does not display irrigation district boundaries, canal or ditch locations, applicable pesticide setbacks from water delivery infrastructure, or drainage district easements.

• Pesticide setbacks from water features: Many pesticide labels require buffer distances from open water, irrigation ditches, and drainage tiles; compliance with these setbacks is your responsibility and is not enforced or displayed by DroneCommand;
• District ordinances: Irrigation and drainage districts may have their own ordinances governing pesticide application near district infrastructure that are separate from state and federal regulations; DroneCommand does not compile or display these requirements;
• Spray contamination of irrigation water: Pesticide contamination of irrigation water used by downstream operators can result in significant crop damage and liability; DroneCommand does not assess the risk of spray reaching irrigation water sources;
• Drainage tile outlet setbacks: Applications near subsurface drainage tile outlets may require specific setbacks or may be prohibited under certain product labels; tile outlet locations are not displayed in DroneCommand;
• We are not liable for any crop damage, water contamination, district ordinance violation, downstream irrigation injury, or other consequence arising from spray applications near irrigation canals, drainage ditches, tile outlets, or other water delivery infrastructure that was not identified or displayed by DroneCommand.

19.17 Surveyed Parcel Boundaries vs. GIS Boundaries — Acreage Discrepancies and Trespass Risk

Field boundaries displayed in DroneCommand are derived from GIS data sources and satellite imagery that may not correspond precisely to legally surveyed parcel boundaries recorded in county deed records. Reliance on DroneCommand field boundaries for determining the legal extent of your application area may result in applications that inadvertently cross property lines, creating trespass and pesticide drift liability to adjacent landowners.

• GIS vs. legal survey discrepancy: GIS-derived parcel boundaries are approximations; the legally binding property line is established by a licensed land survey and recorded deed description, neither of which is incorporated into DroneCommand's mapping data;
• GPS accuracy limitations: Consumer and commercial GPS receivers used with drone systems have accuracy limitations; a field boundary drawn using GPS may deviate from the true property line by several feet to several meters;
• Acreage billing disputes: Acreage calculated by DroneCommand based on drawn field boundaries may differ from acreage calculated by other methods; we make no warranty regarding the accuracy of acreage calculations for billing, FSA reporting, or other purposes;
• Fence line vs. legal boundary: Fence lines, hedgerows, and other physical features commonly used as visual field boundaries during spray operations may not coincide with legal property lines, particularly on older farmsteads;
• We are not liable for any property trespass, pesticide drift claim, over-application, acreage billing dispute, FSA reporting error, or other consequence arising from a discrepancy between DroneCommand's displayed field boundaries and legally surveyed parcel boundaries.

20. Chemical Application and Mix Calculator Disclaimer

The Mix Calculator and chemical application rate tools within DroneCommand are provided as computational aids to assist with batch sizing and rate calculations based on data you enter.

20.1 No Agronomic Advice

THE MIX CALCULATOR AND ALL CHEMICAL APPLICATION RATE TOOLS IN THE SERVICE ARE NOT A SUBSTITUTE FOR PROFESSIONAL AGRONOMIC ADVICE, CERTIFIED CROP ADVISOR CONSULTATION, OR THE PRODUCT LABEL. THE PRODUCT LABEL IS THE LAW UNDER FIFRA. YOU MUST VERIFY ALL CALCULATED RATES, APPLICATION VOLUMES, CARRIER VOLUMES, AND MIXING INSTRUCTIONS AGAINST THE CURRENT PRODUCT LABEL BEFORE EACH APPLICATION.

20.2 User Responsibility for Input Data

The accuracy of Mix Calculator outputs is entirely dependent on the accuracy of the data you enter. We are not responsible for calculation errors arising from incorrect input of product names, application rates, label rates, tank volumes, dilution factors, field acreage, or any other variable you provide.

20.3 Label Compliance

Application rates, tank mixes, spray intervals, personal protective equipment requirements, re-entry intervals, and all other conditions of use are governed exclusively by the registered pesticide label. Rates calculated or suggested by the Service may not reflect the most current label and may not account for specific crop, pest, or environmental conditions. Always consult the current registered label before making any application decision.

20.4 No Liability for Chemical Errors

WE ARE NOT LIABLE FOR ANY HARM, INJURY, CROP DAMAGE, ENVIRONMENTAL CONTAMINATION, REGULATORY VIOLATION, OR OTHER LOSS ARISING FROM THE USE OF THE MIX CALCULATOR OR ANY CHEMICAL APPLICATION RATE TOOL IN THE SERVICE, INCLUDING LOSSES ARISING FROM CALCULATION ERRORS, DATA ENTRY ERRORS, LABEL DISCREPANCIES, OR RELIANCE ON OUTPUTS WITHOUT INDEPENDENT VERIFICATION.

20.7 Autonomous and AI-Assisted Application Planning — No Override of Pilot-in-Command Authority

DroneCommand may include features that suggest application zones, variable-rate prescriptions, or AI-assisted spray planning outputs. All such outputs are advisory only and do not constitute agronomic, regulatory, or operational recommendations.

• Advisory status only: Any application planning suggestions, zone recommendations, variable-rate prescriptions, or AI-assisted planning outputs generated by the platform are advisory only and do not constitute agronomic, regulatory, or operational recommendations of any kind;
• Pilot-in-Command authority is absolute: The FAA-certified Remote Pilot in Command retains sole authority and responsibility for all flight and application decisions regardless of what the platform suggests — no platform output modifies, overrides, or diminishes Pilot-in-Command authority under FAA regulations;
• Real-time conditions not captured: Automated spray planning outputs do not account for real-time field conditions, wind shifts, temperature inversions, formulation interactions, or application rate changes that may occur after plan generation — plans generated hours or days before an operation may not reflect conditions at application time;
• Label compliance is the operator's responsibility: Platform outputs do not constitute pesticide label interpretation — label compliance is always the operator's sole responsibility regardless of what a planning tool suggests or displays;
• We are not liable for any crop damage, drift event, regulatory violation, enforcement action, or other harm arising from implementation of platform-generated spray planning suggestions.

20.8 Nozzle Type, Spray Quality, and Equipment Configuration — Operator Responsibility

DroneCommand may allow operators to enter nozzle type, spray quality classification, and equipment configuration data, and may display reference data based on those inputs. All such data is operator-supplied and is not verified or certified by DroneCommand.

• Operator-supplied inputs are unverified: Nozzle type, spray quality classification (pursuant to ASABE S572.1 or equivalent standards), and equipment configuration data entered in DroneCommand are operator-supplied inputs — DroneCommand does not independently verify, validate, or certify any entered equipment data;
• Reference classifications reflect standard conditions only: ASABE S572.1 spray quality classifications displayed by the platform are based on standard reference data — actual spray quality in operational conditions varies with pressure, formulation, temperature, and wind conditions not monitored by the platform;
• Not a drift reduction certification: Platform spray quality displays do not constitute compliance certification for drift reduction requirements under EPA-registered product labels, state regulations, or voluntary buffer zone programs;
• Manufacturer specifications govern: Equipment configuration data in DroneCommand does not substitute for manufacturer specifications, label requirements, or agronomist recommendations regarding nozzle selection for specific applications;
• We are not liable for any drift event, label violation, crop damage claim, or other harm arising from reliance on platform spray quality classification displays or equipment configuration data.

21. Third-Party Services and Integrations

21.1 Overview

DroneCommand integrates with and relies on third-party services and data sources. We are not responsible for the availability, accuracy, reliability, or content of any third-party service or data.

21.2 Stripe (Payment Processing)

All payment processing is handled by Stripe, Inc. Stripe's Terms of Service and Stripe's Privacy Policy govern the processing of your payment information. We are not responsible for any payment errors, failed transactions, billing disputes, or other issues arising from Stripe's systems. For payment issues, contact Stripe directly via your Customer Portal.

21.3 DriftWatch / FieldWatch

DriftWatch data (sensitive crop and specialty crop registry data) provided in the Service is sourced from the FieldWatch program operated by Purdue University. DriftWatch data is informational only, may be incomplete, may not reflect current registrations, and may not cover all sensitive crops or beekeeping operations in your area. We do not warrant the accuracy, completeness, or timeliness of DriftWatch data. You are solely responsible for complying with all applicable notification and consultation requirements regardless of what DriftWatch data shows. We are not liable for any chemical drift, crop damage, or other harm arising from reliance on DriftWatch data.

21.4 Iowa BeeCheck

Beekeeper registry data from Iowa BeeCheck is informational only and may not reflect all registered apiaries in your operating area. You are solely responsible for complying with all applicable beekeeper notification requirements under Iowa law and any other applicable statute. We are not liable for any bee or apiary damage arising from your spray operations, whether or not Iowa BeeCheck data was consulted.

21.5 Weather Data Providers

Weather data is sourced from third-party meteorological services and is provided for informational and planning purposes only. Weather data may be inaccurate, delayed, unavailable, or not representative of actual conditions at your specific location. We are not liable for any losses arising from reliance on weather data provided through the Service.

21.6 Email Delivery Services

Transactional and notification emails are delivered via third-party email service providers. We do not guarantee email delivery and are not liable for any harm arising from delayed or undelivered emails, including renewal reminders, payment failure notices, or other account notifications. It is your responsibility to ensure that emails from our domain are not blocked by spam filters and that your email address on file is current.

21.7 Cloud Infrastructure

The Service is hosted on third-party cloud infrastructure. We are not responsible for losses arising from cloud provider outages, infrastructure failures, or changes to cloud provider services.

21.8 Third-Party Integration Unavailability — Null or Empty Display

CRITICAL — INTEGRATION OUTAGES: When a third-party integration (including DriftWatch, Iowa BeeCheck, or weather data providers) is unavailable, experiencing an outage, or returning no data, DroneCommand may display a blank result, "no data available" message, zero results, or similar. A blank, empty, or "no results" display when a third-party integration is unavailable does NOT mean there are no sensitive crops, no registered apiaries, or no adverse weather conditions in your area — it means the data could not be retrieved. You must treat an unavailable third-party integration the same as if you had no access to the tool at all. You must independently verify conditions through direct contact, physical scouting, and consultation with neighbors before proceeding with any spray operation. We are not liable for any harm arising from reliance on a blank or null display that was caused by a third-party service outage rather than an actual absence of sensitive crops, apiaries, or adverse conditions.

21.10 Third-Party Data Freshness, Cache Lag, and Registration Timing

CRITICAL — REGISTRATION LAG: Third-party registry data accessible through DroneCommand — including DriftWatch sensitive crop registrations, Iowa BeeCheck apiary registrations, and any similar registry — may reflect data that was current as of the time it was last synchronized with the third-party source, which may not be real-time. Specifically:

• DroneCommand may cache third-party registry data for performance and availability purposes. Cached data may be minutes, hours, or (in the event of a third-party outage) longer behind the live registry at the time of your query;
• An individual, beekeeper, or specialty crop grower may have registered with DriftWatch or Iowa BeeCheck after the last data synchronization and before your query. Their registration would appear in the live registry but may NOT appear in DroneCommand's display if the cache has not been refreshed;
• A display showing "no registrations" or "no sensitive crops" does NOT mean there are no registrations — it means that as of the last cache refresh, there were none. Actual registrations may exist that are not yet reflected. You must treat the registry display as a starting point for investigation, not a definitive answer;
• We are not liable for any harm — including apiary losses, crop damage, neighbor disputes, or regulatory violations — arising from reliance on cached registry data that did not reflect a registration that was in the live registry at the time of your spray operation, but had not yet been synchronized into our cache;
• For operations near areas where sensitive crops or apiaries are likely (based on your own knowledge of local conditions), do not rely solely on DroneCommand's registry display — contact DriftWatch directly, perform physical scouting, and notify neighbors regardless of what the display shows.

21.11 Permanent Discontinuation of Third-Party Integrated Services

The third-party services integrated with DroneCommand — including DriftWatch, Iowa BeeCheck, weather data providers, and mapping services — are operated by independent organizations over which we have no control. Any of these services may be permanently discontinued, restructured, paywalled, or made unavailable at any time. We are not liable for the consequences of a third-party service permanently ceasing operations or discontinuing its integration with DroneCommand.

• If DriftWatch (operated by Purdue University) permanently discontinues its service or its publicly accessible API, we will remove or disable the DriftWatch integration from DroneCommand. We will not be required to provide a substitute integration, and the absence of DriftWatch from the Service does not constitute a Material Adverse Change under Section 33.1 — the DriftWatch integration is an informational convenience feature, not a core compliance tool;
• If Iowa BeeCheck permanently discontinues its service, the same applies — its removal is not a Material Adverse Change;
• If a weather data provider permanently discontinues, we will use commercially reasonable efforts to substitute an alternative weather data provider within a reasonable time, but we cannot guarantee continuity of weather data during any transition period;
• The permanent discontinuation of a third-party service does not entitle you to a refund, service credit, or termination of your subscription without the normal cancellation procedure in Section 12;
• The removal of a third-party integration from the Service following that third party's discontinuation is not a breach by us of these Terms — it is a consequence of the third party's decision, which is outside our control;
• Your operational compliance obligations — including pre-spray notifications, neighbor consultation, and buffer zone compliance — exist independently of whether any third-party tool is available. The permanent unavailability of DriftWatch or Iowa BeeCheck does not suspend or modify your legal obligations to consult neighbors and comply with all applicable spray restrictions.

21.9 General Third-Party Disclaimer

Any links to third-party websites, services, or resources are provided for your convenience only. We do not endorse, control, or accept responsibility for the content, policies, or practices of any third-party service. We are not responsible for any loss or damage arising from your dealings with any third party.

21.12 Chemical Inventory Module — Not a Regulatory Compliance Record

DroneCommand's chemical inventory module allows you to track pesticide, fertilizer, and other agricultural chemical stock for your own operational planning purposes — quantities on hand, usage history, and reorder planning. The chemical inventory module is an operational convenience tool only. It is NOT and does not constitute any of the following legally required records or reports:

• FIFRA Section 8 records: The EPA's recordkeeping requirements for certified pesticide applicators under FIFRA are not satisfied by DroneCommand's inventory module — those requirements specify particular record formats, retention periods, and content requirements that differ from what DroneCommand's inventory module captures;
• SARA Title III / EPCRA Tier II chemical inventory report: If your operation stores reportable quantities of hazardous chemicals, you may be required to file annual Tier II reports with your State Emergency Response Commission, Local Emergency Planning Committee, and local fire department under EPCRA Section 312. DroneCommand's inventory module is not designed to generate or satisfy Tier II reporting requirements;
• OSHA Hazard Communication / HazMat inventory: OSHA's Hazard Communication Standard (29 CFR 1910.1200) requires employers to maintain a list of hazardous chemicals in the workplace and have Safety Data Sheets available. DroneCommand's inventory module does not satisfy these OSHA requirements;
• State pesticide dealer and use records: Iowa and other states may require pesticide dealers or commercial applicators to maintain specific records of pesticide purchases, sales, and use. Consult your state's pesticide regulatory agency to determine your specific recordkeeping obligations — do not assume the inventory module satisfies those requirements;
• Do not submit inventory module exports as regulatory filings: We are not liable for any regulatory violation, fine, penalty, or enforcement action arising from your submission of DroneCommand inventory module data as a substitute for a legally required inventory report or recordkeeping document.

21.14 Email Delivery Classification — Transactional vs. Marketing; Effect of Unsubscribing

Email service providers and inbox providers (Gmail, Outlook, Apple Mail, and others) classify incoming emails into categories such as "Primary," "Promotions," "Spam," "Transactional," and others, using automated filtering algorithms that we do not control. Despite our best efforts to classify our emails correctly as transactional communications, renewal reminders, payment failure notices, security alerts, and other critical account emails may be filtered into your Promotions folder, Spam folder, or blocked entirely by your email provider's filters.

• Classification is not in our control: Individual inbox providers make their own filtering decisions based on proprietary algorithms, your personal email behavior, and your email provider's spam policies. We cannot guarantee that any specific email from us will reach your primary inbox. The fact that an email was sent does not mean it was received or seen;
• Unsubscribing has consequences: Many email clients present an "Unsubscribe" link in all emails from a sender. Clicking this link in a transactional or account-notification email may update your preferences in our email delivery system to stop sending you ALL emails from our domain — including critical renewal reminders, payment failure notices, and security alerts. We attempt to distinguish transactional from promotional emails, but email systems are imperfect. If you unsubscribe from our emails, you must actively monitor your account through the dashboard and Stripe Customer Portal for renewal dates and payment status;
• Corporate email gateways: If your business uses an enterprise email security gateway, that gateway may quarantine or block emails from our sending domain as a policy decision. Configuring your gateway to allow emails from our domain is your IT team's responsibility, not ours;
• Add us to your address book: The single most reliable step you can take to improve delivery of our emails to your primary inbox is to add [email protected] to your email address book or approved sender list. This signals to your email provider that our emails are wanted;
• Our obligation to provide renewal reminders and account notifications is satisfied when we transmit the email to our email delivery service for delivery to your registered address — we are not liable for missed notifications caused by inbox filtering, spam classification, unsubscribe actions, or corporate email gateway blocking.

22. Intellectual Property Rights

22.1 Our Intellectual Property

The Service, including but not limited to all software code, algorithms, databases, designs, user interfaces, graphics, text, logos, trademarks, service marks, trade names, trade secrets, and all other content and materials (collectively, "Our IP"), is owned by or licensed to Country Road Drone Services, LLC and is protected by copyright, trademark, patent, trade secret, and other intellectual property laws. All rights not expressly granted herein are reserved.

22.2 Restrictions

You may not, without our prior written consent: copy, reproduce, distribute, publish, display, transmit, or create derivative works of Our IP; use our name, logo, trademarks, or branding in any way; reverse engineer, decompile, disassemble, or attempt to derive source code from the Service; use any portion of the Service to develop a competing product or service; remove or alter any proprietary notices, labels, or copyright notices; or use automated tools to scrape, extract, or index Service content.

22.3 Feedback

If you provide us with feedback, suggestions, or ideas regarding the Service ("Feedback"), you grant us a perpetual, irrevocable, worldwide, royalty-free license to use, reproduce, modify, publish, distribute, and incorporate such Feedback into the Service or other products without compensation to you. For the avoidance of doubt: (a) Feedback means voluntary, unsolicited suggestions, feature requests, and ideas communicated informally — it does not mean paid consulting work, proposals submitted under a separate consulting agreement, or communications you have designated in writing as proprietary and confidential before submission; (b) we are under no obligation to implement, acknowledge, or respond to any Feedback; (c) if you want compensation for any idea or proposal before sharing it with us, do not share it — once submitted without a prior written compensation agreement signed by a member or manager of Country Road Drone Services, LLC, any idea or suggestion you share with us is treated as Feedback under this Section and you have no compensation claim; and (d) unsolicited proposals accompanied by an invoice or compensation demand will be returned unread.

23. User Content and Data Accuracy

23.1 Your Responsibility for Content

You are solely responsible for the accuracy, completeness, legality, and appropriateness of all User Data and other content you or your Authorized Users enter into the Service. You represent and warrant that: all User Data is accurate and complete to the best of your knowledge; you have all rights and permissions necessary to submit User Data to the Service; your User Data does not violate any law, regulation, or third-party rights; and you have obtained all required consents from employees, pilots, contractors, and other individuals whose personal information is entered into the Service.

23.2 Employee and Personnel Data

You are responsible for obtaining all legally required consents and providing all required notices before entering employee, pilot, or contractor personal information (including names, contact information, time records, payroll data, or any other personal data) into the Service. We process such data on your behalf as a data processor; you remain the data controller with respect to employee data and are solely responsible for compliance with all applicable employment and privacy laws governing such processing.

23.2a Accidental Disclosure Through User Actions

DroneCommand contains competitively sensitive data including field locations, customer lists, pricing, and operational records. You are solely responsible for controlling who can see your DroneCommand account during any screen sharing session, remote access session, video call, demonstration, or any other situation where your screen may be visible to third parties. We have no obligation to implement data masking, privacy screens, or any feature designed to conceal your data from individuals who can physically see your screen. We are not liable for any disclosure of your operational data to competitors, customers, regulators, or any other third party that occurs because you shared, mirrored, or allowed someone to view your screen, device, or exported files without intending to disclose their contents. You are responsible for data security at the presentation layer — i.e., who sees your screen.

23.3 No Monitoring

We do not monitor or verify the accuracy of User Data. However, we reserve the right (but not the obligation) to review User Data where we have reason to believe it violates these Terms, applicable law, or poses a risk to the integrity of the Service.

23.4 Invoice and Financial Accuracy

DroneCommand provides invoicing and job costing tools to assist you in billing your customers. You are solely responsible for reviewing, verifying, and approving the accuracy of all invoices, quotes, job costs, and financial records generated by the Service before transmitting them to your customers or any third party. We are not responsible for any financial disputes, overcharges, undercharges, errors, omissions, or other financial harm to you or your customers arising from inaccuracies in invoices or financial records generated by the Service, whether caused by data entry errors, software bugs, rate miscalculations, tax errors, or any other cause. Your downstream customers are not third-party beneficiaries of these Terms and have no claim against us arising from your invoicing errors.

Acreage Billing Disputes: Acreage figures used in your invoicing, generated from DroneCommand's mapping and calculation tools, are estimates subject to the accuracy limitations described in Section 19. We are not a party to any billing dispute between you and your customers regarding the number of acres sprayed, the acreage calculated by the Service, or the difference between DroneCommand-calculated acreage and any other measurement. If your customer disputes an invoice based on DroneService-calculated acreage, that is a dispute between you and your customer. We are not liable to either party for acreage calculation errors in those billing disputes.

Insurance and Crop Insurance Records: Spray records created in DroneCommand may be submitted as part of crop insurance claims, loss adjustment processes, or other insurance-related purposes. We are not responsible for the outcome of any insurance claim, including claims denied, reduced, or penalized based on information in your DroneCommand records. If your DroneCommand records contain information that an insurance adjuster finds inconsistent with other evidence, that is a function of the data you entered. We do not verify records against field evidence, do not certify records for insurance purposes, and are not liable for insurance claim outcomes attributable to the content of records you created through the Service.

23.5 Employees and Contractors Are Third Parties — No Privity of Contract

Your employees, pilots, contractors, and other personnel who are Authorized Users under your account are not parties to these Terms. These Terms are a contract between you (the Customer) and us. Your employees and contractors have no rights against us under these Terms, and we owe no duty directly to your employees or contractors arising from these Terms. Any claim by your employee or contractor relating to their personal data, wages, time records, payroll information, or any other matter involving their use of or data in DroneCommand must be directed to you as their employer or contracting party — not to us. You are responsible for ensuring your employees and contractors comply with these Terms as Authorized Users. You are responsible for any claims by your employees or contractors arising from data stored in or processed by the Service, as described in Section 27 (Indemnification).

23.5a Time Tracking, Payroll Records, and Labor Law

DroneCommand's time tracking features are operational tools to record hours worked by pilots and staff. They are not certified payroll systems, Human Resources systems, or legal compliance tools for labor law purposes. You are solely responsible for ensuring that time records maintained in DroneCommand are accurate, complete, and that your compensation practices based on those records comply with all applicable federal and state labor laws, including the Fair Labor Standards Act (FLSA), Iowa wage and hour law, and any applicable minimum wage and overtime requirements. We are not responsible for:

• Wage and hour violations arising from how you used or failed to use time data in the Service;
• Overtime calculation errors caused by data entry errors, incomplete time entries, or failure to configure the time tracking features correctly;
• Claims by employees or contractors arising from discrepancies between time tracked in the Service and hours actually worked;
• The use of DroneCommand time records as evidence in any wage dispute, labor board proceeding, or employment litigation — we are not a party to such disputes and bear no responsibility for the accuracy of time records you enter;
• Any decision you make regarding employee compensation based on time data in the Service.

If an employee, pilot, or contractor brings a wage claim and DroneCommand time records are relevant evidence, that is a dispute between you and your employee — not a claim against us. You agree to indemnify us for any costs we incur responding to third-party subpoenas or legal process in connection with employment disputes arising from your use of the Service, per Section 40.

23.6 Prohibited Data — Health, Medical, and Sensitive Personal Information

You may not enter the following categories of sensitive personal information into any field of the Service — including notes fields, job description fields, or any free-text input: health conditions, diagnoses, medications, prescription drug use, disability status, genetic information, mental health information, or any other health or medical information about any individual. You may not enter Social Security numbers, government-issued identification numbers, financial account numbers, or any information that would make the Service a de facto repository of regulated sensitive data categories. DroneCommand is not designed, configured, or certified to store or process protected health information under HIPAA, and storing such information in the Service is a violation of these Terms.

If you enter prohibited sensitive data into the Service in violation of this Section, you bear sole responsibility for: any resulting privacy law violations; any regulatory penalties; any claims by the individuals whose sensitive data was improperly entered; and any data breach consequences specifically attributable to the presence of that prohibited data. We are not a HIPAA Business Associate and have not executed any Business Associate Agreement. We are not liable for any consequences of your decision to enter prohibited data types into the Service.

23.7 "Record Saved" and Confirmation Messages — Not a Guarantee of Persistence

When DroneCommand displays a "Record saved," "Saved successfully," "Changes saved," or similar confirmation message, that message indicates that the Service received and accepted your input at the moment of submission. It does not guarantee that the record was permanently persisted to our database if: (a) a network connection failure occurred between your browser and our servers after the message was displayed but before the write transaction completed on the server side; (b) a server-side error caused the transaction to roll back after the client received a success response; or (c) a browser crash or session timeout caused a pending save to be lost.

• We are not liable for records that appear to have been saved based on a confirmation message but were not actually persisted due to a technical failure of any kind;
• For regulatory spray records in particular: after creating any record that is required by law to be retained, we strongly recommend immediately navigating to that record in the Service to confirm it is visible and accessible before closing the session — do not assume persistence based solely on a confirmation message;
• If you experience a save confirmation followed by a record not appearing in the system, contact us immediately at [email protected] — do not create a new record based on memory until you investigate whether the original record was saved, as this could create duplicate or conflicting records;
• Save confirmation reliability depends on factors including your internet connection quality, browser stability, and the operational state of our servers at the exact moment of save — we do not warrant 100% save confirmation accuracy under all network and browser conditions;
• This limitation applies equally to all record types — spray records, job records, inventory records, time entries, and any other data entered through the Service.

23.8 User-Initiated Deletion — Immediate, Permanent, and Unrecoverable

When you or any Authorized User permanently deletes a record, field, customer entry, time entry, inventory record, job, or any other data item through the Service's delete functionality, that deletion is immediate, permanent, and unrecoverable. We are not able to recover user-initiated deletions from our system backups. Our backup systems are designed for disaster recovery of the entire Service — they do not support point-in-time recovery of individual records deleted by users.

• There is no "trash" or "recycle bin" — deletion is final;
• We are not liable for loss of data deleted by you or any Authorized User, whether the deletion was intentional, accidental, or caused by an Authorized User acting outside the scope of their authority;
• Disgruntled employee sabotage: If an Authorized User — including a current or soon-to-be-terminated employee — deletes records before their access is revoked, those records are permanently lost. This is a foreseeable risk of granting deletion privileges to Authorized Users. You are responsible for: (a) granting deletion permissions only to trusted personnel; (b) revoking access immediately when employment ends or a disciplinary situation arises; and (c) maintaining independent backups of critical records so that user-initiated deletions cannot cause permanent record loss;
• For regulatory spray records specifically: because these records cannot be deleted by users once finalized (they are marked immutable per Section 14.8), the primary deletion risk for regulatory records comes from records that have not yet been finalized — we strongly recommend finalizing regulatory records promptly after each spray operation;
• If you suspect that an employee has deleted records in a deliberate act of sabotage, contact us at [email protected] immediately — while we cannot recover the deleted records, we may be able to provide evidence (from access logs) of who performed the deletion and when, which may be relevant to your legal claims against that individual.

23.9 Our Billing Errors — Remedy Commitment

While our billing is processed by Stripe and is generally accurate, we may make errors — including charging the wrong plan amount, charging twice in one cycle, applying an incorrect tax rate, or other billing mistakes. If we make a billing error:

• Contact us at [email protected] with the subject "Billing Error" and provide the date, amount, and nature of the error;
• We will investigate within five (5) business days of receiving your report and, if we confirm a billing error on our side, we will issue a full refund of the erroneous charge to your original payment method via Stripe within ten (10) business days of confirmation;
• Our liability for a confirmed billing error is limited to refunding the specific erroneous charge — we are not liable for consequential damages arising from a billing error, including overdraft fees charged by your bank, interest charges, returned payment fees from other vendors, or any other secondary financial harm resulting from the erroneous charge;
• Billing errors that are disputed more than ninety (90) days after the charge date may be subject to reduced remedies — contact us promptly upon discovering any billing discrepancy;
• This Section does not apply to disputes about whether a charge was authorized (governed by Section 11.4) or disputes about plan pricing (governed by Section 6.3) — it applies only to situations where we processed a charge in the wrong amount or at the wrong time through a technical or administrative error on our part.

23.10 Invoice Fraud — Our Tools Do Not Authorize False Records

DroneCommand's invoicing and job costing tools allow you to create invoices based on data you enter. Creating a false, inflated, or fraudulent invoice using DroneCommand is a violation of these Terms, regardless of whether the invoice was generated using our tools. We are not a party to invoicing fraud and our tools do not authorize, facilitate, or legitimize any fraudulent or deceptive invoice.

• If you use DroneCommand to generate invoices that contain false acreage figures, fabricated jobs, inflated rates, or other materially inaccurate information for the purpose of overcharging or defrauding your customers, you are solely and entirely responsible for all civil and criminal consequences of that fraud;
• We are not a party to any dispute between you and your customer arising from a false or inflated invoice — the fact that the invoice was generated using DroneCommand does not make us a responsible party in any fraud claim, unfair business practices claim, or contract dispute;
• If a landowner, farmer, or other third party contacts us or pursues legal process against us alleging that DroneCommand was used to generate false invoices against them, we will cooperate with valid legal process and will not shield our records from lawful disclosure. We reserve the right to terminate your account upon credible evidence of fraudulent use of our invoicing tools;
• The generation of an invoice through DroneCommand does not constitute our endorsement, certification, or verification of the accuracy of the amounts invoiced — we do not review invoices for accuracy before they are sent to your customers;
• We are not liable for any claim by your customer against you arising from invoice inaccuracies, and your customer has no claim against us arising from our provision of the invoicing tool you misused.

23.11 Duplicate Records — No Automatic Deduplication; Both Records Appear Official

DroneCommand does not automatically detect or prevent duplicate records. If you or an Authorized User creates two records for the same spray job — whether through user error, double-submission, connectivity retry, or any other cause — both records will appear in your account as separate, official-appearing entries. We do not deduplicate spray records, job records, or any other record type.

• Regulatory Appearance of Duplicate Records: A regulatory inspector reviewing your spray records may see two records with the same date, field, chemical, and rate, and interpret this as evidence that: (a) the same field was sprayed twice in the same day, raising label rate compliance questions; (b) records were fabricated or manipulated; or (c) your record-keeping practices are unreliable. We are not liable for any regulatory consequence arising from duplicate records in your account, including citation, fine, audit escalation, or license proceedings;
• Your Responsibility to Identify and Manage Duplicates: You are solely responsible for reviewing your records, identifying duplicates, and managing them. For non-immutable records (not yet finalized), you can delete duplicates using standard delete functionality. For immutable (finalized) records, contact us at [email protected] — while we cannot delete finalized records, we may be able to add an administrative notation indicating a specific record is a known duplicate, if technically feasible;
• Connectivity Retry Duplicates: If a network connection is unstable during record save, DroneCommand may submit a save request multiple times because the initial response was uncertain — this can result in duplicate records being created. This is a known limitation of web-based record-keeping over unreliable connections. If you are entering records in a location with poor connectivity, verify after saving that exactly one record was created before closing the session;
• No Automated Deduplication Service: We do not offer and are not responsible for providing any deduplication review, audit, or cleanup service. Maintaining clean, accurate, non-duplicate records is your operational and regulatory responsibility as a licensed pesticide applicator;
• If a duplicate-record situation leads to a regulatory compliance problem, insurance dispute, or legal proceeding, our records will reflect exactly what was entered, when, and by whom — and you will be responsible for explaining the circumstances of the duplication to any regulatory authority or party relying on your records.

23.12 Applicator Name in Spray Records Is User-Entered and Unverified

The "pilot," "applicator," or "licensed applicator" field in spray records accepts whatever name or identifier you or your Authorized User types. We do not validate this field against the FAA Airmen Inquiry database, the Iowa Department of Agriculture and Land Stewardship licensing database, or any other government registry in real time or at any other time. A spray record can be created in DroneCommand naming an individual as the licensed applicator whether or not that person actually holds a current, valid license.

• Regulatory consequence of unlicensed applicator records: If a spray record in your account names an applicator who, at the time of the documented spray operation, did not hold a valid Iowa commercial pesticide applicator license or the required FAA Part 107 certificate, that record documents an unlicensed application. Iowa law prohibits commercial pesticide application by unlicensed individuals, regardless of supervision. The existence of a DroneCommand record does not retroactively validate an unlicensed application — it documents it;
• You are responsible for all named applicators: Before creating any spray record naming a specific applicator, you are solely responsible for verifying that person currently holds all required licenses and certificates. Do not name an applicator in a record without personally confirming their current licensure status — do not rely on a prior check, their verbal assurance, or what DroneCommand displays from a prior data entry;
• Incorrect names and identity: If an applicator's name is entered incorrectly — misspelled, abbreviated, or entered under a nickname rather than legal name — that record may not correctly identify the applicant for regulatory or legal purposes. You are responsible for ensuring that the legal name and correct credential numbers are used in all regulatory records;
• Records naming former or terminated applicators: If a record is created after an applicator's license has been revoked, expired, or surrendered, the record still shows that person as the applicator. Regulators may investigate the discrepancy between the record date and license status. We are not liable for any enforcement action arising from records naming an individual whose license status you failed to verify;
• We are not a license registry, a credentialing authority, or a compliance monitoring service. The information in applicator fields is what you entered, and we disclaim all responsibility for the accuracy of applicator credential information in any spray record.

23.13 Your Records Are Discoverable Evidence — Accurate Records Cut Both Ways

By maintaining detailed, timestamped, and — for regulatory spray records — immutable records in DroneCommand, you are creating documentary evidence that may be produced in regulatory proceedings, civil litigation, insurance claim investigations, or criminal investigations. We encourage accurate record-keeping because it is legally required and operationally sound. You should also understand that the records you create can be subpoenaed, produced in civil discovery, or obtained by regulatory authorities through lawful legal process — and we will comply with that process.

• Regulatory subpoenas and inspections: IDALS, EPA, and other regulatory agencies can request spray records during inspections and enforcement investigations. Accurate records demonstrating compliance are your best defense; inaccurate records that contradict physical evidence, neighboring observations, or weather data are evidence against you. The value of your DroneCommand records in a regulatory proceeding depends entirely on their accuracy;
• Civil litigation discovery: If a landowner, neighboring property owner, beekeeper, farmworker, or other party sues you for damages from your spray operations, your DroneCommand records will almost certainly be requested in discovery. Records showing the chemical, rate, time, conditions, and applicator may support your defense — or provide the plaintiff with documentary proof of the elements of their claim against you;
• Records as admissions: A spray record you create in DroneCommand can be used as a party admission in legal proceedings — it is a document you created, in your system, describing what you did. If the record contains inaccurate information, that inaccuracy may be used against you even when the underlying facts were different;
• Prior knowledge and punitive damages: In cases where a claimant alleges willful or reckless conduct, detailed records may be used to show you were aware of relevant risks and continued operations regardless. Your records may be strong evidence of prior knowledge in a punitive damages claim if they document repeated violations, marginal conditions, or ongoing compliance problems;
• We are not liable for any adverse regulatory, legal, or insurance outcome arising from the content of records you created in DroneCommand. The most effective legal protection DroneCommand provides is the ability to create accurate, professional, and timely records of your operations — that protection is only as strong as the accuracy of what you enter.

23.14 Transcription Errors From Paper Records — What DroneCommand Shows Is Your Official Digital Record

Many licensed pesticide applicators maintain handwritten paper records in the field and transcribe them into DroneCommand at a later time. When you transcribe paper records into DroneCommand, you are creating the digital version of your official record. Any transcription errors — transposing a rate, entering the wrong applicator name, recording the wrong field, or misreading a handwritten note — become part of your official digital record. The paper record and the digital record may then diverge, and both may be discoverable in any regulatory or legal proceeding.

• Both records may be produced: If your paper field notes and your DroneCommand spray records tell different stories about the same application — different rates, different times, different chemicals — a regulatory inspector or plaintiff's attorney will have access to both. Discrepancies between paper field notes and digital records can undermine the credibility of both and invite allegations of manipulation or falsification;
• Transcription creates a new record: When you type data from a paper record into DroneCommand, you are not "filing" the paper record — you are creating a new digital record based on your transcription. Transcription errors create divergence, not equivalence, between the paper original and the digital version. If the paper record is the legally required record, its data must be transcribed accurately;
• Timing discrepancy: If you spray at 8:00 AM and transcribe the record at 5:00 PM that day, the "record created" timestamp in our system reflects 5:00 PM. The record's application time field should reflect 8:00 AM if that is when application occurred. A regulatory inspector may ask why your records are routinely created hours after application. This is not a violation if the application time field is accurate — but it is a routine question in compliance audits. You should be prepared to explain your record-keeping workflow;
• Illegible handwritten originals: If a handwritten field note is illegible, ambiguous, or uses abbreviations that are unclear in hindsight, and you transcribe an incorrect value into DroneCommand based on your best interpretation, that transcription becomes your record. We are not liable for the consequences of transcription errors arising from illegible or ambiguous original field notes;
• We are not liable for any regulatory citation, license action, civil liability, or other consequence arising from errors introduced during your transcription of paper or other records into DroneCommand. The accuracy of your digital records is your sole responsibility regardless of the source of the data you entered.

23.15 Records After Account Reactivation — Gaps During Suspension Are Not Recreated

Under Section 10, an account that has been suspended for non-payment transitions to read-only status. You cannot create, edit, or delete records during the suspension period. When you reactivate your account by paying outstanding balances, your account returns to full functionality — but DroneCommand does not fill in, prompt for, or retroactively create records for the period during which your account was suspended.

• Regulatory gap during suspension: If spray operations occurred during your account suspension — performed by pilots without access to DroneCommand — those operations were not recorded in real time. You remain legally obligated to maintain records of all commercial pesticide applications under Iowa IAC 45.26 and equivalent state law regardless of whether your DroneCommand account was active. Regulatory requirements do not pause when your SaaS subscription lapses;
• Retroactive record entry is a transcription risk: When you reactivate, you may attempt to enter records for applications made during the suspension. Retroactively entered records present all of the transcription accuracy risks described in Section 23.14, and additionally face credibility questions because the record creation date will be days or weeks after the documented application date. Be prepared to explain this discrepancy if records are reviewed by a regulatory authority;
• Record retention obligation is continuous: The 3-year record retention obligation under Iowa IAC 45.26 applies to all spray operations, not only those captured in DroneCommand. If operations occurred during a subscription lapse, those operations are still subject to record-keeping requirements and you are responsible for maintaining whatever records exist for that period — including handwritten field notes, photographs, or other contemporaneous documentation;
• No data loss from suspension: Your historical records from before the suspension are preserved in read-only format during suspension and are fully accessible upon reactivation. Account suspension does not delete records. However, restoration of access to historical records is not a substitute for records of operations that were never entered;
• We are not liable for any regulatory citation, compliance gap, insurance issue, or other consequence arising from your failure to maintain records of spray operations conducted during a period of account suspension, regardless of the reason for the suspension.

23.16 Records as Evidence of Prior Knowledge — Punitive Damages Exposure

In civil litigation, punitive or exemplary damages may be awarded against a defendant when the defendant's conduct was willful, wanton, reckless, or demonstrated conscious disregard for the safety of others. A key element in establishing entitlement to punitive damages is evidence that the defendant had prior knowledge of the risk and continued the conduct regardless. Your DroneCommand records — including spray records, weather records at the time of application, job notes, and any communications logged in the system — may constitute evidence of prior knowledge in a punitive damages claim.

• Prior application records in the same area: If you have previously documented spray operations in the same area as an incident — and your records reflect that drift conditions, buffer zone proximity, or other risk factors were present on prior occasions — a plaintiff's attorney may argue that you had prior knowledge of the risk and deliberately ignored it. Accurate records that document near-misses, marginal conditions, or acknowledged risk factors can be used to establish knowledge and recklessness;
• Notes and comments as admissions: Free-text notes fields in DroneCommand allow you to record observations about jobs. If you document concerns about drift risk, marginal weather, buffer proximity, or product concerns in notes, and then proceed with the application anyway, those notes may be produced in discovery and used as evidence that you were aware of the risk. Notes entries are discoverable documents;
• Pattern of conduct evidence: A series of DroneCommand records showing repeat applications under marginal conditions — consistently high wind speeds, repeat applications near the same sensitive neighbor, recurring buffer proximity issues — can be used to establish a pattern of conduct supporting punitive damages that would not be visible from a single incident record. Comprehensive record-keeping, while required by law, makes patterns visible in discovery;
• This cuts in your favor too: Records demonstrating consistent, professional compliance — appropriate weather windows, proper rates, attention to neighbor locations, timely entries — are powerful evidence of due care that negates recklessness and punitive damage exposure. The same record completeness that could hurt you in a pattern-of-violation case can protect you when your operations were conducted responsibly;
• We are not liable for any punitive damages awarded against you in any proceeding in which your DroneCommand records were produced as evidence of prior knowledge, a pattern of conduct, or willful disregard. The content and implications of your records are your responsibility.

23.17 Records and Court-Ordered Amendments — We Cannot Alter Finalized Records

Iowa law and applicable federal regulations treat finalized spray records as immutable regulatory documents once they are created. DroneCommand enforces record immutability for regulatory spray records consistent with Section 14.8. If a court, arbitrator, regulatory authority, or other official body issues an order, judgment, or directive concerning the content of records stored in DroneCommand — whether directing correction, annotation, deletion, or any other modification — we will comply with valid, enforceable legal process as described in Section 40. However, because finalized spray records are immutable, we may be technically unable to comply with certain types of modification orders even if we receive them.

• What we can do: In response to valid legal process, we can: add an administrative notation to a record flagging it as disputed, under court order, or subject to a pending proceeding; produce records in the format required; provide access log evidence about when and by whom records were created; and preserve records beyond our standard retention period pursuant to a litigation hold as described in Section 47.5;
• What we cannot do: We cannot delete, overwrite, or alter the core data content of a finalized spray record — including timestamps, applicator names, chemical names, rates, or field data — even pursuant to a court order. The immutability that protects your records from unauthorized alteration equally prevents court-ordered modification. If a court order requires a type of modification we technically cannot perform, we will notify the issuing court of this technical limitation and cooperate with the court in identifying alternative means of compliance;
• Contradictory records: If a court or regulatory authority finds that a spray record contains false information, the remedy under applicable law may not involve record alteration — it may involve entry of a judicial finding, a regulatory annotation, or other process. You should work with your attorney to understand the remedies available under the applicable legal process;
• Correction of non-finalized records: Records that have not yet been finalized can be edited through the normal editing process. If you discover an error in a non-finalized record, you should correct it through normal editing before finalization rather than attempting to correct it through legal process after the fact;
• We are not liable for any legal prejudice, enforcement consequence, or other harm arising from our technical inability to modify finalized records in response to a court order or regulatory directive that we could not technically execute.

23.18 Browser Auto-Fill and Pre-Populated Fields — Still Your Spray Record

Modern web browsers and password managers aggressively auto-populate form fields based on previously entered data. If your browser has stored prior spray record data — chemical names, application rates, field names, applicator names, or any other field values — it may automatically insert that stored data into new spray record forms in DroneCommand without your active input. If you submit a spray record without verifying that auto-filled or pre-populated values accurately reflect the current application you performed, the submitted record is legally yours — it is not a browser error, a DroneCommand system error, or an automatically generated record that can be disclaimed.

• Browser-filled values are indistinguishable from user-entered values: Once a spray record form is submitted, DroneCommand cannot determine whether a field value was typed by a user, selected from a dropdown, auto-filled by the browser's autocomplete feature, pre-populated from a prior record, or entered through any other method. The submitted data is the record of the application regardless of the mechanism by which it entered the form;
• Pre-populated "copy from prior record" features: DroneCommand may offer features that pre-populate new spray record fields from a prior record as a convenience. If you use this feature, you are responsible for reviewing and correcting all pre-populated values before saving. Pre-populated values do not automatically update to reflect the actual current application — they reflect the prior application from which they were copied;
• Rate and chemical name auto-fill errors are high-consequence: Auto-fill errors involving pesticide active ingredient names or application rates are among the most consequential types of data entry errors in spray records because they can result in incorrect dosage documentation, FIFRA compliance discrepancies between recorded and actual applications, and incorrect information in records produced in response to regulatory requests or civil discovery;
• Correcting auto-fill errors before finalization: If you discover an auto-fill error in a non-finalized spray record, you can correct it through the normal editing process. Once a record is finalized under Section 14.8, it cannot be altered. The time to identify and correct auto-fill errors is before you submit and finalize the record — after finalization, the record stands as submitted;
• We are not liable for any regulatory citation, FIFRA violation finding, insurance discrepancy, crop damage consequence, or other harm arising from a spray record that contains incorrect values that were auto-filled by your browser, pre-populated from a prior record, or otherwise entered without your active verification before submission.

23.19 Records Entered by Someone Else on Your Behalf — Still Your Legal Spray Record

You may authorize employees, pilots, business partners, family members, or contractors to access your DroneCommand account and enter spray records on your behalf. Under Iowa Administrative Code Chapter 45.26, the licensed pesticide applicator of record is responsible for the accuracy and completeness of spray records — not the data entry person, not the software vendor, and not a person authorized to assist with record keeping. A spray record entered into DroneCommand by any Authorized User, contractor, employee, or other person given access to your account is your spray record, binds you as the account holder under Iowa law, and is subject to all of the record-keeping obligations and liability provisions of these Terms.

• Licensed applicator responsibility cannot be delegated: Iowa law places the record-keeping compliance obligation on the licensed commercial pesticide applicator, not on whoever performed the data entry. If your employee enters a spray record with an incorrect rate, wrong chemical, or wrong field boundary, that error is your record-keeping failure under Iowa law. Your commercial pesticide applicator license is what is at risk in a regulatory inspection of your DroneCommand records — not your employee's;
• Data entry latency creates accuracy risk: When there is a time gap between when an application is performed and when a record is entered by another person — hours, days, or longer — the opportunity for error grows significantly. Entries made from memory, handwritten field notes, or verbal descriptions introduce documentation risk that we are not responsible for. Best practice is real-time record entry by the person performing the application;
• Contractor records entered in your account: If you grant a contract pilot or spray service access to your DroneCommand account to enter records for applications they performed on your behalf, those records are your records. If the contractor enters incorrect data — wrong rate, wrong chemical, wrong acreage, wrong date — that error appears in your account and is your compliance responsibility. Granting account access is your management decision and does not transfer compliance liability to the contractor;
• Audit trail does not transfer liability: DroneCommand may maintain logs reflecting which Authorized User account created or last modified each spray record. However, you remain responsible for all records in your account regardless of which specific Authorized User entered them. An audit trail showing that a specific employee entered an erroneous record does not transfer regulatory compliance liability from the license holder to that employee;
• We are not liable for any inaccurate, incomplete, or false spray record entered into your account by any Authorized User, contractor, pilot, employee, or family member — regardless of whether that person acted within or outside the scope of their authorized access when making the entry, and regardless of whether the entry was made with or without your knowledge.

23.20 Records Entered After the Fact — Retroactive Entry and Timing Accuracy

Iowa Administrative Code Chapter 45.26 requires that spray records be created within a reasonable time after an application is made. Industry practice and regulatory expectation generally treat "reasonable time" as within 24 hours of application completion, though the regulation does not specify an exact deadline. The regulation does require that the recorded application date and time reflect the actual date and time of application — not the date and time the record was entered. If you routinely enter spray records days or weeks after applications are completed, those records may be questioned during regulatory inspections for accuracy, completeness, and contemporaneity — and DroneCommand has no way to determine from a record's entry timestamp alone whether the application date and time you entered are accurate reflections of when the application actually occurred.

• Entry timestamp ≠ application timestamp: DroneCommand may record the timestamp at which a spray record was created or last saved. This entry timestamp is not the same as the application timestamp you enter into the record fields. An inspector who sees a record with an application date of three weeks prior and an entry timestamp of today may question whether the application date and other details were accurately reconstructed from memory rather than contemporaneously recorded;
• Memory-based reconstruction creates accuracy risk: Records entered from memory — without contemporaneous notes, a completed field log, or other documentation created at the time of application — are inherently less reliable than contemporaneous records. If the reconstructed record contains errors that cannot be detected because the original application notes no longer exist, those errors are permanent once the record is finalized;
• Regulatory scrutiny of backdated records: IDALS inspectors are trained to identify records that appear to have been created retroactively and to ask questions about the basis for accuracy when records appear to have been entered well after the recorded application date. While retroactive entry is not automatically prohibited, a pattern of retroactive entry combined with record inaccuracies can support an inference of inadequate record-keeping practices under Iowa law;
• Best practice is same-day entry: The most defensible spray record is one entered on the same day as the application, with details recorded at or immediately after the time of application. DroneCommand is designed to support contemporaneous record entry. Using the platform as intended — entering records promptly after each application — is your best protection against accuracy challenges during regulatory inspections;
• We are not liable for any regulatory citation, inspection finding, license action, or other consequence arising from spray records that were entered after the fact, that contain application dates or times that were inaccurately reconstructed from memory, or that an inspector concludes were not contemporaneously and accurately created.

23.21 Spray Records as Evidence Against You in Neighbor Nuisance or Trespass Litigation

If a neighboring property owner, farmer, or other party brings a nuisance, trespass, or pesticide drift claim against you, your DroneCommand spray records may become some of the most important evidence in that litigation — both for and against your position. Accurate, complete spray records establish what was applied, when, at what rate, and on which fields — providing a factual foundation for a defense based on proper application practices. However, those same records can also document facts that support the plaintiff's case, including the proximity of the application to the claimant's property, the products applied, and the conditions under which application occurred. DroneCommand records are not litigation strategy — they are factual records of what you did, and what you did is what determines your legal exposure.

• Records establish application proximity: A spray record that documents an application on a field boundary adjacent to a neighbor's property — combined with wind data, drift calculations, and plaintiff-side expert testimony — can establish the basis for a drift claim. The existence of a detailed spray record does not protect you from liability; it establishes the facts from which liability is determined;
• Records establish timing and weather conditions: Plaintiffs' attorneys in pesticide drift cases routinely obtain spray records through discovery and compare application timing against weather station records, personal weather station data, and meteorological expert testimony. A spray record showing an application during high-wind conditions — even conditions that appeared acceptable at ground level — can be used to establish negligence in drift cases;
• Missing records create an inference problem: If you fail to maintain spray records as required by Iowa law, the absence of records in litigation can create an adverse inference — that the missing records would have been unfavorable to your position. Gaps in record-keeping are not neutral; they may be treated as evidence of concealment or recklessness in civil litigation;
• Record accuracy is your best defense: Accurate, contemporaneous records that reflect proper application practices, appropriate conditions, and label-compliant rates are the strongest factual basis for defending a drift or nuisance claim. Inaccurate records — particularly records that appear to have been created to exculpate rather than to document — can be challenged as self-serving and, in the worst cases, treated as evidence of bad faith;
• We are not liable for any adverse litigation outcome, civil judgment, settlement payment, attorney fees, or other consequence arising from the content of spray records stored in DroneCommand that were produced in discovery or otherwise used as evidence in civil litigation brought against you by a neighboring property owner or other third party.

23.22 Records Deleted by You or an Authorized User — No Recycle Bin, No Recovery

DroneCommand may allow users to delete certain records — including draft records, non-finalized spray records, field entries, equipment records, customer records, or other data — through the normal user interface. When a record is deleted through the standard deletion process, it may be permanently removed from the system immediately or after a short grace period. We do not guarantee the existence of a recycle bin, trash recovery, or undelete function for any category of record. A record deleted by you or by any Authorized User may be permanently unrecoverable — and deliberately deleting a spray record that Iowa law requires you to retain for three years does not eliminate your legal obligation to have that record.

• Iowa retention obligation survives deletion: Iowa Administrative Code Chapter 45.26 requires that pesticide application records be retained for a minimum of three years from the date of application. Deleting a spray record from DroneCommand does not satisfy, extinguish, or reduce your retention obligation under Iowa law. If an IDALS inspector requests a record you deleted, the inability to produce it because you deleted it is not a defense — it is evidence of a record-keeping failure;
• Authorized user deletions are your deletions: Any Authorized User with sufficient access permissions can delete records within their permission level. A record deleted by an employee, contractor, or pilot acting within the scope of their DroneCommand access is a deletion attributable to your account. We do not track deletion intent, and an Authorized User's deletion is treated the same as an account holder deletion;
• Deliberate deletion and obstruction risk: In a regulatory investigation or civil litigation context, the deliberate deletion of records that may be relevant to an enforcement inquiry — particularly after you are aware that an inquiry may be forthcoming — can constitute obstruction of justice, spoliation of evidence, or a violation of Iowa administrative regulations, independently of any record-keeping violation the deleted records might have revealed. The deletion creates a problem; the original content created the records;
• Backup and export before deletion: Before deleting any spray record, customer record, or other operational data from DroneCommand, export the record and store it in your own records system. Even non-compliant records or records containing errors should be exported and retained — correcting an error in a record is accomplished through the editing process before finalization, not through deletion;
• We are not liable for any regulatory citation, inspection finding, litigation consequence, or other harm arising from the permanent deletion of records from DroneCommand by you or any Authorized User, including records that were required to be retained under Iowa law and that cannot be recovered after deletion.

23.23 Post-Finalization Record Amendment Not Available Through Customer Support

Once a spray record or other operational record is created and saved in DroneCommand, the record may be edited or deleted by you or your Authorized Users within the Service interface. DroneCommand's customer support team does not have the ability to alter, amend, or restore individual spray records on your behalf, and requests to modify records through customer support channels will not be fulfilled.

• No support-side record editing: Customer support agents cannot access your tenant's data to make substantive changes to spray records, field data, or application history; all record modifications must be performed through your account interface;
• Error correction is your responsibility: If you discover an error in a spray record after the fact, you must correct it yourself through the Service interface; we are not obligated to assist with, perform, or verify any such correction;
• Audit trail implications: Iowa Administrative Code Chapter 45.26 requires that spray records be accurate and contemporaneous; post-entry corrections that are not documented may raise questions about record integrity in a regulatory inspection;
• No data recovery path: Deleted records cannot be recovered; if you delete a record in error and discover the deletion after the backup retention window, no restoration path exists;
• We are not liable for any regulatory citation, inspection finding, litigation consequence, or other harm arising from your inability to amend or correct a spray record after it was saved, from our refusal to fulfill a customer support request to modify your records, or from your decision to delete records that you subsequently needed.

23.24 Data Portability, Export Format Compatibility, and Migration to Other Systems

DroneCommand provides data export functionality allowing you to download your spray records and operational data in one or more file formats. We do not warrant that exported data will be importable into, compatible with, or recognized by any other software platform, regulatory submission portal, or record-keeping system.

• Format changes without notice: The file formats, field names, column structures, and data encoding used in DroneCommand exports may change at any time; we do not guarantee that export format will remain stable or backward-compatible;
• Iowa IDALS portal compatibility: DroneCommand exports are not pre-formatted for submission to any specific Iowa Department of Agriculture and Land Stewardship portal, inspection system, or regulatory database; field mapping and reformatting for regulatory submission is your responsibility;
• Platform migration risk: If you switch from DroneCommand to another record-keeping platform, the completeness and usability of migrated records depends on the capabilities of the receiving platform; we do not guarantee successful migration;
• No perpetual export obligation: We reserve the right to modify, limit, or discontinue export functionality; you are responsible for maintaining your own copies of records exported from DroneCommand;
• We are not liable for any regulatory citation, data loss, compliance gap, or other consequence arising from exported records that were not importable into another system, not accepted by a regulatory portal, or not formatted consistently with a subsequent platform's requirements.

23.25 Authorized User Access Revocation — Former Employee Data Access Window

When an employee, contractor, or other individual who has been granted Authorized User access to your DroneCommand account leaves your organization, it is your responsibility to revoke that individual's access promptly. DroneCommand does not automatically revoke Authorized User access based on employment status, does not integrate with your HR systems, and cannot detect when a former employee's relationship with your organization has ended.

• Access persists until revoked: An Authorized User's access to your account — including the ability to view, enter, modify, and delete spray records — continues until you affirmatively revoke it through the account management interface;
• Immediate revocation required: You should revoke access for departing employees immediately upon separation, before returning company devices or disabling company email; access revocation in DroneCommand is a separate action from revoking other system access;
• Former employee record tampering: A former employee with unrevoked access could alter, delete, or export your spray records after leaving your organization; we are not responsible for monitoring access patterns or detecting suspicious activity by authorized users;
• Contractor and seasonal worker access: Seasonal employees and contractors who are granted access for a limited period should have their access revoked at the end of each season or engagement, not just at final separation;
• We are not liable for any spray record modification, data deletion, unauthorized data export, regulatory citation, or other harm resulting from access by a former employee or contractor whose Authorized User credentials you failed to revoke after their relationship with your organization ended.

23.26 Export and Third-Party Sharing of Regulatory Records — Accuracy Responsibility

Operators may export spray records from DroneCommand in PDF, CSV, or other available formats and share those exports with landowners, insurers, regulators, or legal counsel. Operators are solely responsible for verifying the accuracy and completeness of exported records before sharing with any third party.

• Point-in-time snapshots only: Exported records are point-in-time snapshots of data as it exists in the system at the time of export — they do not automatically update if underlying records are subsequently corrected, amended, or deleted after the export date;
• Operator verification required before sharing: Operators are solely responsible for verifying the accuracy and completeness of exported records before sharing with third parties including landowners, insurers, regulators, or legal counsel;
• No representation of regulatory sufficiency: DroneCommand makes no representation that exported records satisfy the specific formatting, field-completeness, authentication, or certification requirements of any regulatory agency, insurance program, court, or legal proceeding;
• Third-party reliance is the operator's risk: If a third party relies on an exported record and that record contains an error, omission, or formatting deficiency, the responsibility for that export and its consequences lies with the operator who exported and shared the record;
• We are not liable for any claim, enforcement action, insurance adjustment, coverage denial, or legal consequence arising from third-party reliance on exported records that contain errors, omissions, or formatting incompatibilities.

23.27 Record Completeness Certification — We Cannot Certify Regulatory Completeness

DroneCommand does not and cannot certify that any operator's spray records are complete, accurate, or compliant with applicable law. We will not issue any certification, letter, or document representing that an operator's records satisfy any regulatory requirement.

• No regulatory completeness certification: DroneCommand does not and cannot certify that any operator's spray records are complete, accurate, or compliant with Iowa Administrative Code Chapter 45.26 or the record-keeping requirements of any other regulatory program;
• Platform does not prevent incomplete submissions: Completeness of regulatory records depends entirely on operator entry — the platform does not prevent submission of incomplete records in all cases and does not independently verify the accuracy of entered data against external sources;
• No letters, affidavits, or certifications issued: DroneCommand will not issue letters, certifications, affidavits, compliance attestations, or other documents representing that an operator's records satisfy any regulatory requirement, regardless of how the request is framed;
• Export is reproduction, not certification: Export of records from DroneCommand is a reproduction of data as entered by the operator — it is not a certification of regulatory compliance, record completeness, or data accuracy;
• We are not liable for any enforcement action, audit finding, civil penalty, or compliance determination arising from any representation — by the operator or any third party — that DroneCommand records are complete or compliant with applicable law.

24. Privacy

Our collection and use of personal information in connection with the Service is governed by our Privacy Policy, which is incorporated into these Terms by reference. By using the Service, you consent to our collection, use, and sharing of your information as described in the Privacy Policy. Please review the Privacy Policy carefully before using the Service.

25. Disclaimer of Warranties

26. Limitation of Liability

27. Indemnification

You agree to defend, indemnify, and hold harmless Country Road Drone Services, LLC and its members, managers, officers, employees, agents, contractors, successors, and assigns (collectively, "Indemnified Parties") from and against any and all claims, actions, demands, liabilities, damages, losses, fines, penalties, costs, and expenses (including reasonable attorneys' fees and litigation costs) arising out of or relating to:

• Your use of the Service or any Authorized User's use of the Service;
• Your violation of these Terms or any applicable law or regulation;
• Your violation of any third party's rights, including intellectual property rights, privacy rights, or property rights;
• Your spray operations, including but not limited to chemical drift, off-target application, crop damage to third parties, beekeeper claims, neighboring landowner claims, and environmental contamination;
• Your failure to obtain or maintain required FAA certifications, state pesticide applicator licenses, or other regulatory authorizations;
• Your failure to comply with any applicable federal, state, or local law or regulation governing drone operations, pesticide application, environmental protection, or worker safety;
• Regulatory investigations, audits, fines, or penalties arising from your operations or your record-keeping practices;
• Claims by your employees, pilots, or contractors arising from your use of the Service, including payroll data processing and time record disputes;
• Claims by landowners, farmers, or other customers arising from your spray services;
• Any fraudulent, abusive, or illegal activity by you or any Authorized User;
• User Data you submit to the Service, including any claim that such data infringes third-party rights.

We reserve the right, at your expense, to assume exclusive control of the defense of any matter subject to indemnification by you, and you agree to cooperate with our defense. You may not settle any claim subject to indemnification without our prior written consent.

Indemnification Carve-Out for Our Own Fault: Notwithstanding the broad indemnification obligations above, you are not required to indemnify, defend, or hold us harmless for claims arising directly and primarily from: (a) our own gross negligence or intentional misconduct; (b) a material breach by us of these Terms; or (c) a defect in the Service that was the direct and proximate cause of the third-party harm, independent of your operational decisions. In cases where a third-party claim arises from a combination of our software defect and your operational decision, responsibility shall be allocated proportionally based on the relative causal contribution of each. This carve-out does not apply where a software feature functioned as described and the harm arose from your independent operational decision, input error, or misuse of the Service.

28. Force Majeure

We will not be liable for any delay, failure, or interruption in the performance of our obligations under these Terms to the extent such delay or failure is caused by circumstances beyond our reasonable control, provided we notify you promptly and use commercially reasonable efforts to mitigate the impact. Force Majeure Events include:

• Acts of God, including earthquakes, floods, fires, severe weather events, hurricanes, tornadoes, and ice storms;
• Epidemic or pandemic declared by a recognized public health authority;
• Acts of war, terrorism, invasion, insurrection, riot, or civil unrest;
• Government orders, embargoes, sanctions, or regulatory actions that directly prevent us from operating;
• Nationwide or region-wide labor strikes or lockouts affecting our industry;
• Major failures of the public power grid or telecommunications backbone infrastructure affecting multiple geographic regions and multiple unrelated providers simultaneously (routine internet service disruptions, single-provider outages, or ordinary network congestion are not Force Majeure Events);
• Cyberattacks, distributed denial-of-service attacks, ransomware attacks, or other malicious attacks on our infrastructure. The fact that cyberattacks are a foreseeable category of threat for any internet-connected business does not render any specific attack foreseeable or preventable. A specific attack qualifies as a Force Majeure Event where it: (a) exploits a vulnerability or uses an attack vector that was not publicly documented in widely-used threat intelligence sources (including CISA advisories, the CVE database, or equivalent security bulletins) as of the date of the attack; or (b) is of a scale, persistence, or sophistication that a reasonably prudent SaaS provider of our size, exercising commercially reasonable security investment and practices, could not have prevented. Common attack categories that are widely known and documented — such as phishing emails, credential stuffing, SQL injection, and known ransomware strains — are foreseeable categories, but a specific novel variant, campaign, or targeted exploitation of our specific infrastructure may still qualify if it meets the criteria above. A cyberattack resulting directly from our gross negligence in security practice — including: knowingly operating with unpatched software for which a patch has been publicly available for thirty (30) or more days; failure to use transport-layer encryption; or storing plaintext credentials — is NOT a Force Majeure Event;
• Failure of critical third-party infrastructure providers (cloud hosting, DNS, etc.) where such failure is outside our reasonable control and not caused by our own negligence in vendor selection or contract management;
• Any other event that: (a) is genuinely beyond our reasonable control; (b) could not have been anticipated and planned for by a reasonable business; and (c) cannot be mitigated through commercially reasonable alternative arrangements.

For the avoidance of doubt, the following are NOT Force Majeure Events: ordinary software bugs or errors; routine planned maintenance; server capacity issues arising from failure to scale appropriately; third-party service failures that were reasonably foreseeable or for which reasonable backup arrangements exist; or business decisions by us (such as discontinuing a feature).

In the event of a Force Majeure Event, we will use commercially reasonable efforts to restore Service. Communication During Force Majeure: During any Service outage lasting more than four (4) hours — whether or not caused by a Force Majeure Event — we will post status updates to our status page at intervals not exceeding four (4) hours, describing the known cause, estimated restoration timeline (if known), and steps being taken. This communication commitment is separate from liability for the outage itself; failure to post a status update does not create additional liability but demonstrates our good-faith obligation to keep you informed. Our obligations under these Terms are suspended only to the extent directly prevented by the Force Majeure Event. This Section does not excuse your payment obligations.

See also Section 55 for additional force majeure provisions.

29. Governing Law and Venue

Governing Law: These Terms and any dispute arising hereunder shall be governed by and construed in accordance with the laws of the State of Iowa, without regard to its conflict of law principles, and to the extent applicable, the Federal Arbitration Act.

Venue: Subject to the mandatory arbitration provisions of Section 31, any legal proceeding not subject to arbitration shall be brought exclusively in the state or federal courts located in Iowa, and you hereby consent to the personal jurisdiction and venue of such courts and waive any objection to jurisdiction or venue.

Mandatory State Consumer Protection Laws: The Iowa governing law provision does not apply to the extent it would deprive a resident of another U.S. state of rights under mandatory consumer protection statutes of that state that cannot lawfully be waived by contract. Specifically: (a) California residents retain rights under California mandatory consumer protection law (including the California Consumer Legal Remedies Act, California Unfair Competition Law, and the California Consumer Privacy Act) to the extent those rights cannot be contractually waived; (b) we do not use Iowa law as a mechanism to deprive residents of other states of statutory rights they cannot waive. This provision does not create any additional obligations on us beyond those required by applicable mandatory law.

30. Beta and Preview Features

From time to time, we may offer beta, preview, early access, or experimental features ("Beta Features"). Beta Features are provided "AS IS" with no warranty whatsoever, are not covered by any service level target, and may be modified, suspended, or discontinued at any time without notice or liability. You use Beta Features at your sole risk.

Critical Warning Regarding Beta Features: NEVER use a Beta Feature as the sole or primary basis for any of the following: spray application rate calculations; compliance record generation or submission; job dispatch or crew safety operations; chemical inventory tracking where accuracy is critical; acreage billing; or any other operation where a data error could cause financial loss, regulatory violation, physical harm, or environmental damage. Beta Features may contain significant bugs, produce incorrect outputs, lose data without warning, or behave unpredictably. Maintain independent verification and independent records for any operation where a Beta Feature error could cause harm. If you use a Beta Feature in conjunction with an operation that results in loss, your use of a Beta Feature is an assumption of all associated risks, and our liability is limited to the maximum extent permitted by applicable law — which in many jurisdictions permits full exclusion of liability for knowingly assumed risk of a clearly-labeled experimental feature. In any jurisdiction where some minimum liability cannot be excluded, our liability for Beta Feature losses is limited to the lesser of (i) actual direct losses proven to have been caused solely and directly by a specific Beta Feature defect (not by your independent operational decisions using that output), or (ii) the cap in Section 26(B).

30.1 Beta Features Toggle — Account-Wide Election

• Enabling the Beta Features toggle in account settings constitutes an affirmative election to use Beta Features with full knowledge of the disclaimers in this Section 30. By enabling the toggle, you acknowledge that you have read and understood the critical warnings above;
• The account administrator is responsible for monitoring and controlling the Beta Features toggle for all Authorized Users under the account. If any Authorized User enables the Beta Features toggle, the election applies to all users operating under that account — the toggle is an account-level setting, not a per-user setting;
• Disabling the Beta Features toggle does not retroactively affect records, calculations, or data created while Beta Features were enabled. Such records remain subject to the disclaimers in this Section regardless of the toggle's current state;
• Records created using Beta Features are subject to the disclaimers in this Section regardless of whether Beta Features are subsequently disabled. Disabling the toggle after a record has been created does not alter the nature or reliability of that record.

31. Dispute Resolution; Mandatory Arbitration; Class Action Waiver

31.1 Informal Resolution

Before initiating any formal legal proceeding, you agree to first contact us at [email protected] to attempt to resolve the dispute informally. You agree to give us thirty (30) days from the date of your written notice to attempt to resolve your claim before initiating arbitration. This informal resolution requirement is a condition precedent to arbitration. Deemed Satisfied: If we fail to send any substantive written response to your informal dispute notice within thirty (30) days of receipt, the informal resolution condition precedent is deemed satisfied and you may immediately initiate arbitration without further delay. A "substantive written response" means a response that acknowledges the specific claim and either: (a) proposes a resolution; (b) requests additional information to evaluate the claim; or (c) denies the claim with a stated reason. An auto-reply, read receipt, or generic acknowledgment does not constitute a substantive response. You bear the burden of proving that your notice was sent to [email protected] and received (e.g., by email delivery confirmation or read receipt).

31.2 Binding Arbitration

Except as described in Section 31.3, all disputes, claims, or controversies arising out of or relating to these Terms, the Service, our Privacy Policy, or your relationship with Country Road Drone Services, LLC — including disputes regarding the existence, validity, interpretation, performance, breach, or termination of these Terms — shall be resolved by binding individual arbitration administered by the American Arbitration Association ("AAA") under its Consumer Arbitration Rules (for individual consumers) or its Commercial Arbitration Rules (for businesses), each as in effect at the time the arbitration is commenced and available at www.adr.org. The enforceability of this arbitration agreement is governed by the Federal Arbitration Act (9 U.S.C. § 1 et seq.), not by state arbitration law, except to the extent the FAA is inapplicable.

The arbitration shall be conducted in English and decided by a single neutral arbitrator. For claims of $50,000 or less, arbitration shall be conducted by telephone or video conference unless both parties agree to in-person proceedings or the arbitrator orders otherwise for good cause; for claims over $50,000, the arbitration shall be seated in Iowa. The arbitrator shall have the authority to award any relief that a court could award, including injunctive or declaratory relief, subject to the limitations in these Terms. Judgment on any arbitration award may be entered in any court of competent jurisdiction.

AAA filing fees and arbitrator fees shall be allocated in accordance with the applicable AAA rules, except that in any arbitration you initiate, we will pay all AAA fees (including filing fees and arbitrator compensation) for claims under $10,000, provided the claim is not frivolous as determined by the arbitrator. Each party shall bear its own attorneys' fees in arbitration except where applicable law requires otherwise or where the arbitrator finds a claim or defense was brought or maintained in bad faith.

31.3 Exceptions to Arbitration

Notwithstanding the foregoing, the following are not subject to arbitration and may be pursued in court:

• Claims seeking emergency or temporary injunctive relief to prevent irreparable harm, pending a determination by arbitration on the merits;
• Claims within the jurisdictional limit of the applicable small claims court in the state where you reside or where the claim arose, as that limit is set by law from time to time — for Iowa residents, this is the current Iowa Small Claims Court jurisdictional limit (Iowa Code § 631.1, as amended), provided the claim is individual and not brought as a class action;
• Claims by either party to enforce or protect intellectual property rights;
• Filing of complaints with government agencies, including the FAA, EPA, IDALS, Iowa Attorney General, or any consumer protection agency — these Terms do not prohibit you from filing regulatory complaints or cooperating with government investigations.

31.4 Class Action Waiver

YOU AND COUNTRY ROAD DRONE SERVICES, LLC EACH WAIVE THE RIGHT TO PARTICIPATE IN A CLASS ACTION LAWSUIT OR CLASS-WIDE ARBITRATION. ALL DISPUTES MUST BE BROUGHT ON AN INDIVIDUAL BASIS ONLY. NO ARBITRATION OR COURT PROCEEDING SHALL BE JOINED, CONSOLIDATED, OR CONDUCTED AS A CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE ACTION. THE ARBITRATOR HAS NO AUTHORITY TO CONDUCT CLASS ARBITRATION OR AWARD CLASS-WIDE RELIEF.

If this class action waiver is found to be unenforceable in a particular case, and the only way to proceed as a class would be through litigation rather than arbitration, then the class claim(s) shall proceed in court, but all individual claims shall remain subject to binding individual arbitration.

31.5 Arbitration Opt-Out

You may opt out of the binding arbitration and class action waiver provisions of this Section by sending written notice to [email protected] within thirty (30) days of: (a) the date you first create a DroneCommand account; or (b) the date these Terms become effective (if you are an existing user at the time of an update that adds this arbitration provision). Your opt-out notice must include your full name, account email address, and a statement that you wish to opt out of the arbitration provision. Opting out does not affect any other provision of these Terms. If you opt out, disputes shall be resolved in the courts identified in Section 29.

31.6 Severability of Arbitration Provisions

If any part of this Section 31 (other than the class action waiver in Section 31.4) is found unenforceable, the remainder of this Section shall continue to apply. If the class action waiver is found unenforceable, the entirety of Section 31.2 (binding arbitration) shall be null and void, and disputes shall be resolved in the courts identified in Section 29.

See also Section 90 for additional arbitration and dispute resolution provisions.

32. Statute of Limitations

ANY CLAIM OR CAUSE OF ACTION ARISING OUT OF OR RELATING TO THESE TERMS, THE SERVICE, OR YOUR USE OF THE SERVICE MUST BE FILED WITHIN ONE (1) YEAR AFTER THE DATE ON WHICH THE CLAIMANT KNEW OR REASONABLY SHOULD HAVE KNOWN OF THE CLAIM OR CAUSE OF ACTION, REGARDLESS OF ANY STATUTE OR LAW TO THE CONTRARY. IF NOT FILED WITHIN ONE YEAR, THE CLAIM IS PERMANENTLY BARRED.

The foregoing one-year limitations period does not apply to: (a) claims by us to collect outstanding fees or subscription charges; (b) claims by us to enforce intellectual property rights; (c) claims arising under a federal or state statute that expressly prescribes its own non-waivable limitations period, including: the Iowa Consumer Fraud Act (Iowa Code Chapter 714H); the Nebraska Uniform Deceptive Trade Practices Act (Neb. Rev. Stat. § 87-301 et seq.); the South Dakota Deceptive Trade Practices Act (SDCL § 37-24); the federal Electronic Fund Transfer Act (15 U.S.C. § 1693 et seq.); the Fair Labor Standards Act (29 U.S.C. § 255, which prescribes a two-year limitations period, or three years for willful violations — the contractual one-year period does not apply to FLSA claims); the Americans with Disabilities Act (42 U.S.C. § 12117); Title VII of the Civil Rights Act (42 U.S.C. § 2000e-5); the Age Discrimination in Employment Act (29 U.S.C. § 626); the Iowa Civil Rights Act (Iowa Code Chapter 216); and similar federal and state employment and civil rights statutes of any jurisdiction — for such statutory claims, the applicable non-waivable statutory period governs those claims only; or (d) claims that cannot lawfully be subject to a shortened limitations period under applicable mandatory law.

33. Modifications to Service or Terms

33.1 Changes to Terms

We reserve the right to modify these Terms at any time. For material changes, we will provide notice via at least one of the following methods: (a) email to the address on file for your account at least thirty (30) days before the changes take effect; or (b) a prominent in-app notification displayed within the Service when you log in, at least thirty (30) days before the changes take effect. We will make commercially reasonable efforts to use both methods for Material Adverse Changes as defined in Section 33.1. For non-material changes (such as clarifications, corrections, reorganization without substantive change, or changes required by law), we may update the Terms with shorter notice using either method. The "Last Updated" date at the top of this document will always reflect the most recent revision.

Your responsibility to monitor for changes: You are responsible for keeping your email address current and for monitoring for in-app notifications. If you claim you did not receive email notice of a change, we will not be liable where: (a) the notice was sent to your address on file and bounced or was filtered as spam; or (b) in-app notice was displayed for thirty (30) or more days and you did not log in during that period. We strongly recommend logging into the Service at least once per month during active subscription periods.

Your continued use of the Service after a change to these Terms takes effect constitutes your acceptance of the revised Terms. If you disagree with the revised Terms, you must stop using the Service and cancel your subscription before the new Terms take effect.

Special Protection for Prepaid Subscribers — Material Adverse Changes: If we make a change to these Terms that falls within the definition of a "Material Adverse Change" (defined below), and you: (a) notify us at [email protected] within thirty (30) days of our notice of the change; (b) have an active prepaid Annual, 2-Year, or 4-Year subscription at the time of the change; and (c) affirmatively object to the specific Material Adverse Change, then you may cancel your subscription and receive a prorated refund calculated based on the number of full months remaining in your prepaid term.

A "Material Adverse Change" means a change to these Terms that: (i) removes or materially degrades a core Service feature that was expressly included in your subscription plan at the time you subscribed — where "expressly included" means a feature that was: (A) listed in the published subscription plan feature description on the DroneCommand website or pricing page at the time of your subscription; or (B) functionally available, consistently provided, and reasonably relied upon as a core component of the Service for a continuous period of not less than twelve (12) months before the change — and "materially degrades" means a reduction in functionality that is not merely a redesign of how the feature is accessed or presented but rather a substantial reduction in the actual capability the feature provided; or (ii) removes the 30-day money-back guarantee; or (iii) shortens the post-cancellation data retention window below 30 days. The following are expressly excluded from the definition of Material Adverse Change and do not trigger the refund right: subscription pricing changes at renewal; adding new features or terms; adding, removing, or changing third-party integrations; changes to security practices; adding or clarifying disclaimers and limitations; changes required by applicable law; and changes that are immaterial or that do not adversely affect Customer's substantive rights. The definition of "Material Adverse Change" is objective — it is not determined by our sole discretion but by whether the change falls within the above criteria, subject to arbitration under Section 31 if disputed.

33.2 Changes to Service

We reserve the right to modify, update, add, remove, or discontinue any feature or aspect of the Service at any time. We will use commercially reasonable efforts to provide advance notice of significant feature changes or discontinuations. We are not liable for any harm resulting from Service changes.

34. General Provisions

34.1 Entire Agreement

These Terms, together with the Privacy Policy and any other policies or agreements incorporated herein by reference, constitute the entire agreement between you and Country Road Drone Services, LLC with respect to the Service and supersede all prior and contemporaneous agreements, representations, warranties, and understandings, whether written or oral, between the parties.

Marketing Materials and Pre-Contract Representations: You acknowledge that you have not relied on any statement, representation, warranty, feature description, or promise made in our marketing materials, website content, product demonstrations, sales conversations, email correspondence, support interactions, social media posts, blog posts, or any other pre-contractual communication in deciding to use or continue using the Service, except to the extent expressly stated in these Terms. All marketing descriptions of features, compliance capabilities, availability, and reliability are business descriptions only and do not constitute warranties, conditions, or terms of this agreement. The parol evidence rule applies: no external evidence of prior or contemporaneous oral agreements or representations may be used to vary, supplement, or contradict the written terms herein. Nothing in this paragraph limits liability for fraud or fraudulent misrepresentation.

Sales Conversations, Demos, and Support Communications Do Not Create Obligations: No representation made by us or on our behalf in any of the following creates any contractual obligation, warranty, service level commitment, or modification of these Terms: (a) product demonstration or sales call; (b) email correspondence from any address at our domain before you subscribed; (c) live chat support interactions; (d) social media responses or direct messages; (e) phone support calls; (f) help documentation or knowledge base articles; (g) webinars or training sessions; or (h) any other informal communication. No employee, contractor, or support representative of ours has authority to verbally modify these Terms, make pricing promises, guarantee specific availability or uptime, commit to regulatory compliance for your specific operations, or create any obligation not expressly stated in these Terms. Any such representation, if made, is void and unenforceable. If you believe you were promised something material that is not in these Terms, do not subscribe based on that promise — contact us to get it in writing before committing.

34.1b Product Roadmaps and Future Feature Announcements — No Subscription Commitment

We may publish product roadmaps, feature previews, "coming soon" announcements, development timelines, release notes discussing upcoming features, or other forward-looking product information on our website, blog, social media, or in product communications. Nothing in any product roadmap, future feature announcement, or development preview creates any obligation for us to deliver any described feature by any date, at all, or as described. Specifically:

• If you subscribe to DroneCommand in anticipation of a feature listed as "coming soon," "planned," or "in development," you are subscribing for the Service as it exists today — not for the anticipated future version;
• Roadmap items may be delayed, deprioritized, redesigned, or cancelled without notice and without liability to you;
• A feature appearing on a roadmap is not a promise to deliver that feature and does not constitute a material term of your subscription agreement;
• The failure to deliver a roadmap item — regardless of how prominently it was announced, how long it has been listed, or how much you relied on it in your subscription decision — does not constitute a Material Adverse Change under Section 33.1, a breach of these Terms, or grounds for a refund outside the 30-day Guarantee Period;
• This provision applies to roadmaps communicated in any form: website pages, social media posts, email newsletters, in-app notifications, sales calls, trade show presentations, or any other channel. The entire agreement between us is what is written in these Terms — nothing on a roadmap is incorporated herein;
• If a feature was listed on a roadmap and we subsequently announce we will not be building it, that announcement is not a Material Adverse Change — it is a product decision.

34.2 Severability

If any provision of these Terms is found to be invalid, illegal, or unenforceable by a court of competent jurisdiction or arbitrator, the invalid provision shall be modified to the minimum extent necessary to make it enforceable, or if modification is not possible, severed from the Terms. The remaining provisions shall remain in full force and effect.

34.3 No Waiver

Our failure to enforce any right or provision of these Terms shall not constitute a waiver of that right or provision. A waiver of any right or provision must be in writing signed by an authorized representative of Country Road Drone Services, LLC to be effective.

34.4 Assignment

You may not assign, transfer, delegate, or sublicense your rights or obligations under these Terms without our prior written consent, and any attempted assignment without such consent is void. We may assign these Terms and our rights and obligations hereunder, in whole or in part, including in connection with a merger, acquisition, sale of assets, reorganization, or by operation of law, subject to the following conditions: (a) Assumption of Obligations: Any assignee of these Terms will, as a condition of assignment, assume all of our obligations to you under these Terms, including all data protection obligations, conflict of interest commitments under Section 35, and service discontinuation commitments under Section 46. Our obligations to you do not evaporate upon assignment — the assignee inherits them. (b) Notice to You: We will provide email notice to your account's email address within thirty (30) days following any assignment, identifying the assignee. However, failure to provide this notice does not invalidate the assignment or create any additional liability beyond providing the notice promptly upon discovery of the omission. (c) Pricing Protection: An assignment of these Terms does not entitle the assignee to change your subscription pricing mid-term. Any price changes by an assignee are subject to the same 60-day notice requirement in Section 6.3. (d) Substantive Service Quality: Assignment to a successor is not a basis for us to unilaterally terminate our service obligations to you; if an assignee causes a Material Adverse Change, your rights under Section 33.1 apply against the assignee. Any assignment by us does not relieve you of your obligations under these Terms.

34.5 Notices

All notices, requests, demands, and other communications from you to us shall be in writing and sent to [email protected]. Notices from us to you will be sent to the email address on file for your account or posted within the Service. Email notice is deemed effective upon transmission. You are responsible for keeping your email address current; we are not liable for notices that fail to reach you due to an outdated email address.

34.6 Relationship of Parties

These Terms do not create a partnership, joint venture, employment, agency, or franchise relationship between you and Country Road Drone Services, LLC. You are an independent contractor (in a business relationship context) with no authority to bind us.

34.7 No Third-Party Beneficiaries

These Terms are for the sole benefit of the parties hereto and their permitted successors and assigns. Nothing in these Terms shall create or be deemed to create any right, remedy, or claim of any kind in any third party, including without limitation: neighboring landowners or property owners; beekeepers or apiary operators; organic or specialty crop farmers; your customers or clients (landowners, farm operators, or others who receive your spray services); your employees or contractors; environmental organizations; or any government agency. No third party may rely on the DriftWatch disclaimer, weather data disclaimer, mix calculator disclaimer, or any other provision of these Terms as creating a duty of care owed by us to that third party. Claims by third parties arising from your spray operations are solely your responsibility under Section 27 (Indemnification).

34.8 Headings

Section headings in these Terms are for convenience only and have no legal effect.

34.9 Export Compliance

You represent that you are not located in a country subject to U.S. government embargo or that has been designated as a "terrorist-supporting" country, and that you are not on any U.S. government list of prohibited or restricted parties. You agree to comply with all applicable U.S. export control laws in connection with your use of the Service.

34.10 U.S. Government Users

The Service is a "commercial item" as defined at 48 C.F.R. § 2.101. Government users acquire the Service with only those rights provided to commercial customers in these Terms.

34.11 Regulatory Agencies Are Not Our Partners — We Have No Formal Relationship With IDALS, FAA, or EPA

DroneCommand references Iowa Administrative Code Chapter 45.26, FAA Part 107, FIFRA, and other regulations in our marketing materials, Terms, and product documentation to describe the regulatory context in which our customers operate. These references do not indicate, imply, or suggest that we have any formal relationship, partnership, endorsement, approval, or cooperation agreement with IDALS, the FAA, the EPA, or any other state or federal regulatory authority.

• No endorsement: Neither IDALS, nor the FAA, nor the EPA, nor any other government agency has reviewed, approved, endorsed, or certified DroneCommand as a compliant record-keeping platform for any regulatory purpose. Any use of regulatory citation in our materials is for informational context only — not an endorsement claim;
• No advance determination: We have not received any advance determination, advisory opinion, no-action letter, or equivalent from any regulatory authority confirming that DroneCommand records satisfy any specific regulatory requirement. Compliance determinations are made by inspectors and enforcement officers applying regulatory standards to actual records at the time of inspection;
• Regulatory information may be outdated: Any regulatory descriptions in our Terms, marketing materials, or product documentation reflect our understanding at the time of writing. Regulations change, and our descriptions may not reflect current regulatory requirements. Do not rely on our descriptions as a source of regulatory guidance — consult the applicable regulatory authority directly;
• We cooperate but we are not agents: Our cooperation with regulatory legal process (Section 40) and whistleblower investigations (Section 66) does not make us an agent, partner, or extension of any regulatory authority. We are a private software company that complies with legal obligations — not a regulatory body or compliance certifier;
• Any implication that DroneCommand has been reviewed by, approved by, or is in any way affiliated with IDALS, the FAA, the EPA, or any other governmental body is unintended, and we disclaim any such implication.

34.12 Tooltips, Help Text, In-App Guidance, and Plain-Language Summaries Do Not Modify These Terms

DroneCommand includes contextual help features — tooltips, help text bubbles, in-app guidance overlays, tutorial walkthroughs, onboarding screens, knowledge base articles, and plain-language summaries of regulatory requirements — that are designed to assist users in navigating the software and understanding their general compliance context. These features are educational conveniences provided as a courtesy. Nothing in any tooltip, help text, in-app guidance overlay, tutorial, onboarding screen, knowledge base article, support documentation, chatbot response, or plain-language regulatory summary published by us constitutes a modification of these Terms, a legal compliance guarantee, a regulatory opinion, or a representation that reliance on the guidance will satisfy any applicable legal requirement.

• Plain-language regulatory summaries are approximations: When DroneCommand displays plain-language summaries of Iowa pesticide record-keeping requirements, FAA Part 107 rules, FIFRA provisions, or other regulatory topics, those summaries are simplifications of complex law intended for user convenience. They may not reflect the most recent regulatory amendments, agency interpretive guidance, or applicable case law. These summaries should never substitute for consulting the full text of applicable law, a licensed attorney, or a certified crop advisor;
• Tooltips and help text are user interface elements, not contract terms: Nothing in the user interface — no tooltip, no help icon, no required-field indicator, no success message, no green checkmark, no "record saved" confirmation — constitutes a contractual representation that the data you have entered satisfies any legal record-keeping requirement. UI elements are navigational aids and operational confirmations, not regulatory compliance certifications;
• Knowledge base articles may become outdated: Articles published on our help center, support portal, or website may not be updated in real time as regulations change. We do not commit to maintaining knowledge base articles in synchronization with regulatory amendments. Regulatory citations appearing in help center articles should be independently verified against current law and current agency guidance before any compliance reliance;
• AI assistant and chatbot responses: If DroneCommand provides any AI-powered assistant, chatbot, or automated support feature, responses generated by those tools are subject to all of the disclaimers in this Section and throughout these Terms. AI-generated responses may contain errors, may not reflect current law, and do not modify these Terms in any respect regardless of how specific, authoritative, or responsive they appear;
• We are not liable for any regulatory violation, license consequence, crop damage, financial loss, or other harm arising from reliance on any tooltip, help text, in-app guidance message, plain-language regulatory summary, knowledge base article, tutorial, onboarding screen, or other non-Terms content published by us, regardless of how prominently that content was displayed or how regulatory-specific its language appeared.

35. Conflict of Interest Disclosure — Separation of Operations

Country Road Drone Services, LLC operates two distinct business lines: (1) DroneCommand, a cloud-based SaaS platform for agricultural drone spray operators; and (2) CRDS drone spray services, which provides commercial agricultural drone spray services in Iowa, Nebraska, and South Dakota.

We recognize that DroneCommand customers who are also active spray operators may be concerned about whether their operational data — including field locations, customer lists, spray records, acreage, and pricing — could benefit our own spray services business. We therefore make the following binding commitments:

• Strict data separation: User Data submitted to DroneCommand by any Customer is not accessed by, shared with, or used in any way by our drone spray services operations;
• No competitive use: We will not use any Customer's field locations, customer lists, landowner names, pricing, acreage data, or spray records to identify or solicit customers for our own spray services business;
• No competitive intelligence: We do not use aggregate DroneCommand data, usage patterns, or market intelligence derived from Customer data to gain competitive advantage in our drone spray services business;
• Operational firewall: Personnel who have access to DroneCommand Customer data in their capacity as platform operators do not make spray services sales decisions using that data.

These commitments are part of these Terms and are enforceable. Breach of these commitments by us is a material breach of these Terms. If you believe we have violated these commitments, contact us at [email protected] with a description of the alleged violation.

Verification Mechanism: Upon your written request, our LLC manager or a designated officer will provide a written certification within ten (10) business days confirming whether, to the best of their knowledge following a reasonable internal inquiry, your specific User Data has been accessed or used in violation of these commitments. If you initiate arbitration under Section 31 asserting a violation of this Section 35, you are entitled to seek discovery of: (a) system access logs showing who accessed your data and when; and (b) relevant internal communications between DroneCommand platform personnel and CRDS drone spray services personnel, to the extent permitted by the applicable AAA arbitration rules. Remedies: If we breach these Section 35 commitments and you suffer provable damages, your remedies include: actual damages proven in arbitration; and the right to terminate your subscription and receive a prorated refund of any prepaid term, regardless of whether the harm constitutes a Material Adverse Change under Section 33.1.

35.2 Data Access Logging for Conflict of Interest Verification

To support the enforcement and verification mechanism described in Section 35, we maintain access logs recording which users or system processes accessed Customer data and when. We will retain these access logs for a minimum of three (3) years from the date of each access event. These logs are: (a) maintained as a standard operational security practice; (b) available for inspection in connection with a legitimate conflict of interest claim under Section 35 through the discovery mechanism described therein; and (c) not available for general customer inspection as routine requests (access log review is available only in the context of a bona fide Section 35 dispute). We acknowledge that log completeness depends on our technical implementation and that in the event of a catastrophic system failure, some logs may not be recoverable — but we commit to log retention as a standard practice and not as an aspirational goal. If our logging systems fail for a period exceeding forty-eight (48) hours, we will note the gap and the reason in our internal records, and those records are also subject to discovery in a Section 35 dispute.

36. Artificial Intelligence and Machine Learning

No AI Training Without Express Consent: We will not use your User Data — including spray records, field data, customer information, employee records, inventory data, or any other operational data — to train, fine-tune, or develop artificial intelligence or machine learning models (including large language models, predictive analytics models, or any other AI/ML system) without your express, affirmative opt-in consent.

Definition of "Express Opt-In Consent" for AI Training: For purposes of this Section, express opt-in consent means your separate, affirmative action in response to a clearly labeled, standalone disclosure that: (a) specifically identifies what categories of your User Data will be used; (b) specifically identifies the AI purpose (e.g., "training a crop yield prediction model"); and (c) is presented as a separate, non-pre-checked checkbox or equivalent affirmative step distinct from your acceptance of these Terms. The following do NOT constitute express opt-in consent for AI training purposes: acceptance of these Terms; continued use of the Service; clicking through any notification that does not meet the above criteria; or a pre-checked "I agree" checkbox of any kind.

Aggregate and Anonymized Data: The prohibition on AI training without consent applies even to data that has been aggregated with other customers' data or de-identified, to the extent such data could reasonably be reverse-engineered or re-identified to reveal your identity, your customers' identities, your operational patterns, geographic footprint, or pricing. We will not use de-identified or aggregated datasets derived from your User Data for AI model training if a reasonable data scientist, applying common re-identification techniques, could determine that the data originated from your operations.

AI Features: If we introduce features powered by artificial intelligence or machine learning that process your User Data, we will: (a) clearly label such features as AI-powered; (b) describe what data they use and how; (c) obtain your consent before processing your data in that way if required by applicable law; and (d) provide an opt-out mechanism. AI-powered features are subject to all disclaimers in Section 25 (Disclaimer of Warranties) and Section 26 (Limitation of Liability). AI-generated suggestions, recommendations, outputs, and analyses are for informational purposes only and do not constitute professional advice.

Third-Party AI: If a third-party AI service (such as an AI API provider) is used to power any feature of DroneCommand, we will disclose this in our subprocessor list (Privacy Policy Section 8) and update these Terms. We will not transmit your User Data to third-party AI services without updating this disclosure.

AI-Generated Content Is Not Authoritative Record Data: If we introduce AI-powered features that generate summaries, analysis, dashboards, season recaps, compliance checklists, or any other content derived from your records, such AI-generated content: (a) is for informational and convenience purposes only; (b) is not a substitute for the underlying raw data records in the Service; (c) may contain inaccuracies, omissions, or "hallucinations" (fabricated content) that do not reflect your actual records; and (d) must never be relied upon as the authoritative version of any regulatory record for any legal, regulatory, insurance, or other official purpose. The only authoritative version of your records is the underlying raw data accessible through Settings → Export Data — not any AI-generated summary, analysis, or report. We are not liable for any loss, regulatory fine, insurance denial, or other harm arising from reliance on AI-generated content instead of the underlying record data.

36.1 AI-Generated Content in Insurance Claims, Regulatory Submissions, and Legal Proceedings

CRITICAL WARNING — AI SUMMARIES ARE NOT OFFICIAL RECORDS: If we introduce AI-powered features such as season summaries, compliance checklists, audit-ready reports, or other AI-generated documents, those documents must NEVER be submitted in connection with any of the following without independent verification against the underlying raw data:

• Crop insurance claims or loss adjustment submissions — including ARC/PLC program records, crop insurance indemnity claims, or FSA reporting;
• State or federal pesticide application compliance records — including records submitted to IDALS, EPA, or any state pesticide regulatory authority;
• FAA incident or accident reports;
• Legal filings, court exhibits, sworn affidavits, or declarations;
• Wage and hour records submitted in any employment proceeding.

AI-generated content may contain hallucinations — fabricated dates, quantities, product names, field identifiers, or other data that does not exist in your underlying records. We are not liable for any penalty, fine, claim denial, fraud investigation, regulatory action, or legal liability arising from your submission of AI-generated content in any official proceeding or claim. Submitting fabricated AI-generated data in a government filing, insurance claim, or legal proceeding may constitute fraud, regardless of your intent — verify everything against the raw data export before submitting. This warning supplements and does not replace the disclaimer in Section 36 (final paragraph) regarding AI-generated content generally.

36.2 SMS and Email Notification Reliability — No Guarantee of Delivery

DroneCommand may send SMS text messages and email notifications for account events including trial expiration warnings, billing failures, weather alerts, and system notifications. Delivery of these communications is subject to factors outside DroneCommand's control, and non-receipt does not extend any deadline or modify any obligation under these Terms.

• Delivery is not guaranteed: Delivery of SMS and email notifications is subject to carrier routing, spam filtering, recipient device status, number portability issues, and other factors outside DroneCommand's control — we do not warrant that any specific notification will be received within any specific time frame or at all;
• Maintain current contact information: Operator is responsible for maintaining a current, valid mobile telephone number and email address in their account settings at all times — communications sent to outdated contact information are deemed delivered as of the time of sending;
• Non-receipt does not extend deadlines: Non-receipt of an SMS or email notification — whether due to carrier filtering, spam foldering, device issues, or any other reason — does not extend any trial period, cure any payment failure, waive any late fee, or modify any obligation under these Terms;
• Critical decisions require active monitoring: Operators with time-sensitive regulatory, billing, or operational obligations should not rely solely on platform notifications — regularly logging into the account directly is the reliable method for monitoring account status;
• We are not liable for any loss, missed deadline, data loss, compliance failure, or operational consequence arising from non-receipt or delayed receipt of platform SMS or email notifications.

37. Data Backups — Scope and Limitations

We maintain automated database backups as part of our disaster recovery infrastructure. These backups are maintained for our own operational continuity and are not a data recovery service for individual users.

• Backups are designed to restore the entire Service following a catastrophic system failure — they are not granular per-user restore tools;
• We cannot restore individual records, individual customer accounts, or specific datasets from our backups upon user request;
• Backups do not protect against user-initiated deletions (if you delete a record within the Service, it is not recoverable from backup);
• Backup systems may fail. We do not warrant that backups are current, complete, or recoverable at any given time;
• The existence of our backup system does not reduce or eliminate your obligation to maintain your own independent archives of critical records, including regulatory spray records.

We are not liable for any data loss arising from backup failures, partial restores, or the inability to restore individual user data from system backups.

37.1 Internet Connectivity Required — No Offline Mode

DroneCommand is a cloud-based web application and requires an active internet connection to access, use, and enter records. There is no offline mode, offline data entry, local caching with sync capability, or any other mechanism that allows you to use DroneCommand or create records without an active internet connection at the time of entry.

• No Record Entry Without Connectivity: If you are at a remote spray site without mobile data service or Wi-Fi, you cannot enter spray records into DroneCommand until you restore internet connectivity. Records entered from memory hours or days after a spray event occurred — because you lacked connectivity at the time of application — may be less accurate than real-time records and may not satisfy regulatory requirements for contemporaneous record-keeping under Iowa IAC 45.26;
• Contemporaneous Record-Keeping Obligation: Iowa IAC 45.26 and other applicable pesticide record-keeping regulations may require records to be created contemporaneously with or promptly after a spray application. Delayed record entry due to connectivity limitations does not constitute a legal exception to record-keeping timing requirements. You are solely responsible for ensuring you have sufficient connectivity at your spray sites — or alternative paper-based documentation systems — to meet all regulatory record-keeping timing obligations;
• Time Stamp Accuracy for Delayed Entry: Records entered after the fact should accurately reflect the actual date and time of the spray event, not the date and time of data entry. If our system auto-populates a date/time field with the current time of entry, you are responsible for correcting that field to reflect the actual application time before finalizing the record. Inaccurate record timestamps are your responsibility;
• No Liability for Connectivity Failures: We are not liable for: (a) regulatory compliance failures arising from inability to enter records due to lack of internet connectivity; (b) records entered from memory that contain inaccuracies due to delayed entry; (c) record-keeping timing violations arising from connectivity limitations at remote spray sites; or (d) any other harm arising from the absence of an offline mode;
• Alternative Documentation Recommendation: For spray operations at sites with unreliable or no connectivity, we strongly recommend maintaining a paper-based backup system — field log books completed at the time of application — which you then transfer to DroneCommand when connectivity is restored. Retain the original paper records as backup documentation; do not discard paper records simply because the data has been entered into DroneCommand.

38. Unit Conversions and Calculation Inputs

The Mix Calculator and other calculation tools in DroneCommand perform computations based on values and units that you enter. These tools do not automatically detect or correct unit mismatches, measurement system errors (e.g., metric vs. imperial), product formulation differences (liquid concentrate vs. dry flowable vs. water-dispersible granule), or label-rate discrepancies. Entering the correct unit of measure for every input is your sole responsibility.

Common sources of user error that we are not responsible for include: entering fluid ounces when the label specifies ounces by weight; entering per-acre rates when the tool expects per-1000-sq-ft rates; entering product concentration percentage incorrectly; mixing products with different label rate units in a single calculation; and entering application rates for a different formulation than the one being used. All calculation outputs must be verified against the current registered product label and confirmed by a qualified pesticide applicator before use.

38.2 Intended Application Rate ≠ Actual Delivered Rate

Spray records in DroneCommand document the application rate you entered — your target or intended rate. The actual chemical delivery rate to the field depends on equipment calibration, nozzle condition, pump pressure, aircraft ground speed, swath width, and numerous other physical factors that DroneCommand does not monitor, measure, or have any connection to. We do not interface with your drone's spray system in any way.

• Equipment calibration: Actual delivery depends on your equipment being correctly calibrated at the time of each application. A spray record showing your intended rate of 2 oz/acre is not evidence that 2 oz/acre was actually delivered if your equipment was not calibrated or had malfunctioned since the last calibration check;
• Environmental variables affecting delivery: Wind speed and direction, temperature, humidity, boom height, and aircraft speed all affect actual coverage and deposition independent of what you entered in DroneCommand. These variables are not captured in our records and may cause material over- or under-application relative to the intended rate;
• Regulatory implications of rate discrepancy: If your record documents an application at the label rate but a calibration error or equipment malfunction resulted in a substantially different rate actually being applied, you may have violated label requirements regardless of what the record shows. A DroneCommand record documenting an intended compliant rate does not establish that application occurred at a compliant rate;
• Maintain separate calibration records: Equipment calibration logs, flow rate test results, and maintenance records that corroborate your application rate records are essential to defending any claim that your documented rate was also your delivered rate. These records are outside the scope of DroneCommand and are your operational responsibility;
• We are not liable for any crop damage, over-application, under-application, regulatory citation, pesticide label violation, or other harm arising from a discrepancy between the application rate documented in DroneCommand and the rate actually delivered to the field by your equipment.

38.3 Spray Records Are Not FAA Part 107 Flight Logs — Separate Regulatory Requirements

DroneCommand spray records document pesticide application operations — who applied what chemical, at what rate, on which field, at what time, under what conditions. These spray records are not a substitute for, and do not satisfy, the flight logging and documentation requirements applicable to commercial UAS operations under FAA regulations and your Part 107 Remote Pilot Certificate obligations.

• Part 107 does not require a flight log, but your insurer might: While FAA Part 107 does not currently mandate a flight log in the same way commercial aviation regulations require aircraft logbooks, many aviation liability insurers require documented flight logs as a condition of coverage. If your insurance policy requires UAS flight logs and you rely solely on DroneCommand spray records to satisfy that requirement, confirm with your insurer that DroneCommand spray records meet their specific flight log requirements — we do not make that representation;
• Records of incident proximity: In any FAA enforcement action or NTSB investigation involving a UAS incident, the FAA may request documentation of flight activity. DroneCommand spray records document spray operations, not flight parameters — they do not record battery cycles, total flight time, GPS track logs, airspace authorizations used, or other technical flight data that the FAA might request in an enforcement investigation;
• LAANC authorization records: If you operate in controlled airspace, you are required to obtain airspace authorization via LAANC or FAA DroneZone before each flight. DroneCommand does not record LAANC authorization numbers, expiration times, or authorized altitude limits. Your LAANC authorization records exist with the FAA and your LAANC provider — not in DroneCommand. We are not liable for enforcement actions arising from your inability to produce LAANC authorization records;
• Remote ID compliance: FAA Remote ID rules require UAS to broadcast identification and location data during flight. DroneCommand plays no role in Remote ID compliance, does not record Remote ID module serial numbers or broadcast data, and does not verify that your aircraft have compliant Remote ID capabilities;
• We are not liable for any FAA enforcement action, insurance coverage denial, NTSB investigation consequence, or other regulatory or legal outcome arising from reliance on DroneCommand spray records as a substitute for FAA-required or insurance-required flight documentation.

38.4 Off-Label Applications — Documenting an Off-Label Application in DroneCommand Does Not Make It Legal

Under FIFRA, the pesticide label is the law. Applying a pesticide in a manner inconsistent with its registered label — including at higher rates, on an unregistered crop, in an unregistered geographic area, or under conditions not permitted by the label — is a federal violation regardless of how the application is recorded. Creating a spray record in DroneCommand documenting an off-label application does not authorize, validate, legalize, or reduce the regulatory consequences of that application.

• Documentation is evidence, not authorization: Entering data in DroneCommand about an application is documentation of what occurred — it does not constitute authorization. An accurate spray record documenting an off-label application is evidence of a FIFRA violation, not a defense against one. A spray record describing an application made in excess of the maximum labeled rate does not become a compliant record because it was accurately entered into DroneCommand;
• Common off-label scenarios: Off-label applications include: applying a rate higher than the label maximum; applying to a crop not listed on the label; applying during conditions the label prohibits (e.g., wind speeds exceeding label limits); applying via a method not specified on the label (e.g., aerial application when the label specifies ground application only); or applying during a period that falls outside the label's timing restrictions. DroneCommand does not prevent you from documenting any of these scenarios;
• Label-compliant records do not prove label compliance: If you enter label-compliant values into DroneCommand but actually applied a different rate or under different conditions, the record documents what you entered — not what occurred. A record showing a compliant rate does not prove a compliant application; it proves the compliant rate was what you entered. Physical evidence, calibration records, and witness accounts may contradict your records;
• Regulatory consequences: Off-label pesticide application is a federal FIFRA violation and may also violate state pesticide law. Penalties include civil fines, license revocation, criminal prosecution, and personal liability for damages to crops, neighboring property, water bodies, and third parties. We are not responsible for advising you on label compliance and are not liable for any regulatory consequence of an off-label application you documented in our system;
• We are not a party to any regulatory enforcement action arising from pesticide applications — on-label or off-label — documented in DroneCommand. The records you create are your records; their compliance implications are your responsibility.

38.5 Mix Calculator Does Not Account for Water Volume or Carrier Volume

DroneCommand's Mix Calculator computes product-to-area ratios based on application rate inputs you provide. For spray operations in which water or another carrier liquid is used as the delivery medium, the Mix Calculator does not automatically calculate or validate the required carrier (water) volume per acre, tank capacity relative to coverage area, or the relationship between carrier volume and application rate on efficacy and drift behavior.

• Carrier volume is application-method-specific: In aerial drone application, the total carrier volume (gallons per acre) is typically very low compared to ground application — often 1–5 gallons per acre (GPA) versus 15–30+ GPA for ground rigs. Many pesticide labels specify minimum carrier volumes for aerial application; applying below the minimum labeled carrier volume may constitute an off-label application. The Mix Calculator computes product quantity per acre — not whether your carrier volume meets label minimums;
• Droplet size and drift interaction: Carrier volume affects spray droplet size, and droplet size directly affects drift potential and coverage uniformity. Lower carrier volumes tend to produce smaller droplets that drift more readily. The relationship between carrier volume, nozzle selection, pressure, and droplet classification (per ASABE S572.1) is an agronomic and equipment selection question — not a Mix Calculator output;
• Tank capacity planning: The Mix Calculator does not warn you if the quantities it calculates exceed your tank capacity or require multiple tank refills. Planning tank refill logistics, managing partial-tank applications and rate consistency, and tracking product remaining between tank refills are operational responsibilities outside the scope of the tool;
• Verify against product label adjuvant and carrier requirements: Many pesticide labels specify not only application rate but also required tank mix adjuvants, buffering agents, pH requirements, and carrier volume requirements. The Mix Calculator does not capture or enforce these ancillary label requirements. You are responsible for consulting the current product label for all carrier and adjuvant requirements before any application;
• We are not liable for any efficacy failure, crop damage, regulatory citation for application below labeled carrier volume minimums, equipment damage from improper concentration, or other harm arising from reliance on Mix Calculator outputs that did not account for required carrier volume.

38.6 Pesticide Batch and Lot Number Tracking — Not a Regulatory Recall Management Tool

DroneCommand may allow you to enter batch numbers, lot numbers, product formulation codes, or other product identifiers in spray records or inventory records. This feature is provided as a voluntary operational record-keeping convenience — it is not a pesticide product recall management system, a regulatory recall compliance tool, or a mechanism for receiving recall notifications from EPA, pesticide registrants, or distributors.

• No recall alert capability: DroneCommand does not receive notifications from EPA, pesticide registrants, or distributors when a pesticide product lot is recalled, subject to a cancellation order, or identified as contaminated. If a lot of pesticide you purchased and documented in DroneCommand is later recalled, we will not notify you of that recall — we have no connection to any recall notification system;
• EPA recall obligations are yours: Under FIFRA, recipients of recall notices from EPA or registrants are required to stop use of the recalled product and, in some cases, take affirmative steps to remove it from use. Your obligation to monitor for and respond to EPA pesticide recalls is independent of DroneCommand and exists whether or not you have documented the product in our inventory system;
• Batch/lot number entry is voluntary and unverified: If you enter a batch number in DroneCommand, it is a data entry reflecting what you chose to record. We do not validate batch or lot numbers against any external registry. An entry in our system does not constitute proof that the product used was from a specific lot — it proves that a specific number was entered;
• Contamination and off-spec product: Pesticide products are occasionally found to be off-specification, contaminated, or mislabeled after distribution. DroneCommand has no mechanism to detect or report these product quality issues. You are responsible for monitoring USDA, EPA, and manufacturer communications regarding product quality and safety alerts for products you purchase and use;
• We are not liable for any crop damage, regulatory citation, enforcement action, third-party damage claim, or other consequence arising from your use of a recalled, off-specification, or contaminated pesticide product that was documented in DroneCommand, regardless of whether the batch or lot number was entered in our system.

38.7 Active Ingredient Rate vs. Formulated Product Rate — A Persistently Misused Distinction

Pesticide products sold commercially are formulated products — they contain an active ingredient combined with inert carriers, surfactants, and other components. Pesticide labels specify rates in two ways: as a rate of formulated product (e.g., "apply 1 quart of XYZ Herbicide per acre") and as a rate of active ingredient (e.g., "apply 0.5 lbs a.i. per acre"). These measurements are related but not interchangeable — the same quantity of active ingredient may require materially different volumes of formulated product depending on the product's active ingredient concentration. DroneCommand fields for pesticide application rates accept any numeric value you enter and do not validate whether you have entered the rate of formulated product, the rate of active ingredient, or some other measure — and do not detect or warn you when you may be confusing the two.

• Label compliance requires correct rate type: Product labels specify maximum application rates in terms of formulated product (e.g., oz/acre or qt/acre) or active ingredient (lbs a.i./acre), and sometimes both. Applying above the maximum formulated product rate — even if your active ingredient calculation appears correct — constitutes a FIFRA label violation. You are responsible for knowing whether a rate you are recording is a formulated product rate or an active ingredient rate, and for verifying compliance with all label limits in both terms;
• Concentration confusion when switching formulations: When switching between formulations of the same active ingredient — for example, from a 4 lb/gallon formulation to a 2 lb/gallon formulation — the required volume of formulated product doubles for the same active ingredient dose. Failing to account for formulation concentration when switching products mid-season or between brands is a common source of under-application (failed pest control) and over-application (label violation, crop damage) errors that DroneCommand does not detect;
• Iowa spray record requirements and rate ambiguity: Iowa Administrative Code Chapter 45.26 requires that spray records include the amount of pesticide applied per acre. Whether this refers to formulated product or active ingredient per acre is a compliance question for which you are responsible. Ambiguity in your records about which rate type was used creates compliance risk in any regulatory inspection that reviews your records;
• Tank mix rate calculations: When multiple products are mixed in the same tank, calculating the correct formulated product quantity for each active ingredient requires separate rate calculations for each product based on each product's individual concentration. A rate confusion error in a tank mix affects all acres treated in that tank load and cannot be corrected retroactively after applications are complete;
• We are not liable for any label violation, FIFRA enforcement action, crop damage, rotational restriction violation, or other consequence arising from a spray record in which an active ingredient rate was entered where a formulated product rate was required, or vice versa, or from any other unit or rate confusion error that we did not detect, warn about, or prevent.

38.8 Certified Organic Input Compliance — Not Verified by DroneCommand

USDA National Organic Program (NOP) certification prohibits the use of most synthetic pesticides, herbicides, and fertilizers on certified organic acres. The list of materials approved for use in organic production is maintained by the NOP at 7 CFR Part 205 and supplemented by certifier-approved organic system plans that govern each individual certified operation. DroneCommand does not maintain a database of NOP-approved or NOP-prohibited substances, does not flag pesticide products in your product library as approved or prohibited for use on certified organic acres, and does not alert you when a spray record entry involves a product that is prohibited under NOP regulations or your certifier's approved organic system plan.

• Your certifier's approved organic system plan controls what you can use: Certified organic operations must maintain an approved organic system plan with a USDA-accredited certifier. The certifier approves specific input materials for specific uses — a material that is broadly NOP-compliant may be prohibited by your certifier's plan, or approved only under certain conditions. DroneCommand cannot know the contents of your certifier's approved plan and does not screen your spray records against it;
• A single prohibited substance application may end your certification: Application of a prohibited synthetic substance on certified organic acres — even a single application at a minimal rate — may result in loss of organic certification for those acres for a minimum of three years under NOP regulations. The financial consequence of losing organic certification typically far exceeds the cost of the single application. We are not responsible for identifying products that would trigger this consequence or for preventing their entry into DroneCommand records;
• Adjacent field contamination creates drift liability: Drift of prohibited synthetic pesticides from non-organic neighboring fields onto certified organic acres may trigger an NOP contamination investigation regardless of who performed the application. If you operate both organic and non-organic ground and record applications across those acres in DroneCommand, you are solely responsible for ensuring that applications to non-organic ground do not drift onto certified organic acres in amounts detectable under NOP testing standards;
• Label compliance and NOP compliance are separate determinations: A product may have a valid EPA registration, a compliant label, and a clearly appropriate crop use — and still be prohibited under the NOP because of its synthetic formulation, specific active ingredient, or prohibited inert ingredients. Label compliance does not establish NOP compliance. Both determinations must be made independently, and DroneCommand does not perform either;
• We are not liable for any organic certification loss, certifier decertification action, USDA NOP enforcement, market premium loss, contract breach, or other consequence arising from the use of a substance prohibited under the NOP or your organic system plan that was recorded in a DroneCommand spray record that we did not identify, flag, or prevent from entry.

38.9 Pesticide Product Expiration, Shelf Life, and Registered Label Withdrawals — Not Tracked

Pesticide products have registered label shelf lives, storage requirements, and in some cases, EPA-set expiration dates. Using a pesticide product after its labeled expiration date, under conditions that have degraded its labeled efficacy, or after the product's registration has been cancelled or suspended, raises distinct legal and agronomic risks that differ from using a product within its shelf life and current registration status. DroneCommand does not track the expiration dates of pesticide products entered in your product library, does not display EPA registration status or cancellation orders for products in your library, and does not alert you when a product's registration has been suspended, voluntarily cancelled by the registrant, or subjected to a stop-sale or stop-use order.

• Using expired pesticide products: Applying a pesticide product after its labeled expiration date may result in reduced efficacy — which could mean failed pest control, a wasted application cost, and crop loss — or chemical degradation products that are not covered by the label's safety and environmental risk assessment. In either case, you applied a product in a manner inconsistent with its label, which is a FIFRA violation regardless of whether the degradation was visible;
• Cancelled and suspended registrations: EPA periodically cancels or suspends pesticide product registrations — because of new safety data, voluntary registrant withdrawal, failure to pay registration maintenance fees, or enforcement action. When a registration is cancelled or suspended, using the product may become a FIFRA violation even if you legally purchased it before the cancellation. DroneCommand does not monitor EPA's Office of Pesticide Programs for cancellation orders affecting products in your library;
• Stop-use vs. existing stock provisions: Some EPA cancellation orders permit the use of existing stock for a defined period after cancellation; others require immediate cessation. The distinction matters. You are responsible for monitoring EPA communications about any product you use and for complying with whatever existing stock provision applies to a cancelled or suspended product you have on hand;
• Inventory records reflect what you entered, not current regulatory status: A product entered in your DroneCommand product library reflects the name, registration number, and details you entered at the time of entry. That entry does not update automatically if the product's registration is later cancelled, its label is updated with new restrictions, or the product is reformulated. You are responsible for keeping your product library accurate and for verifying current registration status before each use;
• We are not liable for any FIFRA violation, crop damage, regulatory citation, or other consequence arising from your use of a pesticide product that was expired, had a cancelled or suspended registration, or was subject to a stop-use order that was not reflected in DroneCommand's product library or communicated to you through the Service.

38.10 Pesticide Storage and EPCRA Tier II Reporting — Not Assisted or Tracked by DroneCommand

The Emergency Planning and Community Right-to-Know Act (EPCRA), Section 312, requires facilities that store hazardous chemicals above established threshold quantities to submit annual Tier II inventory reports to state emergency response commissions, local emergency planning committees, and local fire departments by March 1 of each year. Pesticide products with active ingredients classified as extremely hazardous substances (EHS) under EPCRA trigger Tier II reporting obligations when stored above the threshold planning quantity — which for some EHS pesticides is as low as 1 pound. DroneCommand's pesticide inventory tracking features — where available — are provided as an operational convenience for managing your spray program supply; they are not an EPCRA compliance tool, do not calculate your EPCRA reporting obligations, and do not generate Tier II reports.

• Inventory records in DroneCommand are not EPCRA records: DroneCommand may allow you to track pesticide inventory quantities purchased, on hand, and used. These inventory records are operational management data — they are not formatted for or integrated with any state EPCRA Tier II reporting system. Iowa's EPCRA Tier II reporting system is managed by the Iowa Department of Homeland Security and Emergency Management and accepts reports through a specific portal that DroneCommand is not connected to;
• Extremely hazardous substance thresholds are product-specific: The EPCRA Section 302 Extremely Hazardous Substances list includes numerous pesticide active ingredients. Threshold Planning Quantities (TPQ) for EHS pesticides vary by substance and may be as low as 1 pound for the most hazardous compounds. You are responsible for determining whether any pesticide product you store contains an EHS active ingredient and whether your storage quantities exceed the applicable TPQ;
• Agricultural exemptions have limits: EPCRA provides certain exemptions for fertilizers and some agricultural chemicals, but these exemptions do not apply to all pesticide products or all storage configurations. Commercial spray operators storing pesticide inventory in a chemical shed, truck tank, or other facility may have Tier II reporting obligations that differ from those of a single-farm operator storing products for personal use. You are responsible for determining how EPCRA applies to your specific operation and storage configuration;
• Pesticide storage safety regulations: Iowa pesticide storage regulations under Iowa Code Chapter 206 and associated administrative rules impose storage facility requirements — including containment, labeling, and access restrictions — that are independent of EPCRA and not addressed by DroneCommand. You are responsible for compliance with all applicable pesticide storage laws regardless of how you track inventory in DroneCommand;
• We are not liable for any EPCRA Tier II reporting violation, Iowa pesticide storage regulation citation, first responder harm arising from unreported chemical storage, fine, penalty, or other consequence arising from your failure to comply with chemical inventory reporting or storage requirements that DroneCommand's inventory features did not calculate, trigger, or warn you about.

38.11 Spray Equipment Calibration and Nozzle Wear — Actual Application Rate May Differ From Recorded Rate

The application rate recorded in a DroneCommand spray record reflects the rate you enter — typically the intended rate based on your equipment setup, nozzle selection, and spray parameters. The actual amount of product delivered per acre by a drone spray system is a function of ground speed, boom pressure, nozzle flow rate, nozzle wear condition, GPS accuracy, and environmental factors including wind and temperature. Nozzles wear over time — worn nozzles deliver more product per unit area than new nozzles calibrated to the same pressure — and uncalibrated systems may systematically over- or under-apply relative to the recorded rate. DroneCommand does not verify that your equipment is calibrated, that your nozzles are within acceptable wear tolerance, or that the rate you enter into a spray record accurately reflects the rate your equipment actually delivered to the field.

• Recorded rate vs. delivered rate: If your nozzles are worn to 115% of their nominal flow rate, every acre you treat receives 15% more product than the rate you recorded. If the recorded rate is already at the label maximum, your actual application rate exceeds the label maximum — making every application a FIFRA violation, regardless of what the record shows. The record shows intent; calibration determines compliance;
• Calibration is a legal and agronomic obligation: Iowa pesticide applicator licensing standards and FIFRA label compliance both require that spray equipment deliver product at the labeled rate. Equipment calibration — including nozzle tip inspection and replacement at or before the manufacturer's recommended wear threshold — is your operational responsibility. DroneCommand has no way to know whether your equipment was calibrated on the date of any recorded application;
• GPS accuracy and coverage uniformity: Drone spray systems operating in obstacle-affected GPS environments, during periods of poor satellite geometry, or with degraded GPS signal may have ground speed variations that affect application rate uniformity across a field. DroneCommand records the parameters you enter — it does not receive flight telemetry data from your drone to calculate actual coverage uniformity or identify application rate inconsistencies;
• Calibration records: Industry best practice requires maintaining separate calibration records documenting when nozzles were last inspected, replaced, or tested — including flow rate test data. DroneCommand spray records are not a substitute for calibration records. If IDALS requests calibration documentation during an inspection of your records, your DroneCommand spray records will not demonstrate equipment calibration;
• We are not liable for any FIFRA label violation, crop damage, regulatory citation, or other consequence arising from a discrepancy between the application rate recorded in DroneCommand and the actual rate delivered by spray equipment that was not calibrated, had worn nozzles, or otherwise did not perform consistently with the rate you entered.

38.12 Nozzle Type, Spray Quality Classification, and Label Nozzle Requirements

Pesticide labels increasingly specify nozzle types or spray quality classifications (e.g., coarse, medium, fine) as a condition of legal use, particularly for herbicides with drift management requirements. DroneCommand does not verify that the nozzle type installed on your spray equipment matches the nozzle type required or recommended by the pesticide label, and does not validate spray quality classification compliance.

• Label nozzle requirements are legally binding: Where a pesticide label specifies a required nozzle type or prohibits certain spray quality classifications, using a non-compliant nozzle constitutes a FIFRA label violation regardless of the application rate or other parameters;
• ASABE spray quality classification not tracked: The ASABE S572.1 spray quality classification system (VFINE through ULTRACOARSE) is not integrated into DroneCommand; the Service does not record, validate, or display the spray quality classification produced by your nozzle selection at any given pressure and flow rate;
• Nozzle wear and classification drift: A nozzle that originally produced a compliant spray quality classification may produce a finer, higher-drift classification as it wears; DroneCommand does not track nozzle age, hours of use, or wear-related classification drift;
• Drone nozzle specifications vary: Drone spray systems use a variety of nozzle types, orientations, and operating pressures that differ from ground equipment; spray quality classifications developed for ground equipment may not apply equivalently to drone operations;
• We are not liable for any FIFRA label violation, pesticide drift claim, crop damage, regulatory citation, or other consequence arising from the use of a nozzle type or spray quality classification that did not comply with the applicable pesticide label, regardless of what equipment information you have entered into DroneCommand.

38.13 Tank Mix Compatibility, Physical Incompatibility, and Co-Application Risk

Agricultural spray operations frequently involve tank mixes combining two or more pesticides, adjuvants, fertilizers, or other crop inputs applied simultaneously. DroneCommand does not evaluate tank mix physical compatibility, chemical antagonism, or the combined efficacy and safety of co-applied products, and does not warn when a proposed tank mix may result in precipitation, separation, or reduced product performance.

• Physical incompatibility not checked: Certain combinations of pesticide formulations, fertilizers, and adjuvants are physically incompatible and may form precipitates, gels, or separated layers that clog nozzles, result in uneven application, or reduce efficacy; DroneCommand does not check for these incompatibilities;
• Jar test requirement: Industry standard practice requires a jar test before using any new tank mix combination; this physical compatibility test is entirely your responsibility and is not replaced or supplemented by DroneCommand;
• Label mixing order requirements: Pesticide labels often specify a required order of addition for tank mix components; failure to follow the specified mixing order can cause incompatibility; DroneCommand does not provide or enforce mixing order guidance;
• Antagonism and synergy: Some tank mixes may result in reduced efficacy of one or more components (antagonism) or increased phytotoxicity (synergy); these interactions are not assessed by DroneCommand;
• We are not liable for any crop damage, equipment clogging, application failure, regulatory violation, or other consequence arising from physical or chemical incompatibility of products in a tank mix, regardless of what products were recorded in DroneCommand's mix calculator.

38.14 Spray Boom Height, Canopy Penetration, and Coverage Uniformity Not Validated

The efficacy of a pesticide application depends substantially on spray boom height above the canopy, droplet penetration into the plant canopy, and uniformity of coverage across the target area. DroneCommand records the application parameters you enter but does not validate that the boom height, flight altitude, swath width, or speed you recorded produced adequate canopy penetration or uniform coverage for the target pest or disease.

• Height-dependent efficacy: Boom height directly affects droplet size distribution, coverage uniformity, and drift potential; the optimal boom height varies by crop, growth stage, target pest, and nozzle type; DroneCommand does not provide or enforce boom height recommendations;
• Canopy density not assessed: Dense or tall crop canopies may require different application parameters to achieve adequate penetration compared to shorter or more open canopies; DroneCommand does not assess canopy density or adjust coverage requirements accordingly;
• Recorded vs. actual flight parameters: Flight altitude, speed, and swath width recorded in DroneCommand reflect the parameters you enter, which may differ from the parameters actually flown if your autopilot system did not perform as expected or if you manually entered estimated values;
• Water-sensitive paper and coverage testing: Industry standard coverage testing using water-sensitive paper cards or similar methods is the appropriate way to validate spray coverage; DroneCommand does not integrate with or require coverage testing validation;
• We are not liable for any application failure, crop disease progression, pest damage, or other consequence arising from inadequate canopy penetration, non-uniform coverage, or a discrepancy between the flight parameters recorded in DroneCommand and the parameters actually flown.

39. Selective Non-Enforcement

Our decision to enforce, not enforce, or delay enforcement of any provision of these Terms against any particular Customer does not: (a) waive our right to enforce the same provision against any other Customer; (b) create an obligation to treat all Customers identically with respect to Terms enforcement; (c) constitute a custom or course of dealing that modifies these Terms; or (d) create any claim of discriminatory enforcement. Each enforcement decision is made on its own facts and circumstances. The fact that another Customer engaged in similar conduct and was not sanctioned does not create a defense for your violation.

Protected Characteristics: Notwithstanding the above, nothing in this Section authorizes us to enforce or selectively enforce these Terms against any Customer on the basis of race, color, national origin, religion, sex, gender identity, sexual orientation, disability, age, or any other characteristic protected by federal, state, or local civil rights law. This prohibition on discriminatory enforcement is not waivable and applies regardless of any other provision of these Terms. If you believe enforcement action against you was motivated by discrimination based on a protected characteristic, you retain all rights available under applicable civil rights law, which are not limited or modified by these Terms.

40. Government Requests and Legal Process

We may receive subpoenas, court orders, search warrants, regulatory requests, or other legal process requiring us to disclose User Data or restrict your account access. When we receive such process:

• We will comply with valid, enforceable legal process as required by law;
• Where legally permitted to do so, we will provide you with prompt notice before complying, so that you may seek a protective order or other relief;
• In some circumstances, applicable law prohibits us from notifying you (for example, National Security Letters issued under 18 U.S.C. § 2709 include nondisclosure requirements). In those cases, we cannot provide advance notice;
• Complying with valid legal process is not a breach of these Terms or our Privacy Policy;
• We are not liable for any loss or damage arising from our compliance with valid legal process, including account restrictions or data disclosures made pursuant to court orders or government requests;
• We will use commercially reasonable efforts to limit disclosures to the minimum required by the applicable legal process.

You agree to indemnify us for reasonable legal costs we incur in responding to legal process, but only where: (a) the legal process is specifically directed at your User Data (not general audits of our platform or legal process directed at us as a company or at other customers); and (b) the legal process was directly triggered by or arose from your own business activities, conduct, regulatory compliance status, or disputes involving you — not merely from the fact that your records are stored with us. This indemnification does not apply to: legal process resulting from our own wrongdoing; general government investigations of our platform operations; regulatory audits that inquire about our data handling practices rather than your specific conduct; or legal process that equally applies to all our customers.

41. Two-Factor Authentication and Account Security

This section supplements and restates the security obligations in Section 4. Where we offer two-factor authentication ("2FA") or other optional enhanced security features (such as session timeout controls, login notifications, or IP-based access restrictions), you are solely responsible for deciding whether to enable them. We provide these features to assist with your security — we do not mandate them, and we are not liable for harm resulting from your decision not to use available security features.

Your Security Obligations: You agree to: (a) use a strong, unique password not reused on other services; (b) enable 2FA if it is offered and if your operations involve particularly sensitive data; (c) immediately revoke access for any employee, pilot, or contractor who leaves your organization; (d) not share credentials among multiple individuals; and (e) promptly report any suspected unauthorized access.

Employee Access Revocation — Your Responsibility: When an employee, pilot, contractor, or other Authorized User leaves your organization — whether by termination, resignation, or any other reason — you are solely responsible for promptly removing that individual's access from your DroneCommand account. We are not liable for any records deleted, altered, downloaded, or misused by a former employee or contractor whose access you failed to revoke in a timely manner. We strongly recommend revoking access the same business day the employment or contractor relationship ends. We are not liable for any act of retaliation, sabotage, or data theft by a former Authorized User whose access you controlled and failed to revoke.

41.2 False, Malicious, or Sabotage Records Entered by Authorized Users

Any Authorized User with record-creation access can enter data into DroneCommand. We cannot prevent an Authorized User from entering false, fabricated, retaliatory, or malicious data into the Service, and we are not liable for any consequences of false records entered by your own Authorized Users. This includes but is not limited to:

• False regulatory spray records: An Authorized User could enter a spray record claiming that a banned chemical was applied, that an unlicensed applicator performed the work, or that application occurred outside of permitted conditions — even if none of this is true. Once finalized, such a record is immutable within the Service. You are solely responsible for preventing, detecting, and addressing false record creation by your Authorized Users;
• Sabotage by a disgruntled or departing employee: An Authorized User who learns they are about to be terminated, or who has a grievance against your business, may enter false records as an act of sabotage before their access is revoked. The immutability feature that protects legitimate records from alteration equally protects maliciously entered false records from deletion. You are solely responsible for revoking access before or immediately upon any employment termination, for any reason;
• Remediation options for false records: If you discover that an Authorized User has entered false or malicious records, contact us at [email protected]. While we cannot delete finalized regulatory records unilaterally, we may be able to: (a) provide access log evidence showing who created the record and when; (b) add an administrative notation to the record flagging it as disputed, if technically feasible; and (c) assist you in documenting the circumstances for any regulatory authority that needs to understand the context of the record. We cannot, however, delete or alter finalized records on your request, as doing so would undermine the integrity guarantees of the system;
• Criminal and civil remedies: Entering false regulatory records may constitute a crime under applicable pesticide law, fraud statutes, or other laws. We encourage you to consult law enforcement and an attorney if you discover deliberate false record entry. We will cooperate with valid law enforcement investigation of such conduct.

42. Account Access — Estate, Incapacity, and Authorized Representatives

In the event of the death or legal incapacity of an Account Holder, access to or management of the DroneCommand account is governed as follows:

• No Automatic Access: We do not automatically grant account access to heirs, surviving family members, estate representatives, or next of kin. We cannot verify the identity or authority of persons claiming rights through a deceased or incapacitated account holder without documentation;
• Required Documentation: A legal representative seeking account access must contact us at [email protected] and provide: (a) a certified copy of the death certificate or court order establishing incapacity; (b) documentation establishing their legal authority — such as letters testamentary, letters of administration, a court-issued guardianship order, or a durable power of attorney; and (c) a written description of the specific access or data export needed;
• Scope of Authorized Access: Upon verification of documentation, we will provide the authorized representative with the ability to export User Data and access account information for the purpose of orderly account closure, data recovery, or business continuity. We will not transfer a subscription to a new holder without a new agreement;
• Processing Time and Billing Hold: We will process estate access requests within fifteen (15) business days of receiving complete documentation. If we fail to process a complete request within fifteen (15) business days and have not provided a written explanation for the delay with a new estimated completion date, we will place a billing hold on the account (no further subscription charges will accrue) until we complete processing. The billing hold does not cancel the subscription — it temporarily suspends new charges only. The estate is responsible for canceling the subscription through Section 12 methods after estate access is granted;
• Subscription Continues to Bill; Limited Retroactive Refund: The account's subscription continues to charge until formally cancelled through the methods in Section 12. The estate or legal representative is responsible for canceling the subscription promptly after assuming control of the account. We will not retroactively refund charges that accrued before we were notified of the death or incapacity, except that upon verified notification of death or incapacity, we will review and may refund subscription charges incurred in the thirty (30) days immediately preceding our receipt of documentation if: (a) the estate representative demonstrates that the account was not actively accessed during that period; and (b) the cancellation request and documentation are provided within sixty (60) days of the account holder's death or date of incapacity. This is a discretionary goodwill consideration, not a binding obligation, and is evaluated case-by-case;
• No Liability for Documentation Fraud: We are not liable for unauthorized access granted in good faith based on documentation that we verified using reasonable procedures but that was later determined to be fraudulent.

43. Multi-Entity Accounts and Account Separation

DroneCommand accounts are registered to a single legal entity or individual. If you operate multiple legal entities (e.g., multiple LLCs, corporations, DBAs, or partnerships) and manage records for more than one under a single DroneCommand account, the following applies:

• Single-Entity Recommendation: We strongly recommend maintaining a separate DroneCommand account for each distinct legal entity whose records must be legally separable — for example, if different entities have different regulatory licensing requirements, different ownership structures, or whose records may be subject to separate legal proceedings;
• Commingling Risk — Your Sole Responsibility: If you choose to manage multiple legal entities under a single account, you assume all risks including: inability to produce records attributable solely to one entity in litigation or regulatory proceedings; potential exposure of one entity's records in legal proceedings targeting another entity using the same account; and difficulty establishing that records belong to a specific licensed entity for regulatory compliance purposes;
• Legal Hold and Litigation: If we receive a valid legal hold, subpoena, or court order directed at a specific legal entity whose records are commingled with other entities in your account, we will comply with the legal process as to the entire account — we cannot segregate records by entity within an existing shared account structure;
• No Liability for Commingling Consequences: We are not responsible for any legal, regulatory, or financial harm arising from your decision to commingle records for multiple legal entities in a single account.

43.1a Agricultural Co-Operative Accounts

• Applicator License Responsibility: Agricultural co-operatives using DroneCommand are responsible for ensuring that all spray records accurately reflect the pesticide applicator license number of the co-operative entity (or individual applicator, as applicable under state law), not individual member-farmers who are not themselves licensed applicators. DroneCommand does not validate applicator license numbers entered in records;
• Co-Operative as "Customer": In a co-operative operational model, the co-operative entity is the "Customer" for purposes of these Terms regardless of which member's field is being treated. The co-operative is solely responsible for ensuring that all use of DroneCommand by its members, employees, or agents complies with these Terms;
• Regulatory Compliance Determination: DroneCommand does not determine whether a co-operative's use of the platform satisfies Iowa Administrative Code Chapter 45.26 or equivalent provisions of other states for co-operative pesticide applicators — that determination is solely the co-operative's responsibility and should be made in consultation with the applicable state lead agency and legal counsel;
• Member-Farmer Rights: Member-farmers who are not account holders have no independent rights under these Terms. Their data is governed by the co-operative Customer's account agreement, and any requests related to their data must be made through the co-operative account holder.

43.1b Landowner Read-Only Access — Scope and Limitations

DroneCommand may offer features that allow landowners or field owners to view spray records associated with their fields. Any such read-only access is a courtesy feature only and does not constitute a regulatory compliance portal.

• Courtesy feature, not a compliance portal: Any read-only access granted to landowners or field owners to view their spray records is a courtesy feature only — it does not constitute a regulatory compliance portal, an official record-keeping system for landowner purposes, or a substitute for direct communication with the licensed pesticide applicator;
• Same accuracy limitations apply: Records displayed to landowners via shared access are subject to the same data accuracy limitations, GPS accuracy disclaimers, and retroactive entry disclaimers that apply to operator-viewed records — landowner access does not imply any independent verification of record accuracy;
• Applicator retains all regulatory obligations: Granting landowner access does not transfer any regulatory record-keeping obligation from the licensed pesticide applicator to the landowner — the applicator remains solely responsible for record accuracy and completeness under Iowa Administrative Code Chapter 45.26 and any other applicable law;
• Read access is non-transactional: Landowners viewing shared records may not modify, delete, annotate, or otherwise alter spray records — read access is view-only and does not create any contractual relationship between DroneCommand and the landowner;
• We are not liable for any claim by a landowner arising from their interpretation of, reliance on, or inability to access records through shared or read-only access features.

43.2 Minimum Necessary Production for Multi-Entity Subpoenas

If we receive a subpoena, court order, or regulatory request specifically directed at one legal entity whose records are commingled with other entities in your account, we will use commercially reasonable efforts to limit our production to records that are reasonably identifiable as belonging to the specific entity named in the legal process, rather than automatically producing all records in the account. However:

• If records are so thoroughly commingled that they cannot be separated without incurring unreasonable effort or expense, or without risking contempt of the applicable legal process, we may produce the entire account's records to comply with the legal process;
• We are not your legal counsel and are not required to litigate on your behalf to narrow the scope of legal process directed at us — if you believe a subpoena is overbroad, it is your responsibility (or your legal counsel's) to seek a protective order or motion to quash before our compliance deadline;
• We will use commercially reasonable efforts to notify you before complying with legal process (where permitted by law) so that you can seek such relief on a timely basis;
• The risk that a broad subpoena directed at one entity results in production of another entity's records is a foreseeable consequence of commingling records in a single account — this risk is your responsibility under Section 43.1, not ours.

44. International Operations — U.S. Service Only

DroneCommand is designed and provided exclusively for drone spray operations conducted within the United States. The Service's compliance record-keeping tools, regulatory frameworks referenced, DriftWatch integration, and Iowa BeeCheck integration are designed with reference to U.S. federal law and Iowa, Nebraska, and South Dakota state law only.

• Non-U.S. Operations: If you use DroneCommand to plan, record, or manage drone spray operations conducted outside the United States — including Canada, Mexico, or any other country — you do so entirely at your own risk. The Service does not include compliance tools, regulatory databases, or operational guidance for any non-U.S. jurisdiction;
• No Foreign Regulatory Compliance: We make no representation that the Service meets or assists with any non-U.S. regulatory requirement, including without limitation Health Canada PMRA requirements, Canadian provincial pesticide regulations, Transport Canada drone regulations, or any other foreign agricultural, aviation, or environmental law;
• Foreign Privacy Laws: If your operations involve personal data of individuals located in non-U.S. jurisdictions, you are solely responsible for ensuring that your use of DroneCommand complies with all applicable data protection laws of those jurisdictions, including GDPR, PIPEDA (Canada), and any other applicable law. We are not liable for your failure to comply with non-U.S. privacy or data protection law;
• No Obligation to Adapt: We are under no obligation to add features, modify the Service, obtain foreign regulatory approvals, or provide any other accommodation to support non-U.S. operations or compliance with non-U.S. law.

45. Court Proceedings and Record Authentication

DroneCommand is an operational record-keeping tool, not a certified records custodian service. With respect to the use of DroneCommand records in legal proceedings:

• No Certification Services (Without Legal Process): We do not offer record certification, sworn affidavits regarding record accuracy, records custodian testimony, or chain-of-custody documentation as a customer service. We do not respond to informal requests for such services from attorneys, customers, or other third parties without formal legal process;
• Response to Valid Legal Process: If required by a valid court order, subpoena, or attorneys' stipulation, we may provide a declaration or certification establishing a foundation for records as business records under Federal Rule of Evidence 803(6) or equivalent state rule. Such a declaration authenticates only that records were created and maintained in the ordinary course of business through our platform — it does NOT certify the accuracy, completeness, or truthfulness of the data contained in those records. The content of your records is your responsibility, not ours;
• Evidentiary Value is Yours to Establish: The admissibility and evidentiary weight of your DroneCommand records in any legal or regulatory proceeding depends on the accuracy and completeness of data you entered. We are not responsible for the admissibility, evidentiary value, or sufficiency of records in any proceeding;
• Fees for Legal Process Response: We reserve the right to charge reasonable fees for compliance with legal process requiring substantial staff time or legal costs, as permitted by applicable law;
• Your Litigation Strategy: We are not a party to your litigation, are not responsible for your litigation strategy or outcomes, and are not obligated to advocate on your behalf in any proceeding. Our role is to comply with valid legal process, not to assist or advise you in litigation.

46. Service Discontinuation and Business Continuity

We intend to operate DroneCommand as an ongoing commercial service. However, we may discontinue the Service in the future due to business or financial circumstances. In the event of a planned discontinuation:

• Advance Notice: We will provide not less than ninety (90) days' prior written notice of planned Service discontinuation, delivered by email to the address on file for each active account and prominently displayed within the Service;
• Prorated Refunds: Subscribers with prepaid Annual, 2-Year, or 4-Year plans will receive a prorated refund of the unused portion of their prepaid term, calculated as the number of full unused months remaining divided by the total months in the plan, multiplied by the original plan price;
• Data Export Window: We will maintain data export functionality for a minimum of sixty (60) days following the official discontinuation date, so all customers can export their User Data;
• Automatic Data Export on Discontinuation: Within thirty (30) days of issuing our 90-day discontinuation notice, we will automatically generate and deliver to each active account holder a complete export of all their User Data in standard CSV and PDF format, sent to the email address on file — regardless of whether you take any action. This automatic export delivery is not contingent on customer action. You should also independently export your data through Settings → Export Data during the notice period as a backup;
• Regulatory Records on Discontinuation: We will either: (a) deliver a complete export of all retained Regulatory Records to the account holder's email on file within the 90-day notice period; or (b) provide written notice of the specific custodian to whom Regulatory Records will be transferred and how customers can request access. We will not destroy Regulatory Records required by law without first providing customers a copy or a valid transfer;
• Bankruptcy and Involuntary Court-Supervised Proceedings: If Country Road Drone Services, LLC becomes subject to a court-supervised bankruptcy proceeding (Chapter 7 or Chapter 11 under the U.S. Bankruptcy Code), receivership ordered by a court, or similar court-supervised insolvency process — and performance of the 90-day notice or prorated refund commitments is specifically stayed, voided, or prohibited by order of the supervising court — those commitments may not be enforceable solely to the extent the court order prohibits them. Outside of court-supervised proceedings: a voluntary wind-down, strategic discontinuation, sale of the business, or financial decision to discontinue the Service without filing for bankruptcy relief is NOT subject to this carve-out. In those scenarios, the 90-day notice, automatic data export delivery, prorated refund, and Regulatory Records commitments remain fully binding. The best protection against Service discontinuation is regular data export regardless of any business event. We strongly recommend exporting your complete dataset at least once per season, and not relying solely on DroneCommand as your only copy of regulatory records;
• Successor Services: If we transfer or sell the DroneCommand business to a third party (including a successor company or acquirer), the new operator will be notified of these data commitments and we will make commercially reasonable efforts to ensure continuity of service or a smooth transition with adequate notice.

47. Account Transfer on Business Sale or Ownership Change

Your DroneCommand account and subscription are registered to the legal entity or individual identified at account creation. They are not automatically transferable to a third party upon the sale of your business, its assets, or its operations.

• No Automatic Transfer: If you sell your drone spray business, the purchaser does not automatically acquire rights to your DroneCommand account, subscription, login credentials, or User Data. The purchaser must create their own DroneCommand account and new subscription;
• Voluntary Account Transfer by Written Agreement: With our prior written consent (at our discretion), you may request that account ownership be formally transferred to a new legal entity or individual in connection with a legitimate business sale. Both the original Account Holder and the receiving party must execute a written acknowledgment of these Terms. If we approve a transfer, the transferee will inherit the remaining prepaid term and current subscription pricing — we will not require renegotiation of price as a condition of approving a business-sale account transfer. We may require a new subscription agreement for the transferee to acknowledge these Terms, but that agreement will reflect the same pricing and remaining term unless the transferee elects to change their plan;
• User Data in Business Sale: You may export your User Data and provide it to a business purchaser as part of a lawful business sale transaction. However, you are solely responsible for ensuring that any transfer of personal data (including employee records, customer records, and landowner records) complies with applicable privacy law, employment law, and any contractual obligations you have to those individuals;
• Regulatory Records and Business Sales: Your regulatory obligation to retain spray records under Iowa IAC 45.26 and equivalent state law may follow the spray activities, not the account holder. Consult applicable law and your compliance counsel regarding responsibility for regulatory records in a business sale. We are not responsible for regulatory compliance gaps arising from a business sale;
• No Assignment Without Consent: Any attempt to assign, transfer, or delegate your rights under these Terms without our prior written consent is void and of no force or effect, per Section 34.4.

47.2 Business Entity Name Change, Restructuring, and Reorganization

If you change your business entity's legal name, convert from one entity type to another (e.g., sole proprietorship to LLC, LLC to corporation), form a successor entity, or undergo any other business restructuring, your DroneCommand account and all historical records continue to display the entity name that was registered at the time those records were created. Updating your account name going forward does not retroactively alter existing records.

• Historical records bear old entity name: All spray records, job records, and regulatory documents created before an account name update will continue to show the entity name that was current when they were created. If a regulatory inspector reviews records spanning a name change, some records will show your old entity name and some will show your new name. You are responsible for being able to explain this to any regulatory authority or third party;
• Regulatory identity continuity: If your Iowa commercial pesticide applicator license, FAA operating certificate, or other professional credential is issued to the old entity name and your DroneCommand records bear that old name, those records may or may not satisfy regulatory requirements under your new entity name. Consult your compliance attorney and IDALS regarding any required notifications, license transfers, or record-keeping adjustments necessitated by your entity restructuring;
• How to update your account name: To update the entity name associated with your DroneCommand account, contact [email protected] with subject "Account Entity Update." We will update the name for future records but cannot retroactively modify historical records. Provide documentation of the name change (e.g., amended articles of organization, certificate of conversion) with your request;
• License and compliance obligations during restructuring: A business restructuring does not suspend your obligation to maintain current licensing or comply with all regulatory requirements. If your restructuring creates a gap in which the new entity does not yet hold the required licenses held by the prior entity, commercial spray operations during that gap may violate applicable law. We are not responsible for compliance gaps arising from your restructuring timeline;
• We are not liable for any regulatory citation, insurance denial, contract dispute, or other consequence arising from a discrepancy between the entity name in your DroneCommand records and your current legal entity name.

47.5 Post-Termination Data Access and Litigation Hold Requests

When a DroneCommand account is terminated — whether by expiration, cancellation, non-payment, or termination for cause — User Data is retained for the applicable retention period described in Section 14 and then permanently deleted. If you or a third party require access to your DroneCommand data after account termination — including for ongoing litigation, a regulatory investigation, an insurance claim, or any other legal purpose — you must act before account deletion, which follows the timelines in Sections 10 and 14.

• Export before cancellation: You are responsible for exporting all records you need before canceling or allowing your subscription to lapse into the deletion window. We provide export functionality for this purpose. Do not rely on us to preserve your data indefinitely after your account has closed;
• Litigation hold requests: If you are involved in active litigation and require that your DroneCommand records be preserved beyond our standard retention period, contact us at [email protected] with subject "Litigation Hold Request" before your data enters the deletion window. We may, in our sole discretion, agree to extend retention for a specific period upon receipt of a written litigation hold notice from your attorney. We are not obligated to accept or honor litigation hold requests, but we will consider them in good faith;
• Third-party legal holds: If a court order, subpoena, or other legal process requires us to preserve records beyond our standard retention period, we will comply with that process. However, if your account is already in the deletion window and deletion has completed before we receive the legal process, we cannot recover deleted data. We are not liable for data that was deleted before legal process requiring its preservation was received;
• Post-deletion impossibility: Once User Data is permanently deleted under our retention policy, it cannot be recovered by us or by any third party. "Permanent deletion" means it cannot be retrieved — no recovery process, court order, or technical intervention can restore deleted data after deletion is complete. We are not liable for any litigation prejudice, regulatory consequence, or other harm arising from the permanent deletion of records under our standard retention schedule;
• You are solely responsible for implementing your own litigation hold procedures with respect to your DroneCommand data before your account is closed. Do not rely on our platform as your primary litigation document preservation system without implementing an independent export and preservation workflow.

47.6 Records in a Deceased or Incapacitated Account Holder's Account

The registered account holder may become deceased, legally incapacitated, or otherwise unable to access DroneCommand. The records in that account — including spray records required to be retained under Iowa law — may be needed by surviving business partners, farm heirs, estate administrators, or regulatory authorities for compliance, estate, or litigation purposes. DroneCommand has no automated process for identifying or responding to account holder death or incapacity, and the account will continue on its existing subscription terms until cancelled or until non-payment triggers the standard account termination process described in Sections 9 and 10.

• Access requires credentials or legal authority: Surviving family members, estate administrators, or business partners cannot access a deceased account holder's DroneCommand account without either knowing the account login credentials or presenting legal documentation authorizing access — such as letters testamentary, a court order, or a power of attorney that was in effect before incapacity. We will require legally sufficient documentation before granting access to an account to anyone other than the registered account holder;
• Retention clock continues: Iowa's three-year spray record retention requirement runs from the date of each application — not from the date of account holder death or business cessation. Regulatory obligations to retain and produce records for ongoing agricultural operations do not stop because the account holder has died or become incapacitated. The estate, successor business, or surviving partners are responsible for ensuring records remain accessible;
• Subscription cancellation triggers deletion clock: If the estate or survivors cancel the DroneCommand subscription — either deliberately or inadvertently through non-payment — the standard account deletion timeline begins. Records not exported before the deletion window closes will be permanently deleted. We are not responsible for records deleted under our standard policy because the surviving parties failed to act within the export window;
• Business succession planning: Spray operators who conduct business through a sole proprietorship or personal account should ensure that business succession plans address access to DroneCommand records — including providing login credentials to a successor or designating a business account holder who can maintain access continuity. We cannot provide access to accounts after the account holder's death without legally sufficient authorization;
• We are not liable for any record loss, regulatory consequence, estate administration complication, or other harm arising from the inaccessibility of records in a deceased or incapacitated account holder's account, or from the deletion of records under our standard retention policy because the account was not maintained or records were not exported during the applicable window.

47.7 Corporate Acquisition, Merger, and Business Transfer — Account and Record Continuity

When a DroneCommand customer's business is acquired, merged with another entity, dissolved, or substantially transferred as part of an asset sale, the status of the DroneCommand account and the records it contains becomes a matter requiring deliberate attention. DroneCommand accounts are associated with specific customer entities and login credentials — they do not automatically transfer to an acquiring entity. A business acquisition or merger does not automatically transfer a DroneCommand account to the acquirer, does not extend the existing subscription terms to a successor entity, and does not guarantee continued access to records that were created under the predecessor entity's account.

• Account transfer requires affirmative action: If your business is acquired and the acquirer needs continued access to your DroneCommand spray records — for regulatory compliance, ongoing operations, or due diligence purposes — that access must be established through explicit account management actions before the transaction closes. We do not automatically recognize corporate name changes, employer identification number changes, or entity substitutions as authorizing account access changes;
• Regulatory compliance obligations follow the records, not the acquirer: Iowa's three-year spray record retention requirement runs to the pesticide applicator license holder for whose operations the records were created. An acquiring entity that continues the spray operation under a new or assumed license may have its own record-keeping obligations that do not automatically incorporate the predecessor's records. Record continuity planning should be part of any agricultural business transaction due diligence;
• Asset sale vs. entity acquisition: If a transaction is structured as an asset purchase rather than an entity acquisition, the acquiring party does not step into the predecessor's account by operation of law. The predecessor's DroneCommand account remains associated with the predecessor entity. The acquirer must create a new account or request formal account transfer, subject to our then-current account transfer procedures;
• Pre-close export is essential: The safest approach for any business transaction involving DroneCommand records is to export all relevant records before or at transaction close, regardless of how account access is expected to be handled post-close. Pre-close export ensures records are available even if account access arrangements fall through or are delayed;
• We are not liable for any record loss, compliance gap, regulatory consequence, due diligence failure, or other harm arising from the failure to establish access continuity for DroneCommand records in connection with a business acquisition, merger, dissolution, or asset transfer.

47.8 DroneCommand Records as Business Expense Documentation — IRS and Tax Purposes

Agricultural drone spray operators who use DroneCommand to record their operations may rely on DroneCommand records — along with other business documentation — to support deductions for pesticide expenses, custom application services, equipment costs, and other farm business expenditures on their federal and state tax returns. DroneCommand records documenting applications, products used, and acreage treated may be relevant to substantiating farm expense deductions under IRC Section 162 and Schedule F. DroneCommand is not a tax record-keeping system — its records are designed for Iowa pesticide application record-keeping compliance, not for tax documentation purposes — and we make no representation that DroneCommand records satisfy IRS substantiation requirements for any category of business deduction.

• IRS substantiation requirements differ from Iowa pesticide record requirements: Iowa Administrative Code Chapter 45.26 specifies what a pesticide application record must contain. IRS substantiation requirements for business expense deductions — particularly for farm expenses claimed on Schedule F — may require different, additional, or differently formatted documentation than what DroneCommand spray records provide. The overlap between what Iowa law requires and what the IRS requires is not complete;
• Custom application invoice documentation: If you use DroneCommand to record spray jobs performed for customers, those records may be used to document revenue and associated expenses. However, IRS audit support for custom application income and expenses typically requires invoices, customer payment records, and proof of receipt — documentation types that DroneCommand does not generate or store;
• Section 179 and equipment depreciation: DroneCommand allows equipment registration for operational tracking purposes. Equipment records in DroneCommand are not formatted for, and do not satisfy, the placed-in-service documentation requirements for Section 179 expensing or depreciation schedules. Equipment tax records require specific documentation types beyond what DroneCommand stores;
• Consult a tax professional: Whether DroneCommand records can support a specific tax position — or what supplemental documentation an IRS auditor would require to substantiate a specific farm deduction — is a tax law question that we are not qualified to answer. Consult a CPA or tax attorney for guidance on farm expense substantiation and the role that operational records can play in IRS audit support;
• We are not liable for any disallowed deduction, IRS penalty, tax underpayment, or other tax consequence arising from reliance on DroneCommand records as your primary or sole documentation for a tax deduction or income position, or from the failure of DroneCommand records to satisfy IRS substantiation requirements in an audit.

47.9 Third-Party Subpoena of Your Records Without Your Involvement

In litigation or regulatory proceedings involving third parties — including neighboring landowners, competing chemical applicators, pesticide manufacturers, or other parties not in a direct dispute with you — a party may subpoena DroneCommand for records relating to your account and operations without first notifying you or naming you as a party. We may be legally compelled to produce your records in response to a valid subpoena or court order without your advance consent.

• No advance notice guarantee: While we will attempt to provide you with reasonable notice before producing records in response to a third-party subpoena when legally permitted to do so, we may not be able to provide advance notice in every circumstance, including when a court orders confidential production;
• Scope of production: A subpoena or court order may require production of records beyond what you would voluntarily disclose, including metadata, access logs, audit trails, and records you believe were deleted;
• Cost of compliance: We may seek reimbursement from you for the cost of responding to a third-party subpoena that relates to your account, depending on the scope and complexity of the request;
• Motion to quash: We are not obligated to file a motion to quash or otherwise resist a subpoena on your behalf; if you wish to contest a subpoena, you must retain your own legal counsel and intervene in the proceeding;
• We are not liable for any business harm, competitive disadvantage, litigation exposure, regulatory consequence, or other damage arising from the compelled production of your DroneCommand records in response to a valid subpoena, court order, or other lawful legal process issued in a proceeding to which you are not a named party.

47.10 Pesticide Handler and Worker Exposure Records — WPS Emergency Response Information

The EPA Worker Protection Standard (WPS) requires that certain information about pesticide applications be made available to agricultural workers and handlers, including central posting of application information and emergency contact information for the pesticide product applied. DroneCommand records are not formatted or maintained as WPS-compliant central posting records, and we are not responsible for your compliance with WPS posting, notification, or emergency response information requirements.

• WPS central posting requirement: The WPS requires that application information be posted at a central location accessible to workers before they enter treated areas during the restricted-entry interval; this posting obligation is entirely your responsibility;
• Emergency response information: The WPS requires that the SDS (Safety Data Sheet) for each pesticide applied be accessible for emergency medical treatment; DroneCommand does not store, maintain, or make available SDS documents;
• Handler training records: WPS requires that pesticide handlers receive training; DroneCommand does not store handler training records, certification dates, or WPS compliance documentation;
• Worker exposure incident records: In the event of a pesticide exposure incident, records of what was applied, when, where, and at what rate may be critical for medical treatment; while DroneCommand stores application records, accessing them in an emergency may not be practical;
• We are not liable for any WPS violation, worker injury, regulatory citation, OSHA enforcement action, or other consequence arising from your failure to comply with pesticide handler and worker protection requirements, regardless of whether the relevant application was recorded in DroneCommand.

47.11 Business Name Changes, DBA Records, and Organizational Record Attribution

Spray records and operational records in DroneCommand are associated with the organization name, tenant identifier, and user accounts active at the time the records were created. If your business operates under a different name, undergoes a legal name change, adds or changes a DBA (doing business as) designation, or reorganizes its legal structure, historical records may not automatically reflect the new organizational identity.

• Organization name mismatch in regulatory inspections: Iowa pesticide records may be inspected and compared against licensing records, chemical dealer records, and product labels; if your DroneCommand organization name does not match your Iowa commercial applicator license name, inspectors may question the records' attribution;
• DBA vs. legal entity name: Records created under a DBA name may not be legally sufficient to satisfy recordkeeping obligations that require records to be attributable to the licensed applicator's legal name; consult legal counsel on whether your DroneCommand organization name must match your licensed entity name;
• Post-reorganization access: Following a business reorganization, merger, or dissolution and re-formation, access to records created under the prior organizational identity may require administrative action; we do not automatically transfer records between organizational accounts;
• Name change not retroactive: Updating your organization name in DroneCommand settings updates the display name but does not retroactively relabel historical records in all contexts; exported records may reflect the name at the time of creation;
• We are not liable for any regulatory citation, licensing issue, record attribution dispute, or other consequence arising from a mismatch between your DroneCommand organization name and your legal entity name, licensed applicator name, or DBA designation.

48. Use During Active Drone Operations

DroneCommand is an operational management and record-keeping platform for use before and after flight operations — for pre-flight planning, job dispatch, and post-flight record entry. We strongly advise against viewing, entering data into, or otherwise interacting with DroneCommand on any device while simultaneously and actively piloting or directly controlling an unmanned aircraft.

• No Liability for Distracted Operation: We are not liable for any accident, crash, property damage, personal injury, equipment damage, regulatory violation (including FAA Part 107 visual line-of-sight requirements), crop damage, environmental harm, or any other loss or consequence arising from divided attention caused by or attributed to interacting with DroneCommand while actively operating any aircraft, drone, or other vehicle;
• Your Sole Responsibility for Safe Flight: The safe operation of unmanned aircraft is your sole responsibility at all times during flight. FAA regulations require that remote pilots maintain visual line of sight and situational awareness at all times during operation — using any mobile application during active flight is inconsistent with these obligations. No DroneCommand feature requires real-time interaction during active flight; all planning functions can be performed before flight and all record entry can be performed after flight;
• FAA Compliance: Nothing in the Service is designed, intended, or represented to be used in a manner that would violate FAA Part 107 or any other FAA operational rule governing unmanned aircraft systems.

48.1 DroneCommand Is Not an Airspace Authorization Tool

CRITICAL FLIGHT SAFETY AND REGULATORY DISCLOSURE: DRONECOMMAND IS NOT A PREFLIGHT AIRSPACE PLANNING TOOL AND DOES NOT DISPLAY AIRSPACE CLASSIFICATIONS, TEMPORARY FLIGHT RESTRICTIONS (TFRs), NOTICES TO AIR MISSIONS (NOTAMs), CONTROLLED AIRSPACE BOUNDARIES, NO-FLY ZONES, LAANC AUTHORIZATION GRIDS, STADIUM FLIGHT RESTRICTIONS, PRESIDENTIAL TFRS, OR ANY OTHER AERONAUTICAL DATA RELEVANT TO DETERMINING WHETHER A FLIGHT IS LEGALLY AUTHORIZED UNDER FAA RULES.

• No Airspace Overlays: Field boundary maps and operational maps in DroneCommand do not include any overlay of FAA airspace classifications, controlled airspace boundaries, LAANC coverage areas, or any aeronautical data. The absence of any visual warning or restriction indicator in DroneCommand's map interface does NOT mean that the airspace over a field is uncontrolled, unrestricted, or FAA-authorized for flight;
• Your Obligation to Use Official FAA Tools: Before every flight, you are solely responsible for conducting a complete preflight airspace check using official FAA-authorized tools, including: the FAA's B4UFLY mobile application; LAANC authorization through an FAA-approved UAS Service Supplier (USS); SkyVector or another current aeronautical chart service; and a check for active TFRs through tfr.faa.gov or equivalent. DroneCommand is not a substitute for any of these preflight planning requirements;
• No TFR or NOTAM Integration: DroneCommand does not receive, display, or alert you to Temporary Flight Restrictions, NOTAMs, LAANC authorization status, or any real-time or scheduled airspace restriction data. Flying in an active TFR using DroneCommand as your sole preflight planning tool may result in FAA enforcement action, certificate suspension or revocation, civil penalty, or criminal prosecution under 49 U.S.C. § 46307;
• No Liability for Airspace Violations: We are not liable for any FAA enforcement action, penalty, certificate action, aircraft impoundment, criminal prosecution, property damage, personal injury, or any other consequence arising from your operation of an unmanned aircraft in airspace for which you did not obtain required authorization — regardless of whether DroneCommand was used to plan or record that operation;
• High-Risk Proximity Scenarios: DroneCommand's maps may display a field boundary near an airport, hospital helipad, stadium, military installation, national security area, or other sensitive location without any warning that the overlying airspace may be restricted or require special authorization. You must independently determine the airspace status of every proposed flight location using official FAA tools — do not infer airspace authorization from anything displayed in DroneCommand.

50. Subprocessor and Cloud Infrastructure Security Incidents

DroneCommand relies on third-party infrastructure providers — including cloud hosting companies, database services, content delivery networks, and email delivery services — to provide the Service (collectively "Infrastructure Subprocessors"). In the event of a security incident affecting an Infrastructure Subprocessor:

• Our Responsibility vs. Subprocessor's Responsibility: We are responsible for: (a) selecting Infrastructure Subprocessors with reasonable security credentials; (b) configuring our deployment on those platforms in accordance with security best practices; and (c) notifying you of a breach as described in our Privacy Policy Section 20. We are NOT responsible for security failures caused by vulnerabilities within the Infrastructure Subprocessor's own systems, physical infrastructure, or supply chain, provided we: (i) selected the subprocessor using reasonable diligence; (ii) are not ourselves the direct proximate cause of the vulnerability; and (iii) respond appropriately upon learning of the incident;
• Trade Secret and Competitive Data Exposed in Subprocessor Breach: If a subprocessor breach exposes Customer data — including field coordinates, customer lists, spray records, or pricing — to third parties (including competitors), we will: (a) notify you as required by applicable law and our Privacy Policy; (b) cooperate with your reasonable requests for information about the nature of the breach; and (c) take commercially reasonable steps to contain the breach and prevent further exposure. However, our liability for losses arising from a subprocessor breach — including losses arising from a competitor obtaining your field data or customer information — is subject to the limitation of liability in Section 26. We are not liable for the full value of any trade secrets disclosed, for lost profits attributable to competitive use of disclosed data, or for any consequential harm beyond the limitations in Section 26(B);
• Your Risk Mitigation: You can reduce your exposure by: not entering more data than necessary for operational purposes; using role-based access controls to limit which users can see sensitive data; exporting and storing sensitive regulatory records independently of the Service; and not entering data that you consider extremely high-value trade secrets (such as proprietary crop varieties or precision ag IP) into any cloud-based platform, including ours;
• No Liability for Subprocessor's Own Acts: We are not liable for unauthorized access, exfiltration, or misuse of your data by the subprocessor's own employees, contractors, or hackers exploiting the subprocessor's internal systems, provided we exercised reasonable due diligence in selecting and contracting with that subprocessor and had no prior knowledge of the specific vulnerability exploited.

51. Cognitive Decline and Gradual Incapacity Without Legal Declaration

Section 42 governs access requests where an account holder is deceased or has been declared legally incapacitated by a court. This Section 51 addresses situations where an account holder is experiencing cognitive decline, diminished capacity, or other medical conditions affecting their ability to manage the account — but where no formal legal declaration of incapacity exists and no court-issued authority document has been issued.

• No Action Without Legal Authority: Absent a court order, durable power of attorney, or other legally valid authorization document meeting the requirements of Section 42, we cannot transfer control of an account, accept cancellation requests, or release data to a family member, caregiver, or other party — even one acting with good intentions. We cannot independently assess a person's capacity and cannot act on informal representations about someone's medical condition without legal authority documents;
• Subscription Continues Until Formally Cancelled: An account holder's inability to manage their account due to medical or cognitive reasons does not automatically suspend or terminate their subscription — recurring charges continue until the subscription is formally cancelled through the methods in Section 12 by a person with legal authority to act on the account holder's behalf. We are not responsible for subscription charges that accrue during a period when the account holder lacked the capacity to cancel if no legally authorized representative took action to cancel;
• Preventive Planning Recommendation: If you are concerned about incapacity planning for your business accounts, we recommend: (a) adding a secondary authorized administrator to your DroneCommand account with full account management rights so they can manage or cancel the account if needed; (b) including DroneCommand (and your login credentials, stored securely) in your business succession or estate planning documents; and (c) ensuring a trusted person knows how to access and cancel your account through the Stripe Customer Portal. These preventive steps can avoid prolonged subscription billing during periods of incapacity;
• Limited Billing Review: Upon submission of valid legal authority documents establishing authority to act for an incapacitated individual (such as a subsequently-obtained court guardianship order or power of attorney executed before the incapacity became disabling), we will apply the same discretionary retroactive billing review described in Section 42 — reviewing charges in the thirty (30) days preceding documented notification, on a case-by-case goodwill basis;
• Not Liable for Gradual Capacity Loss: We have no means of monitoring whether an account holder's cognitive status changes over time, and we are not liable for failing to detect, accommodate, or automatically respond to gradual cognitive decline. Our obligation is to provide the Service to the registered account holder and comply with valid legal process from authorized representatives.

52. Third-Party Data Subjects — Landowners, Farmers, and Customer Contacts

DroneCommand's record-keeping features allow you to enter personal information about individuals who are not DroneCommand customers and who have not agreed to these Terms or our Privacy Policy — including landowners whose fields you spray, farmers who hire you, your own customers, and other third parties ("Third-Party Data Subjects"). By entering personal information about Third-Party Data Subjects into the Service, the following applies:

• You Are the Data Controller for Third-Party Data: With respect to any personal information of Third-Party Data Subjects that you enter into DroneCommand, you are the data controller under applicable privacy law. You determine what data to enter, for what purpose, and how it is used. We act solely as a data processor, processing that information on your behalf to provide the Service;
• Your Obligation to Obtain Consent and Provide Notices: You are solely responsible for ensuring that you have a lawful basis to collect and process personal information about Third-Party Data Subjects and to submit it to a cloud-based service. Depending on applicable law and your relationship with each individual, this may require: notifying landowners that their name, address, field locations, and spray history are stored in a cloud platform; obtaining written consent from landowners as required by applicable privacy law; including appropriate disclosures in your service agreements with landowners and farmers; and complying with any privacy rights requests those individuals may make to you;
• Privacy Requests from Third-Party Data Subjects Directed to Us: A Third-Party Data Subject who learns that their personal information is stored in DroneCommand may contact us seeking access, correction, or deletion of their data. Because you are the data controller for their data, such requests must ultimately be handled by you, not us. We will: (a) promptly forward any third-party data subject request to you when we receive it; (b) cooperate with reasonable deletion requests for data about Third-Party Data Subjects, in coordination with you; and (c) not unilaterally delete third-party personal data from your account without your authorization, as that data belongs to your account and may include regulatory records. Our Privacy Policy Section [applicable section] governs how we process and respond to data subject requests;
• Iowa ICDPA, CCPA, GDPR, and Other Privacy Law Compliance: You are solely responsible for ensuring that your collection and entry of Third-Party Data Subject information into DroneCommand complies with all applicable data protection laws, including the Iowa Consumer Data Protection Act (ICDPA), the California Consumer Privacy Act (CCPA/CPRA) if applicable, GDPR if applicable, and any other law that governs your processing of personal data about these individuals. We are not responsible for your failure to comply with privacy law obligations with respect to Third-Party Data Subjects;
• Landowner GPS and Field Data: GPS coordinates and field boundary data you enter for a Third-Party Data Subject's property is particularly sensitive — this constitutes precise geolocation data about that individual's property. You are responsible for ensuring that your collection and storage of this data is lawful, disclosed, and consistent with any confidentiality agreements you have with that landowner;
• Indemnification: You agree to defend, indemnify, and hold us harmless from any claims, complaints, regulatory actions, or fines brought by any Third-Party Data Subject or regulatory authority arising from your collection, entry, or processing of their personal information through the Service in violation of applicable law. This indemnification obligation is in addition to and not in limitation of the general indemnification in Section 27.

53. Personal Device and Bring-Your-Own-Device (BYOD) Security

You and your Authorized Users may access DroneCommand from personal devices — including personal smartphones, tablets, and laptops not owned or managed by your business. You are solely responsible for the security of every device used to access your DroneCommand account, whether company-owned or personal.

• Device Loss or Theft: If a device used to access DroneCommand is lost, stolen, or compromised, an active DroneCommand session on that device may allow the finder or thief to access your account and data without knowing your password. Upon discovering any device loss or theft, you should: (a) immediately log into DroneCommand from another device and revoke the session if session management features are available; (b) change your account password immediately to invalidate active sessions; and (c) contact us at [email protected] if you cannot revoke the session yourself;
• No Device-Level Management by Us: We do not provide mobile device management (MDM) features, remote device wipe, device registration, or any other mechanism for controlling access from specific devices. If a lost or stolen device retains access to your account, the responsibility for that access rests with you — not us;
• Downloaded Exports on Personal Devices: Exported records (PDFs, CSVs) downloaded onto a personal device are no longer protected by our platform's security once they leave the Service. If a personal device containing exported DroneCommand records is lost, stolen, shared, or compromised, we have no visibility into and no responsibility for the security of those downloaded files;
• App Store and Browser Caching: Mobile browsers and some applications may cache session data, autocomplete credentials, or store downloaded files in device memory. You are responsible for configuring your devices and browsers appropriately (e.g., not storing passwords in shared devices, clearing cached data on shared or loaned devices);
• Our Liability: We are not liable for unauthorized access to your DroneCommand account or User Data that occurs as a result of: (a) loss or theft of a device with an active session; (b) a device being used by an unauthorized person because you did not lock or secure it; (c) malware or spyware on a device used to access the Service; or (d) exported records stored on a personal device being exposed through that device's loss or compromise;
• Best Practice Recommendation: For accounts containing sensitive business data, we recommend: using DroneCommand only on devices secured with a PIN, fingerprint, or face ID; logging out of DroneCommand after each session on any shared or personal device; not storing DroneCommand login credentials in a browser on a shared device; and reviewing your active sessions periodically if session management features are available.

54. FAA Drone Registration Records — Not Satisfied by DroneCommand Equipment Tracking

DroneCommand's equipment management features allow you to track your drone fleet — models, serial numbers, service dates, and operational records. Your DroneCommand equipment records are operational management records only and do NOT satisfy any FAA drone registration requirement, nor any other aviation-regulated recordkeeping obligation.

• FAA Part 48 registration is separate: The FAA requires registration of all unmanned aircraft systems under 14 CFR Part 48. FAA registration must be completed through the FAA DroneZone portal (faadronezone.faa.gov) or an equivalent FAA-authorized system — not through DroneCommand. Entering a drone into DroneCommand does not register it with the FAA;
• Registration number marking requirement: Registered drones must display their FAA registration number on the aircraft. This physical marking requirement is separate from any DroneCommand record and is enforced by FAA inspectors examining the physical aircraft — not by software records;
• DroneCommand serial number ≠ FAA registration number: The drone serial number or internal identifier in your DroneCommand equipment records has no relationship to your FAA registration number. They are different identifiers in different systems serving different regulatory purposes;
• Maintenance records: If you log drone service records in DroneCommand (battery cycles, motor replacements, firmware updates), those records do not constitute FAA-required maintenance documentation or airworthiness certification. The FAA does not recognize DroneCommand as an approved recordkeeping system for UAS maintenance;
• Fleet tracking vs. FAA compliance: DroneCommand's fleet management is designed to help you manage your operational assets and maintenance scheduling — it is not designed to satisfy aviation regulatory requirements. For all FAA compliance — registration, certifications, and airworthiness — use FAA-authorized systems;
• We are not liable for any FAA enforcement action, civil penalty, certificate action, or other consequence arising from your drone being unregistered or non-compliant with FAA requirements, regardless of whether that drone was entered into DroneCommand's equipment tracking.

55. Force Majeure — Events Beyond Our Reasonable Control

We will not be liable for any failure or delay in performing our obligations under these Terms to the extent such failure or delay is caused by events beyond our reasonable control, including but not limited to:

• Natural disasters: Earthquakes, floods, tornadoes, hurricanes, ice storms, wildfires, and other natural disasters affecting our servers, offices, service providers, or the internet infrastructure we depend upon;
• Third-party infrastructure failures: Prolonged outages affecting our cloud hosting provider's data centers, internet backbone providers, power grids, or content delivery networks that are beyond our ability to remedy or route around;
• Government actions: Laws, regulations, government orders, embargoes, sanctions, or restrictions that prevent us from continuing to operate or provide the Service in the form described in these Terms;
• Cyberattacks: Ransomware attacks, large-scale distributed denial-of-service attacks, or sophisticated cyberattacks on our infrastructure or on critical infrastructure services we depend on, where we have maintained commercially reasonable security precautions;
• Pandemic or public health emergency: Government-ordered business closures or operational restrictions resulting from a declared public health emergency that prevents our staff from operating the Service;
• Effect on your obligations: A force majeure event does not suspend your regulatory record-keeping obligations under Iowa IAC 45.26 or equivalent law — those obligations exist independently of DroneCommand's availability. You must maintain alternative documentation methods for use during any extended Service unavailability, regardless of cause. If a force majeure event causes uninterrupted Service unavailability lasting more than thirty (30) consecutive days, you may cancel your subscription without the standard advance notice requirements in Section 12;
• No refund obligation: A force majeure event suspends our performance obligations for the duration of the event but does not entitle you to a retroactive refund for the affected period — the force majeure event suspends our obligations without creating liability for the resulting interruption.

56. SaaS-Only Service — No On-Premise, Self-Hosted, or Downloadable Version

DroneCommand is offered exclusively as a Software-as-a-Service (SaaS) cloud-based application. There is no on-premise version, self-hosted version, downloadable desktop application, or any other deployment model available under these Terms. All User Data is stored in our cloud infrastructure; you do not receive a copy of the software to install or operate independently.

• No self-hosted migration path: Because there is no self-hosted version, you cannot migrate your DroneCommand data to a locally controlled server or application instance. Your data is accessible only through our application and in the export formats described in Section 14.3;
• Subscription dependency: Your access to your operational history and records within the application depends on maintaining an active subscription. A lapsed subscription means no in-application access until subscription is restored — unlike a locally installed application, a lapsed SaaS subscription is an access cutoff, not a software lockout;
• No source code or schema access: No license to DroneCommand source code, database schema, or technical implementation is granted under these Terms. You do not acquire any right to the software code by subscribing;
• No custom deployment: We do not currently offer private cloud deployment, dedicated server instances, government-cloud deployment (FedRAMP), or any other deployment model outside our standard multi-tenant SaaS platform. If a dedicated or on-premise deployment is a requirement for your organization, DroneCommand is not currently the right product;
• Representations to the contrary: Any representation by any party that an on-premise or self-hosted version of DroneCommand is available, has been promised, or is planned does not constitute a contractual commitment unless set forth in a signed written agreement executed by a member or manager of Country Road Drone Services, LLC. Verbal promises about software deployment models are not binding;
• Business continuity in the event of our service discontinuation is governed by Section 46 — we commit to providing export access before any planned shutdown, but continued access to your data will require exporting it before account closure since no local software installation will be available.

57. Timezone Handling — Record Timestamps Reflect Your Configured Timezone

DroneCommand displays and stores record timestamps based on the timezone configured for your account or, where applicable, the timezone of your device at the time of record entry. You are responsible for ensuring that your account's timezone setting is correct and that timestamps in your spray records accurately reflect local time at the location where operations occurred.

• Server-side storage: All timestamps are stored internally in Coordinated Universal Time (UTC) and converted for display based on the configured timezone. A record showing an application time of 9:00 AM Central Daylight Time is stored as 14:00 UTC. If your timezone is misconfigured, displayed timestamps may be offset by hours from the actual application time — and your regulatory records will reflect the displayed (incorrect) times, not the actual times;
• Daylight Saving Time transitions: During Daylight Saving Time transitions (spring forward, fall back), records created near the transition boundary may display ambiguous or potentially incorrect times if your device or browser has not correctly handled the transition. We are not liable for timestamp errors caused by device-level or browser-level DST handling;
• Cross-timezone operations: If you operate in a state that observes different DST rules than Iowa — or in any location that crosses a timezone boundary — you are responsible for verifying that record timestamps accurately reflect the actual local time at the spray location. Cross-state, cross-timezone operations are your responsibility to record accurately;
• Regulatory timestamp accuracy: Iowa Administrative Code Chapter 45.26 and similar regulations require that spray records accurately reflect the time of application. A timezone misconfiguration that causes your records to document the wrong time may constitute a regulatory record-keeping violation regardless of whether the error was intentional. We are not liable for regulatory citations arising from timestamp errors caused by your timezone misconfiguration;
• We are not liable for any regulatory violation, insurance dispute, or other consequence arising from timestamp errors caused by timezone misconfiguration, DST handling errors, device clock errors, or any other factor affecting the accuracy of displayed timestamps relative to actual application times.

58. No Third-Party Beneficiaries

These Terms are a contract between you (the Customer) and Country Road Drone Services, LLC. No third party — including your customers, landowners, employees, pilots, contractors, lenders, insurers, regulatory agencies, or any other person or entity — is a third-party beneficiary of these Terms or has any right to enforce any provision of these Terms against either party.

• Your customers: The farmers, landowners, and agricultural businesses who hire you to conduct spray operations are not parties to this agreement and have no rights against us arising from their relationship with you. If your customer suffers crop damage, receives an incorrect invoice, or is otherwise harmed by your operations — including operations planned, dispatched, or recorded using DroneCommand — their remedy is against you, not us;
• Your employees and pilots: Authorized Users who access DroneCommand through your account are not parties to these Terms and have no rights against us arising from their use of the Service under your account. Disputes between you and your employees regarding time records, payroll data, or any other employment matter involving DroneCommand records are not our responsibility;
• Regulatory agencies: IDALS, EPA, FAA, and other regulatory agencies are not parties to these Terms. Nothing in these Terms creates any obligation on our part to any regulatory agency, and no regulatory agency has any right under these Terms to demand that we take or refrain from any particular action with respect to your account;
• Subcontractors and vendors: Our subprocessors, infrastructure providers, mapping providers, and other vendors are not parties to these Terms and have no direct obligations to you arising from these Terms;
• Nothing in this Section limits any third party's rights under applicable law that are independent of these Terms — a landowner who suffers crop damage from your operations retains all their statutory and common-law rights against you regardless of what these Terms say.

59. Phishing and Impersonation Using DroneCommand Branding

Criminals sometimes impersonate legitimate SaaS companies by sending fraudulent emails, creating fake login pages, or making phone calls using the company's name and branding in order to steal account credentials, payment information, or sensitive data. We will never ask you for your DroneCommand password, 2FA code, full credit card number, bank account number, or Social Security number by email, text message, or unsolicited phone call.

• Identifying legitimate DroneCommand communications: Legitimate communications from us will come from [email protected] or another email address at the lamprecht.co domain. We will never communicate from a @gmail.com, @yahoo.com, or any other free email provider in our capacity as Country Road Drone Services, LLC. We will never send unsolicited requests for payment information updates by email that link to a page that is not our actual domain;
• Fake login pages: Phishing attacks sometimes redirect users to fake login pages that visually replicate our login page to steal credentials. Before entering your password on any login screen, verify that the URL in your browser address bar is our actual domain. We will never ask you to log in through a link in an email for routine access — type our domain directly into your browser;
• We are not liable for phishing losses: If you are deceived by a phishing attack using DroneCommand's name, branding, or look-and-feel — and as a result you disclose your credentials, payment information, or other sensitive data to the attackers — we are not liable for the resulting harm. Phishing attacks are third-party criminal conduct that we cannot prevent. We are not the attacker. Your security awareness is your first line of defense against credential theft;
• Report suspected impersonation: If you receive a communication that appears to be from DroneCommand but that you suspect may be fraudulent, do not click any links or provide any information. Forward the communication to [email protected] with subject "Suspected Phishing" so we can investigate and, if appropriate, warn other users;
• If you discover that you have provided credentials or payment information to a phishing attacker using DroneCommand's branding, immediately: (a) change your DroneCommand password; (b) enable two-factor authentication if not already enabled; (c) contact your bank or card issuer to report the potential fraud; and (d) notify us at [email protected] so we can monitor your account for unauthorized access.

60. Screen Sharing, Demonstrations, and Remote Access — Your Data Visible to Others

DroneCommand contains competitively sensitive and potentially legally sensitive information including field locations, customer lists, chemical inventories, pricing, regulatory spray records, employee time records, and financial records. When you share your screen, conduct a product demonstration for a customer or prospect, allow a technician remote access to your device, or record and share a screencast or video that shows your DroneCommand account, all information visible on screen may be seen by the recipients of that session or recording.

• No automatic redaction: DroneCommand does not redact, blur, or hide sensitive fields during screen sharing or remote access sessions. Everything visible on your screen — including field names, customer names, chemical products, application rates, pilot names, and financial data — is visible to anyone who can see your screen. We have no visibility into or control over who is watching your screen at any given time;
• Recording and replay: If you record a screen session in which DroneCommand is visible — including via Zoom, Teams, Loom, or any other recording tool — the recording may capture all visible DroneCommand data and can be replayed, shared, or subpoenaed in future proceedings. Be thoughtful about what is on screen before starting a recording;
• Customer demonstrations: If you demonstrate DroneCommand to a potential customer using your own account with your live data, that customer will see your actual field locations, chemical products, customers, and pricing. Consider using a demo account or test account with non-sensitive data for demonstration purposes;
• IT support and remote desktop: If you grant an IT technician, consultant, or support person remote access to your device during a DroneCommand session, that person can see all DroneCommand data visible on screen. We are not a party to your relationship with your IT vendors and are not liable for data seen by IT personnel you authorize to access your device;
• We are not liable for any disclosure of your data — including regulatory records, customer information, competitive intelligence, or personal data of your employees — to any third party who viewed your screen or recording with or without your awareness. The security of your data at the visual layer is your sole responsibility.

61. Geographic Coverage — Iowa-Focused; Other States Use at Your Own Risk

DroneCommand was designed and built for Iowa-based agricultural drone spray operators. The Service's compliance tools, regulatory field configurations, record-keeping prompts, DriftWatch integration, Iowa BeeCheck integration, and any regulatory guidance content are calibrated primarily to Iowa law. If you use DroneCommand to manage operations in states other than Iowa, you do so with full awareness that the Service was not designed for your jurisdiction's specific regulatory requirements.

• Iowa law is the reference framework: Every DroneCommand record-keeping field, required field designation, record format suggestion, and compliance tool reflects Iowa's requirements first. Non-Iowa operators using these tools will receive an Iowa-centric record format that may or may not satisfy their home state's requirements. We make no representation that DroneCommand satisfies the record-keeping requirements of any state other than Iowa;
• No state-specific regulatory updates for non-Iowa states: We monitor Iowa regulatory updates (Iowa Administrative Code Chapter 45.26, Iowa Pesticide Act, Iowa BeeCheck law). We do not systematically monitor regulatory changes in other states. If a non-Iowa state's requirements change in a way that affects how DroneCommand should be used in that state, we may not update the Service to reflect those changes;
• DriftWatch geographic coverage: DriftWatch's sensitive site registry coverage varies by state. Some states may have minimal or no sensitive site registrations. An absence of sensitive site markers in a state does not mean there are no sensitive sites — it may mean the registry is sparsely populated in that geography. You are responsible for identifying and complying with neighbor notification and sensitive site avoidance requirements under that state's law regardless of what DriftWatch shows;
• International use: DroneCommand is designed for United States agricultural operations. Use of the Service outside the United States is entirely at your own risk. We make no representation that the Service complies with or is suitable for the regulatory, privacy, or operational requirements of any country other than the United States;
• We are not liable for any regulatory violation, license enforcement action, crop damage claim, or other consequence arising from your use of DroneCommand to manage operations in any jurisdiction other than Iowa.

62. Government Program Compliance Records — Not Certified for FSA, USDA, or Crop Insurance Programs

Agricultural drone spray operators may participate in federal and state agricultural programs administered by the USDA Farm Service Agency (FSA), USDA Natural Resources Conservation Service (NRCS), USDA Risk Management Agency (RMA), state extension programs, or other government entities that require or accept spray records as documentation for program compliance, cost-share payments, insurance adjustments, or other purposes. We make no representation that DroneCommand records satisfy the specific documentation requirements of any USDA, FSA, NRCS, RMA, state extension, or other government program.

• Program requirements vary: Government program documentation requirements vary by program, crop year, and administrative agency. FSA may accept certain spray records for compliance verification under one program but require additional information under another. RMA may require specific fields or certifications not present in DroneCommand records. You are responsible for determining the exact documentation requirements for each program in which you participate;
• DroneCommand records are not certified: We are not authorized, approved, or recognized by any USDA agency, FSA office, NRCS office, RMA office, or any state agency as a certified provider of program-compliant records. DroneCommand records are your operational records — their acceptability for any government program is determined by the program administrator, not by us;
• Crop insurance claims: Records submitted in support of crop insurance claims under USDA RMA programs are evaluated by crop insurance adjusters based on program-specific criteria. A DroneCommand spray record that satisfies Iowa IAC 45.26 requirements may still be rejected, questioned, or deemed insufficient by a crop insurance adjuster. We are not liable for insurance claim outcomes attributable to the format, content, or perceived inadequacy of DroneCommand records;
• Conservation program practice documentation: NRCS practice standards for conservation programs may require spray records in specific formats, with specific certifications, or with supporting documents (e.g., practice maps, soil test results, agronomist sign-off) that DroneCommand does not capture. Confirm the specific documentation requirements with your local NRCS office before assuming DroneCommand records will satisfy them;
• We are not liable for any denial, delay, reduction, or recovery of government program payments, insurance proceeds, cost-share payments, or other government program benefits arising from any finding that DroneCommand records did not satisfy the specific requirements of that program.

63. Insurance Certificates and Policy Documents Stored in DroneCommand — Informational Only

DroneCommand may allow you to upload, store, or record insurance certificate information, policy numbers, coverage limits, expiration dates, or other insurance-related documentation for your drone operations, aircraft, employees, or business liability coverage. Any insurance information stored in DroneCommand is informational only — it is not a legal insurance document, does not constitute proof of insurance to any third party, and does not create, modify, or guarantee any insurance coverage.

• Not an ACORD certificate: An ACORD Certificate of Insurance or similar official certificate issued by a licensed insurance broker or insurer is the legally recognized proof of insurance for most commercial purposes. Information you enter into DroneCommand's fields about your insurance is a data record — it is not an ACORD certificate and cannot be presented to landowners, government agencies, or other parties as an official proof of insurance;
• Coverage may have lapsed without updating DroneCommand: If your insurance policy expires, is cancelled, or has its coverage modified after you entered the information into DroneCommand, the stored information will continue to show the prior coverage details. DroneCommand has no connection to your insurance carrier and receives no updates when your policy changes. Expiration dates stored in DroneCommand are only as current as what you entered;
• No coverage verification: We do not verify that insurance policies referenced in DroneCommand are actually in force, that coverage limits are as stated, or that your operations are within covered scope. We are not an insurance verification service. If a landowner, customer, or government agency requires proof of insurance, obtain and provide an official certificate from your broker;
• Gaps in coverage not flagged: DroneCommand does not send alerts when stored insurance expiration dates approach or pass (consistent with our policy regarding credential expiration notices described in Section 17.11). You are responsible for maintaining current insurance coverage and tracking renewal dates through your own management systems;
• We are not liable for any uninsured loss, denied claim, coverage dispute, landowner claim, regulatory penalty, or other consequence arising from insurance coverage information stored in DroneCommand that was inaccurate, incomplete, or not current at the time of a relevant event.

64. Joint Spray Operations — Two Operators on the Same Field; Record Conflicts

Some agricultural spray operations involve two or more licensed drone operators — who may have separate DroneCommand accounts or may operate under a single account — spraying the same field or adjacent portions of a field on the same day or during the same operational period. DroneCommand does not coordinate, merge, or reconcile spray records across different accounts or between different users within the same account when multiple operators document work on the same field.

• Duplicate field records across accounts: If Operator A and Operator B each have their own DroneCommand accounts and each creates a spray record for the same field on the same date, two separate records exist in two separate accounts. There is no mechanism that links these records, prevents duplication, or notifies either operator that the other has also created a record for the same field. Regulatory authorities reviewing both operators' records may see records that appear independent or contradictory;
• Overlapping coverage documentation: When two operators cover different portions of a single field in a single operation, the total acreage documented across both records may exceed or fail to equal the actual field acreage. This discrepancy is your operational documentation problem — we are not responsible for reconciling acreage across operators or accounts;
• Co-applicator regulatory requirements: Iowa IAC 45.26 and equivalent regulations require a licensed applicator to be identified in spray records. When two operators work a single field, the question of which operator's license covers which portion of the application — or whether both must be identified — is a regulatory compliance question you must resolve with your compliance counsel and IDALS guidance;
• Indemnification and liability allocation: In a joint operation, if a regulatory violation, drift incident, or other harm results from the combined spray event, questions of which operator's records, which operator's decisions, and which operator's liability are involved are legal questions between you and your co-operator. We are not a party to those disputes;
• We are not liable for any regulatory compliance failure, record discrepancy, liability allocation dispute, or other consequence arising from joint spray operations involving multiple operators, whether operating under the same account or separate accounts.

65. Non-Sublicensable License — You Cannot Grant Others Access Through Your Account

Your DroneCommand subscription grants you a limited, non-exclusive, non-transferable, non-sublicensable license to access and use the Service for your own internal business operations during the subscription term. You may not sublicense, resell, white-label, or otherwise grant third parties access to the Service through your subscription, including by providing API access, screen-sharing-based service delivery, or any arrangement in which you are effectively reselling or redistributing access to DroneCommand to a third party.

• Service bureau and managed service prohibition: You may not use your DroneCommand subscription to provide record-keeping services to other licensed pesticide applicators who are not your employees or contractors. Operating DroneCommand as a service bureau — where you manage spray records on behalf of separate, independent operators who pay you for that service and who are not Authorized Users under your account — violates this provision;
• Authorized Users vs. sublicensees: You may add employees, pilots, and contractors as Authorized Users under your account for legitimate internal use in your spray operations business. An Authorized User is someone who acts on your behalf in your business — not an independent operator using your account to manage their own separate spray business;
• API and integration restrictions: If DroneCommand offers API access, such access is granted solely for integration with your own business systems. You may not use API access to build a competing service, aggregate data from your account for third-party resale, or provide programmatic access to your DroneCommand account to parties who are not your authorized personnel;
• Consequences of sublicensing: We reserve the right to immediately terminate any account that we determine is being used in violation of this provision, without refund of any prepaid subscription period. Revenue generated through unauthorized sublicensing or resale of Service access does not create any obligation on our part and may be subject to disgorgement;
• This prohibition does not prevent you from discussing DroneCommand with peers, referring colleagues to subscribe for their own accounts, or demonstrating the Service to potential users — only from effectively redistributing access to your own subscription to third parties.

66. Regulatory Whistleblower Cooperation — We Will Cooperate With Lawful Government Investigations

Federal and state whistleblower protection laws, including provisions of FIFRA, the Clean Air Act, the Clean Water Act, and various farm worker protection statutes, protect individuals who report regulatory violations to government authorities. Nothing in these Terms prevents, discourages, or penalizes you or your employees from reporting suspected pesticide law violations, environmental violations, or labor law violations to IDALS, EPA, FAA, OSHA, or any other applicable regulatory authority.

• We will comply with government investigations: If any federal or state regulatory authority conducts an investigation involving our platform — including investigations triggered by whistleblower complaints about a customer's operations — we will cooperate with valid, enforceable legal process as described in Section 40. We will not selectively withhold records to protect any customer from lawful government investigation;
• No gag clause: Nothing in these Terms is intended to, or should be construed as, prohibiting you or your employees from reporting potential violations of law to appropriate government agencies. We will not seek to enforce any confidentiality provision in these Terms to silence a regulatory report or a whistleblower disclosure to a government agency with authority over the reported violation;
• Cooperation with IDALS spray record audits: If IDALS or another regulatory authority requests records related to a specific pesticide application operator's practices — whether initiated by a complaint, an inspection, or a routine audit — we will comply with that legal process. We will, where legally permissible, notify the affected account holder before complying;
• No safe harbor for regulatory violations: These Terms do not create any safe harbor, defense, or reduced obligation with respect to regulatory violations that may be evidenced in DroneCommand records. If your records document violations of pesticide law, labor law, environmental law, or any other applicable regulation, those records are what they are — we have no ability to suppress their content, and compliance with legal process is mandatory;
• We are not liable for any regulatory investigation, enforcement action, fine, license action, or other governmental consequence arising from information produced to regulatory authorities pursuant to valid legal process, whistleblower reports, or our own mandatory legal obligations.

67. Record Continuity When Switching Platforms Mid-Season

Some operators begin a spray season using another software platform or paper records and switch to DroneCommand mid-season. Others may switch away from DroneCommand to another system before the season ends. If your spray records for a single regulatory compliance year are split between DroneCommand and another platform or paper records system, the responsibility for maintaining complete, accessible, and integrated records for that entire year rests entirely with you.

• DroneCommand is not your only compliance record: If you operated on paper or another system before migrating to DroneCommand, your pre-migration records are not in DroneCommand. A regulatory inspector who requests all spray records for a compliance year is entitled to the complete year — including records predating your DroneCommand adoption. You are responsible for maintaining and producing your pre-migration records independently;
• Import limitations: DroneCommand may offer data import tools. Any data imported from another system is only as accurate as the export you provided. We are not responsible for data loss, formatting errors, field mapping errors, or incomplete transfers arising from the import of records from another platform. Verify all imported records against original source records before relying on them for compliance purposes;
• Switching away mid-season: If you cancel your DroneCommand subscription or migrate to another platform before the end of a compliance year, you must export your DroneCommand records before your account enters the deletion window. Records not exported before account deletion are permanently lost and cannot be produced to a regulatory authority. Plan your platform transition to ensure complete record continuity;
• Three-year retention across platforms: Iowa IAC 45.26 and equivalent regulations require 3-year retention of spray records. Your 3-year retention obligation does not reset when you change platforms — it runs from the date of each application. Records from platforms you used in prior seasons must be retained and accessible for the full 3-year period from each application date, regardless of whether you are currently using that platform;
• We are not liable for any regulatory citation, compliance gap, insurance dispute, or other consequence arising from incomplete spray records resulting from your decision to switch platforms, your failure to export records before account deletion, or your failure to maintain records from prior platforms for the required retention period.

68. Records for Estate and Probate Purposes — Regulatory Obligations Do Not Die With the Account Holder

Agricultural spray records maintained under Iowa IAC 45.26 and equivalent state law are associated with the licensed pesticide applicator entity, not solely with the individual who created the account. When an account holder passes away, the regulatory obligation to retain, maintain, and produce those records may continue during the estate administration period, and the successor operator (heir, surviving partner, estate administrator, or business successor) must ensure record continuity. DroneCommand does not automatically transfer, transfer-on-death, or otherwise provide estate-managed access to a deceased account holder's records outside the process described in Section 42.

• Probate access process: The executor or personal representative of a deceased account holder's estate may request access to the account's records for estate administration, regulatory compliance, or legal proceedings by contacting us at [email protected] with subject line "Estate Access Request" and providing Letters Testamentary or equivalent court-issued authority documentation. We will honor valid, properly documented estate access requests as described in Section 42;
• Regulatory record continuity for surviving business: If the account holder's spray operations are being continued by an heir, surviving business partner, or estate — and those continuing operations require access to historical records for regulatory compliance — those parties must obtain account access through the estate process before the account deletion clock expires. We cannot retroactively restore access to an account that was deleted while estate proceedings were ongoing;
• Business succession planning: If you operate a commercial drone spray business and wish to ensure that your records remain accessible to a business successor following your death or incapacity, consult your attorney about: (a) maintaining the account under a business entity that survives you; (b) naming an authorized account user with record-keeping access who can continue operations; and (c) maintaining independent exports of records as part of your business continuity plan;
• Iowa IAC 45.26 retention obligation during estate: The 3-year record retention obligation under Iowa IAC 45.26 is not suspended by the account holder's death. The estate or successor entity may be liable for regulatory violations arising from failure to produce required records during the retention period following the account holder's death;
• We are not liable for any regulatory citation, estate complication, business succession failure, or other consequence arising from failure to timely establish estate access to DroneCommand records through the process described in Section 42.

69. No Verbal Commitments From Technical Support Staff — Written Agreement Required for Any Modification

When you contact our technical support team by email, phone, live chat, or any other channel, you may receive guidance, troubleshooting assistance, feature explanations, and other support communications. Nothing said or written by any technical support staff member, account manager, or any other representative of ours in any support interaction constitutes a modification of these Terms, a binding commitment regarding future features or pricing, a warranty regarding regulatory compliance, or any other contractual obligation not expressly stated in these Terms.

• Support staff cannot modify Terms: Our support team members are authorized to help you use the Service — they are not authorized to modify your subscription agreement, waive any provision of these Terms, commit to pricing changes, promise feature delivery timelines, or make any representation that changes the legal relationship between us. Any such statement from support staff is outside the scope of their authority and is not binding;
• Regulatory guidance from support: If a support staff member provides guidance about regulatory compliance — such as explaining how a DroneCommand feature relates to Iowa IAC 45.26 requirements — that guidance is informational and reflects the staff member's understanding at that time. It is not a legal opinion, a regulatory determination, or a representation that following that guidance will result in regulatory compliance. Consult a licensed compliance attorney for regulatory guidance;
• Feature availability representations: If a support staff member tells you that a specific feature is "available," "coming soon," or "planned," that statement reflects their understanding at that moment and does not constitute a commitment to deliver the feature by any date or at all. Feature availability is governed by what is actually in the Service — not by support communications;
• Modifications must be in writing: The only way to modify these Terms is through a formal written amendment executed by a member or manager of Country Road Drone Services, LLC and delivered to you in writing. An email from a support staff member does not meet this standard — it must be a formal written amendment document signed by authorized management;
• If you believe you were given a material commitment in a support interaction that is not reflected in these Terms, contact us at [email protected] before relying on that commitment. We will investigate and, if appropriate, provide a formal written confirmation. Do not take actions or make business decisions in reliance on unsupported verbal commitments from support interactions.

70. Entire Agreement — Integration Clause

These Terms of Service, together with our Privacy Policy (incorporated herein by reference), and any other written agreements or policies expressly incorporated herein, constitute the complete and exclusive statement of the agreement between you (the Customer) and Country Road Drone Services, LLC with respect to the subject matter hereof — the DroneCommand Service. These Terms supersede and replace all prior and contemporaneous agreements, representations, warranties, negotiations, understandings, and communications between the parties concerning the subject matter, whether written, oral, electronic, or implied, including but not limited to:

• Any representation made in sales conversations, product demonstrations, marketing emails, social media posts, or any other pre-contract communication;
• Any representation made on our website, blog, feature pages, or pricing pages, to the extent inconsistent with these Terms;
• Any understanding arising from prior drafts of these Terms;
• Any understanding arising from informal discussions, forum posts, support ticket exchanges, or any other communication not resulting in a formal written amendment as described in Section 69;
• Any prior terms of service, license agreements, or other agreements that may have governed an earlier version of this Service.

By using the Service, you acknowledge that: (a) you have read these Terms and have had the opportunity to seek independent legal counsel before agreeing; (b) you understand that these Terms constitute a binding contract; (c) you have not relied on any representation not expressly stated in these Terms in deciding to use the Service; and (d) no course of dealing, course of performance, usage of trade, prior conduct, or prior agreement not expressly incorporated herein will be used to supplement, vary, contradict, or interpret these Terms. If any court or arbitrator finds that any term of this integration clause is unenforceable, all other provisions of this Section and these Terms shall remain in full force and effect. The parties intend for this integration clause to be enforced to the maximum extent permitted by applicable law.

71. No Uptime Guarantee or SLA During Peak Spray Season

DroneCommand is a cloud-hosted software-as-a-service platform delivered over the internet. Like all cloud-hosted services, it is subject to unplanned outages, scheduled maintenance windows, third-party infrastructure failures, and performance degradation from traffic surges. We do not provide any service level agreement (SLA) guaranteeing a specific uptime percentage, maximum downtime window, response time objective, or recovery time objective — and this limitation applies equally during peak agricultural spray seasons when your need for access to the Service may be most urgent and most commercially consequential.

• No SLA, no credits, no refunds for outages: We do not provide SLA uptime credits, service credits, pro-rata refunds, or any other form of compensation for service outages, degraded performance, or inaccessibility under any subscription plan, including paid plans. Outage-based compensation or refund requests are not available under any provision of these Terms;
• Peak season risk concentration: Agricultural operations in Iowa are concentrated within specific weather-dependent windows — pre-emergence herbicide applications in spring, fungicide and insecticide applications during mid-season pollination, and harvest aid applications in fall. An outage during a time-critical application window may prevent access to records, field plans, mix calculations, and compliance documentation precisely when those resources are most needed. This risk concentration is inherent in the nature of seasonally-dependent agricultural software and does not create additional liability for us;
• Internet-dependent access: Access to DroneCommand requires a functional internet connection between your device and our servers. Rural operations with marginal cellular or broadband coverage may experience higher rates of access difficulty than suburban or urban users. We are not liable for access difficulties arising from your internet service provider, cellular carrier, rural connectivity limitations, or any other network condition outside our control;
• No offline functionality: DroneCommand does not currently offer offline record creation, editing, or viewing functionality. Records cannot be created, edited, or accessed without an active internet connection to our servers. You are responsible for maintaining paper backup records or other offline contingency processes for time-sensitive operations that cannot be delayed pending restoration of connectivity;
• We are not liable for any record-keeping gap, regulatory citation, crop damage, missed application window, data loss, lost business opportunity, or other operational or legal consequence arising from your inability to access DroneCommand during any outage, planned maintenance window, period of service degradation, or connectivity failure, regardless of the timing, duration, or cause of the inaccessibility.

72. Long-Term Record Export Format Accessibility — Your Retention Obligation Runs Three Years

Iowa Administrative Code Chapter 45.26 requires that pesticide application records be retained for a minimum of three years from the date of application. Over a three-year period, file formats, software platforms, browser technologies, and data-reading tools evolve in ways that may make previously exported files more difficult to open, print, or present. We do not guarantee that spray records exported from DroneCommand will remain in a format that is indefinitely accessible, universally printable, or regulatorily acceptable over the full required retention period — and your three-year retention obligation is your responsibility, not ours.

• Export format availability is not guaranteed: DroneCommand currently supports record export in PDF and CSV formats. We reserve the right to change, add, or discontinue supported export formats at any time. If you export records in a format that is later discontinued, your ability to access those records will depend on the availability of third-party software capable of reading that format — software we do not control, maintain, or guarantee;
• CSV files require interpretation software: CSV (comma-separated value) files are human-readable in a plain text editor but are most useful when opened in spreadsheet software. Future spreadsheet software updates, format changes, or encoding conflicts may affect whether legacy CSV exports render correctly. PDF files are more stable for long-term archival but depend on the availability of a PDF reader and the integrity of the exported file;
• You are responsible for long-term storage: Iowa's three-year retention requirement is a legal obligation that runs to you as the licensed pesticide applicator — not to us as the software vendor. We are not a regulated record repository. You are responsible for maintaining accessible copies of required spray records in a format that remains accessible for the entire required retention period. Best practice: export and locally store records at the close of each spray season in at least two formats;
• Account termination export windows: As described in Section 47, access to records after account termination is limited. If you fail to export records before the post-termination access window closes, and you have not maintained independent copies, your records may become inaccessible. Records that become inaccessible due to your failure to export within the available window are not our responsibility to reconstruct;
• We are not liable for your inability to produce spray records for a regulatory inspection, insurance claim, litigation proceeding, or any other purpose because the export format in which records were saved became inaccessible due to software changes, format discontinuation, account termination, or your failure to maintain locally accessible copies of exported records throughout the required three-year retention period.

73. Clickwrap Agreement Enforceability and Electronic Acceptance

You accepted these Terms through a clickwrap process — clicking a checkbox, clicking "I Agree," or completing account registration while these Terms were presented for your review. Courts across the United States, including federal courts applying Iowa contract law, routinely enforce clickwrap agreements that provide adequate notice of terms and clear manifestation of assent. By completing registration and using the Service, you have entered into a binding legal contract with Country Road Drone Services, LLC, and you may not disclaim knowledge of, or avoid enforcement of, these Terms on the grounds that you did not read them before clicking.

• The duty to read doctrine applies: Under the duty to read doctrine as applied in Iowa contract law, a party who manifests assent to a written agreement — including by clicking an "I Agree" button or completing an online registration form — is bound by the terms of that agreement regardless of whether they actually read it before assenting. The statement "I didn't read it" is not a recognized defense to enforcement of a clickwrap agreement that provided a reasonable opportunity to review;
• Reasonable opportunity to review was provided: These Terms are presented in full before account creation is completed, are available at all times at the Terms URL linked in the footer of the Service and our website, and are not hidden or embedded in fine print in the sign-up flow. Courts examining clickwrap enforceability evaluate whether the terms were reasonably conspicuous and whether the user had a fair opportunity to review them. We have provided that opportunity;
• Electronic acceptance under E-SIGN and UETA: The federal Electronic Signatures in Global and National Commerce Act (E-SIGN Act) and Iowa's Uniform Electronic Transactions Act (UETA), Iowa Code Chapter 554D, provide that electronic signatures — including clicking "I Agree" or completing an online registration — are legally equivalent to handwritten signatures for purposes of contract formation under Iowa law. The electronic nature of your acceptance does not reduce its legal effect or provide grounds to void your agreement;
• Acceptance by continued use after updates: If you continue to use the Service after receiving notice of a material update to these Terms — whether by email, in-app notification, or update to the Terms effective date displayed on this page — your continued use constitutes acceptance of the updated Terms. The obligation to review any update before continuing to use the Service is yours;
• We are not liable for any consequence arising from your election not to read these Terms before accepting them, and you waive any claim that these Terms are unenforceable solely because you chose not to read them before clicking the acceptance mechanism, regardless of the length or complexity of these Terms.

74. Court-Ordered Account Termination and Records Consequences

In certain circumstances, a court of competent jurisdiction, regulatory authority, or other governmental body may issue an order directing us to terminate your DroneCommand account, restrict your access to the Service, freeze your account, or transfer control of your account to another party. We will comply with valid, enforceable court orders and legal process as described in Section 40. If a court orders termination or restriction of your DroneCommand account, the standard account termination consequences described in Section 47 will apply — including the data deletion timelines — with such modifications as the court order itself requires.

• Records consequences of court-ordered termination: If your account is terminated pursuant to a court order, your access to spray records, field data, and other stored data will be subject to the post-termination export window described in Section 47, unless the court order specifically provides otherwise. We may be unable to extend your export window beyond what is technically feasible or legally permissible under the applicable order. If record preservation is important to the underlying proceeding, seek a litigation hold provision as part of the court process before the order issues;
• Account transfer orders: A court or regulatory authority may attempt to transfer control of a DroneCommand account from one party to another — for example, in a business dissolution, marital dissolution, or succession proceeding. We will attempt to comply with such orders, but our ability to transfer accounts is limited by our technical architecture, security procedures, and identity verification requirements. We cannot guarantee that any specific form of transfer will be technically possible;
• No liability for compliance with valid legal process: We are not liable to you for any consequence — including loss of data access, spray record inaccessibility, service interruption, or business disruption — arising from our compliance with a valid court order or legal process directed at your account. Our legal obligation to comply with valid court orders is independent of, and supersedes, any contractual obligation we owe you under these Terms;
• Advance notice limitations in ex parte proceedings: In some circumstances — particularly emergency injunctive orders or orders issued ex parte without your participation — we may receive an order and be required to comply before we can notify you. We will notify you of the order as soon as legally permissible, but the order may be operative before you become aware of it. Seek legal counsel if you believe a court order affecting your account has been issued;
• We are not liable for any record loss, data inaccessibility, business interruption, regulatory consequence, lost opportunity, or other harm arising from our compliance with a validly issued court order, regulatory directive, or other legal process directing us to terminate, restrict, suspend, or modify access to your account or data stored in the Service.

75. DroneCommand Records as Evidence in Your Own Insurance Claim

If you suffer a crop loss, liability claim, property damage event, equipment loss, or other insured incident arising from or related to a drone spray operation, your insurer will likely request access to your spray records — including records stored in DroneCommand. Detailed, accurate spray records can support a legitimate insurance claim by establishing the scope of the operation, the products applied, and the timing of the event. However, the same records can also contain evidence that creates problems for your claim — documentation of off-label applications, applications outside the insured field boundaries, rate deviations, incomplete chemical documentation, or timing inconsistencies that your insurer may cite to support a claim denial, a coverage limitation, or a fraud investigation. DroneCommand records, like all business records, can be used as evidence against you in an insurance proceeding as readily as they can be used in your favor — and detailed records create detailed evidence regardless of what that evidence shows.

• Insurance policy conditions precedent: Many agricultural liability and aviation liability policies require the policyholder to maintain specific records — applicator license records, aircraft registration records, flight logs, application rate logs, or other documentation — as a condition of coverage. If your policy includes such conditions and you have not maintained the required records in DroneCommand or elsewhere, your failure to maintain them may provide your insurer with grounds for a coverage defense, regardless of the underlying merits of your claim;
• Inconsistencies between records and claim narrative: If your insurance claim describes an operation that is materially inconsistent with what your DroneCommand records show — different field, different date, different chemical, different rate, different duration — that inconsistency creates an evidentiary problem. Insurers investigating significant claims routinely compare the claimed operation against all available records, including DroneCommand exports. Unexplained material inconsistencies may support a fraud finding under Iowa insurance fraud statutes;
• Third-party liability claims affecting your coverage: If a neighbor, landowner, property owner, or third party files a liability claim against your aviation or agricultural liability insurance arising from a spray operation, your insurer's coverage investigation will include review of your application records. DroneCommand records documenting a rate deviation, an application to an unauthorized target crop, or any other potential label violation may affect whether your insurer defends the claim or seeks to deny coverage under a policy exclusion for intentional or regulatory-violation conduct;
• Records you cannot fully control in litigation: DroneCommand records may be subpoenaed by your insurer, a third-party claimant, or a regulatory authority independently of your decision to produce or withhold them. Once records exist in DroneCommand, their ultimate accessibility through legal process is not entirely within your control. This is not a reason to falsify or omit records — falsification creates catastrophically worse consequences — but it is a reason to record accurately and completely from the start of every operation;
• We are not liable for any insurance claim denial, coverage limitation or exclusion, fraud investigation finding, premium increase, policy cancellation, or other insurance consequence arising from the content of spray records stored in DroneCommand, regardless of whether those records support or undermine your insurance position, and regardless of how those records came to be produced in the insurance proceeding.

76. Third-Party Data Integrations — Sync Errors and Data Overwrites Are Not Our Liability

DroneCommand may now or in the future offer integrations with third-party data sources — including farm management platforms, precision agriculture tools, ERP systems, weather data providers, mapping services, and regulatory reporting portals. When data flows between DroneCommand and a third-party system — whether via API, file import, webhook, or any other mechanism — errors in that data flow are an inherent risk of integration architecture. We are not responsible for data loss, record overwrite, duplicate records, field mapping errors, encoding errors, synchronization conflicts, or any other data integrity issue arising from data transmitted between DroneCommand and any third-party system.

• Data sync conflicts: When records exist in both DroneCommand and a third-party system, sync operations may create conflicts — particularly when a record has been modified in both systems since the last sync. Conflict resolution logic varies by integration and may result in one system's data overwriting the other's without user notification. The outcome depends on the integration's configuration and is not fully predictable from within DroneCommand;
• Third-party system changes break integrations: Third-party systems change their APIs, data formats, and authentication requirements. These changes can cause previously functional integrations to fail silently — data that appears to be syncing may stop syncing without an error message visible to you. You are responsible for verifying that integrations are functioning correctly after any third-party system update;
• Imported data quality: Data imported into DroneCommand from a third-party system is only as accurate as the source data and the import mapping. Field mapping errors — where a third-party field value is imported into the wrong DroneCommand field — can create spray records with incorrect chemicals, rates, or field identifiers. Always verify imported records against source documentation before relying on them for compliance purposes;
• Integration with regulatory reporting portals: If DroneCommand provides or you use any integration with IDALS, FSA, or other regulatory reporting systems, the data transmitted through that integration is your submission. We are not responsible for formatting errors, transmission failures, or data content errors in regulatory submissions made through or facilitated by DroneCommand integrations;
• We are not liable for any data loss, regulatory citation, financial harm, or other consequence arising from sync errors, data overwrites, import mapping errors, integration failures, or any other data integrity issue occurring in connection with data transmitted between DroneCommand and any third-party system, whether the error originated in our system or the third-party system.

77. Geofencing Features Are Advisory Only — Not a Legal or Regulatory Enforcement Mechanism

DroneCommand may offer geofencing features — tools that display geographic boundaries, generate alerts when a logged operation is outside a defined area, or restrict certain actions within defined zones. These features are operational management tools provided as a convenience. Geofencing features in DroneCommand are advisory — they do not prevent you from conducting operations outside a defined boundary, do not substitute for your own verification of authorized spray areas, and do not constitute any legal determination about where you are authorized to spray.

• Geofencing does not prevent unauthorized applications: A geofencing boundary displayed in DroneCommand does not physically prevent a drone from crossing that boundary or prevent you from recording an operation outside the defined zone. Geofencing is a record-keeping and planning aid — it does not enforce physical limits on drone operations or provide any real-time operational control over aircraft;
• Boundary accuracy depends on your inputs: Geofencing boundaries are only as accurate as the field boundaries and zones you have entered into DroneCommand. If a field boundary is entered incorrectly, a geofencing zone based on that boundary will be equally incorrect. We do not independently verify the accuracy of geofencing boundaries against legal property records, government data, or any other authoritative source;
• Alert thresholds are configurable and fallible: Geofencing alerts may have configurable buffer distances, trigger conditions, or suppression settings. Alerts may fail to trigger due to GPS inaccuracy, mobile device connectivity loss, or software errors. A geofencing alert is a notification — not a guarantee that an operation is within authorized boundaries;
• No regulatory effect: Geofencing boundaries in DroneCommand have no legal status under Iowa pesticide law, FAA regulations, or any other regulatory framework. The fact that an operation was conducted within a DroneCommand geofencing boundary does not establish that the operation was legally authorized, within permitted spray areas, or compliant with any applicable regulation;
• We are not liable for any unauthorized application, trespass, regulatory violation, or other consequence arising from reliance on DroneCommand geofencing features that failed to alert, were inaccurately configured, or did not prevent an operation that exceeded authorized boundaries.

78. No Duty to Audit Your Records — We Do Not Review Records for Accuracy, Completeness, or Compliance

DroneCommand stores the records you create and processes them for the features you use — display, export, reporting, and analysis. We do not independently review, audit, cross-check, or otherwise evaluate the content of your spray records for accuracy, regulatory completeness, internal consistency, or any other quality dimension. We have no duty to review your records, no ability to determine whether a recorded application matches what you actually sprayed, and no obligation to alert you to apparent inconsistencies, suspicious patterns, or probable regulatory violations visible in your own records.

• We are a platform, not a compliance auditor: Providing a platform for record creation is fundamentally different from auditing those records for compliance. We store what you enter. We do not compare your recorded rates against label maximums, flag records where the same field was sprayed twice in violation of a spray interval, identify records where a rate appears to exceed label limits, or perform any other compliance review of record content;
• Apparent inconsistencies in your records are yours to manage: If your records contain apparent inconsistencies — records that show the same field sprayed with incompatible products on the same day, rates that appear to exceed label maximums, or application dates that fall outside normal growing seasons — those inconsistencies are yours to identify and correct through normal editing (before finalization) or to address through legal counsel if they reflect actual compliance events;
• No monitoring for regulatory violations: We do not monitor your spray records for patterns that might indicate regulatory violations — including repeated off-label applications, systematic rate violations, or record-keeping patterns that might suggest fabrication. This is not because we condone violations — it is because we are a record-keeping platform, not a regulatory inspector, and we have no practical ability or legal authority to make those determinations;
• Audits are performed by regulatory authorities, not by us: IDALS inspectors, EPA auditors, and other regulatory authorities are responsible for auditing spray records for compliance. When a regulatory audit of your records occurs, the inspector will apply the applicable legal standards — not our assessment. Our role is to provide records in response to valid legal process as described in Section 40;
• We are not liable for any regulatory violation, license consequence, or other harm arising from the fact that we did not identify, flag, or alert you to an error, inconsistency, or probable compliance issue in your spray records that was visible in the data you entered into DroneCommand.

79. Screenshots and PDF Printouts Are Not Authenticated Original Records

DroneCommand users sometimes take screenshots of spray records or print PDFs from the browser as a quick method of creating a paper record. Screenshots and browser-printed PDFs may be convenient for day-to-day reference, but they differ legally and technically from the authenticated export files that DroneCommand generates through its official export function. Screenshots and browser-printed PDFs do not carry any metadata establishing that the displayed content was unaltered at the time of capture, do not constitute authenticated original records under applicable evidence rules, and may not be accepted by IDALS, EPA, courts, or insurers as equivalent to the original electronic records or official exports generated by DroneCommand.

• Screenshots can be altered: A screenshot is an image file — it captures what appeared on a screen at a moment in time but carries no cryptographic or metadata-based assurance that the content is unaltered. In regulatory proceedings and litigation, opposing parties or regulators may challenge the authenticity of records produced as screenshots rather than as authenticated exports from the system of record;
• Browser-printed PDFs lack official record metadata: Printing a DroneCommand record view to PDF from a browser captures the rendered display but does not embed the underlying data fields, record creation timestamps, edit history, or other metadata that official export files contain. Official CSV and PDF exports generated through DroneCommand's export function are more complete and carry more auditable provenance;
• Use the official export function for compliance purposes: For records you may need to produce to IDALS, EPA, an insurer, an attorney, or a court, use DroneCommand's official export function to generate export files in supported formats. These exports contain more complete data and are generated directly from the database rather than from a screen rendering;
• Long-term storage of screenshots: Screenshots stored only on a personal device or in a cloud photo library may be lost in a device failure, account deletion, or photo library sync error. Official exports stored in a designated records folder on a local or cloud drive with regular backups are more reliable as long-term compliance storage;
• We are not liable for any regulatory citation, evidentiary challenge, record rejection, or other consequence arising from your submission of a screenshot or browser-printed PDF as a substitute for an official DroneCommand export or the original electronic records when a more authoritative format was available and should have been used.

80. AI and Automated Recommendation Features — No Agronomic or Regulatory Liability

DroneCommand may now or in the future incorporate artificial intelligence, machine learning, automated recommendation, predictive analytics, or natural language processing features that suggest application timings, chemical selections, rate optimizations, or compliance actions based on your historical data, weather data, or other inputs. Any AI-generated or automated recommendation, suggestion, alert, or advisory output produced by any DroneCommand feature is provided strictly for informational convenience — it is not agronomic advice, it is not a regulatory compliance determination, and reliance on any automated output without independent verification is at your sole risk.

• AI recommendations may be wrong: Machine learning models produce probabilistic outputs based on training data and input patterns. A recommendation that appears confident, specific, and well-reasoned may nevertheless be incorrect — for reasons including model limitations, out-of-distribution inputs, data quality issues, or simply the inherent uncertainty of agronomic prediction. We make no representation about the accuracy of any automated or AI-generated output produced by the Service;
• No regulatory compliance guarantee from automated outputs: An automated suggestion that a specific product, rate, or timing is appropriate for a specific field does not constitute a determination that the application would be compliant with Iowa pesticide law, FIFRA, or any other regulation. You are responsible for independently verifying label compliance, regulatory compliance, and agronomic appropriateness before acting on any automated suggestion;
• The product label is still the law: Nothing any AI feature or automated system generates supersedes, modifies, or displaces the requirements of the registered pesticide label. The label is the law under FIFRA. An AI recommendation that contradicts the label is wrong by definition, and following it constitutes a label violation regardless of the source of the recommendation;
• Automated alerts are not guaranteed: If DroneCommand provides automated alerts — for weather windows, application timing, REI expiration, or any other trigger — those alerts are best-effort conveniences subject to all of the limitations described in these Terms, including connectivity limitations, system availability, and data accuracy limitations. Do not rely on automated alerts as your sole notification mechanism for time-sensitive compliance events;
• We are not liable for any crop damage, regulatory violation, label violation, financial loss, or other consequence arising from reliance on any AI-generated recommendation, automated suggestion, predictive output, or automated alert produced by any feature of DroneCommand without your independent verification of its accuracy and appropriateness for your specific situation.

81. Currency of Integrated Third-Party Data — Weather, DriftWatch, Iowa BeeCheck, and Other Feeds

DroneCommand integrates data from third-party providers — including weather data services, the DriftWatch sensitive crop registry, Iowa BeeCheck apiary registry, mapping base layer providers, and potentially others. These integrations display third-party data within DroneCommand for your operational reference. We do not control the accuracy, completeness, timeliness, or availability of third-party data feeds, and we do not represent that any third-party data displayed in DroneCommand reflects real-time conditions, current registry status, or accurate information at the moment you view it.

• Weather data accuracy and forecast limitations: Weather data displayed in DroneCommand — including current conditions, wind speed and direction, temperature, and forecast data — is sourced from third-party weather services and is subject to all accuracy limitations inherent in meteorological measurement and forecasting. Wind conditions at the precise location and altitude of your spray operation may differ materially from conditions at the nearest weather station. Weather forecasts are probabilistic and frequently inaccurate. Never substitute DroneCommand's weather display for direct measurement of wind speed and direction at the application site immediately before and during application;
• DriftWatch registry cache delays: DriftWatch registry data displayed in DroneCommand is subject to caching and synchronization delays described in Section 21. A DriftWatch registration entered by a sensitive crop producer the morning of your planned application may not appear in DroneCommand's display if the cache has not refreshed. The DriftWatch system is a voluntary registry, and non-participation by affected producers does not remove your obligation to avoid drift onto their crops;
• Iowa BeeCheck registry completeness: Iowa BeeCheck participation is voluntary, and the majority of Iowa apiary locations are not registered. A display showing no nearby registered hives does not represent a comprehensive map of actual hive locations. You are responsible for independent awareness of nearby bee colonies through physical scouting, landowner inquiry, and neighbor communication;
• Third-party data outages affect display, not your obligations: If a third-party data feed is unavailable — due to the provider's downtime, API changes, or connectivity issues — data that would normally be displayed may be absent or stale in DroneCommand. The unavailability of third-party data does not suspend or reduce your legal obligations to avoid drift, notify beekeepers, or comply with any other applicable requirement;
• We are not liable for any crop damage, apiary loss, neighbor claim, regulatory citation, or other consequence arising from reliance on third-party data displayed in DroneCommand — including weather data, DriftWatch registry data, Iowa BeeCheck registry data, or any other third-party data feed — that was inaccurate, incomplete, stale, or unavailable at the time of your application.

82. Multi-State Operations — These Terms Are Iowa-Centric and May Not Satisfy Other States' Requirements

DroneCommand is designed for agricultural drone spray operators operating primarily in Iowa, and the compliance references in these Terms — Iowa Administrative Code Chapter 45.26, Iowa pesticide applicator licensing, Iowa pesticide label requirements, and Iowa-specific regulatory agencies — reflect Iowa law. Drone spray operators who conduct commercial operations in Nebraska, South Dakota, Minnesota, Missouri, Wisconsin, or any other state are subject to those states' independent pesticide application record-keeping requirements, licensing requirements, and regulatory frameworks. DroneCommand's record fields, required field structure, and regulatory language are aligned with Iowa requirements — they may not satisfy the specific format, content, or retention requirements of other states in which you operate.

• State pesticide record-keeping requirements vary: Each state in which commercial pesticide applications are made has its own administrative code governing record-keeping requirements. Some states require different fields, different retention periods, different applicator identification formats, or different product information than Iowa requires. DroneCommand's default record structure is not necessarily compliant with other states' requirements, and we make no representation that it is;
• Licensing reciprocity is not universal: Some states recognize Iowa commercial pesticide applicator licenses through reciprocity agreements; others require separate in-state licensure. Operating under an Iowa license in a state that does not recognize it is a regulatory violation in that state. DroneCommand does not track multi-state licensing status or alert you when an operation is in a jurisdiction where your Iowa license may not be sufficient;
• Tribal and federal lands have distinct requirements: Operations on or adjacent to tribal trust lands, federal public lands, military reservations, or other federal jurisdiction may be subject to federal pesticide law, Bureau of Indian Affairs regulations, or tribal law — not state law — and DroneCommand's Iowa-centric record structure may not satisfy those requirements;
• Consult the regulatory authority in each state of operation: Before conducting commercial spray operations in any state other than Iowa, consult the relevant state department of agriculture to determine what licensing, record-keeping, and reporting requirements apply to your specific operations. Do not assume that Iowa compliance equals compliance in other jurisdictions;
• We are not liable for any regulatory violation, license enforcement action, or other consequence arising from your reliance on DroneCommand records for compliance purposes in a state whose record-keeping requirements differ from Iowa's requirements that the Service was designed to support.

83. Satellite Imagery Staleness — Base Map Images May Be Months or Years Old

The satellite and aerial imagery displayed as base maps in DroneCommand is sourced from third-party mapping providers. This imagery is not real-time — it is captured at intervals by satellite or aircraft and may be months to years old at any given time. Agricultural fields, drainage infrastructure, hedgerows, buildings, waterways, and other features that are visible in DroneCommand's base map imagery reflect the condition of the field at the time the imagery was captured — which may differ significantly from current field conditions. DroneCommand does not disclose the capture date of base map imagery, does not guarantee currency of any map layer, and cannot control when third-party providers update their imagery for any specific geographic area.

• Field changes not reflected in imagery: Tile outlet structures installed last season, new drainage channels, recently erected buildings, newly planted windbreaks, and other field changes that occurred after the imagery was captured will not appear in DroneCommand's base map. Operating based on outdated imagery that does not reflect current field conditions creates safety and compliance risk that physical pre-flight scouting — not digital mapping — is designed to address;
• Waterway and drainage feature currency: Drainage infrastructure — tile outlets, surface inlets, drainage channels, and retention areas — changes more frequently than most imagery update cycles. A drainage modification completed last year may not appear in DroneCommand's base map. Buffer zone requirements around drainage features apply based on actual field conditions, not based on what is visible in imagery;
• Building and structure identification: New buildings, grain bins, livestock confinements, and other structures built after imagery capture will not appear on the base map. A drone operation planned around a base map that does not show a recently constructed building adjacent to the field creates collision and operational risk;
• Imagery currency for CRP and conservation features: CRP enrollments, native prairie restorations, and wetland reserve easements established after imagery capture will not be visible as conservation features in the base map — they may appear as commodity cropland in outdated imagery. This is one reason why CRP and wetland identification requires consulting FSA and NRCS records rather than relying on visual imagery inspection;
• We are not liable for any operational error, collision, safety incident, buffer zone violation, or other consequence arising from reliance on base map satellite imagery that did not reflect current field conditions because the imagery was captured before the relevant field changes occurred.

84. Compliance Checklists and Regulatory Guidance Documents — Informational Only, Not Legal Advice

DroneCommand may publish, link to, or make available compliance checklists, regulatory summaries, how-to guides, seasonal spray preparation guides, or other documents describing regulatory obligations relevant to agricultural drone spray operators. These documents are published as an educational service to our users and are not a substitute for legal advice, consultation with IDALS, EPA, or FAA, or review of the applicable regulations themselves. Compliance checklists and regulatory guidance documents published by DroneCommand may be incomplete, may not reflect the most current regulatory requirements, may not apply to your specific license category or state of operation, and do not constitute legal advice or a legal compliance opinion.

• Regulations change faster than documents: IDALS, EPA, and FAA update regulations, guidance documents, and enforcement policies on an ongoing basis. A compliance checklist published by us six months ago may not reflect a regulatory amendment that took effect last month. We do not commit to maintaining compliance documents in real-time synchronization with regulatory changes, and the publication date — if visible — is the only indication of how current the document may be;
• Checklists are necessarily incomplete: A checklist that covers the most common compliance obligations for a typical Iowa commercial drone spray operator does not cover every obligation that may apply to your specific license type, operation type, geographic area, customer base, or equipment configuration. A checklist is a starting point — not an exhaustive compliance audit. Checking all boxes on a checklist does not guarantee regulatory compliance;
• No attorney-client relationship: Nothing in any compliance document, regulatory summary, checklist, or other guidance content published by us creates an attorney-client relationship, constitutes legal advice, or makes us your legal compliance advisor. We are a software company — not a law firm. For legal compliance questions specific to your operation, consult a licensed Iowa attorney with pesticide, agricultural, or aviation law experience;
• Documents are not binding on regulators: IDALS, EPA, and FAA are not bound by the content of compliance documents we publish. An IDALS inspector who conducts an inspection of your operation applies the applicable regulations — not our checklist. The existence of our compliance document as a resource does not affect the standards to which your operation will be held;
• We are not liable for any regulatory violation, license consequence, enforcement action, or other harm arising from reliance on a compliance checklist, regulatory summary, or guidance document published by us that was incomplete, outdated, or not applicable to your specific regulatory situation.

85. Statute of Limitations — Use of Service Does Not Toll Any Limitation Period

The use of DroneCommand to record, store, or manage agricultural spray records does not extend, toll, suspend, or otherwise affect any applicable statute of limitations or repose period under Iowa law or any other jurisdiction's law. Your legal obligation to preserve evidence and assert claims within applicable limitation periods is entirely your own responsibility, and the existence of records in DroneCommand does not substitute for timely legal action.

• No tolling by recordkeeping: Maintaining records in DroneCommand does not toll the statute of limitations for any claim you may have arising from a crop loss, equipment failure, pesticide injury, or other agricultural incident;
• Iowa limitation periods: Iowa's statute of limitations for personal injury is two years; for property damage, five years; for written contracts, ten years; for oral contracts, five years — these periods run from the date of the incident regardless of when you created or exported records from DroneCommand;
• Discovery rule nuances: Whether the discovery rule applies to toll a statute of limitations for latent pesticide injuries, soil contamination, or other conditions that manifest over time is a legal question that we are not qualified to evaluate and that DroneCommand does not assess;
• Retention vs. limitation periods: The Iowa Administrative Code Chapter 45.26 three-year spray record retention requirement is a regulatory recordkeeping obligation and is entirely separate from civil statutes of limitations; satisfying one does not satisfy the other;
• We are not liable for any time-barred claim, forfeited legal right, or other consequence arising from your failure to assert a legal claim within an applicable statute of limitations period, regardless of whether records of the underlying incident are preserved in DroneCommand.

86. Beta Features, Early Access Programs, and Pre-Release Functionality

From time to time, DroneCommand may offer access to features that are in beta, early access, or pre-release status ("Beta Features"). Beta Features are provided for evaluation purposes and are subject to reduced stability, reliability, and support commitments. Spray records, application data, or operational records created using Beta Features may be lost, corrupted, or rendered inaccessible without notice or recovery options.

• No stability guarantee: Beta Features may contain bugs, errors, or performance issues that cause data loss, incorrect calculations, or feature unavailability; we do not warrant that Beta Features will function correctly or that data entered using them will be preserved;
• Iowa regulatory records not appropriate: You should not rely on Beta Features to create, store, or manage spray records required under Iowa Administrative Code Chapter 45.26; use only stable, production-released features for regulatory recordkeeping;
• Feedback and data use: By participating in a Beta Feature program, you consent to our collection and analysis of your usage data and feedback for product improvement purposes;
• Discontinuation without notice: Beta Features may be discontinued, modified, or promoted to production status at any time; data created in a Beta Feature that is discontinued may not be migrated to the production version of the Service;
• We are not liable for any data loss, record corruption, regulatory citation, crop loss, or other consequence arising from your use of Beta Features or early access programs, regardless of whether the feature was labeled as beta at the time you used it.

87. Pricing Page, Marketing Materials, and Feature Representations

The pricing page, feature comparison tables, marketing emails, blog posts, sales presentations, and other promotional materials published by us describe the Service in general terms and are subject to change without notice. Statements made in marketing materials do not constitute warranties, representations, or contractual commitments regarding the availability, accuracy, or performance of any feature of the Service.

• Pricing subject to change: Pricing listed on our website is subject to change at any time; the price you pay is governed by your current subscription agreement and any applicable renewal terms, not by the price listed on our marketing page at any given moment;
• Feature availability may vary: Features listed in marketing materials or feature comparison tables may be available only in certain subscription tiers, may require configuration to enable, or may be under development and not yet available;
• Third-party integration representations: Statements regarding integrations with third-party services (weather providers, satellite imagery, compliance databases) describe integrations that exist as of the time of publication and do not guarantee that such integrations will remain available;
• Sales representations: Oral or written representations made by sales personnel, resellers, or affiliates are not binding on us unless confirmed in a written amendment to your subscription agreement signed by an authorized officer of Country Road Drone Services, LLC;
• We are not liable for any business decision, investment, loss of opportunity, or other harm arising from reliance on statements in our pricing page, marketing materials, feature announcements, or sales presentations that were not reflected in your executed subscription agreement.

88. Force Majeure — Service Unavailability Beyond Our Reasonable Control

DroneCommand shall not be liable for any failure or delay in the performance of the Service arising from causes beyond our reasonable control, including but not limited to natural disasters, acts of God, flood, fire, earthquake, severe weather, pandemic, acts of war or terrorism, civil unrest, governmental action, internet service provider failures, cloud infrastructure outages, power grid failures, cyberattacks, denial-of-service attacks, or other events beyond our reasonable control ("Force Majeure Events"). During a Force Majeure Event, your obligation to comply with applicable pesticide recordkeeping laws — including Iowa Administrative Code Chapter 45.26 — remains in effect regardless of Service availability.

• Alternative recordkeeping required: You must maintain the ability to create and preserve required spray records through alternative means (paper records, spreadsheets, other software) in the event that DroneCommand is unavailable during a spray season, regardless of the cause of unavailability;
• Cloud and infrastructure dependencies: DroneCommand depends on third-party cloud infrastructure, internet connectivity, and DNS services; outages affecting these dependencies may render the Service unavailable for extended periods without advance notice;
• No liability during outage: We are not liable for any regulatory citation, crop loss, missed application window, or other damage arising from Service unavailability during a Force Majeure Event or any other infrastructure failure beyond our reasonable control;
• Subscription fee suspension: Force Majeure Events do not automatically suspend or prorate subscription fees; fee adjustments during extended outages, if any, are at our sole discretion;
• We are not liable for any loss, damage, regulatory violation, or missed business opportunity arising from Service unavailability caused by a Force Majeure Event, regardless of the duration of the outage or its impact on your operations.

89. Your Indemnification Obligations

You agree to defend, indemnify, and hold harmless Country Road Drone Services, LLC, its members, managers, employees, contractors, agents, successors, and assigns (collectively, "Indemnitees") from and against any and all claims, demands, suits, proceedings, liabilities, judgments, losses, damages, penalties, fines, costs, and expenses (including reasonable attorneys' fees) arising out of or relating to: (a) your use of the Service; (b) your violation of these Terms; (c) your violation of any applicable law, regulation, or third-party right; (d) spray records, application data, or other content you submit to the Service; or (e) any claim by a third party arising from your drone operations, pesticide applications, or agricultural activities.

• Third-party claims: If a neighboring landowner, drift-affected farmer, regulatory agency, or other third party brings a claim against us arising from your operations recorded in DroneCommand, you are obligated to defend and indemnify us against that claim;
• Regulatory enforcement: If your use of the Service or your spray operations result in a regulatory investigation, inspection, or enforcement action that names or involves us, your indemnification obligation covers our costs of response and defense;
• Scope of indemnification: Your indemnification obligation includes claims arising from the accuracy or inaccuracy of records you entered, the legality of the pesticide applications you performed, and any representations you made to third parties about your compliance;
• No indemnification for our gross negligence: Your indemnification obligation does not apply to claims arising solely from our own gross negligence or willful misconduct;
• We reserve the right to assume control of the defense of any claim subject to your indemnification at our own expense; your obligation to indemnify us survives the termination of these Terms and your account.

90. Dispute Resolution — Mandatory Individual Arbitration and Class Action Waiver

This section supplements Section 31. In the event of any conflict between this section and Section 31, the provision more favorable to dispute resolution efficiency shall govern.

Any dispute, claim, or controversy arising out of or relating to these Terms, the Service, or your relationship with Country Road Drone Services, LLC that cannot be resolved informally shall be resolved by binding individual arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, with venue in Polk County, Iowa. YOU WAIVE YOUR RIGHT TO A JURY TRIAL AND YOUR RIGHT TO PARTICIPATE IN ANY CLASS ACTION, CLASS ARBITRATION, OR REPRESENTATIVE PROCEEDING OF ANY KIND.

• Individual claims only: All arbitration proceedings must be conducted on an individual basis; you may not consolidate your claims with those of any other user, and no arbitrator may award relief to any person other than as an individual claimant;
• Informal resolution first: Before initiating arbitration, you must provide written notice of your dispute to us at the address in Section 49 and allow thirty (30) days for informal resolution; many disputes can be resolved without arbitration;
• Arbitration costs: Arbitration filing fees and costs are governed by the AAA Commercial Arbitration Rules; for claims under $10,000, we will pay the filing fee if you are the claimant and the dispute is not frivolous;
• Injunctive relief exception: Either party may seek temporary injunctive or other equitable relief in any court of competent jurisdiction in Polk County, Iowa to prevent irreparable harm pending arbitration;
• If the class action waiver in this section is found unenforceable for any reason, the entire arbitration agreement in this section shall be void and disputes shall be resolved in the state or federal courts located in Polk County, Iowa, to which you irrevocably consent to personal jurisdiction and venue.

91. Limitation on Damages — Exclusion of Consequential and Indirect Damages

To the maximum extent permitted by applicable law, in no event shall Country Road Drone Services, LLC, its members, managers, employees, or agents be liable to you or any third party for any indirect, incidental, special, consequential, punitive, or exemplary damages, including but not limited to lost profits, lost revenue, lost data, loss of goodwill, crop losses, business interruption, or cost of substitute services, arising out of or in connection with these Terms or the Service, even if we have been advised of the possibility of such damages. Our total aggregate liability to you for all claims arising out of or relating to these Terms or the Service shall not exceed the greater of: (a) the total fees paid by you to us during the twelve (12) months immediately preceding the event giving rise to the claim; or (b) one hundred dollars ($100.00).

• Crop loss exclusion: We are specifically not liable for crop losses, yield reduction, application failures, or agricultural economic losses arising from any aspect of the Service, including inaccurate records, feature unavailability, or reliance on data displayed by the Service;
• Regulatory fine exclusion: Regulatory fines, civil penalties, license suspensions, or other governmental enforcement consequences arising from your use of the Service or the content of your records are not recoverable from us;
• Third-party claim costs: Costs and damages you incur in defending or settling third-party claims — including neighbor drift claims, beekeeper claims, and trespass claims — are consequential damages excluded from our liability;
• Some jurisdictions: Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages; in such jurisdictions, our liability is limited to the fullest extent permitted by law;
• The limitations in this section apply regardless of the theory of liability — whether in contract, tort (including negligence), strict liability, or otherwise — and shall apply even if any limited remedy fails of its essential purpose.

92. Entire Agreement — Supersession of Prior Representations

These Terms of Service, together with the Privacy Policy, any executed subscription agreement, and any written amendments signed by an authorized officer of Country Road Drone Services, LLC, constitute the entire agreement between you and us with respect to the Service and supersede all prior and contemporaneous agreements, representations, warranties, and understandings, whether oral or written. No prior course of dealing, industry custom, trade usage, or prior representations made by any employee, contractor, or agent of Country Road Drone Services, LLC shall be considered part of this agreement unless expressly incorporated herein by written amendment.

• Sales representations superseded: Any representation made during the sales process, in a product demonstration, or in pre-contractual negotiations that is inconsistent with these Terms is superseded by these Terms and is not binding on us;
• Email and chat communications: Support emails, chat transcripts, and other informal communications from our team do not constitute amendments to these Terms and do not create enforceable commitments that override these Terms;
• Previous versions superseded: Each update to these Terms supersedes all prior versions; your continued use of the Service after an update constitutes acceptance of the updated Terms;
• Written amendment requirement: Any amendment to these Terms requires a written agreement signed by an authorized officer of Country Road Drone Services, LLC and expressly stating that it amends these Terms;
• If there is any conflict between these Terms and any other document purporting to govern your use of the Service, these Terms shall control unless the other document is a duly executed written amendment signed by an authorized officer of Country Road Drone Services, LLC expressly superseding a specific provision of these Terms.

93. Severability, Waiver, and Assignment

If any provision of these Terms is found to be invalid, illegal, or unenforceable under applicable law, that provision shall be modified to the minimum extent necessary to make it enforceable, or if it cannot be so modified, severed from these Terms, and the remaining provisions shall continue in full force and effect. Our failure to enforce any provision of these Terms shall not constitute a waiver of our right to enforce that provision in the future, and no waiver of any provision shall be construed as a waiver of any other provision.

• Severability of arbitration provisions: If any part of the arbitration or class action waiver provisions in Section 90 is found unenforceable, the remaining provisions of Section 90 shall continue in effect to the maximum extent permitted;
• Course of conduct not a waiver: Our past practice of not enforcing a particular provision — for example, accepting late payments without penalty — does not obligate us to continue that practice and does not waive our right to enforce that provision strictly in the future;
• Assignment by us: We may assign these Terms, and our rights and obligations hereunder, to any successor entity in connection with a merger, acquisition, or sale of all or substantially all of our assets, without your consent;
• No assignment by you: You may not assign your rights or obligations under these Terms to any third party without our prior written consent; any purported assignment without consent is void;
• Section headings in these Terms are for convenience only and do not affect the interpretation of any provision; references to "including" mean "including without limitation" unless the context clearly requires otherwise.

94. Compliance Documents Feature — FAA Waiver and Exemption Storage

DroneCommand includes a Compliance Documents section where operators may store information about FAA waivers, exemptions, certificates, and other regulatory documents. The following disclaimers apply to this feature:

• Documents stored in the Compliance Documents section are informational records only — they are not live-linked to FAA DRACR, IACRA, or any other FAA database. DroneCommand has no integration with FAA systems and does not retrieve, verify, or update document status from any FAA data source;
• Expiration dates displayed in the Compliance Documents section are entered by the user and are not verified against any FAA registry. If you enter an incorrect expiration date, DroneCommand will display that incorrect date without any indication of error;
• Displaying a waiver or exemption as "active" in DroneCommand is a reflection of user-entered data, not a compliance determination. It does not verify the waiver's current legal status with the FAA and does not constitute a representation by DroneCommand that the waiver or exemption is valid, current, or applicable to your operations;
• DroneCommand does not monitor FAA waiver status, administrative revocations, geographic limitation changes, scope modifications, or any other changes to waiver status after initial entry. If the FAA revokes, modifies, or limits your waiver after you enter it in DroneCommand, DroneCommand will continue to display it as entered unless you manually update the record;
• The Compliance Documents feature is a document storage and organizational tracking tool, not a compliance management system or legal advisory service. Using this feature does not constitute legal compliance and does not reduce your obligation to independently verify the status of all waivers and exemptions;
• Operators are solely responsible for verifying the current status of all waivers and exemptions directly with the FAA before conducting any operation authorized by those waivers. You should not rely on DroneCommand's Compliance Documents display as confirmation that a waiver is currently valid;
• We are not liable for any enforcement action, certificate action, fine, penalty, or operational consequence arising from reliance on Compliance Documents feature data, including reliance on an expiration date, status indicator, or other information displayed in that feature.

95. Heatmap and Flight Log Visualization — Analytical Displays Are Not Certified Coverage Records

DroneCommand provides heatmap and flight log visualization features that display recorded GPS flight-path data in a graphical format. The following disclaimers apply:

• The heatmap is a visual representation of recorded GPS flight-path data, not a precision agronomic coverage analysis or certified application coverage record. The heatmap does not measure, calculate, or verify actual spray coverage, application uniformity, or product deposition;
• Heatmap color intensity reflects recorded flight-path density — that is, how many recorded GPS coordinates fall within a given area — not verified chemical application rates, volumes, coverage uniformity, or any other agronomic parameter. A darker color indicates more recorded flight path passes, not a greater volume of product applied;
• GPS accuracy limitations — including signal loss, multipath errors, satellite geometry, and recording gaps caused by device, connectivity, or software issues — directly affect heatmap display accuracy. Displayed patterns may not represent actual spray coverage. Gaps in the heatmap may reflect GPS recording gaps rather than actual missed coverage areas, and vice versa;
• Overlapping colors on the heatmap do not constitute evidence of over-application or double-treatment. The heatmap cannot measure or confirm actual chemical deposition at any location;
• Flight log groupings displayed in DroneCommand are organizational conveniences for display and record-management purposes and do not constitute regulatory record categories under Iowa Administrative Code Chapter 45.26 or any other regulatory framework;
• Heatmap visualizations are not admissible as precision application evidence in any regulatory proceeding, court case, or insurance claim — operators should not rely on heatmap data to establish or rebut compliance with application rate requirements, coverage specifications, or any other regulatory or contractual standard;
• We are not liable for any claim, enforcement action, regulatory citation, insurance dispute, or other consequence arising from interpretation of heatmap visualization data as evidence of coverage, compliance, or application accuracy.

96. Visited Fields Map — Historical Activity Display

DroneCommand includes a Visited Fields map that displays fields for which spray records have been created in your account. The following disclaimers apply:

• The Visited Fields map displays fields for which spray records have been created in your DroneCommand account — it is a derived visualization of your account's data, not an independent audit of actual field visits or spray operations. The map reflects only what has been entered in your account and does not independently verify whether operations were actually conducted;
• "Visited" status on the map reflects the existence of at least one spray record associated with that field in your account and does not distinguish between application visits, planning entries, test records, or records entered in error. A field marked as "visited" may reflect a planning-only entry or an erroneously entered record rather than an actual spray operation;
• The Visited Fields map is not an audited or certified record of all locations accessed by you or your Authorized Users. It does not function as a location history, access log, or compliance audit trail for any purpose;
• Geographic coordinates and field boundary data displayed on the Visited Fields map are subject to the same GPS and geospatial accuracy limitations described in Section 19. Field boundaries are user-defined or GPS-derived approximations and may not correspond precisely to actual legal parcel boundaries;
• We are not liable for any claim, enforcement action, trespass dispute, or other consequence arising from interpretation of Visited Fields map data as evidence of presence, access, application, or non-application at any geographic location.

97. Satellite and Aerial Imagery — Vintage, Accuracy, and Third-Party Sourcing

DroneCommand may display satellite or aerial imagery sourced from third-party providers for field orientation and planning purposes. All imagery reflects conditions at the time of image capture, which may be substantially in the past, and is not a real-time representation of field conditions.

• Imagery reflects past conditions only: Satellite and aerial imagery displayed in DroneCommand is sourced from third-party providers and reflects conditions at the time of image capture, which may be weeks, months, or years prior to the current date — imagery does not reflect current field conditions, crop status, drainage patterns, flood extent, or structure locations;
• Vintage varies by region: Imagery vintage varies by geographic region and provider availability — imagery displayed for one field may be significantly older than imagery displayed for an adjacent field, and no uniform recency standard is guaranteed;
• General orientation use only: Imagery is provided for general orientation and planning purposes only — it is not a real-time representation of field conditions and must not be relied upon as the sole basis for spray operation planning, sensitive receptor identification, or boundary determination;
• Property boundaries are approximate: Property boundary lines displayed over imagery are derived from public GIS data and may not accurately reflect legal parcel boundaries — operators are responsible for independently verifying field boundaries before spray operations;
• Acreage estimates are approximate: Imagery-based acreage estimates are approximate and may not match surveyed acreage — billing based on acreage estimates from imagery may differ from surveyed acreage, and DroneCommand is not responsible for acreage discrepancies;
• Sensitive receptors may postdate imagery: Imagery does not reflect the current presence of sensitive receptors — including apiaries, organic operation buffer zones, or surface water features — that may have been established or altered after the image capture date;
• We are not liable for any operational decision, trespass incident, drift event, crop damage claim, or regulatory consequence arising from reliance on imagery-based representations of field conditions, boundaries, acreage, or sensitive receptor locations.

98. Intellectual Property in Operator-Uploaded Documents — Labels, SDS Sheets, and Third-Party Materials

Operators may upload pesticide labels, Safety Data Sheets, waiver documents, certificates, and other materials to DroneCommand for operational reference. Operators represent that they have the right to upload and store any materials they submit to the platform.

• Operator represents upload rights: Operators who upload pesticide labels, SDS sheets, waiver documents, certifications, or other third-party documents to DroneCommand represent that they have the lawful right to upload and store those materials for operational reference purposes;
• Labels and SDS sheets for operational reference: Pesticide labels and SDS sheets are generally published by manufacturers for distribution — uploading them to your account for personal operational reference is generally consistent with their intended use for materials you have lawfully acquired;
• DroneCommand claims no ownership: DroneCommand does not claim ownership of any documents uploaded by operators — uploaded materials remain the property of the uploading operator or their rightful owner and are not used by DroneCommand for any purpose beyond providing the Service to your account;
• Confidential materials must not be uploaded: Operators must not upload materials subject to confidentiality agreements, non-disclosure obligations, trade secrets, or materials they are not authorized to reproduce or store digitally — DroneCommand does not verify the rights status or confidentiality obligations associated with uploaded materials;
• DMCA removal without prior notice: If a third party asserts that uploaded material infringes their intellectual property rights, DroneCommand may remove the material upon receiving a proper DMCA takedown notice without prior notice to the operator — operators are solely responsible for maintaining copies of materials they upload;
• We are not liable for any intellectual property infringement claim, confidentiality breach, or other legal consequence arising from an operator's decision to upload third-party materials to the platform.

99. Platform Use During Active Government Investigation or Legal Hold

When spray operations documented in DroneCommand become the subject of legal proceedings or government investigation, the operator bears sole responsibility for record preservation. DroneCommand does not function as a legal hold system and does not automatically restrict account activity in response to legal proceedings.

• Operator solely responsible for legal holds: If an operator, their customer, or any third party initiates legal proceedings, a regulatory investigation, or a formal records demand (including subpoenas, FOIA requests, or administrative holds) relating to spray operations documented in DroneCommand, the operator is solely responsible for preserving all relevant records in their original form;
• DroneCommand does not auto-preserve records: DroneCommand is not a party to legal holds and does not automatically preserve, freeze, or restrict records in response to legal proceedings involving operators — operators must export and independently secure records subject to any legal hold obligation using their own document management systems;
• Account functionality continues during proceedings: Continuing to use DroneCommand — including editing, completing, deleting, or adding records — during an active legal hold or investigation is the operator's responsibility; DroneCommand does not restrict account functionality in response to legal proceedings unless required to do so by a valid court order directed specifically at DroneCommand;
• Spoliation risk is the operator's responsibility: We are not liable for spoliation claims, adverse inference instructions, evidentiary sanctions, or other litigation consequences arising from an operator's failure to properly preserve DroneCommand records during legal proceedings or in response to a legal hold obligation;
• We will notify you of legal process directed at us: If DroneCommand receives a valid subpoena, court order, or other compulsory legal process requiring production of operator records, we will use commercially reasonable efforts to notify the affected operator to the extent permitted by applicable law before complying, so the operator may seek appropriate legal relief.

49. Contact Information

For questions, concerns, legal notices, or support regarding these Terms or the Service:

• Company: Country Road Drone Services, LLC
• Address: 3308 330th St, Smithland, IA 51056
• Email: [email protected]
• Phone: (712) 420-0871
• Business Hours: Monday–Friday, 8:00 AM – 5:00 PM Central Time

For billing and payment inquiries, access the Stripe Customer Portal via Account Settings → Manage Billing.

For refund requests, see Section 11 and contact [email protected].

For tax exemption requests, see Section 6.4.

For arbitration opt-out notices, see Section 31.5 — must be submitted within 30 days of account creation.

For data deletion requests, contact [email protected] with subject line "Data Deletion Request."

For conflict of interest complaints, contact [email protected] with subject line "Conflict of Interest Concern."

For account access requests by estate representatives or legal guardians, see Section 42 and contact [email protected] with subject line "Estate Access Request."

For subprocessor security incident inquiries, see Section 50 and contact [email protected] with subject line "Security Incident Inquiry."

For incapacity or cognitive decline account management inquiries, see Section 51 and contact [email protected] with subject line "Incapacity Account Inquiry."

For Third-Party Data Subject privacy requests (landowners, farmers, or customers seeking access or deletion of their data), see Section 52 and contact [email protected] with subject line "Third-Party Data Request."

For account transfer requests (business sale), see Section 47 and contact [email protected] with subject line "Account Transfer Request."

For service discontinuation questions, see Section 46.

---

These Terms of Service were last updated on March 2, 2026 (Round 25 Hardening), and are effective as of that date. By using DroneCommand, you acknowledge that you have read, understood, and agree to be bound by these Terms.

← Back to DroneCommand