Privacy Policy

This Privacy Policy explains how Killzone FPV (“Killzone,” “we,” “us,” or “our”) handles information through killzonefpv.com, the Android app published as com.killzonefpv.mobile, and the iOS app published as com.killzonefpv.ios (together, the “Service”). Core flight and public multiplayer remain available without creating an account.

The Service is operated by IHD LLC under the Killzone FPV brand. Our registered agent and legal-notices address is 6545 Market Ave. North, Suite 100, North Canton, OH 44721, United States. Contact killzonefpv@pm.me for privacy, account, support, or purchase questions.

1. The Service and native controller access

Killzone FPV is a browser-based FPV simulator with offline flight and optional online multiplayer. The Android app reads compatible Bluetooth and USB controller input through Android controller APIs and passes that input to the simulator through an origin-restricted native bridge.

The iOS app can read a compatible controller through Apple’s Game Controller framework. It can also use the ExpressLRS WiFi Joystick feature, which requires iOS Local Network permission so the app can receive controller-channel data from your ExpressLRS transmitter. In direct-radio mode, the iOS app can load a simulator bundled inside the app while the phone has no internet route. Native controller values and local ExpressLRS traffic are processed on the device and are not automatically uploaded as controller diagnostics or raw input history.

The native apps do not request access to your contacts, precise location, photos, camera, or microphone. If you use online features in either app, the same account, multiplayer, and service-provider practices described below apply.

2. Anonymous play and information stored on your device

You can fly and use public multiplayer without a Killzone account. The Service stores simulator data in browser or app storage so it can remember your setup. This can include controller mappings and calibration results, simulator settings, interface preferences, a generated guest callsign, local reconnect information, and chat preferences. Controller diagnostic traces and exported reports remain on your device unless you choose to copy, download, or share them.

3. Online play and chat

When you join an online room, the Service processes the information required to run the match, including a generated or chosen pilot name, room and gameplay actions, current flight/input state, scores and results, reconnect data, and optional text chat. Other people in the room can see your pilot name, gameplay state, results, and chat messages.

Room gameplay and chat are primarily short-lived multiplayer state. The room service keeps a bounded in-memory chat history while a room is active. Free pilots do not receive a durable global profile or leaderboard record. Pro pilots who participate in qualifying public matches may have the minimum result evidence and leaderboard statistics stored with their account. Private matches, raw controller input, and chat do not write leaderboard ranks.

4. Optional Pro accounts and authentication

If you create or use a Pro account, we process your email address, email-verification status, account and provider identifiers, authentication methods, account status, and security records. You may sign in with email and a password or one-time code, a passkey, or an available provider such as Apple, Google, Facebook, Discord, or Twitch. A sign-in provider may send us a provider-specific identifier, email address, and basic profile fields it makes available. Provider tokens are encrypted at rest, passwords are stored only as password hashes, and verification codes and session tokens are stored in hashed form.

For account security and session management, we process session timestamps, IP address, user-agent string, and a coarse device/browser label. Raw IP addresses and user-agent strings remain private account-service data and are not shown on public profiles or added to gameplay telemetry.

5. Pro settings, creations, and public profile

Pro features can store your pilot name and name history; allowlisted simulator and interface settings; named controller-calibration profiles; saved race routes and generated race courses; map-import request URLs and notes you choose to submit; entitlement state; custom livery drafts and published designs; qualifying match results; leaderboard projections; and related security or moderation records. Calibration profiles contain normalized control mappings and a label—not a raw browser fingerprint or continuous controller recording. A saved race route contains the sampled position, velocity, timing, and map needed to regenerate your course.

Your created races are private account content by default. You can use them for offline personal records or choose one while hosting a private Pro lobby. Guests in that lobby receive the generated course needed to play it, but not your original recorded route. A separately reviewed promotion can copy a selected course into the public race catalog for matchmaking, offline racing, course voting, and global leaderboards; the original recorded route and account identity remain private.

A Pro public profile can show your pilot name, Killzone Pro presentation, qualifying ranks and statistics, and race badges. Public-profile and global-ranking visibility is enabled by default for eligible Pro accounts and can be turned off in Account. Your email, authentication methods, purchases, sessions, settings, calibration, private match evidence, and security or moderation details are never shown on the public profile.

