1. Who we are
Governor. Contact: compliance@governorpoker.app. There is no contact form and no ticket queue — that address reaches a person.
2. What the product is
A poker study and training tool for ClubGG, sold by subscription to individual players. It has two parts: a macOS application the customer installs on their own computer, and a server we operate, which does the analysis.
The application captures the customer's own screen, recognises the poker table on it, sends the recognised state to our server, and displays an assessment in a small overlay window on the customer's screen.
We are not going to describe that as anything other than what it is. It reads a live table and it produces an assessment while the hand is in progress.
3. What it does not do
These are checkable claims, not assurances.
3.1 It does not touch your client. No code is injected, no process is attached to, no memory is read, no file of yours is modified, and no network traffic of yours is intercepted or altered. Our software never communicates with your application at all. It reads pixels from the customer's display, using the standard macOS screen-recording permission that the customer grants and can revoke.
3.2 It does not play. It does not click, move the mouse, press keys, or take any action in your client. It cannot: the software contains no input-synthesis code of any kind, and a search of the whole codebase for the system calls that would be needed returns nothing. Every action at the table is taken by the customer, by hand.
3.3 It reads the name on a seat plate, and it keeps none. Our recogniser has eight output classes — card, card fan, seat plate, pot, dealer button, bet, action button and hero plate — and none of them is text. Separately from it, and only on the customer's own Mac, the text inside a seat plate is read for exactly one purpose: to notice that the person sitting at that seat has been replaced. Our software builds a picture of how each seat plays; a seat is not a person, and when someone leaves and someone else sits down, that picture becomes a stranger's. Measured against our own recorded frames, the picture belonged to a stranger on 46% of the moments we assessed. Reading the name is how we throw the stale picture away.
What happens to the name. It exists inside one function, for as long as it takes to reduce it to a 12-byte one-way hash. The hash is salted with 16 random bytes generated fresh every time the application starts and written down nowhere, so the hash cannot be turned back into a name — by us, by you, or by anyone who takes the machine — and it is meaningless the moment the application closes. We do not store the name, we do not log it, we do not send it to our server, and we do not keep a list of your players. The nickname band and the avatar band are still painted solid black on every frame that leaves the Mac, exactly as before; nothing in that change was relaxed. That matters for section 5, and we say more about it there.
3.4 It does not run more than one account, or bot a table. One subscription, one person, two devices, and only one of those two receiving assessments at any moment — the server hands out a single rolling lease per account, so two people cannot play two tables on one subscription.
4. Responsibility, and what we tell our customers
Our Terms of Use require every customer, before they use the product, to read the rules of the platform they play on and to decide whether their intended use is permitted there. They state that the customer alone is responsible for playing honestly and for complying with your terms. We do not tell customers that you permit this, and we do not tell them the rules of your platform, because that is yours to say and not ours.
We are aware that this is a paragraph in a document, and that a paragraph does not constrain anybody. That is why this page exists.
5. If you want a user of ours blocked
Send us the player's email address and we will terminate their access.
Why an email address
Our customers sign in with Google. The identifier we hold is an email address — that, and nothing resembling a table nickname.
You register your players by email. The link between a name at your table and a person is therefore one you already hold, and it is one we have deliberately put ourselves in no position to make. Send us the result of your own lookup and we act on it immediately and with certainty.
One condition, and it sits on your side rather than ours: this resolves if the player used the same email address with you and with us.
6. What to send us
Send to compliance@governorpoker.app, with the subject line BLOCK REQUEST:
- The email address.
- Your reference — your ticket or case number, so that both sides can cite it later.
- A statement that the request is made by your platform, by someone authorised to make it, from a domain we can see belongs to you.
- What you want — access terminated, or suspended pending your investigation.
You do not need to send us hand histories, screenshots, evidence, or your reasoning. We are not going to adjudicate whether your player broke your rules. That is yours.
7. What we do
- Acknowledge within 2 business days, from a person, with your reference quoted back.
- Terminate access. The account is marked blocked and the server stops serving it. This takes effect on the next request the application makes, requires no cooperation from the customer, and is enforced on our server and not by software on the customer's machine — so it cannot be evaded by declining to update, by reinstalling, or by moving to another computer. It is the same mechanism we use for non-payment. No refund is given for a termination on your request.
- Reply within 2 business days with the outcome.
- Record your reference against the account, so that if you ask again we can answer.
- If the address is not one of ours, we say so.
8. What we will not do
- We will not hand over a customer's identity, payment details or gameplay records on request. Terminating access is one thing; disclosing personal data to a third party is another, and it needs a legal basis. Send lawful process if you need data, and we will take it seriously.
- We will not confirm or deny that a named individual is a customer, beyond telling you whether we were able to act on your request.
- We will not build a database of your players. This page used to promise that we would never read a nickname off the screen at all. That is no longer true and we would rather say so than leave a comfortable sentence standing: since 30 August the client reads the name on a seat plate on the customer's own Mac, for the single purpose described in 3.3 — noticing that the occupant of a seat has changed. What the promise was actually protecting is intact. The name is turned into a one-way hash under a random salt that dies with the process; it is never stored, never logged, never sent to us, and never leaves that Mac. We hold no table nicknames and no field for one, we cannot connect a name at your table to an account of ours, and the nickname band is still painted out of every frame we receive. If you would rather that were different, tell us and we will listen.
9. If you want the product changed, or gone
If your position is that this product should not exist in its present form, say so to the address above and say what you want. You will get an answer from a person. We would rather hear it from you directly than read about it.