Privacy policy determination method, electronic equipment and readable storage medium

Abstract

The invention discloses a privacy policy determination method, electronic equipment and a readable storage medium. The method comprises the following steps: acquiring a target hash value corresponding to a target application; obtaining a target version privacy policy corresponding to the target hash value from a privacy policy database according to the target hash value; updating a current version privacy policy of the target application according to the target version privacy policy; wherein the privacy policy database comprises a corresponding relationship between the hash value and the privacy policy version.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and particularly to a method for determining a privacy policy, an electronic device, and a readable storage medium. Background Art

[0002] Data security has always been widely discussed. When an application provides services, the privacy policy stipulates the user's personal data processing permissions to protect the user's personal data security.

[0003] The privacy policy is pre-set when the application is released. When the application version changes and the data collection of the application increases or decreases, the privacy policy also needs to be updated synchronously accordingly. However, in the related technologies, there is a lack of automatic update of the privacy policy, and it is impossible to ensure the consistency between the application version and the privacy policy version in a timely manner. Summary of the Invention

[0004] The embodiments of the present application provide a method for determining a privacy policy, an electronic device, and a readable storage medium, which can at least solve the problem that there is a lack of automatic update of the privacy policy in the related technologies and it is impossible to ensure the consistency between the application version and the privacy policy version in a timely manner.

[0005] To solve the above technical problems, the embodiments of the present application are implemented as follows:

[0006] In a first aspect, a method for determining a privacy policy is provided. The method includes: obtaining a target hash value corresponding to a target application; obtaining a target version privacy policy corresponding to the target hash value from a privacy policy database according to the target hash value; updating the current version privacy policy of the target application according to the target version privacy policy; wherein the privacy policy database includes the corresponding relationship between the hash value and the privacy policy version.

[0007] In a second aspect, an electronic device is provided. The electronic device includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method for determining a privacy policy as described in the first aspect are implemented.

[0008] In a third aspect, a readable storage medium is provided, characterized in that a program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, the steps of the method for determining a privacy policy as described in the first aspect are implemented.

[0009] In an embodiment of the present application, by obtaining a target hash value corresponding to a target application; obtaining a target version privacy policy corresponding to the target hash value from a privacy policy database, where the privacy policy database includes the correspondence between hash values and privacy policy versions, and then updating the current version privacy policy of the target application according to the target version privacy policy, it is possible to quickly obtain from the privacy policy database the target version privacy policy corresponding to the target hash value corresponding to the current target application, so as to update the current version privacy policy of the target application in a timely manner through the target version privacy policy, effectively ensuring the consistency between the target application version and the privacy policy version. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application and used together with the specification to explain the principles of the present application.

[0011] Figure 1 FIG. shows a flowchart of a method for determining a privacy policy provided by an exemplary embodiment of the present application;

[0012] Figure 2 FIG. shows a schematic diagram of a privacy policy database provided by an exemplary embodiment of the present application;

[0013] Figure 3a FIG. shows a schematic diagram of a display of a user interface provided by an exemplary embodiment of the present application;

[0014] Figure 3b FIG. shows a schematic diagram of a display of another user interface provided by an exemplary embodiment of the present application;

[0015] Figure 3c FIG. shows a schematic diagram of a display of another user interface provided by an exemplary embodiment of the present application;

[0016] Figure 3d FIG. shows a schematic diagram of a display of another user interface provided by an exemplary embodiment of the present application;

[0017] Figure 3e FIG. shows a schematic diagram of a display of another user interface provided by an exemplary embodiment of the present application;

[0018] Figure 4 FIG. shows a schematic diagram of a data protection policy library provided by an exemplary embodiment of the present application;

[0019] Figure 5 FIG. shows a schematic diagram of the structure of a system for determining a privacy policy provided by an exemplary embodiment of the present application;

[0020] Figure 6The flowchart shows another method for determining a privacy policy provided by an exemplary embodiment of the present application;

[0021] Figure 7 The structural diagram shows an electronic device provided by an exemplary embodiment of the present application. Detailed implementation manners

[0022] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0023] Figure 1 The flowchart shows a method for determining a privacy policy provided by an exemplary embodiment of the present application. Refer to Figure 1 The method includes the following steps:

[0024] Step 102: Obtain a target hash value corresponding to the target application.

