▶FPV SCHOOL← Back to homeLegal hub

AI Features Policy

AIPrivacyUKLast reviewed: 20 April 2026FPV SCHOOL LIMITED · Company No. 15817837 · ICO: ZB796938

AI Features Policy (Master Page)
Last updated: 20 April 2026

Legal Hub: /legal
Privacy Policy: /legal/privacy-policy
FPV Coins & AI Billing: /legal/fpv-coins-ai-billing
Safety Disclaimers: /legal/safety-disclaimers

1. What this policy covers

This page explains how AI-assisted features operate across FPV School properties where they are enabled, who can access them, how prompts are processed, how billing can apply, and what you must not rely on AI to do.

2. Availability and access gating

AI features are not universally available to every visitor, every account, or every host environment.

At the time of this update, AI access may depend on one or more of the following:

  • being signed in to an eligible FPV School account;
  • belonging to a permitted access cohort or internal rollout group;
  • the relevant runtime being enabled for the current host or environment;
  • daily feature limits, anti-abuse controls, and technical availability; and
  • having enough FPV Coins or other required entitlement for the relevant request.

We may enable, disable, rate-limit, expand, restrict, or withdraw AI features at any time for safety, quality, rollout, cost-control, or operational reasons.

3. What AI features currently do

Where enabled, FPV School AI may support context-aware assistance inside drone and workflow surfaces, including build, rates, PID/tuning, flights, checklists, overview, or related knowledge workflows.

Depending on the feature, AI may use retrieved knowledge-base context, recent conversation state, and limited in-product context in order to answer the request.

4. Private-by-default conversations

AI conversations are intended to be account-private by default. They are not meant to appear automatically on public profile pages, public drone views, or recipient-facing share links.

That said, you are still responsible for what you type into AI features. If you paste personal information, third-party confidential information, or sensitive material into a prompt, that material may be processed as part of the request.

5. How AI processing works

When you submit an AI request, FPV School may process:

  • your prompt and follow-up messages;
  • recent conversation history needed to answer coherently;
  • relevant feature metadata and workflow context;
  • retrieved internal knowledge-base snippets or support context; and
  • billing, usage, and safety metadata needed to run the feature responsibly.

This information may be sent to an external AI provider through business/API services so the request can be processed. According to the provider's published business/API materials available when this policy was updated, business/API data is not used for model training by default unless the customer explicitly opts in. Provider terms can change, so you should review the provider's current materials as well.

6. Billing and FPV Coins

AI requests can consume FPV Coins where the relevant feature is configured as billable. Charges can vary by feature, mode, or processing path.

Where AI billing applies:

  • request cost can be shown before or during use;
  • successful or partially successful work may still consume FPV Coins;
  • some failed requests may be refunded or corrected if billable work did not complete as intended; and
  • separate consumer purchase rules may apply later if FPV School introduces direct paid checkout or subscriptions for AI access.

For the current billing position, read /legal/fpv-coins-ai-billing.

7. Important limitations

AI outputs are educational and assistive only. They are not certified engineering advice, aviation advice, legal advice, or safety approval.

You must not rely on AI as the sole basis for:

  • flight safety decisions;
  • LiPo charging or electrical safety decisions;
  • regulatory compliance decisions;
  • hardware integrity decisions; or
  • any decision where error could foreseeably cause injury, property damage, or legal exposure.

AI can be wrong, incomplete, stale, inconsistent, overly confident, or unsuitable for your setup. You remain responsible for checking manufacturer guidance, firmware notes, laws, regulations, and real-world safety requirements.

8. What you must not submit

Do not submit:

  • passwords, MFA codes, recovery codes, or private keys;
  • payment card numbers or banking credentials;
  • special-category personal data unless strictly necessary and lawfully shared;
  • third-party confidential information you are not authorised to disclose; or
  • requests intended to bypass security, safety, moderation, or legal restrictions.

9. Children and supervised use

AI features are not guaranteed to be available to all users. Where minors can access a relevant property, any use should be supervised by a parent or guardian to the extent required by law and common safety sense.

10. Enforcement and abuse prevention

We may limit, suspend, or block AI use where we reasonably believe there is abuse, unsafe prompting, rate-limit evasion, policy breach, fraud risk, or other integrity risk.

11. Changes to this policy

We may update this policy as AI tooling, providers, rollout status, or legal expectations change. We will update the "Last updated" date when material changes are made.

12. Contact

For questions about AI features or AI-related data handling, contact: [email protected]