Privacy Policy

1.1 Services covered by this Privacy Policy

This Privacy Policy applies to personal information processed through or in connection with DroneJob services that reference this Policy, including, as applicable:

• the public DroneJob website at https://www.dronejob.ai;
• DroneJob web and mobile applications, marketplace, profile, productivity, Mission, billing and AI-assisted features;
• communications provided through DroneJob, including SMS, email and in-app communications;
• APIs, webhooks and other enterprise or partner integrations;
• marketing websites, forms and campaigns that link to this Privacy Policy; and
• other DroneJob services that expressly reference this Privacy Policy.

We refer to these collectively as the "Services."

1.2 DroneJob LLC

DroneJob LLC is a Delaware limited liability company.

Where this Privacy Policy states that DroneJob determines why and how personal information is processed, DroneJob LLC is generally the entity responsible for that processing, subject to applicable law and any separate agreement governing the relevant Services.

Enterprise customers or other organizations may also enter into separate agreements with DroneJob, including order forms, enterprise agreements, data processing addenda, security exhibits or integration agreements.

Those agreements may contain additional privacy and data-processing terms.

If a separate written agreement expressly governs the processing of particular information and conflicts with this Privacy Policy, the applicable contractual terms will govern that processing to the extent provided in that agreement and permitted by law.

1.3 A multi-sided platform

DroneJob is a multi-sided platform.

Information may move between different participants when necessary to provide a service that a user has requested.

For example:

• a prospective client may provide information to contact a pilot;
• a pilot may share professional profile information with prospective clients;
• a client and pilot may communicate through a DroneJob-managed conversation;
• a drone service provider may assign a mission to a member of its team;
• an enterprise customer may create orders or missions and make relevant information available to selected pilots or vendors;
• an organization administrator may configure users, permissions and workflows;
• an authorized enterprise system may create or update DroneJob records through an integration.

The fact that information is processed through DroneJob does not necessarily mean that all information is public or available to all DroneJob users.

Access depends on the feature, account type, organization, authorization, privacy setting and business relationship involved.

1.4 Public and private information

Some DroneJob functionality is intentionally public.

For example, a pilot may choose to publish approved portions of a professional profile or portfolio so prospective clients can evaluate their services.

Other information is designed to remain private, organization-restricted or limited to authorized project participants.

Examples may include:

• private client information;
• CRM records;
• internal pricing notes;
• financial information;
• compliance documents;
• insurance documents;
• raw mission data;
• private deliverables;
• enterprise operational information;
• internal communications;
• audit information; and
• security settings.

DroneJob's Services are designed to distinguish public information from governed or restricted information.

More information about public profiles and visibility controls will appear in Section 22.

1.5 International scope

DroneJob is a United States company and is being developed for use by customers and users in multiple jurisdictions.

The Services may be accessed from the United States, Canada, Latin America, Europe and other supported markets as DroneJob expands.

Privacy rights and DroneJob's legal obligations may therefore vary depending on:

• where the individual is located;
• where the relevant organization is established;
• the nature of the Services;
• the nature of the information;
• the relationship between DroneJob and the customer; and
• applicable privacy and data-protection laws.

Sections 21, 30 and 31 will provide additional information about legal bases, international transfers and privacy rights.

Certain Enterprise or Public Sector Customers may purchase or negotiate specific data-residency, data-sovereignty, security or international-transfer commitments. Where DroneJob expressly agrees to such commitments in an Order Form, Data Processing Addendum, security exhibit or other written agreement, those terms govern the covered processing to the extent stated in that agreement.

2.1 When DroneJob determines how personal information is used

DroneJob generally acts as a controller, business or similar responsible entity when we determine the purposes and essential means of processing personal information for DroneJob's own platform and business operations.

Examples may include processing information to:

• register and authenticate users;
• maintain DroneJob accounts;
• operate public professional profiles;
• administer the DroneJob marketplace and directory;
• manage DroneJob subscriptions and entitlements;
• prevent fraud, abuse and security incidents;
• enforce DroneJob policies;
• administer verification programs;
• operate reviews, reputation and trust features;
• provide DroneJob-originated service notifications;
• respond to support requests;
• administer marketing and product communications;
• analyze use of the Services;
• improve DroneJob products and platform reliability;
• maintain security, audit and operational records;
• comply with legal obligations; and
• establish, exercise or defend legal rights.

In these situations, DroneJob generally determines why the information is processed and how the relevant DroneJob functionality operates.

2.2 When DroneJob processes Customer Data on behalf of a business or enterprise customer

DroneJob also provides productivity, workflow, collaboration and integration functionality through which a business or enterprise customer may provide or connect information concerning its own:

• customers;
• prospects;
• employees;
• pilots;
• contractors;
• vendors;
• contacts;
• project stakeholders;
• work orders;
• mission participants; or
• other individuals.

For example, a drone service provider may use DroneJob's CRM tools to maintain information about its customers, or an enterprise customer may connect an internal work-order system to DroneJob so that mission information is created and managed through an API.

Where DroneJob processes such information solely on the documented instructions of the business or enterprise customer in order to provide contracted Services, DroneJob may act as a processor, service provider or similar entity on behalf of that customer.

We refer to information processed in this capacity generally as "Customer Data."

The applicable customer is responsible for determining whether it has the legal authority to collect, provide, use and instruct DroneJob to process Customer Data.

Where required, processing of Customer Data may be governed by a Data Processing Addendum ("DPA") or other written agreement between DroneJob and the customer.

Customer Data may be processed through productivity functionality, Integrations, automated workflows and AI Features where necessary to provide Services requested or configured by the Customer.

Public-sector organizations may also act as Controllers for Customer Data supplied to DroneJob. No separate privacy classification is created merely because the Customer is a government entity.

2.3 DroneJob's responsibilities can differ within the same customer relationship

DroneJob may act in different privacy roles for different categories of information within the same account.

For example, an enterprise may provide its customer contact information to DroneJob for mission processing.

DroneJob may process that contact information on the enterprise's instructions.

At the same time, DroneJob may independently process:

• the enterprise administrator's DroneJob account information;
• security logs;
• billing information;
• fraud-prevention records;
• product-usage information; or
• records required to enforce DroneJob's contractual terms.

Those processing activities may be performed for DroneJob's own legitimate business, security or legal purposes rather than solely on the enterprise customer's instructions.

2.4 Marketplace interactions

When clients, pilots, DSPs or other marketplace participants use DroneJob to find one another or interact, DroneJob processes information necessary to provide the marketplace and associated platform features.

Depending on the interaction, information may include:

• public profile information;
• service requirements;
• client inquiries;
• mission information;
• reviews;
• communications;
• credentials or verification status;
• scheduling information; and
• transaction information.

DroneJob may determine aspects of this processing in order to operate, secure and govern the marketplace.

At the same time, once one marketplace participant receives another person's information for an independent business purpose, that participant may have its own privacy obligations regarding how it subsequently uses that information.

For example, a drone pilot who receives a prospective client's contact information may independently become responsible for how the pilot uses that information outside the scope of DroneJob's instructions or Services.

Users may not use information obtained through DroneJob for unlawful purposes, unauthorized marketing or purposes inconsistent with the circumstances in which the information was provided.

2.5 Enterprise administrators

Organizations using DroneJob may appoint administrators who control organization-level settings and user access.

Depending on the organization's configuration, administrators may be authorized to:

• invite or remove users;
• assign roles;
• configure permissions;
• access organization-scoped records;
• manage vendor or pilot rosters;
• configure integrations;
• review mission and workflow data;
• access organization audit information;
• configure retention or security settings where available.

The organization—not DroneJob—generally determines which individuals within that organization receive those organizational permissions.

DroneJob enforces the technical authorization model provided by the Services and the organization's authorized configuration.

More information about organization administrator access will appear in Section 23.

2.6 APIs, integrations and connected services

Customers may authorize DroneJob to exchange information with third-party systems.

Examples may include:

• CRM platforms;
• ERP systems;
• accounting platforms;
• GIS systems;
• project-management software;
• flight or fleet systems;
• identity providers;
• cloud-storage services;
• work-order systems;
• communication services;
• other enterprise applications.

When a customer enables an integration, DroneJob may process information necessary to authenticate, operate, monitor and troubleshoot that integration.

The customer is responsible for determining:

• whether it is authorized to connect the system;
• what information should be exchanged;
• what permissions should be granted; and
• whether the exchange complies with applicable law and contractual obligations.

When information is transferred from DroneJob to an independently operated third-party service at the customer's direction, the third party's privacy practices may govern the information after that transfer.

Additional information about integrations will appear in Section 14.

2.7 Service providers and subprocessors

DroneJob uses service providers and subprocessors to help operate the Services.

Depending on their function, they may process information on DroneJob's behalf.

Examples may include providers of:

• cloud infrastructure;
• authentication;
• communications;
• email;
• storage;
• monitoring;
• security;
• analytics;
• payments;
• customer support; and
• artificial-intelligence infrastructure.

DroneJob remains responsible for selecting and managing its providers consistent with applicable contractual and legal obligations.

A more detailed discussion of subprocessors will appear in Section 25.

2.8 Data Processing Addendum

As DroneJob expands enterprise functionality, DroneJob intends to maintain a Data Processing Addendum for customers where required.

The DPA should address matters such as:

• controller/processor relationships;
• processing instructions;
• confidentiality;
• security measures;
• subprocessors;
• data-subject requests;
• breach notification;
• deletion and return of Customer Data;
• international transfers; and
• applicable Standard Contractual Clauses or equivalent transfer mechanisms.

The DPA should supplement—not replace—this Privacy Policy.

3.1 Website visitors and prospective users

This includes people who:

• browse DroneJob websites;
• view public pilot profiles;
• review public content;
• interact with marketing pages;
• submit interest forms;
• join a waitlist;
• request product information;
• contact DroneJob;
• participate in surveys; or
• otherwise interact with DroneJob before creating an account.

3.2 Individual DroneJob account holders

This may include:

• aspiring drone pilots;
• certified drone pilots;
• part-time operators;
• independent professionals;
• specialists;
• business owners;
• clients;
• buyers;
• partners;
• ambassadors; and
• other individuals using DroneJob Services.

The information processed will depend on the individual's account type and the features used.

3.3 Drone pilots and drone service providers

DroneJob may process information relating specifically to professionals and businesses providing drone services, including:

• individual pilots;
• sole proprietors;
• contractors;
• specialists;
• small teams;
• drone service providers ("DSPs");
• vendor organizations; and
• enterprise service providers.

Professional information may include public-profile information as well as private business, operational, credential, client and mission information.

3.4 Clients and prospective clients

DroneJob may process information about individuals seeking drone services.

A client may:

• create a DroneJob account;
• contact a pilot without initially creating a full account;
• submit a service inquiry;
• participate in a conversation;
• create or approve a mission;
• receive project updates;
• review deliverables;
• make a payment;
• leave a review; or
• interact through an enterprise customer's workflow.

Prospective-client information may therefore be processed before the individual becomes a registered DroneJob user.

3.5 Organization and enterprise users

DroneJob may process information about people who use DroneJob on behalf of an organization, including:

• enterprise administrators;
• operations managers;
• procurement users;
• project managers;
• compliance personnel;
• finance users;
• executives;
• internal pilots;
• dispatchers;
• vendor managers;
• IT personnel;
• integration administrators; and
• other Authorized Users.

These users may be subject both to this Privacy Policy and to their organization's own policies and contractual arrangements with DroneJob.

3.6 Employees, contractors and vendors whose information is provided by a customer

A DroneJob customer may provide information about people who do not personally maintain DroneJob accounts.

Examples may include:

• employees;
• subcontractors;
• external pilots;
• vendors;
• customer contacts;
• site contacts;
• property managers;
• project stakeholders;
• emergency contacts;
• invoice contacts;
• approvers.

DroneJob may process this information as Customer Data in order to provide Services requested by the relevant customer.

The customer is responsible for having appropriate rights and legal authority to provide that information to DroneJob.

3.7 People stored in CRM and productivity tools

Pilots, DSPs and organizations may use DroneJob productivity tools to manage their own business relationships.

Those tools may contain information about:

• leads;
• prospects;
• current customers;
• former customers;
• business contacts;
• referral contacts;
• organization representatives.

Some of these individuals may never create a DroneJob account.

When DroneJob processes this information solely to provide the relevant business tools to a customer, DroneJob may process the information on that customer's behalf as described in Section 2.

3.8 Mission and project participants

Mission and workflow records may identify individuals involved in a project even where those individuals are not registered users.

Examples include:

• site contacts;
• access coordinators;
• project managers;
• inspectors;
• client representatives;
• subcontractors;
• safety personnel;
• approvers;
• deliverable recipients.

The information processed should be limited to what is reasonably necessary for the mission, project or workflow.

3.9 Training, education and industry partners

DroneJob may process information about individuals associated with:

• drone schools;
• instructors;
• training providers;
• insurers;
• equipment providers;
• software vendors;
• event organizers;
• sponsors;
• affiliate partners;
• professional organizations.

Additional contractual terms may apply to partner relationships.

3.10 Developers, integration administrators and technical contacts

Enterprise and partner integrations may require information concerning:

• developers;
• API administrators;
• security contacts;
• technical owners;
• system administrators;
• integration support personnel.

This information may be used to administer credentials, integration access, security events, technical notices and support.

3.11 People who communicate with DroneJob

This includes individuals who contact DroneJob for:

• customer support;
• technical support;
• security reports;
• privacy requests;
• legal matters;
• billing questions;
• sales inquiries;
• enterprise procurement;
• vendor onboarding.

3.12 Information about other individuals

Users must exercise care when providing information about another person through DroneJob.

A user should provide another person's personal information only when the user has an appropriate legal basis, authorization or legitimate business reason to do so.

Users must not use DroneJob to:

• upload personal information they are not authorized to process;
• disclose confidential personal information without authorization;
• import contact lists for unlawful or unsolicited marketing;
• evade consent requirements;
• misuse personal information obtained through the marketplace.

More detailed obligations relating to Customer Data, CRM contacts, communications and integrations will be addressed in later sections of this Policy and the Terms of Service.

3.13 People not covered by this Policy in certain contexts

This Privacy Policy is intended primarily for information processed through the DroneJob Services.

Separate notices may apply in the future to information collected in specialized contexts, such as:

• DroneJob employees and job applicants;
• corporate investors;
• certain offline business relationships;
• government-specific environments;
• specialized enterprise implementations governed by separate privacy notices.

Where a separate notice applies, DroneJob will identify that notice at the relevant point of collection.

4.1 Account registration information

When you create or maintain a DroneJob Account, we may collect information such as:

