DROIDEX

DubTrackr Droidex Privacy Policy

Effective date: August 3, 2026
Last updated: November 2, 2026

Droidex is a companion for the Fortnite Creative experience Droid Tycoon. This Privacy Policy explains what Droidex reads, collects, stores, uses, discloses, retains, and deletes when you use the Droidex website, either of our two Windows apps, and related Droidex services.

The two apps are:

In this Policy, "Droidex" means the website, both apps and the services behind them. "The Companion" and "the Droidex app" mean the Droid Tycoon module wherever it runs: in Droidex Companion or inside the Dubtrackr desktop app. Everything this Policy says about the Companion applies to both apps unless a section names one of them. Section 4.8 covers what only the desktop app does.

This Policy is between you and DubTrackr, an independently operated service based in Washington, United States. It is not an agreement between you and Overwolf. Overwolf, Tebex and Epic Games separately control information they process through their own platforms and services.

1. The most important points

Droidex reads only the Fortnite game window, in memory

Droidex installs its own capture helper, a separate program that captures only the Fortnite game window through Windows Graphics Capture. It does not capture other windows or other monitors. Frames are held only in memory, by the helper and the app, and are discarded after Droidex's screen readers use them. OCR and template matching run locally on your computer using bundled components.

Droidex does not save captured frames to files and has no screenshot fallback. When the helper has no current frame, scanning pauses until it recovers. Droidex does not use Overwolf's desktop-streaming or screenshot capabilities for scanning, and does not send frames to an online OCR service.

Droidex 1.2.9 and earlier could save automatic screenshots in Overwolf's screenshots folder for this app (usually Pictures\Overwolf\Droidex). Those files stay on your computer until they are deleted. The current app can find them and delete them when you choose to.

Pressing Send report can separately attach a fresh game screenshot to your private support ticket, as described in Section 5.9. Automatic diagnostics do not include images.

Linking is required before Droidex sends account-linked gameplay data to DubTrackr

An unlinked Droidex installation does not send account-linked player state, collection data, or gameplay observations to the DubTrackr account service. When you link Droidex to your account, the app can synchronize the data described in this Policy.

The Overwolf advertising system is a separate exception. Overwolf ads can run for linked and unlinked users in both apps, as described in Section 8.

Optional hardware and performance diagnostics also work without account linking. They remain off until you choose to share them. Including your account for support is a separate choice, described in Section 5.11.

Connected community features depend on sharing

Droidex is designed to bring participating players together through a live shared lobby. After you link Droidex to your account, Share my stats is enabled by default so Droidex can publish the limited in-game statistics described in Section 7 and receive the shared state needed for lobby coordination. This default-on processing is part of the connected community service and is not treated as consent.

You can turn Share my stats off at any time. It stays off across app restarts, updates and account switches until you turn it back on. Turning it off stops future sharing governed by that control and closes the live lobby connection, so same-lobby statistics, player identification, base ownership, and other connected community features may stop working or become materially limited. Local screen recognition and features that do not require the connected lobby can continue.

Droidex also publishes a confirmed base-ownership binding as part of the same core shared state so participating players can identify whose base they are visiting. The current version does not present base ownership as a separately optional community feature. Future base publication can be stopped by turning Share my stats off, but this also disables or limits the connected features that depend on shared state.

Session reports stay on your computer; uploads for rankings depend on your region and age

After each Droid Tycoon session the app shows a report built on your computer from its own session records. "Where you rank" bands, such as "Top 25%", are worked out on your computer from anonymous charts Droidex downloads, so seeing your rank sends nothing about you. Whether your session summaries are uploaded to help build those charts depends on where you are and the age band you give:

Only you see your rank. Turning uploads off deletes the summaries you uploaded. Sections 4.7 and 5.13 to 5.15 explain the details.

Fortnite Battle Royale matches follow the same upload rules

The Dubtrackr desktop app can record your Fortnite Battle Royale matches from Overwolf's game events and save them to your account, so your match history follows you to other PCs. The same region and age rules as session comparisons decide whether matches upload, and your choice for matches is separate. A match is public only if you share it, and you can stop sharing at any time. Section 5.18 explains the details.

Fortnite replays, ranks and leaderboards add to your own match records

When Fortnite saves a replay, the app can read it on your computer and add every player's team and placement and the elimination feed to that match's record. Other players' account IDs stay inside your record and are never shown publicly. The app can also save your ranked tier. Leaderboards show only players who turned them on, with an Epic display name and their numbers. Player cards on fortnite.dubtrackr.win show anyone's public Fortnite stats, and add Dubtrackr details only for players who turned that on. Nobody is on the leaderboards or shows those details by default. With squad sharing on, Dubtrackr teammates in the same match can also see each other's paths. Section 5.19 explains the details.

Fortnite squad sharing, friends and the party finder are only between players who choose them

In the desktop app's Fortnite module you can share live match stats with Dubtrackr teammates in your Fortnite party, add friends, see when friends are online, find Epic friends who use Dubtrackr, and post or answer party finder listings. Squad sharing works only while both players have it on and are in the same party or team, and live stats are never stored. Players under 18 start with these settings private and only see party listings from players aged 13 to 17. Adults can find a player aged 13 to 17 only after that player ticks a parent acknowledgement, which isn't offered where a law rules it out. Section 7.5 explains the details.

Ads come from Overwolf, and Remove Ads is paid through Tebex

Both apps show Overwolf ads. Overwolf runs the ads and decides what they process. We don't give Overwolf your gameplay, your account or anything the app reads from the game. No ads show on a PC where the player said they are under 13. Section 8 has the details.

Remove Ads is an optional subscription sold through Tebex, Overwolf's payment partner. Tebex handles the payment. We never see your card or other payment details. We only learn whether you have an active plan and which one. Section 5.16 explains how that check works.

Account deletion is immediate for active account records, but not every copy disappears immediately

The Delete Account control removes active account-linked records immediately and irreversibly, with the limited referral exception in Section 5.12. After a referral reward is issued, a protected identifier derived from the referred player's Epic account remains until the published season end to prevent repeat rewards. It is pseudonymous personal data, not anonymous data. Expired identifiers are cleared automatically as described below. Some backup copies remain until their retention periods expire. Anonymous observation and calibration records are not removed because they contain no account or device identifier that Droidex can use to locate them.

2. Scope

This Policy applies to:

This Policy does not govern:

Those third parties are responsible for their own privacy practices.

3. Who controls Droidex data

For the information processed by Droidex and the DubTrackr service:

Controller: DubTrackr
Location: Washington, United States
Privacy contact: dubtrackr.support@gmail.com

Questions and privacy requests should be sent to the address above. Do not email passwords, refresh tokens, device-link codes, or other authentication credentials.

4. Information processed locally on your computer

4.1 Screen capture and local screen recognition

Droidex's capture helper captures only the Fortnite game window, through Windows Graphics Capture. It does not capture other windows or monitors. The helper and the app hold frames only in memory and discard them after the readers run; nothing is written to a file. When the helper has no current frame, scanning pauses. There is no screenshot or desktop-streaming fallback.

Droidex reads the following information from the player’s own Droid Tycoon interface:

Droidex does not read other players’ names from screen pixels. To check that a Player Stats screen shows your own statistics, Droidex compares the name shown on it with your own Fortnite display name on your computer; the name read from the screen is not uploaded. Other-player names used in the same-lobby interface come from Overwolf game events as described below.

Droidex does not send captured frames to an online OCR service. Droidex 1.2.9 and earlier could save automatic screenshots in Overwolf's screenshots folder for this app; the current app does not, and offers to find and delete those old files. Manual support reports can attach a game screenshot as described in Section 5.9.

4.2 Overwolf game-event information

Droidex subscribes to Overwolf game events. Privacy-relevant information can include:

Game-world coordinates are not GPS coordinates and are not your real-world location.

Droidex Companion gets these events from Overwolf's game-events service. The Dubtrackr desktop app gets the same events from Overwolf's game-events package for its Electron platform, and draws its in-game windows with Overwolf's overlay package. Overwolf supplies and updates both packages.

While Fortnite is in focus, both apps watch key presses only to run their hotkeys and to tell when Tab, Alt, Ctrl or the Windows key is held, which lets you move an overlay. They do not record what you type, and key presses are not sent to DubTrackr.

Names of other players are held temporarily in memory to display the lobby interface. Droidex does not read those names from the screen and does not transmit those other players’ names to the DubTrackr service.

4.3 Monitor and display information

Droidex receives monitor topology information from Overwolf (in the desktop app, from Windows through its Electron platform), including display position, width, height, DPI, primary-display status, and an operating-system monitor handle. Droidex uses this information to identify the monitor running the game, crop a multi-monitor capture, and place the companion window on the correct display.

Monitor topology information is held in memory and is not transmitted to DubTrackr. A screen resolution can be transmitted as part of an anonymous calibration profile, as described in Section 6.3.

4.4 Fortnite log and settings files

Droidex reads limited parts of Fortnite's FortniteGame.log file. It looks for droid-card pickup and drop events, when you load into the lobby or an island, which mode you are playing, which island menu is open, and which language the game is using. Droidex also reads the HUD scale from Fortnite's own settings file on your computer (ClientSettings.Sav) to help place its screen readers. Droidex only reads these files. It does not change them, and it does not transmit either file or its contents.

4.5 Local app storage

Droidex uses local storage on your computer for app operation and preferences. Local data can include:

Local information remains on the computer unless the app removes it or you clear the app’s local data. Server-side account deletion does not guarantee that every local file or local-storage value on your computer is erased.

