Terms of Service

1.1 Who is entering into these Terms

If you use DroneJob solely in your individual capacity, "you" means you personally.

If you access or use DroneJob on behalf of a company, organization, agency or other legal entity, "you" includes that entity, and you represent and warrant that:

• you are authorized to act on its behalf;
• you have authority to bind it to these Terms; and
• you agree to these Terms on its behalf.

If you do not have that authority, you may not accept these Terms or use the Services on the organization's behalf.

1.2 How you accept these Terms

You may accept these Terms by:

• creating a DroneJob account;
• affirmatively accepting the Terms through a registration, purchase, onboarding or account flow;
• signing an order form or other agreement incorporating these Terms;
• accessing or using Services that expressly state that use constitutes acceptance of these Terms; or
• otherwise manifesting acceptance in a legally valid manner.

Where applicable law requires a more specific form of consent or agreement, DroneJob will use the legally required method.

1.3 Additional agreements and product-specific terms

Certain DroneJob Services may be governed by additional terms.

These may include, as applicable:

• subscription or order forms;
• enterprise agreements;
• master services agreements;
• statements of work;
• service-level agreements;
• Data Processing Addenda;
• API or developer terms;
• the Acceptable Use Policy at https://www.dronejob.ai/acceptable-use;
• the Cookie Policy at https://www.dronejob.ai/cookie-policy;
• marketplace policies;
• messaging or communications terms;
• payment terms;
• partner agreements;
• supplemental product terms;
• beta or early-access terms;
• security or data-residency exhibits.

We refer to these collectively as "Additional Terms."

Additional Terms become part of the agreement between you and DroneJob when they apply to the Services you use and are accepted or incorporated in accordance with their terms.

1.4 Order of precedence

Unless another written agreement expressly states otherwise, if there is a conflict between these Terms and Additional Terms applicable to a particular Service, the more specific Additional Terms will control for that Service.

For example:

• an enterprise Order Form may control pricing and subscription commitments;
• a DPA may control DroneJob's processing of Customer Data on behalf of an enterprise customer;
• API Terms may control use of DroneJob developer interfaces;
• the Acceptable Use Policy controls prohibited conduct;
• an SLA may control expressly agreed service-level commitments.

These Terms continue to apply to matters not addressed by the applicable Additional Terms.

1.5 Enterprise agreements

An Enterprise Customer may enter into a separately negotiated written agreement with DroneJob.

Where a signed enterprise agreement expressly supersedes these Terms, the signed enterprise agreement will control to the extent stated in that agreement.

Individual Authorized Users of an Enterprise Customer may remain subject to appropriate user-level provisions, acceptable-use obligations and platform policies.

1.6 Third-party terms

Some Services use or connect to third-party services.

Your use of those third-party services may also be subject to agreements between you and the applicable provider.

Acceptance of these Terms does not automatically replace or modify your agreement with a third party.

1.7 Privacy

DroneJob's collection and use of personal information is described in the DroneJob Privacy Policy available at: https://www.dronejob.ai/privacy

Where DroneJob processes personal information on behalf of a business or Enterprise Customer, additional processing terms may apply under a DPA.

1.8 Changes to the agreement framework

DroneJob may add new products or capabilities as the platform evolves.

If a new product requires materially different contractual treatment, DroneJob may require acceptance of Additional Terms before that product is used.

2.1 Account

"Account" means an account or account context through which a person or organization accesses DroneJob.

An individual may have access to more than one permitted account context, role or organization.

2.2 API

"API" means an application programming interface, webhook interface, event interface, developer endpoint, software-development interface or similar technical interface made available by DroneJob.

2.3 Authorized User

"Authorized User" means an individual whom an Organization or Enterprise Customer has authorized to use the Services on its behalf.

Authorized Users may include employees, contractors, administrators, pilots, project managers or other approved personnel.

2.4 Client

"Client" means an individual or organization that seeks, requests, procures or manages drone-related services through or in connection with DroneJob.

A Client may be a consumer, small business, enterprise organization, government-related entity or other permitted customer.

2.5 Customer

"Customer" means a person or entity that purchases, subscribes to, receives or is otherwise contractually entitled to use DroneJob Services.

Depending on context, a Customer may be a Pilot, DSP, Client, Organization or Enterprise Customer.

2.6 Customer Data

"Customer Data" means information, files, records or other content submitted, connected, transmitted, created or maintained in the Services by or for a Customer or its Authorized Users for the Customer's business purposes.

Customer Data may include information originating from connected Third-Party Services.

Customer Data does not include DroneJob's underlying software, platform technology or properly de-identified or aggregated information that no longer identifies the Customer or an individual as described in the Privacy Policy.

2.7 Drone Service Provider or DSP

"Drone Service Provider" or "DSP" means a business, team or organization that provides or coordinates drone-related services.

A DSP may employ, engage, manage or subcontract Pilots, subject to applicable law and these Terms.

2.8 DroneJob Content

"DroneJob Content" means content, interfaces, designs, documentation, templates, software, workflows, taxonomies, educational materials and other materials made available by DroneJob, excluding Customer Data and User Content owned by users.

2.9 Enterprise Customer

"Enterprise Customer" means an organization using DroneJob for enterprise-level operations such as:

• vendor-network management;
• multi-user or multi-site drone programs;
• bulk mission or order workflows;
• compliance or procurement;
• organizational governance;
• API or system integration;
• advanced reporting;
• enterprise security or identity features.

An Enterprise Customer may include a private company, public utility, public institution or governmental/public-sector organization where the applicable DroneJob Services are authorized for that Customer's use.

2.10 Integration

"Integration" means a connection between DroneJob and a Third-Party Service or external system through which information or actions may be exchanged.

Integrations may use APIs, webhooks, files, event streams, authentication protocols or other supported mechanisms.

2.11 Marketplace

"Marketplace" means DroneJob functionality that enables permitted Clients, Pilots, DSPs, partners or other users to discover, contact, evaluate, engage or transact with one another.

2.12 Mission

"Mission" means a DroneJob record representing a drone-related service request, job, project, operational activity or workflow.

A Mission may contain:

• scope;
• location;
• schedule;
• assigned participants;
• requirements;
• approvals;
• status;
• deliverables;
• communications;
• related workflow information.

The creation of a Mission record does not by itself guarantee that a Pilot or DSP has legally or contractually accepted responsibility for performing the underlying service.

2.13 Order or Work Request

"Order" or "Work Request" means an instruction, request or data record submitted to DroneJob requesting or initiating a workflow, Mission, service request or other action.

Orders may originate from:

• a user interface;
• bulk upload;
• API;
• webhook;
• Integration;
• authorized automated workflow.

Specific provisions governing when an Order becomes binding will appear later in these Terms and any applicable Additional Terms.

2.14 Organization

"Organization" means a business, DSP, enterprise, agency, team, institution or other entity represented within DroneJob as an organizational account or governed tenant.

2.15 Pilot

"Pilot" means an individual who uses DroneJob in connection with flying, operating, supporting or offering drone-related services.

Use of the term "Pilot" within DroneJob does not itself represent or guarantee that the individual holds any particular certification, license or regulatory authorization.

Where DroneJob displays a verification status, the meaning and limitations of that status will be governed by these Terms and applicable feature documentation.

2.16 Services

"Services" means the DroneJob websites, software, applications, marketplace, productivity tools, communications functionality, APIs, enterprise tools, AI features, integrations, content and other products or services made available by DroneJob and governed by these Terms.

2.17 Third-Party Service

"Third-Party Service" means a product, platform, website, application, API, communications network, payment provider, mapping system, cloud provider or other service operated by an entity other than DroneJob.

2.18 User

"User" means any permitted person accessing or using the Services.

A User may be acting individually or as an Authorized User of an Organization.

2.19 User Content

"User Content" means information, text, photographs, video, files, portfolio materials, communications, reviews or other content submitted to the Services by a User.

User Content may form part of Customer Data when submitted on behalf of a Customer.

2.20 Verification or Verified

"Verification" means a process by which DroneJob or an approved provider evaluates specified information against defined criteria.

"Verified" means only that the particular information identified by the applicable verification feature satisfied DroneJob's stated verification process at the relevant time.

Verification does not constitute a general guarantee regarding a person's competence, suitability, safety, financial condition, future conduct or legal ability to perform every possible service.

2.21 AI Feature

"AI Feature" means a feature of the Services that uses artificial intelligence, machine learning or similar computational methods to produce, recommend, summarize, classify, analyze, draft or potentially initiate an action.

Additional rules for AI Features will appear later in these Terms.

3.1 General eligibility

You may use the Services only if:

• you are legally capable of entering into a binding agreement;
• you satisfy any age requirements applicable to the relevant Service;
• your use of DroneJob is permitted by applicable law;
• you provide accurate information when required; and
• you comply with these Terms and applicable Additional Terms.

Unless DroneJob expressly offers a separate experience for younger users, individuals using commercial marketplace, contracting, payment or professional-service functionality must be at least 18 years old or the age of legal majority in their jurisdiction, whichever is higher.

3.2 Authority to act for an organization

If you create, administer or use an Account for an Organization, you represent that you are authorized to do so.

You must not:

• create an Organization account without authorization;
• represent that you act for a company or organization when you do not;
• grant permissions on behalf of an Organization without authority;
• connect an Organization's systems or data without authorization.

DroneJob may request evidence of authority where reasonably necessary for security, enterprise onboarding, payment, compliance or other legitimate purposes.

3.3 Accuracy of information

You must provide information that is accurate, current and not misleading when required by DroneJob.

You are responsible for keeping material account and professional information reasonably current.

This obligation is especially important for information such as:

• contact information;
• organization affiliation;
• professional credentials;
• insurance status;
• equipment information;
• service areas;
• payment information;
• integration ownership;
• authorization contacts.

3.4 Commercial pilot eligibility

DroneJob may permit individuals who are not yet commercially qualified pilots to use educational, community, career-development or profile-preparation functionality.

However, a user must not falsely represent that the user:

• is legally qualified for commercial operations;
• holds a certification or authorization the user does not hold;
• is insured when the user is not;
• has experience or qualifications the user does not possess.

Where applicable law requires a remote-pilot certificate, license, operational authorization, insurance or other credential for a particular Mission, the Pilot or DSP remains responsible for satisfying those requirements before performing that Mission.

DroneJob may restrict access to marketplace or mission-execution functionality until specified information has been provided or verified.

3.5 Clients and enterprise users

Clients and Enterprise Customers must have lawful authority to request the services, access the sites or properties, provide project data and authorize the workflows they initiate.

Enterprise Users must comply with their organization's internal authorization policies as well as these Terms.

3.6 Geographic and product availability

Not all Services are available in all countries or regions.

DroneJob may restrict Services based on:

• legal requirements;
• regulatory requirements;
• communications-provider coverage;
• payment-provider availability;
• security requirements;
• product readiness;
• contractual limitations.

The availability of a feature within the interface does not necessarily mean the feature is legally appropriate for every location or use case.

4.1 Marketplace and Professional Network

DroneJob may provide marketplace and professional-network functionality that helps participants discover, evaluate, contact and work with one another.

Marketplace functionality may include:

• public professional profiles;
• service listings;
• pilot and DSP directories;
• geographic search;
• portfolio presentation;
• credential and verification indicators;
• client inquiries;
• lead capture;
• mission or job opportunities;
• matching and qualification tools;
• reviews and reputation;
• referrals;
• training and partner offerings;
• communications;
• future transaction or payment functionality.

Marketplace functionality is intended to help participants identify and coordinate potential business relationships.

Unless DroneJob expressly agrees otherwise in Additional Terms, DroneJob does not guarantee that:

• a Client will hire a Pilot;
• a Pilot will accept a Mission;
• a user will receive leads;
• a Mission will be completed;
• a particular transaction will occur.

4.2 Business Productivity and Operations Suite

DroneJob may provide software tools that Pilots, DSPs, teams and other businesses use to organize and operate their business.

Depending on subscription, product stage and availability, productivity functionality may include:

• CRM and client records;
• lead and opportunity management;
• communications;
• email and SMS tools;
• service packages;
• quoting and proposals;
• contracts or template documents;
• calendars;
• availability and booking;
• mission planning;
• checklists;
• workflow management;
• assignment and scheduling;
• file and deliverable management;
• portfolio and proof-pack management;
• reviews and customer feedback;
• invoices and payment-status tracking;
• expense or profitability information;
• fleet and asset records;
• credential and compliance tracking;
• reminders and notifications;
• reporting and analytics;
• marketing and referral tools;
• AI-assisted productivity features.

DroneJob's productivity tools may be used for business obtained through DroneJob or, where the applicable feature permits, for a user's existing or independently acquired clients.

The availability of a productivity feature does not mean DroneJob becomes a party to the user's underlying business relationship with that client's customer.

4.3 Enterprise Workflow and Integration Platform

DroneJob may provide enterprise capabilities for organizations that manage drone programs, external vendors or recurring drone operations.

Where appropriate for the applicable Customer and service environment, these capabilities may support public infrastructure programs, municipal programs, public utilities, governmental asset inspection and public construction/infrastructure workflows.

Depending on applicable plans and agreements, enterprise functionality may include:

• organizational accounts;
• multi-user access;
• role-based permissions;
• vendor and pilot management;
• vendor readiness;
• credential and insurance tracking;
• preferred or SLA-backed vendor pools;
• bulk Orders and Mission creation;
• assignment and routing workflows;
• standardized Mission templates;
• workflow approvals;
• audit histories;
• compliance reporting;
• secure file and deliverable exchange;
• buyer dashboards;
• multi-site or multi-region operations;
• SSO or federated identity;
• SCIM or automated user provisioning;
• APIs;
• webhooks;
• event-based integrations;
• CSV/PDF exports;
• ERP integrations;
• CRM integrations;
• GIS integrations;
• project-management integrations;
• accounting integrations;
• other approved enterprise connections.

Enterprise Customers may use DroneJob to transmit Orders, create Missions, update workflows or exchange data programmatically.

Specific enterprise capabilities may be governed by separate Order Forms, Enterprise Agreements, SLAs, DPAs, API Terms or Supplemental Terms.

4.4 Communications infrastructure

DroneJob may provide communication capabilities that connect participants through:

• in-app messaging;
• SMS;
• email;
• notifications;
• future supported voice or messaging channels.

DroneJob may use communications providers to transmit these messages.

Where a user sends a message through DroneJob to another participant, DroneJob is providing communications infrastructure and record-keeping functionality; this does not necessarily make DroneJob the author of the user's message.

Additional communications rules appear later in these Terms.

4.5 AI-assisted features

DroneJob may provide AI-enabled capabilities supporting areas such as:

• sales;
• project management;
• mission planning;
• fleet management;
• compliance and risk;
• customer communication;
• marketing;
• professional development;
• data-quality review.

AI Features are intended primarily to assist Users. AI may generate recommendations, summaries, drafts, classifications or proposed actions and, where specifically enabled, may perform bounded actions within authorized permissions. Users remain responsible for reviewing AI Output and for material professional, operational, commercial and regulatory decisions. Additional provisions governing AI Features appear in Section 21.

4.6 Integrations and third-party products

DroneJob is designed to work with third-party technologies rather than replace every specialized drone, aviation or enterprise system.

Users may therefore connect DroneJob to approved third-party tools.

Third-party integrations may be modified, unavailable or discontinued independently of DroneJob.

4.7 Service evolution

DroneJob is an evolving platform.

Features may be:

• added;
• modified;
• removed;
• renamed;
• combined;
• placed behind a different subscription tier;
• limited by usage;
• released in beta or early access.

Specific contractual commitments made in an Order Form or Enterprise Agreement remain subject to the terms of that agreement.

5.1 DroneJob as technology provider

DroneJob provides technology that may help users:

• identify business opportunities;
• evaluate other users;
• communicate;
• prepare projects;
• organize work;
• manage business information;
• create Missions;
• coordinate workflows;
• store files;
• process data;
• connect external systems;
• monitor activity.

Providing these tools does not mean DroneJob assumes responsibility for every decision, statement, instruction or action taken through those tools.

5.2 DroneJob as marketplace facilitator

When DroneJob enables a Client to discover or contact a Pilot or DSP, DroneJob generally acts as the marketplace or technology facilitator.

Unless DroneJob expressly enters into the applicable service agreement as a contracting party:

