Security at Jawaab
Built for institutions that can't compromise
Banks, government agencies, and NGOs run controlled processes on Jawaab. Here is, plainly, how the platform protects the data you collect.
Tenant isolation, enforced in the database
Every table is protected by row-level security. Access checks run inside the database on every query — your organization's forms, responses, and files are invisible to any other tenant, even if application code is bypassed entirely.
Role-based access control
Admins, editors, and viewers have distinct, server-enforced permissions. Sensitive actions — approvals, external integrations, member management — check the caller's role in the database, never just in the browser.
Approval workflows with a permanent audit trail
Reviewer and approver stages are enforced server-side, official-use values can be auto-stamped from the signed-in account, and every action is written to an append-only audit record that survives resets.
Signed, verifiable integrations
Webhook deliveries are signed with HMAC-SHA256 and carry idempotency keys, so your systems can cryptographically verify every payload and safely ignore duplicates. Endpoints are restricted to public https hosts.
Layered backups & disaster recovery
Managed database backups with point-in-time recovery, plus independent nightly incremental and weekly full logical exports to isolated storage — portable JSONL your administrators can download and retain off-platform.
Encryption everywhere
All traffic is encrypted in transit with TLS. Data is encrypted at rest. Respondent uploads live in private storage and are only reachable through short-lived, membership-checked links.
Hardened public endpoints
Anonymous submission endpoints re-validate every answer server-side, enforce per-IP and per-form rate limits, reject oversized or malformed payloads, and guard against regex and content-injection abuse.
Operational visibility
Administrative actions are logged to a dedicated audit log. Email delivery health, webhook deliveries, backups, and platform activity are all observable from the admin console.
Engineering practices
Server-side validation
Every public submission is re-validated against the form definition on the server — required fields, ranges, patterns, and official-use protections don't rely on the browser.
Least-privilege functions
Privileged database routines verify the caller's identity and role before acting, and are revoked from public access by default.
Rate limiting
Submission, upload, messaging, AI, and geocoding endpoints carry per-IP, per-user, and per-organization limits with configurable thresholds.
Secrets management
API keys and service credentials are stored server-side only — never shipped to the browser, never included in exports.
Data portability
Your data is never locked in: CSV/Excel exports, Google Sheets sync, signed webhooks, and platform backups in plain JSONL.
Consent & retention
Built-in consent blocks record acceptance with each response, and soft-deleted data is purged on a fixed schedule.
Reporting a vulnerability
Found something? We want to hear about it before anyone else does. Report suspected vulnerabilities through our contact page and we'll acknowledge within one business day. Please don't access data that isn't yours while demonstrating an issue.
Contact security →