4.6 Local diagnostic files

The developer-only Event Lab can write game-event payloads to local application storage. It is restricted through the authenticated owner account. Event payloads are sanitized before writing and are not automatically uploaded.

Development builds that used Event Lab before sanitizer version 1.1 on August 1, 2026 may have stored the player’s Epic display name and squadmate display names in local diagnostic files because earlier redaction rules did not cover every event shape. Those files were never transmitted by Droidex. Anyone who used an affected development build should delete the older Event Lab session files.

Development runs of the Dubtrackr desktop app (run from source by DubTrackr, not installed) record the first 600 game-event payloads to gep-payloads.jsonl in the app's data folder, to build test fixtures. That file can hold your in-game name. An installed copy of the desktop app never records it. The file is never uploaded.

Droidex can also create two reader logs when the user deliberately presses the corresponding capture control:

These logs contain reader decisions, reader state, and screen-region coordinates. They do not contain screenshots, account details, or player names. Droidex does not automatically upload them. You may choose to attach a log to a support request.

The Droidex app also keeps a rolling scan log in its local app storage for up to 24 hours, so a scanning problem can be diagnosed after it happens. Save scan log writes it to droidex-scan-log.json on your computer. The scan log is uploaded only if you choose Send log to support, as described in Section 5.9.

4.7 Session records, the session report and "Where you rank"

The Droidex app records each Droid Tycoon session on your computer: when it started and ended; time in the island, with Fortnite in focus, and with a readable game screen; the balances its readers proved at the start and end; what it saw you gain in credits, Upgrade Chips, Nova Crystals and Kyber Crystals; Rebirths, Super Rebirths, crafts and Fusion jobs it saw; when Droid Tycoon menus such as Rebirth, Super Rebirth, the Nova Shop or Player Stats opened; and the app and game-data versions. It also keeps a log of your Super Rebirths: the Rebirth each was made at, the Paths, and how long each cycle took. Records are kept in the app's local database, separately for each linked account and for unlinked play. The app keeps up to 2,000 session records and removes the oldest first. Deleting your Droidex account from the app also deletes these local records.

These records power the session report, your session history and your playtime. The report page is loaded from droidex.dubtrackr.win inside the app and receives your records only by message on your computer. It does not load Google Analytics and does not upload your records.

"Where you rank" is worked out on your computer. The app downloads the anonymous rank charts described in Section 5.13 and compares them with your own records locally. Seeing your rank sends nothing about you. Session records leave your computer only as the summaries described in Section 5.13, and only when uploading is on for your account.

4.8 What only the Dubtrackr desktop app does

The desktop app reads the game the same way Droidex Companion does: the same capture helper, the same screen readers, the same Overwolf game events (Section 4.2) and the same Fortnite files (Section 4.4). It adds a few things of its own.

Its own data folder. The desktop app keeps its data in %APPDATA%\Dubtrackr on your computer. That folder holds:

Nothing in that folder is uploaded except what the rest of this Policy describes. Uninstalling the app may leave the folder behind. You can delete it yourself.

The tray and opening at login. Closing the window hides Dubtrackr to the Windows tray. It keeps running until you choose Exit from the tray menu. An installed copy of the desktop app opens at Windows login by default, starting in the tray. You can turn this off in Settings. A copy run from source never adds itself to Windows startup.

Fortnite Battle Royale. The desktop app also has a Fortnite module. During a Battle Royale match it uses Overwolf's game events for Fortnite (Section 4.2) to show your live stats and the storm, and it keeps a record of each match on your computer. After a match it can read that match's replay file on your computer, if Fortnite saved one. It does not read Fortnite's memory. Sections 5.18 and 5.19 cover what is uploaded and shared.

Droidex pages inside the app. The desktop app shows pages from droidex.dubtrackr.win, such as the droid pages, guides and your session reports, in a sandboxed view. Links to other websites open in your browser. These pages load in the app's embedded mode, where Google Analytics does not run (Section 5.10). Home also reads the latest patch notes and, when you're signed in, your account name from the Droidex API.

5. Information collected when you use a Droidex account or online feature

5.1 Epic account identity and authentication

When you sign in with Epic, Droidex receives the Epic account information authorized for the sign-in flow, including a unique Epic account identifier and public display name. Droidex uses this information for account identity and does not receive your Epic password.

When the Epic friends import is available, connecting Epic also asks for Epic's Friends permission, and the import asks for it again. You can decline it and Epic still connects. If you allow it, Droidex reads your Epic friends' account identifiers to find which of them use Dubtrackr (Section 7.5). So the import can be updated later without sending you through Epic again, Droidex keeps Epic's refresh token for that permission, encrypted, and uses it only to re-read your Epic friends list. It is deleted when it expires (Epic sets this), when Epic refuses it, when you disconnect Epic, when you choose Forget Epic friends access in the app, when DubTrackr switches the import off, or when you delete your account. Droidex does not keep your Epic friends list and does not ask for Epic's Online Presence permission.

Droidex also processes authentication and security information such as:

Droidex Companion and the Dubtrackr desktop app link to your Droidex account separately. A sign-in is never copied from one app to the other.

5.2 Account-linked player state

After you link Droidex, the app may synchronize:

5.3 Collection and progress data

Droidex may store:

When the competitive system is enabled for a linked account, Droidex may also store a no-score baseline; app-verified craft and Droidsmith-level events; server-derived resource-balance increase events; daily positive-growth totals and amount-tier progress for Credits, Upgrade Chips, and Nova Crystals; immutable event identifiers; observation and receipt times; canonical droid, variant, and resource values; reader authority, confidence, and consistent-read evidence; the linked device; acceptance, quarantine, anomaly, and invalidation state; season score-ledger entries and reversals; final season results; achievements; player-profile visibility; and the released Droidex droid portrait selected for the profile. The baseline prevents existing progress from being scored retroactively. Manual website collection, Flawless, or resource edits do not create Season XP.

5.4 Community content

When you use community features, Droidex may process information you choose to submit or generate, including:

Announcement comments and replies are public. Do not submit sensitive personal information in comments, messages, listings, profile names, or other free-text fields.

When the global-chat bridge is enabled, new Global chat messages from the website and Companion are relayed to the Droidex Discord server's App-Chat channel, and new human messages from that channel appear in Droidex Global chat. The relay processes message text, timestamps, Discord message and author identifiers, display names and avatar URLs. A verified linked account lets website or Companion posts use that person's Discord name and avatar; the Discord post remains an automated webhook message. Unlinked website posts are labelled as coming from Droidex. Direct conversations are not relayed. Discord attachments and stickers are represented by a notice and a link to the original Discord message rather than copied files. Droidex retains its Global chat history for five days. Discord's copy is governed by Discord and channel moderation; expiry from Droidex does not delete the original channel history.

5.5 Network and operational logs

Droidex infrastructure and hosting providers may process network and operational metadata such as IP address, request time, route, response status, and similar technical information for security, reliability, abuse prevention, and troubleshooting.

Droidex request logs do not record request bodies, refresh tokens, account UUIDs, or Epic identity values.

5.6 Support communications

If you contact DubTrackr, Droidex processes your email address, message, and any screenshots, logs, or other files you choose to provide. Droidex reader logs are not uploaded unless you attach or send them yourself. Scan logs sent from the app are described in Section 5.9.

The support form at droidex.dubtrackr.win/support/ collects your reply email address, support category, summary, message, and an optional name. The form does not accept file attachments. The Droidex API forwards the ticket over the private OVH server network to the DubTrackr bot operating on that server. The bot posts the ticket to a private Droidex support channel on Discord so DubTrackr can review it and reply from dubtrackr.support@gmail.com. Discord may process the ticket content and related technical metadata under its own privacy policy. Do not include passwords, tokens, device-link codes, private keys, payment information, or other sensitive information in a support ticket.

When you uninstall Droidex Companion, the background uninstall task may open the optional survey at droidex.dubtrackr.win/uninstall-survey/ in your browser. The survey collects the reason you selected, any optional comments you enter, the Droidex app version, and the fixed source label overwolf-uninstall. It does not ask for or include your Droidex account, player name, or email address. The API sends the response through the same private bot relay and the bot posts it in the existing private Droidex support channel with the label Uninstall Survey. After a successful relay, the API also adds one to a daily aggregate grouped only by the selected reason and app version. That aggregate does not store the comment, support ticket ID, account or device identifier, or IP address. The website, API, hosting providers, and Discord may also process the network and technical metadata described in Section 5.5.

5.7 Content and reference requests

The protected droid-card artwork displayed inside Droidex is rendered from droidex.dubtrackr.win. That request contains the droid keys and tiers being displayed and a short-lived authorization ticket.

Droidex also downloads reference information such as calibration consensus, rebirth-plan data and the anonymous rank charts described in Section 5.13. Those downloads do not submit account data.

Droidex checks a public file at game-events-status.overwolf.com to determine whether Overwolf’s Fortnite game-event provider is degraded. Droidex does not include user data in that request.

5.8 Mobile Alerts

When your Companion is linked, Mobile Alerts synchronizes your chat-spawn sound choices and belt-droid rules with your account. The Companion sends a private feed of accepted chat and belt detections, including the recognized droid name where available, variant, rarity, location and time. It also sends a connection heartbeat and whether its game-reading gate is active. This feed is separate from the anonymous observation records below; it is visible only through your account and does not include screenshots or raw chat text.

Recent detections and their notification delivery records expire after one hour and are removed by a periodic cleanup. Alert preferences remain until changed or the account is deleted. Device connection records remain until the linked device or account is deleted.

