Browser data storage method and system

Abstract

The invention provides a browser data storage method and system, and the method comprises the steps: a user logs in a browser, obtains user information, equipment information and a random character string, carries out the calculation through a Hash algorithm, obtains a 32-bit private key, and exports the 32-bit private key as a PDF file, and the browser does not store or upload the private key; if the user selects a device which is not associated with the client, the browser encrypts the data through a 32-bit private key, and then stores the data locally or uploads the data to the server; if the user selects a device associated with the client, the browser obtains device information, the device information and the 32-bit private key are calculated through a Hash algorithm to obtain a 32-bit secret key, and then the browser encrypts the data and locally stores the data or uploads the data to the server; two data storage modes of local and cloud synchronization are provided, the security of user data in different environments is ensured, and the data can be associated with equipment, so that the data is safer.

Description

Technical Field

[0001] The present invention relates to the field of data security technology, and in particular to a method and system for storing browser data. Background Art

[0002] In the digital age, data security is the primary concern of users and enterprises. As the demand for data storage and transmission increases, how to protect user data in local and cloud environments has become an important technical challenge. Traditional data storage methods have data leakage and privacy risks, and during the data transmission process, they may be subject to network monitoring and malicious attacks.

[0003] Common data protection solutions in the industry generally only ensure that malicious users cannot crack data, but cannot prevent data leakage by internal personnel. Existing user data is basically stored in plain text in the database, or encrypted in the cloud, which cannot prevent data leakage. In particular, cases of data theft by internal personnel of the company also occur from time to time, greatly affecting the company's reputation and causing economic losses. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method and system for browser data storage, with two data storage modes, local and cloud synchronization, to ensure the security of user data in different environments, and to associate data with devices to make the data more secure.

[0005] In a first aspect, the present invention provides a method for storing browser data, comprising the following steps:

[0006] Step 1: The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key;

[0007] Step 2: If the user chooses not to associate the client device, the browser encrypts the data using a 32-bit private key and then stores it locally or uploads it to the server.

[0008] If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server.

[0009] Step 3. When the user logs in to the browser again, decryption is performed based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data using the 32-bit key, and opens the browser.

[0010] In a second aspect, the present invention provides a system for storing browser data, comprising:

[0011] Get the secret key module. The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key.

[0012] Encrypted storage module: if the user chooses not to associate the client device, the browser will encrypt the data using a 32-bit private key and then store it locally or upload it to the server.

[0013] If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server.

[0014] Decryption module: when the user logs in to the browser again, decryption is performed based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data through the 32-bit key, and opens the browser.

[0015] One or more technical solutions provided by the present invention have at least the following technical effects or advantages:

[0016] 1. Multi-level data security protection:

[0017] The present invention provides two data storage modes: local and cloud synchronization, to ensure the security of user data in different environments. In the local mode, the data is completely stored on the user's local device, avoiding the security risks brought by network transmission. In the cloud synchronization mode, the data is encrypted before being transmitted to the cloud, ensuring that the data cannot be interpreted even if it is intercepted during the transmission process.

[0018] 2. Uniqueness and security of user private keys:

[0019] The present invention generates a 32-bit user private key and exports it to the user. The private key is not uploaded to the server, nor is it stored in the browser, which greatly reduces the risk of the private key being stolen. The uniqueness of the user's private key ensures that the data encryption of each user is independent, and even if a user's private key is leaked, it will not affect the data security of other users.

[0020] 3. Ultimate privacy protection:

[0021] The private key is only kept by the user. This method ensures the absolute privacy of user data. Users can safely store their data on the server without worrying about the data being accessed by the official or third party.

[0022] 4. Flexible storage mode selection:

[0023] Users can choose local mode or cloud synchronization mode according to their needs. For users who have extremely high requirements for data privacy, they can choose local mode to ensure that data does not leave the local device.

[0024] 5. Reduce the risk of data leakage:

[0025] The system is designed with the worst-case data leakage in mind. Even if a malicious user obtains the encrypted data, they still cannot decrypt the data due to the lack of the private key. This design greatly reduces the risk of data leakage and increases user trust in the system.

