IP Library Granted Patent US 12699754
Granted Patent B1
US 12699754 · App. 18/817,634 · Granted Aug 4, 2026

Emergency device access for companions

Inventors: Paul Joseph Astwood (San Antonio, TX); Steven Michael Bernstein (San Antonio, TX); Janell Guzman (Boerne, TX); Gregory David Hansen (Fuquay Varina, NC); Nina Schuessler (San Antonio, TX); Kristina Suniga Cabrera (San Antonio, TX); Mounica Urity (Mountain View, CA)
Assignee: United Services Automobile Association (USAA)
G06F21/31
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12699754
App. No.
18/817,634
Granted
Aug 4, 2026
Kind
B1
Abstract

A method and system for managing and enabling emergency access to critical data. The embodiments provide a system that authenticates companions of a owner of a computing device following a secure enrollment process in which companion data and authentication factor are stored. An app installed on the computing device can then be used to perform authentication of the companion and then allow access to limited features linked to their stored data. In some embodiments, the app can allow the companion to access their information such as emergency contacts and payment details, as well as some features of apps for which they had previously stored their credentials.

Claims (40)

1 . A method for providing authorized users limited access to a computing device, the method comprising:

receiving, at a companion access application running on a first computing device and at a first time, a first request to initiate a companion access session on behalf of a first companion;

blocking, by the companion access application and in response to the first request, access to features or data associated with the first computing device outside of the companion access application;

receiving, at the companion access application and from a first person at a second time after the first time, a first authentication factor;

authenticating, via the companion access application, the first person as the first companion based on the first authentication factor;

initiating, by the companion access application, the companion access session in response to both the first request and the first companion's authentication;

presenting, via the companion access application, a first set of information associated with the first companion retrieved from a companion repository;

presenting, at the companion access application and before the second time, a second request for a second authentication factor associated with an owner of the first computing device in response to receiving the first request; and

presenting, at the companion access application, a third request for the first authentication factor only in cases where the second authentication factor is received and the owner has been authenticated, wherein the third request must be presented before the first authentication factor can be received.

2 . The method of claim 1 , further comprising continuing to block access to features or data associated with the first computing device outside of the companion access application until the second authentication factor is received.

3 . The method of claim 1 , further comprising receiving, at the companion access application during an enrollment session performed at a third time prior to the first time, data for the first companion including the first set of information and a record of the first authentication factor, wherein authentication of the first companion is based on the record.

4 . The method of claim 3 , wherein the data also includes payment details associated with the first companion that enables, during the companion access session, the use of a mobile payment service via the first computing device that is charged to an account for the first companion.

5 . The method of claim 1 , further comprising automatically terminating the companion access session after a prespecified period of time has passed, the prespecified period having been selected by either the first companion or an owner of the first computing device.

6 . The method of claim 1 , further comprising automatically terminating, at a third time after the second time, the companion access session, and continuing to block access to features or data associated with the first computing device outside of the companion access application until the second authentication factor is received.

7 . The method of claim 1 , further comprising automatically wiping the data for the first companion if the first companion fails to initiate any subsequent companion access sessions within a prespecified period of time following the third time.

8 . The method of claim 1 , further comprising:

presenting, at the companion access application and after a prespecified period following the second time, another request for the first authentication factor; and

automatically terminating the companion access session unless reauthentication of the first companion is successful.

9 . The method of claim 1 , further comprising receiving, at the companion access application during an enrollment session performed at a third time prior to the first time, data for the first companion, wherein the data is transmitted from a second computing device associated with the first companion.

10 . The method of claim 9 , wherein the companion access session includes a micro app corresponding to an app that was installed on the second computing device.

11 . A system for providing authorized users limited access to a computing device, the system comprising a processor and machine-readable media including instructions which, when executed by the processor, cause the processor to:

receive, at a companion access application running on a first computing device and at a first time, a first request to initiate a companion access session on behalf of a first companion;

block, by the companion access application and in response to the first request, access to features or data associated with the first computing device outside of the companion access application;

receive, at the companion access application and from a first person at a second time after the first time, a first authentication factor;

authenticate, via the companion access application, the first person as the first companion based on the first authentication factor;

initiate, by the companion access application, the companion access session in response to both the first request and the first companion's authentication;

present, via the companion access application, a first set of information associated with the first companion retrieved from a companion repository;

presenting, at the companion access application and before the second time, a second request for a second authentication factor associated with an owner of the first computing device in response to receiving the first request; and

presenting, at the companion access application, a third request for the first authentication factor only in cases where the second authentication factor is received and the owner has been authenticated, wherein the third request must be presented before the first authentication factor can be received.

12 . The system of claim 11 , wherein the instructions further cause the processor to continue to block access to features or data associated with the first computing device outside of the companion access application until the second authentication factor is received.

13 . The system of claim 11 , wherein the instructions further cause the processor to receive, at the companion access application during an enrollment session performed at a third time prior to the first time, data for the first companion including the first set of information and a record of the first authentication factor, wherein authentication of the first companion is based on the record.

14 . The system of claim 13 , wherein the data also includes payment details associated with the first companion that enables, during the companion access session, the use of a mobile payment service via the first computing device that is charged to an account for the first companion.

15 . The system of claim 11 , wherein the instructions further cause the processor to automatically terminate the companion access session after a prespecified period of time has passed, the prespecified period having been selected by either the first companion or an owner of the first computing device.

16 . The system of claim 11 , wherein the instructions further cause the processor to automatically terminate, at a third time after the second time, the companion access session, and continuing to block access to features or data associated with the first computing device outside of the companion access application until the second authentication factor is received.

17 . The system of claim 11 , wherein the instructions further cause the processor to automatically wipe the data for the first companion if the first companion fails to initiate any subsequent companion access sessions within a prespecified period of time following the third time.

18 . The system of claim 11 , wherein the instructions further cause the processor to:

present, at the companion access application and after a prespecified period following the second time, another request for the first authentication factor; and

automatically terminate the companion access session unless reauthentication of the first companion is successful.

19 . The system of claim 11 , wherein the instructions further cause the processor to receive, at the companion access application during an enrollment session performed at a third time prior to the first time, data for the first companion, wherein the data is transmitted from a second computing device associated with the first companion.

20 . The system of claim 19 , wherein the companion access session includes a micro app corresponding to an app that was installed on the second computing device.