Privacy
Fire-Bid handles department account information and records used for Vacation Bid and Shift Bid, including rosters, ranks, seniority dates, qualifications, vacation balances and picks, seat assignments and audit entries. This page explains what information the system holds, why it holds it, and who can see it.
Last updated 09/30/2026
Who We Are
Fire-Bid is operated by James Bone. It is scheduling software licensed to a fire department. Your department decides who has an account, what your seniority record says, and how bidding is run. Fire-Bid processes that information on the department's behalf.
If you are a firefighter using Fire-Bid, your department, not Fire-Bid, is the right first stop for questions about your own seniority, balance, or bid results.
What Information Fire-Bid Holds
- Account information: your name and work email address, used to sign you in and to send bidding notifications.
- Department and shift: which department you belong to and which shift (A, B, or C) you work.
- Seniority information: hire date, classification, promotion date, and your seniority position, which determine your place in the bid order.
- Vacation and leave selections: the days you pick, whether they were approved or placed on standby, your standby position, and hours charged.
- Vacation balance information: the balance an administrator enters for you, the hours earned projected from it, and any correction an administrator makes, plus the calculation trail behind each check of whether you have enough hours.
- Bid activity: whose turn it is, passes, any choice to give up all your turns for the year, and whether a shift's bid is paused for review.
- Shift Bid information, where your department uses it: your rank, rank seniority date and qualifications, the seat you hold or picked in each shift bid, and any mock bid guesses you make. A mock bid's guesses are private to you unless you share its link. Anyone with the link can read the shared page, which shows your name as its maker, the shift and bid names, the colleague you guessed for each seat and, once the real bid is complete, whether each guess was right. Once the real bid is complete, each mock bid's score, with the name of whoever made it, appears on your department's leaderboard; the guesses do not.
- Access: which of three kinds of access you hold, bidder (you take part in the bids), bid admin, and paging admin, and a record of each change: who made it, for whom, and when.
- Messages from your bid admin: when an administrator nudges you on your turn or sends an announcement to your shift or department, Fire-Bid keeps the message, who sent it, who it went to, when it was scheduled and when it was sent, and for each person whether it was sent by email and by push or why not (for example, that you have that kind of notification switched off).
- Pages, where your department uses it: each page anybody sends, with its subject and message as the sender wrote them, who sent it, who it was addressed to and who it went to (with their shift, rank and qualifications at the time), when it was scheduled, any edit or cancellation before it went, when it was sent, and for each person whether it was sent by email and by push or why not. Fire-Bid also keeps a record each time somebody reaches the department's daily limit on pages, and your own marks of which pages and replies you have read, which nobody else sees.
- Reply threads: when you reply to a page, a thread between you and its sender, with every message in it and when the thread was closed. If your department's administrators open one thread for review, Fire-Bid keeps who asked, who approved, the reason and the times.
- Help questions: when you ask the help box a question, Fire-Bid records who asked, when, how long the question was and whether it was answered, never the question itself.
- Administrative and audit records: a record of administrative actions such as balance adjustments, corrections, and bid changes, including who made the change and why.
- Notification preferences: whether you want notification emails, and the address to send them to.
- Browser push subscriptions: if you turn on push alerts, the browser gives Fire-Bid a subscription for that one browser on that one device, and Fire-Bid stores it along with the browser's description so you can tell your devices apart. It is not a phone number, it cannot be used to contact you anywhere else, and turning alerts off deletes it.
- Issue reports: if you use the in-app "Report an issue" tool, the description you write plus the page you were on, your browser type, up to the last ten error messages the page recorded in your browser, and an optional screenshot you choose to attach.
Fire-Bid does not ask for or use a phone number, and does not send text messages. Notifications go by email and by browser push, and nothing else.
Why This Information Is Used
The categories above, apart from help questions and issue reports, exist to run vacation and shift bidding: to establish the correct seniority and rank order, to check whether a requested block is covered by available hours, to enforce daily staffing limits, to check which seats a person can take, to notify you when it is your turn, and to give administrators an accurate record of what happened and why. Help question records and issue reports are used to support you and to fix problems with the software.
Pages, reply threads and their delivery and review records exist for a different reason: to carry your department's non-emergency messages to the people they are for, and to keep the department's record of what was sent, to whom, and what was done with it.
Fire-Bid does not sell your information, does not share it with advertisers, and does not use it to build advertising profiles.
Who Can See Your Information
- You can see your own account details, your own vacation selections, and your own balance information.
- Your department's administrators can see department-wide information, including rosters, seniority, balances, bid status, and audit history. This is what allows them to administer the bid.
- Paging admins, where your department names any, can see the names, ranks, shifts and qualifications needed to address a message, and the department's messages. They cannot see balances, picks, seats, the bid order or bid records.
- A message from your bid admin is seen by its sender, by the people it was sent to, and by your department's administrators. Whether it reached you, by email or by push, is seen by you and by them.
- A page is seen by its sender, by the people it went to once it has been sent, and by your department's bid admins and paging admins. The sender and those admins can see who it went to; the people it went to see only the group it was addressed to. The sender sees how many it reached; the admins see, for each person, whether it was sent by email and by push.
- A reply thread is read by its two people only: you and the page's sender. Your department's bid admins and paging admins can open one thread for review only when one of them asks, with a written reason, and a second, different one approves; from then on that thread is readable by all of the department's bid admins and paging admins. The review is recorded with both names, the reason and the time, and both of you see it on the thread. Until then the admins see only that a thread exists between the two of you, never what it says.
- Other members of your department can see staffing-level information needed to bid sensibly, such as how many people are already off on a given day and whose turn it is, and on Shift Bid, which person holds each seat.
- The operator, James Bone, can see every department and its people from the operator portal, and can enter any department with its administrators' powers to support it. Entering and leaving are recorded in that department's Change History and in the operator's own log, and a change of the kinds Change History records, made while inside, is recorded in both and marked as the operator's. What the operator only reads is not recorded.
- Issue reports are read by an account Fire-Bid sets aside for reviewing them, which sees every department's reports, screenshots included, with the name of whoever sent each.
- Other departments: records carry the department they belong to, and access rules checked on the server and in the database restrict reads and writes to your own department.
Your notification settings, including the address you choose, are shown only to you. Your department's administrators do see, for each message or page sent to you, whether it went by email and by push or why not, which can show that you have one kind switched off; the sender of a page sees how many people it did not reach. Balance details are limited to you and your department's administrators.
Service Providers
Fire-Bid uses these third-party providers:
- Supabase: managed database and sign-in infrastructure. Your account and department records are stored here.
- Vercel: application hosting and content delivery.
- Resend: delivery of notification emails, such as "it's your turn to pick."
- Anthropic: answers questions typed into the help box. It receives the question as typed, up to three earlier questions and answers from the same conversation, and Fire-Bid's own written help; Fire-Bid sends it none of your department's records.
- GitHub: runs the nightly backup job, which copies the database into a private storage bucket outside Supabase, described on the Security page. Nothing in the application can read that bucket.
- Cloudflare: holds that bucket. The nightly backup copies are stored in Cloudflare R2, with a location hint of western North America, which Cloudflare treats as a preference, not a guarantee. Cloudflare Email Routing also forwards mail sent to contact@fire-bid.com to the operator's inbox.
Browser push alerts are delivered by the push service your own browser uses (Google, Mozilla, or Apple, depending on the browser). Fire-Bid hands them an encrypted message addressed to your subscription; they do not receive your name, your department, or your balance.
See the Security page for how information is protected in transit and at rest, and where it is hosted.
Cookies
Fire-Bid sets two kinds of cookie, both needed for the site to work. The first keeps you signed in. The second is set only if you make a mock bid: it remembers, in that browser, which mock bid guesses are yours so you can come back and change them. It is sent only to the mock bid pages, scripts on the page cannot read it, and it lasts up to 180 days. There is no advertising tracking, and no third-party analytics product is currently used, so there is nothing to opt into or out of.
Retention
Bidding, seniority, access, message, page, reply thread, delivery, review and audit records are retained for as long as the department uses Fire-Bid; a message, page or reply sent to or by somebody who has left stays as a department record, because they are operational records the department relies on. Audit history in particular is deliberately kept intact: nobody in a department, administrators included, can edit or delete an audit entry. The operator can delete a whole department, which removes its audit history with the rest of its records; that is how the schedule below is carried out, and the deletion is recorded in the operator log.
After a department ends its use of Fire-Bid, its administrator can keep using Export for 30 days. All department data is deleted 90 days after termination. Only the 30 most recent nightly copies are kept, so a copy normally rolls off within 30 days. Audit records are deleted with the rest. These deletions are carried out by the operator; nothing in the software deletes a department's data on a timer.
Issue reports and the record of help questions belong to the department and follow the same schedule. A contact form message is sent by email, through Resend, to the operator's mailbox; the application's own database keeps only the time and network address of each message, to limit how often the form can be used. A try to open the demo with an access code is recorded with its time, network address and whether it worked, to limit guessing; a try refused for too many attempts is not recorded. When the code is one the operator issued, the record also says which code, and for an accepted code which view was chosen. Each code is given to a named person or department, so the operator can see when and how often it was used and from how many networks, but not the addresses. None of these is tied to a department, and no schedule for deleting them has been set yet.
Vercel and Supabase keep their own request and sign-in logs, under their standard retention. Fire-Bid does not copy or export those logs.
Correcting or Removing Your Information
Most corrections (a wrong hire date, a wrong seniority position, an incorrect balance) are made by your department's administrator, who has the tools to make and log them. Start there.
For requests your department cannot resolve, or to ask what information Fire-Bid holds about you, use the contact route on the Contact page.
Changes to This Policy
When this policy changes, the date at the top of this page changes with it.
Contact
Privacy questions can be sent to contact@fire-bid.com.