Terms and privacy
Terms of Use
Who runs the site
Drone Front is made and run by an independent educator. Questions about these terms go through the request form.
Sanctions
Drone Front is not available to users in Cuba, Iran, North Korea, or the occupied Crimea, Donetsk and Luhansk regions of Ukraine, or to anyone on a US government sanctions list.
Drone Front is an educational simulation built only from published open sources. It contains no instructions for building, modifying or operating drones.
When you create an account you confirm that none of this applies to you. We keep that confirmation and its date with your account.
Using the simulation
You can launch Drone Front online without an account. You need an account only to save and share scenarios and to put ranked runs on the leaderboards. You must be at least 13 years old to create an account.
What Drone Front is
Drone Front is an educational strategy simulation. Scenarios are simplified. Each figure is marked either Sourced, taken from a linked published source, or Simulation estimate, a teaching value. The numbers inside the simulation are teaching settings, not real system performance. Do not rely on it for real operations, planning or news.
Leaderboards
Ranked runs are checked by replaying your orders on our server, and only that replayed score is listed. Your callsign is public on the boards, so choose one that does not identify you if you prefer. Callsigns must follow the community rules, and we may change or remove a callsign or a run.
Scenarios you share
You own the scenarios you make. When you make one Unlisted or Public, you allow other people to view it, launch it and copy it inside Drone Front. Shared scenarios carry the label “Community scenario, made by a user” and must follow the community rules. Titles and descriptions are checked automatically when you share, and anyone can report a shared scenario. We may hold, hide or remove any shared scenario.
Weekly scenarios and email
Weekly scenarios are built from published reporting and are reviewed before they are published. If you sign up for the weekly email, you can unsubscribe with the link in any email.
Institutional licences
Colleges and academies can use classroom mode, the lesson guides and the offline file under an institutional licence. Access comes with a signed licence for the period the institution chooses; a request alone does not give access. See Licensing. We may ask colleges to list the site on a course page. Saying no does not change your licence.
Ownership and copying
Drone Front, its simulation code, scenarios, drone entries, guides, doctrine library, learning material, illustrations, map tiles and site text are copyright 2026 Drone Front. All rights reserved. You may play Drone Front on this site and, under an institutional licence, use the offline file inside the licensed institution. You may not copy, download, scrape, mirror, host, redistribute, decompile or reverse engineer the simulation or its content, or run it on any other site or service, without written permission. Using automated tools to collect scenarios, images or other content from this site is not allowed. Fair quotation for review, teaching and comment is welcome with a link to this site.
Changes
We may change the simulation, these terms or this notice. We will post the date of the last change on this page.
Privacy notice
What we collect
If you use the simulation without an account, we do not ask for any personal information, and your progress stays in your browser.
If you create an account, we store your name, your email address, your sanctions confirmation and its date, and the scenarios you save.
When you finish a scenario while signed in, we store a summary of that run in your service record: the scenario, side, result, score, how long it took, the cost, losses on both sides, drones launched, lost, shot down and jammed, reconnaissance and strike timings, and the simulation’s estimate of civilian harm. We also store your academy progress. Only you can see your service record, except your run count and campaign badges, which show beside your callsign on the leaderboards.
Academy progress is private practice history reported by the learner: completed lessons, best answers and assessment run IDs used to prevent duplicate counts. Up to 500 recent assessments retain dates, correct answer counts and question counts. Detailed answer choices stay in local field notes and classroom result codes. Practice ranks are not verified qualifications or measures of mastery.
If you put a ranked run on a leaderboard, we store your callsign, the scenario, side, week, score and result with your account. The orders are replayed on our server and not kept.
If you play online against another person, we store both sides’ orders so the match can run, and we delete them 30 days after the match ends. The match itself, with both callsigns and the result, stays in each player’s online record.
Scenarios you share as Unlisted or Public can be seen by other people, with the author name you choose.
Classroom mode needs no student accounts. Class results travel as codes between students and their instructor and never reach our server. When a class joins an online official scenario, its setup code is sent with that scenario request to exempt it from the visitor quota; the handler does not store the code. A student who is signed in also gets the run in their own service record, which only they can see.
If you send the instructor form or sign up for the weekly email, we store what you enter.
When an approved instructor downloads the offline file, we record which account downloaded it and when, and mark the file so that a leaked copy can be traced.
To stop repeated counts, duplicate reports and overuse, we keep scrambled codes made from your network address, browser or account, never the address itself. Codes used against repeated counts and overuse are deleted within two days. A code attached to a report is kept with that report.
Page views and fonts
The Base44 analytics and navigation trackers are disabled. The application does not send appLogs.logUserInApp calls on page views. Base44 infrastructure may retain access logs outside the application. IBM Plex fonts are hosted on this site, without Google Fonts requests. See College IT and data for inspection and deletion details, including limitations that require provider confirmation.
Counts
We count how often scenarios are started and finished, classes are created and results are collected, by country, and how often players choose to strike protected sites in each scenario. These are totals only. No player, class, institution or time is attached to them.
Who can see it
Only the operator of this site can see stored data. We do not sell it, and we do not share it with any government, military or intelligence service. We would release data only if a court order required it, and we would tell the account holder unless the law forbade it.
Where it is kept
The site runs on Base44, which stores account, form and report data for us. The weekly email list is kept with Kit, the service that sends it. Titles and descriptions of shared scenarios, and callsigns, are checked by an AI service through Base44.
How long we keep it
Service records, academy progress and saved scenarios stay until you delete them or your account. Online match orders are deleted 30 days after the match. Instructor requests are kept for two years after our last contact. Offline download records stay until the account is deleted.
Institutions
Licensed institutions can use the offline file, which runs without an internet connection and sends nothing to us.
Your choices
You can delete all your runs, or your account and everything stored with it, from your service record page. You can leave the weekly email with the unsubscribe link in any email.
Last updated: 5 October 2026