If you enable phone notifications, Droidex stores the browser's push endpoint and encryption keys with your account and website session. Encrypted alert messages pass through your browser provider's push service, such as Apple, Google, Mozilla or Microsoft. Turning off phone notifications on that device removes its subscription. Delivery stops when the associated website session is revoked or expires; expired subscriptions are removed by periodic cleanup. Account deletion removes these private alert records, preferences and subscriptions. Your phone or browser may retain notifications already delivered until you clear them.

5.9 Scan logs sent from the Droidex app

If you choose Send log to support on the Droidex app's Scanner card and then press Send report, the app uploads its current scan log (Section 4.6), any optional note and Discord username you type, and a fresh game screenshot when capture is available. The report dialog explains that a screenshot will be included. Nothing is uploaded unless you press Send. The app may suggest sending a report when scanning has been failing, but it never sends one by itself. Older app versions send only the log.

A scan log contains:

A scan log does not contain screenshots, captured pixels, recognized screen text, chat, your Droidex account, Epic account identifier, player name, or email address. The note is text you write; do not include passwords, tokens, device-link codes, or other sensitive information.

The screenshot is a separate attachment showing the current Fortnite game window. It can include player names, chat, account identifiers and other information visible in that window. It is captured from the app's native game capture in memory, may be resized or compressed for delivery, and is not saved in the rolling log, exported log or automatic diagnostics. The app does not capture another monitor or use a desktop screenshot as a fallback for support reports. If a fresh game screenshot cannot be captured, the app still sends the log and tells you that the screenshot was unavailable.

For each report, a linked player can also choose Include my linked account for support. This choice starts unchecked. If you select it, the API uses your authenticated Droidex account to add your account display name and, when available, your linked Discord user identifier to the support ticket so DubTrackr can find you and reply. A Discord username you type is labeled as supplied by you. These details appear separately in the private ticket summary and are not added to the diagnostic attachment. You can send a report without a linked account or Discord username. If the selected account cannot be verified, the app asks you to link again or clear the choice before sending.

The Droidex API checks the log, removes any local file paths, email addresses, and tokens it still finds, validates the screenshot and removes image metadata, and sends the report through the private bot relay described in Section 5.6. Information visible in the screenshot is not automatically redacted. The bot posts a short summary in the private Droidex support channel on Discord with the label Scan Log and attaches the log and available screenshot as separate files. The app shows the support ID it receives so you can quote it if you contact DubTrackr, and confirms screenshot delivery only when the service confirms the attachment. The API does not store scan logs or screenshots in its database. The website, API, hosting providers, and Discord may also process the network and technical metadata described in Section 5.5.

5.10 Google Analytics on the website

The Droidex website uses Google Analytics, a measurement service provided by Google, to count visits and see which pages and tools players use. Google Analytics runs only on the website. It does not run in Droidex Companion or the Dubtrackr desktop app, in the website pages either app shows inside itself, in the card renderer the apps display from the website, on the page that approves a PC for the app, or on your account pages (/account/), such as the account privacy page.

When Google Analytics runs, Google receives:

If you visit from the European Economic Area, the United Kingdom, or Switzerland, Google Analytics does not load, and sets no cookies, until you choose Allow on the Google Analytics bar. Choosing No thanks keeps it off. Droidex determines the region from the country Cloudflare associates with your connection and does not store that country. If Droidex cannot determine the region, it shows the bar. Visitors from other regions do not see the bar, and Google Analytics runs by default. Anyone can change the choice as described in Section 12.5.

DubTrackr does not use Google Analytics for advertising. Droidex sets Google's advertising consent signals to denied, so Google's tag does not store advertising identifiers or use this information to personalize ads. Google signals, which would associate visits with signed-in Google accounts, is turned off.

Google processes this information to provide Google Analytics to DubTrackr. Google explains its own use of information from websites that use its services at How Google uses information from sites or apps that use our services. Section 11 describes how long Google Analytics data is kept.

5.11 Optional Companion hardware and performance diagnostics

Droidex asks once whether you want to Share hardware and performance diagnostics. The choice is off by default and is remembered across ordinary app restarts and updates. Declining does not prevent local scanning or account features. This control is separate from Share my stats and the manual Send log to support control. If you enable diagnostics, the app automatically sends small summaries to DubTrackr's OVH-hosted Droidex API, normally once every two minutes, to help identify performance and stability problems across different computers.

Diagnostics can include:

An interrupted session does not establish that Fortnite or the computer crashed. It can also result from an update, restart, sleep, forced close or other interruption. Diagnostics do not include screenshots, pixels, recognized screen text, chat, process lists, computer names, disk or peripheral inventories, hardware serial numbers, arbitrary error messages, stacks, or full local file paths. Unsupported or unavailable hardware and timing information is recorded as unknown. The client stores a separate random diagnostics credential locally; the API stores only its hash. Hardware information is minimized on the client and checked against a fixed field list on the API. Ordinary connection metadata may also appear in the operational logs described in Section 5.5.

You may separately choose Include my account for support while this PC is linked. That allows DubTrackr's administrator to connect retained diagnostics with your Droidex account and display name when investigating support. The API derives the account from your authenticated app credential; the periodic diagnostic payload does not supply your Epic account identifier or player name. Account association is remembered for the account you chose and requires a fresh choice after switching accounts. Removing the association stops future account attachment and removes retained support links once the API confirms the request. Unlinked players and players who decline account association can still share diagnostics.

Without account association, the dataset is pseudonymous, not anonymous: the random installation identifier connects sessions from one installation and the hardware information can describe an unusual computer. Diagnostic data is restricted to the administrator and is not displayed in public player profiles, rankings or Discord. DubTrackr uses your consent for this optional processing.

You can withdraw either choice in Companion Settings. Turning diagnostic sharing off immediately stops collection/upload and clears queued diagnostics locally. The app requests deletion of that installation's active diagnostic profile and session records on the API. If the computer is offline or the API is unavailable, a minimal deletion request remains queued until it can be confirmed; the app does not continue uploading diagnostics during that time. Confirmed account deletion removes diagnostics explicitly associated with that account, but cannot find unrelated unlinked installations. Daily cohort totals contain no installation, session or account identifiers and are not selectively removable. Minimal revoked credential hashes remain for up to 90 days to prevent delayed requests from recreating withdrawn collection. Backup copies expire under Section 11 rather than being erased immediately.

5.12 Optional referrals

Referral rewards are being prepared and remain disabled. When a reviewed campaign is enabled, you can choose Participate in referrals and count my eligible Companion use in Companion Settings. Participation is optional and off by default for each account. Turning it off stops future referral-use collection and counting. This choice is separate from Share my stats, diagnostics, and Overwolf advertising choices.

If you participate, Droidex may store your invite code, the relationship between the inviting and referred accounts, the linked device, a protected random installation identifier, accepted usage times and accumulated qualifying time, session and retry records, and reward entries. Usage records describe whether Companion content is visible and active, whether there was recent interaction with that content, and whether timing and screen updates are fresh. They do not contain input text, pointer coordinates, screenshots, or the content of your interactions. Installation or elapsed time alone does not qualify. Ad impressions, clicks, playback, availability, and revenue do not determine qualification and are not included in referral-use records.

Only after a referral first qualifies and your inviter receives a reward, Droidex keeps a protected identifier derived from your Epic account for that season. This minimal eligibility record contains only the season, the protected identifier, and its expiration time. It stores no name, contact information, device identifier, Droidex account ID, or inviter ID. It is pseudonymous personal data, not anonymous data: Droidex can recognize the same Epic account if you return during that season, so deleting and recreating an account cannot produce another referral reward.

The protected identifier remains if you turn participation off or delete your account, until the published season end. Its use ends at that time. Expired identifiers are cleared automatically, normally within one minute while the service is healthy. Large cleanup batches, cleanup failures, or a service outage can delay physical removal; removal resumes at the next successful cleanup or service startup. Existing backup retention in Section 11 also applies.

Account deletion removes your normal account-linked referral code, installation association, attribution, and usage-session records. Your inviter keeps earned XP and its reward entry; deleting your account does not reverse that reward. The protected eligibility record does not preserve those deleted activity records or restore account data when you sign in again.

5.13 Session comparisons and rankings

What is uploaded. When uploading is on for your linked account, the app sends a summary of each Droid Tycoon session that ends after you saw the notice or said yes. A summary contains: the session's start and end time; time in the island and active time; how much of it Droidex could read; the app, game-data and island versions; Rebirth, Path and Super Rebirth rank at the start and end; the Rebirths and Super Rebirths made and the Rebirth each Super Rebirth was made at; the credits balance at the start and the credits, Upgrade Chips, Nova Crystals and Kyber Crystals Droidex saw you gain; Nova Crystals spent; crafts and Fusion jobs by variant and rarity, and refused craft reads; and, when you opened the Player Stats screen at both ends of the session, how much its totals changed. The app also sends your Super Rebirths: the Rebirth each was made at, the Paths, its end date, how long the cycle took and how much of it Droidex saw. Summaries contain no screenshots, recognized screen text, names, chat or game-world positions. Sessions shorter than three minutes in the island, sessions played while unlinked, and sessions from before you saw the notice or said yes stay on your computer.

Exact times. The API uses a session's start and end time only to check that two of your devices were not counted for the same time. It removes them after 72 hours. The stored summary then keeps only its date in UTC and its durations.