• the Client selects the Pilot or DSP;
• the Pilot or DSP decides whether to accept the work;
• the Client and Pilot/DSP are responsible for agreeing on the scope, price, schedule, deliverables and other commercial terms;
• the Pilot/DSP is responsible for performing the service;
• the Client is responsible for its obligations under the agreed project.

DroneJob may provide tools, templates or records to help form or document the relationship, but the existence of those tools does not by itself make DroneJob a party to the underlying drone-service contract.

5.3 Managed or enterprise services may differ

DroneJob may in the future offer managed services, enterprise programs or other arrangements under which DroneJob assumes additional contractual obligations.

If DroneJob will act as:

• principal contractor;
• managed-service provider;
• program operator;
• payment intermediary;
• other direct provider,

those responsibilities must be expressly stated in the applicable Order Form, Statement of Work, Enterprise Agreement or Supplemental Terms.

Users should not assume that such responsibilities apply unless DroneJob has expressly agreed to them.

5.4 DroneJob is not an employer or staffing agency by default

Unless expressly stated otherwise in a separate written agreement:

• Pilots and DSPs are not employees of DroneJob;
• DroneJob does not establish an employment relationship between Clients and Pilots;
• DroneJob does not create a partnership or joint venture between users;
• DroneJob does not make a Pilot an agent of DroneJob;
• DroneJob does not make a Client an agent of DroneJob.

Specific independent-contractor provisions will appear later in these Terms.

5.5 DroneJob is not an aviation regulator

DroneJob is not:

• the Federal Aviation Administration;
• an air-navigation authority;
• a civil aviation regulator;
• an airspace-authorization authority;
• a substitute for applicable aviation authorities.

DroneJob may display, integrate or assist with aviation-related information and workflows, but the responsible Pilot, DSP and/or organization must determine whether a specific operation may lawfully proceed.

5.6 DroneJob is not the user's professional advisor

Unless DroneJob expressly agrees otherwise through a separately licensed professional service, DroneJob is not acting as a user's:

• lawyer;
• accountant;
• tax advisor;
• insurance broker;
• engineer;
• licensed surveyor;
• safety officer;
• aviation counsel;
• financial advisor.

Templates, AI outputs, recommendations, checklists, pricing suggestions and other platform assistance are tools for user review and do not replace qualified professional advice where such advice is required.

5.7 Verification is a trust signal, not a guarantee

DroneJob may verify certain information or display verification indicators.

A verification indicator means only that the specified information satisfied the applicable DroneJob verification process at the relevant time.

Verification does not guarantee:

• competence;
• workmanship;
• honesty;
• financial condition;
• legal compliance;
• safety;
• future behavior;
• fitness for every Mission.

Clients must still evaluate providers based on the requirements of their particular project.

Pilots and DSPs remain responsible for maintaining current qualifications and notifying DroneJob where required information changes.

5.8 User-generated information

DroneJob may rely on information supplied by users, organizations and third-party providers.

Although DroneJob may conduct checks or apply verification processes, DroneJob cannot independently guarantee the accuracy of every:

• profile;
• service description;
• credential;
• portfolio item;
• review;
• project requirement;
• site condition;
• client statement;
• integration-originated record.

Users are responsible for information they submit and decisions they make based on information available through the Services.

5.9 Enterprise workflows and integrations

DroneJob may execute actions based on instructions received through authorized:

• user accounts;
• API credentials;
• integrations;
• webhook events;
• automated workflows;
• enterprise systems.

An action processed through an authorized integration does not mean DroneJob independently originated the underlying business instruction.

Later sections of these Terms will define responsibility for API credentials, automated actions, Orders and machine-to-machine workflows.

5.10 Communications intermediary

When users communicate through DroneJob, DroneJob may:

• transmit messages;
• route messages;
• retain conversation records;
• send notifications;
• provide secure links;
• associate communications with a Client, Mission or workflow.

A message written by a Client, Pilot, DSP or enterprise user remains that participant's communication merely because DroneJob transmitted it.

DroneJob may apply automated security, anti-abuse, delivery, routing and platform controls to communications.

Additional provisions governing communications, messaging channels and DroneJob-provided communication addresses appear in Sections 23–25.

5.11 User judgment remains necessary

DroneJob is designed to reduce operational friction and improve information quality, but no software platform can eliminate the need for professional judgment.

Users remain responsible for making decisions appropriate to their role, including decisions concerning:

• whether to accept work;
• price;
• contractual commitments;
• operational safety;
• legal compliance;
• regulatory compliance;
• site conditions;
• data quality;
• mission execution;
• technical conclusions;
• deliverable acceptance.

Where DroneJob requires human approval, where applicable law or professional standards require human judgment, or where an action constitutes a material safety, compliance, financial or contractual decision, Users must not attempt to use AI, automation or another mechanism to bypass the applicable control.

5.12 Public Sector and Government Use

DroneJob may make Services available to governmental, public-sector or government-contractor Customers where the applicable Services are appropriate for that Customer's requirements.

Public-sector Customers may be subject to additional requirements relating to matters such as:

• procurement;
• data residency;
• records retention;
• security;
• accessibility;
• audit;
• confidentiality;
• data processing;
• authorized contracting authority.

Such requirements apply to DroneJob only where required by applicable law or expressly accepted by DroneJob in an applicable:

• Order Form;
• Enterprise Agreement;
• Public Sector Addendum;
• security exhibit;
• Data Processing Addendum;
• other written agreement.

Unless DroneJob expressly states otherwise for a specifically identified service environment, DroneJob does not represent that the general commercial Services hold a particular governmental security authorization such as FedRAMP.

Customers must not use the Services for classified information, CUI requiring an authorization that the contracted environment does not possess, or other information requiring unsupported controls.

6.1 Account registration

When creating an Account, you agree to provide information that is:

• accurate;
• current;
• complete where required;
• not misleading.

You must maintain materially relevant Account information so that it remains reasonably current.

DroneJob may request additional information where reasonably necessary to:

• provide a Service;
• verify eligibility;
• protect Account security;
• administer payments;
• verify credentials;
• satisfy enterprise requirements;
• comply with law.

6.2 Personal use of account credentials

Authentication credentials assigned to an individual are intended for that individual.

You must not:

• share passwords;
• share authentication tokens;
• allow another person to impersonate you;
• use another person's Account credentials;
• circumvent multi-factor authentication;
• knowingly allow an unauthorized person to access your Account.

Organizations that need multiple users should use authorized team or Organization functionality rather than sharing credentials.

6.3 Account responsibility

You are responsible for activities performed through your Account to the extent those activities result from:

• your actions;
• your authorized use;
• credentials you control;
• your failure to use reasonable security measures.

Nothing in this section makes you responsible for activity caused solely by a security failure attributable to DroneJob or another party where applicable law provides otherwise.

6.4 Authentication and security controls

DroneJob may require or support security measures including:

• password requirements;
• passwordless authentication;
• multi-factor authentication;
• email verification;
• mobile verification;
• session controls;
• enterprise SSO;
• device or risk checks;
• reauthentication for sensitive actions.

DroneJob may change or strengthen authentication requirements where reasonably necessary to protect users or the Services.

6.5 Unauthorized access

You must promptly notify DroneJob if you reasonably believe:

• your Account has been compromised;
• credentials have been disclosed;
• an unauthorized person has accessed your Account;
• Organization permissions have been improperly changed;
• an API or integration credential associated with your Account has been compromised.

DroneJob may temporarily:

• restrict access;
• invalidate sessions;
• require credential reset;
• require additional verification;
• suspend affected integrations;
• take other reasonable security measures.

6.6 Account recovery

DroneJob may require reasonable evidence before restoring access to an Account.

Recovery may depend on factors such as:

• verified email;
• verified telephone number;
• Organization affiliation;
• identity verification;
• prior Account information;
• administrator confirmation;
• other security evidence.

DroneJob is not required to transfer an Account to a person who cannot reasonably demonstrate authorization.

6.7 Multiple roles and Organizations

A User may be permitted to participate in more than one role or Organization.

For example, a person may be:

• an independent Pilot;
• a member of a DSP;
• an Enterprise Customer's Authorized User;
• a Client.

DroneJob may maintain separate data scopes, permissions, entitlements and contexts for these roles.

Access to information in one context does not automatically create a right to access information in another context.

6.8 Automated and machine access

Interactive user credentials must not be used to bypass approved API, Integration or machine-to-machine authentication mechanisms.

Where DroneJob provides APIs or automation credentials, machine access must use the authorized mechanism provided for that purpose.

Detailed API and Integration requirements appear later in these Terms.

6.9 Account names and impersonation

You may not create or use an Account that:

• impersonates another person or Organization;
• falsely implies affiliation;
• fraudulently represents credentials;
• deliberately misleads users regarding identity.

DroneJob may require correction, verification or removal of misleading identity information.

6.10 Account suspension or restriction

DroneJob may restrict or suspend an Account when reasonably necessary because of:

• suspected compromise;
• fraud;
• unauthorized use;
• serious Terms violations;
• legal requirements;
• risk to users;
• unpaid amounts where applicable;
• abuse of platform resources.

The broader suspension and termination framework appears in Section 39.

7.1 Organization Accounts

An Organization may use DroneJob to manage information and workflows such as:

• users;
• Pilots;
• Clients;
• vendors;
• Missions;
• projects;
• assets;
• communications;
• files;
• workflows;
• integrations;
• business records.

The individual or entity that establishes or purchases an Organization Account must have authority to do so.

7.2 Authorized Users

An Organization may authorize individuals to access its DroneJob environment.

Authorized Users may include:

• owners;
• employees;
• contractors;
• Pilots;
• dispatchers;
• project managers;
• operations personnel;
• compliance personnel;
• sales users;
• finance users;
• administrators;
• executives;
• other permitted personnel.

Each Authorized User should have their own Account identity.

Organizations must not use shared credentials as a substitute for proper Authorized User Accounts.

7.3 Organization responsibility for Authorized Users

The Organization is responsible for:

• determining who should be an Authorized User;
• assigning appropriate access;
• removing access when no longer appropriate;
• ensuring Authorized Users understand applicable Organization policies;
• ensuring Authorized Users use the Services consistently with the Organization's authority and these Terms.

Subject to applicable law and any separate agreement, an Organization is responsible for actions its Authorized Users take within the Organization's DroneJob environment when acting within their actual or apparent authorization.

7.4 User responsibility

Authorized Users also remain individually responsible for:

• protecting credentials;
• complying with these Terms;
• using access only for authorized purposes;
• avoiding misuse of information;
• not attempting to exceed assigned permissions.

Organization responsibility does not eliminate an Authorized User's individual obligations.

7.5 Membership and access changes

An Organization may:

• invite Users;
• approve membership;
• assign roles;
• modify access;
• remove Users;
• disable access.

Removal from an Organization may affect access to:

• Organization Missions;
• Organization Clients;
• internal communications;
• files;
• reports;
• integrations;
• other Organization-scoped information.

Removal from an Organization does not necessarily delete the individual's separate personal DroneJob Account where the product permits separate individual use.

7.6 Multiple Organizations

Where permitted by the Services, an individual may belong to multiple Organizations.

DroneJob may separate information and permissions by Organization or tenant.

Users must not:

• copy confidential data from one Organization to another without authorization;
• use one Organization's credentials to access another;
• intentionally defeat tenant boundaries.

7.7 Contractors and external users

An Organization may be permitted to add external users such as:

• subcontractors;
• outside Pilots;
• vendors;
• consultants.

The Organization is responsible for assigning an appropriate role and limiting access consistent with the external user's business need.

Being added as an Authorized User does not by itself create:

• employment;
• partnership;
• agency;
• contractor status with DroneJob.

7.8 Affiliates and related organizations

Where an Enterprise Agreement or plan allows affiliated entities to participate, access may be extended to Affiliates subject to:

• applicable entitlements;
• tenant configuration;
• applicable Order Forms;
• contractual terms.

Affiliates do not automatically receive access merely because they are legally related to the Customer.

7.9 Organization data boundaries

Organization records may include information that is not available through an individual's personal DroneJob context.

DroneJob may enforce Organization-level authorization to help ensure that Organization-scoped information is accessible only to permitted users.

Users remain responsible for using information they access within the scope of their authorization.

8.1 Administrator capabilities

Depending on the applicable Service and permissions, administrators may be able to:

• invite Users;
• remove Users;
• assign roles;
• modify permissions;
• configure teams;
• manage Pilots or vendors;
• configure Organization settings;
• manage subscription entitlements;
• configure communications;
• connect Integrations;
• manage API access;
• configure SSO or provisioning;
• access Organization reports;
• access Organization activity or audit information;
• manage files, Missions or workflows;
• export Organization Data.

Available administrator capabilities depend on the product, plan, role and Organization configuration.

8.2 Organization authorization

The Organization is responsible for deciding:

• who receives administrator rights;
• the scope of those rights;
• when those rights should be changed or revoked.

DroneJob may rely on instructions issued by a properly authenticated administrator within the apparent scope of that administrator's permissions.

8.3 Administrator access to User activity and Organization Data

Authorized administrators may have access to information relating to activity performed within the Organization environment.

Depending on the Services and permissions, this may include:

• Account information;
• Organization profile information;
• Missions;
• workflows;
• customer records;
• communications;
• files;
• deliverables;
• activity records;
• audit information;
• Integration data.

Authorized Users should understand that activity conducted within an Organization's DroneJob environment may be accessible to the Organization and its authorized administrators.

The Privacy Policy provides additional information regarding Organization access.

8.4 Administrator responsibility

Administrators must use their privileges only for legitimate Organization purposes.

Administrators must not:

• access information without legitimate authorization;
• use Organization Data for unrelated personal purposes;
• grant access to unauthorized persons;
• bypass security controls;
• improperly export confidential information.

8.5 Administrative changes

DroneJob may log or retain evidence of material administrative changes such as:

• role changes;
• permission changes;
• membership changes;
• Integration configuration;
• security settings;
• export actions where supported.

These records may support:

• security;
• auditing;
• compliance;
• dispute resolution;
• enterprise administration.

8.6 Loss of administrator access

If an administrator:

• leaves the Organization;
• changes roles;
• loses authority;
• has a compromised Account,

the Organization should promptly remove or modify the administrator's access.

DroneJob may assist with administrator recovery or reassignment where appropriate but may require reasonable evidence of authority.

8.7 Administrative disputes

If DroneJob receives conflicting instructions concerning:

• Organization ownership;
• administrator authority;
• control of an Account;
• access to Organization Data,

DroneJob may temporarily restrict sensitive administrative changes while it reasonably determines what documentation or authorization is needed.

DroneJob is not required to resolve internal corporate, employment, ownership or partnership disputes.

Parties remain responsible for resolving those disputes through their own governance and legal processes.

8.8 Enterprise identity management

Where available, Enterprise Customers may manage Users through systems such as:

• SSO;
• identity federation;
• SCIM;
• automated provisioning.

Actions performed by authorized enterprise identity systems may:

• create Accounts;
• grant access;
• update identity attributes;
• suspend access;
• remove access.

The Enterprise Customer is responsible for configuring its identity systems and authorization rules appropriately.

9.1 Plan features

Different plans may include different access to features such as:

• profile and portfolio capabilities;
• marketplace visibility;
• CRM;
• Missions;
• communications;
• storage;
• AI Features;
• automation;
• analytics;
• team members;
• fleet or asset tools;
• integrations;
• API access;
• enterprise controls;
• support.

The applicable pricing page, checkout flow, Order Form or other purchase documentation will describe material plan features at the time of purchase.

9.2 Usage limits

Some Services may be subject to usage limits.

Examples may include:

• number of Authorized Users;
• Organizations;
• Missions;
• leads;
• contacts;
• portfolio items;
• storage;
• file size;
• AI credits or usage;
• SMS or communication usage;
• email usage;
• API requests;
• webhook activity;
• automations;
• integrations;
• reports;
• exports;
• visibility boosts;
• verification services;
• other metered resources.

Limits may be measured:

• monthly;
• per billing cycle;
• per User;
• per Organization;
• per Mission;
• per transaction;
• by storage;
• by computational usage;
• using another stated metric.

9.3 Exceeding limits

If a Customer reaches a plan limit, DroneJob may, consistent with the applicable plan terms:

• prevent additional usage;
• temporarily restrict the feature;
• offer additional capacity;
• require upgrade;
• apply a disclosed overage charge;
• apply fair-use restrictions.