[0026] 6. User autonomy and responsibility:

[0027] The present invention gives the management right of the private key to the user, thereby enhancing the user's autonomy over data security.

[0028] This data encryption storage system provides users with a secure, flexible and highly privacy-protected data storage solution, meeting the high standards of modern users for data security.

[0029] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0031] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0032] Figure 2 It is a schematic diagram of the structure of the system in the second embodiment of the present invention. DETAILED DESCRIPTION

[0033] The embodiments of the present application provide a method and system for storing browser data, thereby greatly improving the security of browser data.

[0034] The technical solution in the embodiment of the present application has the following general idea:

[0035] Data storage modes include: local storage mode and cloud synchronization mode;

[0036] Local storage mode: In local storage mode, all user data is stored on the local computer. Encryption technology is used to protect local data to prevent data from being stolen during transmission.

[0037] Cloud synchronization mode: In cloud synchronization mode, user data is transmitted to the server after being encrypted.

[0038] User private key generation: Generate a 32-bit user private key on the client and export it to the user. The private key is only stored by the user.

[0039] Data encryption: Use the user's private key + device information to encrypt all user privacy data with AES-256. The encryption process is completed locally on the client to ensure that the data is encrypted before being transmitted to the cloud. Among them: whether to combine device information for encryption is optional. If encryption is combined with device information, it is necessary to avoid device damage that may cause data to be unable to be retrieved.

[0040] Data decryption: Data can only be decrypted after the user enters the private key, ensuring the privacy and security of the data. If the user chooses to associate device information, the data can only be decrypted after the user enters the private key in the client on the same device. If the device is changed or the private key is incorrect, the data cannot be decrypted.

[0041] When uploading user data to the server: the server includes a business server and an encryption and decryption server; the browser uploads user data, and the browser requires the user to log in with an account and password, and the business server stores the account and the corresponding user ID; the business server receives the user data; the business server queries and obtains the corresponding first user ID according to the client, and the business server sends the user data and the first user ID to the encryption and decryption server; the encryption and decryption server generates a first cloud key through a hash algorithm according to the first user ID, encrypts the user data through an AES encryption algorithm through the first cloud key, obtains first encrypted data, and then sends the encrypted data to the business server; the encryption and decryption server deletes the first cloud key and the first user ID; the business server stores the first encrypted data; the browser requests data from the business server, and the business server obtains the second encrypted data corresponding to the browser, and sends the second encrypted data and the second user ID corresponding to the browser to the encryption and decryption server; the encryption and decryption server generates a second cloud key through the second user ID, decrypts the second encrypted data through the second cloud key, obtains decrypted data, sends the decrypted data to the business server, and the business server forwards the decrypted data to the browser.

[0042] Embodiment 1

[0043] like Figure 1 As shown, this embodiment provides a method for storing browser data, including the following steps:

[0044] Step 1: The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key;

[0045] Step 2: If the user chooses not to associate the client device, the browser encrypts the data using a 32-bit private key and then stores it locally or uploads it to the server.

[0046] If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server.

[0047] Step 3. When the user logs in to the browser again, the data is decrypted based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data through the 32-bit key, and opens the browser. When the user data is stored on the server, the browser needs to obtain it from the server, and then use the private key or the key to decrypt it.

[0048] In this embodiment, preferably, the step 1 is specifically as follows: the user logs in to the browser, obtains user information, device information and a random string, calculates through the sha1 algorithm, obtains a 32-bit private key, and exports it as a PDF file, the PDF file is used for user storage, the browser does not save or upload the private key, the user information is the user ID, the device information includes: CPU ID, hard disk ID, motherboard ID and system unique identifier, which are calculated through the sha1 algorithm to obtain a 32-bit string; the random string is a 32-bit string generated by a random algorithm.

[0049] In this embodiment, preferably, step 2 is specifically as follows: if the user chooses not to associate the client device, the browser encrypts the data using the AES-256 encryption algorithm with a 32-bit private key, and then stores it locally or uploads it to the server;

[0050] If the user chooses to associate the client's device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then uses the AES-256 encryption algorithm to encrypt the data, and then stores it locally or uploads it to the server.

