Encryption in transit
TLS 1.2 or higher at the reverse proxy; HSTS enabled in production.
Trust Centre
This page describes what the platform does, where it runs, who processes data, and which claims are not yet true. It is updated with the product, not with the sales cycle.
Jurisdiction & hosting
Those are two different facts, and we state both. RemoteRegister is designed for South African statutory obligations. The current production deployment runs on Hetzner in Helsinki, Finland.
Security programme
Each item below is implemented in the application or the deployment process. None of it replaces an independent penetration test; that is listed as an open item.
TLS 1.2 or higher at the reverse proxy; HSTS enabled in production.
Provider volume encryption plus application-level envelope encryption for sensitive fields.
Short-lived access tokens, rotating refresh sessions, optional OIDC SSO and TOTP for privileged roles.
Role and tenant scope enforced by API middleware, with separation-of-duties checks in finance and verification flows.
Hash-chained audit entries and daily Merkle roots. The public verifier resolves hashes against sealed roots.
Integrity-checked snapshots with a documented restore drill. Production restores verify the audit chain before applying.
Per-client sliding windows, Redis-backed in multi-worker deployments.
Content-type protection, frame denial, referrer policy, permissions policy and production HSTS.
Documented severity model, break-glass support protocol and post-incident review.
Type checking, automated tests and dependency review in the release process.
Subprocessors
The register names the processor, the purpose and the location. “To be confirmed” means the deployment does not yet have a contracted provider for that function.
| Processor | Purpose | Location | Notes |
|---|---|---|---|
| Hetzner Online GmbH | Cloud compute and block storage | Finland (EU) | Primary application and snapshot storage |
| Cloudflare, Inc. | DNS, TLS termination and proxy | Global edge | TLS and DDoS protection; no application database access |
| Email gateway | Transactional email | To be confirmed | Only if configured; otherwise transactional email is disabled |
| SMS / WhatsApp gateway | OTP and service notifications | To be confirmed | Only if configured; otherwise OTP routes return 503 in production |
| DHA reseller | Identity verification | South Africa | Only if configured; simulator mode otherwise |
| AVS-R bureau | Bank account verification | South Africa | Only if configured; simulator mode otherwise |
| Payout providers | Stipend disbursement | South Africa | Only if configured; sandbox or simulator mode otherwise |
| Biometric matcher / PAD vendor | Template matching and liveness | To be confirmed | Required for production biometric matching; contract defined |
Integration register
RemoteRegister ships adapters with explicit modes. Simulator mode is useful for demonstration and testing; it is never represented as a real external effect.
| Channel | Default mode | Go-live requirement |
|---|---|---|
| DHA identity | Simulator until configured | Certified reseller contract, credentials, smoke test |
| AVS-R bank verification | Simulator until configured | Bureau contract, credentials, smoke test |
| Payout rails | Simulator until configured | Provider onboarding, webhook secret, sandbox then live |
| SMS / WhatsApp | Disabled in production until configured | Local gateway contract and OTP handset test |
| Disabled until configured | Gateway URL and sender verification | |
| LMS connectors | Configured per tenant | LMS endpoint and credentials, connection test |
| Fingerprint matcher / PAD | Simulator until configured | Certified vendor contract and benchmark |
| Public verification | Live | Sealed ledger lookup only; fabricated hashes return NOT_FOUND |
Statutory mapping
Lawful processing, purpose limitation, minimality, consent records, Information Officer contact, data-subject request workflow and section 72 cross-border safeguards.
Data messages and electronic signatures are admissible where integrity and reliability are demonstrated. The audit chain and sealed evidence packs provide that record.
Learnership stipend and working-hour rules are encoded in the stipend engine and attendance policy.
Learnership floor tiers and shortfall top-up are applied deterministically during pay-run calculation.
Deduction schedules, ETI monthly summaries and IT14SD supplementary declarations are generated from the same learner and payroll records.
NLRD File 27/28/29 generators, SETA MIS mapping profiles and a quality gate before submission.
Access, correction, deletion and objection requests are logged and routed to the Information Officer. Email [email protected].
Report a suspected vulnerability to [email protected]. Please do not test against learner data or a production tenant without written authorisation.
Operational status is published at https://rr-status.medq.co.zw. Material incidents are disclosed there with the affected service and current state.
Send it. We will answer every line, including the ones where the answer is “not yet”.