Privacy Policy

1. Who is responsible for your data

The Service is operated by Tech Things, LLC, a Louisiana limited liability company ("Provider", "we"). Each law-enforcement agency that uses the Service (an "Agency") decides what is entered, who may see it and how long it is kept. For the content of bulletins and the accounts of its personnel, the Agency is the data controller and Provider is its processor, acting on the Agency's instructions given through the Service's settings and these terms. Provider is the controller only for the minimal technical and security data needed to run the Service.

2. What we collect

From officers and other authorized users

• Account information: your name, agency email address, role (officer, dispatcher, supervisor, admin), approval status, the date you accepted the terms, your officer profile (rank, first and last name, badge or unit number, phone, division), whether you may send Agency Notices, and your duty status (on or off duty, and when it last changed). Your Agency may enter this profile for you by import; you review it on first sign-in.
• Sign-in data handled by Google Firebase Authentication / Identity Platform: your Google or Apple account identifier or, for password accounts, your email and a hashed password. We never see your Google or Apple password.
• Device notification tokens for each phone or browser where you turn notifications on, with the platform and the time it was registered, so alerts can reach you.
• What you enter: bulletins (including drafts not yet sent), Agency Notices, photos and video you take or attach, documents, notes, sightings (with direction of travel and time seen if you give them), updates, closures, drawn search areas, and edits, all stamped with your name and the time. For each push the Service records how many devices it reached.
• Location only when you tap the GPS button, report a sighting with GPS, or use "Near You" or the incident map's "you are here" and directions, or when a street address or landmark you chose is converted to map coordinates. Near You and "you are here" are computed on your device and never sent to us. See Section 7.
• Activity logs: posts, edits, views of shared documents, shares, role changes, deletions, sign-in events, and every administrator export (records packets, indexes, backups) with its criteria, kept for the Agency's audit purposes.
• Technical data: IP address, browser or app version, operating system, and application-attestation tokens, used to secure the Service and diagnose problems. We do not use third-party analytics or advertising trackers.

About people who appear in bulletins

Agencies enter information about wanted persons, missing persons, persons and vehicles of interest, witnesses and others: names, dates of birth, descriptions, photos, addresses, vehicles, charges and narratives. This information is the Agency's record. Provider does not collect it from those people and does not use it for any purpose other than providing the Service to the Agency.

3. What is kept on your device

Photos taken in the app go straight to the Agency's secure storage and are not saved to the camera roll. Since October 30, 2026 the app keeps an offline copy on the device, so officers can still read bulletins without signal: what the feed shows (every active bulletin with its card photo and details) and the recent bulletins the officer opened, held in the browser's database store and protected by the device's lock and encryption. The copy is erased at sign-out, is never shared with other apps, and an Agency can turn it off for every device under Agency Settings → Rules when its policy forbids data at rest. Extra photos, video, posters and case packets are loaded live and are not kept. Anything an officer sends while offline waits on the device and goes to the Agency's server when signal returns. The sign-in session and the notification preference are kept as before.

4. How we use information

• To operate the Service: show bulletins to authorized users of the same Agency, send notifications, build posters and packets, place pins on maps, run follow-up timers, archive and purge on the Agency's schedule.
• To secure it: restrict access to the Agency's email domain and approved users, detect abuse, verify that requests come from the real app, and keep audit logs.
• To support the Agency: diagnose problems an administrator reports.
• To improve the Service using de-identified, aggregated operational statistics (for example, how many bulletins were posted per month) that identify no person or Agency.

We do not sell personal information, do not use it for advertising, and do not use bulletin content to train machine-learning models.

5. Who we share it with

• Your Agency. Everything you do in the Service is visible to your Agency's administrators and, for bulletins, to its authorized users.
• Recipients you choose. When you share a poster or packet or create a public link, the recipients you send it to receive that content. See Section 6.
• Partner agencies, only if and when your Agency's administrator enables sharing with a specific agency and you opt in.
• Service providers (sub-processors) acting on our instructions: Google LLC (Firebase and Google Cloud: hosting, database, file storage, authentication, push messaging, application attestation, all in the United States); Apple Inc. (push notifications to iPhones; Apple Maps for map display and address lookup); the U.S. Geological Survey National Map (public-domain map tiles used in printed packets; only your IP address and the map area requested reach it); and Google reCAPTCHA Enterprise (app attestation for the web). Each receives only what its function requires.
• Legal requirements. We may disclose information if required by law, subpoena or court order, or to protect the safety of any person or the security of the Service. Where lawful, we will refer requests concerning Agency Data to the Agency and notify it.
• Business transfer. If the Service is sold or transferred, information may transfer to the successor, who must honor this policy.