[0051] In this embodiment, preferably, step 3 is specifically as follows: when the user logs in to the browser again, decryption is performed based on whether the device of the client is associated. If there is no device associated with the client, the data is decrypted using the AES-256 encryption algorithm based on the 32-bit private key input by the user. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened; if there is a device associated with the client, the browser obtains the device information and the 32-bit private key input by the user, and then calculates the 32-bit key through the hash algorithm, and decrypts the data using the AES-256 encryption algorithm through the 32-bit key. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened.

[0052] In this embodiment, preferably, the uploading to the server specifically includes: including a business server, a storage server and an encryption and decryption server; the browser uploads user data, and the business server receives the user data; the business server queries and obtains the corresponding first user ID according to the browser, and the business server sends the user data and the first user ID to the encryption and decryption server; the encryption and decryption server goes to the storage server to obtain the first cloud key according to the first user ID. If it does not exist, the encryption and decryption server generates a random string of a set length through a random algorithm, generates a first cloud key through a hash algorithm according to the first user ID and the random string, encrypts the user data through the AES encryption algorithm through the first cloud key to obtain the first encrypted data, and the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the storage server. The data is sent to the business server; if it exists, the encryption and decryption server encrypts the user data by using the first cloud key to obtain encrypted data, and then sends the encrypted data to the business server; the encryption and decryption server sends the first cloud key and the first user ID to the storage server for storage; the business server stores the first encrypted data; the browser requests data from the business server, the business server obtains the second encrypted data corresponding to the browser, and sends the second encrypted data and the second user ID corresponding to the browser to the encryption and decryption server; the encryption and decryption server obtains the second cloud key from the storage server according to the second user ID, decrypts the second encrypted data by using the second cloud key to obtain decrypted data, sends the decrypted data to the business server, and the business server forwards the decrypted data to the browser.

[0053] Based on the same inventive concept, the present application also provides a system corresponding to the method in Example 1, see Example 2 for details.

[0054] Embodiment 2

[0055] like Figure 2 As shown, in this embodiment, a system for storing browser data is provided, including:

[0056] Get the secret key module. The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key.

[0057] Encrypted storage module: if the user chooses not to associate the client device, the browser will encrypt the data using a 32-bit private key and then store it locally or upload it to the server.

[0058] If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server.

[0059] Decryption module: when the user logs in to the browser again, decryption is performed based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data through the 32-bit key, and opens the browser.

[0060] In this embodiment, preferably, the secret key module is specifically as follows: the user logs in to the browser, obtains user information, device information and a random string, calculates through the sha1 algorithm, obtains a 32-bit private key, and exports it as a PDF file, the PDF file is used for user storage, the browser does not save or upload the private key, the user information is the user ID, the device information includes: CPU ID, hard disk ID, motherboard ID and system unique identifier, calculates through the sha1 algorithm, and obtains a 32-bit string; the random string is a 32-bit string generated by a random algorithm.

[0061] In this embodiment, preferably, the encryption storage module is specifically: if the user chooses not to associate the client device, the browser uses the AES-256 encryption algorithm with a 32-bit private key to encrypt the data, and then stores it locally or uploads it to the server;

[0062] If the user chooses to associate the client's device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then uses the AES-256 encryption algorithm to encrypt the data, and then stores it locally or uploads it to the server.

[0063] In this embodiment, preferably, the decryption module is specifically as follows: when the user logs in to the browser again, decryption is performed based on whether the client device is associated. If there is no device associated with the client, the data is decrypted using the AES-256 encryption algorithm based on the 32-bit private key input by the user. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened; if there is a device associated with the client, the browser obtains the device information and the 32-bit private key input by the user, and then calculates the 32-bit key through the hash algorithm, and decrypts the data using the AES-256 encryption algorithm through the 32-bit key. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened.

