guest@pissclient:~/legal$ cat privacy.txt

privacy policy

What we collect, why, where it lives and how long we keep it.

version 1 · effective · support@pissware.lol

1. who we are

PissClient runs the client and pissware.lol. For anything about your data, write to support@pissware.lol.

Our servers are rented from Oracle Cloud, in its Ashburn, Virginia (United States) region. Everything below is stored there unless it says otherwise.

2. your account

what
Your username; your email address if you give one (without one we store a placeholder, <username>@ghostclient.online, that is not a real inbox); your password, stored only as an Argon2 hash and never in plain text; who invited you, the invite code you used, your current invite code and how many invites you have left; your role and status; when you registered and last signed in; and the version of the terms you agreed to and when.
why
To run your account, sign you in, keep invites working and show you who you invited.
kept
For as long as the account exists.

3. sign-ins and your machine

what
Each time you sign in, on the site or in the client: your IP address, your browser's user agent, when the session started, was last used and expires. For the client, also its version and your hardware ID (HWID).
hwid
The HWID is made on your machine as a SHA-256 digest of your operating system's name and architecture, the name of your computer account and the hardware (MAC) address of a network adapter. Only the digest is sent; we never receive those values themselves. Your licence is bound to the first HWID it sees, and we keep when it was bound and when it was last seen.
why
To keep you signed in, to enforce one machine per licence, to spot stolen or shared accounts, and for support.
kept
Indefinitely. Sessions that have expired or been signed out are not deleted at present.

4. the security log

what
A record of account events with the IP address and user agent they came from: registrations (with the email, username and invite used), sign-ins and failed sign-in attempts, licence bindings and sign-ins from a different machine, password resets, invite changes, changes to what friends may do in your client, a friend sending your client to a server (with the server's address), support tickets being opened and closed, and every action staff take on an account.
why
Security, abuse prevention, refunds (it is how we tell whether the client was run after a purchase) and support.
kept
Indefinitely. Nothing deletes it at present.

5. chat, direct messages and tickets

what
Every line you send in the site's chat or the client's irc, with the name it was sent under, the time and your IP address. That includes guests, who get a random guest name held in a cookie. Lines removed by a moderator are hidden but kept. When the slur filter masks a line we keep the original wording for staff. Friend requests, your friends list, the permissions and nicknames you give friends, and direct messages between friends (with when they were read) are stored. Support tickets are stored with their subject, kind and every message.
who sees it
Public channels: anyone, including people without an account. Members' channels: signed-in members. Direct messages: you and the friend. Tickets: you and staff. Staff can see everything here, including removed lines, original wording and IP addresses.
kept
Indefinitely. Nothing deletes chat, messages or tickets at present.

6. what your friends see

what
While the client is connected: the Minecraft server you are on, your game mode and your Minecraft name and UUID.
where
Held only in the server's memory, never written to disk, and gone when you disconnect. Shown only to friends you share presence with (you can turn that off per friend).

7. the duel bot

brain
When the duel bot runs, the client sends each tick of the fight to our brain server: positions, movement, health, hits and the opponent's Minecraft name. The fight itself is not stored. What the bot learns about how each opponent plays is kept in a file for your account, keyed by the opponent's Minecraft name, so it can play them better next time. The server logs when your client connects and disconnects, with your username and IP address.
tapes
Only if you turn on duel upload in the client, which is off until you agree to it when asked: recordings of your duels (where you and the other player were, the keys you held, where you looked, each swing, hit and knockback, and the other player's name) are uploaded and stored under your username, up to 4 GB per account. We use them to train and test the duel bot. Copies are made to our own development machines and may be shared with the machines that train the bot, including machines run by people we trust.
kept
Indefinitely, unless you ask us to delete them. Turning duel upload off stops new uploads.

8. payments

what
Payments are handled by Stripe. We never see or store your card number. We store the IDs Stripe gives us (your Stripe customer, the checkout and the payment), and for each purchase the plan, amount, currency, the time it covers and whether it was paid, refunded or disputed, plus the payment notifications Stripe sends us.
stripe
What you enter at checkout (such as your name, email, card and billing country) goes to Stripe and is covered by Stripe's own privacy policy.
kept
Indefinitely, as a record of what was bought.

9. server logs and rate limits

web server
Every request to pissware.lol is logged with your IP address, the time, the address requested and your user agent. These logs are rotated daily and deleted after 14 days.
api
Every request to the account service is logged with your IP address and the address requested. These logs are kept in the system journal until it reaches its size limit and the oldest entries are dropped; there is no fixed period.
rate limits
Counters keyed by your IP address, to stop floods and password guessing. Each expires on its own after its window, from a few minutes to an hour.

10. cookies

The site sets two cookies, both needed for it to work: ghost_session keeps you signed in (30 days), and pc_guest holds a guest's chat name (30 days). It also remembers in your browser that the start-up animation has played this session.

There are no analytics, no ads, no tracking pixels and no third-party scripts. Fonts and videos are served from our own server.

11. who we share it with

We do not sell your data and we do not use it for advertising. It reaches others only:

  • - Stripe, to take payments
  • - Oracle Cloud, which hosts our servers
  • - the machines that train the duel bot, for uploaded tapes
  • - other users, as described above: public chat, friends' presence and messages
  • - anyone the law requires us to give it to

12. on your own machine

The client keeps its settings, a remembered password (sealed with a key derived from your HWID), duel tapes and other logs in your Minecraft folder. Nothing there is sent to us except what this policy describes.

13. your choices and rights

You can ask us for a copy of the data we hold about you, or to correct it. Write to support@pissware.lol or open a support ticket from the account. We may ask you to prove the account is yours.

To delete your account, open an "account deletion" ticket in #support while signed in, or write to support@pissware.lol. Deletion is done by hand, and we will tell you when it is done. Deleting an account ends its access, and time left on it is not refunded (see the refund policy).

When we delete an account, what is tied only to it goes with it: sign-ins, licence, purchase records, friends and direct messages, and we delete its duel bot file and uploaded tapes. Copies of tapes already used for training may remain in the training data. Chat lines, support tickets and security log entries stay, no longer linked to the account but with the name and IP address they were made under, for moderation and security. Stripe keeps its own records of payments.

You can turn off duel upload and presence sharing in the client at any time.

14. children

Accounts are for people 13 or older. If we learn that an account belongs to someone younger, we will delete it.

15. changes to this policy

We may change this policy. The version and the date it took effect are shown at the top of this page, and when a change matters we will say so on the site.

PissClient · version 1~/legal/privacy.txt