Data security system and method
Abstract
A system and method are disclosed for secure storage of customer's public and private data in a personal data store. Companies communicate with a secure data storage server using a public encryption key linked to a registered IP Address, customers communicate with a private encryption key, and encrypted data can be stored using a variety of encryption keys. The personal data store can be used for preparing customer product views, linking personal data to avoid repeated customer data entries, customer identification and loyalty card linking. Encrypted stored data ensures no other person can read it.
Claims
exact text as granted — not AI-modified1 .- 40 . (canceled)
41 . A system for controlling bidirectional communication comprising:
a server communicatively connected to at least one data store comprising application data having public data and private data; a security mechanism coupled to the server; and an application capable of bidirectionally communicating with the server via the security mechanism, the security mechanism further comprising, an application programming interface that can be used by the application to interact with the server; a security condition, wherein the security mechanism determines if the security condition is met, the determination including at least using first application data from the application, wherein the first application data is encrypted and stored using a first private key, and using second service provider data from the server, wherein the second service provider data is encrypted and stored using a second private key.
42 . The system according to claim 41 , wherein the determination that a security condition is met includes receiving and sending application data, service provider data, requests and commands.
43 . The system according to claim 41 , wherein the server accesses the at least one data store only from a previously registered IP address, or a token.
44 . The system of claim 41 , wherein the security mechanism is configured to make a determination whether the application supplied a password or a token, as a condition for the security condition being met.
45 . The system of claim 41 , wherein the security mechanism is capable of encrypting one or more of the first and second private keys.
46 . The system of claim 45 , wherein the security mechanism stores the encrypted first or the second private keys in the data store.
47 . The system of claim 46 , wherein the password or the token is used by the security mechanism to determine whether to decrypt the first or the second private keys from the data store.
48 . A device, comprising:
a server communicatively connected to at least one data store comprising application data having public data and private data; a security device coupled to the server; and an application capable of bidirectionally communicating with the server via the security mechanism, the security mechanism further comprising, an application programming interface that can be used by the application to interact with the server when a security condition is determined to be met by the security device, the determination including at least using first application data from the application, wherein the first application data is encrypted and stored using a first private key, and using second service provider data from the server, wherein the second service provider data is encrypted and stored using a second private key.
49 . The device according to claim 48 , wherein the determination that a security condition is met includes receiving and sending application data, service provider data, requests and commands.
50 . The device according to claim 48 , wherein the server accesses the at least one data store only from a previously registered IP address or a token.
51 . The device of claim 48 , wherein the security mechanism is configured to make a determination whether the application supplied a password or a token, as a condition for the security condition being met.
52 . The device of claim 51 , wherein the security device is capable of encrypting one or more of the first and second private keys.
53 . The device of claim 52 , wherein the security device stores the encrypted first or the second private keys in the data store.
54 . The device of claim 53 , wherein the password or the token is used by the security device to determine whether to decrypt the first or the second private keys from the data store.
55 . A method for controlling bidirectional communication, the method comprising the steps of:
providing at least one server communicatively connected to at least one data store comprising first data having public data and private data relating to an application, wherein the server is bidirectionally communicating with the application and a third-party device; obtaining the first data from the at application, wherein the first data is encrypted and stored using a first private key; obtaining second data from the at least one third-party device, wherein the second data is encrypted and stored using a second private key; receiving a request via an application programming interface from the application to interact with the third party device; and using a security mechanism capable of determining if the application can interact with the third-party device.
56 . The method of claim 55 , wherein the step of using a security mechanism further comprises:
receiving a password or a token that is used to determine if a security condition has been met.
57 . The method of claim 55 , wherein the step of receiving a request further comprises:
providing a user interface to the application and receiving the request via the user interface.
58 . The method of claim 57 , wherein the step of using further comprises encrypting one or more of the first and second private keys.
59 . The method of claim 58 , wherein the step of using further comprises storing the encrypted first or the second private keys in the data store.
60 . The method of claim 59 , wherein the step of using further comprises using the password or the token to determine whether to decrypt the first or the second private keys from the data store.Join the waitlist — get patent alerts
Track US2021042804A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.