DroneJob will not intentionally impose undisclosed paid overage charges.

Where automatic paid overages are part of a plan, they should be disclosed and authorized through the applicable purchasing or contractual process.

9.4 Usage measurement

DroneJob's records will generally be used to measure usage of metered Services, subject to correction of demonstrable errors.

Usage systems may measure technical events such as:

• message sends;
• AI requests;
• storage consumed;
• API calls;
• completed workflows;
• Mission activity;
• other defined consumption units.

9.5 Authorized User entitlements

Plans may limit:

• number of Users;
• type of Users;
• roles;
• administrative seats;
• team seats;
• enterprise seats.

Users must not share Accounts to circumvent seat or User limits.

Where permitted, an Organization may reassign a seat or entitlement according to applicable plan rules.

9.6 Feature availability

Not every feature is available:

• in every plan;
• in every region;
• to every role;
• for every industry;
• in every application;
• at every stage of product development.

DroneJob may require additional:

• verification;
• configuration;
• legal terms;
• provider availability;
• enterprise onboarding;

before a feature becomes available.

9.7 Free and promotional entitlements

DroneJob may offer:

• trials;
• promotional credits;
• founder benefits;
• partner benefits;
• referral entitlements;
• temporary upgrades;
• beta access.

Unless expressly stated otherwise, such benefits:

• may expire;
• may be subject to limits;
• may not be transferable;
• do not guarantee permanent access to the feature.

9.8 Enterprise entitlements

Enterprise Customers may receive custom:

• usage limits;
• features;
• support;
• integrations;
• security controls;
• SLA commitments;
• pricing.

The applicable Enterprise Agreement or Order Form controls where it differs from standard plan terms.

9.9 Feature evolution

DroneJob may modify standard plan packaging as the product evolves.

Changes may include:

• adding features;
• removing features;
• changing limits;
• moving features between plans;
• introducing new add-ons.

Any modification remains subject to:

• applicable law;
• existing contractual commitments;
• any required notice;
• specific commitments in Order Forms or Enterprise Agreements.

9.10 Future functionality

A Customer's purchase is based on the Services and commitments actually included in the applicable plan or agreement at the time of purchase.

Unless expressly stated in a signed agreement, purchases are not contingent upon:

• an announced roadmap;
• anticipated functionality;
• future integrations;
• future AI capabilities;
• other features not yet generally available.

Preview, Beta or Early Access functionality is also subject to Section 38 and should not be treated as a commitment that the functionality will become generally available.

9.11 Billing and renewal

Detailed provisions regarding:

• pricing;
• renewal;
• payment methods;
• taxes;
• refunds;
• chargebacks;

will be addressed in Section 34 and applicable purchase documentation.

This Section 9 primarily defines access, limits and entitlements.

10.1 Marketplace participants

Marketplace participants may include:

• Clients;
• Pilots;
• DSPs;
• Enterprise Customers;
• vendors;
• other authorized service participants.

Access to particular marketplace functions may depend on:

• role;
• region;
• verification;
• plan;
• eligibility;
• Mission requirements;
• other platform criteria.

10.2 Client inquiries

A Client may contact a Pilot or DSP through DroneJob.

An inquiry may contain information such as:

• requested service;
• location;
• timing;
• project description;
• deliverables;
• contact details;
• budget information;
• other relevant requirements.

An inquiry is generally a request for information or potential services.

Unless the applicable workflow expressly states otherwise, an inquiry alone does not create a binding service contract.

10.3 Responses and proposals

Pilots and DSPs may respond through:

• messages;
• questions;
• quotes;
• proposals;
• service packages;
• availability;
• other permitted workflows.

A response does not automatically create a binding service agreement unless the relevant parties complete the applicable acceptance process.

Later sections address Quotes, Proposals and Service Agreements.

10.4 Selection of providers

Clients remain responsible for selecting the Pilot or DSP they engage.

DroneJob may provide information to assist the decision, including:

• profiles;
• portfolio;
• credentials;
• verification indicators;
• ratings;
• reviews;
• availability;
• location;
• service capability;
• marketplace recommendations.

These features support decision-making but do not eliminate the Client's responsibility to evaluate suitability for the specific project.

10.5 Acceptance of work

Pilots and DSPs remain responsible for deciding whether to:

• respond to an inquiry;
• submit a proposal;
• accept a Mission;
• perform requested work.

DroneJob does not require an independent Pilot or DSP to accept a particular project merely because the opportunity appears on DroneJob, except where a separate contractual program expressly provides otherwise.

10.6 Service agreement between marketplace participants

Unless DroneJob expressly agrees to act as a contracting party in Additional Terms, the underlying drone-service relationship is between the applicable:

• Client; and
• Pilot or DSP.

Those participants are responsible for establishing applicable commercial terms such as:

• scope;
• price;
• schedule;
• cancellation;
• access;
• deliverables;
• payment;
• change orders;
• project-specific requirements.

DroneJob may provide tools to help document these terms.

10.7 Marketplace information and due diligence

Users should exercise reasonable judgment before entering into a business relationship.

Clients should evaluate relevant factors such as:

• credentials;
• insurance;
• capability;
• portfolio;
• project-specific requirements.

Pilots and DSPs should evaluate factors such as:

• project scope;
• location;
• legality;
• access;
• safety;
• payment terms;
• project feasibility.

DroneJob trust features supplement rather than replace appropriate due diligence.

10.8 Matching and recommendations

DroneJob may:

• rank;
• recommend;
• filter;
• match;
• organize;

marketplace participants or opportunities.

These results may consider factors such as:

• location;
• capability;
• credentials;
• verification;
• availability;
• reviews;
• marketplace activity;
• Client requirements;
• user preferences;
• plan features;
• other relevant factors.

A recommendation is not a guarantee that the recommended person or project is suitable.

10.9 Paid visibility and promoted placement

DroneJob may offer paid features that affect marketplace visibility, such as:

• boosts;
• promoted profiles;
• featured placement;
• sponsored placement.

Where appropriate, DroneJob should distinguish paid or sponsored placement so users are not materially misled about the nature of the result.

Paid visibility does not constitute:

• verification;
• endorsement;
• a guarantee of quality.

10.10 Marketplace communications

Participants may communicate through DroneJob-supported channels.

DroneJob may retain communications that pass through DroneJob-controlled channels as described in the Privacy Policy and Sections 23–25.

Communications may help establish:

• project scope;
• timing;
• price;
• requirements;
• approvals.

Users should communicate clearly and preserve important project commitments using appropriate DroneJob workflows where available.

10.11 No guarantee of opportunities or earnings

DroneJob does not guarantee:

• number of inquiries;
• number of leads;
• response rate;
• Mission availability;
• acceptance;
• bookings;
• revenue;
• earnings;
• business growth.

Marketplace supply and demand may vary based on:

• geography;
• industry;
• season;
• qualifications;
• competition;
• Client demand;
• economic conditions;
• other factors.

Professional profiles, visibility tools, marketing tools, AI assistance, Marketplace access and similar functionality are tools intended to help Users operate their businesses and pursue opportunities. Results vary.

10.12 Existing and independently acquired Clients

Where supported by the applicable productivity tools, a Pilot or DSP may use DroneJob to manage:

• Clients acquired through DroneJob;
• existing Clients;
• independently acquired Clients.

Using DroneJob productivity functionality for an independently acquired Client does not automatically convert that Client relationship into a DroneJob-originated marketplace relationship.

Different product terms or fees may apply depending on the feature used.

10.13 Circumvention and off-platform activity

The detailed policy regarding off-platform communication, contracting and payments will appear in Section 35.

At minimum, users should understand that when business activity moves outside DroneJob-controlled workflows, DroneJob may be unable to provide features such as:

• conversation history;
• payment protection;
• dispute support;
• platform audit trails;
• automated workflow history;
• verification evidence associated with the transaction.

10.14 Enterprise marketplace programs

Enterprise Customers may use marketplace/vendor-network functionality under separate program rules, Order Forms or agreements.

Enterprise programs may include:

• preferred vendor pools;
• SLA requirements;
• qualification thresholds;
• custom pricing;
• routing rules;
• program-specific obligations.

Where Enterprise Additional Terms conflict with general marketplace terms, the applicable Additional Terms control as provided in Section 1.

11.1 Relationship between DroneJob and Pilots or DSPs

Unless DroneJob expressly enters into a separate written agreement stating otherwise, a Pilot or DSP using DroneJob is not:

• an employee of DroneJob;
• an agent of DroneJob;
• a partner of DroneJob;
• a joint venturer with DroneJob.

DroneJob's provision of:

• marketplace access;
• software;
• profile tools;
• communications;
• workflow tools;
• payment functionality;
• AI assistance;
• verification indicators;
• Mission opportunities;

does not by itself create an employment relationship between DroneJob and the Pilot or DSP.

11.2 DroneJob does not determine employment classification between Users

DroneJob supports multiple legitimate business structures.

A Pilot may, for example, be:

• self-employed;
• an employee of a DSP;
• an employee of an Enterprise Customer;
• an independent contractor of a Client;
• a subcontractor;
• a member of an internal drone program.

DroneJob does not determine or guarantee the legal classification of a relationship merely because the participants use DroneJob.

The applicable parties are responsible for determining the correct relationship under:

• applicable employment law;
• tax law;
• contract;
• insurance requirements;
• other relevant law.

11.3 Client and provider relationships

Unless DroneJob expressly agrees otherwise through Additional Terms, a Client and the applicable Pilot or DSP establish their own underlying service relationship.

DroneJob does not become:

• employer;
• staffing agency;
• agent;
• joint employer;
• partner;

merely because DroneJob facilitates discovery, communication or project workflow.

11.4 Enterprise internal Pilots

An Enterprise Customer may use DroneJob to manage its own employees or internal drone program.

Nothing in these Terms changes the existing employment relationship between the Enterprise Customer and its employees.

DroneJob's software may assist the Enterprise Customer with:

• assignments;
• scheduling;
• credentials;
• Missions;
• workflows;
• operational records.

The Enterprise Customer remains responsible for its employment and workforce obligations.

11.5 DSP workers

A DSP may employ or engage Pilots.

The DSP—not DroneJob—is responsible for determining and administering its relationship with those individuals, including matters such as:

• compensation;
• payroll;
• taxes;
• benefits;
• worker classification;
• scheduling obligations;
• insurance;
• supervision;
• employment policies.

11.6 No authority to bind DroneJob

Unless expressly authorized by DroneJob in writing, no Pilot, DSP, Client, Organization or Enterprise Customer has authority to:

• enter contracts on DroneJob's behalf;
• make warranties on DroneJob's behalf;
• create obligations for DroneJob;
• represent that the person is DroneJob's employee or agent.

11.7 Tax and business obligations

Users remain responsible for their own applicable:

• taxes;
• registrations;
• licenses;
• payroll obligations;
• business filings;
• worker classification;
• accounting.

DroneJob may provide records or tools that assist users, but DroneJob does not assume responsibility for determining each User's tax or employment obligations.

12.1 Required aviation qualifications

Pilots and DSPs must comply with applicable aviation requirements.

In the United States, this may include requirements relating to:

• FAA Remote Pilot certification under Part 107;
• aircraft registration;
• Remote ID;
• operational limitations;
• airspace authorization;
• waivers or approvals;
• recurrent training;
• other applicable FAA requirements.

Outside the United States, Pilots and DSPs are responsible for applicable national, regional and local aviation requirements.

DroneJob's reference to Part 107 does not imply that Part 107 governs operations outside its jurisdiction.

12.2 Mission-specific authority

Holding a Pilot credential does not necessarily mean a Pilot is authorized to perform every Mission.

Before performing a Mission, the responsible Pilot/DSP must evaluate requirements including, as applicable:

• airspace;
• operating category;
• aircraft;
• payload;
• location;
• flight conditions;
• local restrictions;
• site permissions;
• required approvals;
• special operational requirements.

12.3 Insurance

Pilots and DSPs are responsible for determining whether:

• insurance is legally required;
• the Client requires insurance;
• an Enterprise program requires insurance;
• applicable coverage is sufficient for the Mission.

Where DroneJob displays insurance information or verification status, that does not constitute advice that the policy covers a particular Mission or claim.

12.4 Equipment and airworthiness

Pilots/DSPs are responsible for ensuring that equipment used for a Mission is:

• appropriate;
• maintained;
• operationally suitable;
• legally permitted;
• safe for the intended operation.

This responsibility may include:

• aircraft;
• batteries;
• payloads;
• sensors;
• controllers;
• accessories;
• support equipment.

DroneJob equipment records or alerts are productivity tools and are not a substitute for the responsible operator's inspection or judgment.

12.5 Safety

The responsible Pilot or Organization retains responsibility for operational safety.

DroneJob may provide:

• checklists;
• risk tools;
• alerts;
• weather information;
• planning aids;
• AI recommendations;
• compliance information.

These tools assist decision-making.

They do not replace:

• preflight evaluation;
• on-site judgment;
• regulatory requirements;
• the responsible operator's duty to stop or modify an unsafe operation.

12.6 Site and property requirements

Pilots/DSPs must determine whether they have appropriate:

• property access;
• landowner permission where required;
• site authorization;
• safety access;
• Client authorization;
• permissions relating to restricted facilities.

A Client's request to perform a Mission does not automatically establish that every legally necessary permission has been obtained.

12.7 Specialized services

Certain services may involve additional professional or industry obligations.

Examples may include:

• surveying;
• engineering;
• thermal inspection;
• utility inspection;
• insurance claims;
• mapping;
• public safety;
• agriculture;
• infrastructure.

Pilots/DSPs must not represent that a drone deliverable constitutes a regulated professional conclusion unless they are legally qualified to provide that conclusion.

For example, a drone-generated map should not be represented as a licensed land survey where applicable law requires a licensed surveyor unless the applicable professional requirements are satisfied.

12.8 Data and privacy obligations

Pilots and DSPs may have obligations concerning:

• privacy;
• property rights;
• confidentiality;
• data collection;
• image capture;
• sensitive sites;
• personally identifiable information.

Users are responsible for using DroneJob and performing Missions consistently with such obligations.

12.9 Enterprise and Client requirements

A Client or Enterprise Customer may impose requirements beyond legal minimums.

Examples:

• higher insurance limits;
• background checks;
• safety training;
• site orientation;
• equipment standards;
• data-security requirements;
• deliverable standards.

A Pilot/DSP should not accept a Mission unless it can satisfy the applicable agreed requirements.

12.10 Changes in qualification

Pilots/DSPs must keep material qualification information reasonably current.

If a material credential:

• expires;
• lapses;
• is suspended;
• is revoked;
• changes status,

the Pilot/DSP must not continue representing the credential as valid.

12.11 DroneJob tools do not grant operational authority

No DroneJob feature, including:

• AI agent;
• checklist;
• verification badge;
• Mission-ready indicator;
• weather view;
• airspace integration;
• risk score;

constitutes final legal authorization to fly.

The responsible Pilot, DSP or Organization remains responsible for the go/no-go decision.

13.1 Scope of verification

DroneJob may verify information such as:

• identity;
• Pilot certification;
• insurance;
• training;
• Organization affiliation;
• specialty credentials;
• other stated attributes.

Each verification applies only to the specific information and verification process identified.

13.2 Meaning of “Verified”

A label such as Verified means that DroneJob or an approved provider evaluated the specified information according to the applicable process and found it satisfied that process at the relevant time.

It does not mean that DroneJob:

• guarantees the User;
• endorses the User;
• guarantees workmanship;
• guarantees future behavior;
• guarantees safety;
• guarantees legal compliance;
• guarantees financial condition;
• guarantees fitness for every Mission.

13.3 Credential status

A displayed credential status may include:

• Verified;
• Unverified;
• Pending;
• Expired;
• Unable to Verify;
• other appropriate status.

DroneJob may change a displayed status where:

• underlying information changes;
• a credential expires;
• new information becomes available;
• re-verification is required.

13.4 User responsibility remains

Verification does not relieve a Pilot, DSP, Client or Enterprise Customer of responsibility to evaluate Mission-specific suitability.

For example, Part 107 Verified means the applicable credential passed DroneJob's defined verification process.

It does not mean: "This Pilot is legally authorized for every operation."

13.5 Enterprise-specific qualification

Enterprise Customers may establish program-specific qualification criteria.

For example:

DroneJob may use such requirements to determine whether a Pilot/vendor appears eligible for an enterprise pool or Mission.