5a. Agency reference data, exports and administrators

Agencies also store reference data in the Service: divisions and bureaus with addresses and phone numbers, local landmarks, cities, charge tables and the agency's headquarters and leadership names. Administrators can export the agency's bulletins as case packets, public-records packets, spreadsheets, and the whole agency as a backup file. These exports contain personal information and are the Agency's records; the Agency decides what is released and redacts what the law requires. Administrators can also see which devices each user has registered for notifications (platform and time) so that missing alerts can be diagnosed, and can create review or demonstration accounts by username.

6. Public poster and packet links

An officer may create a link that opens a poster or case packet without a sign-in so it can be sent by text message or email. The link is a long random code that is never listed anywhere, is a snapshot of the document at the time it was created, works only while the bulletin is active, and shows "no longer active" once the Agency closes the case. Each opening is counted in the Agency's log. The decision to create and send such a link belongs to the officer and the Agency.

7. Location

The Service asks for your device's location only when you tap a GPS button on a form, report a sighting, or turn on "Near You" or open an incident map with Near You on. Near You compares your position to active bulletins on the device itself; the incident map shows your position and distance and can open Apple Maps for directions; none of this is stored or transmitted. When you mark yourself off duty the Service does not request your location at all. The fix you take is attached to that bulletin or sighting as coordinates and shown on the case map to your Agency's users. Typed addresses may be sent to Apple Maps to be converted to coordinates. The Service does not track officers' locations in the background and keeps no location history of you beyond the fixes you deliberately attach.

8. Notifications

Notifications are optional and controlled by you in the app's Settings and in your device's notification settings. Marking yourself off duty in Settings stops all pushes to your devices except Agency Notices, which you can also turn off while off duty. Turning them off or signing out stops them on that device. Notification content is delivered through Apple and Google push services.

9. Cookies and similar technology

The web version uses only what is needed to keep you signed in and secure (authentication session storage, application-attestation tokens, and the notification registration if you turn notifications on) plus a few preferences you choose, such as light or dark mode. We set no advertising, analytics or cross-site tracking cookies. Every item, what it is for and how long it is kept is listed in our Cookie Policy.

10. Retention and deletion

Bulletins follow the schedule the Agency's administrator sets: how long closed bulletins stay in the feed, when they are archived, and when photos and documents are purged (on archive or after one year, by default). Public links stop working when a bulletin closes. Audit logs are kept for the Agency's records. Account records are kept while you are an authorized user and removed when your Agency removes you. Device tokens are removed when you sign out, turn notifications off, or the platform reports the device gone. When an Agency stops using the Service its data is deleted within a commercially reasonable period unless the law requires otherwise.

11. Security

Data is encrypted in transit and at rest on Google Cloud. Access requires sign-in with an account on the Agency's email domain and, where the Agency chooses, administrator approval. Every read and write is checked against security rules that enforce agency boundaries and roles. The Service verifies that requests come from the real app, sets strict browser security headers, can sign users out after inactivity on shared desks, and logs administrative actions. No system is perfectly secure; if you believe your account or the Service has been compromised, contact your Agency administrator and us immediately.

12. Your choices and rights

If you are an officer or other authorized user, your Agency controls your account. To access, correct or delete your account information, or to ask questions about how your Agency uses the Service, contact your Agency administrator. You can turn off notifications and revoke location permission at any time in your device settings. Depending on where you live, you may have additional rights under state or national privacy law; we will help your Agency respond to any request you make, and you may also contact us directly.

13. Members of the public

If you are not an Agency user and believe information about you appears in a bulletin, poster or packet, please contact the law-enforcement agency that issued it; it controls that record and is the proper party for correction, public-records and legal requests. Provider will forward any request it receives to the Agency concerned. Provider does not itself make decisions about whom an Agency lists.

14. Children

The Service is for law-enforcement personnel and is not directed to children; we do not knowingly create accounts for anyone under 18. Agencies may enter information about missing or endangered minors in the course of their duties; that information is the Agency's record and is handled under the Agency's policies and the protections above.

15. Where data is processed

The Service is hosted in the United States. If you access it from elsewhere, your information is transferred to and processed in the United States.

16. Changes

We may update this policy. We will post the new version here with a new effective date and, for material changes, notify Agency administrators through the Service.

17. Contact

Tech Things, LLC, Active BOLO · hello@techthings.net · activebolo.com