Security & trust

How CallHeim protects your incident operations.

Organization isolation, roles and permissions, encryption in transit and at rest, an append-only audit trail with a retention-locked archive, and point-in-time recovery — the controls behind every incident your team runs through CallHeim.

  • Organization A4 rows
  • Organization B3 rows
  • Organization C5 rows
API authorization rule

Example: a read from Organization B

Returns Organization B’s three rows and nothing from A or C.

One shared database, with every organization fenced off from the others.

Organization isolation

How your data is separated from other organizations

Reads and writes are scoped by the API authorization rule to the caller’s organization, or to the caller’s own user for personal records, and custom operations enforce the organization in server-side code. CallHeim is multi-tenant on a shared database.

Identity & access

Who gets in, and what they can do.

Assignment

Your organization and role are assigned server-side and stamped on your token; users cannot edit them.

Sign-in and two-factor

E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication.

Roles and permissions

Five built-in roles with granular permissions, plus per-organization permission overrides and custom roles.

Directory provisioning. Business and Enterprise organizations can create, update and deactivate members from their identity provider through SCIM 2.0. Roles are set in CallHeim, not by the identity provider.

Integration secrets are stored in AWS Secrets Manager and are shown once when created or rotated; the console never shows them again.

Encryption

How data is protected in transit and at rest.

The console

The console is served over HTTPS (TLS 1.2 and 1.3 are accepted) with HTTP redirected to HTTPS, HSTS with a two-year max-age, nosniff, clickjacking and referrer protections.

Data at rest and in transit

Data is encrypted at rest with AWS encryption (DynamoDB, S3 and SQS) and in transit with TLS.

Storage

CallHeim’s S3 buckets block public access and are encrypted at rest.

Audit log

An append-only record of what changed.

The audit log is append-only: no client can modify or delete an entry.

The audit log records incident acknowledge and resolve, user invitations and deactivations, role changes, forced sign-out and organization settings changes. Configuration changes to schedules, escalation policies, services, teams and integrations are recorded with before and after values.

Audit records are copied daily to an S3 Object Lock archive (governance mode) with a 7-year retention lock, held by CallHeim. An audit-log export downloads straight to your device, and CallHeim keeps no copy of it.

Data protection & recovery

Backups and point-in-time recovery, built in.

Point-in-time recovery (35-day window) and deletion protection are enabled on CallHeim’s production data tables.

A daily managed backup with 35-day retention covers eight core tables (incidents, alerts, organizations, users, schedules, escalation policies, the audit log and de-duplication keys), in an AWS Backup vault in the same account and region. Daily per-organization configuration snapshots (users, teams, schedules, escalation policies, integrations) are kept for CallHeim-assisted recovery.

Incident intelligence

How severity suggestions use your incident data.

No incident data is sent to an external language model, and CallHeim does not train any model on your incidents. Severity suggestions and related-incident insights are rule-based code running inside CallHeim’s own AWS environment.

See how severity suggestions work →

Release safeguards

What has to pass before a change reaches production.

Every release of the CallHeim app runs automated tests, a type-check, lint, a secret scan and a dependency audit that blocks on critical findings before it deploys, and a failing step stops the deploy.

Reliability

How inbound alerts are buffered.

Inbound alerts are queued durably, with a dead-letter queue and alarms, so a burst of alerts is buffered while it is processed.

Where your data goes

Every recipient of page content and platform data.

Application data is stored in AWS us-east-1. Page e-mail is sent through Resend and contains the recipient address, the incident’s severity, number and title, an acknowledge link and a link to the incident. Phone-number verification codes are sent through Twilio. If your organization turns on SMS and voice, those texts and calls also pass through Twilio: a text carries the incident severity, title and a one-time acknowledge link, and a call reads out the severity and title. If a responder turns on push notifications, a short notification with the incident title and links passes through their browser vendor’s push service. If your organization connects Slack or Microsoft Teams, incident notifications also go to the channels you configure there. The sign-in page at app.callheim.com loads its fonts from Google Fonts.

Compliance

Compliance status.

CallHeim does not currently hold SOC 2, ISO 27001 or other third-party security certifications.

For your security review

Quick answers to the questions reviewers ask.

QuestionAnswer
Who operates the service?Packysnappy, which runs CallHeim.
Where is data stored?In Amazon Web Services, region us-east-1.
How are organizations separated?Reads and writes are scoped by the API authorization rule to the caller’s organization, or to the caller’s own user for personal records, and custom operations enforce the organization in server-side code. CallHeim is multi-tenant on a shared database.
How is data encrypted?Data is encrypted at rest with AWS encryption (DynamoDB, S3 and SQS) and in transit with TLS. The console is served over HTTPS (TLS 1.2 and 1.3 are accepted) with HTTP redirected to HTTPS, HSTS with a two-year max-age, nosniff, clickjacking and referrer protections.
How do people sign in?E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication. Business and Enterprise organizations can create, update and deactivate members from their identity provider through SCIM 2.0. Roles are set in CallHeim, not by the identity provider.
What roles exist?Five built-in roles with granular permissions, plus per-organization permission overrides and custom roles.
Is there an audit log?The audit log is append-only: no client can modify or delete an entry. Audit records are copied daily to an S3 Object Lock archive (governance mode) with a 7-year retention lock, held by CallHeim. An audit-log export downloads straight to your device, and CallHeim keeps no copy of it.
What about backups?Point-in-time recovery (35-day window) and deletion protection are enabled on CallHeim’s production data tables. A daily managed backup with 35-day retention covers eight core tables (incidents, alerts, organizations, users, schedules, escalation policies, the audit log and de-duplication keys), in an AWS Backup vault in the same account and region. Daily per-organization configuration snapshots (users, teams, schedules, escalation policies, integrations) are kept for CallHeim-assisted recovery.
Where are integration secrets kept?Integration secrets are stored in AWS Secrets Manager and are shown once when created or rotated; the console never shows them again.
Which services receive data?Amazon Web Services, Resend, Twilio, browser push services, and Slack or Microsoft Teams if you connect them. The full list is on the service providers page.
Is incident data sent to an AI model?No incident data is sent to an external language model, and CallHeim does not train any model on your incidents. Severity suggestions and related-incident insights are rule-based code running inside CallHeim’s own AWS environment.
How are releases checked?Every release of the CallHeim app runs automated tests, a type-check, lint, a secret scan and a dependency audit that blocks on critical findings before it deploys, and a failing step stops the deploy.
Certifications?CallHeim does not currently hold SOC 2, ISO 27001 or other third-party security certifications.

For a questionnaire or a data processing agreement, open a request from Help Center in the app; it opens with the free trial. How to reach the team →

Responsible disclosure

Report a security issue.

Report a vulnerability privately through Help Center in the app: set the priority to Urgent, put “Security” in the subject, and include the steps to reproduce, the affected URL and the impact. If you do not have an account, a free trial opens one. Do not test against data that belongs to other organizations. The route is also published in /.well-known/security.txt.

CallHeim

Built to be checked, not just claimed.

Start a 14-day trial, connect one alert source and send yourself a test page.