Evidence before promises
Trust should be inspectable.
This centre explains what GamHR does, how important controls work, where data may flow, and which responsibilities remain with people.
Where GamHR fits
A South African HR control layer for growing organisations.
GamHR is designed especially for organisations with 11-50 employees that need clearer employee records, approvals, self-service, payroll readiness, and audit evidence.
You can keep an existing payroll, accounting, calendar, or email system. Native payroll is available, but replacing another system is not a condition of using GamHR.
Purpose-limited processing
For workspace records, the subscribing employer generally decides why employee information is processed. Mangam Systems provides GamHR and processes that information to deliver, secure, support, and recover the service under the applicable agreement.
Public-site and trial-contact information is used only for the requested acquisition, communication, security, and support purposes described in the Privacy Policy. GamHR does not sell personal information.
Read the Privacy Policy or review the official POPIA publication.
Role and tenant boundaries
Workspace data is tenant-scoped. Directors and HR Managers have organisation-wide operating authority; Managers are team-scoped; Employees use self-service access to their own appropriate records.
Privileged operations use current authorization and MFA where required. Important actions create tamper-evident audit evidence. A journey, notification, agent, or provider connection never grants authority by itself.
Statutory basis
The SARS 2027 tax year covers 1 March 2026 to 28 February 2027. Payroll processing requires reviewed source evidence and explicit operator activation of the versioned rules selected by pay-period date. New payroll records snapshot the exact rule identities used so historical results can retain their original basis.
If the required source, activation, or historical snapshot evidence is unavailable, generation is blocked while read-only workspace access remains available. A published tax-year date is not proof that a workspace's payroll or historical files have passed production certification.
Payslips and implemented statutory review outputs carry tax-year and rule-set evidence. Current custom EMP201, EMP501, and legacy IRP5 exports are for internal review and reconciliation; they are not represented as SARS submission files.
Provider data flows
Firebase supports authentication, Firestore stores application records in its configured South African location, and Azure hosts the application and protected credential references. Provider access is purpose-limited and credentials are not stored in ordinary workspace documents.
Optional Mish, calendar, and Xero workflows are separately controlled and revocable. Mish receives bounded, redacted guidance context; calendar connections send approved-leave scheduling data without leave reasons; Xero receives aggregate journal data only and creates reviewed drafts when that capability is enabled.
Zoho Books, QuickBooks Online, public agent OAuth, and remote MCP are planned programme work and are not described here as live connections.
Backup and recovery
GamHR uses provider-managed backup controls and a guarded restore procedure. A controlled August 2026 drill restored a selected production backup into an isolated database, compared privacy-safe aggregate counts and digests, and removed the isolated target only after review.
This evidence demonstrates that the procedure was exercised. It does not promise zero data loss, uninterrupted service, or a contractual recovery time. Customers should retain exports needed for their own continuity and evidentiary duties.
Export and retention
Authorised users can export implemented payroll, compliance, audit, and workspace records. Under the current billing contract, billing owners retain export access for 30 days after normal access stops, and a retained workspace may remain recoverable for up to 90 days.
Employment, payroll, security, and legal records may require different retention periods. GamHR provides review and archival controls; the employer remains responsible for selecting a lawful purpose, applying its policy, and keeping required external copies.
Product and integration limits
- GamHR is operational software, not legal, tax, labour-law, payroll, or accounting advice.
- People remain responsible for payroll finalisation, leave approval, HR decisions, legal acceptance, and statutory submission.
- Optional integrations are feature-gated and may be unavailable to a workspace.
- No specific uptime percentage, penetration-test result, or external security certification is claimed.
- The evidence date above is not a statement of current live availability.
First payroll and migration expectations
Start with company settings, an active department, and one payroll-ready staff record. Imports and statutory settings must be reviewed before the first payroll preview. A Director or HR Manager should compare opening information and preview totals with the source records they trust.
Migration timing depends on data quality, chosen scope, and the employer's review. GamHR does not promise an unattended migration or automatic first payroll.
Observed operations
Dated evidence, not a permanent badge.
The latest accepted production evidence recorded before this review observed a healthy application revision, passing public smoke checks, and no failed requests in the sampled stability window. That observation is historical and can become stale.
For a current access problem, use Support. GamHR does not currently publish a guaranteed response time. Signed-in users can also submit an issue with a durable reference and acknowledgement workflow.
Choose the next useful step