MwoLab 개인정보처리방침

Privacy Policy

This policy applies to the MwoLab website and its public fitting features. MwoLab does not operate a separate application server or password account system. Privacy questions and deletion requests may be sent to killkimno@gmail.com.

Information processed

• Google sign-in: Firebase Authentication may associate your Google account identifier, display name, email address, profile photo URL, and provider information with an authentication account. MwoLab does not use the Google display name as a nickname or public fitting author name.
• Optional nickname: If a signed-in user chooses one, MwoLab stores the unique nickname, its lowercase uniqueness key, the initial-prompt state, and creation/update times in the publicly readable users/{uid} profile. A nicknames/{key} reservation stores the normalized key's owner UID and creation time. Changing a nickname reserves the new key and releases the previous key. When no nickname is set, Pilot is only a UI fallback and is not stored as the nickname.
• Public fittings: The submitted title, MWO loadout code, mech identifier, like count, creation time, schema version, and Firebase user identifier (UID) are stored in a publicly readable document. The UID is used for ownership checks, the user's upload list, and nickname lookup. Nicknames are not copied into fitting documents; the UI displays the selected nickname or Pilot as the author and never uses the Google name, email address, or profile photo for this purpose.
• Operational records: Firestore separately stores per-user like state; the current upload count, last changed fitting identifier, change type, and time used to enforce the 100-public-fitting account limit; and the fitting identifier, owner UID, mech identifier, and request time needed to clean up likes after deletion. Security rules block general users from listing these records, and only the account owner may read its upload count.
• Local browser data: Named local fittings and UI preferences remain in browser storage unless you explicitly publish a fitting.
• Analytics: MwoLab uses Cloudflare Web Analytics to understand site usage and does not set its own analytics cookies.

Purposes, services, and retention

Information is used for authentication, unique optional nicknames, public fitting publication and viewing, private ownership checks, one like per account, abuse prevention, troubleshooting, and aggregate usage measurement. Authentication data is not used to reveal the publisher's real identity. MwoLab uses GitHub Pages, Google Firebase Authentication and Cloud Firestore, and Cloudflare Web Analytics. Local data remains until cleared from the browser; Firebase-related data is retained while needed to operate the service. When an owner deletes a public fitting, the public document is removed immediately and a private cleanup request is created; an administrative maintenance pass then removes the fitting's like records and the request. Contact the address above to request account deletion. Ownership may need to be verified before deletion.

Google sign-in is required to set a nickname, publish or delete fittings, or manage likes. Nickname setup is optional and can be skipped. Public fittings can be viewed and applied without signing in. The UI displays the selected nickname or Pilot as the author, but never the publisher's Google name, email address, or profile photo. MwoLab does not sell personal information or provide personalized advertising. This policy and its effective date will be updated if these practices materially change.