[0025] The target hash value corresponding to the target application may include an MD5 value (Message-Digest Algorithm 5).

[0026] Step 104: Obtain a target version privacy policy corresponding to the target hash value from the privacy policy database according to the target hash value.

[0027] Among them, refer to Figure 2 The privacy policy database includes the correspondence between hash values (such as MD5 values) and privacy policy versions, and can find the version privacy policy corresponding to the hash value from the privacy policy database through the hash value. One MD5 value corresponds to only one privacy policy version, ensuring that the corresponding privacy policy can be uniquely determined through one MD5 value. One privacy policy version may correspond to multiple MD5 values. For example, if certain functions or configurations of the target application change, the MD5 value will also change accordingly. If the privacy policy does not substantially change, the changed MD5 value will also correspond to this privacy policy.

[0028] For example, the target hash value corresponding to the target application is the MD5 value 4, and the privacy policy version V1 corresponding to the MD5 value 4 is obtained from the privacy policy database according to the MD5 value 4.

[0029] Step 106: Update the current version privacy policy of the target application according to the target version privacy policy.

[0030] In an embodiment of the present application, a target hash value corresponding to a target application is obtained; a target version privacy policy corresponding to the target hash value is obtained from a privacy policy database according to the target hash value, where the privacy policy database includes a correspondence between a hash value and a privacy policy version, and then the current version privacy policy of the target application is updated according to the target version privacy policy, so that the target version privacy policy corresponding to the target hash value corresponding to the current target application can be quickly obtained from the privacy policy database according to the target hash value, thereby updating the current version privacy policy of the target application in a timely manner through the target version privacy policy, effectively ensuring the consistency between the target application version and the privacy policy version.

[0031] Optionally, the privacy policy of the target application after updating the current version privacy policy of the target application according to the target version privacy policy is displayed on the user interface of the target application. Refer to Figure 3a , the target version privacy policy V3 is displayed on the user interface of the target application, and the privacy policies V1 and V2 of other versions are hidden.

[0032] In one implementation, after obtaining the target hash value corresponding to the target application in step 102 above, the method may further include the following steps:

[0033] Step 103, in the case that there is no target version privacy policy corresponding to the target hash value in the privacy policy database, obtain the first data collected by the target application based on each first function and the field feature values corresponding to each second function in the historical privacy policy of the target application, where each second function is the function corresponding to each first function in the historical privacy policy; and / or, in the case that the field feature value matches the first data, establish a first correspondence between the target hash value and the historical privacy policy, and store the first correspondence in the privacy policy database.

[0034] Among them, the historical privacy policy is the privacy policy of the version used by the target application in the historical period. The field feature values corresponding to each second function in the historical privacy policy of the target application are descriptions of the relevant information of each first function of the target application, such as the type and scope of data that needs to be collected when performing the first function. The first function corresponds to the second function. For example, the first function is the login function in the target application, and the second function is the login function in the historical privacy policy.

[0035] In an embodiment of the present application, when there is a target version privacy policy corresponding to the target hash value in the privacy policy database, the target version privacy policy corresponding to the target hash value can be obtained from the privacy policy database according to the target hash value. When there is no target version privacy policy corresponding to the target hash value in the privacy policy database, it is necessary to further determine the matching degree between the target application and the historical privacy policies, so as to determine whether there is a privacy policy with a version consistent with the target application among the historical privacy policies that can be used. It can be achieved by obtaining the first data collected by the target application based on each first function and obtaining the field feature values corresponding to each second function in the historical privacy policy of the target application, where each second function is the function corresponding to each first function in the historical privacy policy. By comparing the first data collected by the target application based on each first function during the actual task execution process with the field feature values corresponding to each second function specified in the historical privacy policy of the target application, and when the matching is consistent, a first correspondence relationship is established between the target hash value and the historical privacy policy, and the first correspondence relationship is stored in the privacy policy database, so that according to the first correspondence relationship between the target hash value and the historical privacy policy, the historical privacy policy can be obtained from the privacy policy database and the current version privacy policy of the target application can be updated, thereby ensuring the consistency between the target application version and the privacy policy version.

