Security, stated plainly: what is live, what is designed, and what we got wrong once.

What is live today

GeezSoft operates three production products — BetJocker, Habesha Game Hub and Jocker — with real users and real Telebirr and CBE transactions. BetJocker and Habesha Game Hub run on PostgreSQL-backed ledgers with webhook-based, HMAC-verified deposit pipelines, TLS on every endpoint, and role-based back offices with per-action audit logs; Jocker records every draw on the server before it is called and keeps a full wallet ledger. The same practices apply to the institutional and business systems we build for clients; see how we work for backups, documentation, training and support.

Encryption

• In transit: TLS everywhere, no exceptions — every page on this site and every service we run.
• At rest: managed-database encryption at rest. Per-tenant keys are part of the multi-tenant engine design.
• Secrets: bot tokens and payment-rail credentials never ship to the client or the repository.

Payments

Deposit callbacks are verified (HMAC), processed idempotently (a duplicate delivery cannot double-credit), and reconciled against the provider's own records rather than trusting the callback alone. Withdrawals pass through tiered KYC and an approval queue.

Tenant isolation — the design we are building to

The white-label engine for third-party operators is being designed so every row — players, bets, deposits, withdrawals, sessions, audit logs — carries an indexed tenant identifier enforced by PostgreSQL row-level security, with CI fixtures that assert cross-operator invisibility. This engine is in development; we do not describe it as live.

Game integrity

Games publish their return. Provably-fair seeding (committed seed and nonce per round, revealed after) and independent RNG certification are on the roadmap and will be listed on the status section when live.

A finding from our own audit

An earlier version of this website shipped a browser-based admin tool that asked visitors to paste a GitHub personal access token with write access to this repository, stored in plain text in the browser, and wrote lead data into a public file. That tool has been removed, the exposure closed, and the lesson — secrets and personal data never belong in a static site — is now a rule in how we build.

Reporting a vulnerability

If you believe you have found a security issue in any GeezSoft product or this website, email security@geezsoft.org. We read every report and reply to every one.