Privacy Policy

Poop Fighters 3D — rabidspider.com/poopwars · last updated 2026-10-16

The short version. No accounts, no cookies, no analytics, no advertising, nothing sold or shared with anyone. Two things ever leave your device: the ordinary data of playing online (§3), and a bug report — which is voluntary, and only sent if you open the bug screen and press SEND (§4).

1. Who runs this

The game is served from rabidspider.com by Rabid Spider. For anything in this policy — access, deletion, or a question — write to joserr@rabidspider.com.

The source code is public at github.com/jaruizramon/PoopWars, and its issue tracker is the place for bugs. It is not the place for a privacy request: issues are public, and the report ID you would have to quote is exactly what you are asking us to remove.

2. What your browser keeps (and how to remove it)

The game stores a few values in your browser's localStorage. They are not cookies, they are never sent to anyone in the background, and no site other than this one can read them. Clearing "site data" in your browser removes all of them; the game still works without them.

3. Playing online

A match is played through the lobby server (the "governor"). While you are in a lobby or a match, it holds your display name, that random id and the match messages (inputs, state hashes, lobby actions) in memory for the session. It keeps no accounts and no database, and its match logs record player ids and match ids — not IP addresses.

Two ordinary facts of any network connection, stated plainly because they are easy to overlook: the server (and the web server that fronts this site) sees the IP address your connection comes from, and standard access logs — address, requested URL, time — are kept as part of running the site and rotated away automatically.

Direct connections between players. In an online match the game tries to send frames straight between the players instead of through the server. To find that path it asks a public STUN service (Google's stun.l.google.com:19302) what your public address looks like from the outside; when a direct path exists, the other players' browsers can see your IP address, which is inherent to any direct connection. When it does not exist, frames are relayed through the server instead. You can force the server-relayed path at any time from your browser's console: window.__iceServers = [].

Voice chat is off until you turn it on. When you enable it, your browser asks for microphone access — that prompt is the only consent step, and declining it leaves voice off. With voice on, your microphone audio is sent directly to the other players' browsers in your queue, room or match: it is never sent to, mixed by or stored on the server, and it is not part of a bug report (§4) or of any log. The server only carries the connection setup messages (the same STUN-assisted path described above, so the same fact applies: players you connect to directly can see your IP address). Turning voice off, muting, or leaving the queue/room/match stops the microphone.

4. Bug reports — voluntary, and only when you press SEND

Reporting a bug is entirely optional and entirely manual. Nothing is captured, and nothing is transmitted, unless you open the bug screen yourself and press SEND — you can play the whole game, online included, and never send one. The screen shows exactly what would be sent before you send it.

A sent report is stored on the server as one file per report, containing:

• the session log from §2 (up to 2500 lines: positions, phases, frame timings, console output),
• the game and network state (mode, round, world seed, whether you were host, frame and socket counters),
• whatever you typed in "what happened",
• your display name, and what your browser reports about itself: user agent, language, screen and viewport size, pixel ratio, touch support,
• one screenshot of the game's own view — the 3D canvas, re-rendered by the game when the screen opens and again if you press GAME VIEW. That is the only image a report can carry: there is no file picker, no clipboard paste and no screen capture, so you cannot upload an image of your own (a file, your desktop, or another tab), and nothing else on your device can be attached,
• and the IP address the report was sent from.

That is the whole list; it is what a report needs to be reproducible. Reports are readable only by the operator, through a password-protected panel. They are kept until they are deleted there — there is no automatic expiry — so if you want yours removed, keep the report ID the screen showed you when you sent it and ask for its deletion by email at joserr@rabidspider.com, quoting that ID.

5. What is not done

No accounts. No cookies. No analytics, telemetry or crash-reporting service. No advertising. No third-party scripts: the 3D engine, the music player and every asset are served from this site. No data is sold, rented or shared with anyone. The only request the game can make to an outside service is the STUN lookup in §3. The RabidSpider logo is an ordinary link, and following it is a normal visit to that site under its own policy.

6. Children

The game asks for nothing beyond an optional display name. If you are a minor, please get a parent's permission before sending a bug report: it contains your logs and display name and, if one is attached, a picture of the game's own view — never anything else from your device, since no other image can be attached.

7. Changes to this policy

If this policy changes, the date at the top changes with it and the new text appears here. Because the game stores so little, a change would normally be a clarification rather than a new use of data.