SMS Messaging Consent & Opt-in Practices
Last updated: 2026-08-16
This page describes how officers opt in to SMS messaging from Patrol Trainer. For how we handle data and the full messaging terms, see our Privacy Policy and Terms & Conditions:
Consent to receive SMS is given directly to Patrol Trainer and the officer’s employing agency. Mobile opt-in information and messaging consent are never shared with third parties or affiliates for marketing or promotional purposes, and are never sold.
About Patrol Trainer
Patrol Trainer, a service of P4 Security Solutions LLC, is a workforce training and communications platform used by public safety agencies and private security firms to deliver compliance training, de-escalation scenarios, and operational broadcasts to their officers. Each agency that uses Patrol Trainer collects SMS consent independently from its own officers; Patrol Trainer is the technical platform that records and enforces those opt-ins on the agency’s behalf.
Who sends, who receives
- Sender: the supervisor (or designated administrator) of the officer’s employing agency, sending from a number provisioned for that agency on the Patrol Trainer platform.
- Recipient: officers and employees of that same agency whom (a) a supervisor has invited by name and mobile phone number, (b) the supervisor has attested SMS consent for — a consent record written with IP, user-agent, and timestamp before the first text — and who (c) can opt out at any time by replying STOP or by toggling SMS off in their account settings. Officers sign in with their mobile number and a one-time code; no password or email is required.
- No third-party messaging: phone numbers and consent records are never shared, sold, or used for marketing by Patrol Trainer or by any third party. Consent is scoped to the specific agency the officer works for.
Opt-in flow
The complete consent flow inside Patrol Trainer. Officers are invited by their agency supervisor, who attests SMS consent at invite time; the officer signs in with their mobile number and a one-time code and can opt out at any time by replying STOP or from the in-app account settings page.
Supervisor invites the officer and attests SMS consent
A supervisor invites an officer by entering their first name, last name, and mobile phone number. To invite by mobile number the supervisor must affirmatively attest that the officer has agreed to receive SMS — the required checkbox is unchecked by default, and the verbatim consent language it carries is snapshotted to the officer’s consent record with the IP address, user-agent, and timestamp before the first text is ever sent. The invitation itself is then delivered by SMS to that number.
Invite officer
Officer signs in with their mobile number and a one-time code
The officer signs in by entering their mobile number and the one-time code texted to them — no password or email is required. The officer can opt out of SMS at any time, either by replying STOP to any message or by toggling SMS off at /account; opting out records a revocation on the same consent row and stops all outbound SMS other than transactional login codes. Login one-time codes are always delivered so the officer can still access their account.
Officer modifies or revokes consent any time (in-app account settings)
After signing in, every officer has access to /account where they can change their phone number, opt back in to SMS, or revoke SMS consent. Toggling SMS off immediately stops all outbound SMS to the officer and creates a revocation record on the same consent row (preserving the audit trail). The opt-out also fires when an officer replies STOP to any received SMS - carrier-level handling is enforced by Twilio.
Phone & notifications
You sign in with this number and get supervisor SMS broadcasts here. Standard message and data rates may apply. You can opt out of broadcasts anytime — instantly via reply STOP, or by toggling this off. Sign-in codes are always sent.
US numbers only. This is your sign-in number.
Checking this box authorizes your agency to send automated SMS to the number above, including supervisor broadcasts. A timestamped record of this consent is saved whenever you turn it on or off. Consent isn’t required to use the platform — reply STOP to any message to opt out instantly.
How officers opt in - in detail
Officer consent is captured when the employing agency supervisor attests written consent while inviting the officer. The officer can opt out at any time by replying STOP or from their account settings. Consent is always affirmative and is never a condition of employment.
Supervisor attestation at invite
A supervisor invites an officer by entering their first name, last name, and mobile phone number. To invite by mobile number, the supervisor must affirmatively attest that the officer has agreed to receive SMS from the agency. That attestation writes a consent record — with the verbatim language below, the IP address, user-agent, and timestamp — before the first text (the invitation itself) is sent. The invitation is then delivered by SMS to that number.
Verbatim consent text recorded
“I consent to receive automated SMS text messages from [Agency Name] at the phone number I provided, including operational notifications and broadcasts from my supervisor. Message and data rates may apply. Message frequency varies. Consent is not a condition of employment. I can opt out at any time by replying STOP to any message, or by toggling SMS notifications off in my account settings.”
[Agency Name] is replaced at runtime with the officer’s actual employing agency. The exact string is snapshotted and stored alongside the consent record (IP, user-agent, timestamp).
Officer sign-in and opt-out via STOP or the account page
The officer signs in with their mobile number and a one-time code — no password or email. The officer can opt out of SMS at any time, either by replying STOP to any message or from /account. Opting out creates a revocation record on the same consent row and immediately stops outbound SMS — other than transactional login one-time codes, which are always delivered so the officer can still access their account.
What kinds of messages are sent
SMS messages sent through Patrol Trainer fall into a small set of operational categories:
- •Account & verification - the officer’s invitation to the platform and the one-time login codes used to sign in. These are transactional and are sent regardless of marketing opt-in status so the officer can always reach their account
- •Supervisor broadcasts - operational updates, schedule changes, roll-call adjustments, safety alerts sent by the officer’s supervisor
- •Training reminders - notifications about assigned training that is due, overdue, or newly assigned
- •Compliance attestation deadlines - notifications when a periodic compliance module needs re-attestation
No marketing, no promotional content, no third-party offers. SMS is operational only. Officers will not receive promotional messages or messages from any party other than their own employer’s authorized supervisor.
Message frequency
Frequency varies by agency and by individual officer’s schedule and training assignments. Typical volume is 2-10 messages per officer per month. Periods of heavy operational activity (shift restructurings, large broadcasts, training deadlines) may temporarily increase that. Standard message-and-data rates from the recipient’s wireless carrier may apply.
How officers opt out
Officers can opt out at any time using any of the following methods. All take effect immediately and all are logged as revocation events on the same consent record:
- STOPReply STOP (or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT) to any received SMS. Carrier-level opt-out handling is enforced by the underlying messaging provider (Twilio).
- HELPReply HELP to receive an automated response with platform contact information and a reminder of opt-out instructions.
- UIToggle SMS notifications off on the
/accountpage after signing in. - ASKAsk their supervisor to disable SMS on their behalf. The supervisor edits the officer’s contact panel, which writes the same revocation record attributed to the supervisor for audit purposes.
Privacy & record retention
- Phone numbers are stored securely, access-controlled, and encrypted at rest at the storage layer, accessible only to the officer’s own agency supervisors and the officer themselves. They are never shared with third parties, never sold, and never used for any purpose other than the SMS messaging described above.
- Consent records are retained indefinitely as a TCPA/CAN-SPAM compliance audit trail. Each record includes the snapshotted consent text, timestamp, IP address, user-agent, and (for revocations) the same metadata for the opt-out event.
- Tenant isolation: agencies cannot read each other’s phone numbers or consent records. Database- level row security enforces the boundary independently of the application layer.
Contact
For questions about Patrol Trainer’s messaging practices, this consent disclosure, or specific consent records, contact:
zwhitaker@p4secure.comFor opt-out assistance specific to YOUR agency, contact your direct supervisor or your agency’s administrator. They can disable SMS on your behalf and the revocation will be recorded with full audit metadata.