Terms and Services

1. The service

foxholewwc.com is a community tool for Foxhole. It provides storm and upcoming-condition information, weather-station and claim management, maps, reporting, and contribution tracking for the Warden community with integrations with the Warden Weather Channel (henceforth: "WWC"). It is provided "as is", and is subject to the protections that applicable law gives you.

Profile defaults for map style and legend visibility apply to this browser, rather than your Discord account. They are not synchronized across devices. You can change or reset them in your profile; clearing site data or using private browsing can remove them.

2. Eligibility and accounts

You must be at least 13, meet any higher minimum age applicable in your jurisdiction or required by Discord, and have a Discord account. Protected features require membership and the appropriate verified roles in a configured verification server. You are responsible for protecting your Discord account and for your use of foxholewwc.com.

3. Acceptable use

• Do not attack, overload, disrupt, or bypass the service's access controls or request limits.
• Do not submit unlawful, harassing, hateful, or sexual content.
• Do not impersonate other players, groups, the operator or the WWC administrator team.
• Do not scrape, resell, republish, or disclose restricted Warden data without permission.
• Do not exploit bugs to access unauthorized data. Report suspected vulnerabilities privately to dr.kvass on Discord.

4. Community content and permissions

WWC administrators configure access and staff roles. Authorized members can view or manage submitted game content according to their permissions. Submission of a storm report sends it to the configured WWC Discord reporting channel, where members with channel access can see it.

5. Your content

You retain any rights you hold in the content you submit. You grant WWC a non-exclusive license to host, process, transmit, and display that content as needed to operate the service, including delivery of reports to the WWC Discord server, and any discord server subscribed to its announcement channel. Submit only content you have the right to share.

6. Discord integration

foxholewwc.com uses Discord for sign-in, verification, and configured bot reports and notifications. Discord's own terms and policies also apply. You can revoke authorization in Discord settings and log out of WWC at any time. Signing in again requires authorization. Revocation alone does not clear an existing foxholewwc.com browser session or delete earlier records.

Website storm-report messages identify the reporter by nickname on the registered discord server only, without including their Discord ID. Internal records still retain the ID, as described in the Privacy Policy.

7. Intellectual property

Foxhole and its related game assets belong to Siege Camp and their respective rights holders. foxholewwc.com is a community project and is not affiliated with or endorsed by Siege Camp. Original code, branding, and contributed assets remain subject to their owners' rights and applicable licenses. Credits for the map mods used by foxholewwc.com are available in the profile dropdown.

8. Suspension and termination

The operator may restrict or end access for violations of these Terms or to protect the service. You may stop using foxholewwc.com at any time and contact dr.kvass on Discord to request deletion of your personal data. Ending access does not automatically delete logs, backups, or Discord messages.

9. Availability and warranties

To the extent permitted by law, foxholewwc.com is provided without warranties. We do not guarantee uninterrupted operation, accurate or complete game data, or timely delivery of notifications. The service is under development and may contain bugs.

10. Liability

To the extent permitted by applicable law, the operator and contributors are not liable for indirect, incidental, or consequential losses arising from use of the service, including lost playtime or in-game outcomes. Nothing in these Terms excludes liability or limits rights that cannot lawfully be excluded or limited.

11. Changes to these Terms

These Terms may be updated as the service changes. The date above identifies the latest revision. Material changes will be announced through the WWC Discord server. Review updated Terms before continuing to use foxholewwc.com; continued use after they take effect signifies acceptance where permitted by law.

12. Contact

For questions about these Terms, contact dr.kvass on Discord.

1. Information we collect

• Discord account and verification data. Your Discord user ID, username or display name, and server nickname. Discord OAuth also supplies profile information and your server-membership list so foxholewwc.com can check membership and relevant roles in the verification servers. foxholewwc.com keeps the selected server's name and ID and your resulting access level and staff roles in the login session. It does not retain your avatar or full server-membership list.
• Member and contribution records. foxholewwc.com caches member IDs and nicknames for account selection and attribution. When applicable, records link your account to weather-station ownership, claims, storm analysis and other contributions, together with contribution points and their calculation time.
• Game information you submit. Storm reports include the hex name, FHS coordinates, a map-position link, whether the storm has started or concluded, a map preview, and any optional screenshot. Staff edits can include storm names, classifications, geometry, times, weather stations, claims, analyst assignments, and upcoming conditions. Normal two-hex upcoming updates also retain the selected pair, update time and result in history, even after a newer update replaces them on the website. FHS coordinates describe the game map, not your real-world location.
• Activity and operational logs. IP addresses (IPv4 or IPv6), timestamps, login/logout results, verification server, denied access attempts, and security or error events. Request logs can include method, path or URL, query parameters, browser/user-agent, response status, and processing time. Recorded commands and staff actions include the source, action, category, supplied options, affected records, and before/after values for database edits. Report delivery records include the destination Discord server/channel, message ID, and delivery result. Interaction identifiers link related events.
• API credentials and usage, if applicable. For issued API tokens, foxholewwc.com stores a token hash, token name, permission level, creator's Discord ID, and creation time. API usage logs can include the client IP, authenticated token name, request parameters, and submitted JSON data or upload size/type. Plaintext tokens are not stored in the credential database, and credentials are excluded from audit logs.
• Browser storage. A signed HTTP cookie contains the account and verification information needed to keep you logged in. Temporary OAuth state protects the login flow, and a return-location HTTP cookie preserves map links across login. Local browser storage remembers your map style and gradient and colours/edges legend settings. These preferences are not sent to the server as account settings or used for tracking. Admin view-as selections are kept in the session and recorded in the audit log.

