Security & data

Your agency's records, kept yours.

What your IT and procurement offices usually ask: where the data lives, who can see it, what gets logged, how it's backed up, and what the AI tools do with it.

Your data stays yours.

Walled off in the databaseEach agency's records are kept apart by the database itself, with PostgreSQL row-level security, so one agency cannot see another's. The app checks the agency and the person's role on every request as well.
Tested on every routeIn November 2026 we tested all 352 of the app's routes with two test agencies: 861 attempts by one agency to read, search, export or change the other's records, with every response and every exported file (spreadsheets, PDFs, ZIPs) searched for the other agency's data. None got through. That test now runs automatically on every change.
Export anytimeExport your records at any time, and a full export if you leave, including after your subscription ends.
Who at Battle Rhythm has accessTwo owner-administrators. Support access to an agency's records happens only at that agency's request.
If something goes wrongWe notify your agency within 72 hours of confirming a security incident that affects your agency's data.

Access follows the ICS position.

Each person's access comes from their position, and one sign-in opens every tool your agency has turned on.

  • Command / Admin: manages the agency's people and settings, with full access to its records.
  • Finance/Admin Section: enters costs, and approves crew time and shift tickets.
  • Field (crew boss): the field app only, with no pay rates or costs.
  • Command & General Staff: view only: dashboards, costs and reports, with no changes.
  • Leadership: view only, for city and county managers and elected officials: one summary page of the event, with no downloads and no changes.

One person can hold several positions (in a small county, the EOC Director is often the PIO too). Extra positions add the duties of that seat but never raise the person's permission level.

PasswordsAt least 15 characters, stored only as a bcrypt hash.
Two-step sign-inWith an authenticator app. Required for every administrator, and your agency can require it for everyone. Two-step secrets are encrypted with AES-256-GCM.
Setup linksNew accounts and password resets get a single-use link by email that expires after 72 hours. Links are never written to our server logs.
SessionsIdle sign-out set by each agency (30 minutes by default), and every session ends after 12 hours.
Sign-in attemptsRate limited from each network, and an account locks for 15 minutes after 10 wrong passwords or two-step codes in a row, from anywhere.

Audit & legal.

Activity logEvery sign-in, change, approval and export is recorded. The log is append-only: the database refuses edits, deletes and wipes to it, even from the database owner.
For your adminsAgency admins can view the log and export it to CSV.
Deleted isn't goneDeleted entries are archived and can be restored, for records-retention requirements.
Signed recordsEach signature carries a SHA-256 fingerprint of exactly what was signed, so a change made after signing, even one made outside the app, shows up as a mismatch.
Signed means lockedSigned and approved entries can't be edited or deleted. To correct one, an approver reopens it with a reason and it is signed again. The entries it removed are kept as view-only copies in Deleted records, so an auditor can see what was there.
Legal holdPut a project on legal hold and its records can't be deleted, and signed records can't be reopened, until the hold is released.
Changes under legal holdWork on a held project can continue, but every change needs a reason, and the version before it is kept view-only: what it was, what it became, who changed it, when and why. That history can't be edited or deleted.

Backups & retention.

Nightly off-site backupsEvery night to Backblaze B2, a separate provider, and each run is verified when it finishes.
RestoresA restore goes into a separate database first and is checked there, never straight over live data.
Backup retentionEach nightly backup is locked for 30 days: during that time no one, Battle Rhythm included, can change or delete it. The hosting side can add backups but never read or remove them.
Your recordsKept for as long as your agency uses Battle Rhythm. See the privacy policy.

Hosting & encryption.

Where it runsOn Railway, in its United States (US East) region, with a managed PostgreSQL database. Railway holds SOC 2 Type II and SOC 3 reports.
In transitHTTPS only, with HSTS.
At restEncrypted with AES-256 by Railway, including the database, its storage and its backups.
Browser protectionsContent Security Policy, X-Frame-Options DENY, nosniff, and strict referrer and permissions policies.
Security testingInternal penetration testing of sign-in, agency separation, uploads and the public pages, most recently in November 2026, with every finding fixed. Automated security tests run on every change.
Support requestsSupport tickets are kept with your agency's records and seen only by your agency's administrators, the person who opened them and Battle Rhythm support. Bug reports send our engineering tracker a summary with names, emails, phone numbers and long numbers removed, never your records.
Website visitsVisits to our public website are counted on our own servers, with no cookies and no outside tracking company. Nothing inside TRACE is tracked.

PoppaGPT & AI.

PoppaGPT, your guide to the PAPPG, and Scout, which reads invoices and receipts, use OpenAI.

Your agency decidesEach agency admin can turn PoppaGPT and Scout off. Nothing is sent to OpenAI then.
ScoutRequests are sent with storage off, and scanned documents are not stored by OpenAI for training. Your people confirm every line Scout reads before it's saved.
PoppaGPT and trainingPoppaGPT and Scout use OpenAI’s API. OpenAI does not use data sent through its API to train its models.
People stay in chargeEntries made by talking or typing to PoppaGPT are confirmed before they're saved. PoppaGPT cannot approve or sign anything.
Your documents stay yoursDocuments your agency adds for PoppaGPT (plans, policies, agreements) go into a library only your agency’s PoppaGPT searches. Removing one deletes it from the library and from OpenAI’s file storage. Uploads and removals are in the audit log.
State guidance stays in its stateEach state’s guidance is kept in its own PoppaGPT library, searched only for agencies in that state, so an agency never gets another state’s rules.
Only what you can seePoppaGPT only sees what you can see and can't change records. Its guide (what's waiting on you, why something is stuck) reads your own screens with your permissions, and every lookup is recorded in the audit log.

Offline field app.

Crew bosses can keep working with no signal. Here is what stays on the phone while it's offline.

Crew time reportsSaved in the phone's browser storage as drafts, including shift tickets and signatures, until there's signal. They sync to your agency's account as drafts when the phone is back online.
SubmittingSubmitting a report for approval needs signal. After it's submitted, its draft is removed from the phone.
Crew listThe crews, people, equipment and events or projects the crew boss works with are kept on the phone so the app opens offline.
Debris photosQueued in the phone's storage with their details and upload on their own when signal returns. Each is removed from the phone once it's uploaded.

Mapped to NIST SP 800-53.

For security reviewers: how these protections line up with NIST SP 800-53 Rev. 5 controls. This is our own mapping, not a certification or a third-party assessment.

  • AC-3, access enforcement: database row-level security per agency plus a role check on every request, tested across all 352 routes.
  • AC-6, least privilege: access follows the ICS position; crew bosses never see pay rates or costs, view-only seats can't change anything, and extra positions never raise permissions.
  • IA-2(1), multi-factor for privileged accounts: two-step sign-in is required for every administrator.
  • AU-2 and AU-12, audit events: sign-ins, changes, approvals, exports and PoppaGPT lookups are logged with who, when and from what network address.
  • AU-9, protection of audit information: the audit log is append-only in the database, even for the database owner.
  • SI-7, information integrity: SHA-256 fingerprints on signed and approved records reveal any change made after signing.

Documents for procurement.

  • W-9 and certificate of insurance on request.
  • Security questionnaire answers on request.
  • Accessibility report (VPAT): not available yet. Ask us about accessibility.
  • Report a security issue: see security.txt.

Ask for any of these through the contact page. Pricing and purchasing terms are on the pricing page.

Questions from your IT office?

We'll answer them, or fill in your agency's security questionnaire.