• full name;
• preferred or display name;
• email address;
• mobile telephone number;
• country or region;
• language or locale;
• time zone;
• account role or user type;
• account status;
• organization affiliation;
• profile image;
• communication preferences;
• account creation date;
• other information necessary to create or administer the Account.

Some information may be optional.

If information is required for a particular feature, declining to provide it may prevent that feature from functioning.

4.2 Authentication information

DroneJob uses authentication and identity-management technologies to help authenticate users and protect Accounts.

Depending on the authentication method used, we may process information such as:

• a unique user or identity identifier;
• login timestamps;
• authentication method;
• identity-provider information;
• session identifiers;
• authentication tokens or token metadata;
• multi-factor authentication status;
• security or verification events;
• failed-login information;
• account recovery information;
• device or browser information associated with authentication.

DroneJob may rely on third-party identity providers to perform authentication.

Where authentication is performed through a third-party identity provider, that provider may process credentials according to its own privacy practices and its agreement with DroneJob or the user.

DroneJob does not need to receive or store the password that you use with an independent third-party identity provider merely because that provider is used to authenticate you to DroneJob.

4.3 Social, federated and enterprise authentication

Where available, DroneJob may allow users to access the Services using:

• social login;
• federated identity;
• Single Sign-On ("SSO");
• enterprise identity providers;
• other approved authentication methods.

When you or your Organization chooses one of these methods, DroneJob may receive information from the identity provider such as:

• your name;
• email address;
• organization identifier;
• user identifier;
• account claims;
• role or group information where configured;
• authentication status;
• other information authorized by the Organization or user.

Enterprise identity configurations may allow an Organization to control whether its Authorized Users can access DroneJob and which organization context or permissions are assigned to them.

More information regarding Organization administrator access appears in Section 23.

4.4 Organization membership and role information

If you participate in DroneJob through an Organization, DSP, team or Enterprise Customer, we may process information concerning:

• the Organization to which you belong;
• invitation status;
• membership status;
• assigned role;
• permissions;
• department or team where supplied;
• reporting or administrative relationships where configured;
• internal pilot/vendor status;
• account entitlement;
• date added to or removed from an Organization.

This information is used to provide appropriate access and help prevent unauthorized access to Organization-scoped information.

4.5 Account security information

DroneJob may collect and generate information to protect Accounts and the Services.

This may include:

• login history;
• authentication failures;
• suspicious-access indicators;
• security alerts;
• IP address;
• session metadata;
• device information;
• approximate location inferred from technical information;
• account lock or restriction events;
• administrative changes;
• role or permission changes;
• password-reset or recovery events;
• security-support interactions.

We may use this information to:

• authenticate users;
• detect unauthorized access;
• investigate suspected compromise;
• prevent fraud or abuse;
• protect users;
• enforce access controls;
• maintain auditability;
• comply with security obligations.

More detailed information regarding technical, usage, security and diagnostic information appears in Section 18.

4.6 Account recovery and verification

If you request help recovering or securing an Account, DroneJob may request information reasonably necessary to confirm that you are authorized to access the Account.

Depending on the circumstances, this may include:

• contact-information confirmation;
• email or mobile verification;
• organization confirmation;
• authentication challenges;
• support interaction records;
• additional verification where necessary to prevent unauthorized account takeover.

DroneJob should limit recovery-related information to what is reasonably necessary for the applicable security purpose.

4.7 Administrative account changes

Certain changes to an Account may be made by:

• the Account holder;
• an authorized Organization administrator;
• DroneJob support;
• automated security controls;
• enterprise identity or provisioning systems;
• other authorized mechanisms.

DroneJob may retain records of material Account changes where reasonably necessary for:

• security;
• auditability;
• dispute resolution;
• compliance;
• support.

4.8 Deactivated, suspended and deleted Accounts

An Account may become inactive, suspended or deleted.

Account status does not necessarily mean that every associated record is immediately erased.

For example, DroneJob may need to retain certain information relating to:

• completed Missions;
• business transactions;
• communications;
• security events;
• audit records;
• legal obligations;
• dispute resolution;
• Organization records;
• fraud prevention.

Data-retention and deletion principles are addressed in Section 28.

5.1 Professional profile information

Depending on the Services used, DroneJob may collect or allow you to provide professional information such as:

• professional or business name;
• biography;
• profile photograph or logo;
• location or service region;
• languages;
• services offered;
• service categories;
• industries served;
• professional specialties;
• years or type of experience;
• availability;
• service radius;
• business description;
• website;
• social or professional links;
• preferred contact methods;
• service packages;
• pricing or pricing ranges where supported;
• portfolio information;
• equipment or capability information;
• credentials and verification indicators;
• reviews and ratings;
• achievements, badges or recognition;
• other information you choose to include in your professional presence.

5.2 Service catalog and capability information

DroneJob may allow Pilots or DSPs to describe services and operational capabilities.

This may include information regarding:

• photography or video services;
• inspection capabilities;
• mapping or surveying-adjacent services;
• thermal imaging;
• construction progress;
• agriculture;
• infrastructure;
• real estate;
• equipment;
• payloads;
• sensors;
• software capabilities;
• geographic coverage;
• deliverable formats;
• operational capabilities;
• specialties.

This information may be used to:

• display services;
• help Clients understand capabilities;
• support search and filtering;
• facilitate matching;
• determine potential Mission fit;
• provide recommendations;
• improve marketplace organization.

5.3 Portfolio information

Users may be able to upload or link professional portfolio materials such as:

• photographs;
• video;
• project summaries;
• case studies;
• sample deliverables;
• sanitized project examples;
• descriptions of prior work;
• other professional evidence.

Users are responsible for ensuring that they have the right to publish or share portfolio information.

Users should not publish:

• confidential client information;
• restricted site information;
• private infrastructure information;
• personally sensitive information;
• proprietary deliverables;
• material they are not authorized to disclose.

DroneJob may provide privacy or visibility controls for portfolio information where supported.

5.4 Public profile visibility

Information that you intentionally designate as public may be visible to:

• DroneJob users;
• prospective Clients;
• other Pilots;
• organizations;
• partners;
• website visitors;
• search engines;
• other persons who access the public Internet.

Public profile information may be indexed or cached by search engines or copied by third parties outside DroneJob.

Even after information is removed from DroneJob, copies may remain temporarily or permanently in:

• search-engine caches;
• browser caches;
• archival services;
• content previously copied by another person;
• records retained as required by law.

DroneJob will use reasonable measures to stop displaying information that a user removes from DroneJob-controlled public surfaces, subject to applicable retention requirements.

5.5 Private professional information

Not all professional information is public.

Information that may remain private or restricted includes, depending on the feature:

• internal pricing notes;
• profitability information;
• non-public availability;
• customer lists;
• CRM information;
• private portfolio materials;
• private Mission history;
• unpublished deliverables;
• insurance documents;
• credential documents;
• sensitive equipment information;
• organization-only information.

The fact that information helps generate a public badge, ranking, recommendation or profile attribute does not necessarily make the underlying information public.

5.6 Reviews and reputation information

DroneJob may process reviews, ratings and other reputation information relating to marketplace or service activity.

This may include:

• reviewer identity;
• review content;
• numeric or categorical ratings;
• Mission or transaction association;
• response from the reviewed user;
• moderation status;
• dispute or investigation information;
• whether a review is verified against platform activity.

Some review information may be publicly displayed.

Private moderation records, fraud signals and dispute information generally are not intended to be public.

5.7 Marketplace search, discovery and matching

DroneJob may use profile and marketplace information to:

• enable search;
• provide filters;
• recommend Pilots or DSPs;
• identify potentially suitable providers;
• rank or organize marketplace results;
• suggest Missions or opportunities;
• identify geographic or capability fit;
• help Enterprise Customers build vendor pools.

Factors may include, where relevant:

• location;
• service category;
• credentials;
• verified information;
• availability;
• equipment;
• experience;
• reviews;
• past platform activity;
• Mission requirements;
• user preferences;
• plan or feature entitlements;
• other relevant marketplace signals.

Where DroneJob offers paid promotional placement, boosts or sponsored visibility, those features should be identified or presented in a manner appropriate to the context and applicable law.

DroneJob should not describe marketplace ranking as a guarantee of suitability or future performance.

Matching, ranking or recommendations may use deterministic rules, statistical techniques, or AI-assisted methods where available, but the use of such technology does not change the visibility or verification limitations described in this Policy.

5.8 Profile analytics

DroneJob may provide users with information about how their professional profile performs.

This may include metrics such as:

• profile views;
• search appearances;
• inquiries;
• clicks;
• portfolio engagement;
• conversion-related activity;
• marketplace visibility.

DroneJob may use similar information internally to:

• operate marketplace features;
• analyze product performance;
• detect abuse;
• improve ranking and discovery;
• improve user experience.

5.9 Information imported or derived from other sources

Where authorized, DroneJob may supplement professional profiles using information from:

• connected systems;
• training providers;
• credential providers;
• publicly available sources;
• partners;
• user-authorized integrations.

DroneJob should identify or distinguish externally sourced or inferred information when necessary to avoid misleading users about its source or verification status.

5.10 User responsibility for professional information

Professional information should be:

• accurate;
• current;
• not misleading;
• lawfully provided;
• appropriately classified as public or private.

Users should update materially outdated professional information, especially information concerning:

• certifications;
• insurance;
• service capabilities;
• geographic availability;
• business affiliation.

DroneJob may restrict, remove or flag information that appears fraudulent, misleading, unsafe, unlawful or inconsistent with platform requirements.

6.1 Professional credentials

Depending on the Services available and the user's jurisdiction, DroneJob may collect or process information concerning:

• FAA Remote Pilot Certificates under Part 107;
• equivalent commercial drone credentials in other jurisdictions;
• recurrent-training status;
• aviation authorizations;
• specialty training;
• industry certifications;
• manufacturer certifications;
• software certifications;
• professional licenses where relevant;
• other professional qualifications.

Information may include:

• credential type;
• issuing authority;
• credential number or identifier;
• issue date;
• expiration or renewal information;
• current status;
• supporting document;
• verification result;
• date verified.

6.2 Insurance and coverage information

DroneJob may allow or require Pilots, DSPs or vendors to provide insurance-related information.

This may include:

• insurer;
• policy type;
• policy number or reference;
• coverage amount;
• effective date;
• expiration date;
• Certificate of Insurance ("COI");
• relevant endorsements;
• verification status.

Underlying insurance documents may contain sensitive business information and generally should not be treated as public unless the user intentionally shares them through an authorized feature.

DroneJob may publicly display limited indicators such as:

• "Insurance on File";
• coverage status;
• verification status;
• expiration warning;

A displayed status does not constitute insurance advice or a guarantee that coverage applies to a particular Mission.

6.3 Identity verification

Where identity verification is offered or required, DroneJob or an approved verification provider may process information such as:

• legal name;
• date of birth;
• address;
• mobile number;
• photograph or selfie;
• government-issued identification;
• document identifiers;
• document-validity information;
• identity-verification result;
• fraud or authenticity indicators;
• verification timestamp.

Depending on the verification method and jurisdiction, an approved identity-verification provider may process:

• driver's license;
• passport;
• national identity document;
• other government-issued identification.

DroneJob should collect or retain only the information reasonably necessary for the relevant verification, security or legal purpose.

Where a third-party provider performs the verification, the provider may process information according to its contractual obligations and applicable privacy terms.

6.4 Sensitive verification documents

Underlying identity and credential documents may contain sensitive information.

DroneJob should not make such documents publicly available merely because a user has a public profile.

Where appropriate, DroneJob should display a verification result or status instead of exposing the source document itself.

Examples:

Part 107 — Verified
Insurance — Verified
Identity — Verified

rather than displaying the underlying certificate, policy or government ID publicly.

A User may separately choose to share a document with an authorized Client or Organization where the product permits it.

6.5 Verification providers and data sources

DroneJob may verify information using:

• document review;
• third-party verification providers;
• issuing authorities;
• databases;
• APIs;
• insurance providers;
• training providers;
• enterprise administrators;
• other reliable data sources.

Verification methods may differ by credential and jurisdiction.

6.6 Verification results

DroneJob may create or retain information regarding the outcome of a verification, including:

• verified;
• unverified;
• pending;
• expired;
• rejected;
• unable to verify;
• additional information required.

DroneJob may also retain:

• date of verification;
• verification method;
• source;
• relevant evidence reference;
• expiration or re-verification date.

These records may be used for:

• trust features;
• marketplace eligibility;
• matching;
• enterprise vendor readiness;
• security;
• compliance;
• dispute resolution;
• auditability.

6.7 Expiration and continuing validity

A credential that was valid at the time of verification may later:

• expire;
• lapse;
• be suspended;
• be revoked;
• change status;
• cease to satisfy a specific Mission requirement.

DroneJob may send reminders or change displayed verification status based on available information.

Users remain responsible for maintaining qualifications required for their activities and for notifying DroneJob where required information is no longer accurate.

6.8 Failed or incomplete verification

If DroneJob cannot verify information, we may:

• request additional information;
• display the information as unverified;
• restrict certain marketplace or enterprise functionality;
• prevent assignment to a Mission requiring the credential;
• refer the matter for manual review;
• take other reasonable steps appropriate to the feature.

An inability to verify information does not necessarily mean the information is fraudulent.

6.9 Enterprise-supplied verification information

An Enterprise Customer or DSP may provide or confirm certain information regarding:

• its employees;
• Pilots;
• contractors;
• vendors;
• qualifications;
• organizational status.

Where DroneJob relies on enterprise-supplied information, the source should be appropriately represented where needed.

The providing Organization is responsible for having authority to provide the information and for keeping material information current.

6.10 Fraud and abuse prevention

Verification information may be used to:

• prevent identity fraud;
• detect false credentials;
• protect users;
• prevent account abuse;
• investigate suspicious marketplace activity;
• protect enterprise vendor pools;
• enforce DroneJob policies.

Verification-related fraud indicators should not be publicly displayed unless required or appropriate.

6.11 Verification status and public display

DroneJob may publicly display limited verification indicators where the user participates in public marketplace functionality.

Public indicators should communicate only the scope of the verification performed.

For example:

Part 107 Verified

should mean that DroneJob verified the applicable Part 107 information under the relevant verification process.

It should not imply:

• endorsement by the FAA;
• guaranteed legal compliance for every Mission;
• guaranteed skill;
• guaranteed safety;
• guaranteed quality;
• a background check unless one was separately performed.

6.12 Retention of verification information

DroneJob may retain verification information for periods reasonably necessary to:

