Privacy Policy

Private by Default. Lawful When Required.

Signal Public Safety is built for agencies that handle operational, personnel, training, and healthcare-adjacent data. We collect as little as we can, use it for narrow purposes, do not sell it, and preserve the ability to comply with valid legal and regulatory obligations.

Last updated: October 11, 2026

Privacy Posture

Ad TrackingNo Third-Party Pixels

CCPA Sale/ShareNo

Customer PHIBAA-Governed

Legal RequestsValid Process Required

Plain-English Summary

What We Will and Will Not Do.

Signal Public Safety is operated by Signal Public Safety, LLC, an Ohio limited liability company.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not put third-party advertising pixels on this public site.

We use data to run the service. That includes demo follow-up, account access, product security, agency support, billing and administration, audit logs, backups, and compliance.

We can comply with law. If we receive valid legal process, regulatory instructions, a contractual duty, or an emergency request that meets the law, we may preserve or disclose only what is required.

Notice at Collection

Information We Collect.

This section describes categories collected in the past 12 months and the reasons we collect them.

CategoryExamplesPurposeRetention
IdentifiersName, email, phone, agency, role, account IDsDemo follow-up, account access, support, security, customer administrationFor the relationship, then as needed for legal, audit, backup, and dispute purposes
Internet or network activityIP address, request metadata, security logs, device/browser signalsSecurity, abuse prevention, diagnostics, availability, incident investigationLimited operational windows unless needed for security, legal, or audit reasons
WatchDesk product analyticsProduct-use events and account-derived identifiersUnderstand how WatchDesk features are used and improve the productSubject to the Security and Retention terms below
Customer and professional dataAgency affiliation, title, department role, training or roster context entered by a customerProviding product features, permissions, training, scheduling, reporting, supportControlled by the customer agreement and product retention settings where applicable
Operational public-safety dataCAD context, protocol activity, reports, messages, policy acknowledgments, schedules, audit recordsProviding the contracted product modules and agency workflowsControlled by customer settings, operational need, legal requirements, backups, and audit obligations
Sensitive personal informationAccount credentials, precise role/access permissions, protected health information when a customer uses a product for PHIAuthentication, authorization, security, contracted healthcare/public-safety workflows, legal complianceOnly as reasonably necessary for the permitted purpose, customer agreement, law, security, and audit
CommunicationsDemo messages, support requests, administrative email, customer instructionsResponding to you, supporting the service, maintaining business recordsFor the relationship, then as needed for legal, audit, backup, and dispute purposes

Sources include you, your agency or organization, authorized users, product activity, public-safety systems connected by a customer, security logs, and service providers that help operate Signal.

We collect WatchDesk product-use events for product analytics, including events associated with identifiers derived from your Signal ID account.

Purpose Limits

How We Use Information.

Run the Products

Authenticate users, enforce agency scope, deliver product features, maintain audit logs, provide support, and operate backups.

Improve the Products

Measure how WatchDesk features are used to understand product use and improve the product.

Secure the System

Detect abuse, troubleshoot errors, investigate security events, prevent unauthorized access, and preserve evidence when necessary.

Communicate

Respond to demo requests, support messages, customer administration, product updates, and legally required notices.

Comply

Meet contractual, HIPAA business-associate, tax, accounting, public-safety, litigation, regulatory, and legal-process obligations.

For GDPR purposes, our lawful bases may include contract performance, legitimate interests in operating and securing the service, consent where requested, legal obligations, and vital interests or public-interest obligations in narrow emergency or public-safety contexts.

Disclosure Boundaries

When Information Leaves Signal.

We disclose personal information only to the extent needed for the service, the customer relationship, security, compliance, or the law.

  • Customer-directed access: agency administrators and authorized users may see data within their permitted organization, role, and department scope.
  • Service providers: infrastructure, hosting, email, security, backup, logging, and support providers may process information under contractual limits.
  • SignalAI questions: In WatchDesk, questions you choose to ask, recent conversation history, and recent dispatch information available to your agency, including incident locations and radio summaries or transcript excerpts, may be sent to Amazon Bedrock to answer your question.
  • Radio and dispatch: WatchDesk may send radio audio, transcripts, and dispatch details such as call type, location, incident description, and assigned units to Amazon Bedrock to transcribe radio traffic, extract dispatch information, and create radio summaries and briefings.
  • Common Hazards: For WatchDesk Common Hazards analysis, property addresses, coordinates, public-record facts, and property imagery may be sent to Amazon Bedrock.
  • Other product AI features: Some features in other Signal products send content you submit or generate (for example images, scripts, voice, or report text) to AI providers such as OpenAI, Google, ElevenLabs, and Runway to produce the result you requested. Radio and dispatch processing described above is separate.
  • Legal and safety: courts, regulators, law enforcement, public authorities, or emergency responders may receive information only when the request meets the legal standard or an emergency exception applies.
  • Business changes: information may transfer as part of a merger, financing, acquisition, reorganization, or asset sale, subject to confidentiality and applicable law.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not use sensitive personal information to infer characteristics for advertising.

