CONTROL TOWER RESTRICTIONS ON THIRD PARTY PLATFORMS
Systems, methods, and apparatuses for providing a user a central location to manage permissions provided to third-parties and devices to access and use user data maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information. A user additionally is able to have user data and third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal. Restrictions on how user data is used by devices, applications, and third-party systems can be imposed via a central portal.
1 . A service provider computing system comprising:
a network interface configured to communicate via a telecommunications network; and
one or more processors and a memory having stored thereon instructions which, when executed by the one or more processors, cause the service provider computing system to:
maintain a listing identifying one or more computing devices which have been granted access to a user account associated with a user;
receive, via the network interface, an access request from an application installed on a computing device in the listing, the access request identifying the user account and data corresponding to the user account;
in response to verifying the access request, use the network interface to transmit the data to the application installed on the computing device;
receive, from a user device of the user, a first request that identifies the computing device and indicates that the user of the user account has denied the computing device access to the user account;
modify, responsive to receiving the first request, the listing to indicate that the user of the user account has denied the computing device access to the data corresponding to the user account;
receive, from the user device of the user, a second request to delete the user account for which the data was provided to the application;
generate, responsive to receiving the second request, a command that requests deletion of the user account and the data from the application; and
use the network interface to transmit the command to the application to have the application, consistent with the second request from the user device, delete the user account and the data received from the service provider computing system.
2 . The system of claim 1 , wherein the command includes an API call to the application, wherein the API call identifies the user and the data to be deleted.
3 . The system of claim 1 , wherein the access request is an API call transmitted by the application to the service provider computing system.
4 . The system of claim 1 , wherein the command instructs the application to delete the data from all computer-readable storage media controlled by the application.
5 . The system of claim 1 , wherein the second request identifies a selection made, via a graphical interface presented by a client application running on the user device, between permitting a use of the data and prohibiting the use of the data.
6 . The system of claim 5 , wherein the data identifies a credit or debit card, and wherein the use corresponds with use of the credit or debit card in an identified category of financial transactions.
7 . The system of claim 6 , wherein the identified category of financial transactions is foreign transactions.
8 . The system of claim 1 , wherein the listing further identifies one or more computing devices which have been granted access to the data corresponding to the user account.
9 . The system of claim 1 , wherein the instructions are further configured to cause the processor to:
determine that a calendar application has been granted access to data corresponding to the user account; and
transmit, to the calendar application, a list of upcoming payments owed by the user for display by the calendar application.
10 . The system of claim 1 , wherein the listing further comprises one or more applications installed on the user device and an indicator for each respective application to indicate whether the respective application has been granted access to data corresponding to the user account.
11 . The system of claim 1 , wherein the access request is verified by verifying, based on the listing, that the user of the user account has granted the application access to the data.
12 . A method comprising:
maintaining, by a service provider computing system, a listing of one or more computing devices which have been granted access to a user account associated with a user;
receiving, by the service provider computing system, an access request from an application installed on a computing device in the listing, the access request identifying the user account and data corresponding to the user account;
in response to verifying the access request, transmitting, by the service provider computing system, the data to the application installed on the computing device;
receiving, by the service provider computing system, from a user device of the user, a first request that identifies the computing device and indicates that the user of the user account has denied the computing device access to the user account;
modifying, by the service provider computing system, responsive to receiving the first request, the listing to indicate that the user of the user account has denied the computing device access to the data corresponding to the user account;
receiving, by the service provider computing system, from the user device of the user, a second request to delete the user account for which the data was provided to the application;
generating, by the service provider computing system, responsive to receiving the second request, a command that requests deletion of the user account and the data from the application; and
transmitting, by the service provider computing system, the command to the application to request the application to, consistent with the second request from the user device, delete the user account and the data received from the service provider computing system.
13 . The method of claim 12 , wherein the command includes an API call to the application, wherein the API call identifies the user and the data to be deleted.
14 . The method of claim 12 , wherein the command instructs the application to delete the data from all computer-readable storage media controlled by the application.
15 . The method of claim 12 , wherein the second request identifies a selection made, via a graphical interface presented by a client application running on the user device, between permitting a use of the data and prohibiting the use of the data.
16 . The method of claim 15 , wherein the data includes account data usable in financial transactions, and wherein the use corresponds with use of the data in an identified category of financial transactions.
17 . The method of claim 16 , wherein the account data is for a credit or debit card, and wherein the identified category of financial transactions is foreign transactions.
18 . The method of claim 12 , wherein the access request comprises an API call transmitted by the application to the service provider computing system.
19 . The method of claim 12 , wherein the listing further identifies one or more computing devices which have been granted access to the data corresponding to the user account.
20 . The method of claim 12 , further comprising:
determining, by the service provider computing system, that a calendar application has been granted access to data corresponding to the user account; and
transmitting, by the service provider computing system, to the calendar application, a list of upcoming payments owed by the user for display by the calendar application.