• maintain trust and verification status;
• support audits;
• investigate fraud;
• resolve disputes;
• comply with legal requirements;
• demonstrate prior verification;
• manage expiration and renewal.

Where possible and appropriate, DroneJob should avoid retaining sensitive source documents longer than necessary once the required verification result and evidence have been securely recorded.

Specific retention rules will be addressed in Section 28.

7.1 Client and contact records

Depending on the Services used, Customer Data may include information concerning a Customer's Clients, prospective Clients or other business contacts, such as:

• name;
• business or organization name;
• job title;
• telephone number;
• email address;
• mailing address;
• billing address;
• service address;
• preferred communication method;
• account or customer reference numbers;
• tags or categories;
• lead source;
• customer status;
• internal notes;
• relationship history;
• assigned account owner or representative;
• other information the Customer chooses to maintain for legitimate business purposes.

Not every person represented in a CRM or contact record necessarily has a DroneJob Account.

7.2 Leads and prospective Clients

DroneJob may process information about leads and prospective Clients when a Customer uses DroneJob to manage sales or business-development activity.

This may include:

• inquiry source;
• services requested;
• industry;
• project type;
• potential location;
• desired timing;
• budget or pricing information;
• follow-up status;
• pipeline stage;
• notes;
• communication history;
• reason an opportunity was won, lost or closed;
• other relevant sales information.

Some leads may originate through DroneJob Marketplace functionality.

Other leads may be entered manually or imported from a Customer's independent business activities.

7.3 Marketplace-generated Client information

When a prospective Client contacts a Pilot or DSP through DroneJob, DroneJob may collect information necessary to:

• create the inquiry;
• deliver it to the intended recipient;
• create or maintain a conversation;
• allow the parties to respond;
• support subsequent Mission or workflow creation;
• maintain marketplace integrity;
• provide applicable trust or support functionality.

The information may then become part of the Pilot's or DSP's DroneJob business records where the Services support that workflow.

7.4 Independently acquired Client information

Where supported, Customers may use DroneJob's productivity tools to maintain information concerning Clients or prospects that the Customer acquired outside the DroneJob Marketplace.

For example, a Pilot may use DroneJob CRM tools to manage:

• an existing real-estate Client;
• a construction company acquired through referral;
• a roofing company contacted directly;
• a recurring commercial customer.

The inclusion of such a contact in DroneJob does not mean that DroneJob originated or owns that business relationship.

Where DroneJob processes the information solely to provide productivity Services to the Customer, DroneJob may process the information on the Customer's behalf as described in Section 2.

7.5 Customer responsibility for CRM data

Customers are responsible for determining whether they have appropriate authority or other lawful basis to:

• collect contact information;
• enter it into DroneJob;
• communicate with the person;
• maintain notes or records;
• use the information for the Customer's business purposes;
• direct DroneJob to process the information.

Customers must not use DroneJob CRM functionality to:

• maintain unlawfully obtained contact lists;
• facilitate spam;
• evade marketing-consent requirements;
• store information they are prohibited from processing;
• use marketplace information for unrelated unauthorized solicitation.

7.6 Client addresses and service locations

A CRM Client may be associated with one or more locations.

For example:

Client:
ABC Construction

Billing Address:
Corporate Office

Service Locations:
Site A
Site B
Site C

DroneJob may distinguish between:

• a Client's billing or business address;
• contact addresses;
• project or service locations;
• Mission locations.

A Mission or project location should not automatically be treated as the Client's personal or billing address.

Additional information concerning operational and geospatial information appears in Section 10.

7.7 Notes and relationship history

Customers may be able to maintain notes concerning Clients, leads or contacts.

Customers may also keep personal workspace notes (Sticky Notes) as private User Content. Those notes are visible to the account holder and to people they explicitly share with.

Notes may include information such as:

• project preferences;
• prior service history;
• follow-up reminders;
• customer requirements;
• internal coordination information;
• billing notes;
• relationship context.

Customers are responsible for using reasonable judgment concerning the information they place in free-text notes.

Customers should not place:

• unnecessary sensitive personal information;
• discriminatory information;
• unlawfully obtained information;
• information unrelated to a legitimate business purpose;

into CRM notes merely because the product permits free-text entry.

7.8 Client communication preferences

Customers may maintain information concerning a Client's communication preferences or consent status.

This may include:

• preferred channel;
• email preferences;
• SMS eligibility;
• opt-in records;
• opt-out records;
• communication restrictions.

DroneJob may also independently maintain consent or suppression records necessary to comply with DroneJob's own messaging obligations.

Detailed SMS privacy practices appear in Section 13.

7.9 CRM history and related business objects

Where available, DroneJob may associate a Client or contact with related records, including:

• inquiries;
• quotes;
• proposals;
• Missions;
• appointments;
• invoices;
• deliverables;
• files;
• communications;
• reviews;
• payments;
• workflow events.

This enables a Customer to view relevant business history in context.

7.10 Organization access to CRM information

CRM records created or maintained within an Organization Account may be accessible to Authorized Users based on:

• role;
• permissions;
• team;
• Organization configuration.

Individual Users should not assume that CRM activity conducted within an Organization environment is private from authorized Organization administrators.

Additional information regarding Organization administrator access appears in Section 23.

8.1 Organization information

Depending on the Services used, DroneJob may process information such as:

• legal or business name;
• trade name;
• business address;
• website;
• business contact information;
• industry;
• Organization type;
• operating regions;
• Organization identifiers;
• tax or registration information where required;
• subscription information;
• organizational settings;
• security configuration;
• billing contact information.

Some Organization information may relate to an identifiable individual, particularly for sole proprietors or small businesses.

8.2 Organization members and workforce information

An Organization may provide or maintain information about:

• employees;
• Pilots;
• contractors;
• subcontractors;
• vendors;
• administrators;
• managers;
• dispatchers;
• operations personnel;
• finance users;
• compliance personnel;
• other Authorized Users.

Information may include:

• name;
• business contact details;
• role;
• job function;
• Organization membership;
• permissions;
• service area;
• Pilot qualifications;
• credential status;
• assignment eligibility;
• availability;
• team;
• internal user identifiers;
• employment or contractor classification where the Organization provides it.

DroneJob does not determine an individual's legal employment classification merely because a role or classification is represented in the Services.

8.3 Organization membership and access status

DroneJob may process records such as:

• invitation date;
• invitation sender;
• membership acceptance;
• active/inactive status;
• role;
• permission changes;
• date added;
• date removed;
• administrative actions.

These records may support:

• access control;
• auditing;
• security;
• compliance;
• troubleshooting.

8.4 Vendor and Pilot rosters

Enterprise Customers and DSPs may use DroneJob to manage internal or external Pilot/vendor networks.

Vendor records may include:

• business identity;
• primary contacts;
• assigned Pilots;
• qualifications;
• insurance status;
• service regions;
• equipment;
• performance information;
• availability;
• Organization-specific approval status;
• preferred-vendor status;
• program membership;
• SLA eligibility.

Some vendor information may constitute Customer Data provided by the Enterprise Customer.

Other information may originate from a Pilot's own DroneJob profile or from DroneJob verification functionality.

DroneJob should preserve relevant source/context distinctions where necessary.

8.5 Workforce scheduling and assignment information

Organizations may use DroneJob to coordinate work.

Where available, this may involve information concerning:

• availability;
• assignment;
• work schedule;
• Mission participation;
• operational readiness;
• geographic coverage;
• equipment assignment;
• workload;
• workflow status.

The fact that DroneJob processes scheduling or assignment information does not mean that DroneJob acts as the individual's employer.

8.6 Performance and operational information

Depending on the Services used, an Organization may create or access information concerning:

• Mission completion;
• timeliness;
• service quality;
• SLA performance;
• assignment history;
• operational exceptions;
• reviews;
• customer feedback;
• utilization;
• other program metrics.

Enterprise Customers should use employee, contractor or vendor performance information consistently with applicable laws, contracts and internal policies.

DroneJob may impose technical access controls but does not determine how an Organization lawfully manages its workforce.

8.7 Enterprise administrators

Authorized administrators may have broader access to Organization-scoped information.

This can include information relating to:

• users;
• roles;
• workflows;
• Client records;
• Missions;
• files;
• integrations;
• activity history;
• audit logs.

Users operating within an enterprise environment should understand that Organization-related information may be accessible to authorized administrators.

A more complete description appears in Section 23.

8.8 Enterprise identity and provisioning data

Where available, Enterprise Customers may manage users using:

• SSO;
• identity federation;
• SCIM;
• directory synchronization;
• similar identity-management technologies.

DroneJob may process:

• enterprise user identifiers;
• email;
• name;
• role;
• group;
• department;
• account state;
• provisioning event;
• identity claims authorized by the Enterprise Customer.

8.9 Enterprise Customer responsibility

An Enterprise Customer or Organization is responsible for determining that it has appropriate authority to provide and manage workforce, vendor and organizational information through DroneJob.

This may include satisfying obligations regarding:

• transparency;
• employee notices;
• contractor notices;
• monitoring;
• access rights;
• record retention;
• workplace privacy;
• applicable labor and privacy laws.

8.10 Separation between Organization and individual contexts

Where DroneJob permits both personal and Organization use, information associated with an Organization should remain governed by the appropriate Organization context.

For example:

Personal Pilot Profile
≠
Enterprise Employer's Internal Mission Records

A User's participation in an Organization does not automatically make all information in the User's independent DroneJob context available to the Organization.

Similarly, removal from an Organization does not necessarily delete records that the Organization is independently entitled or required to retain.

9.1 Service requests and Orders

Depending on the applicable Service, an Order, Work Request or service inquiry may identify the requesting Client or Organization and describe the requested work, location, timing, deliverables, requirements and related project details.

Orders may be created manually by a User, from a Client inquiry, by an Enterprise Customer, through bulk upload, through an authorized API, through a webhook, through an Integration, or through an approved automated workflow.

9.2 Mission records and participants

A Mission may include operational details needed to coordinate the work, such as parties, scope, location, schedule, assignments, status, files, deliverables, approvals and workflow history. Not all Mission fields are personal information, but Mission records may contain or be associated with personal information.

Mission information may identify people who participate in or receive the work. A person may appear in a Mission without having a full DroneJob Account.

9.3 Workflow status, approvals and audit

DroneJob may maintain structured records of workflow events, approvals, assignments, exceptions and related timestamps or actors. Actual workflow states depend on the feature and use case.

Approval and audit records may be retained to support collaboration, troubleshooting, enterprise reporting and dispute support. Audit records may be retained separately from user-facing workflow records.

Where recommendations are generated by automation or AI, additional information may be processed as described in Sections 15 and 16.

9.4 Enterprise workflow data

Enterprise Customers may use DroneJob to manage high volumes of Orders or Missions. Related records may include internal project identifiers, site or asset references, program or contract identifiers, SLA targets and other Customer Data processed on the Enterprise Customer's behalf.

9.5 Automated workflow creation

A workflow action may originate from an authorized automated process, such as an Enterprise work order arriving through an authorized Integration and creating a DroneJob Order and Mission workflow.

DroneJob may process metadata necessary to identify the source system, authorization, time, workflow, action result and error state. More information about automated and machine-to-machine processing appears in Section 15.

10.1 Service areas

Pilots and DSPs may provide general service-area information such as city, region, country or a geographic radius. Service-area information may be displayed publicly as part of a professional profile or used for marketplace search and matching.

A public service area does not necessarily disclose the Pilot's home or exact current location.

10.2 Project, Mission and operational location

DroneJob may process location information for Client properties, inspection or construction sites, infrastructure and other places where drone services are requested. This may include an address, coordinates, site name or geospatial boundary. Project locations may be confidential or operationally sensitive even where the address itself is publicly known.

A Mission may include precise information concerning where work is intended to occur. Mission location should be available only to users whose role or participation requires access, except where a Customer intentionally makes information public.

Where DroneJob supports flight-related records or file metadata, location may also appear in flight paths, capture coordinates or embedded image metadata. Users should understand that removing visible location information from an image does not necessarily remove embedded metadata.

Airspace data and regulatory assistance should not be treated as proof that a Mission is legally authorized to proceed.

10.3 Device location and tracking

Where supported and authorized, DroneJob mobile or web applications may request access to device location for location-aware Mission views, arrival or on-site status, or field coordination. Users may generally control device-location permission through their device or browser settings.

The availability of location functionality does not mean DroneJob continuously tracks a Pilot or other User at all times.

DroneJob may also infer an approximate location from technical information such as IP address. This is distinct from precise GPS/device location.

10.4 Organization visibility and sensitive sites

If a User participates in an Organization account, authorized Organization users may be able to view certain work-related location information where the feature is enabled and appropriate to the User's role.

Organizations are responsible for ensuring that their use of workforce location information complies with:

• applicable law;
• employment policies;
• contractor agreements;
• privacy obligations.

Users should exercise particular care when providing information concerning critical infrastructure, private residences, government facilities or other security-sensitive sites.

10.5 Location retention

DroneJob should retain precise location and flight information only for as long as reasonably appropriate to provide the Services, maintain Mission history, support evidence and deliverables, satisfy Customer instructions, comply with legal or contractual obligations, investigate incidents or maintain security.

Specific retention rules will be addressed in Section 28.

11.1 Types of files and project content

DroneJob may process photographs, video, reports, maps, documents, Mission instructions, processed deliverables, proof-of-evidence materials, portfolio content and other files uploaded or generated through the Services.

The specific file types supported depend on the applicable Service and product functionality.

11.2 Mission deliverables

Mission records may include or reference deliverables created for a Client or Enterprise Customer.

Deliverables may include:

• photographs;
• videos;
• reports;
• inspection materials;
• mapping outputs;
• measurements;
• technical files;
• models;
• project documentation;
• other agreed outputs.

DroneJob may process deliverables in order to:

• store them;
• organize them;
• associate them with a Mission;
• make them available to authorized participants;
• record delivery or acceptance;
• generate related evidence;
• support workflow or reporting functionality.

11.3 Raw files and processed outputs

DroneJob may distinguish between:

• original/raw files;
• intermediate processing artifacts;
• final deliverables;
• previews;
• thumbnails;
• supporting evidence.

Access and retention may differ based on:

• Customer configuration;
• Mission requirements;
• plan;
• file class;
• applicable contract;
• legal requirement.

11.4 Proof Packs and evidence

DroneJob may create or support structured evidence associated with completed work.

A proof or evidence package may include information such as:

• Mission identity;
• Pilot/DSP;
• date;
• location;
• credential status;
• completion status;
• selected deliverables;
• Client acceptance;
• relevant workflow events;
• other authorized evidence.

DroneJob may use this information to help Users demonstrate experience, Mission completion or vendor readiness.

