Privacy Policy

1. Introduction

gunsmoke.app ("we", "our", or "the site") respects your privacy. This policy explains what data we collect, how we use it, and your rights. We do not run ads and we do not sell or share your personal data with third parties for marketing.

2. Data we collect

We collect only what is needed to run the service:

• Updated Account data: Username, password (stored in hashed form only), optional nickname (display name shown to other members), and for username/password accounts one optional recovery security question with a case-sensitive answer (answer stored hashed). If you sign in or link your account with Discord, we receive your Discord id and handle only; your Discord display name is used as your default nickname. We do not collect or store email addresses.
  April 2026 Optional email; Discord email and avatar → No email; optional hashed security Q&A; Discord id and handle only
• Guild data: Guild name, hashed guild password, recruitment text, server name, guild level, platoon id, member count, language, Discord invite, and whether the guild is public or recruiting. Your role in the guild (leader, officer, or member) is stored.
• Game data: Commander names, season scores, ranks, and guild leaderboard data you or your guild upload. Your profile may include in-game dolls (power, fortification, imprints) and Growth Loadouts remolding core inventory.
• New Builds (kits): Local kits are stored only in this browser (IndexedDB), including for guests. After you log in or register in the same browser, we move guest kits into a store keyed to your account on this device — we do not auto-upload them. Private kits are stored on our servers and are visible only to you. Public kits are stored on our servers and shown in the gallery with your display name.
• New Puppet leaderboard: If you submit a run, we store Challenge Points, damage stats, weakness type, a snapshot of the kits you chose (published with the run after it is accepted), and your display name. Screenshots are stored privately for admin review, then deleted when the run is accepted or rejected. Anyone can view accepted runs.
• New Auto Setups: If you submit a setup, we store the configuration string, a short description, doll, fortification, and your display name. Listings are public.
• Support: If you create a ticket, we store the title, description, priority, classification, and any comments (including admin replies).
• Codes: If you claim a game code, we record that you claimed it.
• Technical: We record when you were last online (on login). We do not store your IP address long-term; our rate limiting uses it only in memory to protect the API.

3. How we collect it

• Direct: When you register, log in, update your profile, create or join a guild, submit a ticket, use Growth Loadouts (calculator and saved loadouts), save Builds (Private/Public), submit a Puppet run or Auto Setup, or claim a code. If you choose "Login with Discord" or "Link Discord", we receive data from Discord as part of that process.
• On your device: Local Builds kits use IndexedDB in your browser. Optional “Read screenshot” for Puppet runs runs OCR in your browser; image pixels are not uploaded for that feature.
• Cookies: We use one cookie — a session cookie — to keep you logged in and to secure your session. It is strictly necessary for the service. We do not use advertising or tracking cookies.

4. How we use your data

We use your data only to provide and improve the site: to authenticate you, show leaderboards and guild data, manage your profile and units, handle tickets and codes, run Growth Loadouts features, store Private/Public Builds, review Puppet submissions, and list Auto Setups. We do not use your data for advertising. We do not sell or share your personal data with third parties. If you use Discord to log in or link your account, Discord's own terms and privacy policy apply to their processing; we only receive what Discord sends us to create or link your account.

5. Legal basis (EU)

We process your data where necessary to perform our contract with you (providing the service) and, where applicable, with your consent (e.g. optional Discord link). We do not rely on legitimate interest for marketing or sharing.

6. Data sharing

We do not sell or share your personal data. The only exception is when you use Discord to log in or link your account: Discord processes your data according to their policy (see Discord Privacy Policy). We load styles and scripts from content delivery networks (CDNs) for the site; those providers do not receive personal data from us.

7. Cookies

We use a single cookie: a session cookie. It keeps you logged in and helps secure your session. It is strictly necessary for the site. We do not use analytics or advertising cookies. You can disable cookies in your browser, but the site will not be able to keep you logged in.

8. Data retention

We keep your data for as long as your account exists. If you ask us to delete your account (there is no in-app delete control; email us), we will remove or anonymize personal data as required by law: Private and Public Builds, pending or rejected Puppet runs, Puppet screenshots, and Auto Setups are deleted; accepted Puppet runs stay on the board with the account name removed. Local kits remain in your browser until you clear site data. Some data (e.g. for legal or operational reasons) may be retained for a short period after deletion.

9. Security

We hash passwords and sign the session cookie. We use HTTPS in production. We do not share your data with third parties except as stated above.

10. Your rights

You can access and correct your profile data in the app. You can ask us to delete your account or to provide a copy of your data. To do so, contact us (see below). If you are in the European Economic Area, you have the right to lodge a complaint with a supervisory authority.

11. Children

The site is not directed at children under 13. We do not knowingly collect personal data from children. If you believe a child has provided us data, please contact us and we will delete it.

12. Changes

We may update this policy. We will post the new version here and, if the changes are important, we may notify you on the site. The "Last updated" date at the top will change when we revise the policy.