Privacy Policy

Updated: 2026-10-14 · Bản tiếng Việt

DF Mate ("the app") is a fan-made desktop app (Electron), not an official product of the game's publisher. This page covers data collected by the Hub — the sync/community server at hub.dfmate.com — when you use community features (submitting builds, liking, commenting, logging in, sending feedback). What's stored only on your own machine is covered separately in section 2.

1. Data the Hub stores

Data	When	Stored as
Install id	When you like/submit a build/report/set a nickname/send feedback	Only the sha256 hash of a random token the app generates on your machine — the raw token is never stored, and it's never tied to your real name, email, or device
Nickname	When you choose to set one	A text string you pick, shown publicly on the leaderboard
Display name + avatar from Discord/Google	When you choose to log in to comment	Only the public display name + avatar URL the provider returns. Your email, password, and the provider's access token are never stored — the access token is discarded immediately after the one-time profile fetch; only the Hub's own session token is created, and that's stored as a hash
Builds you submit	When you submit to the community hub — requires login	The build code, weapon/mode, a required description/optional source link — public immediately; the description is auto-filtered for some inappropriate words. Tied to your logged-in account (previously tied only anonymously to your device).
Loadout screenshot (optional, attached when submitting a build)	When you choose to attach an image while submitting a build	The image is re-processed on the server (resized, re-encoded, all original metadata including EXIF/location stripped before storage) — the file you uploaded is not kept as-is. The image is visible to admins only until approved; once approved it's public alongside the build. An admin may reject it (hard-deleting the file) if it's inappropriate.
Comments	When you comment on a build (requires login)	Plain-text content, public, tied to your account's display name
Comments + images on map markers, and likes/dislikes	When you comment, attach an image, or like/dislike a comment on a Chiến Dịch map marker (requires login)	Same mechanism as build comments above — text is public immediately, an attached image (if any) is re-processed and queued, visible to admins only until approved. Likes/dislikes are counted per account only, never shown to others as "you liked this".
Likes / reports	When you like or report something	Only a count per hashed install id — anonymous
Anonymous match report (opt-in)	Only when you turn on "Share anonymous match data" in Settings — off by default	Map, your own operator, win/loss, score, per-round outcome (attack/defense side, win/loss, whether the bomb was planted). No player names, no teammates/opponents, no kills/deaths, no play time. Tied to the same hashed install id as likes/reports above (anonymous) — kept for up to 24 months then auto-deleted, see section 5 to delete it sooner.
Feedback / bug reports	When you send one via the Send Feedback / Report a Bug feature	What you wrote, kind (bug/feedback), contact info only if you choose to give it, app version, locale, platform (Windows/macOS/...), current screen — visible only to the project owner, never shown publicly, never includes an IP address
Crash reports	Automatically, when the app hits an error — on by default, turn off anytime with "Send error reports automatically" in Settings	The error message and a technical stack trace, app version, platform, which part of the app crashed, and the last ~20 lines of this app's own local activity log at the moment of the crash (e.g. "overlay shown", "settings opened" — no player names, no match content). File paths under your home folder and any token-like text are stripped on your device before sending, and home-folder paths are stripped again on the server. Visible only to the project owner, never shown publicly, never includes an IP address.
Vision check ("recognition check")	Only when you press the "Send result to DF Mate" button in Settings — off by default, nothing is sent until you click it	What the app read off one captured frame (screen/mode/map/score/operator names), your app version and platform, and — only if you leave the "Include a screenshot" checkbox checked — a screenshot of that one frame, which may show other players' in-game names or chat. Used only to fix recognition bugs, kept for up to 30 days, visible only to the project owner, never shown publicly. You'll get a short id (e.g. "7K3F") in the app to quote if you want it deleted sooner — see section 5.
Device check-in	Automatically, on launch and roughly every 24 hours while running — on by default, turn off anytime with "Send device info automatically" in Settings	App version, platform (Windows/macOS/...), OS version, and the latest screen-capture permission result (granted/denied/error/not yet requested). No images, no match content, no player names. Each machine keeps exactly one row (latest state, not a history) — tied to the same hashed install id as likes/reports above (anonymous), plus your logged-in account if you're logged in at the time. Visible only to the project owner, never shown publicly, never includes an IP address.