A Proof Pack does not itself establish a regulated professional conclusion or legal certification unless expressly stated.

11.5 Portfolio content

Users may choose to reuse authorized work as public or private portfolio content.

The User is responsible for determining whether:

• the Client permits publication;
• confidentiality obligations allow publication;
• sensitive location information should be removed;
• individuals appearing in content can lawfully be shown;
• proprietary material may be disclosed.

DroneJob should not automatically convert private Mission deliverables into public portfolio content without an authorized product workflow.

11.6 Client-provided materials

Clients and Enterprise Customers may provide materials necessary for work, such as:

• plans;
• maps;
• inspection specifications;
• reference photographs;
• scope documents;
• site instructions;
• asset information;
• CAD/GIS files;
• other project materials.

The providing party is responsible for having appropriate authority to provide such materials to DroneJob and the authorized Mission participants.

11.7 File metadata

Files may contain metadata such as:

• filename;
• MIME/file type;
• size;
• upload date;
• uploader;
• Mission association;
• Client association;
• checksum;
• camera/device information;
• timestamps;
• geolocation;
• technical metadata.

DroneJob may process metadata to:

• organize files;
• secure access;
• verify integrity;
• provide evidence;
• support search or processing;
• maintain audit records.

Location metadata is addressed further in Section 10.

11.8 File access and permissions

Files may have different visibility scopes, including:

• public;
• private to the User;
• Organization-only;
• Mission participant;
• Client-shared;
• enterprise-restricted;
• administrator-restricted.

DroneJob may enforce access based on:

• role;
• Organization;
• Mission membership;
• authorization;
• Customer configuration.

Users should verify the intended visibility before sharing sensitive information.

11.9 Sensitive and confidential content

Project content may contain:

• confidential business information;
• trade secrets;
• infrastructure information;
• personal information;
• security-sensitive site data;
• proprietary Client information.

Users should not place highly sensitive or regulated information in DroneJob unless:

• necessary for an authorized Service;
• permitted by applicable agreements;
• appropriate safeguards are available.

DroneJob may establish restrictions on categories of sensitive information.

11.10 Retention and deletion

Files may be retained based on:

• Customer configuration;
• Mission history;
• business requirements;
• evidence requirements;
• plan;
• legal obligations;
• dispute or security needs.

Specific retention principles appear in Section 28.

Deleting a user-facing reference to a file may not immediately remove:

• backups;
• audit records;
• legally required copies;
• retained enterprise records.

11.11 Content processing

DroneJob may process files to provide requested functionality such as:

• previews;
• thumbnails;
• metadata extraction;
• search;
• evidence generation;
• AI-assisted review;
• file organization;
• technical validation.

Where AI Features process project content, the additional practices described in Section 16 apply.

12.1 Supported communications

Depending on availability, DroneJob communications may include:

• in-app messages;
• SMS;
• transactional email;
• email relay;
• notifications;
• future supported communication channels.

DroneJob may use third-party communications providers to deliver communications.

12.2 Canonical DroneJob Conversations

DroneJob may maintain a Conversation as a business record independent of the transport used to deliver an individual message.

For example, a Conversation may contain a Client SMS, a Pilot SMS reply, an in-app Client response and an email follow-up. Where supported, these communications may appear within the same DroneJob conversation timeline.

12.3 Information processed

Communication information may include participants, message content, channel, timestamps, delivery status, Conversation or Mission association, consent or suppression status, and related communication metadata.

12.4 Messages authored by Users

A message written by a User remains that User's communication merely because DroneJob transmits or stores it.

DroneJob may process the communication to:

• route it;
• deliver it;
• preserve conversation history;
• generate notifications;
• detect abuse;
• provide AI-assisted functionality requested by the User;
• support disputes or auditing;
• comply with law.

12.5 DroneJob-originated communications

DroneJob may also send its own service communications, such as:

• security messages;
• verification messages;
• inquiry notifications;
• workflow alerts;
• account notices;
• Mission notifications.

A DroneJob-originated notification should be distinguished from a message authored by another marketplace participant where necessary.

12.6 Communication providers

DroneJob may use communications providers to deliver:

• SMS;
• email;
• voice or other supported channels.

Providers may process information necessary for:

• routing;
• delivery;
• spam/abuse prevention;
• delivery status;
• carrier compliance;
• technical support.

DroneJob should not rely on a transport provider as the sole authoritative source for DroneJob's business conversation history.

12.7 Communications outside DroneJob

If Users exchange personal contact information and communicate entirely outside DroneJob-controlled channels, DroneJob generally cannot access or preserve those communications.

For example, a Pilot and Client exchanging personal phone numbers without use of a DroneJob relay is generally outside DroneJob's Conversation record.

DroneJob does not attempt to access unrelated native-device SMS or call history.

12.8 Communications within Organizations

Communications associated with an Organization environment may be accessible to authorized Organization Users or administrators where appropriate to:

• Mission management;
• Client support;
• supervision;
• audit;
• compliance.

Users should understand that communications conducted as part of Organization business may not be private from appropriately authorized Organization administrators.

12.9 Message retention

DroneJob may retain communication records as necessary to:

• provide conversation history;
• support customer workflows;
• maintain Mission records;
• resolve disputes;
• enforce policies;
• satisfy legal obligations;
• support auditability.

Retention is addressed further in Section 28.

12.10 Automated analysis of communications

Where enabled, DroneJob may use automation or AI to assist with functions such as:

• summarization;
• suggested replies;
• extracting follow-up tasks;
• identifying potential scheduling information;
• identifying potential scope changes;
• organizing Conversation context.

Such features are supportive tools.

A machine-generated interpretation of a communication does not replace the original communication or automatically create a binding Client/Pilot commitment unless an authorized workflow expressly does so.

Section 16 describes AI processing in greater detail.

13.1 SMS message types

Depending on the Services used, SMS messages may include:

• account or telephone verification;
• security alerts;
• new Client inquiries;
• Pilot or Client replies;
• Conversation notifications;
• scheduling coordination;
• Mission or project updates;
• appointment reminders;
• account activity;
• workflow notifications;
• secure links to continue activity in DroneJob;
• other transactional service communications.

Marketing or promotional SMS, if offered, will be handled according to the consent requirements applicable to that messaging purpose.

13.2 Consent

Where consent is required, DroneJob obtains messaging consent using an appropriate opt-in mechanism.

For example, a User may voluntarily select an unchecked checkbox authorizing service-related text messages.

Messaging consent must be:

• voluntary;
• appropriate to the message purpose;
• separate from unrelated agreements where required.

Consent to receive marketing SMS is not a condition of purchasing goods or Services.

Consent to one messaging purpose does not automatically constitute consent to unrelated promotional messaging.

13.3 Message frequency

Message frequency varies depending on Account activity, Client inquiries, Conversations, Missions and other DroneJob service activity.

13.4 Message and data rates

Message and data rates may apply.

Carrier or mobile-plan charges are determined by the User's wireless provider.

13.5 Opt-out

Users may reply STOP to supported DroneJob SMS messages to opt out of the applicable messaging program.

DroneJob may send a final confirmation message acknowledging the opt-out.

Opting out of SMS does not necessarily terminate a DroneJob Account or prevent permitted communications through other channels.

13.6 Help

Users may reply HELP for assistance.

DroneJob may provide support information through the resulting message.

13.7 Messaging consent data

The following sentence is intentionally included to support current U.S. carrier/Twilio compliance requirements and must not be altered without compliance review:

All the above categories exclude text messaging originator opt-in data and consent; this information won't be shared with any third parties.

DroneJob may use service providers acting on DroneJob's behalf solely as necessary to operate, secure and deliver the messaging service.

Those providers are not permitted to use SMS opt-in or consent information for their own marketing or promotional purposes.

DroneJob does not:

• sell SMS opt-in information;
• rent SMS opt-in information;
• disclose mobile numbers or messaging consent to third parties or affiliates for their own marketing or promotional purposes.

13.8 SMS relay

Where DroneJob provides SMS relay between participants, DroneJob may process:

• sender/recipient numbers;
• message content;
• delivery metadata;
• Conversation mapping;
• opt-out state.

The purpose is to deliver and retain authorized business communications while helping keep them associated with the relevant DroneJob Conversation.

13.9 Carrier and provider processing

Wireless carriers and communications providers may process information necessary to:

• route messages;
• prevent abuse;
• comply with telecommunications requirements;
• report delivery status.

Their independent obligations may be governed by applicable law and their own policies.

13.10 Messaging records

DroneJob may retain messaging records consistent with:

• Conversation history;
• Mission history;
• legal obligations;
• support;
• audit;
• dispute resolution;
• security.

13.11 SMS consent records

DroneJob may maintain evidence regarding messaging consent, including:

• telephone number;
• consent status;
• consent source;
• timestamp;
• disclosure/version;
• opt-out status;
• opt-out timestamp.

These records support compliance and User preference management.

14.1 Types of connected systems

Connected systems may include:

• CRM;
• ERP;
• GIS;
• work-order management;
• project management;
• accounting;
• identity systems;
• cloud storage;
• flight or fleet systems;
• aviation tools;
• communications systems;
• customer systems;
• other approved applications.

14.2 Information received through integrations

DroneJob may receive information such as:

• Organization information;
• Users;
• Clients;
• Orders;
• Work Requests;
• Missions;
• asset identifiers;
• location;
• files;
• workflow status;
• financial references;
• credentials;
• other Customer Data.

The information received depends on:

• the Integration;
• Customer configuration;
• permissions granted;
• requested workflow.

14.3 Information sent to connected systems

DroneJob may transmit authorized information such as:

• Mission status;
• assignment;
• Pilot/vendor information;
• deliverable links;
• compliance status;
• invoice status;
• workflow events;
• files or references;
• other Customer-authorized information.

14.4 Customer authorization

A Customer that enables an Integration directs DroneJob to exchange information within the authorized scope.

The Customer is responsible for determining:

• that it has authority to connect the systems;
• that it has the rights necessary to exchange the information;
• which scopes/permissions are appropriate;
• whether the Integration is appropriate for the Customer's regulatory or contractual environment.

14.5 Credentials and tokens

DroneJob may process:

• API credentials;
• OAuth tokens;
• webhook secrets;
• Integration identifiers;
• related technical metadata.

Such credentials should be protected as sensitive security information.

DroneJob should use them only as necessary to operate the authorized Integration.

14.6 Integration logs

DroneJob may record information such as:

• API call time;
• Integration;
• endpoint/action;
• success/failure;
• correlation ID;
• source system;
• destination system;
• retry status;
• technical error.

Logs support:

• security;
• debugging;
• auditing;
• reliability;
• enterprise support.

14.7 Third-party privacy practices

When information is transferred to an independently controlled Third-Party Service at the Customer's direction, that provider's privacy terms may govern its subsequent handling of the information.

DroneJob does not control the independent data practices of a Third-Party Service merely because it can be connected to DroneJob.

14.8 Revoking an Integration

Where supported, a Customer may disable an Integration.

Disabling a connection may stop future data exchange but may not automatically delete information already:

• received by DroneJob;
• transmitted to the third party;
• incorporated into Mission history;
• retained according to legal obligations.

14.9 Enterprise integration contracts

Certain Integrations may be subject to:

• API Terms;
• Enterprise Agreements;
• DPAs;
• security requirements;
• Integration-specific terms.

Those agreements may provide additional data-processing obligations.

15.1 Examples of automated processing

Examples may include creating a Mission from an authorized work order, generating a reminder when a credential is nearing expiration, requesting a review after Mission completion, or notifying a Client when a deliverable is uploaded.

15.2 Information processed

Automated workflows may process Customer Data, Mission data, workflow status, contacts, files, dates, Integration data and other relevant business information.

15.3 Customer configuration

Customers may configure triggers, conditions, actions, recipients, scopes and workflow rules. Where the Customer configures the workflow, DroneJob processes information according to the Customer's authorized configuration.

15.4 Machine-to-machine instructions

DroneJob may receive instructions from authorized systems rather than directly from a human User. For example, a Customer ERP may send an authorized API request that DroneJob processes.

DroneJob may process source, credential, action, payload, timestamp, result, error and correlation information needed to execute and audit that instruction.

15.5 Workflow auditability

DroneJob may maintain records concerning:

• trigger;
• action;
• actor or system;
• timestamp;
• state change;
• result.

This supports:

• troubleshooting;
• compliance;
• accountability;
• enterprise reporting.

15.6 Errors and retries

Automated processes may:

• fail;
• be delayed;
• retry;
• receive duplicate events;
• receive incorrect source data.

DroneJob may process technical information required to:

• prevent duplicate actions;
• retry safely;
• diagnose errors;
• alert appropriate Users.

15.7 Human oversight

Organizations are responsible for determining which business processes are appropriate to automate.

Automation should not be configured to bypass:

• required human approval;
• regulatory requirements;
• safety controls;
• access controls.

15.8 Automation versus legal authority

The fact that a workflow executes automatically does not determine whether the underlying business action is legally authorized.

The Customer remains responsible for configuring automation consistent with:

• its authority;
• applicable contracts;
• applicable law.

15.9 AI-assisted automation

Where AI is used to determine, recommend or assist an automated action, the additional rules in Section 16 apply.

16.1 Examples of AI-assisted functionality

Depending on availability, AI Features may assist with: drafting, summarization, Mission planning, communications, compliance review and other productivity tasks.

16.2 Inputs

AI Features may process information provided or authorized by Users, including prompts, Account information, Customer Data, Mission information, Conversations, files and workflow context.

A User should provide information to AI Features only where the User or Customer has appropriate authority to process that information.

16.3 Outputs

AI Features may produce text, summaries, recommendations, classifications, drafts, proposed workflow actions or other generated results. AI Outputs may be inaccurate, incomplete, non-unique or otherwise require additional context.

Users should review Outputs before relying on them.

16.4 AI as supportive technology

AI Features are intended to support Users rather than replace them. AI may flag weather, detect a possible additional deliverable, or draft a message, but the responsible Pilot determines whether a Mission may proceed, the User determines whether a scope change should be created, and the responsible User reviews a commercial commitment before sending it where approval is required.

16.5 Human-controlled material decisions

DroneJob should maintain human review or an explicitly authorized bounded workflow for material decisions involving, as applicable, pricing or contractual commitments, regulatory representations, Mission go/no-go decisions, safety or qualification overrides, payments and other high-impact actions.

DroneJob AI should not independently represent that it is the responsible Pilot, aviation authority, legal advisor, licensed engineer, surveyor, insurance professional or other regulated professional.

16.6 AI Actions