Enterprise eligibility is distinct from general DroneJob verification.

13.6 Customer-supplied verification

Some qualification information may be confirmed by:

• DSPs;
• Enterprise Customers;
• credential providers;
• training partners;
• other approved sources.

DroneJob may identify the source or scope of verification where necessary to avoid misleading Users.

13.7 Changes and expiration

A verification result may become outdated.

Users must update DroneJob where required if verified information materially changes.

DroneJob may:

• notify Users;
• remove a badge;
• restrict eligibility;
• require re-verification.

13.8 Fraudulent credentials

Users may not:

• submit fraudulent documents;
• alter credentials;
• misrepresent certification;
• impersonate another credential holder;
• intentionally conceal expiration or revocation.

DroneJob may investigate suspected fraud and may suspend relevant functionality or Accounts.

13.9 Background checks

If DroneJob later offers background-check functionality, the scope, provider and meaning of the check must be clearly disclosed.

A generic "Verified" badge must not be interpreted as indicating that a background check occurred unless that check was actually included in the verification.

13.10 Verification is not a warranty

Verification information is intended as an informational trust signal.

To the extent permitted by applicable law, verification does not constitute a warranty by DroneJob concerning the verified person or Organization.

14.1 Accurate project information

Clients must provide information that is reasonably accurate and complete regarding the requested services.

Relevant information may include:

• location;
• requested service;
• deliverables;
• schedule;
• deadlines;
• access;
• site contact;
• known hazards;
• special requirements.

14.2 Scope

Clients should clearly communicate what they expect from a project.

A Client should not intentionally:

• conceal material requirements;
• materially expand scope without addressing the change;
• misrepresent the property/site;
• misstate deliverable expectations.

DroneJob may provide scoping tools, but the Client and provider remain responsible for agreeing on the project scope.

14.3 Site access

The Client is responsible for providing or arranging access that the Client has agreed to provide.

This may include:

• gates;
• keys;
• escorts;
• site contacts;
• access windows;
• security procedures;
• required on-site permissions.

If access is unavailable, a Mission may be delayed, rescheduled or subject to applicable cancellation/mobilization terms.

14.4 Property and project authority

A Client should request drone services only where the Client has appropriate authority to do so.

The Client must not knowingly request:

• unlawful surveillance;
• unauthorized access;
• prohibited capture;
• illegal operations.

14.5 Known hazards and restrictions

Clients should disclose known conditions that could materially affect:

• safety;
• site access;
• Mission planning;
• equipment;
• timing.

Examples may include:

• active construction;
• hazardous operations;
• restricted areas;
• high-voltage equipment;
• security requirements;
• unusual site restrictions.

This does not transfer the Pilot's independent safety responsibility to the Client.

14.6 Aviation information

Clients are not required to be aviation experts.

However, a Client must not intentionally pressure a Pilot/DSP to:

• violate aviation regulations;
• fly when unsafe;
• bypass required authorization;
• falsify compliance records.

A Pilot/DSP may refuse, delay or modify an operation based on legal or safety requirements.

14.7 Deliverable requirements

Clients should communicate:

• desired outputs;
• formats;
• resolution;
• timing;
• technical requirements;
• acceptance criteria;

where relevant.

Specialized technical deliverables may require additional information.

14.8 Confidential or sensitive information

Clients should identify information or sites requiring heightened confidentiality or security where reasonably necessary.

Enterprise Customers may establish additional security requirements through applicable agreements.

14.9 Approvals

Where DroneJob provides:

• quote approval;
• scope approval;
• schedule confirmation;
• change-order approval;
• deliverable acceptance;

Clients are responsible for reviewing information before approving it.

Clients should not approve information they know to be materially incorrect.

14.10 Changes

If requirements change, the Client should communicate the change promptly.

Material changes may affect:

• price;
• timing;
• equipment;
• Pilot eligibility;
• deliverables;
• Mission feasibility.

Detailed change-order provisions appear in Section 30.

14.11 Client-provided content

Clients are responsible for having appropriate rights to information or materials they provide to DroneJob or a Pilot/DSP.

Examples include:

• site plans;
• maps;
• contact information;
• reference files;
• inspection criteria.

14.12 Client evaluation of providers

Clients remain responsible for evaluating whether a provider is appropriate for the specific project.

DroneJob may assist through:

• verification;
• profiles;
• reviews;
• matching;
• enterprise qualification.

These tools do not eliminate reasonable Client judgment.

15.1 Organization teams

Organizations may use DroneJob to coordinate:

• employees;
• Pilots;
• contractors;
• subcontractors;
• project managers;
• support personnel.

The Organization is responsible for deciding which individuals are authorized to act on its behalf.

15.2 DSP responsibility

Where a Client engages a DSP rather than a specific individual Pilot, the DSP is responsible for:

• staffing the work;
• assigning appropriately qualified personnel;
• supervision;
• ensuring applicable credentials;
• maintaining required insurance;
• meeting contractual obligations.

DroneJob's assignment tools do not transfer those responsibilities from the DSP to DroneJob.

15.3 Internal enterprise teams

Enterprise Customers may use DroneJob to assign their own employees or internal Pilots.

The Enterprise Customer remains responsible for:

• employment obligations;
• supervision;
• training;
• workplace safety;
• internal authorization;
• applicable policies.

DroneJob provides the software used to coordinate the activity.

15.4 Contractors and subcontractors

Where lawful and permitted by the applicable service agreement, a Pilot or DSP may use contractors or subcontractors.

The party engaging the subcontractor is responsible for:

• determining whether subcontracting is permitted;
• selecting qualified personnel;
• verifying required credentials;
• ensuring appropriate insurance;
• communicating applicable scope and safety requirements;
• supervising performance as required;
• ensuring confidentiality and data obligations are respected.

15.5 Client expectations regarding personnel

If a Client engaged a specific individual based materially on that person's identity, qualifications or expertise, substitution may require Client approval depending on the applicable agreement.

A provider should not secretly substitute an unqualified person for a Pilot or specialist whose credentials were material to the Client's decision.

15.6 DroneJob qualification controls

Where available, DroneJob may help an Organization determine whether an individual appears qualified for an assignment based on information such as:

• credentials;
• insurance;
• skills;
• service area;
• equipment;
• Organization approval.

These controls are productivity and governance tools.

The responsible Organization remains accountable for its staffing decision.

15.7 Assignment restrictions

Organizations should not assign a person to a Mission that requires qualifications the Organization knows the person lacks.

DroneJob may prevent or flag an assignment where available information indicates a requirement is not satisfied.

An override feature, where available, does not transfer responsibility for the decision to DroneJob.

15.8 Contractor Accounts

Where a contractor uses DroneJob in connection with Organization work, access should be limited to information reasonably necessary for assigned responsibilities.

An external contractor should not automatically receive access to:

• the Organization's entire Client list;
• unrelated Missions;
• confidential financial information;
• unrelated vendor information.

The Organization is responsible for configuring access appropriately using available controls.

15.9 Data and confidentiality

Organizations must ensure team members and subcontractors handle:

• Client Data;
• Mission information;
• deliverables;
• credentials;
• confidential information;

consistently with applicable obligations.

More detailed confidentiality requirements appear in Section 28.

15.10 Responsibility for team activity

Subject to applicable law and agreements, an Organization or DSP is responsible for the performance of personnel it selects to fulfill its service obligations.

The fact that an individual has a separate DroneJob Account does not eliminate that responsibility.

15.11 No automatic relationship with DroneJob

A person's participation on a team or Mission does not make that individual:

• DroneJob's employee;
• DroneJob's contractor;
• DroneJob's agent.

Any direct engagement by DroneJob must be established separately.

16.1 Meaning of an Order

An Order or Work Request is an instruction or request that may initiate a DroneJob workflow.

Depending on the applicable workflow, an Order may request:

• Pilot sourcing;
• Mission creation;
• assignment;
• scheduling;
• inspection;
• capture;
• deliverables;
• other drone-related services or operational actions.

An Order record does not automatically mean that:

• a Pilot has accepted the work;
• a DSP has accepted contractual responsibility;
• required regulatory approvals exist;
• a binding service agreement has been formed.

The applicable workflow or Additional Terms determine when a binding commitment occurs.

16.2 Order sources

DroneJob may receive Orders from an authorized:

• User;
• administrator;
• enterprise system;
• Integration;
• API client;
• automated workflow.

DroneJob may record the source for:

• auditability;
• troubleshooting;
• authorization;
• reconciliation.

16.3 Customer authorization

An Enterprise Customer is responsible for ensuring that persons and systems submitting Orders on its behalf are properly authorized.

An instruction received through valid Customer-controlled credentials or an authorized Integration may be treated by DroneJob as an instruction from the Customer within the scope of the granted authorization.

16.4 Order accuracy

Customers are responsible for the accuracy and completeness of information they submit or cause to be submitted.

This may include:

• service type;
• location;
• timing;
• scope;
• asset;
• deliverables;
• qualification requirements;
• site information;
• other project requirements.

DroneJob may validate information but is not required to independently verify every field submitted through an enterprise system.

16.5 Duplicate Orders

Customers should use applicable identifiers, idempotency mechanisms or other supported controls to reduce unintended duplicate Orders.

DroneJob may implement technical safeguards against duplicates but cannot guarantee that all duplicate or conflicting source instructions will be detected.

16.6 Order validation

DroneJob may:

• reject;
• pause;
• request correction;
• flag;

an Order where information appears:

• incomplete;
• invalid;
• unauthorized;
• contradictory;
• technically unsupported;
• unsafe;
• inconsistent with platform rules.

16.7 Enterprise identifiers

Orders may include Customer-provided references such as:

• work-order ID;
• site ID;
• asset ID;
• project ID;
• purchase-order reference;
• cost center;
• other enterprise identifiers.

DroneJob may use these references to support reconciliation with external systems.

16.8 Program-specific requirements

Enterprise programs may impose requirements such as:

• SLA;
• approved vendor pool;
• qualification;
• insurance;
• deliverable standards;
• workflow approval.

These may be governed by applicable Additional Terms.

17.1 Mission records

A Mission may originate from an inquiry, accepted proposal, direct User creation, Enterprise Order, API, Integration or authorized automation. It may contain the operational details needed to coordinate the work, such as parties, scope, location, timing, assignments, deliverables, status and approvals.

Where the workflow requires a Pilot or DSP to accept a Mission, acceptance should be performed through the applicable authorized method. Assignment does not become acceptance until the required acceptance process occurs.

17.2 Workflow state

DroneJob may use workflow states to help participants coordinate work. Actual states depend on the Service.

A software status should be interpreted in context and does not independently establish a legal or regulatory conclusion.

For example, "Ready" does not mean that aviation law necessarily authorizes flight.

17.3 Exceptions and closure

Recording an exception such as weather, access, equipment or safety does not automatically determine which party bears financial or contractual responsibility. Applicable agreements govern those consequences.

Mission completion or closure within DroneJob may indicate that the workflow has reached the applicable completed state. It does not automatically waive payment obligations, warranty claims, confidentiality or dispute rights.

18.1 Authorized access

Customers may access APIs only through credentials and methods provided or approved by DroneJob.

Customers must not:

• bypass authentication;
• scrape protected interfaces as a substitute for approved APIs;
• circumvent rate limits;
• use another Customer's credentials;
• exceed authorized scopes.

18.2 Credentials

Customers are responsible for protecting:

• API keys;
• OAuth credentials;
• webhook secrets;
• certificates;
• other Integration credentials.

Credentials must not be:

• exposed publicly;
• committed to public source repositories;
• shared outside authorized personnel or systems.

18.3 Customer applications

A Customer may connect its own application to DroneJob where permitted.

The Customer is responsible for:

• its application;
• configuration;
• security;
• compliance;
• actions performed through the application;
• rights to data submitted through it.

18.4 Scope and permissions

An Integration should request only the permissions reasonably necessary for its approved function.

DroneJob may restrict API access by:

• scope;
• Organization;
• role;
• endpoint;
• rate;
• data type;
• action.

18.5 Webhooks

DroneJob may send webhook notifications concerning events such as:

• Mission creation;
• Mission assignment;
• status change;
• deliverable availability;
• vendor readiness;
• other supported events.

Customers are responsible for maintaining:

• valid endpoints;
• security;
• webhook secret validation;
• processing logic.

18.6 Delivery and retries

API requests and webhook deliveries may:

• fail;
• time out;
• retry;
• arrive more than once;
• arrive out of order.

Customers should design Integrations appropriately, including use of:

• idempotency;
• event identifiers;
• timestamps;
• retry-safe processing;

where supported.

18.7 Rate limits

DroneJob may impose reasonable technical limits to protect:

• availability;
• security;
• other Customers.

Customers must comply with documented rate limits.

18.8 API changes

DroneJob may:

• update;
• version;
• deprecate;
• retire;

API capabilities.

Where commercially reasonable and applicable to supported enterprise APIs, DroneJob may provide notice of material deprecations according to applicable documentation or agreement.

Specific enterprise commitments may differ under an Enterprise Agreement.

18.9 Data obtained through APIs

API access does not grant broader rights to Customer Data than the Customer otherwise has.

Customers must use API-accessed information consistent with:

• these Terms;
• Privacy Policy;
• applicable law;
• rights of applicable data subjects or Customers;
• applicable agreements.

18.10 Security suspension

DroneJob may immediately:

• revoke;
• rotate;
• restrict;
• suspend;

Integration credentials where reasonably necessary because of:

• suspected compromise;
• abuse;
• security risk;
• material Terms violation.

18.11 Additional API Terms

DroneJob may introduce separate API or Developer Terms as the Integration ecosystem matures.

Where applicable, those Additional Terms will control as described in Section 1.

19.1 Customer-directed automation

Examples may include:

ERP work order
    ↓
Create DroneJob Order

Mission completed
    ↓
Notify Client

Credential expiring
    ↓
Notify administrator

19.2 Authorized system instructions

Actions received through a Customer's properly authorized:

• Account;
• API credentials;
• Integration;
• webhook configuration;
• automation rules;

may be treated as instructions authorized by that Customer within the configured scope.

19.3 Customer responsibility

Customers are responsible for:

• selecting automations;
• configuring triggers;
• configuring conditions;
• configuring actions;
• defining permissions;
• testing business-critical automation;
• supervising appropriate outcomes.

19.4 Material actions

DroneJob may require:

• human approval;
• additional verification;
• workflow approval;

before certain material actions.

Examples may include:

• contractual commitment;
• pricing approval;
• payment;
• compliance override;
• Mission safety override.

Customers must not use automation to circumvent such controls.

19.5 Incorrect source data

Automations may act on inaccurate or incomplete source information.

Customers should maintain reasonable:

• data quality;
• configuration;
• validation.

19.6 Errors

Automated actions may:

• fail;
• duplicate;
• be delayed;
• produce unintended results.

DroneJob may provide:

• logs;
• alerts;
• retry behavior;
• audit information.

No automation system can guarantee error-free execution.

19.7 Reversibility

Some automated actions may be difficult or impossible to reverse.

Customers should use appropriate review and approval controls for consequential actions.

19.8 Auditability

DroneJob may record:

• trigger;
• source;
• action;
• result;
• timestamp;
• authorization context.

19.9 AI-assisted automation

If AI influences or determines an automated action, Section 21 applies in addition to this Section.

20.1 Customer authorization

By enabling an Integration, the Customer authorizes DroneJob to:

• access;
• receive;
• transmit;
• process;

information within the permissions granted for that Integration.

20.2 Third-party terms

A Third-Party Service is governed by the Customer's separate agreement with that provider.

DroneJob's Terms do not replace those third-party terms.

20.3 Data transferred to third parties

Once DroneJob transfers Customer Data to an independently controlled Third-Party Service at the Customer's direction, DroneJob may no longer control:

• storage;
• retention;
• processing;
• security;
• model training;

performed by that provider.

Customers should review the provider's terms and privacy practices before enabling the connection.

20.4 Third-party availability

DroneJob does not control the continued availability or functionality of independent Third-Party Services.

An Integration may stop working because of:

• third-party API changes;
• outages;
• pricing changes;
• authorization changes;
• discontinuation.

20.5 Customer credentials

Where a Customer supplies credentials for a Third-Party Service, the Customer represents that it is authorized to use those credentials and permit the Integration.

20.6 Revocation

Customers may revoke connected services where supported.

