Privacy Policy
Last updated: September 28, 2026
1. Who We Are, and Our Two Roles
SARGOS is operated by TASAR Software LLC, a Pennsylvania limited liability company. SARGOS is a coordination and logistics tool for search and rescue (SAR) teams: personnel, equipment, incident documentation, and a team operating picture. SARGOS supplements radio communications, 911, dispatch, and your agency's procedures. It does not replace them.
For your account (your login, profile, certifications, gear, preferences), SARGOS decides how data is handled and is your point of contact.
For your organization's operational data (incidents, subjects, clues, personnel records, GPS tracks), your SAR organization controls the data. It decides what is entered, who sees it, and when it is deleted. We process it only to provide the service, on the organization's behalf. If you are a search subject, a family member, or a witness and want data about you accessed or removed, contact the SAR organization that ran the operation. They control that record, and we act on their instructions. We route any such request we receive to that organization.
2. Data We Collect
Account and profile (from you)
Email address and password (passwords are handled by our authentication provider; we never see them in plain text), optional multi-factor authentication, display name, phone number, call sign, emergency-contact name and phone, profile photo, certifications and uploaded certificate documents, personal gear and loadouts, K9/handler records, notification preferences, and display settings. Sign-in with Google or Microsoft, where offered, shares your name, email, and profile basics from that provider.
Operational data (entered by your organization)
Incident records and locations, sector boundaries, team assignments, check-in/check-out times, incident logs, clue reports, ICS forms, equipment records, and search-subject records, which may include a missing person's name, description, photos, last-known position, and contact information for family and witnesses. Designated medical fields on subject and volunteer records are stored with an additional layer of field-level encryption and are not displayed in the product's interfaces at this time.
Walk-up volunteers (QR check-in)
Name, phone number, emergency-contact name and phone, affiliation, certifications, vehicle (optional), what you brought, how long you can stay, and a required safety-briefing acknowledgment. No medical information is asked for. No account is created. Ninety days after the incident closes, a scheduled job replaces your name with ‘Scrubbed Volunteer’ and removes your phone, vehicle and emergency contact; the incident log keeps its record that a named volunteer checked in and out, because it is part of the operational record.
Location data
Live responder positions are never stored on our servers: they are relayed in memory and are gone when the incident view closes. Live positions are visible to the people running that incident: its checked-in participants and command staff, including checked-in responders from a partner organization on an incident shared under Section 6. Recorded GPS tracks (uploaded, or recorded with your explicit, revocable in-product consent) are stored as part of the incident record. SOS/distress events capture the position, accuracy, and time of the signal. Positions and tracks are visible only to that incident's participants and command.
Integrity and legal records
An append-only, tamper-evident audit log of administrative and security-relevant actions (the acting user's email, IP address, and browser identifier are stored encrypted and separately purgeable), and records of your acceptance of our terms (version, time, IP address, browser identifier).
Device and technical data
IP address and browser identifier on requests (used for security, rate limiting, and abuse prevention), push-notification subscriptions per device, and the cookies and on-device storage described in Section 9.
3. What We Do NOT Do
- We do not sell or share personal information for advertising, and we run no advertising or third-party analytics technology: no ad networks, no tracking pixels, no session recorders.
- We do not combine your data with data acquired from other sources.
- We do not store live responder positions on our servers.
- We do not build analytics, models, or heat maps on subject or responder location data.
- We do not accept criminal-justice system data (CLEAN/NCIC); entering it is prohibited by our terms.
- We do not use your operational data for anything except providing the service.
4. Sub-Processors and Sharing
We use these service providers to run SARGOS, each engaged for the sole purpose of providing the service:
| Provider | Purpose | What reaches it |
|---|---|---|
| Supabase | Database, authentication, file storage | All service data; login credentials; sends account emails |
| Fly.io | Application server hosting (US) | All service data in transit; live positions in memory only |
| Vercel | Web application hosting (US) | Pages and data delivered to your browser |
| Cloudflare | Network security, bot protection, encrypted backups | Request metadata and IP addresses; the bot-check (Turnstile) receives your IP; encrypted database backups |
| Stripe | Payment processing (paid plans) | Organization name, the billing admin's email, and payment details you enter on Stripe's own pages (card data never touches SARGOS) |
| Mapbox | Map tiles, place search, directions, map images | Map tiles and styles; place-search text with the approximate map centre; walking-directions waypoints; and, for map images we render (incident thumbnails, printed ICS map panels), the incident's map pins: last-known point, initial planning point, command post, staging, subject last-known points and clue locations. Mapbox's standard map-load telemetry |
| USGS National Map | Topographic map tiles (US government service) | Map viewport coordinates |
| Resend | Application email (invites, notifications) | Recipient email addresses and message content |
| Sentry | Error monitoring, always on (see Section 9) | The error, where in our code it happened, an opaque account identifier, and Content-Security-Policy violation reports. If you use the in-app Feedback form, the text you type, the name and email you choose to give, and any screenshot you attach also go to Sentry. No cookies, no request bodies, no session recording |
| Cloudflare Turnstile | Bot check on sign-in, sign-up and password forms | Your IP address and browser signals go to Cloudflare to decide whether you are a person |
| Checkly | Uptime monitoring of our public pages | None of yours: it loads our public pages and a monitoring-only test account |
| Inngest | Background job processing | Job events referencing internal IDs |
| Browser push services (Google, Apple, Mozilla) | Push notification delivery | Your device's push endpoint; notification content is written to avoid personal data |
Map and weather data sources
When you open a map, your browser also requests public data straight from the agencies that publish it, sending only the map area you are looking at: USGS National Map (topographic tiles and imagery), Esri/ArcGIS Online services for FAA sectional charts and obstacles, PAD-US public lands, HIFLD cell towers and NIFC fire perimeters, PASDA (Pennsylvania imagery), and Iowa State University's Mesonet radar. Our server asks the National Weather Service (api.weather.gov) for the forecast and alerts at the incident's location rounded to about one kilometre. None of these receives your identity.
We may also disclose information when required by law (subpoena, court order), to protect life or safety, or in a business transition. If a public agency is your organization's authority, records may be subject to public-records laws that apply to it. No other parties collect personal information across other websites through our service.
We add or replace a sub-processor by updating this list; for a new sub-processor that will handle your organization's operational data we give organization administrators at least 30 days' notice by email. Write to legal@getsargos.com to be notified of every change.
5. How Long We Keep Data
The defaults below are enforced by scheduled jobs. Organizations that need a different window for their own records can ask us at legal@getsargos.com; self-service settings for these windows are not offered yet. Deletion timelines apply to active systems first. Encrypted backups expire on rotation (up to 12 months), are used only for disaster recovery, and if ever restored, deletions are re-applied.
| Data | Default |
|---|---|
| Account and profile data (name, contact details, certifications, gear, photos) | Kept while your account exists; removed when you delete your account (Section 8) |
| Walk-up volunteer name, phone, vehicle and emergency contact | Scrubbed 90 days after the incident closes (Section 2) |
| In-app notifications | 30 days after you dismiss them or they are superseded |
| Billing records | Kept by Stripe under its own terms; we keep the subscription state and invoice references for as long as tax and accounting law requires |
| GPS track attribution (who recorded it) | Removed 180 days after the incident closes; the coverage line itself is kept as part of the operational record |
| Mutual-aid visitor snapshots | Anonymized 180 days after the incident closes |
| Audit-log requester details (email/IP/browser) | Purged 365 days after the entry; the audit ledger itself is permanent |
| Incident records, subject records, logs, SOS events, audit ledger, terms acceptances | Retained as operational, safety, and integrity records; subject-record deletion is your organization's decision |
Some records are append-only by design and are not deleted by any self-service action: the audit ledger, incident logs, SOS events, and witness-contact logs. Records under a legal hold are not purged while the hold stands.
6. Mutual Aid and Partner Sharing
An organization (the “host”) may share a single incident with another SARGOS organization (the “partner”) it has an accepted partnership with. Sharing is per incident and does not give the partner access to any other incident, to the host's roster, or to any other part of the host's account. Partner responders never become members of the host organization.
What crosses between organizations
When a partner deploys one of its members to a shared incident, the host receives an operational subset of that person's record: their display name, phone number, active certifications, and the equipment they bring. Medical information, emergency contacts, email addresses, and the partner's own roster are not transferred. The subset is captured as a snapshot at the time of deployment. Activity the deployed person records on the shared incident (check-in and check-out times, status changes, assignments, GPS tracks recorded under the host's incident tracking consent, and their own activity-log entries) is part of the host's incident record.
Controller roles
The host organization is the controller of the incident record, including the rows describing partner responders on that incident. The partner organization remains the controller of its own member records. SARGOS acts as a processor for both organizations and does not use shared data for any purpose of its own. A request to access, correct, or delete a member record is directed to that person's own organization; a request concerning the incident record is directed to the host organization.
How access ends
Access ends at the earliest of: the deployed person checking out, the host revoking the share, the partner recalling that person, the incident closing, or the share reaching an expiry the host set. Ending is immediate: the next request the person makes is refused, and any open live connection is closed. After access ends, the person can no longer read the host's incident.
The deployment record
After a deployment ends, the partner organization retains a read-only record of its own people: who was deployed, their times and hours, the assignments they held, the tracks they recorded, and their own activity-log entries. It contains no data about the host's own responders or any other organization on the incident. The detail in this record follows the host's incident retention. If the host purges the incident, the detail goes with it and a summary of the deployment remains.
Record of the sharing itself
Every step (the partnership request and acceptance, the share and its level, each deployment, each change of level, and each ending) is recorded in the audit log of the organization that performed it, with the identifiers of the records involved and not the personal details of the people named in them.
7. Security
Data is encrypted in transit and at rest. Designated medical fields carry an additional layer of application-level encryption. Access is isolated per organization at the database level. The audit log is append-only and tamper-evident (hash-chained). Our application security posture is self-assessed against OWASP ASVS 5.0 Level 2. A summary is available to customer organizations on request. We offer a data-processing agreement to any organization that asks; write to legal@getsargos.com. We do not claim certification against any standard. Security researchers: see our vulnerability disclosure policy at /security.
If we confirm a breach of security that affects your data, we will notify affected organizations without undue delay and within 72 hours of becoming aware, notify affected individuals where the law requires it, and comply with the breach-notification laws that apply to us, including Pennsylvania's Breach of Personal Information Notification Act.
8. Your Rights and Requests
Self-service (in the product)
Export your account data (profile, memberships, certifications, gear, participation history) and delete your account. Account deletion anonymizes your operational history and removes your profile, certifications, gear, and photos.
By request
Send access, correction, or deletion requests to legal@getsargos.com. We log every request in a register.
How we verify you
The sensitivity of the data sets the bar: routine requests are verified by your authenticated session; requests touching contact details or history require re-authentication; requests touching precise location or medical data require strong re-authentication. Every irreversible deletion requires strong re-authentication and a typed confirmation in the product. Deleting your account takes effect immediately and cannot be undone; we do not hold it for a waiting period. Records that survive deletion are listed in Section 5 (append-only operational records, and your acceptance of our terms, which we keep with your account identifier removed). We do not accept identity documents by email. For data about people without accounts (subjects, family, witnesses), we cannot verify identity ourselves and route the request to the controlling organization (Section 1). A request that fails verification is declined, not partially fulfilled.
Timing
We aim to acknowledge within 7 days and resolve within 30. This is a service commitment we hold ourselves to, stated here so you can hold us to it too.
When we must decline
We may decline or defer requests that would alter append-only operational or evidentiary records, records under legal hold, another person's data, or records needed for an active operation (handled after the incident closes).
9. Cookies, On-Device Storage, and Signals
We use no advertising or cross-site tracking cookies, and no third-party analytics cookies of any kind. What we do use:
- Essential cookies only: sign-in session (two or three HttpOnly, Secure cookies; your session stays signed in on that device until you sign out or it is revoked; the cookies last up to 400 days and are refreshed on each request); a one-time sign-in helper used during the sign-in handshake (HttpOnly, minutes); active organization (HttpOnly, Secure, one year); a short-lived re-authentication ticket during sensitive changes (HttpOnly, 10 minutes, carries your account identifier); a record that we received your Global Privacy Control signal (one year); interface preferences: density and sidebar state (one year, readable by the page). Volunteers who open an incident link receive a 24-hour cookie that holds their volunteer session so a reload keeps them signed in; it is limited to the launch page. Theme is stored in your browser's local storage, not a cookie. These are required for the product to work, which is why we set them without asking and why the cookie banner is a notice rather than a choice: we set no cookie that a consent toggle could switch off.
- Error monitoring is always on, and is not cookie-based. SARGOS is used to coordinate life-safety operations, so an unreported crash during a live search is an operational failure, not an inconvenience. We rely on legitimate interests rather than consent, because switching crash reporting off for everyone who never answers a banner would leave us blind to faults in exactly the tool people are depending on. What the error reporter in your browser sends to Sentry is deliberately narrow: no cookies and no IP address, both disabled at the SDK; no request bodies, no query strings, no URL parameters, and no request headers other than content type, accept and user agent, all removed before a report leaves your browser; an opaque account identifier (a random ID, not your name or email); the trail of recent actions leading to the crash, with phone numbers and coordinates stripped out of it; and no session replay or screen recording. It does not track you, across sites or otherwise, and it is used only to find and fix faults. Content-Security-Policy reports and the Feedback form are listed in Section 4.
- Performance telemetry is a preference, not a cookie. Separately from crash reporting, we measure page performance (load and responsiveness timings) and one timing measurement on SOS delivery. Signed-in members can turn this off at any time under Settings, Privacy and data usage (“Help improve SARGOS”). It carries no incident data and no personnel information.
- On-device storage: the app stores your unsent field entries (check-ins, log entries, track recordings) in encrypted form on your device so work in poor coverage isn't lost; SOS and track buffers are cleared on sign-out and incident close, and a manual “wipe browser data” control exists in settings.
We do not sell personal information and we do not share it for cross-context behavioral advertising. Some browsers send a Global Privacy Control (GPC) signal, a universal opt-out of the sale and sharing of personal information. We read that signal and record that we received it. Because there is no sale or sharing to switch off, a request that carries GPC is served exactly like any other; we record it so we can demonstrate we honored it rather than ignored it. We treat Do Not Track the same way.
10. Children's Privacy
SARGOS is a tool for SAR organizations. Account creation requires you to be 18 or older; users and checked-in volunteers must be 13 or older. We do not knowingly collect personal information from children under 13, and if we learn we have, we will delete it. Records about minors (for example, a missing child's description entered by a team) are operational subject records controlled by the organization, per Section 1.
Members between 13 and 17 take part only through an organization, which is responsible for any consent their guardian must give under its own rules; SARGOS does not ask for a date of birth and relies on the organization and the member's own confirmation.
11. Where Data Lives
Service data is stored in the United States (our database and application servers run in US regions). Named exceptions: content delivery and TLS security run on global edge networks (Cloudflare, Vercel), encrypted backups are stored with Cloudflare R2, and error reports go to Sentry's US instance. We do not offer data residency guarantees beyond this description.
SARGOS is offered to organizations in the United States. If you use it from elsewhere, your data is transferred to and processed in the United States.
12. Changes to This Policy
The date at the top identifies the version you accepted. For material changes we will notify you and ask you to re-accept at your next sign-in. We will not change your rights by silently editing a webpage.
13. Contact
TASAR Software LLC · legal@getsargos.com · Support: support@getsargos.com · Security reports: see /security. Access and correction requests: Section 8 above.
Accessibility: we aim for WCAG 2.1 AA and are not yet audited against it; tell support@getsargos.com about any barrier you meet.
Postal address: available on request until we publish one.