Who sees it. Only you see your uploaded summaries and your rank. They are not shown to other players, on profiles, on leaderboards or in Discord. Each night the API builds anonymous rank charts from the summaries of players who upload. A chart covers players in the same economy period (the time between game updates that change prices or income) and, for credits and Rebirths per hour, the same Rebirth band. Each player counts once, by their typical session over the last 30 days, and only after three qualifying sessions of at least 10 minutes from a current app version. The highest and lowest 1% are left out. A group of fewer than 30 players gets no chart, and the number of players is not shown below 10. The charts also carry a community average for the session report's "You vs your usual": six rates per hour in Droid Tycoon (credits, Upgrade Chips, crafts, Rebirths, Kyber Crystals and Nova Crystals), averaged for each player and then across players, with the number of players. It uses every qualifying session of at least 10 minutes from a current app version in the economy period and has no minimum group size, so it shows however few players upload. When very few players upload, the average can be close to one player's own numbers. Charts hold only band edges, such as the value needed for "Top 25%", these averages and the group sizes: no account identifier, name, device or individual session. Charts are public reference data that the app and website download, and your band is worked out on your computer.

Checks. The API checks summaries against game data, against the Player Stats changes when present, and against your other sessions. A summary that does not fit, such as one that overlaps a session from another of your devices or a Super Rebirth whose Nova Crystals do not match the game's payout table, is kept but does not count toward charts. DubTrackr's administrator can exclude a session from the charts and rebuild them.

Defaults by region and age. Section 5.15 explains how Droidex tells your region, and Section 5.14 the age band.

Where you are18 and over16 to 1713 to 15Under 13No birthday given
Outside the European Economic Area, the United Kingdom and SwitzerlandOn after a one-time notice in the app; you can turn it offOnly if you chooseOnly if you chooseNeverNothing uploaded
United KingdomOnly if you chooseOnly if you chooseOnly if you chooseNeverNothing uploaded
European Economic Area and Switzerland, or region unknownOnly if you chooseOnly if you chooseNeverNeverNothing uploaded

"Only if you choose" means a one-time question with two equal answers, Count my sessions and Not now. Nothing is uploaded until you choose to count your sessions. Either way you still see your rank from the charts.

Turning it off. Turn session comparisons off in the app's Settings or on the account privacy page of the Droidex website. Turning it off stops uploads and immediately deletes every session summary and Super Rebirth record you uploaded. The choice stays off across restarts and updates; an update never turns it back on, and a change of region never turns a "no" into a "yes". Charts already built on earlier nights cannot be separated by player and remain, but they contain nothing that identifies you. On the website you can also download your uploaded summaries, or delete them without changing your choice.

How long. Session summaries are deleted 180 days after the session date, and Super Rebirth records 180 days after their end date, by a cleanup that runs every 15 minutes while the service is healthy. Rank charts contain no personal data; the newest 400 are kept. Each choice you make (the notice shown, yes or no) is kept as a record of what you chose and when, with the notice version and the region and age band it was made under, while your account exists.

DubTrackr can turn session uploads off for everyone with a server switch.

5.14 Your age band

The app may ask When were you born? once: at the end of your first session report, or when you link an account if you have not answered yet. It is never asked during play. You can also answer on the account privacy page of the Droidex website. You pick a month and a year; nothing is selected in advance. The app or the page works out your age band on your device (under 13, 13 to 15, 16 to 17, or 18 and over) and keeps only the band and when you answered. The month and year are not kept or sent. When your app is linked, or you answer on the website, the band is also stored with your Droidex account so it applies on every computer.

If you entered the wrong birthday, you can fix it yourself with Fix my birthday in the app's Settings › Privacy & Age or on the account privacy page, for example from a teen band to 18 and over or back. Droidex keeps a record of each answer and each change (the band before and after, the region group, whether it was given in the app or on the website, and when) while your account exists. A fixed band changes the upload defaults in Section 5.13 and the profile default in Section 7.4 from then on. An answer of under 13 cannot be changed in the app; if it was a mistake, contact dubtrackr.support@gmail.com.

Answering is optional for the app's features on your computer, which all keep working. Without an answer, nothing is uploaded for rankings. The band decides the upload defaults in Section 5.13 and the profile default in Section 7.4.

If you tell Droidex you are under 13, the app does not link to a Droidex account and uploads nothing for rankings. If the app was already linked, or you answer on the website, Droidex deletes that Droidex account and its server records, as described in Section 12.1; the app unlinks and the website signs you out. Features on your computer keep working.

5.15 How Droidex tells your region

The Droidex API uses the country Cloudflare associates with each connection to place you in one of three groups: the European Economic Area and Switzerland; the United Kingdom, including the Crown Dependencies and Gibraltar; or elsewhere. It stores only that group and when it last checked it. It does not store the country or your IP address apart from the network logs described in Section 5.5. When Cloudflare gives no usable country, for example over some VPNs, Droidex applies the rules for the European Economic Area. You can also choose the stricter European rules yourself in the app or on the account privacy page.

5.16 Remove Ads subscriptions

Remove Ads is an optional subscription that turns off the Overwolf ads in our apps. It is sold through Tebex, Overwolf's payment partner. There are monthly, quarterly and yearly plans.

Payment. Checkout opens in your web browser through Overwolf's subscription service and Tebex. Tebex collects and processes your payment and billing details under its own terms and privacy policy. DubTrackr never receives your card number or other payment details. We only learn whether you have a plan, which plan it is, and whether it is active or cancelled but still paid up.

In Droidex Companion. Your plan belongs to your Overwolf account, so you need to be signed in to Overwolf to buy one. Droidex Companion uses your Overwolf user ID and a short-lived Overwolf session token to ask Overwolf's subscription service (subscriptions-api.overwolf.com) whether your Overwolf account holds one of our plans. Checkout also passes your Overwolf user ID so the purchase lands on your Overwolf account. The app checks when it starts, when your Overwolf sign-in changes, and again every few hours. It keeps the last confirmed answer on your computer and trusts it for up to 3 days. If a check fails, ads stay on. Ads are off on every PC signed in to the same Overwolf account.

On your Droidex account. When Droidex Companion is linked, it also sends that short-lived Overwolf session token to DubTrackr after each check. DubTrackr then asks Overwolf's subscription service the same question itself. It saves only the answer with your Droidex account: which plan, whether it is active or cancelled but still paid up, and when Overwolf confirmed it. The token is not stored. That answer is how the Dubtrackr desktop app on the same account knows to turn ads off. It is trusted for up to 3 days and replaced by each new check.

Cancelling. You can see and cancel your plan at checkout.tebex.io/payment-history. The Manage button in the app opens that page. After you cancel, ads stay off until the period you paid for ends. Billing, renewal and refunds are covered in the Droidex Terms.

5.17 Settings saved to your account

When the Companion is linked and Save my settings to my account is on, Droidex saves these app settings with your account. They then follow you to your other PCs and into the Dubtrackr desktop app. The switch is on by default, and you can turn it off in Companion Settings › Account.

They never include screenshots, text read from the screen, chat or sign-in details. Each group of settings keeps its last 20 earlier versions with the time and the PC that saved it. That way a change that lost to a newer change from another PC isn't lost without a trace. Turning the switch off stops new saves. Settings already saved stay until you delete your account, which removes them and their earlier versions.

Moving from Droidex Companion to the desktop app. Droidex Companion saves a move file on your PC at %LOCALAPPDATA%\Dubtrackr\migration\. It holds the settings above, your Sentinel alert choices and your age band, and never a sign-in. The desktop app asks before it reads that file. Move to the Dubtrackr app also shows a one-time move code that links the desktop app to the same account. The code lasts 10 minutes, works once, and is stored only as a keyed hash.

5.18 Fortnite Battle Royale matches

What the app records. For each Fortnite Battle Royale match (not Creative islands or Droid Tycoon), the desktop app records on your computer: when the match started and ended and how it ended; the playlist, the mode (solo, duo, trio or squad), Build or Zero Build, and whether it was ranked; your placement and how many players and teams started; your eliminations, knocks, assists, revives, deaths, damage dealt and taken, accuracy, shots fired and time survived, where Overwolf provides them; the storm phase at the end; your position on the island, at most once every 2 seconds and up to 1,000 positions; the kill feed you saw, with the names in it; your team's names; your display name; Overwolf's match identifier; and the app version. Players in anonymous mode appear as "anonymous". Records contain no screenshots, chat or voice.

What is uploaded. When match uploads are on for your linked account, the app sends each finished match's record to DubTrackr. The server stores it with your account and the device that sent it, so your match history shows in the app on any PC. Matches that ended before you saw the notice or said yes, matches played while unlinked, and matches more than 30 days old stay on your computer.

Defaults by region and age. The rules in the table in Section 5.13 apply: on after a one-time notice for adults outside the European Economic Area, the United Kingdom and Switzerland; only if you choose in the United Kingdom, the European Economic Area, Switzerland, an unknown region, and for players aged 13 to 17; never for players aged 13 to 15 in the European Economic Area or Switzerland; never under 13; nothing without a birthday. Your choice for matches is separate from your choice for session comparisons. DubTrackr can turn match uploads off for everyone with a server switch.

Who sees it. Only you see your match history, except for the squad paths and the leaderboards and benchmarks Section 5.19 describes.