[0064] In this embodiment, preferably, the uploading to the server specifically includes: including a business server, a storage server and an encryption and decryption server; the browser uploads user data, and the business server receives the user data; the business server queries and obtains the corresponding first user ID according to the browser, and the business server sends the user data and the first user ID to the encryption and decryption server; the encryption and decryption server goes to the storage server to obtain the first cloud key according to the first user ID. If it does not exist, the encryption and decryption server generates a random string of a set length through a random algorithm, generates a first cloud key through a hash algorithm according to the first user ID and the random string, encrypts the user data through the AES encryption algorithm through the first cloud key to obtain the first encrypted data, and the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the storage server. The data is sent to the business server; if it exists, the encryption and decryption server encrypts the user data by using the first cloud key to obtain encrypted data, and then sends the encrypted data to the business server; the encryption and decryption server sends the first cloud key and the first user ID to the storage server for storage; the business server stores the first encrypted data; the browser requests data from the business server, the business server obtains the second encrypted data corresponding to the browser, and sends the second encrypted data and the second user ID corresponding to the browser to the encryption and decryption server; the encryption and decryption server obtains the second cloud key from the storage server according to the second user ID, decrypts the second encrypted data by using the second cloud key to obtain decrypted data, sends the decrypted data to the business server, and the business server forwards the decrypted data to the browser.

[0065] Since the system introduced in the second embodiment of the present invention is a system used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the system based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All systems used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0066] The technical solution provided in the embodiments of the present application has at least the following technical effects or advantages:

[0067] This embodiment provides a method of local data storage and cloud data storage to ensure the security of browser data; and if the user encrypts by associating hardware information, the data can only be decrypted and used in the hardware, and cannot be decrypted in other hardware, which greatly ensures the security of the data.

[0068] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for storing browser data, characterized in that: The steps include: Step 1: The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key; Step 2: If the user chooses not to associate the client device, the browser encrypts the data using a 32-bit private key and then stores it locally or uploads it to the server. If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server. Step 3. When the user logs in to the browser again, decryption is performed based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data using the 32-bit key, and opens the browser.

2. A method for storing browser data according to claim 1, characterized in that: The step 1 is specifically as follows: the user logs in to the browser, obtains user information, device information and a random string, calculates through the sha1 algorithm, obtains a 32-bit private key, and exports it as a PDF file. The PDF file is used for user storage. The browser does not save or upload the private key. The user information is the user ID. The device information includes: CPU ID, hard disk ID, motherboard ID and system unique identifier, which are calculated through the sha1 algorithm to obtain a 32-bit string; the random string is a 32-bit string generated by a random algorithm.

3. A method for storing browser data according to claim 1, characterized in that: The step 2 is specifically as follows: if the user chooses not to associate the client device, the browser encrypts the data using the AES-256 encryption algorithm with a 32-bit private key, and then stores it locally or uploads it to the server; If the user chooses to associate the client's device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then uses the AES-256 encryption algorithm to encrypt the data, and then stores it locally or uploads it to the server.

4. A method for storing browser data according to claim 1, characterized in that: The step 3 is specifically as follows: when the user logs in to the browser again, decryption is performed based on whether the device of the client is associated. If there is no device associated with the client, the data is decrypted using the AES-256 encryption algorithm based on the 32-bit private key input by the user. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened; if there is a device associated with the client, the browser obtains the device information and the 32-bit private key input by the user, and then calculates the 32-bit key through the hash algorithm, and decrypts the data using the AES-256 encryption algorithm using the 32-bit key. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened.

5. A method for storing browser data according to claim 1, characterized in that: The uploading to the server specifically includes: including a business server, a storage server and an encryption and decryption server; the browser uploads the user data, and the business server receives the user data; The business server queries and obtains the corresponding first user ID according to the browser, and sends the user data and the first user ID to the encryption and decryption server; the encryption and decryption server obtains the first cloud key from the storage server according to the first user ID. If it does not exist, the encryption and decryption server generates a random string of a set length through a random algorithm, generates a first cloud key through a hash algorithm according to the first user ID and the random string, encrypts the user data through the AES encryption algorithm through the first cloud key to obtain the first encrypted data, and the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the business server; if it exists, the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the business server; the encryption and decryption server sends the first cloud key and the first user ID to the storage server for storage; The business server stores the first encrypted data; the browser requests data from the business server, the business server obtains the second encrypted data corresponding to the browser, and sends the second encrypted data and the second user ID corresponding to the browser to the encryption and decryption server; the encryption and decryption server obtains the second cloud key from the storage server according to the second user ID, decrypts the second encrypted data using the second cloud key to obtain decrypted data, sends the decrypted data to the business server, and the business server forwards the decrypted data to the browser.