[0036] It should be noted that the judgment on whether the field feature value of the historical privacy policy matches the first data may include: whether the first functions for collecting the same first data are the same, whether the first data collected by the same first function is the same, whether the underlying execution codes for the same first function to collect the same first data are the same, etc. For example, for collecting the same data, in the historical privacy policy, it is for logging in to an account, while in the target application, it is for displaying the account, then the field feature value of the historical privacy policy does not match the first data. Another example is that the same function collects the same data, but in the historical privacy policy, it is executed through the server's self-developed code, while in the target application, it is executed through a third-party software development kit (SDK), then the field feature value of the historical privacy policy does not match the first data.

[0037] Optionally, to find the historical privacy policy of the target application, the version release time information of the target application and the version release time of the historical privacy policy can be obtained, and by comparing the two version release times, the historical privacy policy with a version release time close to that of the target application is preferentially selected to improve the efficiency of finding the historical privacy policy.

[0038] In one implementation manner, after obtaining the target hash value corresponding to the target application in step 102 above, the method may further include the following steps:

[0039] Step 1051, when there is no target version privacy policy corresponding to the target hash value in the privacy policy database, obtain the first data collected by the target application based on each first function and the field feature values corresponding to each second function in the historical privacy policy of the target application, where each of the second functions is a function corresponding to each of the first functions in the historical privacy policy.

[0040] Step 1052, when the field feature values do not match the first data, update the historical privacy policy according to the difference between the first data and the field feature values.

[0041] Among them, the situation where the field feature values of the historical privacy policy do not match the first data may include that the collection scope of the first data is different in the historical privacy policy and in the target application; the number or purpose of the functions for collecting the first data is different in the historical privacy policy and in the target application.

[0042] Step 1053, establish a second correspondence between the target hash value and the updated historical privacy policy, and store the second correspondence in the privacy policy database.

[0043] In the embodiment of the present application, when comparing the first data collected by the target application based on each first function during the actual execution of tasks with the field feature values corresponding to each second function specified in the historical privacy policy of the target application, and the two do not match, it indicates that there is a difference between the first data and the field feature values, and further indicates that there is a difference between the target application and the historical privacy policy. The historical privacy policy can be updated according to the difference between the first data and the field feature values, and then the second correspondence established between the target hash value and the updated historical privacy policy is stored in the privacy policy database, so as to obtain the historical privacy policy from the privacy policy database according to the target hash value and update the current version privacy policy of the target application, thereby ensuring the consistency between the target application version and the privacy policy version.

[0044] In one implementation manner, step 1052 of updating the historical privacy policy according to the difference between the first data and the field feature values may include the following steps:

[0045] Step 11, when the first data collection scope of the first function is smaller than the second data collection scope of the second function, reduce the second data collection scope of the second function in the historical privacy policy to be the same as the first data collection scope; where the second data collection scope is determined according to the field feature values.

[0046] In an embodiment of the present application, based on the fact that the first data collection range of the first function based on the difference between the first data and the field feature value is smaller than the second data collection range of the second function, it can be known that the data collection range specified for the second function in the historical privacy policy exceeds the data collection range of the actual target application for the first function. To ensure the consistency between the target application version and the privacy policy version, modify the data collection range of the second function in the historical privacy policy, and reduce the second data collection range of the second function in the historical privacy policy to be the same as the first data collection range.

[0047] For example, the first function of the target application is the login function, and the data collection range of the first data includes: the user's account and password. The second function in the historical privacy policy is the login function, and the data collection range of the first data includes: the user's account, password, and login time. Then the first data does not match the field feature. According to the difference between the two: the historical privacy policy collects the user's login time more for the login function. Delete the item of the user's login time collected for the login function in the historical privacy policy to ensure the consistency between the target application and the historical privacy policy.

[0048] In one implementation manner, step 1052 of updating the historical privacy policy according to the difference between the first data and the field feature value may include the following steps:

[0049] Step 21, when the first quantity of each first function is less than the second quantity of each second function, and / or when the purpose of the first function is different from the purpose of the second function, reduce the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or change the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function.

[0050] In an embodiment of the present application, based on the fact that the first quantity of each first function is less than the second quantity of each second function due to the difference between the first data and the field feature value, and / or, in the case where the purpose of the first function is different from the purpose of the second function, it can be known that the quantity of the second function for collecting the first data stipulated in the historical privacy policy is more than the quantity of the first function for collecting the first data in the target application, and / or, the purpose of the second function for collecting the first data stipulated in the historical privacy policy is different from the purpose of the first function of the target application. To ensure the consistency between the target application version and the privacy policy version, modify the quantity and / or purpose of the second function in the historical privacy policy, reduce the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or, change the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function.

