Fire-BidA flame inside an open two-tone circular arc.
Sign in

Security

Fire-Bid holds seniority, leave and shift bid information that people care about being right and being private. This page describes the protections that are in place today.

Last updated 09/30/2026

Sign-In

  • The first time you sign in, Fire-Bid emails a one-time link to the work address your department has on file. Opening it asks you to set a password, and that password is how you sign in from then on.
  • If you forget it, Fire-Bid emails you a link to set a new one. That link is single-use and expires.
  • An administrator can issue you a temporary password. It works for one sign-in, expires after 7 days, and must be replaced with a password of your own at that sign-in.
  • Only an email address your department administrator has already put on file can be used to sign in. There is no self-registration.
  • The public demo is separate: an access code the operator issues signs a visitor into one of three fixed accounts (an administrator, a firefighter and a chief) in a fictional department, which holds no real personnel.
  • Pages that show personnel information require a valid session; signed-out visitors are redirected to the sign-in page. The one exception is a mock bid its maker chooses to share: anyone with its link can read it. It shows the maker's name, the shift and bid names, the colleague guessed for each seat and, once the real bid is complete, whether each guess was right.

Who Can Reach What

  • Access is checked on the server, and again in the database. Every signed-in page and action that reads or writes department or personnel records checks the signed-in account's role and department on the server first. Row-level access rules inside PostgreSQL also refuse a request that reaches the database directly with a signed-in account's own credentials, whatever the interface did or did not show.
  • Your own records stay yours. Regular accounts can read their own vacation selections, their own balance record, and their own balance-check calculations, not other people's. This is verified by direct testing against the database, not just by inspection.
  • Administrator actions require an administrator. Every administrative operation re-checks the caller's role on the server before doing anything, so a request sent directly to the server by a non-administrator is rejected.
  • Departments are separated. Department-owned records carry the department they belong to, and access rules restrict reads and writes to the requester's own department. The same department separation applies to Vacation Bid and Shift Bid.

Audit History

Administrative changes (balance adjustments and corrections, bid open/close, standby promotions, manual vacation changes, role changes; on Shift Bid, each shift's bid starting, seat assignments, changes to who holds a seat, and turn corrections) are written to an audit record that captures who made the change, what changed, when, which department it affected, and the reason given. When the operator enters a department, entering and leaving are recorded, and a change of those kinds made while inside is recorded the same way, marked as the operator's, and copied to a separate operator log. What the operator only reads is not recorded. Vacation picks and passes, and Shift Bid seat takes, removals and admin changes, are recorded in Change History, where nobody in the department can edit or delete an entry, with who acted and when.

That history cannot be changed entry by entry. Nobody in a department, administrators included, can edit or delete an audit entry, and the database refuses a deletion even from an administrator account; this has been confirmed by direct testing. The operator can delete a whole department, which removes its audit history with the rest of its records, as the schedule under Retention describes; that deletion is recorded in the operator log.

Audit records are kept for as long as the department uses Fire-Bid, and are deleted with the rest of its data on the schedule under Retention on the Privacy page.

Backups and Recovery

  • A copy of the database is taken nightly and stored outside the hosting provider, in a private Cloudflare R2 bucket that no part of the application can read. The bucket carries a location hint of western North America, which Cloudflare treats as a preference, not a guarantee. It holds the application's records and the sign-in accounts. It does not hold uploaded issue-report screenshots, the database's permission grants (recorded separately in the code repository), or the hosting configuration's secrets. Each copy is checksummed on the way in, and the job fails loudly rather than appearing to succeed with nothing in it. The 30 most recent copies are kept, and a separate check runs every day and emails the operator if the newest copy is more than two days old.
  • Restoring from one of those copies has been rehearsed, not assumed. On 08/14/2026 a real nightly copy was restored onto a separate PostgreSQL server and checked: the file matched its checksum, every table, access rule, function and constraint in it came back, and every row count and integrity check matched the original. The sign-in accounts were restored the same way on 08/16/2026.
  • A restore is not how a problem during a bid gets fixed. If something goes wrong while a bid is running, an administrator or the operator pauses it first, which holds everyone's place and advances nothing. The correction is then made in place, and logged. Restoring a backup would discard picks people have already made, so it is a last resort for damage that cannot be repaired any other way.

Fire-Bid does not claim that a complete rebuild of the running service has been rehearsed end to end. What has been tested is described above, and no more.

Connections, Hosting and Encryption

  • The application runs on Vercel, in its Washington, D.C. region (iad1). The database and sign-in service are Supabase's managed PostgreSQL, in the AWS US East (Ohio) region (us-east-2).
  • Traffic between your browser and Fire-Bid is encrypted using HTTPS/TLS, and browsers are instructed to refuse unencrypted connections to the site for two years, subdomains included.
  • Supabase states that all customer data it hosts is encrypted at rest with AES-256 and in transit with TLS. That is the provider's control; Fire-Bid adds no encryption of its own to the stored data.
  • Fire-Bid sends browser security headers that restrict where page content may be loaded from, prevent the site from being embedded in another site (clickjacking), and stop signed-in pages from being stored in shared caches.
  • Privileged database credentials are used only by server-side code and are never sent to the browser.

Infrastructure Providers

Fire-Bid runs on managed infrastructure rather than self-managed servers. The certifications below belong to those providers and describe their platforms; they are not certifications of Fire-Bid itself:

  • Supabase provides Fire-Bid's managed PostgreSQL database and sign-in infrastructure. Supabase reports SOC 2 Type 2 compliance and ISO 27001 certification for its platform.
  • Vercel hosts the Fire-Bid application and provides HTTPS/TLS termination and content delivery.

Fire-Bid has not itself completed SOC 2, ISO 27001, HIPAA, CJIS, or FedRAMP programs, and does not claim to have done so. Using certified infrastructure is not the same as being certified.

Reporting a Vulnerability

If you believe you have found a security problem in Fire-Bid, please report it rather than testing it against a live department's data. Send details to contact@fire-bid.com. What to report, when you will hear back, and the limits of good-faith testing are in the Vulnerability Disclosure Policy. See also the Contact page.

Fire-Bid is operated by James Bone. The same address is published for automated tools at /.well-known/security.txt.

Technical Notes

  • Hiding a button is not a security control. That is why every action checks the caller on the server, and why the database carries its own access rules as a second check.
  • Certified infrastructure is not the same as a certified product, and this page does not blur the two. Every certification named above belongs to a provider and is labeled as one.
  • Each statement on this page has a row in a claims register that records its evidence, and an automated check that runs on every change to the site fails if the wording of a withdrawn statement appears on it again.