CN112835613B - APP privacy policy content management method - Google Patents
APP privacy policy content management method Download PDFInfo
- Publication number
- CN112835613B CN112835613B CN202110125795.9A CN202110125795A CN112835613B CN 112835613 B CN112835613 B CN 112835613B CN 202110125795 A CN202110125795 A CN 202110125795A CN 112835613 B CN112835613 B CN 112835613B
- Authority
- CN
- China
- Prior art keywords
- privacy policy
- information
- background
- packaging
- policy file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title abstract description 18
- 238000004806 packaging method and process Methods 0.000 claims abstract description 63
- 238000000034 method Methods 0.000 claims description 44
- 238000012790 confirmation Methods 0.000 claims description 30
- 238000009434 installation Methods 0.000 claims description 4
- 238000013500 data storage Methods 0.000 abstract description 4
- 238000012856 packing Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The invention relates to an APP privacy policy content management method, which comprises the following steps: s1, inputting all packaged basic information into an information data repository of a privacy policy background; s2, selecting a first parameter name contained in the packaging basic information in the packaging background, and requesting the privacy policy background to acquire the packaging basic information matched with the first parameter name by the packaging background through the first parameter name; s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from the information data storage library through the second parameter name contained in the first parameter name and acquires the privacy information related to the privacy policy in the packaging basic information; s4, the privacy policy background updates the privacy information to the privacy policy template, generates a first version number, adds the first version number to the privacy policy template to generate a privacy policy file, and returns the privacy policy file to the packaging background. Therefore, the privacy policy files can be uniformly updated and managed through the privacy policy background.
Description
Technical Field
The invention relates to the field of computer software, in particular to an APP privacy policy content management method.
Background
At present, the quantity and the channel quantity of the APP product of the great internet company of scale are more, because the difference that market intermodal and SDK function introduced leads to each channel of each APP product all need manual according to the SDK condition of using independently edit a privacy policy file, and is consuming time hard and difficult to maintain, very easily because the untimely and incomplete initiation problem of update, and easily because the numerous condition of appearing updating the omission of APP product quantity. In addition, each version and each channel of each APP product need to maintain a latest privacy policy file, so that the third-party SDK introduced into the privacy policy file is not updated timely due to negligence of personnel, new permission is not applied and not declared timely, the APP product is detected out, violation collection user information is collected, and loss caused by off-shelf application of the APP product is caused.
Disclosure of Invention
Technical problem to be solved
In order to solve the above problems in the prior art, the invention provides a method for managing the content of an APP privacy policy, which facilitates the management of privacy policy files of APP products.
(II) technical scheme
In order to achieve the purpose, the invention adopts a technical scheme that: a method of APP privacy policy content management, comprising:
s1, inputting all packaged basic information into an information data repository of a privacy policy background;
s2, selecting a first parameter name contained in the packaging basic information in a packaging background, and requesting the privacy policy background to acquire the packaging basic information adapted to the first parameter name by the packaging background through the first parameter name;
s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from an information data repository through a second parameter name contained in the first parameter name and acquires privacy information related to a privacy policy in the packaging basic information;
and S4, the privacy policy background updates the privacy information into a privacy policy template, generates a first version number, adds the first version number into the privacy policy template to generate a privacy policy file, and returns the privacy policy file to the packaging background.
(III) advantageous effects
The invention has the beneficial effects that: the method comprises the steps that packaging basic information of an APP product is input into an information data repository of a privacy policy background to be managed, when a privacy policy file needs to be updated, only basic packaging information corresponding to the APP product needs to be inquired through a parameter name, privacy information related to a privacy policy is obtained from the packaging basic information, and the privacy information is updated into a policy template, so that a new privacy policy file can be generated. Therefore, the method and the device only need to manage the packaging basic information of the APP product in the information data storage of the privacy policy background, and the packaging basic information can be locally updated only after being updated in the privacy policy background, so that the management and the updating of the privacy policy file of the APP product are facilitated.
Drawings
FIG. 1 is a flow chart of a method for APP privacy policy content management in accordance with the present invention.
Detailed Description
For the purpose of better explaining the present invention and to facilitate understanding, the present invention will be described in detail by way of specific embodiments with reference to the accompanying drawings.
Referring to fig. 1, a method for APP privacy policy content management includes:
s1, inputting all packaged basic information into an information data repository of a privacy policy background;
s2, selecting a first parameter name contained in the packaging basic information in a packaging background, and requesting the privacy policy background to acquire the packaging basic information adapted to the first parameter name by the packaging background through the first parameter name;
s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from an information data repository through a second parameter name contained in the first parameter name and acquires privacy information related to a privacy policy in the packaging basic information;
and S4, the privacy policy background updates the privacy information into a privacy policy template, generates a first version number, adds the first version number into the privacy policy template to generate a privacy policy file, and returns the privacy policy file to the packaging background.
From the above description, the beneficial effects of the present invention are: the method comprises the steps that packaging basic information of an APP product is input into an information data repository of a privacy policy background to be managed, when a privacy policy file needs to be updated, only basic packaging information corresponding to the APP product needs to be inquired through a parameter name, privacy information related to a privacy policy is obtained from the packaging basic information, and the privacy information is updated into a policy template, so that a new privacy policy file can be generated. Therefore, the method and the device only need to manage the packaging basic information of the APP product in the information data storage of the privacy policy background, and the packaging basic information can be locally updated only after being updated in the privacy policy background, so that the management and the updating of the privacy policy file of the APP product are facilitated.
Further, the step S4 is followed by:
and S5, after receiving the privacy policy file, the packaging background sends the privacy policy file to a specified position in an APP installation package in the client.
As can be seen from the above description, the privacy policy file can be pushed to the specified position in the APP installation package in the client through the packaging background, and local update of the privacy policy file of the APP in the client can be completed.
Further, the packing basic information includes: basic information of the product, sub-channel use SDK information of the product, third-party SDK information, basic information of a public company and template information;
the basic information of the product comprises: the product issuing company name, the product ID, the product basic function point and the authority required by the product basic function point;
the SDK information used by the product sub-channels comprises: product ID, channel name, third party SDK name used;
the third-party SDK information includes: the name of the SDK, authority information used by the SDK, the function of the SDK and an independent privacy policy address of the SDK;
the management of the public company basic information includes: company name, company contact address, company and contact address;
the template information includes: a privacy policy template, the privacy policy template containing template information of a public part of a privacy policy;
the first parameter name includes: a product name, a channel name, and a second version number;
the second parameter name includes: product name and channel name.
Further, still include:
s61, after the client installs the privacy policy file, detecting whether the client is installed for the first time;
if yes, starting a popup confirmation process of the privacy policy file;
if not, go to S62;
s62, judging whether the first version number of the privacy policy file is consistent with the third version number of the local privacy policy file;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, go to S63;
s63, judging whether the client confirms the popup confirmation process of the privacy policy file or not;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
As can be seen from the above description, the pop-up window confirmation process for confirming the privacy policy file can be completed after the client is installed.
Further, the step S4 is followed by:
s41, after a new privacy policy file is generated, configuring the version range of the client to be updated in the packaging background;
s42, after the client is started, the client automatically requests the privacy policy background to inquire whether a new privacy policy file matched with the version of the client exists;
if so, updating the new privacy policy file to the local part of the client, and replacing the old privacy policy file;
s43, after updating the new privacy policy file, the client side starts a popup confirmation process for checking whether the new privacy policy file is confirmed or not every time;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
From the above description, the client can automatically introduce the online updating mode of the privacy policy file version for updating management, once the privacy policy file of the old version is updated, the old version can be timely pushed to the remote client, and the packaging background is not needed to actively send the privacy policy to the client, so that the updating timeliness is ensured.
Example one
Referring to fig. 1, a method for APP privacy policy content management includes:
s1, inputting all packaged basic information into an information data repository of a privacy policy background;
s2, selecting a first parameter name contained in the packaging basic information in a packaging background, and requesting the privacy policy background to acquire the packaging basic information adapted to the first parameter name by the packaging background through the first parameter name;
s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from an information data repository through a second parameter name contained in the first parameter name and acquires privacy information related to a privacy policy in the packaging basic information;
and S4, the privacy policy background updates the privacy information into a privacy policy template, generates a first version number, adds the first version number into the privacy policy template to generate a privacy policy file, and returns the privacy policy file to the packaging background.
Wherein, the step S4 is followed by the step:
and S5, after receiving the privacy policy file, the packaging background sends the privacy policy file to a specified position in an APP installation package in the client.
Wherein the packing basic information includes: basic information of the product, sub-channel use SDK information of the product, third-party SDK information, basic information of a public company and template information;
the basic information of the product comprises: the product issuing company name, the product ID, the product basic function point and the authority required by the product basic function point;
the SDK information used by the product sub-channels comprises: product ID, channel name, third party SDK name used;
the third-party SDK information includes: the SDK name, the authority information used by the SDK, the function of the SDK and the independent privacy policy address of the SDK;
the management of the public company basic information includes: company name, company contact address, company and contact address;
the template information includes: a privacy policy template, the privacy policy template containing template information of a public part of a privacy policy;
the first parameter name includes: a product name, a channel name, and a second version number;
the second parameter name includes: product name and channel name.
Wherein, still include:
s61, after the client installs the privacy policy file, detecting whether the client is installed for the first time;
if yes, starting a popup confirmation process of the privacy policy file;
if not, go to S62;
s62, judging whether the first version number of the privacy policy file is consistent with the third version number of the local privacy policy file;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, go to S63;
s63, judging whether the client confirms the popup confirmation process of the privacy policy file or not;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
Example two
Referring to fig. 1, a method for APP privacy policy content management includes:
s1, inputting all packaged basic information into an information data repository of a privacy policy background;
s2, selecting a first parameter name contained in the packaging basic information in a packaging background, and requesting the privacy policy background to acquire the packaging basic information adapted to the first parameter name by the packaging background through the first parameter name;
s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from an information data repository through a second parameter name contained in the first parameter name and acquires privacy information related to a privacy policy in the packaging basic information;
and S4, the privacy policy background updates the privacy information into a privacy policy template, generates a first version number, adds the first version number into the privacy policy template to generate a privacy policy file, and returns the privacy policy file to the packaging background.
Wherein, the step S4 is followed by the step:
s41, after a new privacy policy file is generated, configuring the version range of the client to be updated in the packaging background;
s42, after the client is started, the client automatically requests the privacy policy background to inquire whether a new privacy policy file matched with the version of the client exists;
if so, updating the new privacy policy file to the local part of the client, and replacing the old privacy policy file;
s43, after updating the new privacy policy file, the client side starts a popup confirmation process for checking whether the new privacy policy file is confirmed or not every time;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
Wherein the packing basic information includes: basic information of the product, sub-channel use SDK information of the product, third-party SDK information, basic information of a public company and template information;
the basic information of the product comprises: the product issuing company name, the product ID, the product basic function point and the authority required by the product basic function point;
the SDK information used by the product sub-channels comprises: product ID, channel name, third party SDK name used;
the third-party SDK information includes: the name of the SDK, authority information used by the SDK, the function of the SDK and an independent privacy policy address of the SDK;
the management of the basic information of the public company comprises the following steps: company name, company contact address, company and contact address;
the template information includes: a privacy policy template, the privacy policy template containing template information of a public part of a privacy policy;
the first parameter name includes: a product name, a channel name, and a second version number;
the second parameter name includes: product name and channel name.
Wherein, still include:
s61, after the client installs the privacy policy file, detecting whether the client is installed for the first time;
if yes, starting a popup confirmation process of the privacy policy file;
if not, go to S62;
s62, judging whether the first version number of the privacy policy file is consistent with the third version number of the local privacy policy file;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, go to S63;
s63, judging whether the client confirms the popup confirmation process of the privacy policy file or not;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
In summary, according to the method for managing the content of the APP privacy policy provided by the present invention, the packaged basic information of the APP product is entered into the information data repository of the privacy policy background for management, and when the privacy policy file needs to be updated, only the basic packaged information corresponding to the APP product needs to be queried through the parameter name, and the privacy information related to the privacy policy is obtained from the packaged basic information and is updated into the policy template, so that a new privacy policy file can be generated. Therefore, the method and the device only need to manage the packaging basic information of the APP product in the information data storage of the privacy policy background, and the packaging basic information can be locally updated only after being updated in the privacy policy background, so that the management and the updating of the privacy policy file of the APP product are facilitated.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (2)
1. A method for APP privacy policy content management, comprising:
s1, inputting all packaged basic information into an information data repository of a privacy policy background;
s2, selecting a first parameter name contained in the packaging basic information in a packaging background, and requesting the privacy policy background to acquire the packaging basic information adapted to the first parameter name by the packaging background through the first parameter name;
s3, the privacy policy background receives the request, and the privacy policy background inquires the packaging basic information from an information data repository through a second parameter name contained in the first parameter name and acquires privacy information related to a privacy policy in the packaging basic information;
s4, the privacy policy background updates the privacy information into a privacy policy template, generates a first version number, adds the first version number into the privacy policy template to generate a privacy policy file, and returns the privacy policy file to a packaging background;
the S4 further includes:
s41, after a new privacy policy file is generated, configuring the version range of the client to be updated in the packaging background;
s42, after the client is started, the client automatically requests the privacy policy background to inquire whether a new privacy policy file matched with the version of the client exists;
if so, updating the new privacy policy file to the local part of the client, and replacing the old privacy policy file;
s43, after updating the new privacy policy file, the client side starts a popup confirmation process for checking whether the new privacy policy file is confirmed or not every time;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file;
s5, after receiving the privacy policy file, the packaging background sends the privacy policy file to a specified position in an APP installation package in a client;
s61, after the client installs the privacy policy file, detecting whether the client is installed for the first time;
if yes, starting a popup confirmation process of the privacy policy file;
if not, go to S62;
s62, judging whether the first version number of the privacy policy file is consistent with the third version number of the local privacy policy file;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, go to S63;
s63, judging whether the client confirms the popup confirmation process of the privacy policy file or not;
if yes, not starting a popup confirmation process of the privacy policy file;
if not, starting a popup confirmation process of the privacy policy file.
2. The method of APP privacy policy content management according to claim 1, wherein the packaging base information comprises: basic information of the product, sub-channel use SDK information of the product, third-party SDK information, basic information of a public company and template information;
the basic information of the product comprises: the product issuing company name, the product ID, the product basic function point and the authority required by the product basic function point;
the SDK information used by the product sub-channels comprises: product ID, channel name, third party SDK name used;
the third-party SDK information includes: the name of the SDK, authority information used by the SDK, the function of the SDK and an independent privacy policy address of the SDK;
the management of the public company basic information includes: company name, company contact address, company and contact address;
the template information includes: a privacy policy template, the privacy policy template containing template information of a public part of a privacy policy;
the first parameter name includes: a product name, a channel name, and a second version number;
the second parameter name includes: product name and channel name.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110125795.9A CN112835613B (en) | 2021-01-29 | 2021-01-29 | APP privacy policy content management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110125795.9A CN112835613B (en) | 2021-01-29 | 2021-01-29 | APP privacy policy content management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112835613A CN112835613A (en) | 2021-05-25 |
| CN112835613B true CN112835613B (en) | 2022-05-17 |
Family
ID=75931060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110125795.9A Active CN112835613B (en) | 2021-01-29 | 2021-01-29 | APP privacy policy content management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112835613B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113435173B (en) * | 2021-05-28 | 2023-03-10 | 荣耀终端有限公司 | Text generation method, related device and system |
| CN113254923B (en) * | 2021-06-25 | 2021-10-26 | 南京网眼信息技术有限公司 | Method and system for generating privacy policy text according to APK (android package) |
| CN113703810B (en) * | 2021-09-02 | 2024-04-05 | 维沃移动通信有限公司 | Updating method and device |
| CN113822036B (en) * | 2021-09-28 | 2022-07-12 | 百度在线网络技术（北京）有限公司 | Privacy policy content generation method and device and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104881616A (en) * | 2015-06-29 | 2015-09-02 | 北京金山安全软件有限公司 | Privacy information storage method and device based on application program |
| CN112199506A (en) * | 2020-11-10 | 2021-01-08 | 支付宝(杭州)信息技术有限公司 | Information detection method, device and equipment for application program |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| SE0202057D0 (en) * | 2002-07-02 | 2002-07-02 | Ericsson Telefon Ab L M | Cookie receipt header |
-
2021
- 2021-01-29 CN CN202110125795.9A patent/CN112835613B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104881616A (en) * | 2015-06-29 | 2015-09-02 | 北京金山安全软件有限公司 | Privacy information storage method and device based on application program |
| CN112199506A (en) * | 2020-11-10 | 2021-01-08 | 支付宝(杭州)信息技术有限公司 | Information detection method, device and equipment for application program |
Non-Patent Citations (1)
| Title |
|---|
| 《NDK开发：保存App私密信息成So库，使用加载动态连接库获取私密信息》;技术承载梦想;《https://blog.csdn.net/u013823101/article/details/88532721》;20190313;第1-5页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112835613A (en) | 2021-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112835613B (en) | APP privacy policy content management method | |
| CN106886423B (en) | Method and apparatus for distributing Loadable Software Aircraft Parts (LSAP) | |
| US8631014B2 (en) | Method and system for integrated asset management | |
| US6886017B1 (en) | System and method for managing distribution of content to a device | |
| US7139737B2 (en) | Apparatus and method for managing software licenses and storage medium storing a program for managing software licenses | |
| US10127218B2 (en) | Object templates for data-driven applications | |
| US9069805B2 (en) | Migration of business object data in parallel with productive business application usage | |
| US20080005787A1 (en) | Software Distribution and License Management System | |
| KR20030037123A (en) | Platform Independent Software Automatic Searching/Distribution/Install Apparatus and The method of Searching and Distribution for that apparatus | |
| WO2020015191A1 (en) | Business rule releasing and managing method, electronic device and readable storage medium | |
| AU2014305816B2 (en) | Migrating data for web content management systems | |
| CN114385759A (en) | Configuration file synchronization method and device, computer equipment and storage medium | |
| CN104506628A (en) | Plugin repository management method and system | |
| JP2005523515A (en) | Method and system for managing a computer system | |
| US9658845B2 (en) | Generating a where-used objects list for updating data | |
| US8898626B2 (en) | System and method for managing a software asset for inclusion in a software library | |
| US20150379439A1 (en) | Integrated and intrinsic intellectual property management | |
| CN112015454B (en) | System upgrade package generation method and device, electronic equipment and storage medium | |
| CN110018835B (en) | YANG model configuration data processing method and device, terminal device and storage medium | |
| KR20110117560A (en) | System and method for providing automatically update | |
| CN113220633A (en) | Unified file coding management method and system | |
| US9720919B1 (en) | System and method of assessing the state of a database product for installation consistency | |
| CN111078252A (en) | Application publishing and automatic updating method based on terminal application | |
| CN109446159B (en) | Multi-version file management method, server and computer readable storage medium | |
| CN112883695A (en) | Method, device, equipment and medium for generating report template and displaying data report |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |