DROPZONE / PRIVACY

Privacy statement.

Effective September 27, 2026 · Covers the current Dropzone app and this website.

Dropzone is an independent Windows game companion maintained by Jaden Trask. You can use it without creating a Dropzone account. This statement explains what stays on your device and when the app or website contacts another service.

Information stored on your PC

The desktop app stores saved builds, favorites, map positions and targets, Sons of the Forest found-location progress and layer preferences, previously saved Gray Zone Warfare progress and annotations, text-size settings, source-warning preferences, and downloaded game-feed caches in its local app profile. These are used to remember your choices and show previously downloaded information when a source is unavailable. Dropzone does not require a cloud account. Saved records are not uploaded unless you explicitly use a sharing or encrypted-sync action.

Copy controls write the text you choose to the clipboard. Export controls save the selected information to a file you choose. Calculator positions refer to the game map; Dropzone does not request your device’s physical location.

Session tools and device access

Session notes, goals, practice scores, calendar events, imported frame-time data and clips stay on your device by default. Optional running-game detection checks process names locally and does not read game memory. Launchers and settings-file access are chosen explicitly. Restoring a settings file requires confirmation. The microphone test starts only after you choose it; it is not recorded or uploaded by Dropzone. Optional voice commands depend on the runtime and may use its speech provider.

Second-screen pairing and encrypted workspace sync

Local-network pairing shares the cards and draft you select with devices holding its link. Links expire after eight hours or when you stop pairing. Any link holder can view those cards and edit draft slots. This service runs on your PC, not on the public website.

If you explicitly create or connect an encrypted workspace, the session-center records are encrypted on your device with AES-GCM before upload. The hosted service stores ciphertext, a hash of its access token, version and expiry metadata, and a daily hash of the creator’s network address to limit creation. The encryption key stays in your sync code and local app storage. Anyone with the full code can read, update or delete that workspace. The server cannot recover a lost key. Uploaded workspaces expire 30 days after creation or the last upload and may be deleted earlier by a code holder. Expired data is inaccessible and removed in bounded batches; infrastructure backups and logs may follow the hosting provider’s retention policies. Local media, launcher paths and publisher-account credentials are not included.

Rocket League tracker and optional accounts

After setup, the Rocket League tracker reads Rocket League’s local Stats API to record player display names, platform identifiers, team scores, match dates and game statistics on your PC. It may read the active Steam account identifier locally to match your game profile. It does not read your Steam or Epic password or game memory. The setup assistant checks installed game configuration and creates a backup before changing it.

Optional Dropzone accounts use Supabase for email-and-password authentication. Supabase processes your email address, a password hash, verification and recovery information, session information and normal service logs. Dropzone does not save your plaintext password. Desktop sign-in tokens are stored using the operating system’s encrypted credential storage. See Supabase’s privacy policy.

Verification and password-reset emails are delivered through Resend. Resend processes the recipient email address, message content (including the temporary verification code), and delivery records needed to send and troubleshoot these emails. These are account-service emails, not marketing messages. See Resend’s privacy policy. Provider logs may have separate retention schedules.

Signing in enables cloud synchronization of your completed personal match records: match identifier, date, result and supported personal statistics. The cloud upload does not include the full opposing roster, their platform IDs, raw event streams or game configuration files. Profile details include your Dropzone username, optional display name and chosen profile picture. Profile pictures are resized locally before storage.

Cloud match history is limited to the latest 365 days. Older cloud match records are removed by scheduled cleanup. Without a signed-in account, local match history is limited to the latest 30 days; signed-in accounts retain up to 365 days locally. Older local records are removed as the tracker applies its retention window. Account and friendship records remain until removed or the account is deleted. Service logs and infrastructure backups may have separate provider retention schedules.

Other users can send a request using your exact Dropzone username. People participating in a friend request can see profile details. Match statistics are private by default and become visible only to accepted friends when you enable “Share stats with friends.” Removing a friend or disabling sharing prevents further access through the service. People who already viewed information may retain their own copies.

Open your personal account from the Rocket League navigation bar to sign out, change sharing, or delete your account. Manage and remove friends on the Friends page. Deleting an account removes its cloud profile, friendships and uploaded matches; it does not erase local history on your PC. For access or deletion questions, contact the maintainer through the link below without posting credentials.

Game sources and media

Dropzone requests information from game publishers and community services, including Riot, Activision, Embark/Steam, CODMunity, community WARDOGS sources, and Ubisoft. Gray Zone Warfare remains under construction; its data and patch-note requests are disabled. Previously saved Gray Zone Warfare progress and personal map annotations remain on your PC. Connected feeds are checked when the app opens and periodically while it runs. These services receive normal network-request information, such as your IP address and requested resource. The source and filter you open can determine the request sent.

External images and video thumbnails may load from their providers. YouTube players load after you choose to play a video; embedded playback uses YouTube’s privacy-enhanced domain. YouTube and other external services operate under their own privacy policies. Following a progression, source, or video link opens that service; Dropzone does not receive your Steam or game account credentials.

WARDOGS progression and MetaForge

Progression snapshots you import or enter, snapshot history and damage-lab preferences stay in the local app profile. Import files are processed locally. Dropzone does not automatically synchronize your game account. The optional MetaForge view loads the provider website in a separate persistent browser session; its cookies and sign-in state stay on this PC. MetaForge may load its own advertising and analytics under its own policies. Signing in there does not import progression into Dropzone.

Optional squad rooms

Connecting to a squad room sends its map and the markers you choose to share to the Dropzone website service. Every holder of the invite code can read, add and remove room markers. Automatic target sharing is off until you enable it. A room expires after eight hours, or its creator can close it sooner. Expired rooms are inaccessible and are removed in bounded batches during subsequent room creation; infrastructure logs and backups may remain under the hosting provider’s policies. Invite codes and saved plans are stored on your PC. The service stores hashes of room secrets and a daily hash of the creator’s network address for room-creation limits. It does not receive your progression snapshot, loadouts, account password or physical location.

Personal patch watch

While enabled, the app checks official patch pages for names from your saved loadouts and watch list. Matching happens on your PC; the names are not sent as search queries. Publisher sites still receive ordinary connection information. Checks run while Dropzone is open, and can be disabled in My patch alerts.

App downloads and updates

Installers are distributed through GitHub Releases. Installed copies check GitHub for app updates on launch and periodically while running. Downloads may happen in the background; installation requires the app’s restart-and-update action. GitHub and its download infrastructure receive connection information as part of those requests. See the GitHub privacy statement.

This website

This website uses Cloudflare Web Analytics to measure visits and page performance. It does not include advertising pixels, account forms or newsletter forms. Cloudflare describes Web Analytics as privacy-first analytics. See Cloudflare’s Web Analytics documentation for how its beacon works. The home page asks GitHub for the latest stable release so its download button stays current. That request exposes normal connection information to GitHub. If it fails, the button links to the latest-release page on GitHub.

The site’s hosting and delivery providers may process IP addresses, request details, and security or operational logs to serve and protect the website. Infrastructure may use its own security cookies. Dropzone’s site code does not control provider retention periods. Hosting is provided through OpenAI Sites and its delivery infrastructure; see OpenAI’s privacy policy.

Analytics and advertising

The website loads the Cloudflare Web Analytics beacon from static.cloudflareinsights.com. It reports visit and browser performance metrics to Cloudflare. This website analytics addition does not instrument the desktop app or send its saved loadouts, map markers or calculator inputs.

The current Dropzone app does not include a maintainer-operated analytics, advertising, or automatic crash-reporting service. The maintainer does not sell saved loadouts or app preferences. External providers’ collection and retention are governed by their own policies.

Deleting local information

You can remove saved loadouts and targets with the app’s controls. To remove all local preferences and feed caches, close the app and remove its local profile. Uninstalling is designed to preserve that profile so a reinstall can retain your saves. If you need help identifying the profile, ask the maintainer before deleting folders; older installations may use a previous app name.

Questions and changes

Contact the maintainer through JadenTrask on GitHub. Please do not post passwords, access tokens, or other private information in public issues. This statement will be updated when Dropzone’s data practices change, with the effective date shown above.