6. Purchases and entitlements

If you start or complete a purchase, we process an account-linked checkout intent and records such as the product, purchase source, amount, currency, status, external transaction identifier, and relevant timestamps. Depending on the purchase option offered, Stripe Managed Payments—presented at checkout as “Sold through Link”—an app store, BTCPay Server, Monero infrastructure, or another disclosed payment provider may process payment, billing, transaction, tax, refund, dispute, support, and fraud-prevention information under its own privacy terms. Killzone does not store full payment-card details, cryptocurrency spend keys, or a customer cryptocurrency balance.

We keep the minimum purchase and entitlement history needed to activate or restore Pro, handle refunds or disputes, prevent duplicate fulfillment, maintain financial records, and comply with legal obligations. A payment provider’s records and retention are controlled by that provider.

7. Issue reports and Android beta invitations

If you submit an issue report or feature idea, we collect the category and text you provide plus the current release, page, mode, and online/offline context. The report does not automatically include your display name, chat, player ID, room code, IP history, or raw browser string. Reports are kept for up to one year unless a shorter period is appropriate.

If you join the Android closed-beta list, we collect the email address you submit, when it was first and most recently submitted, and the signup source. We use it only for tester invitations and related testing updates. Email killzonefpv@pm.me to request removal.

8. Diagnostics, abuse prevention, and service providers

On the public website, privacy-scrubbed error reports may be sent to Sentry to diagnose crashes and availability problems. We configure browser reporting to remove user information, cookies, request and response headers, request bodies, query parameters, and breadcrumbs. Cloudflare provides website delivery, database, security, and human-verification services. Cloudflare Turnstile may evaluate browser and interaction signals before multiplayer admission, account or purchase actions, issue reports, or beta signup.

Infrastructure providers may process IP addresses, timestamps, request metadata, cookies or security tokens, and abuse-prevention signals as needed to deliver and protect the Service. Operational reporting is designed around aggregate counts and does not add account identifiers to anonymous gameplay telemetry, public-room logs, or general performance metrics.

9. Advertising, sale, and disclosure

The current Service does not contain advertising SDKs or personalized advertising. We do not sell personal information. We disclose information only to service providers acting for the purposes described here; when you choose an authentication or payment provider; when required by law; or when reasonably necessary to protect the Service, its users, or others.

10. Retention

Local settings and personal race times remain until you clear browser or app data. Active-room state is removed when it expires or the room service restarts. Account information remains while your account is active and afterward only as needed for recovery, security, dispute handling, and legal obligations. Expired sessions and verification records are removed or become unusable under their configured lifetimes. Cloud settings, calibration profiles, saved race routes and courses, profile visibility, and published content remain until you delete them, close the related feature, or request account deletion, subject to bounded integrity and moderation records.

Account deletion removes or anonymizes product personal data where appropriate, including pending map-import requests, but minimized purchase, tax, accounting, fraud-prevention, dispute, and security records may be retained when required. Infrastructure and external providers may use separate retention periods under their own terms.

11. Your choices

You can clear local data through your browser or device, delete individual cloud calibration profiles and created races, rename created races, hide your public Pro profile and leaderboard visibility, revoke other account sessions, and download a machine-readable copy of available account data from Account. You can request correction, account closure or deletion, or Android beta-list removal by emailing killzonefpv@pm.me. We may need to verify that you control the account before completing a request.

12. Children

The Service is not directed to children under 13. We do not ask anonymous pilots for a date of birth. The Pro purchase flow requires confirmation that the account holder is at least 13. If you believe a child has submitted personal information, contact us so we can review and delete it where appropriate.

13. Security, changes, and contact

We use HTTPS/WSS for public network connections, restrict native controller bridges to approved Killzone origins, separate account and commerce records from anonymous observability and issue-report data, and limit the information exposed to multiplayer services. No transmission or storage method is completely secure.

We may update this policy when the Service changes. The effective date above identifies the current version. Questions, privacy requests, and concerns can be sent to killzonefpv@pm.me.