Security at HelpBat

How HelpBat protects your customers’ conversations, and what we do not claim.

Tenant isolation

Every record belongs to one workspace, and every query carries the workspace id. Requests name their workspace and are checked against the person’s membership and role first. Tests check that one workspace cannot read or change another’s data.

Roles and permissions

Built in roles plus custom roles with granular permissions. API keys act as the member who made them, limited by scopes, and stop working when that member leaves.

Sign in

Sign in goes through OfficeBats. Workspaces can require two factor sign in and limit access to approved IP ranges. Sessions are HTTP only cookies, and cross site requests are refused.

Encryption of stored credentials

Mailbox passwords, webhook signing secrets and channel app secrets are encrypted at rest with AES-256-GCM under a key kept outside the database, with key rotation. They are never sent back to the browser.

Audit log

Admin changes, exports, erasures, redactions and API writes are written to an append only audit log. Each entry includes a hash of the previous one, so an altered or removed entry is detected. Enterprise workspaces can export it.

Email and content safety

Inbound HTML is cleaned to a short allowlist before it is stored or shown: no scripts, forms, frames or event handlers. Links open safely. Help center and portal pages use a strict content security policy.

Attachments

Only common document, image and media types are accepted, with size limits, and the file content must match its declared type. Files are served as downloads unless they are images or PDFs, with nosniff and sandbox headers.

Sensitive data

Card numbers (checked with the Luhn rule), ID numbers and bank accounts can be removed from messages on arrival, or by an agent at any time. GDPR export and erase are built in, and retention policies delete old tickets.

Rate limits and abuse

Per network limits on the app, per key limits on the API, limits on sign in, chat, forms and webhooks, and honeypot fields on public forms. Outbound webhooks refuse private network addresses.

Reliability

Scheduled work (replies after undo, scheduled replies, SLA checks, automations, mail polling, webhook retries) is stored in the database and claimed with leases, so a restart or a second server never loses or doubles work. Health checks and a public status page show the state of each part.

Backups

Data lives in a managed MongoDB cluster with automated backups and point in time recovery. Attachments live in object storage.

What we do not claim

HelpBat is new. It does not hold SOC 2 or ISO 27001 certification today. Ask us at [email protected] for details of how data is handled.