[0051] For example, the first function of the target application for collecting the first data includes a login function, and the second function of the historical privacy policy for collecting the first data includes a login function and a function of displaying user information. Then, there are differences in the quantity and purpose between the first function and the second function for collecting the first data. Reduce the login function and the function of displaying user information included in the second function for collecting the first data in the historical privacy policy to the login function.

[0052] In one implementation manner, step 1052 of updating the historical privacy policy according to the difference between the first data and the field feature value may include the following steps:

[0053] Step 31, in the case where the first data collection range of the first function is greater than the second data collection range of the second function, determine whether the first data collection range is the minimum necessary data collection range through the data collection strategy library.

[0054] Among them, the data collection strategy library includes the minimum necessary data collection range of each first function. For example, the login function only needs to collect an account (or mobile phone number) and a password.

[0055] Step 32, in the case where the first data collection range is the minimum necessary data collection range, increase the second data collection range of the second function to be the same as the first data collection range.

[0056] In an embodiment of the present application, when the first data collection range of the first function is greater than the second data collection range of the second function, and the first data collection range is the minimum necessary data collection range, it can be known that the data collection range specified in the historical privacy policy for the second function is less than the first data collection range of the target application for the first function, and the data collection range specified in the historical privacy policy for the second function cannot meet the data collection range required when the second function performs tasks. To ensure the consistency between the target application version and the privacy policy version, modify the data collection range of the second function in the historical privacy policy, and increase the second data collection range of the second function to be the same as the first data collection range.

[0057] For example, the first function of the target application is the login function, and the data collection range of the first data includes: the user's account and password. The second function in the historical privacy policy is the login function, and the data collection range of the first data includes: the user's password. Then the first data collection range of the first function is greater than the second data collection range of the second function, and the first data collection range is the minimum necessary data collection range, that is, the login function requires the user's account and password. According to the difference between the two: the login function of the target application also collects the user's account, and increasing the data collection range for the login function in the historical privacy policy to the user's account and password can achieve the login function.

[0058] In one implementation, step 1052 of updating the historical privacy policy according to the difference between the first data and the field feature value may include the following steps:

[0059] Step 41, when the first quantity of each first function is greater than the second quantity of each second function, and / or when the purpose of the first function is different from the purpose of the second function, determine whether the first data collection range is the minimum necessary data collection range through the data collection policy library.

[0060] Wherein, the data collection policy library includes the minimum necessary data collection range of each first function.

[0061] Step 42, when the first data collection range is the minimum necessary data collection range, increase the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or change the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function.

[0062] In the embodiment of the present application, when the difference in the mismatch between the first data and the field feature value is that the first quantity of each first function is greater than the second quantity of each second function, and / or when the purpose of the first function is different from the purpose of the second function, and when the first data collection scope is the minimum necessary data collection scope, it can be known that the historical privacy policy lacks regulations on the data collection scope, purpose, etc. of certain second functions. According to the difference between the two, increase the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or change the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function.

[0063] For example, the first functions for the target application to collect the first data include the login function and the function of displaying user information, and the second function for the historical privacy policy to collect the first data is the login function. Then, there are differences in the quantity and purpose between the first function and the second function for collecting the first data, and the function of displaying user information for collecting the first data is added to the historical privacy policy.

[0064] In one implementation manner, when the first data collection scope is the minimum necessary data collection scope, the method further includes the following steps:

[0065] Step 51, divide the first data into second data of different levels according to the classification and grading rules.

[0066] For example, the classification and grading rules include data sensitivity. The first data can be divided into second data of the first level, the second level, and the third level according to data sensitivity. Different protection strategies are set for the second data of different levels.

[0067] Step 52, when the first protection strategy of the second data at different levels does not match the second protection strategy in the data protection policy library, generate a first warning message.

