How SentryIQ works

Two ways to participate in a stronger security network.

Network gives verified storage operators a place to report, collaborate, and see general local patterns. Protect adds secure cross-facility matching, authorized details, and tools for deciding what to do next.

Network · Free

Participate, contribute, and stay informed.

Network is the shared foundation of SentryIQ. Verified facilities can contribute useful information and coordinate with one another without paying for detailed cross-facility intelligence.

Record incidents and observations

Enter factual reports for your facility, including what happened, when, relevant identifiers, and approved supporting information. Choose what may be shared and with whom.

Ask the network for information

Send Requests for Information (RFIs) and respond to permitted requests from other facilities. Use Be on the Lookout notices (BOLOs) to share specific, time-limited concerns.

See local patterns

View privacy-safe network trends and basic Watch Brief summaries of behaviors and methods, when enough verified facilities contribute to support them.

Control participation

Membership is verified. Roles, facility assignments, sharing limits, and moderation govern who can contribute and receive information.

What Network does not include: detailed reports from other facilities, automated cross-facility exact-match alerts, facility watchlists, or the Prevention Action Center.

Protect · Paid

Connect the information and put it to work.

Protect includes everything in Network. It adds matching and follow-up tools to help your team recognize when permitted intelligence from another facility is relevant to your own.

Secure cross-facility entity matching

SentryIQ compares approved exact license plates, phone numbers, and email addresses across records your facility is authorized to use. This is a form of entity resolution: it connects records sharing an identifier, without assuming they involve the same person.

Match alerts and incident details

Review eligible cross-facility matches, the exact identifier that matched, and authorized source details. See what the records establish and what remains unknown.

Detailed Watch Brief and watchlists

See current, prioritized intelligence relevant to your facility. Keep approved exact identifiers on facility watchlists and review authorized matches as they arise.

Prevention Action Center

Turn a relevant alert or briefing into a review task. Assign follow-up, track its status, preserve context, and record what the team did and found.

Intelligence history and learning

Revisit permitted intelligence, the actions taken, and documented outcomes. Corrections and withdrawn information are reflected in current alerts and priorities.

Additional authorized sources

Where lawful access and redistribution rights exist, approved storage-relevant public-safety information can add context. Availability depends on the source and jurisdiction.

An important limit: paying does not unlock every facility's records. Every detailed match and report still depends on verification, sharing permissions, and facility access. An exact match is a connection between records, not proof of identity or wrongdoing. Compare the plans.

Getting information into SentryIQ

Manual reporting now. Approved integrations where available.

Your facility controls what information it submits. Choosing which reports and approved identifiers enter SentryIQ is separate from deciding what other facilities are allowed to see.

Manual path

Choose the reports and identifiers to submit

Staff select which factual observations and approved identifiers to enter. A facility may also upload a supported CSV export containing the records and fields it chooses. Imported records start as facility-private drafts for review, not automatic network disclosures. Arbitrary PDF parsing and AI extraction are not available in Phase 1.

Integration path · Pilot-dependent

Agree on what an approved integration receives

SentryIQ has a read-only ingestion framework for approved source systems. A live connection requires a verified vendor, documented rights, and a defined mapping of supported data fields. Integrations are configured by SentryIQ administrators; not every gate, access, or property-management API is connected today. Eligible connector records can be processed into facility-private intelligence.

Two separate decisions—not one blanket permission

Submitting information for matching does not automatically make that information visible across the network.

Choice 1 · Submit for matching

What information enters the system?

Your team chooses what to enter or import. With approved integrations, the supported source data is agreed and mapped beforehand. After a record is published within your facility, eligible exact identifiers can be compared securely without disclosing the underlying private record to another facility.

Choice 2 · Share with the network

What can other facilities receive?

Published reports start facility-private. An authorized user must separately choose which records to share and whether to reach the local network, county, or a broader area. Statewide and nationwide requests require moderation. Sharing is set for the approved record, not individual fields within it; receiving facilities still need the appropriate access and paid entitlements.

SentryIQ may detect a private record-to-record match internally, but it cannot send another facility a detailed match alert based on your private source record unless you have authorized the relevant sharing scope and all other permissions are satisfied. You can later narrow sharing or revoke a record; related alerts are re-evaluated.

A practical example · Fictitious data

How a connection between two facilities becomes useful.

01

Facility A chooses to submit an incident record and plate DEMO-417. The record starts private; Facility A separately decides to share it with its local network.

02

Facility B independently records the same exact plate. SentryIQ detects a record-to-record match; Facility A's sharing choice determines whether its record can support an alert to B.

03

An authorized Protect user at Facility B receives the eligible alert, reviews permitted source details, and decides whether to check access activity, preserve evidence, or contact Facility A.

Network members can contribute reports and coordinate through permitted RFIs or BOLOs, but they do not receive this paid exact-match alert. A plate match alone does not establish who was driving, intent, or criminal involvement.

Next · Explore the product

Now see what it looks like.

Take a short, no-login product tour. Switch between Network and Protect, try different sharing choices, and see when a cross-facility alert becomes available. The first demonstration uses fictitious data; no real customer records or vendor integrations are exposed.

Ready to discuss a real-data pilot afterward? That requires verified facilities, source rights, security readiness, and agreed terms.