Revocation may stop future access but cannot necessarily reverse prior actions or delete information already transmitted.

20.7 Third-party actions

Where a Third-Party Service can take actions within DroneJob, the Customer is responsible for:

• choosing the service;
• configuring permissions;
• supervising its use.

20.8 External AI tools

If a Customer connects its own AI provider, AI agent, model or API key, that connection is a Customer-directed Third-Party Service.

Additional AI provisions appear in Section 21.

21.1 AI Feature examples

Depending on availability, AI may assist with drafting, summarization, scoping, Mission planning, communications, compliance review and other productivity tasks. Availability depends on the Customer's plan and configuration.

21.2 Inputs

"AI Input" means information, prompts, instructions, files, Customer Data or context provided to or processed through an AI Feature.

Users are responsible for ensuring they have the rights and authority necessary to provide Input.

Users should not intentionally submit:

• unlawfully obtained information;
• confidential information they are prohibited from processing;
• unnecessary highly sensitive data.

21.3 Outputs

"AI Output" means content or results generated by an AI Feature.

Output may include draft text, a recommendation, summary, classification, analysis, prediction or proposed action. AI Output may be inaccurate, incomplete, misleading or non-unique.

DroneJob does not represent that Output is guaranteed to be correct.

21.4 User review

Users are responsible for reviewing AI Output before:

• relying on it;
• sending it externally;
• incorporating it into professional deliverables;
• making material decisions.

21.5 Supportive role

AI does not become the accountable professional.

For example:

• a Risk Agent may flag a concern, but the responsible Pilot makes the operational decision;
• a Sales Agent may draft a price proposal, but the business determines the price;
• a Project Manager Agent may propose a Mission plan, but authorized Users approve material commitments;
• a Fleet Agent may flag an equipment issue, but the responsible operator determines equipment suitability.

21.6 AI Actions

Some AI Features may be capable of performing bounded actions where enabled, such as creating a draft or task, updating a record, preparing a Mission, sending an approved communication or executing a configured workflow action.

21.7 Authorization

By enabling an AI Feature with action permissions, the Customer authorizes the AI Feature to operate within the configured scope.

Customers are responsible for:

• selecting permissions;
• limiting scope;
• determining appropriate actions;
• monitoring use.

21.8 Human approval

DroneJob may require explicit human approval for material actions.

DroneJob's intended baseline is that decisions involving significant:

• safety;
• regulatory compliance;
• financial commitment;
• contractual commitment;
• professional conclusion;

remain subject to responsible human review unless a specific lawful and contractually authorized workflow expressly provides otherwise.

21.9 No bypass

Users may not intentionally configure or use AI to bypass:

• authorization;
• security;
• regulatory controls;
• required approval;
• safety controls.

21.10 Third-party AI models

DroneJob AI Features may rely on third-party AI technologies.

DroneJob may change the models or providers used.

Where those providers process Customer Data on DroneJob's behalf, applicable privacy/subprocessor obligations apply.

21.11 General-purpose model training

DroneJob's default policy is not to use private Client data, private Mission data, private communications, private deliverables or Enterprise Customer Data to train general-purpose AI models for the benefit of unrelated Customers unless:

• the applicable Customer expressly opts in; or
• a separate written agreement expressly authorizes the use.

This policy is further described in the Privacy Policy.

21.12 Customer-specific AI

DroneJob may process Customer Data to provide AI functionality for that Customer.

For example, an AI Feature may use:

• the Customer's service catalog;
• approved business information;
• Mission context;
• Client history;

to produce a response for that Customer.

This does not by itself authorize use of that Customer Data to train a general-purpose model for other Customers.

21.13 Similar outputs

Because AI systems are probabilistic and many Users may provide similar Inputs, AI Outputs may be identical or similar across different Users.

DroneJob does not guarantee that AI Output is unique.

21.14 Intellectual-property limitations

DroneJob does not guarantee that:

• AI Output is copyrightable;
• exclusive rights exist in Output;
• Output will not resemble third-party material.

Users should evaluate intellectual-property implications before commercial reliance.

21.15 Connected external AI

If a Customer connects a third-party AI tool, the Customer is responsible for:

• choosing the tool;
• granting permissions;
• understanding the provider's terms;
• supervising its actions.

Once Customer Data is transmitted to that independent provider, its practices may be governed by the Customer's agreement with that provider.

21.16 Audit and AI activity

DroneJob may record information about AI Features such as:

• request;
• Output;
• proposed action;
• executed action;
• approval;
• timestamp;
• errors.

Such records may support:

• auditability;
• security;
• troubleshooting;
• product improvement.

21.17 AI availability

AI Features may:

• change;
• improve;
• be replaced;
• use different models;
• be discontinued.

AI-specific usage limits may apply according to the Customer's plan.

22.1 Mission planning

DroneJob may assist with:

• scope;
• schedule;
• location;
• equipment;
• checklists;
• capture requirements;
• project requirements;
• workflow preparation.

A generated Mission plan remains subject to User review.

22.2 Airspace

DroneJob may display or integrate airspace-related information.

Users are responsible for determining:

• current restrictions;
• applicable authorization;
• legality of the planned operation.

DroneJob is not the FAA or another aviation authority.

22.3 Weather

DroneJob may display:

• weather;
• forecast;
• wind;
• operational-condition information.

Weather data may:

• change;
• be delayed;
• be incomplete.

The responsible operator must assess actual conditions.

22.4 Risk tools

DroneJob may provide:

• risk scores;
• warnings;
• recommended mitigations;
• checklists.

These tools do not replace a professional or legally required risk assessment where one applies.

22.5 Compliance assistance

DroneJob may help Users track:

• credentials;
• insurance;
• training;
• documents;
• authorizations;
• compliance requirements.

A software status does not guarantee legal compliance.

22.6 AI compliance assistance

An AI Feature may:

• identify missing information;
• highlight a potential compliance issue;
• explain a requirement;
• suggest a next step.

AI must not be treated as final legal or aviation authorization.

22.7 Go/no-go decision

The final decision regarding whether a Mission may safely and legally proceed remains with the appropriately responsible human operator and Organization.

DroneJob must not be treated as the Pilot in Command.

22.8 Specialized professional outputs

DroneJob may assist with workflows relating to:

• surveying;
• inspection;
• thermal analysis;
• engineering-adjacent work;
• insurance;
• mapping.

DroneJob assistance does not transform a User into a licensed professional or make an AI Output a regulated professional conclusion.

22.9 Enterprise procedures

Enterprise Customers may configure additional:

• approvals;
• safety rules;
• compliance requirements;
• internal procedures.

Users participating in those programs remain responsible for following applicable requirements.

22.10 Conflicting information

If DroneJob information conflicts with:

• applicable law;
• official regulator information;
• site-specific safety instructions;
• a qualified professional's required determination;

the responsible User must not rely on DroneJob merely because it is more convenient.

23.1 DroneJob Conversations

DroneJob may maintain a Conversation as a unified business record.

A Conversation may contain messages delivered through more than one channel.

For example:

Client inquiry       — SMS
Pilot reply          — SMS
Client follow-up     — IN_APP
Pilot response       — EMAIL

Where supported, these communications may appear in the same DroneJob timeline.

23.2 User-authored communications

A message authored by a User remains that User's communication.

DroneJob's:

• routing;
• transmission;
• storage;
• notification;
• formatting;

of the message does not make DroneJob the author of the communication.

Users are responsible for the messages they send.

23.3 DroneJob-originated communications

DroneJob may separately send its own messages relating to:

• Account security;
• authentication;
• verification;
• Client inquiries;
• Missions;
• platform activity;
• billing;
• Services.

DroneJob-originated messages should not be confused with messages authored by another Client or provider.

23.4 Appropriate communication use

Users may use DroneJob communications for legitimate purposes related to:

• Client inquiries;
• professional services;
• Missions;
• scheduling;
• project coordination;
• business operations;
• permitted marketplace activity.

Users must not use communications to:

• spam;
• harass;
• threaten;
• defraud;
• transmit unlawful material;
• conduct unauthorized marketing;
• distribute malware;
• evade opt-out requirements.

23.5 Communications with independently acquired Clients

Where supported, a Pilot/DSP may use DroneJob to communicate with Clients obtained outside the DroneJob Marketplace.

The User remains responsible for having:

• appropriate authority;
• required messaging consent;
• appropriate business relationship;

before contacting those persons.

DroneJob's availability as a communication tool does not create consent where consent does not otherwise exist.

23.6 Contact information

Users should provide accurate communication information.

Users should not deliberately:

• impersonate another person;
• spoof identity;
• use another person's contact information without authority.

23.7 Communication history

DroneJob may retain communications as part of:

• Client history;
• inquiry history;
• Mission records;
• workflow history;
• dispute history;
• enterprise audit records.

Retention practices are described in the Privacy Policy.

23.8 Communications outside DroneJob

Users may choose to exchange personal contact information and communicate outside DroneJob where permitted.

DroneJob generally cannot preserve or provide platform protections for communications that occur entirely outside DroneJob-controlled channels.

Moving communications outside DroneJob may reduce the availability of:

• Conversation history;
• audit history;
• AI context;
• dispute evidence;
• workflow automation;
• communication-based Mission records.

The detailed off-platform policy appears in Section 35.

23.9 Organizational communications

Communications performed within an Organization environment may be accessible to authorized:

• Organization administrators;
• managers;
• support Users;
• other authorized personnel.

Users should not assume that business communications conducted within an Organization environment are private from the Organization.

23.10 Recording and voice communications

If DroneJob later provides:

• voice calls;
• recording;
• transcription;

additional notice, consent and legal requirements may apply.

DroneJob must not interpret this Section as blanket authorization to record calls.

Recording functionality should not be activated without appropriate product and legal review.

23.11 Communications monitoring

DroneJob may use automated or manual systems to detect:

• spam;
• abuse;
• malware;
• fraud;
• security incidents;
• policy violations.

This does not mean DroneJob undertakes to manually review every communication.

23.12 AI assistance

Where enabled, AI may assist Users with:

• summaries;
• suggested replies;
• tasks;
• potential schedule extraction;
• potential scope changes.

AI interpretations remain subject to Section 21.

A suggested interpretation is not a substitute for the original communication.

24.1 DroneJob messaging program

DroneJob SMS may provide service-related and transactional communications such as:

• Account verification;
• security messages;
• new Client inquiries;
• Client/Pilot replies;
• Conversation notifications;
• scheduling coordination;
• Mission updates;
• appointment reminders;
• project updates;
• Account activity;
• secure links to continue activity in DroneJob.

The exact messages received depend on the Services and messaging program for which the User has opted in.

24.2 Consent

Where required, Users must affirmatively consent to receive SMS messages from the applicable DroneJob messaging program.

Consent must be:

• voluntary;
• appropriate to the messaging purpose;
• separate from required acceptance of these Terms where required.

SMS consent is not automatically granted merely because a User:

• creates an Account;
• accepts these Terms;
• purchases a Service;
• provides a telephone number.

24.3 Separate messaging purposes

Consent for transactional or service-related messages does not automatically constitute consent for unrelated promotional or marketing SMS.

Where DroneJob offers multiple message programs, separate consent may be required.

24.4 Consent is not a condition of purchase

Consent to receive marketing text messages is not a condition of purchasing any property, goods, or services from DroneJob.

24.5 Message frequency

Message frequency varies depending on your Account activity, Client inquiries, Conversations, Missions and use of DroneJob Services.

24.6 Message and data rates

Message and data rates may apply.

Your carrier's standard messaging and data charges may apply.

24.7 Opting out

You may reply STOP to an applicable DroneJob SMS message to opt out of that messaging program.

DroneJob or its messaging provider may send a final confirmation message acknowledging the opt-out.

Following an applicable opt-out:

• DroneJob will stop messages covered by that opt-out as required;
• other communications not covered by the opt-out may continue through permitted channels.

Opting out of SMS does not automatically terminate your DroneJob Account.

24.8 Re-enrollment

Where permitted, a User who has opted out may later voluntarily re-enroll through an approved opt-in method.

24.9 Help

Reply HELP for help.

You may also obtain support at https://www.dronejob.ai or support@dronejob.ai.

24.10 Carriers

Carriers are not liable for any delayed or undelivered messages.

SMS delivery depends on:

• carrier networks;
• device availability;
• recipient connectivity;
• provider availability;
• other factors outside DroneJob's control.

DroneJob cannot guarantee that every SMS message will be delivered or delivered at a particular time.

24.11 Supported carriers and regions

Messaging functionality may vary based on:

• country;
• carrier;
• number type;
• regulatory requirements;
• provider capabilities.

A DroneJob SMS service available in one jurisdiction may not be available in another.

24.12 Privacy

DroneJob's handling of mobile information and SMS consent information is described in the Privacy Policy: https://www.dronejob.ai/privacy

In particular, DroneJob does not sell or share mobile numbers or SMS opt-in information with third parties or affiliates for their own marketing or promotional purposes.

24.13 Client/Pilot SMS relay

Where DroneJob supports SMS relay:

Client
   ↕
DroneJob
   ↕
Pilot

DroneJob may:

• route messages;
• maintain Conversation mapping;
• store communication history;
• provide secure links;
• maintain delivery state.

Users remain responsible for the content of messages they author.

24.14 Messaging consent from Customers' contacts

If a Pilot, DSP or Enterprise Customer uses DroneJob to send SMS to that Customer's independently acquired contacts, the Customer is responsible for ensuring that appropriate messaging authority or consent exists.

DroneJob may:

• require evidence of consent;
• apply messaging restrictions;
• suspend messaging features;

where reasonably necessary to prevent abuse or regulatory violations.

24.15 Opt-in confirmation

Where required by the applicable messaging program or carrier rules, DroneJob may send a confirmation message after a User enrolls.

Such confirmation may identify:

• DroneJob;
• the messaging program;
• frequency;
• rate disclosure;
• HELP;
• STOP.

24.16 Program changes

DroneJob may modify or discontinue an SMS program subject to applicable law and carrier requirements.

25.1 DroneJob numbers

DroneJob may use:

• toll-free numbers;
• local numbers;
• messaging numbers;
• pooled numbers;
• dynamically assigned numbers;
• other supported numbers.

A number may be used for:

• notifications;
• Conversation relay;
• support;
• verification;
• future voice functionality.

25.2 No ownership right

Unless DroneJob expressly agrees otherwise in writing, a User does not acquire ownership of a DroneJob-provided telephone number or communication address.

DroneJob may:

• assign;
• reassign;
• replace;
• retire;
• pool;

communication identifiers as necessary to operate the Services.

25.3 Branding and contact cards

DroneJob may allow Users to save DroneJob communication information as a contact or vCard.

A saved contact name or brand presentation does not change:

• carrier routing;
• ownership;
• regulatory treatment;

of the underlying number.

25.4 Conversation routing

A communication address may be used to associate an incoming message with the appropriate DroneJob Conversation.

Routing may depend on:

• sender;
• recipient;
• temporary mapping;
• Conversation state;
• assigned number;
• other technical context.

Users must not attempt to deliberately defeat DroneJob routing controls.

25.5 Shared and pooled numbers

Some DroneJob numbers may be shared across multiple Users or Conversations through technical routing.

Users should not assume that a DroneJob number is a private or permanent telephone number dedicated exclusively to that User.

25.6 Number changes

DroneJob may need to change a communication number because of:

• carrier requirements;
• regulatory requirements;
• abuse;
• provider changes;
• technical limitations;
• availability;
• product changes.

Where commercially reasonable, DroneJob may provide notice where a material number change affects an active service.

25.7 Portability

DroneJob does not promise that DroneJob-provided numbers are portable to another provider or transferable to the User unless a specific written agreement expressly provides otherwise.

25.8 Use restrictions

DroneJob-provided numbers must not be used for:

• unlawful messaging;
• spam;
• unauthorized marketing;
• harassment;
• fraud;
• impersonation;
• prohibited content;
• bypassing carrier requirements.

25.9 Emergency communications

DroneJob communication services are not emergency services unless DroneJob expressly states otherwise.

Users should not rely on DroneJob messaging, voice or communication numbers for:

• 911;
• emergency dispatch;
• urgent life-safety communications.

25.10 Caller and sender identification

Carrier or device display behavior may vary.

DroneJob cannot guarantee that a receiving device will display:

• DroneJob;
• a particular business name;
• a particular caller ID;
• a saved contact name.