[0068] Wherein, the data protection policy library includes second protection strategies corresponding to the first protection strategies of the second data at different levels; the first warning message is used to indicate modifying the first protection strategy of the second data according to the second protection strategy in the data protection policy library. For example, the second protection strategy in the data protection policy library adopts simple protection measures for low-sensitivity data to improve performance, but for high-sensitivity data, such as passwords, etc., local security partition encryption storage, secure transmission protocol transmission, separate encryption during transmission, server-side encryption storage, and the encryption method is not lower than the Secure Hash Algorithm 256 (SHA256) should be adopted. See Figure 4, the data protection policy library includes classification 1: low-sensitivity data and classification 2: high-sensitivity data classified according to sensitivity. The second protection policies configured for the second data after classification include Policy 1 and Policy 2. Policy 1 is configured for the low-sensitivity data of classification 1, and Policy 2 is configured for the high-sensitivity data of classification 2. In the case where the first protection policies of the low-sensitivity data and high-sensitivity data divided from the first data in the target application are inconsistent with the second protection policies of the low-sensitivity data and high-sensitivity data in the above data protection policy library, a first warning message needs to be generated.

[0069] In the embodiment of the present application, the first protection policy of the second data obtained by dividing the first data is compared with the second protection policy in the data protection policy library to determine whether the current protection policy for the second data matches the protection policy in the data protection policy library. And in the case of non-matching, a first warning message is generated, so that it can be timely indicated to modify the first protection policy of the second data according to the second protection policy in the data protection policy library, and accurate protection verification of the first data can be realized.

[0070] In one implementation, after determining whether the first data collection range is the minimum necessary data collection range through the data collection policy library as described above, the method may further include the following steps:

[0071] Step 61, in the case where the first data collection range is not the minimum necessary data collection range, generate a second warning message.

[0072] Wherein, the second warning message is used to indicate modifying the first data collection range.

[0073] In the embodiment of the present application, in the case where the first data does not match the field feature value and the first data collection range of the first data is greater than the second data collection range of the second function, or the first quantity of each first function is greater than the second quantity of each second function, and / or, in the case where the purpose of the first function is different from the purpose of the second function, and then in the case where it is determined that the first data collection range is not the minimum necessary data collection range, it can be known that there is unnecessary data in the first data collected by the target application based on the first function, and a second warning message is generated, so that it can be timely indicated to modify the first data collection range, and accurate protection verification of the first data can be realized.

[0074] In one implementation, the above method for determining the privacy policy may further include: displaying the updated historical privacy policy on the user interface of the target application.

[0075] Wherein, displaying the updated historical privacy policy on the user interface of the target application can be realized by the following method.

[0076] Implementation method 1: Refer to Figure 3b , display the updated historical privacy policy V4 on the user interface of the target application, and hide the privacy policies V1 and V2 of other versions.

[0077] Implementation method 2: Refer to Figure 3c , display "Privacy policy is being updated..." on the user interface of the target application during the update process, and display the updated historical privacy policy V4 after the update is completed.

[0078] Implementation method 3: Refer to Figure 3d , display "Privacy policy is being updated..." on the user interface of the target application during the update process, and display the updated historical privacy policy V4 after the update is completed, and update and display the link to the updated historical privacy policy in real time and dynamically.

[0079] Implementation method 4: Refer to Figure 3e , during the update process, if the text method is used, its text description can be automatically added or reduced through the crawler method. If the picture method is used, the historical privacy policy can be updated through the picture combination method, and this process is displayed on the user interface of the target application. Such as Figure 3e Modify function 3 according to function 4 in

[0080] Optionally, the display of the updated content of the privacy policy of the target application can adopt prominent methods such as italic, bold, enlarged, colored, etc., or can also adopt animation forms such as flying in, splicing, dissolving, and picture enlargement and combination. The user interface for displaying the privacy policy in the target application can be displayed through a pop-up window.

[0081] It should be noted that the above method for determining the privacy policy can be executed when the target application is started, or can also be executed during the silent upgrade process. When the version of the target application is consistent with the version of the privacy policy, no reminder can be selected. When the version of the target application is inconsistent with the version of the privacy policy, the updated content can be displayed through a pop-up window to inform the user that the privacy policy of the current version of the target application has changed.

[0082] Figure 5 Shows a schematic structural diagram of a system for determining a privacy policy provided by an exemplary embodiment of the present application. Refer to Figure 5 , the system 500 includes a main control module 51, an application analysis module 52, an abnormal data analysis module 53, a data classification and grading module 54, a protection strategy warning module 55, a privacy policy update module 56, a privacy policy database 57, a data collection strategy library 58, and a data protection strategy library 59.

