Privacy Policy

Last updated October 17, 2026

This explains what OpsBoard stores, why, and who else is involved. OpsBoard is used by public safety agencies; the agency decides what goes on its board.

What we store

• Your agency's setup: its name, number, logo, home location, units, member roster (names, member numbers, certification), hospitals, radio feeds, cameras, phone numbers, and any hydrant and building pre-plan lists it adds.
• Logins: admins' and members' names and email addresses, passwords stored only as salted hashes, two-step sign-in secrets, and the names of the devices signed in.
• The board: what your people enter while working: calls, incidents, triage counts, transports (with tag numbers and age group, not names), events, operations, places pinned on the map, and a time-stamped log of what happened.
• Team positions, only while a phone shares them: during an operation, a team's phone can share where it is. While it does, it sends its position about every 20 seconds (sooner when it moves), with the team's name, the name it is signed in under, how accurate the fix is, and the path walked (its last 60 points). Everyone on your agency's board who has the operation open can see it, including partner agencies' guest devices invited to it and big-screen displays. It stops when someone presses the button again on that phone. Closing the page also stops it, but if the page is opened again during the same operation within 12 hours of turning it on, it starts again. Stopping replaces the position with a note that sharing has stopped. If the page is just closed, the last position and path stay with the operation on your board. Positions are kept like the rest of the board, and are not in the reports.
• Dispatch messages, if your agency turns them on: a private email address your dispatch centre can send call messages to. Each message is read for the address, town, cross street, what the call is, the call number, the time and the units. Names, phone numbers, email addresses, ages and comments are dropped, and the message itself is never saved. What is kept shows on your board as a message waiting, with who took or dismissed it. We keep at most the 40 latest, and clear out any older than three days each time a new one arrives.
• Emergency alerts sent on the board: the alert, where it is, who sent it, and any photo with it. We clear out alerts older than three days each time a new one is sent.
• Alerts to a closed app, if a device turns them on: that browser's push address and keys, with the device's name and the name it is signed in under, so an emergency alert (and, if the device chose it, a new dispatch message's address, town and call type) can reach it. The alert goes to the device encrypted, through the browser's own push service (Google, Apple, Mozilla or Microsoft), which can see that a message was sent but not what it says.
• An activity log: sign-ins and sign-outs, people joining, being invited or removed, settings changes, two-step sign-in and password resets, and plan and billing changes, with who did it, when and, for sign-ins, on which device. Admins can see it. Each entry is deleted after 90 days.
• Billing: your plan, your payments and receipts, and the Stripe customer and subscription that go with them. Card numbers go straight to Stripe; we never see or store them.
• Contacting us or trying the demo: what you put in the contact form (your name, title, email, phone, agency, its type, state, county, town, size and message) or in the demo form (your email, and your name and agency if you add them), with which demo you opened and when. The demo itself runs on your device, and nothing you enter in it is saved by us. Like the board, it sends places on its map to our relay to look up weather, flood zones and aircraft (see below).
• Stopping abuse: to limit how often the sign-up, contact and password-reset forms can be used, we keep a scrambled (one-way hashed) form of the network address that used them, for up to two days.

Patient names and other health information should never be entered. OpsBoard is built to work without them.

Why

Only to run OpsBoard for your agency: to share your board between your devices, to sign people in, to keep the record your final reports are made from, and to bill your subscription. If you gave your email for the demo or the contact form, we may write to you about OpsBoard; ask through the contact form, and we'll stop and remove it. We don't sell data or show ads. The boards and consoles use no tracking or analytics at all.

To help your agency, OpsBoard's owner can open your agency console as an admin. Each time is written in your activity log.

Places sent to look things up

To show weather, flood zones and aircraft, the board sends a place to our own relay, and the relay asks the public services. The place is the scene (or its landing zone), the operation or event, your agency's home, a spot someone taps on the map, or the middle of the map. Nothing else goes with it: no names, no sign-in, and nothing about patients or the call. The relay doesn't save them with your agency's data. To answer faster, Cloudflare's cache keeps the services' answers, looked up by place, for between a few seconds and 30 days (the longest is which county a point is in).

• Weather, tides, rivers, lightning and coastal currents: the board sends the place rounded to three decimal places (within about 100 metres, or 330 feet). The relay rounds it again, to about 1 kilometre (two-thirds of a mile), before asking the National Weather Service and NOAA (tides and currents, river gauges, nowCOAST, and NOAA's coastal radar currents).
• Aircraft: the place rounded to three decimal places goes to adsb.lol, a free public aircraft feed. If it doesn't answer, the OpenSky Network is asked for an area around the place, rounded to a tenth of a degree.
• FEMA flood zone, county risk and declarations: the place rounded to four decimal places (within about 10 metres, or 35 feet), because a flood zone can change from one lot to the next. The relay asks FEMA's flood map and the FCC's census lookup for that point, then FEMA's National Risk Index and OpenFEMA for the county only.

Counting visits to the website

The public pages (the home, contact, demo and sign-up pages) ask whether we may count visits, so we can tell whether anyone is finding the website. The counting script isn't loaded until you press Accept. If you do, Cloudflare Web Analytics counts your visit: the page, where you came from, your browser and your approximate country. It sets no cookies and doesn't follow you to other sites. No thanks is remembered. If you haven't chosen yet, a browser's Global Privacy Control or Do Not Track setting is taken as a no, without asking. You can change your mind any time with Visit counting in the footer of the home page.

Who else is involved

• Cloudflare hosts the website and our relay, and stores the data, encrypted in transit. Its Email Routing receives the messages sent to your dispatch address.
• Stripe processes card payments. It gets your agency's name and the email of the admin who subscribes.
• Resend sends our emails: invitations (the person's name and email, and the agency), password-reset links, receipts, and notices to us about new trials, demo sign-ups and contact-form messages (with what you wrote).
• The browsers' own push services (Google, Apple, Mozilla or Microsoft) carry alerts to a closed app, encrypted, as above.
• Pages load fonts from Google Fonts and code libraries from cdnjs (Cloudflare), which see your device's IP address.
• Map pictures come straight to your device, not through us: the map from the U.S. Geological Survey (and, in New Jersey, the New Jersey Office of GIS), the radar, cloud, lightning and current pictures from NOAA, and the flood zone pictures from FEMA. Those services see your device's IP address and the part of the map being shown.
• On a hazmat operation, Which way does it run? sends the exact release point, and eight points 250 feet around it, from your device straight to the U.S. Geological Survey's elevation service (epqs.nationalmap.gov). It happens only when someone presses it.
• Emergency department status is fetched by our relay from New Jersey's public divert board, so that service doesn't see your device.
• Cameras and radio feeds your agency adds load from wherever they're hosted. Buttons that open Apple Maps, Google Maps or Waze send the place to that service when you press them.
• Only if you press Accept on the website's visit-counting notice: Cloudflare Web Analytics, as above.
• OpsBoard sets no cookies. The board keeps its settings, and a saved copy of your board, in your browser's own storage on your device.

On your devices

Each device keeps a copy of its board so it works offline. Signing a device out, or removing it in the agency console, stops it from receiving new data; its saved copy stays in that browser until cleared.

How long, and your choices

We keep your agency's data while it uses OpsBoard, except where a shorter time is given above. An admin can change or remove most of it in the agency console. Ask us to delete your agency's account and data, or for a copy of it, with the contact form below.

Every night we save a backup of accounts, people and logins, plans and billing, contact and demo requests, and each agency's setup, hydrant and pre-plan lists. Live boards and the activity log are not in it. Each backup is deleted after 14 days, so after we delete an agency, its data can stay in a backup for up to 14 days. We can also download a backup as a file, for example before a big change. We keep the record of what an agency paid, for our accounts, and Stripe keeps its own records.

Contact

Use the contact form at opsboard911.com/contact.