Sharing a match. Share in the app creates a link with a random code, such as fortnite.dubtrackr.win/match/ followed by the code. Until that site opens, the same match also opens at droidex.dubtrackr.win/fortnite/match/ with the same code. Anyone with the link can see your display name, the match date (not the time of day) and length, the mode, your placement and stats, the storm phase, your path, the kill feed and your team's names. The page does not show your account, your device, the exact start time or Overwolf's match identifier. It asks search engines not to index it and does not load Google Analytics. Stop sharing turns the link off at once, and sharing again makes a new link. Anyone who already saw the page may have kept a copy. A match you share can also show the path of a teammate who uses Dubtrackr and has squad sharing on, under the rules in Section 5.19, with their display name, or no name if they play in anonymous mode. It never shows the path of a teammate who doesn't use Dubtrackr or has squad sharing off, and it never shows account IDs.

Other players' names. The kill feed and team names are the names the game showed you. They are stored only in your match record and appear in public only on a match you share.

Turning it off and deleting. You can turn match uploads off in the app's Fortnite settings. That stops uploads and immediately deletes every match you uploaded, shared ones included. You can also delete one match, or all of them, without changing your choice. Deleting your account deletes them too.

How long. Uploaded matches are deleted 180 days after the match by a cleanup that runs every 15 minutes while the service is healthy. A shared match is kept while it is shared; once you stop sharing, the 180-day rule applies again. Each choice you make (the notice shown, yes or no) is kept as a record of what you chose and when, with the notice version and the region and age band it was made under, while your account exists.

Lifetime and season stats. The app's Fortnite profile shows lifetime and current season Battle Royale totals (wins, matches, eliminations, K/D, win rate, eliminations per match, minutes played and level) from fortnite-api.com, an independent service that Epic Games does not endorse. To get them, the DubTrackr server sends the Epic account ID to fortnite-api.com and keeps the answer in memory for up to 10 minutes; it is not stored in the database. Fortnite-api.com has only the stats Epic makes public. If you turned off Public Game Stats in Fortnite's privacy settings, the app says your stats are private. The server can look up the public stats of any Epic account by its account ID, as fortnite-api.com itself can.

5.19 Fortnite replays, ranks, leaderboards and the item shop

These features are in the Dubtrackr desktop app's Fortnite module. DubTrackr can turn each off for everyone with a server switch.