[0083] Among them, the main control module 51 is used to control other modules. The application analysis module 52 is used to analyze whether there are changes in the data collection content of the target application. The abnormal data analysis module 53 is used to analyze whether there are behaviors beyond the data collection scope of the target application according to the data collection policy library 58, and initiate data verification if so. The data classification and grading module 54 is used to classify and grade the data, and compare the current protection policy of the data with the protection policies in the data protection policy library 59. The protection policy warning module 55 is used to warn of abnormal protection policies, analyze and warn of abnormal data protection measures. The privacy policy update module 56 is used to update the privacy policy.

[0084] Figure 6 Fig. shows a flowchart of another method for determining a privacy policy provided by an exemplary embodiment of the present application. This method can be applied to the above-mentioned privacy policy determination system. Refer to Figure 6 , and this method includes the following steps:

[0085] Step 601: Start the application, and determine whether there is a corresponding target version privacy policy in the privacy policy database according to the target MD5 value of the application. If it exists, obtain the target version privacy policy and display it. If it does not exist, execute step 602.

[0086] Step 602: Decompile the Android system installation package to obtain data collection permissions and interfaces, and collect data according to the data collection permissions and interfaces.

[0087] Among them, if data cannot be accurately collected through the data collection permissions and interfaces, data can be determined and collected through the data collection permissions, interfaces, and code call stack.

[0088] Step 603: Determine whether the collected data matches the field feature values corresponding to the historical version privacy policy. If so, establish a first correspondence between the target MD5 value and the historical version privacy policy, and store it in the privacy policy database. If not, execute step 604.

[0089] Step 604: Determine whether the collected data has increased or decreased according to the field feature values corresponding to the historical version privacy policy. If it has decreased, modify the historical privacy policy, establish a second correspondence between the target MD5 value and the historical privacy policy, and store it in the privacy policy database. If it has increased, execute step 605.

[0090] Step 605: Determine whether the scope of the collected data is the minimum necessary data collection scope through the data collection policy library. If not, report a first warning message, which is used to indicate modifying the first data collection scope. If so, execute step 606.

[0091] Step 606: Divide the collected data and determine whether the first protection policy of the classified data matches the second protection policy in the data protection policy library. If not, report a second warning message, which is used to indicate modifying the first protection policy according to the second protection policy in the data protection policy library. If so, execute Step 607.

[0092] Step 607: Modify the historical privacy policy, establish a third correspondence between the target MD5 value and the historical privacy policy, and store it in the privacy policy database.

[0093] Through the embodiments of the present application, it is possible to quickly determine the matching degree between the current and historical version privacy policies based on the MD5 value, and to update the current version privacy policy of the application in a timely manner to ensure that the implementation of the application function is consistent with the relevant content in the privacy policy. And it is possible to protect the collected data.

[0094] The embodiments of the present application also provide an electronic device. Figure 7 The following shows a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application. Refer to Figure 7 This electronic device is used to execute the above method for determining the privacy policy. Figure 7 The following is a schematic structural diagram of an electronic device for implementing various embodiments of the present application. The electronic device may vary greatly due to different configurations or performances, and may include a processor 701, a communication interface 702, a memory 703, and a communication bus 704. Among them, the processor 701, the communication interface 702, and the memory 703 communicate with each other through the communication bus 704. The processor 701 can call a computer program stored in the memory 703 and running on the processor 701 to execute each step of the above embodiments of the method for determining the privacy policy, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0095] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals, or other devices other than terminals.

[0096] The above structure of the electronic device does not limit the electronic device. The electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements. For example, the input unit may include a Graphics Processing Unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes at least one of a touch panel and other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, power on / off keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0097] The memory can be used to store software programs and various data. The memory mainly includes a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area can store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory can include volatile memory or non-volatile memory, or the memory can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM).

[0098] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor either.

[0099] The embodiments of the present application also provide a readable storage medium, in which at least one computer program is stored. The computer program is loaded and executed by the processor to implement all or part of the steps in the above-mentioned method for determining the privacy policy. For example, the readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0100] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, article or device including that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0101] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc), and includes several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the various embodiments of the present application.

[0102] Other embodiments of the present application will be readily apparent to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the claims.

