Privacy Policy
Effective October 18, 2026 · Last updated November 11, 2026
- AMP Global Connect is communications and dispatch software for public-safety agencies. You use it because your agency gave you an account.
- Your agency runs AMP on servers it controls. What the apps collect (location, radio and call audio, video, messages, sign-in details) goes to your agency's AMP system, not to us.
- Addresses and routes are worked out on your agency's system from its own map data, and speech is turned into text on your agency's system, with the few exceptions listed below.
- We do not receive, sell or share your information, we do not show ads, and the apps do not track you across other apps or websites.
- Your agency controls its records. Questions about a record, or a request to see or delete it, go to your agency.
1. Who we are
This policy covers the AMP Global Connect mobile apps (iPhone and Android), the in-vehicle app, the dispatch console for Windows, and the AMP Global Connect web services (together, "AMP"). AMP is provided by Amp Global Strategies LLC, 90 N Pioneer Ave, Shavertown, PA 18708, United States ("we", "us").
The AMPGS Dispatch text alerts (section 8) are operated by Real Time Mission Critical Strategies LLC, 55 Melody Lane, Farmington, NH 03835, United States. For text alerts, "we" and "us" mean Real Time Mission Critical Strategies LLC.
AMP is software licensed to public-safety agencies (police, fire, EMS, emergency communications) and other organizations ("your agency"). Your agency installs and operates the AMP system on servers it controls. The information described below is collected by and for your agency and stored on your agency's system. We, the maker of the software, do not run those servers and do not receive that information.
AMP apps do not come with a server address built in. When you first start one, you enter your agency's AMP server address or scan the setup code your agency gives you, and the app then works with that server.
Your agency decides who gets an account, what each person can see and do, which outside services its system connects to, and how long its records are kept. Your agency is responsible for that information under the laws that apply to it.
2. What the apps collect for your agency, and why
| Information | When | Why |
|---|---|---|
| Account details: name, username, role, agency, unit, work phone number, a PIN | Set up by your agency; you choose your own password and PIN when you enroll a device | To sign you in, show who is talking or responding, and give you the right access |
| Two-factor sign-in details: what is needed to check your authenticator app, security key or Windows Hello; your recovery codes (stored in scrambled form); a record of two-factor sign-ins; and, if you choose "remember", a token that remembers that browser or console for a set number of hours | Only when you set up or use two-factor sign-in | To confirm it is you, on top of your password. Fingerprint or face data used by Windows Hello or a security key stays on your device; AMP receives only the device's signed confirmation. |
| Device details: device type, app version, a device enrollment record and security certificate | When you enroll a phone, tablet or vehicle computer | To make sure only enrolled devices connect, and to secure the connection |
| Location (GPS) | While you are signed in and on duty. On iPhone and the in-vehicle app this includes while the app is in the background. The Android app collects location only while it is open on screen. | So dispatch and your team see where units are, send the nearest help, and find you in an emergency. You can stop it by signing out or going off duty. |
| Radio audio (push-to-talk) | When you press to talk, and when you listen to channels | To carry your transmissions over your agency's radio system. Radio traffic may be recorded and turned into text on your agency's AMP system for its radio log, as agencies are often required to do. |
| Voice commands, dictation and read-aloud | When you use a voice command, dictate, or have something read aloud | To understand the command or write the text. Speech is turned into text on your agency's AMP system (on the dispatch console, on the console computer itself), not by a cloud speech service. Read-aloud uses the AMP system's own voice or the voice built into your device, which works under the device maker's policy. One exception: when AMP's web phone page is opened in an ordinary web browser, its dictation and voice-search buttons and its read-aloud use the browser's own speech services (for example Google in Chrome or Apple in Safari), which receive that audio or text. On the dispatch console, spoken read-back of lookup results may use Microsoft's online voice service, which receives the text being read. |
| Phone calls, including 911 calls handled on the console: caller number and the location delivered with the call | When a call comes in or is made through AMP | To connect the call, show the caller's location to the call taker, and create the call record |
| Camera video | Only when you start a live video stream or your agency connects a camera | To share live video with dispatch and your team. Agencies that use AI video analysis may have video analysed for alerts, licence plates and, where the agency turns it on and the law allows, face recognition. Photos in agency records may be added to the agency's face-recognition database (see section 4). |
| Messages and pages, including text messages to and from phone numbers, which pass through the agency's SMS provider | When you send or receive them | To deliver them and keep them with the call they belong to |
| Incident and records data: calls for service, reports, people and vehicles, and queries to state and national criminal-justice systems | When users of your agency create or look them up | To run dispatch and records for your agency. Criminal-justice information is handled under your agency's security rules. |
| Service and security logs: sign-ins, failed sign-in attempts and the internet address they came from, connection times, errors, and which software files were downloaded and by whom | As the service runs | To keep the service secure and working, to block repeated password guessing, and to investigate problems |
The apps do not collect advertising identifiers, contacts, photos you have not chosen to send, or health data, and nothing is used to build marketing profiles.
Device permissions the apps ask for
- Location (on iPhone, including "Always"): unit location on duty, as above. The Android app explains this on its own screen before Android asks.
- Microphone: push-to-talk, phone calls, voice commands and dictation.
- Camera: live video, and scanning the setup code.
- Bluetooth (iPhone and in-vehicle app): pairing with an in-vehicle display or headset.
- Notifications: dispatch alerts, pages, messages and push-to-talk.
- Side key (Android): AMP can use a rugged phone's programmable side key as the push-to-talk button, through the phone's own key setting or, in some builds, an Android accessibility service. It is used only to detect that key and does not read screen content.
You can turn any permission off in your device settings; some features will then stop working.
3. How the information is used
- To run AMP for your agency: radio, dispatch, calls, maps, messaging, video and records.
- To secure the system: sign-in, two-factor checks, device checks, encryption, detecting misuse.
- For your agency's own legal duties, such as records requests, which your agency handles.
It is never used for advertising, and it is never sold or rented.
4. Who can see it
- Your agency and the people it authorizes, such as dispatchers, supervisors and other units. Agencies that work together through AMP's mutual-aid features may share call and unit information with each other, as their agencies set up.
- Outside services that AMP uses or that your agency connects, only to provide that service. Some are built into AMP and used unless your agency replaces them; others are chosen and contracted by your agency. They include:
- map and aerial-image services (for example Esri, OpenStreetMap and state GIS offices, or your agency's own map server), which receive your device's internet address and the map area being viewed. Your agency can change this list in AMP Settings;
- a map or address provider, only if your agency contracts one and turns it on in AMP Settings. It then receives only the kinds of information your agency chooses to send it, such as typed addresses or positions. Without one, AMP does not send unit positions or typed addresses to any address-lookup or routing service;
- phone carriers that connect calls, and conference-call services, which receive phone numbers and call audio;
- text-message (SMS) providers (for example Twilio), which receive phone numbers and message text;
- AI video analysis services, including face recognition and licence-plate recognition where your agency turns them on, which receive camera video and, for face recognition, photos and names from agency records;
- emergency-location data services for 911 calls, where your agency uses them;
- network services that help devices connect, such as public STUN servers (for example Google), which see only your device's internet address;
- public content-delivery networks (for example unpkg, jsDelivr and Google Fonts), from which some AMP web pages load common map code and fonts, and which see your device's internet address and the page that asked;
- software vendors' licence checks (for example the video server's), which do not include your information.
- Apple and Google deliver the apps and, on iPhone, push-to-talk notifications (which carry the channel or caller name), and provide built-in maps and directions when you open them, under their own privacy policies. When you tap OPEN IN MAPS, AMP hands only the destination to your device's maps app. The in-vehicle app runs in Google Chrome.
- Operating systems and browsers that AMP runs on (Microsoft Windows and Edge WebView2, Google Chrome, Ubuntu, Microsoft SQL Server) may send their own diagnostic and update data to their makers under their own policies, and a device's own location service may use nearby Wi-Fi and cell information to work out its position. AMP does not add your information to that data.
- Smart glasses: if your agency decides to test Meta smart glasses, and you pair them with the iPhone app, Meta's software on your phone handles that connection under Meta's privacy policy.
- Demonstration and trial systems: when Amp Global Strategies hosts a demonstration or trial system, we act for the agency and handle its information under this policy.
- Technical support: if your agency asks us for help, it may give our support staff temporary access to its system. That access is controlled by your agency, used only to fix the problem, and ends when the work is done.
- Legal reasons: agency records are often subject to public-records law and lawful requests, which your agency handles.
5. Where it is kept and how it is protected
Everything the apps collect is stored on your agency's AMP system, on servers your agency operates or chooses. Connections between the apps and that system are encrypted. Connections from your agency's system to outside services are encrypted where the service supports it; some phone-carrier and camera links use the provider's own unencrypted standards. Your agency's AMP server reaches the AI video analysis service over an encrypted (HTTPS) connection through the agency's AMP FIPS gateway.
FIPS 140 encryption
AMP includes a FIPS mode for agencies that handle criminal-justice information. With it turned on:
- phones, tablets and vehicle computers connect to the agency's AMP system through an encrypted IKEv2 VPN that ends at the agency's AMP FIPS gateway;
- criminal-justice traffic that leaves the agency's network, such as queries to state and national criminal-justice and motor-vehicle systems, is sent through that gateway;
- the gateway encrypts with a FIPS 140-validated cryptographic module: the OpenSSL 3.1.2 FIPS provider, NIST CMVP certificate #4985. The AMP Android app connects through the agency's FIPS gateway using the same OpenSSL 3.1.2 FIPS provider; on iPhone, the VPN uses Apple's built-in validated cryptography.
An agency may use its own FIPS-validated network equipment instead. Which option is in use is set by your agency.
Other protections
Devices must be enrolled and signed in, and access is limited by role. The apps sign in with short-lived access tokens, any password kept on a device is stored encrypted, and the apps can be locked with a PIN. Repeated wrong passwords or codes lock sign-in for a time. AMP also offers two-factor sign-in (an authenticator-app code, a security key, or Windows Hello), which your agency can require. The area where agency staff download AMP's Windows apps needs an AMP sign-in plus a one-time code from an administrator. No system is perfectly secure; your agency is responsible for securing its system and for telling you of a breach where the law requires it.
6. How long it is kept
Your agency sets how long its records are kept, usually under state records-retention laws. When your account is closed, your agency removes your sign-in and device enrollment; records you created for your agency stay with your agency under its retention rules.
7. Your choices and rights
- Location: sign out or go off duty to stop sharing, or turn location off in your device settings.
- Access, correction, deletion, closing your account: ask your agency's AMP administrator. The records are your agency's, and some cannot be deleted while the law requires them to be kept.
- Withdrawing consent: turn off a permission in your device settings, sign out, or remove the app. Removing the app deletes what the app stored on that device.
- Asking to delete your account and data: ask your agency's AMP administrator, or email tim.brown@ampgs.com with your name and agency. Because we do not hold your data, we pass the request to your agency and confirm to you when we have done so. Your agency deletes your account and data, except records it must keep by law.
- Questions about this policy or the software itself: contact us below.
8. Text message alerts (SMS)
AMPGS Dispatch text alerts are dispatch notifications sent by text message to agency staff and volunteers who sign up for them. The text alert service is operated by Real Time Mission Critical Strategies LLC, 55 Melody Lane, Farmington, NH 03835, United States, which sends the messages and is responsible for the text alert information described in this section. How to sign up and the full terms are on the Text alerts and Texting terms pages.
- What we use: your mobile number, the consent you gave and when, the messages sent to you, their delivery status, and any replies (such as STOP or HELP).
- Why: only to send you the dispatch notifications you signed up for, to honour STOP and HELP, and to keep a record of your consent.
- Who receives it: your agency, and the text-message provider and mobile carriers that deliver the messages, only to deliver them.
- No mobile information will be sold or shared with third parties for promotional or marketing purposes. Text messaging originator opt-in data and consent will not be shared with any third parties, except the providers that deliver the messages.
- Stopping: reply STOP to any message, or turn text alerts off in your AMP account. Reply HELP for help. Message and data rates may apply.
9. Children
AMP is a work tool for agency personnel. It is not meant for children under 18.
10. Changes to this policy
If we change this policy, we will post the new version here with a new date.
11. Contact
Amp Global Strategies LLC
90 N Pioneer Ave, Shavertown, PA 18708, United States
Email: tim.brown@ampgs.com
Text alerts (AMPGS Dispatch):
Real Time Mission Critical Strategies LLC
55 Melody Lane, Farmington, NH 03835, United States
Email: tim.brown@ampgs.com