HIPAA and Healthcare Data

Business-Associate Posture, Not Hand-Waving.

Signal Public Safety is not your healthcare provider and this policy is not a HIPAA Notice of Privacy Practices for a covered entity. When a covered entity or business associate customer uses Signal in a way that creates, receives, maintains, or transmits protected health information, we handle that PHI under the applicable customer agreement and Business Associate Agreement.

Under a BAA, we use or disclose PHI only as permitted by the BAA, the customer, and law; apply administrative, technical, and physical safeguards appropriate to electronic PHI; require appropriate downstream assurances from subcontractors; report reportable security incidents or breaches to the customer; and assist the customer with HIPAA duties where the BAA requires it.

The public demo form must not be used for patient names, protected incident details, Social Security numbers, medical record numbers, or other PHI. Customer production workflows should use the secured product surfaces configured for that agency.

Your Rights

California, GDPR, and Other Privacy Requests.

Depending on where you live and how you interact with Signal, you may have rights to know/access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent, opt out of sale/share or certain profiling, limit sensitive personal information, and avoid discrimination for exercising privacy rights.

California residents can request the categories or specific pieces of personal information collected, the sources, purposes, categories of disclosures, deletion, correction, opt-out of sale/share, and limitation of sensitive personal information where the law applies. Because Signal does not sell personal information or share it for cross-context behavioral advertising, Global Privacy Control signals are treated as opt-out signals for any future sale/share activity.

For customer-controlled product data, we may need to route your request to the agency that controls the data. We will verify requests before acting and may keep information when needed for security, legal compliance, contractual obligations, audit records, backups, or another permitted exception.

Text Messages

Texts Are Opt-In, and You Can Stop Them Any Time.

Signal Public Safety alerts cover open shifts from Signal Schedule and dispatch backup alerts from WatchDesk. Signal ID also sends a verification code when you request enrollment. Recurring work alerts require department membership and verified consent. We use your mobile number and consent record to verify your number, deliver these messages, honor your choices, and maintain consent and opt-out records. Message frequency varies. Message and data rates may apply.

To enroll, sign in to your own Signal ID account at id.signalpublicsafety.app and open Text Message Alerts. Alerts are off by default. Enter your mobile number, check the initially unchecked consent box, and select “Text Me a Code.” Enter the 6-digit code sent to that number and select “Turn On Text Alerts.” The verification text is sent when you request it; recurring work alerts begin only after verification. Consent is not a condition of employment or service.

Mobile numbers and text-message consent are not shared with third parties or affiliates for marketing or promotional purposes. Service providers may process this information only to operate and support the text-message program, including number verification, delivery, consent records, and opt-out handling. We may disclose information when required by law, as described below.

Reply STOP to the toll-free number that sent the message to block further program texts to your number. The carrier sends the STOP confirmation. You can also stop alerts for your Signal ID account by selecting “Stop Text Alerts” in Settings > Text Message Alerts. Stopping alerts in Settings displays confirmation on the page and does not send a confirmation text. For help with an opt-out request, email contact@signalpublicsafety.app with the subject “SMS Opt-Out.”

Reply HELP for information about Signal Public Safety alerts and how to contact support, or email contact@signalpublicsafety.app for assistance.

See our Text Message Alerts terms for program details, help, and cancellation instructions.

Stopping text alerts does not turn off app push or email notifications. Texts are supplemental and may be delayed or not delivered. Always follow your department's approved dispatch and paging procedures; do not rely on SMS alone for dispatch.

Security and Retention

Serious Controls with Honest Limits.

Signal uses HTTPS, access controls, scoped roles, secure session cookies, password hashing, encryption for sensitive product data, audit trails, backups, monitoring, and operational hardening. No system can promise perfect security; our obligation is to keep reducing risk, detect problems quickly, and respond responsibly.

We retain information only as long as reasonably necessary for the purposes described in this policy, customer agreements, product settings, legal obligations, audits, backups, dispute resolution, and security. Backup copies age out on their normal cycle unless preservation is required.

Contact

Privacy Requests and Questions.

Email contact@signalpublicsafety.app with the subject line "Privacy Request." Include your name, email, agency if applicable, the right you want to exercise, and enough context for us to verify and route the request. Do not include PHI in email unless we have directed you to a secure intake channel.

EU/UK/EEA individuals may also contact their local data protection authority. California residents may use the same email to exercise CCPA rights or to have an authorized agent submit a request, subject to verification.