Where available, an AI Feature may be permitted to carry out bounded actions within a User's Account, such as creating a draft or reminder, preparing a Mission draft, sending a communication the User has authorized, or updating a workflow within configured permissions.

DroneJob may process records concerning the requested action, authorizing User, result, approval and timestamp. These records support transparency, safety and auditability.

16.7 Customer control and permissions

Organizations may be able to control which AI Features are enabled, what information they may access, which Users may use them, which actions are permitted and whether approval is required.

Enterprise governance controls may differ by plan and agreement.

16.8 Third-party AI providers

DroneJob may use third-party AI providers or models to provide AI functionality.

Where they process Customer Data on DroneJob's behalf, DroneJob will treat them as service providers/subprocessors as appropriate.

DroneJob should disclose applicable AI subprocessors through its subprocessor documentation when required.

16.9 General-purpose model training

As a default trust principle:

DroneJob does not 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 other customers unless the applicable Customer has expressly opted in or a separate written agreement expressly permits that use.

DroneJob may use:

• de-identified information;
• aggregated information;
• Usage Data;
• AI performance metrics;
• User feedback;

to evaluate and improve the Services, subject to the practices described in this Privacy Policy.

DroneJob will not attempt to re-identify information that has been properly de-identified for such purposes.

16.10 Customer-specific AI assistance

DroneJob may use authorized Customer Data to provide or improve an AI experience specifically for that Customer, such as retrieving that Customer's service catalog or referencing approved business policies.

Such processing does not mean that the underlying Customer Data becomes training material for a general-purpose model used for the benefit of unrelated Customers.

16.11 User feedback on AI

DroneJob may collect information about acceptance, rejection, editing, rating or reported errors of AI Outputs in order to evaluate feature performance and improve safety. Where possible, improvement should rely on Usage Data, evaluation signals or appropriately de-identified information rather than exposing unrelated Customers' private content.

16.12 AI logs and retention

DroneJob may retain AI-related records such as prompts, Inputs, Outputs, actions, approvals and performance signals where reasonably necessary to provide the feature, troubleshoot, investigate abuse, maintain auditability or improve the Services. Retention should be proportionate to the purpose and addressed under Section 28.

16.13 User-connected external AI tools

If DroneJob later allows a Customer to connect its own AI provider, model, agent or API key, the Customer may direct DroneJob to transmit information to that provider.

Once information is sent to a separately controlled provider at the Customer's direction, that provider's agreement and privacy practices may govern its processing.

DroneJob should clearly distinguish:

• DroneJob-provided AI Features;
• Customer-connected external AI tools.

16.14 Sensitive information and AI

Users should avoid submitting unnecessary highly sensitive information to AI Features. DroneJob may establish additional restrictions concerning government IDs, financial credentials, passwords, health data, children's data or other specially regulated information.

16.15 AI and automated profiling

Where AI or automated techniques materially affect marketplace visibility, qualification, enterprise eligibility or another significant User outcome, DroneJob should evaluate whether applicable law requires additional notice, explanation, human review or an appeal or correction mechanism.

16.16 Changes to AI practices

AI technologies and providers evolve rapidly.

If DroneJob materially changes how private Customer Data is used for AI model training or similar purposes, DroneJob should:

• update this Privacy Policy;
• provide notice where required;
• obtain consent where applicable;
• respect contractual Enterprise commitments.

17.1 Subscription and billing information

DroneJob may process information such as:

This may include subscription plan, billing cycle, subscription status, and other related information depending on the Services used.

17.2 Payment instruments

DroneJob may use third-party payment processors to process:

• credit cards;
• debit cards;
• bank payments;
• other supported payment methods.

Where a payment processor handles the payment instrument directly, DroneJob may not receive or store the full underlying card or bank-account credentials.

Instead, DroneJob may receive information such as:

• payment-method type;
• last four digits;
• tokenized identifier;
• expiration information where provided;
• processor reference;
• payment status.

The exact information depends on the applicable payment processor and payment method.

17.3 Marketplace transactions

Where DroneJob supports marketplace payments, DroneJob may process information concerning:

This may include Client, Pilot or DSP, Mission, and other related information depending on the Services used.

This information may be associated with Mission and business records.

17.4 Pilot and provider payouts

Where DroneJob facilitates payouts, information may include:

This may include payout account reference, payout amount, payout status, and other related information depending on the Services used.

Payment providers may independently require identity, tax, banking or compliance information.

Where the provider collects that information directly, its privacy policy also applies to that processing.

17.5 Invoices and business financial records

DroneJob productivity tools may allow Users to create or manage records such as:

This may include invoices, estimates, payment status, and other related information depending on the Services used.

Some of this information may be Customer Data maintained by the User for their own business purposes.

17.6 Enterprise billing

Enterprise Customers may provide information relating to:

This may include billing contacts, purchase-order numbers, cost centers, and other related information depending on the Services used.

17.7 Tax-related information

DroneJob or its payment providers may collect tax-related information where required to:

• process payments;
• issue required tax documents;
• verify businesses;
• comply with reporting requirements.

The information required varies based on:

• jurisdiction;
• account type;
• transaction type;
• applicable law.

17.8 Fraud, disputes and payment security

Payment-related information may be processed to:

This may include prevent fraud, identify suspicious transactions, resolve disputes, and other related information depending on the Services used.

17.9 Financial data restrictions

Users should not place unnecessary financial credentials into:

• free-text notes;
• Conversations;
• Mission descriptions;
• AI prompts;
• uploaded files.

For example, Users should not intentionally submit:

• full card credentials;
• online banking passwords;
• private payment credentials;

unless the specific secure feature is designed to receive that information.

17.10 Payment providers

Payment processors and financial providers may act as independent controllers or service providers depending on the particular processing activity.

Their privacy practices may apply in addition to this Privacy Policy.

18.1 Device and browser information

Depending on how the Services are accessed, information may include:

This may include device type, browser type, operating system, and other related information depending on the Services used.

DroneJob should not describe a persistent device identifier as collected unless the applicable application actually collects it.

18.2 Network and connection information

DroneJob may process:

• IP address;
• connection timestamp;
• network information;
• approximate region derived from network information;
• request metadata.

Approximate location derived from IP or network information is distinct from precise device GPS information described in Section 10.

18.3 Usage information

DroneJob may collect information about how Users interact with the Services, including:

This may include pages viewed, screens opened, features used, and other related information depending on the Services used.

18.4 SaaS usage and entitlement information

DroneJob may record information required to administer plan features and usage limits, including:

This may include AI consumption; storage consumption; message activity; and other related information depending on the Services used.

This information may be used to:

• operate subscriptions;
• display usage;
• enforce limits;
• calculate disclosed usage charges;
• plan platform capacity.

18.5 API and Integration telemetry

Where APIs or Integrations are used, technical data may include:

This may include API endpoint, request timestamp, Customer/Organization, and other related information depending on the Services used.

DroneJob should avoid unnecessarily logging sensitive payload contents solely for technical monitoring.

18.6 Application logs

DroneJob may generate logs relating to:

This may include errors, crashes, authentication, and other related information depending on the Services used.

18.7 Diagnostic information

Diagnostic information may include:

This may include error codes, stack traces, failure state, and other related information depending on the Services used.

Where diagnostic information contains personal or Customer information, DroneJob should apply appropriate access and retention controls.

18.8 Security telemetry

DroneJob may process information to detect or investigate:

This may include unauthorized access, credential abuse, suspicious login, and other related information depending on the Services used.

18.9 Observability information

DroneJob may measure system and business-health indicators such as:

This may include system availability, API latency, application error rates, and other related information depending on the Services used.

Observability information may be linked to an Account, Organization, Mission or request where needed to investigate or support a specific issue.

18.10 Push notification information

Where mobile push notifications are supported, DroneJob may process:

• push-notification token;
• application identifier;
• device/platform information;
• notification-delivery information.

A push token should be used for notification delivery and related security/operational purposes.

18.11 Cookies and similar technologies

Some technical or usage information may be collected through:

• cookies;
• local storage;
• analytics technologies;
• similar technologies.

Detailed cookie and similar-technology practices appear in the Cookie Policy and are summarized in Section 27.

https://www.dronejob.ai/cookie-policy

18.12 Data minimization in logs

DroneJob should design technical logs to avoid recording unnecessary:

• message bodies;
• private Client content;
• payment credentials;
• authentication secrets;
• government identification;
• confidential file contents.

Where sensitive information is incidentally captured during debugging or incident response, access should be appropriately restricted.

19.1 Information provided directly by you

DroneJob may receive information when you:

This may include create an Account, build a profile, upload files, and other related information depending on the Services used.

19.2 Information provided by another DroneJob User

Another User may provide information about you.

Examples include:

• a Client identifying a site contact;
• an Organization inviting a Pilot;
• a DSP adding a contractor;
• a User submitting a review;
• a Client submitting an inquiry;
• an Enterprise Customer creating a vendor record.

The providing User is responsible for having appropriate authority to provide that information.

19.3 Information provided by Organizations and Enterprise Customers

Organizations may provide information concerning:

This may include employees, Authorized Users, Pilots, and other related information depending on the Services used.

DroneJob may process this information as Customer Data on the Organization's behalf.

19.4 Information from Clients and marketplace participants

Marketplace interactions may generate information including:

This may include inquiries, reviews, Mission requirements, and other related information depending on the Services used.

19.5 Information from Integrations and connected systems

DroneJob may receive information from authorized systems such as:

This may include ERP, CRM, GIS, and other related information depending on the Services used.

The Customer determines which Integrations it authorizes.

19.6 Identity and authentication providers

DroneJob may receive information from authentication providers, including:

• User identifier;
• email;
• name;
• authentication status;
• permitted account claims.

19.7 Verification and credential sources

Where appropriate, information may come from:

This may include credential issuers, aviation authorities, training providers, and other related information depending on the Services used.

19.8 Payment and billing providers

Payment providers may provide information concerning:

• payment status;
• transaction identifiers;
• payment method;
• payout status;
• verification status;
• disputes.

19.9 Communications providers

Communication providers may provide:

• delivery status;
• sender/recipient information;
• message identifiers;
• carrier status;
• opt-out status;
• communication metadata.

19.10 Public and professional sources

Where permitted, DroneJob may obtain professional or business information from publicly available or authorized sources.

Examples may include:

• business websites;
• professional directories;
• public license or credential information;
• publicly available organization information.

DroneJob should distinguish public-source information from DroneJob-verified information where necessary to avoid misleading Users.

19.11 Automatically generated information

DroneJob generates or receives technical information when Users use the Services as described in Section 18.

19.12 Derived or inferred information

DroneJob may derive information from existing records, for example:

This may include profile completeness, readiness indicator, marketplace relevance, and other related information depending on the Services used.

Where an inference is generated using AI, Section 16 also applies.

A derived indicator should not be represented as independently verified fact unless its underlying methodology supports that representation.

20.1 Provide and operate the Services

We use information to:

This may include create Accounts, authenticate Users, operate profiles, and other related information depending on the Services used.

20.2 Connect marketplace participants

We may use information to:

This may include help Clients find Pilots or DSPs, deliver inquiries, support matching, and other related information depending on the Services used.

20.3 Provide productivity and business-management tools

We may process information to help Users manage:

This may include leads, Clients, schedules, and other related information depending on the Services used.

20.4 Provide enterprise workflow functionality

We may use information to:

This may include process Orders, manage vendor networks, determine program eligibility, and other related information depending on the Services used.

20.5 Provide communications

We may use information to:

This may include send notifications, send email, send SMS, and other related information depending on the Services used.

20.6 Provide AI-supported functionality

Where enabled, we may process authorized information to:

• generate drafts;
• summarize;
• recommend;
• classify;
• assist workflow decisions;
• execute bounded authorized actions.

The AI practices and limitations described in Section 16 apply.

20.7 Process payments and subscriptions

We may process information to:

This may include bill subscriptions, manage entitlements, process payments, and other related information depending on the Services used.

20.8 Verify information and improve trust

We may process information to:

• verify identity;
• verify credentials;
• verify insurance;
• maintain badges;
• prevent fraudulent profiles;
• support enterprise vendor readiness.

20.9 Security and fraud prevention

We may use information to:

This may include authenticate, detect abuse, protect Accounts, and other related information depending on the Services used.

20.10 Support and troubleshooting

We may process information to:

• answer support requests;
• diagnose failures;
• restore Accounts;
• investigate delivery issues;
• troubleshoot Integrations;
• resolve disputes.

20.11 Analytics and product improvement

DroneJob may use information to understand:

• feature usage;
• platform performance;
• marketplace health;
• conversion;
• workflow effectiveness;
• system reliability.

Where feasible and appropriate, DroneJob should use:

• aggregated;
• de-identified;
• minimized;

information for broad analytics and benchmarking rather than unnecessary private Customer Content.

20.12 Improve AI Features

DroneJob may use:

• Usage Data;
• evaluation results;
• feedback;
• acceptance/rejection signals;
• appropriately de-identified or aggregated information;

to evaluate and improve AI functionality.

Private Customer Content remains subject to the AI training restrictions in Section 16.

20.13 Communications and marketing

DroneJob may use contact information to send:

• service communications;
• legally required notices;
• product notices;
• educational content;
• marketing communications;

in accordance with:

• applicable law;
• consent;
• preferences.

Marketing communication does not override the separate SMS consent rules in Section 13.

20.14 Legal and compliance purposes

DroneJob may process information to:

This may include comply with law, respond to legal process, maintain records, and other related information depending on the Services used.

20.15 Corporate operations

Information may be used for:

This may include accounting, financial reporting, audits, and other related information depending on the Services used.

20.16 Customer instructions

Where DroneJob acts as a processor or service provider on behalf of a Customer, DroneJob processes Customer Data to:

• provide the contracted Services;
• follow documented Customer instructions;
• maintain security;
• satisfy applicable legal obligations.

DroneJob should not independently repurpose Customer Data for unrelated activities inconsistent with the applicable relationship or agreement.

21.1 Performance of a contract

DroneJob may process information where necessary to:

This may include create an Account, provide requested Services, operate subscriptions, and other related information depending on the Services used.

21.2 Steps requested before entering a contract

DroneJob may process information where necessary to respond to:

• product inquiries;
• account-registration requests;
• enterprise sales requests;
• requests to engage DroneJob Services.

21.3 Legitimate interests

Where permitted by applicable law, DroneJob may process information for legitimate interests such as:

This may include securing the Services, preventing fraud, supporting Users, and other related information depending on the Services used.

When relying on legitimate interests, DroneJob should consider the impact on individuals and whether those interests are overridden by applicable privacy rights.

21.4 Consent

