Your data, plainly.

Strike Trainer is run by Unconventional Robotics(“UCR”, “we”). This page lists everything we collect when you use it, why, who helps us process it, how long we keep it, and how to get it deleted. We record a lot, including every frame of every flight, so we would rather you read it here than be surprised later.

Who can use it

Strike Trainer is for adults only. You must be 18 or older to create an account. If we learn an account belongs to someone under 18, we delete it.

What we collect

From your Google account

Your email address, name and profile picture, which Google shares with us when you sign in.

Your pilot card

Callsign, country and flying experience (required).
Radio model and organisation (optional), and whether you want emails from us.
That you confirmed you are 18+, which terms version you accepted and when, and your consent to research use of your flights.

Your callsign, country and profile picture appear publicly on the leaderboards next to your scores. Your email never does.

Every run you fly

The setup: map, mission, airframe, video feed, flight mode, controller type and name, and options such as the target cue and grid.
The outcome, scores and their breakdown, timings, impact data (speed, dive angle, miss distance), distance, top speed, altitude, battery and frame rate.
A full flight log: for every frame, your stick inputs and the drone's position, attitude, velocity, body rates and motor outputs, plus battery and video-link state and the positions of the targets.

How you use the product

Product events such as clicks, setup choices, errors, controller connections and pages viewed.
Device information: browser, operating system, screen size, graphics card (GPU), number of CPU cores, memory, language and time zone.
Approximate location (country, region and city) worked out from your IP address. We do not store the IP address itself, only a salted hash of it, which we use for rate limiting and spotting abuse.
The page that referred you and any campaign (UTM) tags in the link you followed.

If you contact us

The name, email, organisation, role and message you send through the contact form.

Why we use it

Running the trainer: signing you in, saving your settings and radio calibration, scoring runs and showing leaderboards.
Improving it: finding bugs and slow devices, and understanding which maps, missions and features people use.
Research and training autonomous drone models: your flight logs and run data may be used by UCR to research and train autonomous drone models. You agree to this when you create your pilot card. If you do not want this, do not create an account, or delete it at any time.
Keeping it fair and safe: detecting tampered scores, abuse and spam.
Talking to you: replying to messages, and sending product news only if you opted in.

We do not sell your personal data.

Who processes it for us

Supabase: database, sign-in and file storage, hosted in the Mumbai (India) region.
Vercel: hosting the website and API, plus Vercel Web Analytics and Speed Insights.
Google: Google sign-in and Google Analytics.

These providers process data on our behalf under their own terms. Some of them may process data outside India.

How long we keep it

Account data (your pilot card and runs): until you delete your account.
Raw product events: 90 days, after which we keep only aggregated counts.
Flight logs: until you delete your account. Anonymised derivatives already used to train models (for example, a trained model, or datasets with your identity removed) may persist after deletion.
Contact messages: as long as we need them to deal with your enquiry.

Cookies and local storage

Your sign-in session, so you stay signed in.
Your trainer settings and radio calibration, kept in your browser and synced to your account.
Analytics: Google Analytics sets cookies to count visits. Vercel Web Analytics does not use cookies.

Your rights

See and correct your details on your pilot card.
Delete your account and data with “Delete my account and data” on your pilot card. This removes your profile, runs, leaderboard entries, flight logs and saved settings.
Anything else, such as a copy of your data or a question about this policy: contact us.

Security

Data travels over HTTPS. Database access is restricted per user, and only our backend can read other pilots' data. No system is perfectly secure; if we have a breach that affects you, we will tell you.

Changes

If we change this policy we will update the version date above. If a change materially affects how we use your data, we will ask you to accept it again before you fly.