Replay files. Fortnite can save a replay of each match on your computer, in %LOCALAPPDATA%\FortniteGame\Saved\Demos. When Read my replay files is on (it is on by default; you can turn it off in the app's Fortnite settings), the app reads the replay of a Battle Royale match you just played, on your computer, after Fortnite has finished writing it. It never changes or uploads the file. From it, the app adds to that match's record: each player in the match with their Epic account ID, display name (left out for players in anonymous mode), team, team placement and elimination count, and whether they are a bot; the eliminations and knocks in the match, with the time, who and whom, the weapon and whether it was a headshot; your own headshots and the materials you gathered and used; and the Fortnite version and the name and version of the reader. It also adds the match's session identifier, which every player in that match shares, and the movement of you and your teammates through the match, up to 1,000 positions each. It never adds the movement of a player on another team. If match uploads are on (Section 5.18), this goes to DubTrackr inside that match record, and nothing else from the replay file does. The app also adds the weapons in your loadout when the match ended, from Overwolf's game events.

Other players in a replay. Other players' account IDs and names from a replay are stored only inside your match record. DubTrackr never shows the account IDs publicly (a match you share shows the names the game showed, never the IDs) and does not use them to build profiles of people who aren't Dubtrackr users. They are deleted with the match.

Squad paths. Your teammates' movement from your replay file is stored with that match record and follows its rules in Section 5.18. You see it in the app on any PC. If a teammate also uses Dubtrackr and uploads the same match, and both of you have squad sharing on (Section 7.5), each of you can see the other's path, end-of-match numbers (eliminations, knocks, assists, revives, damage dealt and taken, accuracy), placement and how the match ended, and the teammates' movement from the other player's replay file. DubTrackr shows this only when both records come from the same match and team, each player's replay names the other on that team, and neither has blocked the other. It checks this every time, so turning squad sharing off or blocking the other player stops it at once. A player on another team never sees any of it.

Weapons. From your matches, DubTrackr keeps which weapons you eliminated or knocked players with, how many, and which were in your loadout at the end, with each match. Your top weapons on your profile come from these. Weapon stats across Dubtrackr players are totals over everyone's matches and never show a player.

Your rank. The app can save your ranked tier and progress for Ranked Battle Royale and Ranked Zero Build, with where it came from: Overwolf's game events, a replay, Fortnite's log, the app reading Fortnite's ranked screens, or you setting it yourself. Each saved rank has the season and the time it was seen. Saving ranks follows your match upload choice (Section 5.18). Only you see your rank history; a rank you set yourself never appears on a leaderboard.

Benchmarks. Your profile can show where your numbers sit against all Dubtrackr players in the same mode, such as "top 5 %" for K/D. These are worked out from everyone's uploaded matches, only for modes where at least 50 players have at least 20 matches, and show only your own position. Nobody sees another player's numbers through them.

Leaderboards. Battle Royale leaderboards on fortnite.dubtrackr.win and in the app rank players by wins, eliminations, K/D, win rate, average placement, damage and verified rank, from uploaded matches. Nobody is on them by default: you appear only after you turn them on in the app's Fortnite settings, and only with at least 10 matches in the board's filters. You can turn them off at any time. A board shows your Epic display name, your value and how many matches it counts, and for ranked boards your rank from game data or screen reading. It never shows your account ID.

Public player card. Anyone can search an Epic display name on fortnite.dubtrackr.win and see that player's card: the Epic display name, level and lifetime and season stats from fortnite-api.com. These come from Epic and are already public unless the player turned off Public Game Stats in Fortnite, and the card doesn't say whether the player uses Dubtrackr. A card's page address contains the player's Epic account ID. If you turn on the public card in the app's Fortnite settings, your card also shows your benchmark positions (above), a rarity frame for your best one with the stat and mode it is for, and your last 10 uploaded matches, each with its date, mode, Build or Zero Build, ranked, and your own placement, eliminations and damage. It never shows the other players in those matches. With it on, a search for the Epic display name on your Dubtrackr account finds your card even when your Fortnite stats are private. It is off by default for everyone, needs an age band, and doesn't show for a banned account. You can turn it off at any time in the same place, and your card goes back to the public stats on the next search.

Item shop and wishlist. The item shop, news and Epic's server status come from fortnite-api.com and Epic's public status page; DubTrackr sends them nothing about you. Your wishlist (the shop items you mark, with their names and when you added them) is stored with your account. When an item on it is in the shop, DubTrackr tells the app once that shop day, when the shop loads or when the app next connects that day, so it can show you a notice. It records the date it told you, so you aren't told twice.

How long. Replay details, weapons and the loadout are part of the match record and follow its rules in Section 5.18. Saved ranks are deleted 180 days after they were seen, when you say no to match uploads, when you delete them in the app, and with your account. Your leaderboard choice, public card choice and wishlist are kept until you change them or delete your account. Leaderboards, benchmarks and weapon stats are recalculated from current matches every few minutes, so a deleted match drops out of them.

6. Anonymous and unlinked service-improvement data

6.1 Droid observation records

Droidex readers can identify droids on the conveyor belt, in the player’s hand, in the craft banner, in a rare-spawn line, or as a companion. After account linking, Droidex may send an observation event containing:

The request is authenticated to prevent unauthorized submissions, but the account identity is discarded before the observation is stored. The observation table contains no account identifier or device identifier. The per-launch session key is not derived from your account, computer, or device, is not saved to disk, and is replaced when the app restarts.

A short-lived network log may separately contain ordinary network metadata, but the stored observation record is designed not to identify the player.

Droidex uses these records to measure in-game spawn and pickup patterns, evaluate reader quality, distinguish app-reader changes from game changes, and prevent duplicate retries from being counted twice.

6.2 Why observations survive account deletion

Observation records cannot be selectively removed through account deletion because they do not contain the identifier needed to find which rows came from a particular account. They remain in the aggregate observation dataset after account deletion.

6.3 Calibration profiles

When you save a screen-region calibration profile, Droidex may submit:

The free-text profile name and local profile identifier are not transmitted. The Droidex API rejects a calibration submission that contains the profile name rather than silently accepting it. Calibration records contain no account identifier or device identifier.

Droidex uses pooled calibration profiles to improve default capture regions for different resolutions and interface configurations.

6.4 Why calibration profiles survive account deletion

Calibration profiles cannot be located by account because they do not contain an account or device identifier. They therefore remain in the calibration dataset after account deletion.

6.5 Website audience and guide-action counters

The Droidex website creates a random browser identifier in local storage. The server stores a one-way hash of that identifier to count total views and approximate unique browsers. It does not attach a page path, account identifier, or Epic identity to that counter.

When someone views any public page, follows a guide link, opens a calculator, starts using the Rebirth Tracker, changes collection progress, visits an update page, or uses a site search, Droidex adds one to a daily aggregate containing the public page, destination path, and action type. Search events do not contain the search text, selected result, or droid name. Collection events do not contain the affected droid or variant.

On the first page load, Droidex may also count the referring website's normalized hostname, such as google.com. Droidex does not store the full referrer URL, path, query string, or fragment. Same-site referrals are not recorded.

These measurement totals contain no browser identifier, account identifier, Epic identity, or individual browsing history. Ordinary short-lived network logs may still contain the technical metadata described in Section 5.5. Google Analytics, described in Section 5.10, is a separate service with its own cookie identifiers.

7. Information shared with other players

7.1 Share my stats

After you link Droidex to your account, Share my stats is enabled by default because Droidex's live lobby and coordination features depend on participating players exchanging a limited set of current in-game information. Droidex may share the following with participating players in the same lobby:

Turning this control off stops future sharing governed by the control and closes Droidex's live lobby connection. It stays off across app restarts, updates and account switches until you turn it back on. Features that depend on reciprocal lobby state, including same-lobby statistics, player identification, and base ownership, may stop working or become materially limited. Turning the control off does not by itself delete account-linked records already held by DubTrackr; those records remain subject to the retention and deletion rules in Sections 11 and 12.

Because the feature is enabled by default after account linking, DubTrackr does not treat the default state as consent. The shared fields are limited to in-game identity and gameplay state, are shared only for the participating-player community experience, and are not supplied to advertising networks by DubTrackr.

7.2 Base ownership sharing

Droidex can publish a confirmed base-ownership binding so another participating player's app can identify whose base the player is standing in. The binding associates the player's in-game identity with the confirmed base identifier. Publication occurs as part of the default-on connected community service when the app is linked, Share my stats is on, and a base has been confirmed.

Base ownership is a core input to Droidex's same-lobby coordination and is not presented as a separate optional community feature in the current version. Turning Share my stats off stops future base publication but also closes the live lobby connection and disables or materially limits connected features that depend on shared state. Account deletion removes the active account-linked base record as described in Section 12; turning sharing off does not itself delete records already retained under Section 11.

7.3 Other players’ names

Other players’ names reach Droidex through Overwolf’s me and team events for players in the same lobby or squad. Droidex holds those names in memory to draw the lobby list. Droidex does not transmit those other players’ names to its service.

7.4 Public player profiles and season rankings

Your profile page and leaderboard participation have separate controls. When your profile page is public, its display name, selected Droidex droid portrait, collection and Flawless totals, app-observed Droidsmith level, unique verified droid/variant craft record and totals, current Season XP and rank, season history, and achievements can be visible to anyone, subject to your profile detail settings. Turning on Appear on public leaderboards allows public ranking and final season placement. A leaderboard entry always shows your display name, rank, and score, even when your profile page is private.

Turning leaderboard participation off removes your entry from public rankings and excludes it from final placement. Making your profile page private prevents public access to the page and leaves your separate leaderboard choice unchanged. Droidex may retain account-linked verified activity and score records while either control is off so that linked synchronization, integrity review, and a later choice to participate can work. These controls do not delete retained account records. Account deletion removes the active profile and account-linked competitive records as described in Section 12.

Private by default in Europe and the UK, and for teens. If Droidex places you in the European Economic Area, Switzerland or the United Kingdom, cannot tell your region, or you gave a 13 to 17 age band, your profile page stays private and you do not appear on public leaderboards until you turn either on yourself. Profiles that an earlier update made public are held private in the same way: Droidex sets the earlier settings aside and restores them the next time you start the linked app or visit the website from elsewhere with no teen age band. Once you set your profile visibility or leaderboard participation yourself, Droidex keeps your choice and no longer changes it. Session comparisons (Section 5.13) never appear on profiles or leaderboards.

Public leaderboards never expose Epic account identifiers, email addresses, Discord identities, device identifiers, authentication material, or screen images.

7.5 Fortnite squad sharing, friends and the party finder

These features are in the Dubtrackr desktop app's Fortnite module. Each one needs an age band (Section 5.14) and a linked account, and DubTrackr can turn each off for everyone with a server switch.

Defaults by age. For players 18 and over, squad sharing, Friends see when I'm online, Friends see what mode I'm playing, Friends see my recent matches and Let my Epic friends see I use Dubtrackr start on. For players aged 13 to 17 they start off; you can turn the first four on, and Let my Epic friends see I use Dubtrackr stays off and locked until you are 18. Without an age band all five are off. You can change them in the app's Fortnite settings. If you had chosen Friends see my activity before it was split into the three Friends see settings on November 1, 2026, your choice was copied into all three.

Squad sharing. While you are in a Fortnite party or match with another Dubtrackr player, and both of you have squad sharing on, each app sends the other, through DubTrackr's server: whether you are alive, knocked or eliminated, your eliminations, knocks, assists, accuracy and damage taken, and the weapons and their rarity in your loadout slots, from Overwolf's game events, at most twice a second. To pair you, your app sends DubTrackr your Fortnite party identifier and the names in your lobby, or the match identifier, your team number and your teammates' names. Both players must name each other, so a player on another team can't receive your stats. None of this is written to storage; it is held in memory while the app is connected and dropped when the match ends. The only thing kept is the squad table you upload with your own match record (your teammates' names and end-of-match numbers), under the rules in Section 5.18. Squad sharing also decides whether a Dubtrackr teammate can see your path and end-of-match numbers from a match you both uploaded, and whether your path can appear on a match they share (Section 5.19, Squad paths).

Friends. You can send a friend request by Epic display name or by Discord name or user ID. DubTrackr stores friend requests and friendships with your account. A search by name never shows a player aged 13 to 17 to an adult, or an adult to that player, unless they are matched Epic friends or the younger player has ticked the parent acknowledgement below, and a blocked player gets the same answer as a name that doesn't exist. Friends see each other's Epic display name.

Parent acknowledgement for players aged 13 to 17. A player aged 13 to 17 can use friends with adults after ticking: "My parent or guardian knows I use Dubtrackr's friends features and takes responsibility for monitoring how I use them." It is the player's own statement: DubTrackr does not verify it or contact a parent. DubTrackr records that you ticked it, when, your age band, the version of the text, and the country (with the US state or Canadian province) your request came from, so the record shows which rules applied; withdrawing it is recorded the same way. Where a law needs more than this, such as a minimum age or a parent's verified consent, the checkbox isn't offered and the app names the rule; DubTrackr reads the country from each request for this and does not store it on your account. If a later request comes from a place whose rule rules it out, the acknowledgement is withdrawn. Withdrawing it, by you or for that reason, ends your friendships and waiting friend requests with adults, except matched Epic friends. It covers friends only: it doesn't open adult party finder listings and doesn't change your defaults.

What friends see. Three settings decide it. With Friends see when I'm online on, your friends see whether the app is online and whether you are in the menu, in a Battle Royale lobby or in a match. With Friends see what mode I'm playing also on, they see the mode, Build or Zero Build and ranked. With Friends see my recent matches on, your friend summary shows your last five uploaded matches (date, mode, placement, eliminations, assists, damage dealt and time survived). Your app reports what you are doing; DubTrackr keeps it in memory only. Friends also see your lifetime and season stats from fortnite-api.com, which are public anyway (Section 5.18). Strangers see none of this.

Epic friends import. If you allow Epic's Friends permission (Section 5.1), DubTrackr reads the Epic account identifiers of your Epic friends who have allowed Epic Account Services apps, and matches them against Epic accounts connected to Dubtrackr whose owners are 18 or over and have Let my Epic friends see I use Dubtrackr on. This happens when you connect Epic or run the import, and again whenever the app refreshes the import with the stored refresh token (Section 5.1). Only those matches are stored, replacing the previous import, with the time of the import and how many friends were read and matched. Your Epic friends list itself is not stored. If you turn Let my Epic friends see I use Dubtrackr off, you disappear from other players' matches at once.

Party finder. A listing shows the mode, Build or Zero Build, ranked, region, platform, input, goal, an optional note of up to 140 characters, and a snapshot of your public stats taken when you post it: your fortnite-api.com level, wins, matches, K/D, win rate and eliminations per match, and your Dubtrackr history over 30 days (matches, wins, average placement and eliminations). It does not show your name. Notes can't contain links, emails, phone numbers or social handles. A request to join carries the same kind of snapshot of the requester. When the listing's player accepts, each of you sees the other's Epic display name so you can add each other in Fortnite. You only see listings from players in your own age group: 13 to 17, or 18 and over. The parent acknowledgement doesn't change this. A listing lasts up to 60 minutes and closes when you go offline. If you are 18 or over you can tick Also post in the Dubtrackr Discord: the DubTrackr bot then posts the listing's details, note and stats snapshot, without your name, in the Dubtrackr Discord server's looking-for-group channel, where anyone in that server can see it, and deletes the post when the listing closes. DubTrackr keeps the post's Discord message identifier with the listing so the bot can delete it.

Report and block. You can report a listing or a request, with an optional note of up to 300 characters, and block a player. A report stores who reported whom, the reason, your note and a copy of the listing's note, so a Droidex moderator can act. Each moderator decision is kept in the moderation log. Three reports close a listing until a moderator reviews it, and a moderator can ban a player from the party finder for a set time. A block is account-wide: it ends a friendship, cancels requests both ways, hides each of you from the other's searches, listings and squad sharing, and also applies to trading chat. It keeps the name you saw only if one had been shown to you.

Teammates without Dubtrackr. In a duo, trio or squad match, the squad overlay can show a teammate's season wins, K/D and matches from fortnite-api.com, which are public when that player has Fortnite's Public Game Stats on. Your app sends DubTrackr the teammate's Epic display name, or Epic account ID when the match gives one, once per match. The server asks fortnite-api.com and keeps the answer in memory for up to 10 minutes; nothing is stored. A teammate who hides their stats shows as "Stats private".

How long. Live squad state, pairing reports, online status and teammates' season stats are never stored. Friendships, settings and blocks are kept until you change them or delete your account. Answered friend requests are deleted 30 days after the answer. Party listings and their requests are deleted 24 hours after the listing closes. Reports are deleted after 180 days. A listing whose Discord post is still up waits up to 7 days for the bot to delete it. Parent acknowledgement records are kept while the account exists. The Epic refresh token is kept as Section 5.1 says. Deleting your account deletes all of it.

8. Advertising and Overwolf

Both apps show Overwolf ads. Droidex Companion uses the Overwolf Ads SDK. The Dubtrackr desktop app uses Overwolf's ad element for its Electron platform and shows two ad units beside its pages. Overwolf loads and operates the ads in both apps. They can run for every player, including players who have not linked a Droidex account. They are not controlled by the Share my stats setting.

Ads do not show:

Droidex does not provide Overwolf's ad system with:

The desktop app tells Overwolf's ad system which of its pages an ad is on (for example Home) and which of its two slots it fills. It sends nothing else of ours with the ad.

Ad consent in the desktop app. When you start the desktop app, it asks Overwolf whether ad consent is required where you are. It usually is in Europe. When it is, the app shows a consent screen before the first ad, with Accept all and Manage. Manage opens Overwolf's own ad privacy settings, where you can choose purposes and vendors. The app keeps your answer in its data folder (Section 4.8) and asks again on each start until you answer. Anyone, anywhere, can change their choices later in Settings › Ad privacy › Manage. Droidex Companion uses Overwolf's own consent screens on the Overwolf platform.

Overwolf controls ad selection, ad delivery, advertising partners, and the information processed by its advertising system. Overwolf states that its advertising systems may process advertising or online identifiers, device and technical information, active application, process, or window information, privacy-consent strings, ad-call information, approximate location derived from network information, and advertising interactions. Actual processing depends on Overwolf’s systems, the user’s region, privacy choices, and the applicable advertising partners.

Overwolf provides its own consent-management and privacy controls. Users should review and manage those choices through Overwolf. Overwolf’s processing is governed by the Overwolf Platform Privacy Policy, not this Policy.

Neither app includes a separate general-purpose analytics SDK such as Google Analytics, Sentry, Amplitude, Mixpanel, or Segment. The Droidex website uses Google Analytics as described in Section 5.10.

9. Other disclosures and service providers

Droidex may disclose or make information available to the following categories of recipients only for the purposes described in this Policy:

Overwolf

Overwolf provides the platform both apps run on, the game-event and overlay services, the ads, the ad consent tools and the subscription service that checks Remove Ads plans. Overwolf independently processes platform, advertising and subscription information under its own policies.

Tebex

Tebex, Overwolf's payment partner, sells Remove Ads plans and processes their payments, renewals and cancellations. Tebex independently processes your payment and billing information under its own terms and privacy policy. DubTrackr does not receive your payment details.

Epic Games

Epic Account Services provides the sign-in flow and authorized Epic account identity information. If you allow its Friends permission, Epic also returns your Epic friends' account identifiers for the Epic friends import, and a refresh token that lets DubTrackr update that import (Sections 5.1 and 7.5). Epic independently processes Epic account information under the Epic Games Privacy Policy.

Cloudflare

Cloudflare provides website delivery, network protection, and Cloudflare Tunnel services. Cloudflare may process network and request metadata needed to provide those services.

OVHcloud

OVHcloud provides infrastructure on which the Droidex API and PostgreSQL database operate.

Discord

Discord hosts the private Droidex support channel used to receive tickets submitted through the Droidex support form. The DubTrackr bot running on OVHcloud posts the reply email, optional name, support category, summary, message, submission source, and ticket identifier to that channel. If you post a party finder listing in the Dubtrackr Discord (Section 7.5), the bot posts its details, without your name, to that server's looking-for-group channel. Discord independently processes that information under the Discord Privacy Policy.

fortnite-api.com

Fortnite-api.com, an independent service that Epic Games does not endorse, provides the lifetime and season Battle Royale stats in the Dubtrackr app's Fortnite profile. The DubTrackr server sends it the Epic account ID being looked up and nothing else about you (Section 5.18); for a squad teammate without Dubtrackr it may send the teammate's Epic display name instead (Section 7.5). It also provides the item shop, Fortnite news and the current Fortnite version, for which the server sends it nothing about you (Section 5.19). When someone searches an Epic display name on fortnite.dubtrackr.win, the server sends it the name searched (Section 5.19). Epic's public status page provides Fortnite's server status, and the server sends it nothing about you either.

Google

Google provides Google Analytics for the Droidex website and processes the information described in Section 5.10 to provide that service.

Other participating players and public profile visitors

Droidex shares the lobby statistics and base information described in Section 7 as part of the connected community service and subject to the Share my stats control. Public profile visitors can see the limited fields you allow on a public profile page. When leaderboard participation is on, leaderboard visitors can see your display name, rank, and score independently of profile page visibility, as described in Section 7.4.

Legal, safety, and security recipients

DubTrackr may preserve or disclose information when reasonably necessary to comply with law, respond to valid legal process, protect users, investigate fraud or abuse, enforce applicable terms, or protect the security and integrity of Droidex.

Business transfer

If ownership or operation of Droidex is transferred, relevant information may be transferred as part of that transaction, subject to this Policy and applicable law. Users will receive notice of a material change where required.

DubTrackr does not sell personal information for money. DubTrackr does not provide Epic identity or account-linked gameplay data to advertising networks for cross-context behavioral advertising. Overwolf’s separate advertising processing is described in Section 8.

10. Purposes and legal bases

Where data-protection law requires a legal basis, DubTrackr uses the following:

PurposeInformation involvedLegal basis
Provide local OCR, overlays, tracking, account linking, synchronization, collection, and requested community featuresScreen-derived values, Epic identity, authentication records, player state, collection and community dataPerformance of the service requested by you and performance of a contract
Operate the default-on connected lobby, including Share my statsSelected lobby statistics and display namePerformance of the connected community service requested by the user and legitimate interests in providing reciprocal, limited same-lobby coordination; users can object by turning the control off, although dependent connected features will stop or become limited
Provide base-ownership identification as a core part of the connected lobbyDisplay name or player identity associated with a confirmed basePerformance of the connected community service requested by the user and legitimate interests in providing limited same-lobby identification and coordination; future publication stops when Share my stats is turned off, although dependent connected features will stop or become limited
Operate verified player profiles, season scoring, integrity review, rankings, final results, and badgesPublic display name, selected droid portrait, and profile choice; baseline; verified event and evidence records; score ledger; season results; achievementsPerformance of the requested linked and competitive services and legitimate interests in fair, auditable rankings and abuse prevention; profile page visibility and leaderboard participation use separate controls
Offer optional referrals and count qualifying Companion useInvite codes, account and installation associations, usage-session records, and qualifying timeConsent, withdrawable by turning referral participation off in Companion Settings
Prevent repeated referral rewards within a season after account deletionA protected season-specific identifier derived from the referred player's Epic account, the season, and expiration timeLegitimate interests in preventing repeat rewards using a minimal, time-limited eligibility record
Secure accounts and infrastructure, prevent abuse, troubleshoot failures, and enforce rulesAuthentication records, device links, IP and network metadata, operational logsLegitimate interests and, where applicable, legal obligations
Improve reader accuracy, spawn measurement, and calibration defaultsUnlinked observation and calibration recordsLegitimate interests in improving Droidex and measuring game events using minimized, non-account-linked data
Measure website visits and which pages and tools players use with Google AnalyticsPage addresses and titles, referring pages, site-search words, cookie identifiers, device and browser information, approximate location, and page interactionsConsent for visitors from the European Economic Area, the United Kingdom, and Switzerland. Legitimate interests in understanding how players use the website for visitors from other regions, who can object at any time from the Cookie Notice
Respond to support and privacy requestsContact information and information you submitPerformance of requested support, legitimate interests, and legal obligations
Build anonymous rank charts from uploaded session summaries and Super Rebirth records, and check them for errors and cheatingSession summaries, Super Rebirth records, the linked account and device, and the exact session times for 72 hoursConsent, withdrawable at any time, for players in the European Economic Area, Switzerland and the United Kingdom, players aged 13 to 17, and anyone who chose to count their sessions. For adults elsewhere where the upload is on by default: legitimate interests in offering rankings that show players how they compare, using minimized numbers that only the player sees; you can object at any time by turning session comparisons off, which also deletes what you uploaded
Keep a record of session-comparison choicesThe choice, its time, the notice version, and the region group and age band it was made underLegal obligation to demonstrate consent where consent is the basis, and legitimate interests in honouring each player's choice
Apply age- and region-appropriate defaults, and stop collection from players under 13Age band and each change to it, region group, and when each was set or checkedLegal obligation and legitimate interests in protecting children and applying the privacy rules of each player's region
Diagnose Companion performance across different PCsOptional hardware and performance summaries, random installation/session identifiers, and separately chosen support account associationConsent, withdrawable from Companion Settings
Check whether you have a Remove Ads plan and turn ads off for itOverwolf user ID and short-lived session token, the plan and its state, when it was last confirmed, and the linked PC that checkedPerformance of a contract, the subscription you bought
Show the ad consent screen in the desktop app and keep your answerWhether Overwolf says consent is required, your answer and when you gave itLegal obligation where consent for ads is required, and legitimate interests in respecting your choice
Retain or disclose records required by lawRelevant account, transaction, security, or request recordsLegal obligation

Overwolf determines the legal bases for its separate platform and advertising processing.

11. Retention

Droidex uses the following retention rules and criteria:

Data or copyRetention
Active account, player-state, collection, competitive, profile, sharing, announcement-comment, and other community recordsRetained while the account remains active or until the user deletes the account, unless a longer period is required for legal, security, integrity-review, moderation, or dispute purposes
Account-linked referral codes, installation associations, attributions, and usage sessionsRetained with the active account and removed on account deletion; turning participation off stops future collection and counting
Protected referral eligibility identifiers created after a successful rewardUsed only until the published season end, including after participation is turned off or the referred account is deleted; automatically cleared normally within one minute while the service is healthy, with cleanup delays and recovery described in Section 5.12
Device links, app tokens, authorizations, browser sessions, and related authentication recordsRetained until expiration, revocation, replacement, or account deletion, as applicable
Local app storage and user-created local logsRetained on the computer until removed by the app or user
The Dubtrackr desktop app's data folder (%APPDATA%\Dubtrackr)Retained on the computer until you delete it. Uninstalling may leave it behind
Last confirmed Remove Ads answer on your computerTrusted for up to 3 days, replaced by each new check
Remove Ads answer saved with your account (Section 5.16)Trusted for up to 3 days, replaced by each new check; deleted with the account
Settings saved to your account and their last 20 earlier versions (Section 5.17)While the account exists; deleted with the account
Move codesUsable for 10 minutes and once; stored as a keyed hash; deleted with the account
Session records and the Super Rebirth log on your computerUp to 2,000 session records, oldest removed first; deleted from the app with your Droidex account
Automatic screenshots saved by Droidex 1.2.9 and earlierRemain in Overwolf's screenshots folder for this app until you or the current app delete them; the current app saves none
Uploaded session summaries180 days after the session date
Exact start and end times of uploaded sessions72 hours, then removed from the summary
Uploaded Super Rebirth records180 days after their end date
Session-comparison choice records, age band, its change records and region groupWhile the account exists; deleted with the account
Uploaded Fortnite Battle Royale matches (Section 5.18)180 days after the match; a shared match while it is shared, then 180 days after the match
Battle Royale match-upload choice recordsWhile the account exists; deleted with the account
Lifetime and season stats from fortnite-api.com on the DubTrackr serverUp to 10 minutes, in memory only
Replay details, weapons and the end-of-match loadout (Section 5.19)Part of the match record: as uploaded Fortnite Battle Royale matches
Saved Battle Royale ranks180 days after each was seen; deleted with a "no" to match uploads
Leaderboard choice, public card choice and wishlistUntil you change them; deleted with the account
Live squad stats, pairing reports and online status (Section 7.5)Never stored; in memory while the app is connected
Fortnite friendships, friend settings and blocksUntil you change them; deleted with the account
Answered friend requests30 days after the answer
Matched Epic friends and the time of the last importReplaced on each import; deleted with the account
Party finder listings and requests24 hours after the listing closes
Party finder reports180 days
Epic refresh token for the Epic friends import (encrypted)Until it expires, Epic refuses it, you disconnect Epic or choose Forget Epic friends access, or the import is switched off
Parent acknowledgement records (Section 7.5)While the account exists; deleted with the account
Teammates' season stats from fortnite-api.comUp to 10 minutes, in memory only
Anonymous rank chartsThe newest 400 nightly charts; they contain no personal data
Support communications, uninstall surveys, and scan reports with game screenshots sent from the app, including copies in the private Discord support channelRetained for as long as reasonably necessary to address the request, improve Droidex, protect the service, and meet legal obligations
Optional Companion diagnostic session summariesUp to 30 days after the last accepted update, then folded into identifier-free daily hardware/version cohorts
Optional diagnostic hardware profiles and credentialsRemoved after 90 days of inactivity or a confirmed diagnostic deletion request; revoked credential hashes/revisions remain for up to 90 days to prevent delayed retries
Identifier-free daily diagnostic cohort totalsUp to 90 days by cohort day
Anonymous or unlinked observation recordsRetained while useful for longitudinal spawn measurement, reader-quality analysis, and integrity checks; not selectively deletable by account
Anonymous or unlinked calibration profilesRetained while useful for calibration consensus and reader compatibility; not selectively deletable by account
Website audience hashes, aggregate first-party measurement totals, and anonymous uninstall reason/version totalsRetained while useful for audience and product-performance measurement; not linked to a Droidex account or Epic identity
Google Analytics data held by GoogleEvent-level data for 2 months and user-level data for 14 months. The 14-month period restarts with each new visit from the same browser. Aggregated reports can remain available after those periods
Google Analytics cookies in your browserExpire two years after the most recent visit, or earlier when you choose No thanks or clear site data
Active PostgreSQL account rows after confirmed deletionRemoved before the deletion response is returned
Local database or rollback backupsUp to 30 days; currently not encrypted at rest
Off-site backupsUp to 183 days under daily, weekly, and monthly rotation; encrypted at rest
Host journalsUp to 7 days
Container logsRotating files, limited to 7 files of up to 10 MB each

Backup copies that contain deleted account data remain until the applicable retention period expires. DubTrackr will not represent that every backup copy disappears immediately when the active account is deleted.

12. Account deletion and other controls

12.1 Delete Account

You can use the Delete Account control in your Droidex website account settings. Deletion requires the exact typed confirmation:

DELETE MY DROIDEX ACCOUNT

Deletion is immediate, irreversible, and cannot be cancelled by signing in again. A later Epic sign-in creates a new account and does not restore deleted account data.

Confirmed deletion removes active records for:

Deletion does not immediately remove:

12.2 Actions that do not delete the account

Signing out, unlinking a device, rotating a token, or linking another computer does not delete account progress. The confirmed Delete Account process is the destructive action.

12.3 Sharing controls

You can:

You can also:

12.4 Data export

Droidex does not currently provide a complete self-service account-data export. You can download your uploaded session summaries and Super Rebirth records from the website's account privacy page. Where applicable law gives you a right to access or receive a copy of personal data, contact dubtrackr.support@gmail.com. DubTrackr will respond as required by applicable law.

12.5 Google Analytics choice

Use Change Google Analytics choice on the Cookie Notice to allow or stop Google Analytics in the browser you are using. Choosing No thanks stops Google Analytics from loading and deletes its cookies from that browser. The choice is saved only in that browser. Clearing its site data removes the choice, so visitors from the European Economic Area, the United Kingdom, and Switzerland are asked again.

13. Your privacy rights

Depending on where you live, you may have the right to:

DubTrackr does not discriminate against users for exercising applicable privacy rights.

To submit a request, email dubtrackr.support@gmail.com. DubTrackr may ask you to authenticate through your Droidex account or provide information reasonably necessary to verify the request and protect the account. To appeal a decision, reply to the decision with the subject Privacy Appeal.

Rights generally do not apply to information that is genuinely anonymous and cannot reasonably be linked to an individual. Requests concerning Overwolf platform or advertising information must be directed to Overwolf under its privacy policy. Requests concerning Epic account information must be directed to Epic. Requests about payment and billing information for Remove Ads must go to Tebex, because DubTrackr does not hold it.

14. International processing

DubTrackr is based in the United States. Droidex service providers may process information in the United States and other countries in which they or their subprocessors operate. Those countries may have privacy laws that differ from the laws where you live.

Where applicable law requires a recognized transfer safeguard, DubTrackr will use an available lawful transfer mechanism or require the relevant service provider to do so.

15. Security

DubTrackr uses administrative, technical, and organizational measures intended to protect Droidex information. Measures include local screen processing, data minimization, authenticated account and device links, access controls, encrypted network transport, restricted diagnostics, short-lived session credentials where appropriate, request-body log exclusions, and encrypted off-site backups.

A known limitation is that local database and rollback backups may remain unencrypted at rest for up to 30 days. No storage or transmission method is completely secure, and DubTrackr cannot guarantee absolute security.

If a breach affects information for which notice is legally required, DubTrackr will provide notice to affected users and authorities as required by applicable law.

16. Children and eligibility

You must be at least 13 years old to link a Droidex account or use account or community features, as the Droidex Terms say. Droidex does not knowingly collect personal information from children under 13.

The app may ask for your birthday as described in Section 5.14. If you tell Droidex you are under 13, the app does not link to a Droidex account and uploads nothing for rankings; an account already linked is deleted with its server records. Players aged 13 to 17 get more protective defaults: session uploads only if they choose them (and never for players aged 13 to 15 in the European Economic Area or Switzerland), and a private profile page and no public leaderboard entry until they turn those on themselves. They can find and add adults as Fortnite friends only after ticking a parent acknowledgement, which isn't offered where a law rules it out (Section 7.5).

If DubTrackr learns that it collected account-linked personal information from a child under 13, or under the applicable age of digital consent in the child’s jurisdiction, DubTrackr will take reasonable steps to delete that information. A parent or guardian who believes a child provided information should contact dubtrackr.support@gmail.com.

Overwolf and Epic apply their own age, account, and parental-consent rules to their services. Overwolf's own terms may require a higher minimum age to use the Overwolf platform.

17. Automated processing

Droidex uses OCR, template matching, confidence scoring, event matching, and deduplication to read game information and operate app features. Rank bands compare your gameplay with other players' (Section 5.13); this comparison of gameplay is profiling in data-protection terms. Bands are worked out on your computer, only you see them, and they change nothing in the game or in your account. Automated checks can stop a session summary from counting toward the charts. Droidex does not use automated decision-making that produces legal effects or similarly significant real-world effects about a person.

18. Changes to this Policy

DubTrackr may update this Policy when Droidex features, data practices, service providers, or legal requirements change. The updated version will show a new effective or last-updated date.

For a material change, DubTrackr will provide additional notice in the app, on the website, or through another appropriate channel where required. If applicable law requires consent for a new use, DubTrackr will request it before beginning that use.

19. Contact

For privacy questions, requests, or concerns:

DubTrackr
Washington, United States
Email: dubtrackr.support@gmail.com