DroneJob may rely on consent for activities where consent is appropriate or required.

Examples may include:

• certain marketing communications;
• SMS messaging;
• optional device permissions;
• certain cookies;
• voluntary AI/data-use programs.

Where processing relies on consent, individuals may withdraw consent subject to:

• applicable law;
• technical limitations;
• processing already lawfully performed.

21.5 Legal obligation

DroneJob may process information where necessary to comply with:

• tax;
• accounting;
• regulatory;
• legal-process;
• recordkeeping;
• other legal obligations.

21.6 Protection of rights and legal claims

Where permitted, DroneJob may process information to:

• establish;
• exercise;
• defend;

legal rights or claims.

21.7 Vital interests or emergency circumstances

In rare circumstances, DroneJob may process information where permitted or required to protect a person's vital interests or respond to a serious emergency.

This basis should not be treated as a normal basis for DroneJob operations.

21.8 Customer-controlled processing

Where DroneJob acts as a processor/service provider for an Enterprise Customer, DSP or other business Customer:

the Customer generally determines the legal basis for its processing of the personal information contained in Customer Data.

DroneJob processes that information according to:

• Customer instructions;
• applicable DPA;
• applicable law.

Individuals with questions about processing controlled by a DroneJob Customer may need to contact that Customer directly.

21.9 Different terminology under different laws

Different privacy laws use different terminology and legal bases.

Nothing in this Section should be interpreted as asserting that GDPR terminology applies to every User worldwide.

DroneJob applies the legal framework appropriate to the relevant jurisdiction.

21.10 Public Task or Official Authority

Where applicable law provides and the relevant processing is carried out by or on behalf of a public authority, processing may in some circumstances rely on a legal basis connected with:

• performance of a task carried out in the public interest; or
• exercise of official authority.

Where DroneJob acts only as a Processor or Service Provider for a Public Sector Customer, the applicable Customer generally determines the lawful basis for the Customer's processing.

DroneJob does not assume that every governmental Customer relies on the same lawful basis.

Public task or official authority is not presented as DroneJob's general legal basis for its own commercial operations.

22.1 Public professional profiles

Where a User enables or participates in public profile functionality, information that may be displayed could include:

This may include name or professional name, profile photograph, business name, and other related information depending on the Services used.

The exact information displayed depends on:

• available features;
• User settings;
• applicable role;
• product rules.

22.2 Public marketplace discovery

Public or marketplace-visible information may be used to:

• appear in directory results;
• appear in geographic search;
• match with Clients;
• support marketplace recommendations;
• appear on vertical or service pages;
• support professional discovery.

22.3 Search engines

Public pages may be:

• indexed;
• cached;
• displayed;

by search engines.

Removing information from DroneJob does not guarantee immediate removal from:

• search-engine caches;
• third-party archives;
• copies previously made by others.

DroneJob will stop serving removed information from its own public surfaces as appropriate.

22.4 Private information is not automatically public

Information such as the following should not become publicly visible merely because a User has a public profile:

This may include CRM records, private Client information, private Conversations, and other related information depending on the Services used.

22.5 Verification indicators

DroneJob may publicly display limited verification information, such as:

Part 107 Verified
Insurance Verified
Identity Verified

The underlying sensitive source document need not be public.

Verification remains subject to the limitations described in Section 6 and the Terms of Service.

22.6 Portfolio visibility

Users may choose to display portfolio content.

Users are responsible for ensuring that portfolio content may lawfully and contractually be published.

A private Mission deliverable should not become public portfolio content merely because it is stored in DroneJob.

22.7 Reviews

Certain reviews or ratings may be publicly displayed.

DroneJob may also maintain private information used for:

• moderation;
• fraud detection;
• dispute handling.

22.8 Service area versus precise location

DroneJob may publicly display:

• city;
• region;
• service radius;
• general coverage area;

without displaying a Pilot's precise residential or current location.

Precise operational location is governed separately under Section 10.

22.9 Enterprise private directories

Enterprise Customers may use private:

• vendor pools;
• internal Pilot directories;
• qualification rosters.

Information visible within an enterprise environment is not necessarily public to the broader DroneJob Marketplace.

22.10 Aspiring or non-commercial Users

DroneJob may allow aspiring Users to maintain educational or career-development profiles without representing them as commercially verified or eligible.

DroneJob should distinguish:

• learning/career status;
• verified commercial eligibility;

where required to avoid misleading Clients.

22.11 Visibility changes

Where supported, Users may change:

• profile visibility;
• portfolio visibility;
• marketplace participation;
• other public settings.

Some information may continue to be retained privately where necessary for:

• Account history;
• security;
• legal requirements;
• business records.

23.1 Administrator access

Depending on the Services, configuration and permissions, an Organization administrator may be able to access or manage information such as:

This may include User identity and contact information, Organization membership, roles and permissions, and other related information depending on the Services used.

Administrator access is limited by the technical capabilities and authorization model of the applicable Services.

23.2 Organization-controlled accounts and contexts

Where an Account or Account context is provided, managed or paid for by an Organization, the Organization may have authority to:

• manage the User's Organization membership;
• change roles;
• suspend Organization access;
• remove the User;
• access Organization business records;
• preserve Organization records after the User leaves.

A User's separate personal DroneJob Account or personal professional profile does not automatically become Organization property merely because the User joins an Organization.

DroneJob should maintain reasonable separation between:

Personal DroneJob Context

and

Organization-Controlled Context

where the product supports both.

23.3 Enterprise administrators

Enterprise administrators may receive broader governance capabilities, including:

This may include security configuration, SSO configuration, provisioning, and other related information depending on the Services used.

Enterprise administrators should use such access only for authorized organizational purposes.

23.4 Public-sector administrators

Public-sector Organizations may designate administrators such as:

This may include agency administrators, IT administrators, procurement administrators, and other related information depending on the Services used.

DroneJob may process information according to the public-sector Customer's authorized configuration and contractual instructions.

The existence of administrator access does not itself authorize the Organization to use personal information in a manner prohibited by applicable:

• employment law;
• privacy law;
• public-sector regulation;
• internal policy;
• collective agreement;
• contract.

23.5 Organization access after User departure

When an Authorized User leaves an Organization, the Organization may continue to retain or access Organization business records created during that User's authorized work, including:

• Missions;
• Client records;
• files;
• communications;
• approvals;
• audit history.

The departing User may lose access to those records.

This does not necessarily affect information maintained independently in the User's personal DroneJob context.

23.6 Administrator auditability

DroneJob may record material administrative actions including:

This may include role changes, access grants, User removals, and other related information depending on the Services used.

These records may be used for:

• security;
• compliance;
• Customer administration;
• troubleshooting;
• investigations;
• public-sector accountability.

23.7 Government and public records obligations

Public-sector Customers may be subject to:

• freedom-of-information laws;
• public-records laws;
• records-retention schedules;
• litigation holds;
• government audit requirements.

DroneJob may process or preserve Organization information according to such Customer instructions and applicable law.

DroneJob does not determine whether a particular Customer record is legally subject to public disclosure.

The applicable public-sector Customer remains responsible for responding to its own public-records obligations unless a separate agreement expressly allocates responsibilities differently.

24.1 Other DroneJob marketplace participants

Where necessary to facilitate marketplace interactions, information may be disclosed between:

• Clients;
• Pilots;
• DSPs;
• other authorized marketplace participants.

For example, a Client inquiry may be made available to the Pilot or DSP contacted by the Client.

24.2 Mission and project participants

Information may be made available to authorized participants in a Mission or project, including:

This may include Client representatives, Pilots, DSPs, and other related information depending on the Services used.

Access should reflect the participant's role and business need.

24.3 Organizations and administrators

Information associated with an Organization environment may be disclosed or made available to the Organization and its authorized administrators as described in Section 23.

24.4 Service providers and subprocessors

DroneJob may disclose information to providers that assist with functions such as:

This may include infrastructure, storage, authentication, and other related information depending on the Services used.

Providers receive information according to their function and applicable contractual obligations.

Section 25 provides additional information regarding subprocessors.

24.5 Connected Third-Party Services

Where a Customer or User enables an Integration, DroneJob may disclose information to the connected service within the authorized scope.

Examples may include:

This may include ERP, CRM, GIS, and other related information depending on the Services used.

The connected provider's privacy practices may apply after the information is transferred to that independently controlled service.

24.6 Customer-directed disclosures

DroneJob may disclose information where a Customer instructs DroneJob to do so.

Examples may include:

• exporting Mission information;
• sending deliverables to a Client;
• sharing a vendor record;
• transmitting information through an API;
• providing information to an approved enterprise system.

24.7 Public information

Information intentionally designated for public display may be disclosed publicly as described in Section 22.

24.8 Professional and business advisers

DroneJob may disclose information where reasonably necessary to:

• legal counsel;
• auditors;
• accountants;
• insurers;
• professional advisers;

subject to appropriate obligations.

24.9 Legal, regulatory and safety disclosures

DroneJob may disclose information where reasonably necessary to:

This may include comply with law, respond to valid legal process, respond to government or regulatory requests, and other related information depending on the Services used.

DroneJob may evaluate legal requests according to applicable law.

24.10 Public-sector Customer disclosures

Where DroneJob provides Services to a public-sector Customer, information may be disclosed:

• at that Customer's lawful direction;
• to authorized government personnel;
• for audits;
• for records-management purposes;
• where applicable law requires.

A public-sector Customer's disclosure of its own records under open-records or freedom-of-information law is generally controlled by that Customer and applicable law rather than DroneJob's general privacy choices.

24.11 Business transactions

Information may be disclosed in connection with a proposed or completed:

• merger;
• acquisition;
• financing;
• restructuring;
• asset sale;
• corporate transaction.

DroneJob will handle personal information according to applicable law during such transactions.

24.12 Mobile messaging information

The restrictions in Section 13 continue to apply.

DroneJob does not sell or disclose:

• mobile telephone numbers;
• SMS opt-in information;
• SMS consent information;

to third parties or affiliates for their own marketing or promotional purposes.

25.1 Types of providers

DroneJob may use providers for functions including:

This may include cloud hosting, databases, object/file storage, and other related information depending on the Services used.

25.2 Provider access

A provider should receive access only to information reasonably necessary for its role.

Provider access may vary significantly.

For example:

Email Provider
→ receives information necessary to deliver email

Storage Provider
→ stores authorized Customer files

AI Provider
→ may receive authorized AI Inputs required for a requested feature

Payment Provider
→ receives payment-related information required for transactions

25.3 Contractual safeguards

Where required, DroneJob will impose appropriate contractual requirements relating to:

This may include confidentiality, security, permitted processing, and other related information depending on the Services used.

25.4 Subprocessor list

DroneJob should maintain a current public or contract-accessible list of material Subprocessors used to process Customer Data.

The future preferred location is:

https://trust.dronejob.ai/subprocessors

or an equivalent DroneJob-controlled legal/trust URL.

Do not create this route as part of this task unless it already exists.

25.5 Information included in the future list

Where appropriate, the Subprocessor list should identify:

• provider name;
• service/function;
• processing location or relevant region;
• categories of processing where useful.

Do not expose confidential infrastructure details that would create unnecessary security risk.

25.6 Subprocessor changes

Enterprise Customers may receive:

• advance notice;
• objection rights;
• other contractual rights;

regarding new Subprocessors where required under a DPA or negotiated Enterprise Agreement.

The general Privacy Policy does not create broader objection rights than those contained in applicable law or contract.

25.7 Residency-sensitive Customers

A Customer with contractual data-residency requirements should evaluate the Subprocessors applicable to the contracted Services.

DroneJob may:

• restrict certain providers;
• configure regional services;
• disable incompatible features;
• provide alternative processing;

where expressly supported and agreed.

A residency commitment applies only to the categories and Services expressly covered by the applicable agreement.

25.8 AI subprocessors

Where DroneJob uses an external AI provider to process private Customer Data on DroneJob's behalf, the provider should be governed as an applicable Subprocessor.

DroneJob's previously approved restrictions on general-purpose model training of private Customer Data continue to apply.

25.9 Public-sector restrictions

Certain public-sector Customers may require:

• approved vendor lists;
• domestic processing;
• personnel restrictions;
• data-location restrictions;
• security review.

DroneJob may accommodate such requirements only where expressly accepted in the applicable contract.

The existence of the general commercial Service does not imply that every Subprocessor satisfies every public-sector standard.

26.1 Aggregated information

Aggregated information may combine information from multiple Users, Customers, Missions or transactions.

Examples may include:

This may include number of Pilots in a geographic region, marketplace demand by service category, average response time, and other related information depending on the Services used.

26.2 De-identified information

DroneJob may transform information so that it no longer reasonably identifies:

• an individual;
• Customer;
• Client;
• specific confidential project;

when used as de-identified information.

Where DroneJob represents information as de-identified, DroneJob should take reasonable measures not to re-identify it except where necessary to test or validate de-identification techniques as permitted by law.

26.3 Derived information

DroneJob may generate derived information such as:

• profile completeness;
• marketplace relevance;
• readiness indicators;
• workflow metrics;
• operational performance measures;
• aggregate demand indicators.

Derived information relating to an identifiable User may remain personal information and is treated accordingly.

26.4 Product improvement

Aggregated or appropriately de-identified information may be used for:

This may include analytics, capacity planning, product development, and other related information depending on the Services used.

26.5 Industry insights

DroneJob may develop industry-level insights regarding topics such as:

• Pilot availability;
• regional service supply;
• aggregate pricing trends;
• skills demand;
• service-category demand;
• enterprise procurement patterns.

DroneJob should design such insights to avoid revealing confidential information belonging to a particular Customer or public-sector project.

26.6 Enterprise benchmarking

Where offered, benchmarking may allow an Enterprise Customer to compare its operations with aggregated market or peer information.

DroneJob must not represent confidential data from another identifiable Customer as benchmarking data unless authorized.

26.7 Public-sector and sensitive infrastructure information

DroneJob should apply heightened care before using data associated with:

• public infrastructure;
• utilities;
• government facilities;
• security-sensitive assets;
• emergency-response operations;

for external benchmarking or public insights.

Aggregation alone may not be sufficient where a small dataset could reveal a sensitive Customer or facility.

26.8 AI improvement

Use of aggregated and de-identified information for AI evaluation or improvement remains subject to Section 16.

Private Customer Data does not become eligible for unrestricted general-model training merely because DroneJob can technically derive metrics from it.

27.1 Strictly necessary technologies

These may be used for purposes such as:

• authentication;
• session management;
• security;
• load balancing;
• preferences necessary to operate the Service;
• fraud prevention.

Where applicable law permits, these technologies may operate without optional consent because they are necessary to provide the requested Service.