foxholewwc.com does not ask for your Discord password or email address. OAuth access tokens are used during verification and revocation is requested when verification ends; they are not saved for later use by the website.

2. How we use information

foxholewwc.com uses this information to authenticate users, verify Warden-only access, apply staff permissions, display account and contribution information, and provide the map, weather-station and storm-reporting features. It also supports configured Discord reports and notifications, investigates abuse, and helps diagnose failures and maintain the service.

Discord verification and its essential session information are required to access the protected website. Routine map browsing, asset loading and display toggles do not create activity entries in the website's audit log. Login/logout, submitted reports, staff database edits, Admin view changes, and access/security events can create entries. Separate server request logs may also record visits before login.

3. Storage and sharing

Records are kept on the server used to host foxholewwc.com, and the operator can access the underlying databases, logs and backups. Authorized foxholewwc.com administrators can view audit records containing nicknames and activity details. IP addresses and Discord user IDs in the website's log viewer are replaced with hashed identifiers before being sent to the browser, thus ensuring your discord ID or IP is not visible to anyone but the operator. Other details, mainly the users discord nickname remain readable, so these records are not fully anonymous. This protection applies to the log viewer; your own login session and authorized game features still use the identifiers they require.

foxholewwc.com does not sell your data or make its internal logs public. Submitted game content and contribution details are shared with foxholewwc.com members according to their access permissions. Discord receives reports and notifications sent through the bot, and users with access to the destination channels can see them. A website storm-report message identifies the reporter by nickname only; the bot does not include the reporter's Discord ID in that message. The ID is still retained in internal records for accountability.

Hosting and Discord services process information needed to provide their services. Discord's handling of authorization data, messages and attachments is also covered by its Privacy Policy. Information may be disclosed where required by law.

4. Screenshots and map previews

Storm-report images are sent to the foxholewwc.com server, checked, and converted to new JPEG images before delivery to Discord. Original file names and embedded metadata are not forwarded. The visible contents of the images remain visible, including any names, chat text or other personal information shown in the screenshot.

Image contents are not copied into the audit log. The delivered images and report are stored as a Discord message and attachments. foxholewwc.com does not perform OCR on these images. Only submit screenshots you are comfortable sharing with the report's recipients.

5. How long records are kept

Active database logs are normally cleared after each Foxhole war, often roughly once a month, when the operator resets the database. The interval depends on the war's duration and when the reset is performed.

A database backup is made before a reset. Backups and separate server logs can therefore retain earlier records; a war reset does not erase every copy or guarantee deletion within one month. API credentials and verification-server configuration are stored separately and survive these resets. Discord messages and attachments also remain until removed on Discord. There is no automatic cleanup that deletes all of these records at the end of a war.

Login expires 24 hours after authentication; activity does not extend it. Logging out clears the login cookie. The temporary return-location cookie is cleared when its map link is used and otherwise follows your browser's session-cookie retention settings. Browser defaults have no set expiry and survive logout. Reset defaults restores the initial settings; clearing site data removes them. Private browsing or browser cleanup can also remove them. Contact the operator about records still held about you or to request deletion, including records in backups or Discord reports.

6. Security and breach notices

foxholewwc.com uses access checks, signed session cookies, request limits, and image validation to protect the service. Use the HTTPS website to protect data in transit. No system is completely secure; protect your Discord account with a strong, unique password and two-factor authentication.

The operator will communicate suspected or confirmed personal-data breaches affecting this website through the Discord servers used for verification. Affected individuals and the relevant supervisory authority will also be notified where required by law.

7. Your choices and data-protection rights

You can log out of the website, clear its cookies and local browser storage, and revoke the application's authorization in Discord settings. Revoking Discord authorization does not by itself clear an existing foxholewwc.com browser session or delete previously stored records. Log out as well to end that browser's session.

Where the General Data Protection Regulation (GDPR) applies, you may contact dr.kvass on Discord to request access to and a copy of your personal data, correction of inaccurate information, or deletion. You may also request restriction of processing, object to processing, or request data portability where those rights apply. Identity confirmation may be needed, and legal exceptions can affect whether particular data must be deleted.

You also have the right to complain to your data-protection supervisory authority. Agreeing to these Terms does not waive your data-protection rights. If you authorize with Discord again after deletion, new authentication and activity records will be created. The European Data Protection Board explains these rights.

8. Children

This service is not intended for anyone under 13 or below the higher minimum age applicable in their jurisdiction or required to use Discord. Do not use the service if you do not meet those requirements. Contact the operator if you believe data from a child below the applicable age has been collected.

9. Changes to this policy

This policy may be updated as the service changes. The date above identifies the latest revision. Material changes will be announced through the Discord servers used for verification.

10. Contact

For privacy requests, questions or concerns, contact dr.kvass on Discord.