Trust & Security

A plain-language summary of how IHGIZ handles your data today. Every claim on this page is verified against the codebase — nothing here is aspirational.

Data storage

All application data lives in MongoDB Atlas. Following our incorporation in Dubai (June 2026), migration of the database region to the UAE is planned; until it completes, data may be hosted in another Atlas region.

Encryption

All traffic is encrypted in transit (TLS). Channel credentials you connect — bot tokens, API keys, provider secrets — are encrypted at rest with AES-256-GCM, and a production deployment refuses to start without the encryption key.

Access & authentication

Sign-in uses session-based authentication, and new accounts are approved manually during the invite-only pilot. Operator capabilities are restricted to named platform administrators, and restricted portal areas use per-user access grants.

Inbound message verification

Webhooks from messaging providers are verified before processing: Meta channels via X-Hub-Signature-256 HMAC, inbound email via a shared-secret or HMAC header, and SMS providers via each provider's published signature scheme. Unverified requests are rejected.

API keys

API keys are scoped per resource, shown once at creation, and stored only as SHA-256 hashes. Keys can be revoked at any time, and revoked keys remain on record for audit.

Audit trail

Every appointment state change writes an audit entry on the event itself — including automated transitions, which are tagged as system actions with their trigger. "Who confirmed this?" is always answerable.

Sub-processors

Deliveries run only through the channels you choose: Resend (email), Meta Cloud API (WhatsApp, Messenger, Instagram), Telegram Bot API, and your configured SMS provider (e.g. Twilio). Meeting links are created with your chosen video provider. Data storage: MongoDB Atlas.

Certifications

IHGIZ does not yet hold SOC 2 or ISO 27001 certification, and we will not display badges we have not earned. This page will track our security posture as it evolves.

This is a code-verified engineering summary, not a legal document. Formal security documentation and lawyer-drafted policies are pending counsel review.

Last verified against the codebase: 23 July 2026

Back to home