27.2 Preference technologies

DroneJob may use technologies to remember choices such as:

• language;
• region;
• display preferences;
• interface configuration.

27.3 Analytics technologies

DroneJob may use analytics technologies to understand:

This may include page usage, product navigation, feature adoption, and other related information depending on the Services used.

DroneJob should configure analytics to minimize unnecessary exposure of private Customer Content.

27.4 Marketing and attribution technologies

On public marketing surfaces, DroneJob may use technologies to understand:

• campaign effectiveness;
• referral source;
• advertising attribution;
• marketing engagement.

DroneJob should not intentionally expose private:

• Mission content;
• Client CRM data;
• communications;
• confidential enterprise data;

to advertising technologies merely for marketing purposes.

27.5 Authenticated application environments

DroneJob should use greater restraint with advertising and marketing trackers inside authenticated productivity, Mission and enterprise environments.

In particular, sensitive Customer workflows should not be treated like public marketing pages.

27.6 Public-sector environments

Where a Public Sector Customer's agreement or security requirements prohibit:

• advertising technologies;
• non-essential tracking;
• particular analytics providers;

DroneJob may restrict those technologies for the applicable contracted environment where supported.

27.7 Cookie choices

Where required by applicable law, DroneJob will provide appropriate choices concerning non-essential cookies or similar technologies.

The Cookie Policy describes current technologies and available browser controls.

https://www.dronejob.ai/cookie-policy

Choices may vary by:

• jurisdiction;
• site;
• technology;
• Service.

27.8 Browser signals

Where legally required or supported, DroneJob may recognize applicable privacy preference signals such as Global Privacy Control.

Do not claim support for a specific signal unless the implementation currently supports it or is being implemented.

27.9 Do Not Track

Browser "Do Not Track" mechanisms have not historically had a uniform industry standard.

Do not make a specific DNT commitment unless DroneJob has implemented a defined response.

27.10 Third-party analytics

Third-party analytics providers may process technical information according to their role and applicable agreements.

Where they act as DroneJob service providers, applicable contractual requirements apply.

28.1 Account information

Account information may generally be retained:

• while the Account is active;
• as necessary to provide the Services;
• for a reasonable period after termination where needed for legal, security or business purposes.

28.2 Organization and Customer Data

Customer Data may be retained for:

• the duration of the Customer relationship;
• a contractual export or transition period;
• applicable backup periods;
• legal or regulatory requirements.

Enterprise agreements or DPAs may provide more specific retention or deletion commitments.

28.3 Mission and business records

Mission records may need to be retained to support:

This may include Client history, deliverables, evidence, and other related information depending on the Services used.

28.4 Communications

Communications may be retained as part of:

• Conversation history;
• Mission history;
• CRM history;
• dispute records;
• compliance records.

28.5 Consent records

DroneJob may retain evidence of:

• SMS consent;
• marketing consent;
• opt-outs;
• communication preferences;

for a period sufficient to demonstrate compliance and honor suppression preferences.

An opt-out record may need to remain after other Account information is deleted so that DroneJob does not inadvertently resume prohibited messaging.

28.6 Financial and transaction records

Billing, payment and tax-related records may be retained according to:

• accounting requirements;
• tax law;
• payment disputes;
• fraud-prevention needs.

28.7 Verification information

Verification records may be retained according to the principles in Section 6, including as needed to:

• demonstrate prior verification;
• detect fraud;
• manage expiration;
• resolve disputes.

Sensitive source documents should not be retained longer than reasonably necessary merely because a verification status exists.

28.8 Security and audit records

DroneJob may retain:

• security events;
• administrative activity;
• audit logs;
• fraud records;

for periods appropriate to security, compliance and investigative purposes.

28.9 AI records

AI Inputs, Outputs, actions and related audit information may have retention periods appropriate to:

• User context;
• feature functionality;
• troubleshooting;
• auditability;
• security.

Enterprise agreements may impose additional restrictions.

28.10 Public-sector retention

Public-sector Customers may be subject to legally mandated retention schedules.

A public-sector Customer may instruct DroneJob to preserve records for:

• statutory retention;
• litigation hold;
• public-records requirements;
• audit;
• investigation.

DroneJob may be unable to fulfill a deletion request where retention is required by applicable law or valid Customer instruction.

28.11 Legal holds

DroneJob may preserve otherwise deletable information where reasonably necessary because of:

• litigation;
• investigation;
• subpoena;
• regulatory obligation;
• preservation request.

28.12 Backups

Deleted information may remain temporarily in:

• encrypted backups;
• disaster-recovery systems;
• system snapshots;

until those systems cycle according to applicable retention practices.

Backup copies should remain protected and not be restored for normal business use except as necessary for recovery or legal purposes.

28.13 Customer export

Where provided by the applicable plan or agreement, Customers may export Customer Data before termination or deletion.

Specific enterprise export periods may be defined in applicable Additional Terms.

28.14 Deletion requests

Deletion rights are subject to:

• applicable privacy law;
• Customer controller instructions;
• security verification;
• legal exceptions;
• retention obligations.

Where DroneJob acts as a processor for Customer Data, a data-subject request may need to be directed to the applicable Customer.

29.1 Security program

DroneJob's security program may include measures concerning:

This may include access control, authentication, authorization, and other related information depending on the Services used.

29.2 Encryption

DroneJob should use industry-appropriate encryption:

• in transit;
• at rest where appropriate to the applicable system/data.

Do not specify algorithms or certifications in the Privacy Policy unless confirmed and approved.

29.3 Identity and access management

Security controls may include:

This may include unique User identities, role-based access, least privilege, and other related information depending on the Services used.

29.4 Tenant and Organization separation

DroneJob should apply technical authorization controls intended to prevent one Customer or Organization from improperly accessing another Customer's restricted information.

29.5 Security monitoring

DroneJob may monitor for:

• unauthorized access;
• account compromise;
• malicious activity;
• suspicious API use;
• application failures;
• potential abuse.

29.6 Secure development

DroneJob may employ practices such as:

This may include code review, dependency management, vulnerability scanning, and other related information depending on the Services used.

Do not turn this Privacy Policy into a detailed security-control catalogue.

A future Trust Center or security documentation should provide technical detail.

29.7 Incident response

DroneJob maintains or intends to maintain procedures for:

• investigating security incidents;
• containing incidents;
• remediating issues;
• notifying affected Customers or individuals where required.

Specific contractual breach-notification periods should be placed in:

• DPA;
• Enterprise Agreement;
• security addendum;

rather than invented in this general Privacy Policy.

29.8 Customer responsibilities

Security is a shared responsibility.

Customers and Users are responsible for matters such as:

This may include protecting credentials, properly configuring permissions, managing administrators, and other related information depending on the Services used.

29.9 Public-sector security requirements

Public-sector Customers may require specific controls beyond DroneJob's standard commercial security program.

Such requirements may be addressed through:

• security exhibits;
• Order Forms;
• procurement requirements;
• Customer-specific configuration;
• approved service environments.

DroneJob must not represent that the general commercial Service satisfies a government security framework unless the applicable service has actually been assessed or authorized for that framework.

29.10 Sensitive infrastructure

Customers using DroneJob for:

• utilities;
• telecommunications;
• public infrastructure;
• government facilities;
• security-sensitive projects;

should apply appropriate Organization access controls and contractual safeguards.

29.11 Security documentation

DroneJob may eventually provide additional information through a Trust Center concerning:

• security;
• subprocessors;
• compliance;
• data residency;
• security contacts.

The future preferred architecture is:

trust.dronejob.ai

Do not create or promise certifications that do not currently exist.

30.1 Standard commercial processing

Unless DroneJob has expressly agreed to a specific data-residency commitment, information may be processed in:

• the United States;
• other locations in which DroneJob or its authorized providers operate.

DroneJob should not publish a more specific default location statement unless it has been verified against the production architecture and current Subprocessor list.

30.2 Contractual data-residency options

DroneJob may offer or negotiate data-residency options for eligible Enterprise or Public Sector Customers.

A residency commitment should identify, as appropriate:

This may include region/country, Services covered, categories of Customer Data covered, and other related information depending on the Services used.

A data-residency commitment exists only where DroneJob expressly agrees to it in applicable documentation such as:

• Order Form;
• Enterprise Agreement;
• DPA;
• data-residency exhibit.

30.3 Storage residency versus processing/access residency

A commitment that Customer Data is stored in a particular region does not necessarily mean that no processing or access occurs outside that region.

For example, unless the applicable agreement states otherwise, processing may occur for:

This may include authentication, security, support, and other related information depending on the Services used.

Where a Customer requires both:

data-at-rest residency

and

processing/access residency,

that requirement should be expressly documented.

30.4 European Economic Area, United Kingdom and Switzerland

Where personal information protected by European, UK or Swiss data-protection law is transferred internationally, DroneJob will use an appropriate transfer mechanism where required.

Depending on the circumstances, mechanisms may include:

• European Commission Standard Contractual Clauses;
• UK transfer addendum or other UK-approved mechanism;
• another legally recognized transfer mechanism.

DroneJob must not claim participation in the EU-U.S. Data Privacy Framework unless DroneJob has actually completed and maintains the required certification.

30.5 GDPR and residency

GDPR compliance does not automatically require that all personal information remain physically within the European Union.

DroneJob may nevertheless agree to European residency where required by:

• Customer contract;
• public procurement;
• sector requirement;
• security policy;
• other legitimate business requirement.

30.6 Brazil and other jurisdictions

DroneJob may implement appropriate international-transfer measures under laws such as Brazil's LGPD and other applicable data-protection laws as the Services expand internationally.

Do not state that a specific legal transfer mechanism is in place until verified.

30.7 Public-sector and government residency

Public-sector Customers may require information to remain:

• within a particular country;
• within a specific region;
• within approved facilities or providers.

DroneJob may agree to such restrictions in writing where its architecture supports them.

Public-sector Customers are responsible for communicating required:

• data classification;
• residency;
• sovereignty;
• personnel/access restrictions;

during procurement or onboarding.

30.8 Restricted government information

Customers must not submit information requiring a security authorization or environment that DroneJob has not expressly agreed and documented as supporting.

This may include, depending on applicable requirements:

• classified information;
• CUI requiring a specified authorized environment;
• export-controlled information;
• other specially regulated government data.

30.9 FedRAMP distinction

Data residency in the United States does not mean that a service is FedRAMP authorized.

Unless DroneJob expressly identifies a particular service environment as holding a FedRAMP authorization, DroneJob does not represent that the general DroneJob commercial platform is FedRAMP authorized.

If DroneJob later launches a separately authorized government environment, that environment should be:

• separately identified;
• separately documented;
• subject to applicable Government Additional Terms.

30.10 Customer-enabled exports and Integrations

A Customer may cause information to leave an agreed residency region by:

• exporting data;
• downloading files;
• connecting an Integration;
• sending an email;
• using a communications channel;
• connecting an external AI provider.

Customers are responsible for considering their own residency and security requirements when enabling such actions.

30.11 Subprocessors

Regional commitments may depend on the Subprocessors used to provide the applicable Service.

Section 25 describes DroneJob's Subprocessor framework.

30.12 Future regional architecture

DroneJob may add or modify regional hosting options as the platform grows.

The existence of one regional environment does not imply availability in every region or for every feature.

31.1 Access

Where applicable, you may have the right to request information concerning personal information DroneJob processes about you.

Depending on applicable law, this may include information concerning:

• categories of personal information;
• specific personal information;
• sources;
• purposes;
• categories of recipients;
• retention;
• automated processing;
• other information required by law.

31.2 Correction

You may have the right to ask DroneJob to correct inaccurate or incomplete personal information.

Some information can be updated directly through your Account.

Other information may require:

• verification;
• Customer administrator action;
• support review;
• credential re-verification.

A User may not use a correction request to cause DroneJob to falsify:

• historical records;
• audit records;
• transaction history;
• verification history.

Where appropriate, DroneJob may preserve the historical record while correcting the currently displayed information.

31.3 Deletion

You may have the right to request deletion of personal information, subject to applicable exceptions.

DroneJob may need to retain information for purposes including:

• legal obligations;
• security;
• fraud prevention;
• tax/accounting;
• contractual obligations;
• Mission records;
• dispute resolution;
• public-sector retention;
• legal hold;
• protection of rights.

Deletion of an Account does not necessarily require immediate deletion of every record associated with that Account.

Section 28 describes retention in greater detail.

31.4 Restriction of processing

Where applicable law provides, you may have the right to request that processing of certain personal information be restricted.

A restriction may affect the ability to use certain DroneJob Services.

31.5 Objection

Where applicable, you may have the right to object to certain processing based on:

• legitimate interests;
• direct marketing;
• other grounds provided by applicable law.

DroneJob will evaluate an objection in accordance with the applicable legal standard.

31.6 Data portability

Where applicable law provides, you may have the right to receive certain personal information in a:

• structured;
• commonly used;
• machine-readable;

format.

The scope of portability may differ from DroneJob's broader business-data export functionality.

For example:

GDPR personal-data portability
≠
Enterprise export of every Mission file and system record

Enterprise Customer Data export may separately be governed by:

• plan;
• Order Form;
• Enterprise Agreement;
• EU Data Act obligations where applicable;
• other contractual requirements.

31.7 Withdrawal of consent

Where DroneJob relies on consent, you may withdraw that consent.

Withdrawal does not invalidate processing lawfully performed before the withdrawal.

Withdrawal may prevent access to functionality requiring the consent.

Examples may include:

• optional marketing;
• SMS;
• certain cookies;
• device permissions;
• voluntary data-use programs.

31.8 Communication choices

Users may manage communications using available controls.

Examples include:

SMS

Reply:

STOP

to applicable DroneJob SMS messaging programs.

Email marketing

Use the unsubscribe mechanism contained in applicable marketing email.

Service communications

Certain operational or legally required communications may continue where necessary to:

• operate the Account;
• provide requested Services;
• maintain security;
• satisfy legal obligations.

31.9 Public profile choices

Where supported, Users may be able to control:

• profile visibility;
• marketplace participation;
• portfolio visibility;
• public professional information.

Disabling public visibility does not automatically delete information DroneJob needs to retain privately for other lawful purposes.

31.10 Device permissions

Users may control certain permissions through:

• mobile-device settings;
• browser settings;
• application controls.

Examples may include:

• location;
• notifications;
• camera;
• photographs/files.

Disabling a required permission may prevent a feature from functioning.

31.11 Cookie and analytics choices

Where legally required and technically supported, DroneJob will provide controls relating to non-essential:

• cookies;
• analytics;
• marketing technologies.