2. Data that stays only on your machine, the Hub never sees it

Your personal build library, app settings, local usage history — except the anonymous match report when you turn sharing on (see section 1); your detailed match history itself (full context, teammates, strategy) is never sent to the Hub — only the minimal fields in section 1 are, and only once you turn this on
The raw install token (only its hash is ever sent to the Hub)
Discord/Google access tokens (used only for the one-time login exchange, never kept)

3. IP addresses

The Hub uses your IP to rate-limit requests (anti-spam/abuse) — that counting lives only in the server process's memory, resets on a server restart, and is never written to the database. The Hub does not log IPs per request. This site is served through Cloudflare (section 6) — Cloudflare sees your IP the same way any CDN does.

Separately, each time the app checks for updates, the update server logs your IP address, app version, and OS version — kept for at most 14 days then deleted automatically, used only to tell whether updates are working, never for anything else.

4. Cookies

The Hub does not use cookies. Login uses a session token sent over an HTTP header, stored by the desktop app itself — no browser, no cookie involved.

5. Retention and deletion

Deleting your login account (Discord/Google): available any time in the app — hard-deletes the account and every session; comments you wrote are kept but anonymised (shown as "Deleted account"), not deleted outright. Builds (and images, if any) you submitted are kept as-is — they're public content already shared with the community, not your private data, so they aren't deleted/anonymised when your account is.
Builds/likes/reports tied to your install id (from before the login requirement took effect): there's currently no self-serve deletion in the app; contact [email protected] to request it.
An image an admin rejects, or a build that's taken down: the image file is deleted from the server immediately and cannot be recovered.
Anonymous match reports: kept for up to 24 months from when the server received them, then auto-deleted by a periodic sweep. Turning off "Share anonymous match data" in Settings stops sending new ones immediately, but doesn't delete ones already sent — to delete sooner than 24 months, contact us via the Support page with the contents of your install-token.json file (in the app's data folder on your machine) so the project owner can identify the right install; deletion removes every report tied to that install and cannot be undone.
Feedback / bug reports: kept for the project owner to act on, for as long as the reported problem needs it; to have yours deleted at any time, email [email protected].
Crash reports: individual error samples are kept for up to 90 days then auto-deleted by a periodic sweep; the aggregate count/first- seen/last-seen per distinct error is kept longer so recurring bugs stay visible to the project owner even after the detailed samples age out. Turning off "Send error reports automatically" in Settings stops sending new ones immediately.
Vision checks: kept for up to 30 days then auto-deleted by a periodic sweep. To ask for one deleted sooner, contact [email protected] with the short id shown in the app after you sent it (e.g. "7K3F").
Device check-in: kept for up to 90 days from the most recent ping, then auto-deleted by a periodic sweep (a new ping within that window resets the clock); the total number of rows across every install is also capped at 50,000 — past that cap, the oldest row is deleted first regardless of its own 90-day age. Turning off "Send device info automatically" in Settings stops sending new ones immediately.

6. Third parties

Discord, Google: contacted only when you choose to log in with that provider — see their own privacy policies for how they handle login data.
Overwolf: if you installed DF Mate from the Overwolf app store, Overwolf runs and updates it, and Overwolf's own privacy policy also applies.
Cloudflare: sits in front of hub.dfmate.com as a CDN/DDoS shield — sees connection traffic the way any CDN does.
Advertising (Overwolf version only): the version of DF Mate distributed through Overwolf shows ads served by Overwolf, in the app's main window only — never in game (no ads in the overlay or the mini HUD). To show and measure these ads, Overwolf and its ad partners may store or access information on your computer (such as cookies) and process data such as your IP address; Overwolf's own privacy policy applies to this. Where the law requires consent, you can change your choices anytime in Settings → "Privacy settings (ads)". The personal (non-Overwolf) version of DF Mate shows no ads.
No other advertising and no other analytics/tracking tools on these pages or in the app.

7. Children

The app/Hub is not directed at children and has no age-verification mechanism. If you are under 16, use the community features (sign-in, posting, comments) only with a parent's or guardian's permission.

8. Changes to this policy

This policy may be updated; the most recent update date is always shown at the top.

9. Contact

Privacy questions: [email protected].