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 mobile-money and bank transactions. BetJocker and Habesha Game Hub run on database-backed ledgers with signature-verified, repeat-safe deposit pipelines, TLS on every endpoint, and role-based back offices with per-action audit logs; Jocker confirms deposits from the transaction reference on the player's receipt, 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 signature-verified, 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 at the database level, 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.

The site is now managed through an authenticated admin console backed by a small service on our own server. The editor signs in with a password that is stored only as a salted hash; the service checks the account and its role, holds the repository credential itself, and commits content changes to the repository, where the service rebuilds the site, runs its checks and publishes it. Inquiries from the contact form are stored by that service on the server, never in a public file, and the browser never sees a secret.

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.