Privacy Policy

This Privacy Policy describes how Shift Size Up (“we,” “us”) handles information when you visit shiftsizeup.com, use our contact form, or use the Shift Size Up product for a fire department. It is meant to match how the product actually works — not a generic template.

1. Who this covers

Website visitors who browse the marketing site or send a message through the contact form.

Department customers and members who sign in to the product. For a pilot or subscription, the department (city or agency) is typically the customer; individual firefighters and supervisors are end users under that relationship.

2. Information we collect

Marketing contact form. Name, email address, and message text you submit. We use that to reply. We do not sell it.

Account identity. Sign-in email (invite address), display name, role, and department membership needed to authenticate and scope what you can see.

Operational facts from department exports. Unit identifiers, incident or call numbers, timestamps, dispatch type or determinant codes, disposition and coded outcomes, units assigned, flags, capacity answers, and similar fields needed for overnight load and related screens. If a structured age column is present, we may store an age band only (pediatric / adult / senior), never the exact age.

Street name (no house number). We may store the incident’s street name with any house number removed. That is not a GPS track and not a full patient address.

Member-owned content. Personal notes and similar Me-only fields stay with the member. Notes are never copied onto a peer share, follow-up, or anniversary record.

Peer Team (when enabled for a department). Peer follow-up is a limited, department-scoped feature. Peers may see call type, dispatch time, street name (no house number), unit, and subject name — not the member note. Enrollment defaults on with opt-out. The subject chooses which Peer Team members are off their list. Anniversary notices, when used, go to the peer’s invite email and do not include name, street, or call type. Published Peer Team contact fields (name, published email, phone) are separate from the sign-in invite email.

3. What we do not collect (MVP)

The product is built so the MVP does not collect protected health information. We do not intend to retain dispatch narrative, call notes from CAD as patient narrative, house numbers, city, ZIP, coordinates, patient names or identifiers, exact patient age, vitals, ePCR content, or named destination facilities. We do not use GPS trackers or wearables. Imports go through quarantine, an allowlist strip (default deny), and a sanitized durable copy only; the quarantined original is deleted on a short TTL.

This posture is intended to keep the MVP outside HIPAA business-associate obligations for typical department CAD exports of the kind described in our product specs. Department counsel should confirm that for their own data set. If a department later wants narrative or ePCR-driven features, that would require a separate agreement and infrastructure appropriate for PHI.

4. How we use information

• Operate and improve the morning crew picture and member records
• Authenticate users and enforce department-scoped access
• Support Peer Team follow-up and anniversary notices where enabled
• Respond to contact-form messages and provide customer support
• Maintain security, diagnose issues, and meet legal obligations

We do not sell personal information. We do not use product data to rank named firefighters for command, and we do not put peer-support activations on command screens as a significance score.

5. Who can see what

Access is department-scoped. Command-facing views are built for crew and unit load, not for reading another member’s private note. Member-owned tables are partitioned so they are not read by command-facing queries. Peer Team surfaces are limited as described above.

6. Service providers and hosting

Primary hosting is in the United States: the application on Vercel; authentication and Postgres on Supabase (AWS). Contact-form email is sent through an email delivery provider (currently Resend). These providers process data only to provide their services to us. Supabase maintains SOC 2 Type 2 controls for its platform; Shift Size Up itself is not a SOC 2–certified product.

7. Cookies and sessions

Product sign-in uses secure session cookies (or equivalent session tokens) needed to keep you logged in. The marketing site does not currently load a third-party analytics pixel. If that changes, we will update this policy.

8. Retention, export, and deletion

Department operational data remains the department’s. We retain account and operational data for as long as the department relationship requires, plus a reasonable period for backups and legal holds. Departments may request an export of their operational data. Members who need account changes should contact their department administrator or us at the address below.

9. Security

We use HTTPS (TLS 1.2+) in transit. Database and object storage sit on infrastructure with encryption at rest. Passwords are stored as one-way hashes. Row-level security scopes rows to the signed-in member’s department. No method of transmission or storage is perfectly secure; we work to protect data with industry-standard controls appropriate to this product.

10. Children

The service is for fire-department professionals and is not directed at children under 13. We do not knowingly collect personal information from children.

11. Changes

We may update this policy as the product changes. The effective date at the top will change when we do. Material changes for department customers will be communicated through the pilot or contract contact.

12. Contact

Privacy questions: michael@shiftsizeup.com. You can also use the contact form on the home page.

Related: Terms of Service.