Security overview
Scene SizeUp LLC · Last updated 17 November 2026
This page describes how Scene SizeUp protects department data. It is written for the person in a fire department, town, or county who has to answer "is this safe to buy" before a purchase order is signed. It describes what the system actually does today, not what is planned.
If you need something this page does not cover, write to support@getsizeup.com and ask. We would rather answer a specific question than have you guess.
What we hold
A department using Scene SizeUp stores:
- Accounts: names, usernames, email addresses, and roles for the members a department adds.
- Scenarios: photographs of buildings in the department's district, addresses, and the fire conditions an instructor authored.
- Drill records: an append-only log of everything that happened in a training exercise, including who held command, unit assignments, and timestamps.
- Radio traffic: audio recorded during a drill, and an automatic text transcript of it.
- Evaluations: an instructor's assessment of a member's performance, where the department uses that feature.
- Training items: documents, pictures and links that instructors and administrators post for their department's members, with a title, a description and any dates set for them.
- Billing contact details for departments that are invoiced.
We do not ask for and do not want: social security numbers, dates of birth, home addresses of members, medical information, or any record about a real incident or a real patient. Scene SizeUp is a training system. Do not put real incident data, real patient information, or anything covered by HIPAA into it. That includes files posted as training items: no medical forms, no discipline letters, and no photographs of patients or accident scenes.
Where it runs
Scene SizeUp runs on Railway infrastructure in the United States, behind Cloudflare. All traffic is served over TLS. Department data lives on a persistent volume attached to the application, and on backup snapshots in object storage. Railway publishes its own security and compliance documentation covering the underlying platform, and we are happy to point you to it.
Access control
- Departments are isolated. Every query that reads department data is scoped to the department making the request. A member of one department cannot read another department's scenarios, drills, rosters, recordings, or training files.
- There are two exceptions, both deliberate and opt-in. The first is the Scenario Library. A department administrator may choose to submit a scenario for us to review and publish, and a published scenario can then be copied by other departments. Nothing is published unless an administrator submits it, the street address is removed automatically, and credit names the department and never an individual. Drills, rosters, recordings, evaluations and training records are never publishable by any route. See the Scenario Library Submission Terms.
- The second is a mutual aid drill. Two departments may link so they can train together, which takes an administrator on each side. A drill is shared only when the department running it turns on Allow mutual aid for that drill. Members of the linked department who join see and hear what any participant in that drill does, and can open its review afterward. Nothing else about either department becomes visible to the other: not its roster, its scenarios, its other drills, its evaluations or its training records. Either department can end the link at any time.
- Roles. An admin runs the department and manages the roster. An instructor builds scenarios and runs drills. A member takes part in drills. An instructor never sees the roster management surface.
- Guests. A drill can optionally admit guests with a four-letter code and no account. Guests see only the drill they joined and never appear in training-hours reporting.
- Our own access is audited. Scene SizeUp staff can act inside a department for support purposes. When that happens the system records both identities: the staff member who is really acting and the account they are acting as. That record cannot be turned off by the person using it.
Passwords and sessions
- Passwords are hashed with scrypt using a per-account random salt and a 64-byte derived key. Plaintext passwords are never stored and never written to logs.
- New accounts are issued either a single-use link where the person sets their own password, or a temporary password that must be changed at first sign-in.
- Changing or resetting a password revokes every existing session for that account immediately.
- Password reset links are single-use and expire after seven days. A reset request returns the same answer whether or not the account exists, so the form cannot be used to discover who has an account.
- Sign-in is rate limited, and repeated failures are recorded in the audit trail with the source address.
- Multi-factor authentication (MFA) with an authenticator app can be required for every account in a department. When it is, signing in takes the password and a 6-digit code (RFC 6238), each code works once, and a sign-in allows five code attempts before starting over. It covers every way of starting a session, including password reset links, so control of a member's email is not enough to get in. Ten single-use recovery codes are issued at setup and stored only as hashes. App secrets are encrypted at rest with a key held outside the database, so a copy of the database alone cannot produce codes. A department admin can reset a member who loses their phone; the reset is recorded and the member is emailed. Scene SizeUp's own staff accounts always use it.
The audit trail
Administrative actions are recorded with what changed, who changed it, when, from which address, and with which browser. That includes account creation and deactivation, role changes, password resets, scenario visibility changes, billing changes, and staff access to a department. Departments can request an export of their own audit records.
Training files
Instructors and administrators can post documents and pictures for their department's members to read or look at. These files are kept apart from scenario images and handled this way:
- Private to the department. Sign-in and department membership are checked on every request, so someone removed from the roster loses access at once. A member can open a file only while its item is showing. Instructors and administrators can open it at any time, and so can our platform staff when supporting a department.
- Not kept by browsers or our content delivery network. Files are marked so that no browser or shared cache stores them. A picture's small preview may stay in that person's browser, and it is checked with the server each time it is shown.
- Checked by what they contain, not by their name. Only PDF, Word (.docx), JPG, PNG and WebP files are accepted. A Word document with macros, active controls, embedded objects, a remote template or a password is refused, and a Word document always downloads rather than opening on our site.
- Pictures are rebuilt. A picture is re-encoded when it is uploaded, which removes its location data and other metadata. PDF and Word files are stored exactly as uploaded, so any metadata in them stays there.
- Files are not scanned for viruses. The checks above reduce the risk from a harmful file and do not eliminate it.
- Files are not encrypted separately for each department. They sit on the same volume and in the same backup storage as other department data, and the access checks above are what separate one department's files from another's.
Backups and retention
- The database is snapshotted automatically to object storage. Thirty snapshots are retained, and older ones are removed on a rolling basis.
- Restores are tested, not assumed. A production snapshot is periodically restored and integrity-checked end to end. The most recent verified restore was 2 September 2026.
- Radio audio is deleted after 14 days. The written transcript is kept as part of the permanent training record, so a drill remains fully readable after the audio is gone.
- A deleted drill or scenario is recoverable for 30 days, then permanently purged along with its media.
- Training files are copied to object storage with the backups. A deleted training item is recoverable for 30 days, then permanently purged along with its file, and the file's backup copy is removed about 30 days after that. A file uploaded but never saved to an item counts as deleted after 7 days.
- Departments can request deletion of their data at any time. See the Data Processing Addendum for the contractual version of this.
Availability and change management
- Uptime is monitored externally and continuously. The service reports its own health, including database reachability, storage headroom, memory, and event-loop responsiveness, and that history is retained for 30 days.
- Every change is covered by an automated regression suite and an automated accessibility audit that must both pass before the change can be committed.
- Changes are deployed with a graceful handover: connected drills are told the server is restarting and reconnect automatically rather than being dropped.
- We do not currently offer a contractual uptime guarantee. We would rather say that plainly than publish a number we cannot stand behind. If your procurement process requires a service level commitment, contact us and we will discuss what we can actually commit to.
Subprocessors
These are the third parties that may process department data on our behalf.
| Subprocessor | Purpose | Data involved |
|---|---|---|
| Railway | Application hosting, database storage, backup storage | All department data |
| Cloudflare | DNS and content delivery | Network traffic metadata |
| Stripe | Payment processing and invoicing | Billing contact and payment details. Card details go directly to Stripe and never touch our systems |
| Resend | Outbound email (invitations, password resets, alerts) | Recipient name and email address |
| Zoho | Inbound and support email | Anything a person writes to us |
| Google Cloud | Street View and satellite imagery, dispatch speech synthesis, AI scene generation, radio transcription | Addresses looked up, dispatch text, scene photographs, and radio audio submitted for transcription |
We will give reasonable advance notice before adding a subprocessor that processes department data.
What we do not do
- We do not sell department data, and we do not share it with anyone except the subprocessors above.
- We do not run advertising, third-party analytics, or tracking scripts. Our marketing pages count anonymous daily totals with no cookies and no visitor identifiers.
- We do not use department scenarios, drill records, or radio recordings to train our own models.
Reporting a vulnerability
Email support@getsizeup.com with "security" in the subject. Tell us what you found and how to reproduce it. We will acknowledge within two business days. We will not pursue action against anyone who reports a genuine issue in good faith, does not access data beyond what is needed to demonstrate the problem, and gives us reasonable time to fix it before disclosing.
What we do not claim
We think it is more useful to be direct about this than to let a certification logo imply something untrue.
- Scene SizeUp is not SOC 2 certified. We are a small company and have not undertaken that audit.
- We are not FedRAMP authorized and are not suitable for federal systems requiring it.
- We do not process protected health information and are not a HIPAA business associate.
If your procurement requires any of the above, tell us early so nobody wastes time.