Privacy Policy
Version 2026-10-29.2 · Effective date 2026-10-28
BanPickMod (the “Operator”) publishes this Privacy Policy to explain how personal data is handled and how privacy requests are addressed.
1. Purposes, data and retention
| Basis and purpose | Data | Retention |
|---|---|---|
| Contract performance: login, account security and saved settings | Battle.net account identifier and display name, age-confirmation time, consent history | Until account deletion |
| Optional C1 consent: replay upload, analysis and playback | Original SC2Replay file; hash, size, upload time and client version; map, duration, race, result, draft, unit movement/production, economy and battle records. Analysis records keep, instead of participants' Battle.net profile handles, an irreversible hash used only to recognise one game uploaded by both players, and never the handle itself (the original file does contain them) | Until the user deletes the replay or account. Automatic maximum retention: 원본 파일은 분석이 끝나면 삭제하고(평가가 끝나지 않으면 최장 7일), 분석 실패·미지원 버전은 30일 |
| Optional C2 consent: public viewing and anonymous statistics | Analysis and timeline with identifiers removed; aggregate values by period and matchup | Until C2 withdrawal, replay deletion, accepted removal request or account deletion |
| Optional C3 consent: future AI-training candidate | Derived gameplay records excluding names, profile handles and chat. No training pipeline is currently operating | Until C3 withdrawal or deletion of source/candidate data. Withdrawal does not retroactively alter completed model training |
| Feedback, bug reports and public-replay reports | Title, message, page URL, browser information, attached images, account ID when signed in, and an IP HMAC for abuse prevention | Until deletion is requested or operational retention ends. Target retention: 처리 종료 후 1년 |
An original replay may contain participant names, profile IDs and chat. The original is currently kept privately for re-analysis, so those fields are not selectively removed from the original immediately after analysis. Public responses never include names, profile handles, chat or uploader information.
Files that are not BPM games or are corrupt are deleted after analysis. An unsupported new version may be retained so it can be analysed later.
2. Optional consent and refusal
- C1, C2 and C3 are independent and all are off by default.
- Refusing C1 does not block the information site, but launcher upload and personal analysis cannot be provided.
- Refusing C2 or C3 does not prevent personal analysis.
- Account identifiers strictly needed for login, security and saved settings are processed to perform the service contract and are not presented as optional consent.
3. Public disclosure and third-party provision
The Operator does not provide personal data to third parties for advertising or sale. When C2 is enabled, the following is made public on the Internet.
- Players are shown only as Player 1/2; names, profile handles, chat and uploader information are excluded.
- The original replay file is not published or downloadable.
- An opponent's anonymised gameplay may be replayed. If an opponent or data subject reports it, privacy/opponent reports are taken down first and then reviewed.
4. Processors and overseas transfers
Cloud hosting necessary to provide the service is performed as processing/storage required to perform the service contract. You may object to an overseas transfer through the contact below, but login and replay storage cannot then be provided.
| Processor and contact | Country | Data and method | Purpose and period |
|---|---|---|---|
| Railway Corporation [email protected] | 네덜란드 (EU West, 암스테르담) | Account, consent and analysis database; server logs and session data / transferred over TLS while using the service | Web, API, Postgres and worker hosting / until account deletion, purpose completion or end of the processing contract |
| Cloudflare, Inc. [email protected] | 아시아·태평양 (APAC) | Original replays, timelines and feedback attachments / transferred over TLS while using the service | Private R2 object storage / until deletion, purpose completion or end of the processing contract |
5. Children under 14
This service does not allow registration or use by children under 14 and does not collect dates of birth. Users self-confirm that they are at least 14 before first sign-in. If we learn that a child under 14 supplied data without a legal representative's consent, we will delete the account and data without undue delay.
6. Your rights and how to exercise them
- Account settings provide consent withdrawal, JSON export, replay deletion, device revocation and account deletion.
- Requests for access, correction, deletion, restriction or objection to overseas transfer may be sent to [email protected].
- Turning off C2 immediately removes the replay from public pages, shared links and statistics.
- Turning off C3 immediately removes unused training candidates. Model weights from completed training cannot be separated back into a specific individual's record.
7. Deletion procedure and method
When retention expires or the purpose is complete, data is deleted without undue delay. Electronic files and database rows are removed through application and storage deletion so they are no longer accessible. If backups are used, deleted data is isolated until the backup cycle expires and is not returned to service processing.
We do not claim direct physical-sector overwriting; deletion follows the secure deletion procedures of the managed cloud services in use.
8. Security measures
- HTTPS/TLS in production and HttpOnly, Secure, SameSite session cookies
- Launcher tokens and reporter IPs stored as SHA-256/HMAC values rather than raw values
- Original replays and attachments stored as private objects accessible only through owner, worker or operator APIs
- Public responses are rebuilt from an allow-list and profile handles are removed
- Operator access requires a named token plus an authenticator one-time code (two-factor) and is logged
- Same-origin checks on signed-in writes, per-API authentication/rate limits and isolated replay parsing
9. Cookies and automatic collection
We use a short-lived cookie to protect Battle.net OAuth and an essential session cookie to keep you signed in. We do not use advertising or behavioural tracking cookies. Language is selected by the /ko or /en URL path and no language cookie is stored. Refusing cookies may prevent login and account features from working.
10. Privacy contact and remedies
Operator and privacy contact
BanPickMod
[email protected]
Make a request to see, correct, delete or restrict your data, or to object to transfer abroad →
11. Changes to this policy
Material changes to data, purposes or processors will be announced on the site before taking effect. A change that requires consent will be presented as a new consent version.