Section 27 and the Cookie Policy describe these technologies.

https://www.dronejob.ai/cookie-policy

Do not claim a specific cookie-management implementation if the website does not yet provide it.

31.12 Artificial intelligence choices

Where supported, Organizations or Users may be able to:

• enable or disable certain AI Features;
• restrict AI access;
• restrict AI actions;
• require approval;
• control connected external AI providers.

Enterprise Customers may receive additional AI governance options under applicable plans or agreements.

31.13 Automated decision rights

Applicable law may provide rights relating to decisions based solely on automated processing where those decisions produce:

• legal effects; or
• similarly significant effects.

Where such rights apply, an individual may be entitled to protections such as:

• information about the processing;
• human review;
• ability to express a viewpoint;
• ability to challenge the result;
• other rights required by law.

DroneJob should not characterize ordinary:

• recommendations;
• search ranking;
• productivity suggestions;
• draft generation;

as legally significant automated decision-making unless the actual use and applicable law support that characterization.

31.14 United States state privacy rights

Residents of certain U.S. states may have rights such as:

• knowing/accessing personal information;
• correcting inaccurate information;
• deleting information;
• receiving portable copies;
• opting out of certain sales;
• opting out of certain sharing or targeted advertising;
• limiting certain uses of sensitive personal information;
• opting out of qualifying profiling;
• appealing certain request decisions;
• exercising rights without unlawful discrimination.

The rights available depend on the applicable state law and whether that law applies to DroneJob.

DroneJob should not claim that it:

• sells personal information;
• shares personal information for cross-context behavioral advertising;
• uses sensitive personal information beyond permitted purposes;

unless actual current practices support those statements.

If DroneJob begins engaging in processing that triggers specific opt-out requirements, appropriate:

• notices;
• links;
• preference mechanisms;

must be implemented.

31.15 California rights

Where the California Consumer Privacy Act, as amended, applies, eligible California residents may have rights including:

• right to know;
• right to access;
• right to correct;
• right to delete;
• right to opt out of qualifying sale or sharing;
• right to limit qualifying use/disclosure of sensitive personal information;
• right to non-discrimination.

A California resident may also use an authorized agent where permitted.

Do not add a "Do Not Sell or Share My Personal Information" link unless DroneJob's actual practices and legal obligations require that link.

31.16 European Economic Area, United Kingdom and Switzerland

Where GDPR, UK GDPR or equivalent applicable law applies, individuals may have rights such as:

• access;
• rectification;
• erasure;
• restriction;
• portability;
• objection;
• withdrawal of consent;
• protections regarding certain automated decision-making.

Individuals may also have the right to lodge a complaint with the competent supervisory authority.

31.17 Brazil

Where Brazil's LGPD applies, eligible individuals may have rights that can include:

• confirmation of processing;
• access;
• correction;
• anonymization, blocking or deletion of qualifying unnecessary or unlawfully processed information;
• portability where applicable;
• information about sharing;
• withdrawal of consent;
• deletion of qualifying consent-based information;
• objection where legally available;
• review or information regarding qualifying automated decisions.

Rights are subject to applicable LGPD rules and exceptions.

31.18 Other jurisdictions

Additional privacy rights may exist in:

• Canada;
• other U.S. states;
• Latin American jurisdictions;
• European jurisdictions;
• other supported markets.

DroneJob will process qualifying requests according to applicable law.

31.19 Where DroneJob acts as Processor or Service Provider

If the information at issue is Customer Data controlled by:

• an employer;
• DSP;
• Enterprise Customer;
• Client Organization;
• Public Sector Customer;

DroneJob may refer the request to that Customer or instruct the individual to contact the Customer.

Example:

Enterprise employee
       ↓
requests deletion of employer Mission records
       ↓
Enterprise = Controller
DroneJob = Processor

DroneJob generally should not override the Customer's lawful instructions merely because the data subject contacts DroneJob directly.

DroneJob will assist Customers with qualifying requests as required by:

• law;
• applicable DPA;
• Enterprise Agreement.

31.20 Identity verification

DroneJob may request information reasonably necessary to verify:

• identity;
• authority;
• jurisdiction;
• scope of the request.

DroneJob should avoid collecting unnecessary verification information.

31.21 Authorized agents

Where legally permitted, an individual may authorize another person or entity to submit a request on their behalf.

DroneJob may require reasonable evidence of that authority.

31.22 Appeals

Where applicable privacy law provides an appeal right, DroneJob will provide an appropriate method for appealing a denied qualifying request.

Do not create a dedicated appeal workflow in legal copy unless one actually exists.

31.23 No unlawful discrimination

DroneJob will not unlawfully discriminate against an individual for exercising an applicable privacy right.

The exercise of a right may nevertheless affect a feature where the information is genuinely necessary to provide that feature.

31.24 Requests and response periods

DroneJob will respond to qualifying privacy requests within the period required by applicable law.

Do not publish one global response period because different laws establish different deadlines.

31.25 Supervisory and regulatory complaints

Where applicable, individuals may have the right to contact a:

• data-protection authority;
• privacy regulator;
• attorney general;
• consumer-protection authority;
• other competent regulator.

DroneJob encourages individuals to contact DroneJob first where appropriate so that we have an opportunity to address the concern, but doing so does not waive a legally available complaint right.

32.1 Commercial Service eligibility

Unless DroneJob expressly offers a separate youth or educational experience, Users participating in:

• commercial marketplace activity;
• service contracting;
• paid Missions;
• payments;
• professional service delivery;

must satisfy the age and contractual-capacity requirements described in the Terms of Service.

The current Terms generally require a User of commercial contracting functionality to be:

at least 18 years old or the legal age of majority in the applicable jurisdiction, whichever is higher.

32.2 Children under 13

DroneJob's general commercial Services are not directed to children under 13.

DroneJob does not knowingly seek personal information from children under 13 through the general commercial Services.

If DroneJob learns that information from a child under 13 was improperly collected through those Services, DroneJob will take appropriate steps consistent with applicable law.

32.3 Teen and aspiring Pilot users

DroneJob may in the future offer:

• educational materials;
• career exploration;
• training;
• community;
• school programs;

that could be relevant to individuals who are not yet eligible for commercial marketplace activity.

Such functionality must not automatically grant the individual access to:

• commercial contracting;
• paid Mission acceptance;
• unrestricted Client engagement;

where the individual lacks legal capacity or regulatory eligibility.

32.4 Future educational products

If DroneJob intentionally launches services for schools or younger students, DroneJob should create a dedicated legal framework rather than stretching this commercial Privacy Policy to cover those activities.

That framework may include, as applicable:

• Educational Use Terms;
• Student Privacy Notice;
• school/district agreement;
• parent/guardian consent;
• age-appropriate controls;
• student-data restrictions.

Applicable laws may include requirements under laws such as:

• COPPA;
• FERPA;
• state student-privacy laws;
• GDPR child-consent rules;
• other applicable education/privacy laws.

Do not represent DroneJob as currently compliant with a student-specific regulatory framework merely because future educational functionality is contemplated.

32.5 Public schools and educational institutions

A public university, training institution or other educational organization may use standard DroneJob Enterprise Services where the Services are appropriate for its Users and data.

K-12/student-specific processing should receive separate review before launch.

32.6 Reporting a concern

If a parent, guardian or other person believes a minor's personal information has been improperly provided to DroneJob, they may contact DroneJob using the information in Section 35.

33.1 Distinguishing Third-Party Services from Subprocessors

The distinction matters.

Example:

DroneJob chooses infrastructure provider
to operate DroneJob
        ↓
Subprocessor / Service Provider
        ↓
Section 25

versus:

Customer connects its own ERP
to DroneJob
        ↓
Customer-directed Third-Party Service
        ↓
Section 33

The same company could potentially act in different roles depending on the functionality.

33.2 Connected applications

Customers may connect systems such as:

• CRM;
• ERP;
• GIS;
• accounting;
• project-management;
• identity;
• storage;
• fleet;
• flight;
• aviation;
• communications;
• AI services.

DroneJob may exchange information with the connected service according to the authorization granted by the Customer.

33.3 Authentication providers

Users or Organizations may use:

• social login;
• enterprise SSO;
• federated authentication;
• other identity providers.

The provider's own terms and privacy practices may apply to the provider's independent processing.

33.4 Payment providers

Payment processors may independently process information necessary for:

• payment;
• payout;
• fraud;
• identity verification;
• banking;
• tax compliance.

DroneJob does not control all processing performed by an independently regulated financial provider.

33.5 Communications providers

SMS, email, voice and other communication services may involve:

• communications providers;
• carriers;
• email providers;
• networks.

Their independent legal obligations may also apply.

The special SMS privacy restrictions in Section 13 remain controlling for DroneJob's use of mobile opt-in information.

33.6 Mapping, aviation, airspace and weather providers

DroneJob may display or process information originating from third-party providers concerning:

• maps;
• imagery;
• airspace;
• weather;
• aviation;
• location;
• navigation.

Such information may be governed by the provider's applicable:

• licenses;
• terms;
• attribution requirements.

Third-party operational data should not be treated as infallible.

33.7 Flight and fleet integrations

DroneJob may connect with:

• drone manufacturers;
• flight systems;
• fleet tools;
• telemetry platforms.

A Customer is responsible for ensuring it has appropriate authority to connect and process data from those systems.

33.8 Customer-connected AI

Where a Customer connects an external:

• AI provider;
• model;
• agent;
• API key;

DroneJob may transmit information according to the Customer's instructions.

The independent provider's:

• training practices;
• retention;
• security;
• location;
• privacy terms;

may apply after the information is transmitted.

DroneJob's protections applicable to DroneJob-provided AI do not automatically bind an independently selected external provider.

33.9 Data residency impact

Connecting a Third-Party Service may cause information to:

• leave an agreed region;
• be stored elsewhere;
• be processed by additional providers.

Customers with:

• public-sector;
• GDPR;
• residency;
• sovereignty;
• security;

requirements should evaluate an Integration before enabling it.

33.10 Public-sector restrictions

Public Sector Customers may prohibit or restrict:

• certain Integrations;
• consumer cloud storage;
• external AI;
• marketing analytics;
• unapproved communication channels.

DroneJob may technically disable or contractually restrict features for a particular environment where supported.

The availability of an Integration in the general commercial platform does not mean that the Integration is approved for every public-sector Customer.

33.11 App stores and operating systems

DroneJob mobile applications may be distributed through:

• Apple App Store;
• Google Play;
• other approved distribution channels.

The platform provider may process information according to its own terms.

33.12 External links

DroneJob websites or User Content may contain links to third-party sites.

DroneJob is not responsible for the privacy practices of an independently controlled site merely because a link appears in DroneJob.

33.13 Revocation

Where supported, Users may disconnect an Integration.

Disconnecting it generally stops future authorized exchange but does not automatically delete information that:

• DroneJob previously received;
• the provider previously received;
• was incorporated into business records.

33.14 Changes to third-party services

Third-party providers may:

• change APIs;
• discontinue functionality;
• change terms;
• suffer outages.

DroneJob cannot guarantee continued interoperability with an independently operated service.

34.1 Effective Date

The current Effective Date must be displayed near the beginning of this Privacy Policy.

When DroneJob makes an update, the Effective Date should be updated appropriately.

34.2 Material changes

Where required by applicable law, DroneJob will provide additional notice before or when a material change takes effect.

Notice may be provided through methods such as:

• Account notification;
• email;
• website notice;
• in-product notification;
• another appropriate method.

34.3 Changes requiring consent

If applicable law requires consent before DroneJob materially changes a particular processing purpose, DroneJob will obtain the required consent.

Merely posting a revised policy should not be treated as sufficient consent where law requires a more affirmative action.

34.4 AI data-use changes

The following principle is particularly important:

DroneJob should not silently convert its approved policy:

private Client data, private Mission data, private communications, private deliverables and Enterprise Customer Data are not used to train general-purpose AI models for unrelated Customers by default

into a materially broader general-model-training authorization merely by quietly updating this Privacy Policy.

If DroneJob proposes such a material change, it must consider:

• existing contractual commitments;
• applicable privacy law;
• Customer notice;
• consent/opt-in where required;
• Enterprise restrictions.

34.5 Enterprise agreements

A Privacy Policy update does not automatically override stronger privacy or data-processing commitments contained in an active:

• DPA;
• Enterprise Agreement;
• Security Exhibit;
• Data Residency Exhibit;
• Public Sector Addendum;
• other signed agreement.

34.6 Public-sector Customers

Public Sector contracts may require:

• advance notice;
• change control;
• fixed contract terms;
• renewal-based acceptance.

Those contractual requirements control where applicable.

34.7 Prior versions

DroneJob should eventually maintain access to prior material versions of the Privacy Policy.

Preferred future pattern:

Privacy Policy
Current

Previous Versions
├── YYYY-MM-DD
├── YYYY-MM-DD
└── ...

Do not create an archive system as part of this legal-content task unless one already exists.

35.1 Privacy requests

Users may contact DroneJob concerning matters such as:

• access;
• correction;
• deletion;
• privacy rights;
• privacy questions;
• consent;
• data-processing concerns.

Where DroneJob provides a dedicated privacy-request form in the future, it may be listed here.

Do not claim that such a form exists until implemented.

35.2 Customer-controlled data

If your personal information was provided to DroneJob by:

• your employer;
• a DSP;
• an Enterprise Customer;
• a Public Sector Customer;
• another Organization;

and DroneJob is processing that information on the Organization's behalf, you may need to direct the request to that Organization.

DroneJob will assist the applicable Customer as required by law or contract.

35.3 Data Protection Officer

Do not list a DroneJob Data Protection Officer unless DroneJob has formally appointed one.

If applicable law later requires a DPO and DroneJob appoints one, update this Section.

35.4 European or UK representative

Do not claim that DroneJob has appointed an:

• EU representative;
• UK representative;

unless an appointment has actually been made and reviewed.

If required by DroneJob's operations, those details should later be added here.

35.5 Brazil privacy contact

Do not invent or designate an LGPD encarregado in this Policy unless DroneJob has formally made the appointment.

35.6 Security vulnerabilities

Privacy requests and security-vulnerability reports are different processes.

If DroneJob later publishes a dedicated vulnerability-disclosure contact or policy, link to it separately.

Preferred future location:

https://trust.dronejob.ai/security

or:

https://www.dronejob.ai/legal/security

Do not create that page as part of this task.

35.7 Public-sector records requests

Requests under:

• public-records laws;
• freedom-of-information laws;

concerning records controlled by a Public Sector Customer should generally be directed to the applicable governmental entity.

DroneJob does not determine whether a Customer-controlled record must be publicly disclosed.