25.11 Account termination

Upon suspension or termination:

• communication access may end;
• temporary number mappings may be removed;
• relay functionality may stop.

DroneJob may retain Conversation records as described in the Privacy Policy and applicable agreements.

25.12 Future voice functionality

If a DroneJob number later supports voice:

• additional usage terms;
• carrier charges;
• recording consent;
• emergency-service limitations;

may apply.

26.1 Customer Data

Customer Data may include information concerning:

• Clients;
• leads;
• Missions;
• employees;
• Pilots;
• vendors;
• files;
• communications;
• enterprise Orders;
• workflows;
• business records.

The Customer remains responsible for the lawfulness, accuracy and appropriate use of Customer Data.

26.2 User Content

User Content may include:

• profile information;
• portfolio media;
• files;
• messages;
• personal notes;
• reviews;
• comments;
• project content;
• other material submitted by a User.

26.3 User ownership

DroneJob does not claim ownership merely because content is uploaded to the Services.

The applicable User or Customer retains whatever intellectual-property or other rights that party lawfully holds.

26.4 License to DroneJob

The User/Customer grants DroneJob a non-exclusive license to:

• host;
• store;
• copy;
• process;
• transmit;
• display;
• format;
• create technical derivatives;
• otherwise use;

Customer Data/User Content solely as reasonably necessary to:

• provide;
• secure;
• support;
• maintain;
• improve;

the Services consistent with these Terms and the Privacy Policy.

For public content, the license includes making the content publicly available according to the User's selected or applicable visibility setting.

26.5 Authority to provide content

Users represent that they have the rights and authority necessary to provide content to DroneJob.

Users must not upload content that:

• infringes another person's rights;
• violates confidentiality;
• is unlawfully obtained;
• violates privacy rights;
• contains malware;
• is otherwise prohibited.

26.6 Customer-controlled data

Where DroneJob processes Customer Data on behalf of an Enterprise Customer, DSP or other business Customer, DroneJob's processing is also subject to applicable:

• DPA;
• Enterprise Agreement;
• Customer instructions.

26.7 Organization ownership and user departure

Content created within an Organization environment may constitute Organization Customer Data even if an individual Authorized User created it.

An Authorized User leaving the Organization does not necessarily gain a right to remove Organization business records.

Similarly, an Organization does not automatically acquire ownership of content the User maintained separately in an independent personal context.

26.8 Public content

Users who designate content as public authorize DroneJob to display that content publicly.

Public content may be:

• indexed;
• cached;
• copied;

by third parties.

Users should publish only content they are authorized to make public.

26.9 Moderation

DroneJob may:

• remove;
• restrict;
• quarantine;
• decline to display;

content where reasonably necessary because of:

• law;
• infringement claims;
• malware;
• fraud;
• abuse;
• platform rules;
• security.

26.10 Backups

Customers remain responsible for maintaining independent copies of important business data where appropriate.

DroneJob's backup systems are intended to support service resilience and should not necessarily be treated as a Customer's only archival system.

26.11 AI use of Customer Data

AI processing of Customer Data remains subject to Section 21 and the Privacy Policy.

Uploading Customer Data does not by itself authorize DroneJob to use private Customer Data to train general-purpose AI models for unrelated Customers.

26.12 Aggregated and de-identified information

DroneJob's rights concerning properly aggregated or de-identified information will be governed by the Privacy Policy and applicable Enterprise agreements.

27.1 Client materials

Clients may provide materials such as:

• site plans;
• specifications;
• logos;
• maps;
• CAD files;
• reference imagery;
• instructions.

The Client retains its rights in such materials.

The Client grants the provider and DroneJob the rights necessary to use those materials for the authorized project and platform workflow.

27.2 Pilot/DSP background materials

A Pilot or DSP may use pre-existing:

• templates;
• methods;
• processes;
• know-how;
• software;
• report formats;
• intellectual property.

Unless the parties agree otherwise, merely performing a Mission does not automatically transfer ownership of all pre-existing provider intellectual property.

27.3 Mission deliverables

Deliverables may include:

• photography;
• video;
• reports;
• maps;
• inspection outputs;
• models;
• measurements;
• processed imagery;
• data files.

The applicable Client/Pilot agreement should determine:

• ownership;
• license;
• permissible use;
• transfer rights;
• publication rights.

27.4 DroneJob does not determine transfer

Uploading or delivering a file through DroneJob does not itself determine whether:

• ownership transferred;
• an exclusive license was granted;
• copyright was assigned;
• commercial reuse is permitted.

Those rights depend on the applicable agreement and law.

27.5 Portfolio use

A Pilot/DSP may use Mission material publicly only if authorized.

DroneJob may provide a workflow allowing content to be copied or referenced into a portfolio.

The existence of that workflow does not override:

• confidentiality;
• Client restrictions;
• intellectual-property rights.

27.6 Proof Packs

DroneJob may generate a Proof Pack or other evidence record derived from authorized Mission information.

DroneJob's ownership of the Proof Pack format, template or platform technology does not give DroneJob ownership of the underlying Client/Pilot intellectual property contained in it.

27.7 Technical metadata

DroneJob may create technical metadata such as:

• file identifiers;
• hashes;
• thumbnails;
• previews;
• workflow metadata.

DroneJob may use such technical material to operate the Services.

27.8 Specialist and regulated outputs

Specialized deliverables may be subject to:

• professional-license requirements;
• regulatory standards;
• Client contractual requirements.

DroneJob's storage or presentation of a deliverable does not convert it into a licensed professional work product.

27.9 AI-generated assistance

AI may assist with:

• drafting;
• formatting;
• summarization;
• organization.

AI-generated content remains subject to the limitations in Section 21.

DroneJob does not guarantee that AI Output:

• is unique;
• is copyrightable;
• does not resemble third-party material.

27.10 Third-party software outputs

Deliverables created using third-party software may also be subject to that provider's terms.

28.1 Confidential Information

"Confidential Information" means non-public information disclosed or made available in circumstances where a reasonable person would understand that the information is confidential.

Examples may include:

• project information;
• Client information;
• Mission locations;
• infrastructure information;
• site plans;
• pricing;
• business records;
• customer lists;
• technical information;
• security information;
• proprietary files;
• unpublished deliverables;
• trade secrets.

28.2 Exclusions

Confidential Information generally does not include information that the recipient can demonstrate:

• is publicly available without breach;
• was lawfully known before disclosure;
• was independently developed without use of the Confidential Information;
• was lawfully received from another source without confidentiality restriction.

28.3 Permitted use

A recipient may use another party's Confidential Information only as reasonably necessary to:

• evaluate an opportunity;
• perform an authorized Mission;
• operate the applicable project/workflow;
• provide agreed services;
• comply with applicable obligations.

28.4 Protection

Recipients must use reasonable care to protect Confidential Information from:

• unauthorized access;
• use;
• disclosure.

28.5 Team access

A User may share Confidential Information with:

• employees;
• contractors;
• subcontractors;
• professional advisors;

only where they:

• have a legitimate need to know;
• are subject to appropriate confidentiality obligations.

28.6 Enterprise access

Enterprise Customers may restrict access to sensitive information through:

• roles;
• permissions;
• vendor pools;
• project controls.

Technical permissions supplement but do not replace contractual confidentiality obligations.

28.7 Required disclosure

A recipient may disclose Confidential Information where required by:

• law;
• court order;
• valid governmental process;
• public-records laws;
• freedom-of-information laws;
• government audit requirements.

Where legally permitted and appropriate, the recipient should provide reasonable notice to the disclosing party.

Where a public entity is legally prohibited from providing advance notice, failure to give notice does not itself constitute a breach of this baseline confidentiality Section.

28.8 No public portfolio right

Receiving or creating Confidential Information in a Mission does not create an automatic right to:

• publish;
• market;
• post;
• place in a portfolio;

that information.

28.9 DroneJob access

DroneJob may access Confidential Information where reasonably necessary to:

• provide the Services;
• support Users;
• secure the platform;
• troubleshoot;
• investigate abuse;
• comply with law.

DroneJob's handling of Customer Data is also governed by the Privacy Policy and applicable enterprise agreements.

28.10 Enterprise agreements

Enterprise agreements may impose stricter:

• confidentiality;
• data-security;
• use restrictions.

Where applicable, those terms control as described in Section 1.

28.11 No reduction of independent obligations

This Section establishes a baseline.

It does not reduce confidentiality obligations the parties already owe under:

• NDA;
• employment;
• contract;
• law.

29.1 Drafts and acceptance

A quote, estimate or proposal may describe services, price, assumptions, schedule and other commercial terms. Unless expressly stated otherwise, a draft quote is not binding until the applicable acceptance requirements are satisfied.

AI-generated commercial documents are supportive drafts. The User is responsible for reviewing pricing, legal terms, scope and professional claims before sending or accepting a document where approval is required.

29.2 Underlying service agreement

Unless DroneJob expressly agrees otherwise, the underlying drone-service agreement is between the Client and the Pilot/DSP. Contract templates are productivity tools, not legal advice. A project managed in DroneJob may remain governed by a contract formed outside DroneJob.

29.3 Enterprise and public-sector agreements

Enterprise work may be governed by a master services agreement, statement of work, purchase order or program rules.

A DroneJob workflow action alone does not grant legal authority to a User who lacks actual authority under applicable procurement rules.

Where a valid Public Sector agreement expressly governs a transaction, its applicable procurement and contracting terms control over inconsistent default marketplace workflow assumptions as provided by Section 1.

30.1 Change Orders

Unless the applicable agreement provides otherwise, a proposed change does not automatically modify the existing agreement. Material changes should be approved through an authorized workflow or other valid contractual method.

30.2 AI detection of scope changes

AI may flag that a Conversation appears to request additional work and may suggest creating a Change Order.

The AI detection itself does not modify:

• price;
• scope;
• contract.

An authorized User or workflow must approve the applicable change. DroneJob does not guarantee payment merely because additional work was recorded in the platform.

30.3 Safety and public-sector change control

Operational safety changes do not necessarily constitute a Client-approved commercial Change Order.

A DroneJob User's technical ability to approve a workflow does not represent that the User has statutory or procurement authority to obligate public funds.

31.1 Weather and site conditions

Weather, airspace restrictions, site access, equipment issues or other operational conditions may make a Mission unsafe, unlawful or impractical. The responsible Pilot retains authority over safe operation.

31.2 Safety authority

No Client, Enterprise Customer or DroneJob workflow may require a Pilot to conduct an operation that the responsible Pilot reasonably determines cannot be performed lawfully or safely.

31.3 Rescheduling and estimates

Where a Mission cannot proceed, the parties may attempt to reschedule. Applicable cancellation, mobilization, SLA or public-contract terms may determine commercial consequences. ETA and similar predictions are estimates unless expressly guaranteed. An SLA should not require unsafe or unlawful aviation activity.

A recorded exception reason is a workflow record and does not automatically resolve financial responsibility between the parties.

32.1 Cancellation

A Client or provider may cancel subject to the applicable agreement. A Pilot must not be penalized by DroneJob merely for refusing to knowingly conduct an unlawful operation.

32.2 No invented automatic fee

DroneJob does not create a mobilization, travel or cancellation fee unless it is disclosed in the applicable marketplace or contractual terms.

The existence of a scheduled Mission, an arrival status or a cancelled status does not itself create a specific cancellation or mobilization charge.

32.3 Automated cancellation

An AI Feature or automated workflow should not impose a material cancellation charge or terminate a binding project unless the Customer has expressly authorized that action within an approved workflow.

Where DroneJob processes a payment, any applicable refund is also subject to Section 34.

33.1 Reviews

Eligible Users may be permitted to submit:

• written reviews;
• ratings;
• structured feedback;
• other experience information.

33.2 Genuine experience

Reviews must relate to a genuine interaction or service experience where required by the applicable review feature.

Users must not submit:

• fabricated reviews;
• reviews on behalf of undisclosed third parties;
• fraudulent ratings.

33.3 Review manipulation

Users must not:

• purchase fake reviews;
• coordinate fraudulent ratings;
• threaten another User to manipulate a review;
• offer an undisclosed prohibited incentive for a positive review;
• create Accounts solely to manipulate reputation.

33.4 Moderation

DroneJob may moderate reviews where reasonably necessary because of:

• fraud;
• harassment;
• privacy;
• irrelevant content;
• unlawful content;
• extortion;
• policy violation.

DroneJob is not required to remove a review solely because the reviewed User disagrees with it.

33.5 Disputes

DroneJob may provide a process allowing:

• response;
• report;
• review of alleged policy violations.

The existence of a dispute does not guarantee removal.

33.6 Verified reviews

Where DroneJob identifies a review as tied to a verified DroneJob transaction or Mission, that indicator means only that DroneJob associated the review with the applicable platform record.

It does not mean DroneJob independently verified every factual statement in the review.

33.7 Enterprise performance information

Enterprise Customers may maintain private vendor or Pilot performance information separate from public reviews.

Examples may include:

• SLA performance;
• quality score;
• internal approval;
• preferred-vendor status.

Private enterprise scoring should not automatically become a public marketplace rating.

33.8 AI-generated summaries

DroneJob may use AI to summarize review themes where available.

AI should not fabricate:

• ratings;
• reviews;
• customer experiences.

The underlying reviews remain the primary source.

33.9 Public-sector feedback

Feedback submitted by or maintained for a public-sector Customer may be subject to:

• public-records law;
• retention;
• agency policy.

DroneJob cannot guarantee deletion where lawful retention obligations apply.

33.10 Reputation portability

DroneJob may allow Users to build professional reputation through the platform.

The existence of a rating does not guarantee:

• marketplace visibility;
• future work;
• qualification for every Mission.

34.1 DroneJob subscription fees

DroneJob may charge for:

• subscriptions;
• plan upgrades;
• AI usage;
• storage;
• communications;
• add-ons;
• other Services.

Material pricing and billing terms will be disclosed through:

• checkout;
• pricing documentation;
• Order Form;
• applicable agreement.

34.2 Marketplace service payments

Where supported, DroneJob may facilitate payment from a Client to a Pilot/DSP.

The underlying service payment is distinct from DroneJob's own SaaS subscription charges.

34.3 Payment processor

DroneJob may use a third-party payment provider.

The provider may process:

• payment credentials;
• payouts;
• identity verification;
• bank information;
• disputes.

Additional provider terms may apply.

34.4 No escrow representation

DroneJob should not describe itself as:

• escrow agent;
• bank;
• money transmitter;

unless the applicable functionality and legal structure actually support that representation.

34.5 Fees

DroneJob may charge:

• subscription fees;
• disclosed transaction fees;
• usage fees;
• add-on fees;
• other disclosed charges.

DroneJob will not intentionally impose undisclosed fees.

34.6 Usage-based charges

Where a plan includes paid usage beyond an included allowance, the relevant:

• unit;
• rate;
• authorization;
• billing rule;

should be disclosed before charge.

34.7 Authorization

Users must use payment methods that they are authorized to use.

34.8 Provider payouts

Pilot/DSP payouts may be subject to:

• payment-provider verification;
• banking processing time;
• fraud review;
• dispute status;
• legal requirements.

34.9 Taxes

Users remain responsible for taxes applicable to:

• their business;
• income;
• service transactions;

except for taxes DroneJob is legally required to collect or remit.

34.10 Public-sector tax exemptions

A tax-exempt public entity may be required to provide valid exemption documentation.

DroneJob is not required to treat a transaction as exempt without documentation reasonably required to support the exemption.

34.11 Enterprise billing

Enterprise Customers may be billed according to:

• Order Form;
• purchase order;
• invoice;
• negotiated payment terms.

34.12 Public-sector invoicing

Public-sector Customers may require:

• purchase-order numbers;
• invoicing portals;
• specific invoice content;
• payment schedules;
• authorized procurement processes.

Such requirements bind DroneJob only where included in an applicable agreement or accepted procurement document.

34.13 Appropriations and government-specific clauses

Do not add federal appropriations, anti-deficiency, sovereign-immunity or mandatory government clauses to the general Terms.

Those provisions should be handled in an applicable Public Sector Addendum or negotiated agreement when required.

34.14 Refunds

Refund eligibility depends on:

• applicable subscription terms;
• marketplace rules;
• service agreement;
• applicable law.

A refund is not automatically owed merely because a Customer did not use an available feature.

34.15 Chargebacks

Users should contact DroneJob or the applicable provider to resolve legitimate billing disputes where appropriate.