[0103] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A method for determining a privacy policy, characterized in that, Including: Obtain a target hash value corresponding to a target application; Obtain a target version privacy policy corresponding to the target hash value from a privacy policy database according to the target hash value; Update the current version privacy policy of the target application according to the target version privacy policy; Wherein, the privacy policy database includes a correspondence between hash values and privacy policy versions.

2. The method according to claim 1, wherein After obtaining the target hash value corresponding to the target application, the method further includes: In the case that there is no target version privacy policy corresponding to the target hash value in the privacy policy database, obtain first data collected by the target application based on each first function and field feature values corresponding to each second function in the historical privacy policy of the target application, where each of the second functions is a function corresponding to each of the first functions in the historical privacy policy; and / or In the case that the field feature values match the first data, establish a first correspondence between the target hash value and the historical privacy policy, and store the first correspondence in the privacy policy database.

3. The method according to claim 1, wherein After obtaining the target hash value corresponding to the target application, the method further includes: In the case that there is no target version privacy policy corresponding to the target hash value in the privacy policy database, obtain first data collected by the target application based on each first function and field feature values corresponding to each second function in the historical privacy policy of the target application, where each of the second functions is a function corresponding to each of the first functions in the historical privacy policy; In the case that the field feature values do not match the first data, update the historical privacy policy according to the difference between the first data and the field feature values; Establish a second correspondence between the target hash value and the updated historical privacy policy, and store the second correspondence in the privacy policy database.

4. The method according to claim 3, wherein The updating the historical privacy policy according to the difference between the first data and the field feature values includes: In the case that the first data collection range of the first function is smaller than the second data collection range of the second function, reduce the second data collection range of the second function in the historical privacy policy to be the same as the first data collection range; Wherein, the second data collection range is determined according to the field feature values.

5. The method according to claim 3, characterized in that, The updating the historical privacy policy according to the difference between the first data and the field feature values includes: In the case that the first quantity of each of the first functions is smaller than the second quantity of each of the second functions, and / or in the case that the purpose of the first function is different from the purpose of the second function, reduce the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or change the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function.

6. The method according to claim 3, characterized in that Updating the historical privacy policy according to the difference between the first data and the field feature value includes: In the case where the first data collection scope of the first function is greater than the second data collection scope of the second function, determining whether the first data collection scope is the minimum necessary data collection scope through a data collection strategy library; In the case where the first data collection scope is the minimum necessary data collection scope, increasing the second data collection scope of the second function to be the same as the first data collection scope; Wherein, the data collection strategy library includes the minimum necessary data collection scope of each of the first functions.

7. The method according to claim 3, wherein Updating the historical privacy policy according to the difference between the first data and the field feature value includes: In the case where the first quantity of each of the first functions is greater than the second quantity of each of the second functions, and / or in the case where the purpose of the first function is different from the purpose of the second function, determining whether the first data collection scope is the minimum necessary data collection scope through a data collection strategy library; In the case where the first data collection scope is the minimum necessary data collection scope, increasing the second quantity of the second function in the historical privacy policy to be the same as the first quantity, and / or changing the purpose of the second function in the historical privacy policy to be the same as the purpose of the first function; Wherein, the data collection strategy library includes the minimum necessary data collection scope of each of the first functions.

8. The method according to claim 6 or 7, characterized in that, In the case where the first data collection scope is the minimum necessary data collection scope, the method further includes: Dividing the first data into second data at different levels according to a classification and grading rule; Generating a first warning message in the case where the first protection strategy of the second data at different levels does not match the second protection strategy in the data protection strategy library; Wherein, the data protection strategy library includes the second protection strategy corresponding to the first protection strategy of the second data at different levels; the first warning message is used to indicate modifying the first protection strategy of the second data according to the second protection strategy in the data protection strategy library.

9. The method according to claim 6 or 7, characterized in that, After determining whether the first data collection scope is the minimum necessary data collection scope through the data collection strategy library, the method further includes: Generating a second warning message in the case where the first data collection scope is not the minimum necessary data collection scope; Wherein, the second warning message is used to indicate modifying the first data collection scope.

10. The method according to any one of claims 3 to 7, characterized in that The method further includes: Displaying the updated historical privacy policy on the user interface of the target application.

11. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the method for determining a privacy policy according to any one of claims 1 to 10 are implemented.

12. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method for determining a privacy policy according to any one of claims 1 to 10 are implemented.

Images