6. A system for storing browser data, characterized in that: include: Get the secret key module. The user logs in to the browser, obtains user information, device information and a random string, calculates through a hash algorithm, obtains a 32-bit private key, and exports it as a PDF file. The browser does not save or upload the private key. Encrypted storage module: if the user chooses not to associate the client device, the browser will encrypt the data using a 32-bit private key and then store it locally or upload it to the server. If the user chooses to associate a client device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then encrypts the data and stores it locally or uploads it to the server. Decryption module: when the user logs in to the browser again, decryption is performed based on whether the device is associated with the client. If there is no device associated with the client, the data is decrypted based on the 32-bit private key entered by the user and the browser is opened. If there is a device associated with the client, the browser obtains the device information and the 32-bit private key entered by the user, and then calculates the 32-bit key through the hash algorithm, decrypts the data through the 32-bit key, and opens the browser.

7. A browser data storage system according to claim 6, characterized in that: The secret key obtaining module is specifically as follows: the user logs in to the browser, obtains user information, device information and a random string, calculates through the sha1 algorithm, obtains a 32-bit private key, and exports it as a PDF file. The PDF file is used for user storage. The browser does not save or upload the private key. The user information is the user ID, and the device information includes: CPU ID, hard disk ID, motherboard ID and system unique identifier, which are calculated through the sha1 algorithm to obtain a 32-bit string; the random string is a 32-bit string generated by a random algorithm.

8. A browser data storage system according to claim 6, characterized in that: The encryption storage module is specifically as follows: if the user chooses not to associate the client device, the browser uses the AES-256 encryption algorithm with a 32-bit private key to encrypt the data, and then stores it locally or uploads it to the server; If the user chooses to associate the client's device, the browser obtains the device information and calculates it with the 32-bit private key through a hash algorithm to obtain a 32-bit key. The browser then uses the AES-256 encryption algorithm to encrypt the data, and then stores it locally or uploads it to the server.

9. A browser data storage system according to claim 6, characterized in that: The decryption module is specifically as follows: when the user logs in to the browser again, decryption is performed based on whether the client device is associated. If there is no device associated with the client, the data is decrypted using the AES-256 encryption algorithm based on the 32-bit private key input by the user. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened; if there is a device associated with the client, the browser obtains the device information and the 32-bit private key input by the user, and then calculates the 32-bit key through the hash algorithm, and decrypts the data using the AES-256 encryption algorithm through the 32-bit key. If the decryption is successful, the browser is opened; if the decryption fails, the browser is not opened.

10. A browser data storage system according to claim 6, characterized in that: The uploading to the server specifically includes: including a business server, a storage server and an encryption and decryption server; the browser uploads the user data, and the business server receives the user data; The business server queries and obtains the corresponding first user ID according to the browser, and sends the user data and the first user ID to the encryption and decryption server; the encryption and decryption server obtains the first cloud key from the storage server according to the first user ID. If it does not exist, the encryption and decryption server generates a random string of a set length through a random algorithm, generates a first cloud key through a hash algorithm according to the first user ID and the random string, encrypts the user data through the AES encryption algorithm through the first cloud key to obtain the first encrypted data, and the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the business server; if it exists, the encryption and decryption server encrypts the user data through the first cloud key to obtain the encrypted data, and then sends the encrypted data to the business server; the encryption and decryption server sends the first cloud key and the first user ID to the storage server for storage; The business server stores the first encrypted data; the browser requests data from the business server, the business server obtains the second encrypted data corresponding to the browser, and sends the second encrypted data and the second user ID corresponding to the browser to the encryption and decryption server; the encryption and decryption server obtains the second cloud key from the storage server according to the second user ID, decrypts the second encrypted data using the second cloud key to obtain decrypted data, sends the decrypted data to the business server, and the business server forwards the decrypted data to the browser.

Images