Fraudulent or abusive chargebacks may result in:

• payment review;
• restriction;
• suspension;

subject to applicable law.

34.16 Payment disputes between Client and provider

Where a dispute concerns the underlying drone service, DroneJob may provide records or dispute-support functionality but does not automatically become financially responsible for the provider's performance unless separate terms state otherwise.

35.1 External communications

Users may exchange personal contact information and communicate directly.

DroneJob generally cannot preserve communications that do not pass through DroneJob-controlled channels.

35.2 External contracts

Clients and providers may enter into contracts outside DroneJob.

If the relationship is later managed through DroneJob, the external agreement may continue to govern the underlying services.

35.3 Independently acquired Clients

A Pilot/DSP may use DroneJob productivity tools for Clients obtained independently of the DroneJob Marketplace.

Those relationships do not automatically become DroneJob-originated marketplace relationships.

35.4 Loss of platform records or protections

Moving activity outside DroneJob may reduce or eliminate features such as:

• Conversation history;
• audit records;
• payment history;
• change-order history;
• dispute evidence;
• workflow automation;
• AI context;
• delivery records;
• platform payment protection where offered.

35.5 Off-platform payments

Where Users choose or are permitted to pay outside DroneJob, DroneJob may have no visibility into:

• amount;
• payment status;
• refund;
• chargeback.

DroneJob should not represent such transactions as protected or verified.

35.6 Consent and privacy

If a User contacts another person outside DroneJob, the User remains responsible for:

• privacy;
• communication consent;
• applicable marketing law;
• confidentiality.

35.7 Enterprise required workflows

An Enterprise Customer may require its personnel/vendors to use approved DroneJob workflows for:

• audit;
• compliance;
• security;
• procurement;
• recordkeeping.

That requirement arises from the applicable Organization policy or agreement.

35.8 Public-sector approved channels

A public-sector Customer may require communications, approvals or records to remain within approved systems for:

• public-records compliance;
• audit;
• procurement;
• security;
• retention.

Users participating in such a program must follow the applicable Customer requirements.

35.9 No circumvention fee unless separately established

This Section does not create:

• marketplace exclusivity;
• mandatory commission;
• anti-circumvention charge;
• conversion fee.

If DroneJob later adopts such a marketplace policy, it must be:

• clearly disclosed;
• commercially approved;
• incorporated through applicable Terms or Marketplace Additional Terms.

35.10 Security warning

Users should exercise care before moving sensitive:

• Client information;
• infrastructure information;
• Mission files;
• credentials;
• enterprise records;

to personal email, personal storage or other uncontrolled systems.

36.1 Unlawful and unsafe operations

Users must not use DroneJob to violate law, facilitate illegal conduct, or knowingly support unauthorized, unsafe or unlawful drone operations.

DroneJob tools must not be used to make an unlawful operation appear compliant.

36.2 Fraud, abuse and privacy

Users must not falsify credentials, impersonate another person or Organization, commit fraud, harass others, or use DroneJob for unlawful surveillance or unauthorized disclosure of personal information.

36.3 Security, APIs and unauthorized testing

Users must not:

• bypass authentication or tenant isolation;
• circumvent API limits;
• share API credentials improperly;
• scrape restricted information outside approved APIs;
• conduct penetration testing, vulnerability scanning or denial-of-service testing against DroneJob without written authorization.

36.4 AI, automation and messaging

Users must not use DroneJob AI Features to:

• bypass security;
• bypass human approval required by DroneJob;
• falsify credentials or records;
• create deceptive compliance representations.

Users must not configure AI or automation to intentionally bypass a required human:

• go/no-go decision;
• safety approval;
• compliance override;
• regulatory approval.

Users must not represent AI Output as FAA approval or another regulated professional determination unless that process has independently occurred.

Messaging use remains subject to Sections 23–25.

36.5 Restricted government information

Users must not submit classified information, CUI requiring an unsupported authorization, or other government data that the contracted environment does not support.

36.6 Enforcement

DroneJob may investigate suspected violations and may warn, restrict, suspend or terminate access as described in the Acceptable Use Policy and Section 39.

37.1 Account security

Users must protect:

• passwords;
• authentication factors;
• recovery methods;
• devices used to access DroneJob.

Users must promptly report suspected unauthorized access.

37.2 Multi-factor authentication

Where DroneJob requires MFA, Users must not:

• disable;
• circumvent;
• share;

authentication factors in a manner intended to defeat the control.

Organizations should use available MFA and SSO capabilities consistent with their risk.

37.3 Organization access

Organizations are responsible for:

• assigning appropriate roles;
• limiting administrator access;
• removing departed Users;
• reviewing external contractor access;
• protecting sensitive Organization information.

37.4 Principle of least privilege

Customers should grant Users and systems only the access reasonably necessary for their responsibilities.

This is particularly important for:

• Enterprise administrators;
• APIs;
• contractors;
• Integrations;
• AI Actions.

37.5 API credentials

Customers must secure:

• API keys;
• OAuth credentials;
• webhook secrets;
• certificates;
• tokens.

Credentials should not be:

• committed to public repositories;
• embedded in publicly distributed code;
• shared through insecure communications.

37.6 Webhook security

Customers receiving DroneJob webhooks should use supported validation mechanisms.

Customers should design webhook consumers to address:

• duplicate events;
• replay risk;
• unauthorized senders;
• credential rotation.

37.7 Connected systems

Customers are responsible for security of systems they connect to DroneJob.

A compromised Customer system may create risk even if DroneJob itself has not been compromised.

37.8 Exported data

After Customer Data is:

• exported;
• downloaded;
• transmitted to an external system;

the Customer is responsible for protecting copies under its control.

37.9 Devices

Users accessing sensitive Client or Enterprise information should use devices appropriate for that information.

Users should consider:

• screen lock;
• operating-system updates;
• malware protection;
• device encryption;
• remote-wipe controls;

where appropriate.

37.10 Communications

Users should not send:

• passwords;
• API secrets;
• highly sensitive credentials;

through ordinary DroneJob messaging unless the communication method is specifically designed for such secrets.

37.11 AI permissions

Organizations should carefully configure AI access to:

• Customer Data;
• Client Data;
• communications;
• files;
• actions.

An AI Feature should not receive broad access merely for convenience where narrower access is sufficient.

37.12 External AI services

Customers connecting external AI providers are responsible for evaluating:

• security;
• retention;
• training practices;
• data residency;
• contractual terms.

37.13 Security incidents

Customers must promptly notify DroneJob if they become aware that:

• DroneJob credentials were compromised;
• API credentials were exposed;
• an Integration is being abused;
• unauthorized DroneJob access occurred.

37.14 Public-sector security

Public Sector Customers are responsible for identifying applicable:

• data classification;
• security requirements;
• residency requirements;
• procurement restrictions;

before placing regulated data in DroneJob.

DroneJob is responsible only for security commitments expressly applicable to the contracted environment.

37.15 No unsupported certification assumption

The presence of:

• encryption;
• SSO;
• logging;
• data residency;

does not mean a DroneJob environment holds:

• FedRAMP;
• CMMC;
• FISMA authorization;
• another certification;

unless DroneJob expressly identifies it as such.

38.1 Standard Service availability

Unless a separate SLA expressly provides otherwise, DroneJob will use commercially reasonable efforts to operate purchased production Services.

This general Terms page does not create a specific uptime percentage.

38.2 Planned maintenance

DroneJob may perform planned maintenance.

Where commercially reasonable, DroneJob may provide advance notice of material planned downtime affecting production Services.

38.3 Emergency maintenance

DroneJob may perform emergency maintenance without advance notice where necessary to:

• protect security;
• prevent data loss;
• restore functionality;
• respond to infrastructure failures.

38.4 External dependencies

Availability may be affected by systems outside DroneJob's reasonable control, including:

• Internet providers;
• cloud infrastructure;
• carriers;
• email providers;
• payment processors;
• AI providers;
• Third-Party Services;
• aviation/weather sources;
• Customer systems.

38.5 Mobile and field connectivity

Drone operations may occur in locations with limited:

• mobile connectivity;
• GPS availability;
• Internet service.

Users should not rely on constant connectivity unless a particular feature expressly supports an offline workflow.

38.6 No emergency-service reliance

DroneJob is not intended to function as:

• emergency dispatch;
• life-safety communication;
• aviation traffic control;
• emergency navigation.

Users should maintain appropriate independent emergency procedures.

38.7 Enterprise Service Level Agreements

Enterprise Customers may purchase or negotiate specific SLAs covering matters such as:

• uptime;
• support response;
• recovery objectives;
• incident communication.

An SLA applies only where incorporated into an applicable:

• Order Form;
• Enterprise Agreement;
• SLA exhibit.

38.8 Public-sector SLAs

Public Sector Customers may require:

• service availability;
• response times;
• maintenance windows;
• escalation procedures.

Those commitments apply only where expressly accepted by DroneJob.

38.9 Beta, Preview and Early Access Services

DroneJob may offer functionality designated as:

• alpha;
• beta;
• preview;
• pilot;
• experimental;
• early access;
• developer preview;
• evaluation.

We refer to these as "Beta Services."

38.10 Optional participation

Unless expressly required by a separate agreement, participation in Beta Services is voluntary.

38.11 Beta limitations

Beta Services may:

• contain errors;
• be incomplete;
• change materially;
• be unavailable;
• lose data;
• operate differently from documentation;
• never become generally available.

38.12 Beta production use

Users should not rely on Beta Services for:

• safety-critical operations;
• required regulatory compliance;
• emergency use;
• irreversible business processes;

unless DroneJob expressly states that the applicable Beta Service is appropriate for that use.

38.13 Beta warranty

To the fullest extent permitted by law and unless Additional Terms provide otherwise, Beta Services are provided:

"as is" and "as available."

They are not subject to standard production SLA commitments.

38.14 Beta confidentiality

A private Beta may be designated DroneJob Confidential Information.

Participants must respect applicable confidentiality requirements.

38.15 Beta feedback

DroneJob may request feedback concerning Beta Services.

Feedback remains subject to Section 40.

38.16 Discontinuation

DroneJob may:

• modify;
• discontinue;
• replace;

a Beta Service.

Participation in a Beta does not guarantee commercial release.

38.17 Product roadmap

Purchases are based on Services and contractual commitments actually available or expressly included in the applicable agreement.

Unless expressly stated in a signed agreement, a purchase is not contingent upon:

• roadmap;
• future AI feature;
• future Integration;
• announced functionality.

39.1 User account closure

A User may stop using DroneJob.

Where available, Account closure may be initiated through:

• Account settings;
• support;
• another approved method.

Closing an Account does not automatically eliminate:

• accrued payment obligations;
• Organization records;
• legally required records;
• Mission history;
• records subject to retention obligations.

39.2 Subscription cancellation

Paid subscription cancellation is governed by:

• applicable plan;
• checkout terms;
• Order Form;
• Enterprise Agreement.

Cancellation of renewal does not necessarily mean immediate termination of access before the end of the paid term.

39.3 Suspension for security

DroneJob may suspend access where reasonably necessary because of:

• suspected compromise;
• security threat;
• malicious activity;
• risk to other Customers.

39.4 Suspension for AUP violation

DroneJob may suspend access or specific features for material violation of Section 36.

39.5 Messaging suspension

DroneJob may restrict messaging where required because of:

• spam;
• consent violations;
• carrier restrictions;
• telecommunications rules;
• provider requirements.

39.6 Integration suspension

DroneJob may revoke or restrict Integration credentials where necessary because of:

• compromise;
• API abuse;
• security;
• material Terms violation.

39.7 Suspension for nonpayment

Where permitted by applicable agreement and law, DroneJob may suspend paid Services for overdue undisputed fees after applicable notice.

Enterprise or Public Sector agreements may provide different procedures.

39.8 Legal suspension

DroneJob may restrict Services where required by:

• law;
• court order;
• regulator;
• sanctions;
• governmental requirement.

39.9 Notice and cure

For ordinary curable commercial breaches, DroneJob should generally attempt to provide:

• notice;
• reasonable opportunity to cure;

where commercially appropriate.

Immediate action may be taken where delay could create material:

• security;
• legal;
• safety;
• fraud;
• abuse;

risk.

39.10 Termination for material breach

DroneJob or a Customer may have termination rights for material breach under applicable:

• Terms;
• Order Form;
• Enterprise Agreement.

Enterprise agreements may define:

• notice;
• cure periods;
• refunds;
• termination consequences.

39.11 Organization User removal

An Organization may remove an Authorized User.

Removal may terminate the User's access to:

• Organization Clients;
• Missions;
• files;
• Conversations;
• audit records.

It does not automatically require deletion of the Organization's business records.

39.12 Data export before termination

Customers should export important business information before access ends where applicable export tools are available.

DroneJob should not promise a universal post-termination export window unless the relevant functionality and operational process actually support it.

39.13 Enterprise export period

Enterprise Agreements may provide a defined post-termination period for Customer Data export.

Recommended future standard once operationally supported:

30 days

unless a different period is negotiated.

This recommendation is not a binding general commitment unless DroneJob confirms the capability.

39.14 Public-sector export

Public Sector contracts may require:

• structured export;
• records transfer;
• archival delivery;
• transition assistance.

Such commitments apply only where expressly accepted.

39.15 Data deletion

After applicable retention/export periods, DroneJob may delete Customer Data subject to:

• Privacy Policy;
• DPA;
• legal obligations;
• backup cycles;
• public-sector retention;
• legal hold.

39.16 Backups

Deleted Customer Data may remain in protected backups until applicable backup cycles expire.

39.17 Telephone numbers and messaging addresses

Upon termination:

• DroneJob-provided numbers may be reclaimed;
• mappings may terminate;
• communication relay may stop.

Users do not acquire a right to continue using those identifiers unless expressly agreed.

39.18 API access

Termination may revoke:

• API keys;
• OAuth credentials;
• webhook delivery;
• Integration access.

39.19 AI context

Termination or deletion may affect:

• AI history;
• generated context;
• saved assistant state;
• AI-related records.

Retention remains subject to the Privacy Policy.

39.20 Outstanding payment obligations

Termination does not eliminate amounts properly accrued before termination.

39.21 Survival

Provisions that by their nature should survive may include:

• accrued payment obligations;
• intellectual property;
• confidentiality;
• disclaimers;
• limitations of liability;
• indemnification;
• dispute provisions;
• other terms intended to survive.

40.1 DroneJob technology

DroneJob's intellectual property may include:

• software;
• source code;
• object code;
• platform architecture;
• APIs;
• interfaces;
• workflow designs;
• databases and schemas;
• documentation;
• templates;
• visual designs;
• trademarks;
• logos;
• branding;
• proprietary content;
• AI orchestration technology.

40.2 Limited right to use Services

Subject to compliance with these Terms, DroneJob grants the User a limited:

• non-exclusive;
• non-transferable except as expressly permitted;
• revocable;
• non-sublicensable except where authorized;

right to access and use the Services during the applicable entitlement period.

The right is limited to permitted use of DroneJob.

It does not transfer ownership.

40.3 Customer Data

Ownership and licensing of Customer Data remains governed by Section 26.

40.4 Mission deliverables

Rights between Clients and service providers remain governed by Section 27 and their applicable service agreement.

40.5 DroneJob trademarks

Users must not use:

• DroneJob;
• DroneJob.ai;
• DroneJob.org;
• DroneJob logos;
• other DroneJob marks;

in a way that falsely suggests:

• endorsement;
• partnership;
• employment;
• authorization.

40.6 Permitted brand use

DroneJob may publish brand-use guidelines.

A User may be allowed to use approved DroneJob badges or marks for purposes such as:

• profile verification;
• partner participation;
• approved program membership.

Use must follow applicable guidelines.

40.7 Verification badges

A DroneJob verification badge remains a DroneJob platform indicator.

Users must not:

• alter it;
• create counterfeit badges;
• continue displaying a revoked badge in a misleading manner.

40.8 Customer names and logos

DroneJob should not automatically assume a right to publicly use an Enterprise or Public Sector Customer's name or logo for marketing merely because that Customer uses the Services.

Public use should require:

• permission;
• applicable Order Form authorization;
• another valid agreement.

This is particularly important for:

• government agencies;
• public utilities;
• enterprise customers;
• security-sensitive organizations.

40.9 Feedback

Users may voluntarily provide:

• suggestions;
• ideas;
• comments;
• feature requests;
• feedback.

DroneJob may use non-confidential Feedback to:

• develop;
• improve;
• operate;

the Services without an obligation to compensate the contributor.

40.10 Feedback does not transfer Customer confidential information

A Feedback provision does not authorize DroneJob to use:

• Customer Confidential Information;
• private Mission data;
• proprietary Client files;

as general product Feedback.

40.11 Open-source software

Parts of the Services may contain open-source software governed by separate open-source licenses.

Applicable open-source licenses control where they grant rights inconsistent with these Terms.

40.12 Third-party content

Third-party content remains owned by the applicable third party and may be subject to its own terms.

41.1 Platform technology

DroneJob does not warrant that:

• every Service will be uninterrupted;
• every error will be corrected;
• every feature will always remain available;
• every Integration will continue operating.

41.2 Marketplace participants

DroneJob does not guarantee:

• identity beyond the scope actually verified;
• competence;
• quality;
• honesty;
• safety;
• financial condition;
• performance;

of marketplace participants.

41.3 Underlying drone services

DroneJob is not generally the provider of independent Pilot/DSP drone services.

DroneJob does not warrant the quality or result of such services merely because they were:

• found;
• scheduled;
• managed;
• paid for;

through DroneJob.

41.4 Earnings and business results

DroneJob does not guarantee:

• leads;
• jobs;
• revenue;
• earnings;
• marketplace demand;
• ROI.

41.5 Regulatory information

DroneJob may assist with:

• aviation information;
• compliance tracking;
• credentials;
• airspace;
• planning.

DroneJob does not guarantee that an operation is legally authorized.

41.6 Weather and airspace

Weather, maps, airspace and related data may:

• be delayed;
• contain errors;
• change rapidly.

The responsible operator must verify material operational information.

41.7 AI

AI Output may:

• be inaccurate;
• be incomplete;
• contain errors;
• resemble third-party material;
• require professional review.

AI is not a substitute for the responsible human decision-maker.

41.8 Automation

Automated workflows may:

• fail;
• duplicate;
• delay;
• act on incorrect data.

Users remain responsible for appropriate configuration and oversight.

41.9 No legal advice

DroneJob does not provide legal advice through:

• templates;
• AI;
• compliance assistance;
• contract tools.

41.10 No accounting or tax advice

DroneJob financial/productivity tools do not constitute:

• accounting;
• tax;
• financial advice.

41.11 No engineering or surveying advice

DroneJob tools do not convert a User or output into a:

• licensed engineer;
• licensed surveyor;
• other regulated professional.

41.12 No insurance advice

Insurance-status information does not determine whether coverage applies to a particular incident.

41.13 Third-Party Services

DroneJob makes no warranty regarding independent Third-Party Services except where expressly stated.

41.14 Communications delivery

DroneJob does not guarantee delivery of every:

• SMS;
• email;
• push notification;
• webhook;
• other communication.

41.15 Beta Services

Beta Services remain subject to the enhanced limitations in Section 38.

41.16 Public-sector use

Availability of DroneJob to a governmental Customer does not constitute:

• procurement authorization;
• statutory approval;
• security accreditation;
• FedRAMP authorization;

unless expressly documented.

41.17 Mandatory legal rights

Nothing in these disclaimers excludes:

• warranties;
• remedies;
• rights;

that applicable law prohibits DroneJob from excluding.

42.1 Exclusion of certain damages

To the fullest extent permitted by applicable law, DroneJob and its:

• affiliates;
• officers;
• directors;
• employees;
• agents;
• service providers;

will not be liable for indirect, incidental, special, exemplary, punitive or consequential damages arising out of or relating to the Services.

This may include, where permitted:

• lost profits;
• lost revenue;
• lost business opportunity;
• business interruption;
• loss of goodwill;
• loss of anticipated savings.

42.2 Data-related losses

To the fullest extent permitted by law and except where expressly provided in an applicable agreement, DroneJob will not be liable for indirect or consequential loss resulting from:

• Customer configuration;
• Customer deletion;
• external Integration;
• Third-Party Service;
• User error;
• activity outside DroneJob's control.

This subsection must not be drafted to disclaim responsibility DroneJob legally cannot disclaim for its own conduct.

42.3 Underlying service-provider conduct

DroneJob is not responsible for damages caused solely by:

• Pilot;
• DSP;
• Client;
• other marketplace participant;

in performing or failing to perform an underlying drone-service agreement, except to the extent DroneJob independently has liability under applicable law or an express agreement.

42.4 Recommended aggregate liability cap

Recommended default commercial structure:

To the fullest extent permitted by law, DroneJob's aggregate liability arising out of or relating to the Services will not exceed the greater of:

(A) the fees actually paid to DroneJob for the Services giving rise to the claim during the twelve months immediately preceding the event giving rise to liability; or

(B) USD $100 if no applicable fees were paid.

This is a recommended working position comparable to common SaaS structures.

Do not silently change:

• 12 months;
• $100;
• fees giving rise to the claim;

without legal/business approval.

42.5 Enterprise caps

An Enterprise Agreement may establish:

• different cap;
• higher cap;
• super-cap;
• separate security/privacy cap;
• other negotiated risk allocation.

The Enterprise Agreement controls where applicable.

42.6 Public-sector limitations

A Public Sector agreement may require limitations appropriate to:

• sovereign-immunity rules;
• appropriations law;
• procurement law;
• statutory limitations.

Nothing in these general Terms requires a governmental entity to waive a legal immunity it cannot lawfully waive.

42.7 Excluded limitations

Nothing in these Terms limits liability where applicable law prohibits limitation.

Depending on law and applicable agreement, this may include liability relating to matters such as:

• fraud;
• willful misconduct;
• certain personal injury;
• other legally non-limitable obligations.

Do not invent a universal carve-out list where jurisdiction-specific law differs.

42.8 Consumer protections

If a User has non-waivable consumer rights, those rights remain.

42.9 Essential allocation

The limitations in this Section are intended to allocate risk between DroneJob and Users and form part of the basis on which the Services are provided and priced.

43.1 User indemnification

To the extent permitted by applicable law, a User or Customer agrees to defend, indemnify and hold harmless DroneJob and its affiliates, officers, employees and agents from third-party claims arising out of or relating to:

• unlawful use of DroneJob;
• material violation of these Terms;
• User Content or Customer Data for which the User lacked appropriate rights;
• violation of another person's intellectual-property rights;
• violation of privacy or confidentiality obligations;
• underlying drone services performed by the User;
• unsafe or unlawful Mission conduct;
• communications sent by the User in violation of law;
• Customer-selected Third-Party Services or Integrations;
• misuse of AI or automation by the Customer.

43.2 Marketplace disputes

User indemnification may include qualifying third-party claims arising from an underlying dispute between:

• Client;
• Pilot;
• DSP;

where the claim results from the indemnifying User's own:

• acts;
• omissions;
• services;
• representations;

rather than DroneJob's independent misconduct.

43.3 Mission operations

A Pilot/DSP remains responsible for third-party claims arising from the Pilot/DSP's performance of drone services to the extent provided by applicable law and the underlying agreement.

43.4 Customer Data

Customers are responsible for third-party claims arising from Customer Data where the claim results from the Customer's lack of:

• rights;
• authority;
• required notice;
• required consent.

43.5 Defense procedures

DroneJob should provide reasonable notice of a qualifying claim.

The indemnifying party should receive appropriate control of the defense subject to:

• cooperation;
• reasonable settlement restrictions.

No settlement may impose:

• admission;
• obligation;
• liability;

on a protected party without that party's appropriate consent.

43.6 DroneJob conduct

A User is not required under this Section to indemnify DroneJob for a claim to the extent caused by DroneJob's own conduct where applicable law or an applicable agreement allocates that responsibility to DroneJob.

43.7 Enterprise mutual indemnity

The general public Terms do not create a broad DroneJob IP-indemnification obligation for every free or self-service User.

DroneJob should instead provide an appropriate mutual enterprise indemnification framework through:

• Enterprise Agreement;
• MSA;
• applicable Order Form.

Recommended enterprise structure should later evaluate:

DroneJob indemnification

Third-party claims alleging that purchased DroneJob technology infringes specified intellectual-property rights.

Customer indemnification

Third-party claims involving:

• Customer Data;
• Customer integrations;
• Customer misuse;
• underlying services.

Do not implement a separate Enterprise MSA in this task.

43.8 Government/public-sector entities

A governmental entity's indemnification obligations apply only to the extent:

• permitted by applicable law;
• validly authorized;
• expressly accepted in the applicable Public Sector agreement.

This Section does not require a Public Sector Customer to provide indemnification that applicable law prohibits.

44.1 Recommended approach for current DroneJob stage

This working implementation does not introduce mandatory arbitration or a class-action waiver unless specifically approved by legal counsel.

Reasons include:

• DroneJob has individual Users;
• Enterprise Customers;
• international Customers;
• public-sector Customers;
• government entities may be legally unable to accept arbitration provisions;
• different consumer laws may affect enforceability.

For the current working Terms, the recommended approach is a conventional court-based dispute structure.

44.2 Informal dispute resolution

Before filing a formal legal action, the parties should attempt in good faith to resolve a dispute through reasonable written notice and discussion, except where:

• urgent injunctive relief;
• security;
• intellectual property;
• legal deadline;

makes informal resolution impractical.

Recommended informal period:

30 days after receipt of sufficiently detailed dispute notice.

44.3 Recommended governing law

Because DroneJob LLC is organized under Delaware law, the recommended baseline is:

Except where applicable law or applicable Additional Terms require otherwise, these Terms and disputes arising from them are governed by the laws of the State of Delaware, without regard to conflict-of-law principles.

This recommendation requires final approval before deployment.

44.4 Recommended venue

Recommended baseline:

Subject to applicable law and applicable Additional Terms, state and federal courts located in Delaware will have jurisdiction over disputes arising from these Terms.

Before production, counsel should decide whether to specify:

• New Castle County;
• another Delaware venue;
• another principal-business jurisdiction.

No county is selected by these working Terms without approval.

44.5 Public-sector exception

A governmental Customer may be legally required to use:

• its own governing law;
• statutory claims process;
• government board;
• court;
• venue.

An applicable Public Sector Addendum or negotiated agreement may supersede this Section.

44.6 Consumer rights

Nothing in this Section eliminates mandatory rights concerning:

• jurisdiction;
• venue;
• consumer law;

that cannot legally be waived.

44.7 International Customers

International Enterprise agreements may establish a different:

• governing law;
• venue;
• dispute mechanism.

44.8 No arbitration assumption

These Terms do not add AAA or JAMS arbitration, a class-action waiver or a jury-trial waiver without an explicit subsequent legal and business decision.

45.1 Entire agreement

These Terms, together with applicable Additional Terms, constitute the agreement governing the relevant Services.

45.2 Order of precedence

The order-of-precedence rules in Section 1 continue to apply.

A signed:

• Enterprise Agreement;
• Public Sector Addendum;
• DPA;
• Order Form;
• Security Exhibit;
• SLA;

may control applicable subject matter where expressly provided.

45.3 Purchase orders

A purchase order submitted by a Customer does not automatically amend these Terms.

Additional or conflicting purchase-order terms bind DroneJob only where:

• expressly accepted by DroneJob;
• incorporated into an executed agreement.

Public-sector procurement documents may be treated differently where expressly accepted.

45.4 Assignment

A User may not assign these Terms without DroneJob's consent except where an applicable agreement permits.

DroneJob may assign the agreement in connection with:

• merger;
• acquisition;
• corporate reorganization;
• sale of substantially all relevant assets;

subject to applicable law and existing Enterprise commitments.

Enterprise Agreements may contain different assignment terms.

45.5 No partnership or agency

Nothing in these Terms creates a:

• partnership;
• joint venture;
• fiduciary relationship;
• agency;
• employment relationship;

except where separately established by an applicable written agreement.

45.6 Third-party beneficiaries

Unless expressly stated otherwise, these Terms do not create rights for unrelated third-party beneficiaries.

45.7 Waiver

Failure to enforce a provision does not automatically waive the right to enforce that provision later.

45.8 Severability

If a provision is determined unenforceable, the remaining provisions remain effective to the extent legally possible.

45.9 Force majeure

Neither party should be responsible for failure or delay caused by events beyond its reasonable control to the extent permitted by law.

Examples may include:

• natural disaster;
• widespread infrastructure failure;
• war;
• civil disturbance;
• governmental action;
• pandemic;
• labor disruption;
• major Internet/provider failure.

Force majeure generally does not excuse payment obligations already due.

45.10 Export controls and sanctions

DroneJob software and technology may be subject to:

• U.S. export laws;
• sanctions;
• other trade restrictions.

Users must not use, export or provide access to DroneJob in violation of applicable export-control or sanctions law.

45.11 Restricted parties

Users must not knowingly use DroneJob in a manner prohibited by applicable denied-party or sanctions restrictions.

Do not publish a static list of sanctioned countries because legal restrictions change.

45.12 Anti-corruption

Users must not use DroneJob to facilitate:

• bribery;
• kickbacks;
• unlawful payments;
• corruption.

This is particularly important for:

• enterprise procurement;
• public-sector procurement;
• vendor programs.

45.13 Electronic communications

The parties may use legally valid electronic methods for:

• agreements;
• notices;
• approvals;
• signatures;

where applicable law permits.

45.14 Electronic signatures

Where DroneJob provides electronic acceptance/signature functionality, the parties agree that electronic actions may have legal effect where applicable law recognizes them.

This does not create contracting authority where a person otherwise lacks authority.

45.15 Notices

Operational notices may be provided through:

• Account;
• email;
• website;
• other appropriate electronic methods.

Formal legal notices may be subject to different requirements in an:

• Enterprise Agreement;
• Order Form;
• Public Sector Addendum.

45.16 English language

The controlling version of these Terms is the English version unless an applicable signed agreement states otherwise.

DroneJob may provide translations for convenience.

These Terms do not state that support is English-only unless that is the actual support policy.

45.17 Headings

Headings are for convenience and do not alter interpretation.

45.18 No reliance on roadmap

The product-roadmap limitation in Sections 9 and 38 continues to apply.

45.19 Public-sector procurement

Public-sector Customers may be subject to mandatory:

• procurement;
• statutory;
• sovereign-immunity;
• public-records;
• appropriations;

requirements.

Such mandatory requirements apply to the extent required by law or expressly incorporated into an applicable agreement.

DroneJob's general Terms should not attempt to pre-write every government contracting clause.

46.1 Effective Date

The Terms must display the current Effective Date near the top.

46.2 Notice of changes

DroneJob may provide notice of updated Terms through:

• website;
• Account;
• email;
• in-product notice;
• other legally appropriate method.

46.3 Material changes

Where applicable law requires additional notice or affirmative acceptance for a material change, DroneJob will use the required process.

46.4 Existing Enterprise agreements

A unilateral change to these general Terms does not automatically override conflicting provisions in an active signed:

• Enterprise Agreement;
• Public Sector Agreement;
• Order Form;
• DPA;
• SLA;
• Security Exhibit.

46.5 Renewal-based terms

An Enterprise or Public Sector agreement may provide that updated standard terms apply only:

• on renewal;
• through a new Order Form;
• following agreed notice.

Those contractual rules control.

46.6 Continued use

Where legally valid and where no separate agreement provides otherwise, continued use after the effective date of updated Terms may constitute acceptance.

Do not rely on continued use where applicable law requires affirmative consent.

46.7 Material new product terms

DroneJob may require separate acceptance before a User gains access to:

• new payment functionality;
• marketplace programs;
• API/developer programs;
• new AI capabilities;
• regulated or specialized Services.

46.8 Prior versions

DroneJob should eventually make material prior versions accessible for reference.

A version archive is not built by this Terms implementation unless one already exists.

47.1 Support questions

Routine questions regarding:

• Account;
• billing;
• features;
• Services;

should use DroneJob's published support channels.

47.2 Legal notices

Enterprise and Public Sector agreements may specify a particular method for formal legal notice.

Where such a method exists, that method controls.

47.3 Privacy

Privacy questions should be handled according to: https://www.dronejob.ai/privacy.

47.4 Security reports

Security vulnerabilities should not be routed through a legal address if DroneJob has a dedicated security process.

If no security process currently exists, these Terms do not invent one.

A future Vulnerability Disclosure Policy should define the appropriate channel.