Express
Location-Verified Alerts
Sends user data to a third party only after confirming both biometric identity and a live GPS location match.
US11418503B2 gates data retrieval behind two checks that must both pass: who you are, and where you're standing when you ask.
Stolen credentials and spoofed biometrics let attackers authenticate as someone else from anywhere in the world. A system that only checks identity has no way to know if the real person is actually present.
The system pairs a biometric or device-based identity check with a live GNSS location match — both have to agree before any data moves.
A computing platform first collects source data tied to a user and derives "assistance information" that includes a GPS-based location. Later, when the user authenticates with biometric or device data, the platform checks both that they are who they claim to be and that they're standing where the system expects, before releasing the stored data to a third party.
The platform sits between a user's sensors and an enterprise's notification pipeline.
Sensor systems and a user's communication device feed source data into the assistant platform. After authenticating identity and location, the platform pushes the retrieved data to an enterprise host platform or admin device.
The platform doesn't just store incoming data — it parses it for meaning before deciding what to do next.
When the user's device sends source data, the platform parses keywords out of it and uses those keywords to determine what "assistance information" to generate. This is what lets the system react differently depending on the content of what's being sent, not just its presence.
The "assistance information" sent back to the user isn't just data — it's data anchored to a GNSS coordinate.
That embedded location becomes the reference point the system checks against later. When the user re-authenticates, their current GPS position has to match the location baked into this earlier message — turning a one-time data exchange into a standing geofence.
Identity verification and location matching are independent gates — failing either one stops the data release.
The platform compares incoming biometric or device authentication data against a stored authentication database to confirm identity, and separately compares the user's current location against the location recorded in the earlier assistance information. Only when both checks succeed does it retrieve the stored source data and notify a third party.
The message sent to the third party isn't just "user verified" — it can include the user's recent activity history.
A dependent claim extends the notification payload to include data corresponding to historical activity at the second communication device. That turns a bare verification ping into a richer alert — useful for an enterprise recipient deciding how to respond.
Two uses are explicitly claimed; two more are reasonable extensions of the same mechanism.
This patent has one related filing on record — a continuation application from the same assignee — and no third-party citations yet.