Data processing method and device in privacy mode of browser

Abstract

The invention relates to the technical field of electronic information, in particular to a data processing method and device in a privacy mode of a browser, and the method comprises the steps that a target browser is started, and the target browser is in the privacy mode; a target plug-in is loaded in the target browser, and the target plug-in is used for receiving access information logged in by a user through the target browser in the privacy mode; and running the target plug-in to monitor an access process in the target browser to obtain a target access data set, the target access data set comprising at least one piece of access information, and the target access data set being located in the target plug-in. According to the method, on the premise of not invading the privacy of the user, monitoring and data collection are carried out on the browser activity in the privacy mode, so that the protection of the privacy of the user is ensured, and meanwhile, the security review requirement in a specific environment is met.

Description

Technical Field

[0001] The present application relates to the field of electronic information technology, and in particular to a method and device for processing data in a browser privacy mode. Background Art

[0002] In today's highly developed Internet era, the importance of personal privacy protection has become increasingly prominent. In response to this demand, many web browsers, including but not limited to Chrome, Firefox, Safari, etc., have launched private mode or incognito browsing functions to prevent users' online behavior from being tracked and recorded. This mode effectively prevents the saving of history, cookies, cache and form data, so that after the user closes the private window or tab, no trace of online browsing will be left.

[0003] Nevertheless, the widespread use of privacy mode also brings certain challenges. In specific scenarios such as enterprise network environments, family education monitoring, and personal security audits, it has become an urgent need to legally and compliantly obtain and analyze users' online behavior in privacy mode. Existing technical means often cannot effectively record and review users' network activities when users enable privacy mode, making it difficult for security managers to identify and prevent potential network risks.

[0004] Currently, traditional data review methods and technologies, such as WebActivity API or C++-based monitoring programs, cannot work in privacy mode because the browser's privacy protection mechanism prevents these tools from capturing user access records. This technical limitation makes it difficult to meet security review requirements in specific environments while protecting user privacy, thus exposing the difficulty of balancing privacy protection and security monitoring in existing technical solutions. Summary of the invention

[0005] One purpose of an embodiment of the present invention is to provide a data processing method and device in a browser privacy mode, so as to solve the technical problem that existing browsers cannot meet specific security review requirements while ensuring user privacy.

[0006] In a first aspect, an embodiment of the present invention provides a method for processing data in a browser privacy mode, the method comprising: Launching a target browser, wherein the target browser is in a privacy mode; Loading a target plug-in in the target browser, the target plug-in being used to receive access information of a user logging in through the target browser in the privacy mode; The target plug-in is run to monitor the access process in the target browser to obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

[0007] In a second aspect, an embodiment of the present invention provides a data processing device in a browser privacy mode, the device comprising: A starting unit, used for starting a target browser, wherein the target browser is in a privacy mode; A loading unit, configured to load a target plug-in in the target browser, wherein the target plug-in is configured to receive access information of a user logging in through the target browser in the privacy mode; The running unit is used to run the target plug-in to monitor the access process in the target browser and obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

[0008] In a third aspect, an embodiment of the present invention provides a computer device, including: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to the first aspect.

[0009] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the method as described in the first aspect.

[0010] In the scheme implemented by the data processing method and device in the above-mentioned browser privacy mode, the method first starts the target browser, the target browser is in the privacy mode, and then loads the target plug-in in the target browser, the target plug-in is used to receive the access information of the user logging in through the target browser in the privacy mode, and finally, runs the target plug-in to monitor the access process in the target browser to obtain the target access data set, the target access data set includes at least one access information, and the target access data set is located in the target plug-in. The method allows the monitoring and data collection of browser activities in the privacy mode without infringing the user's privacy, ensuring the protection of user privacy while meeting the security review requirements in a specific environment. Further, the target plug-in can receive the user's access information in the privacy mode, providing technical means for specific security review requirements, so that while protecting user privacy, it can also meet the needs of supervision or auditing, and the target access data set is located in the target plug-in, realizing the centralized management and storage of access information, facilitating subsequent data analysis and processing, and also improving the security of the data. Further, since the target plug-in only runs in the privacy mode, it will not interfere with the user's browsing experience in the normal mode, thereby protecting the user's privacy while maintaining the fluency and ease of use of the browser. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0012] Figure 1 It is a flowchart of a data processing method in a browser privacy mode in one embodiment of the present invention; Figure 2 is a schematic diagram of the structure of a data processing device in a browser privacy mode in one embodiment of the present invention; Figure 3 It is a schematic diagram of the structure of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0013] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0014] It should be noted that, if there is no conflict, the various features in the embodiments of the present invention can be combined with each other, all within the scope of protection of the present invention. In addition, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in a different order from the module division in the device or the flow chart. Furthermore, the words "first", "second", "third", etc. used in the present invention do not limit the data and execution order, but only distinguish the same items or similar items with basically the same functions and effects.

[0015] The technical solution of the present application can be applied to various browser scenarios.

[0016] In view of this, the present application proposes a data processing method in the browser privacy mode to solve the above problems, which is described in detail below.

[0017] See also Figure 1 , Figure 1 A flowchart of a data processing method in a browser privacy mode provided by an embodiment of the present invention, the method comprising the following steps: S10. Start a target browser, which is in a privacy mode.

[0018] The target browser may be the Chrome browser, which is not a sole limitation.

[0019] Here, launching refers to the operation of opening a browser, and the user can perform this operation by double-clicking the browser shortcut, selecting the browser from the start menu, or using any other method to open an application.

[0020] Among them, private mode, also known as incognito mode, is a browser feature that allows users to surf the Internet without saving browsing history, cookies, cache, and other website data. The purpose of using private mode is to protect the user's privacy and ensure that no traces are left after the session ends. Therefore, in private mode, the user's browsing activities will not be permanently recorded by the browser.

[0021] Furthermore, when the browser is in private mode, it will not store any user data on the local computer, or at least limit the storage of data to prevent other users or programs from accessing this information.

[0022] It can be seen that in this embodiment, starting the browser and placing it in privacy mode is an important prerequisite, which ensures that the user's privacy will not be violated even when the user's web page access behavior is recorded.

[0023] S20. Load a target plug-in in the target browser, where the target plug-in is used to receive access information of a user logging in through the target browser in the privacy mode.

[0024] Loading refers to the process of installing a plug-in into a browser and making it operational. This is usually done through the browser's extension management page, where users can choose to add downloaded plug-in files or install them directly from the browser's online app store.

[0025] The target plug-in refers to a browser extension specially designed to implement the functions of the present invention. It contains the necessary code and resources to perform specific tasks in the browser. Specifically, the role of the target plug-in is to monitor and record the browsing behavior of users in privacy mode, including information such as the URLs visited by users, page titles, and access times. In this way, the target plug-in can receive and process the user's access information in privacy mode to support compliance data review requirements.

[0026] Therefore, the target plugin's functionality and code must be compatible with and not invalidated by the privacy mode's restrictions.

[0027] Receiving refers to the target plug-in's ability to capture and process information entered by the user during the login process, such as username, password, and other data that may be used for authentication.

[0028] Among them, access information may include but is not limited to the websites visited by users, login time, session duration, etc.

[0029] When receiving this information, the target plug-in needs to ensure that its operations comply with privacy protection requirements and do not leak sensitive information of users.

[0030] It can be seen that in this embodiment, the target plug-in is enabled in the privacy mode of the browser to receive and process the user's access information in the privacy mode, thereby supporting compliance data review requirements.

[0031] S30: Run the target plug-in to monitor the access process in the target browser and obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

[0032] Running refers to activating the monitoring function of the plug-in and starting it to work. This usually happens after the user installs and authorizes the plug-in, or it is automatically executed when the browser is started. The purpose of running the target plug-in is to monitor the user's browsing behavior in real time in the privacy mode of the target browser.

[0033] Among them, monitoring means that the plug-in continuously tracks and records the user's activities in the browser, including the web pages opened, the operations performed, the data entered, etc.

[0034] The access process may include each user's interactive behavior such as page loading, form submission, and click events.

[0035] The target access dataset is a set of multiple access information. Each access information usually includes the following fields: URL, which is the address of the web page visited by the user; title, which is the title of the web page; access time, which is the timestamp when the user visits the page. However, any information that can directly identify the user should be avoided to protect the user's privacy.

[0036] Furthermore, the target access dataset is stored in the plug-in's local storage, or uploaded to a remote server for further processing and analysis as needed. The target access dataset is stored in the plug-in's own storage space, rather than in the browser's regular storage location, to prevent the data from being cleared by the browser's own privacy mode, and also to protect the data from being accessed by other applications or users.

[0037] Among them, the target plug-in may use the browser extension API, such as chrome.webRequest or chrome.tabs, to capture necessary information when monitoring the access process.

[0038] It can be seen that in this embodiment, by running the target plug-in, the target browser can monitor the user's browsing behavior in real time in the privacy mode.

[0039] This method allows monitoring and data collection of browser activities in privacy mode without infringing user privacy, ensuring the protection of user privacy while meeting security review requirements in specific environments. Further, the target plug-in can receive user access information in privacy mode, providing technical means for specific security review requirements, so that while protecting user privacy, it can also meet the needs of supervision or auditing. The target access data set is located in the target plug-in, which realizes centralized management and storage of access information, facilitates subsequent data analysis and processing, and also improves data security. Furthermore, since the target plug-in only runs in privacy mode, it will not interfere with the user's browsing experience in normal mode, thereby protecting user privacy while maintaining the fluency and ease of use of the browser.

[0040] In one embodiment, loading a target plug-in in the target browser comprises: preloading the target plug-in in an extension management page of the target browser according to an insert instruction, the target plug-in comprising a plurality of permission rules; after the preloading is completed, displaying the plurality of permission rules required for authorization on a display interface of the target browser; obtaining a target instruction, the target instruction being used to indicate whether authorization of the plurality of permission rules is agreed; when the target instruction received indicates authorization is agreed, completing the preloading to obtain the loaded target plug-in, the loaded target plug-in executing a predetermined function in the privacy mode according to the plurality of permission rules.

[0041] The insertion instruction refers to an instruction issued by the user in some way (such as a command line, script, or other user interface) to instruct the browser to start the process of preloading the plug-in.

[0042] Among them, the extension management page is a page in the browser where users can manage installed plug-ins, including enabling, disabling or configuring them.

[0043] Preloading means that the browser loads the plug-in code and resources in advance before the plug-in function is fully activated, in preparation for subsequent authorization and operation.

[0044] The target plug-in contains multiple permission rules, which define the access rights required by the plug-in at runtime, such as reading browser tab information, storing data, etc.

[0045] Furthermore, once the preloading is completed, the browser will display a dialog box or page to the user on the interface, listing all permissions requested by the plug-in. The user can view these permission rules and decide whether to grant the plug-in the corresponding permissions.

[0046] Among them, obtaining the target instruction means that the plug-in or browser waits for the user to input the instruction. The target instruction is the user's agreement or rejection of the permission rule. The user usually issues the instruction by clicking the "Agree" or "Reject" button.

[0047] Specifically, when a target instruction that the user agrees to authorize is received, the preloading process is completed, the plug-in is officially loaded into the browser, and obtains the permissions required to execute the predetermined function.

[0048] Among them, after obtaining authorization, the target plug-in will perform its functions in privacy mode according to the permission rules, such as monitoring browsing activities, collecting data, etc. Execution in privacy mode means that the operation of the target plug-in will not leave browsing history, cache or cookies, thereby protecting the privacy of users.

[0049] It can be seen that in this embodiment, by displaying and authorizing multiple permission rules, the user can accurately control the functional scope of the plug-in and only allow the plug-in to perform operations that it deems necessary and safe, thereby enhancing the user's control over personal data; and in privacy mode, the target plug-in can effectively collect and analyze access data and provide support for data review without affecting the user's normal browsing experience, thereby improving the efficiency and accuracy of the review.

[0050] In one embodiment, the multiple permission rules include at least: allowing access to the current browser tab metadata, allowing storage of the browser page activity data in an offline environment, allowing temporary access to the currently activated tab, and allowing operation in the privacy mode.

[0051] Among them, allowing to obtain the tab metadata of the current browser means that the plug-in is authorized to access the basic information of each tab opened in the current browser. Tab metadata includes but is not limited to information such as URL, page title, tab ID, etc. The tab metadata is used to monitor the user's browsing behavior and record access status.

[0052] Among them, allowing the activity data of the browser page to be stored in an offline environment means that the plug-in can store the user's browsing activity data in the local storage when there is no network connection, ensuring that the plug-in can normally record the user's browsing behavior even in an offline environment.

[0053] The activity data includes, but is not limited to, the interaction data between the user and the page, such as input text, click events, scrolling behavior, etc.

[0054] Among them, allowing temporary access to the currently activated tab means that the target plug-in needs to temporarily access the currently activated tab to obtain detailed information about the tab and perform corresponding processing. This includes obtaining the URL and page content of the currently activated tab. Furthermore, temporary access should be strictly limited to cases where the user actively triggers it, and after the user leaves the tab or closes the target plug-in, the target plug-in should immediately lose access to the tab.

[0055] Among them, allowing to run in the privacy mode means that the target plug-in is authorized to perform its functions in the privacy mode of the browser. Privacy mode usually prohibits tracking, caching and saving browsing history, so this permission is crucial to ensure that the target plug-in can still provide necessary services while protecting user privacy. The operation of the target plug-in in privacy mode should follow additional privacy protection measures to ensure that no personal information of the user is leaked, and the user should clearly know which functions are available and which are not available in privacy mode.

[0056] It can be seen that in this embodiment, the permission rules are used to balance the functionality of the plug-in and the protection of user privacy, ensuring that the plug-in does not infringe on the privacy rights of users while providing convenience.

[0057] In one embodiment, the target plug-in is run to monitor the access process in the target browser to obtain a target access data set, including: running the target plug-in to obtain at least one tab that has been loaded in the target browser and tab metadata corresponding to each tab in the at least one tab; performing data processing on the at least one tab according to a preset random algorithm to obtain a fuzzy access time corresponding to each tab in the at least one tab; determining the tab metadata corresponding to each tab and the fuzzy access time corresponding to each tab as access information of each tab; storing the access information of each tab in an access record item corresponding to each tab to obtain a target access data set, the target access data set being stored in a global data structure of the target plug-in, the target access data set comprising multiple access record items, each access record item corresponding to a tab, and corresponding access information being stored in the access record item.

[0058] The target plug-in obtains this information through the browser's API (such as chrome.tabs), and this process is usually carried out after the user agrees to the plug-in permissions.

[0059] The preset random algorithm may include but is not limited to a random time generation algorithm, which is used to blur the actual access time to protect the privacy of the user.

[0060] Fuzzy access time refers to randomizing the actual access time through a preset random algorithm to protect user privacy. For example, if the actual access time is 10:15, the fuzzy access time generated by the random algorithm may be 10:12 or 10:18. The purpose of fuzzy access time is to reduce the traceability of user behavior while still providing enough information for data analysis.

[0061] The access information includes but is not limited to the URL, title, tab ID, and access time of the page after obfuscation.

[0062] Each tab creates an access record item to store the access information of the tab. The access record item is a data structure used to save the metadata and fuzzy access time of each tab.

[0063] Therefore, all access records form a target access data set, which contains the access information of all loaded tabs.

[0064] The global data structure is a data storage area in the target plug-in memory, which is used to save the access record items of all tabs. In the global data structure, each access record item corresponds to a tab page, storing the access information of the tab page, and the target plug-in can access and process these record items at any time.

[0065] It can be seen that in this embodiment, the target plug-in can obtain and process the tab data in the browser, generate fuzzy access time, and store the access information in the global data structure to form a target access data set containing multiple access record items.

[0066] In one embodiment, after determining that the tab metadata corresponding to each tab page and the fuzzy access time corresponding to each tab page are the access information of each tab page, the method further includes: determining the access time corresponding to each tab page based on the tab metadata corresponding to each tab page; formatting the access time corresponding to each tab page to obtain the target access time corresponding to each tab page; determining the tab metadata corresponding to each tab page, the fuzzy access time corresponding to each tab page and the target access time corresponding to each tab page as the access information of each tab page.

[0067] The access time can be the exact time when the user opens the tab, or it can be the time calculated from an event (such as when the page is loaded). For example, the actual access time of a tab is 21:00:00 on November 14, 2024.

[0068] Formatting refers to converting the access time into a specific format or adjusting it according to the time zone, such as converting the timestamp into a readable date and time format (such as YYYY-MM-DD HH:MM:SS). For example, the actual access time 2024-11-14 21:00:00 is formatted into the ISO 8601 format: 2024-11-14T21:00:00Z.

[0069] Optionally, the formatting process may also include time zone conversion, daylight saving time adjustment, etc., to ensure the accuracy and consistency of the time information.

[0070] Specifically, the metadata, fuzzy access time and target access time of each tab are combined to determine the complete access information of the tab. Therefore, the access information includes the URL, title, tab ID, fuzzy access time and target access time of the tab.

[0071] It can be seen that in this embodiment, a structured and easy-to-understand access information record is created while protecting the user's privacy. In this way, the plug-in can provide valuable access data without revealing the specific details of the user's behavior.

[0072] In one embodiment, obtaining at least one tab page that has been loaded in the target browser and tab page metadata corresponding to each tab page in the at least one tab page includes: monitoring the page status corresponding to each tab page in the target browser; when the page status of the target tab page is obtained as loading completed, collecting data corresponding to the target tab page to obtain tab page metadata corresponding to the target tab page; and continuously monitoring each tab page in the target browser to obtain at least one tab page that has been loaded and tab page metadata corresponding to each tab page in the at least one tab page.

[0073] The page status may include but is not limited to "loading", "loading completed", "failed", etc. For example, the browser API (such as Chrome's chrome.tabs.onUpdated event) is used to monitor the status changes of each tab.

[0074] Once the plug-in detects that the page status of a tab has changed to "loaded", the data collection process will be triggered. The collection process includes extracting metadata related to the tab, such as URL, title, icon, page content, etc. The collected data should be within the scope allowed by the plug-in permission rules and should follow the principle of privacy protection. For example, the plug-in may not collect sensitive personal information on the page.

[0075] Optionally, each tab page in the target browser is continuously monitored to ensure that all loaded tab pages can be obtained in time. Through continuous monitoring, all loaded tab pages and their corresponding tab page metadata are collected.

[0076] Continuous monitoring may involve setting up event listeners or polling mechanisms to respond to changes in the state of the tab in a timely manner. This process is dynamic and can handle situations such as users opening new tabs, closing existing tabs, or reloading tabs.

[0077] It can be seen that this embodiment ensures that the plug-in can accurately capture and record the user's activities in the browser while maintaining respect for the user's privacy. By monitoring the page status and collecting data in a timely manner, the plug-in can build a detailed tab metadata set for subsequent analysis and processing.

[0078] In one embodiment, after running the target plug-in to monitor the access process in the target browser and obtaining the target access data set, the method further includes: sending the target access data set to a server so that the server stores the target access data set, and the server has established a communication connection with the target browser; receiving a storage success instruction sent by the server, and deleting the target access data set in the target plug-in.

[0079] A communication connection has been established between the target browser and the server to ensure smooth data transmission. The target plug-in transmits data to the remote server via HTTP requests, WebSockets or other communication protocols.

[0080] Optionally, before sending data, the target plug-in should ensure that the data has been properly encrypted to protect user privacy and data transmission security; the server needs to have a corresponding interface to receive data, and the communication between the server and the browser should be secure, such as using the HTTPS protocol; before sending data, the target plug-in needs to check the user's privacy settings and permissions to ensure that the user agrees that the data is sent and stored.

[0081] After receiving the target access data set, the server stores the data. The server can use a database or other storage mechanism to save the data. After successfully storing the data set, the server sends a storage success instruction back to the target plug-in to notify the plug-in that the data has been successfully stored.

[0082] The confirmation instruction may refer to a simple success response or may include additional information such as a stored data ID or a timestamp.

[0083] After receiving the confirmation instruction, the target plug-in will delete the data from its internal storage. This is to save local storage space. The target plug-in deletes the locally stored target access data set to ensure that the data no longer occupies local resources and avoids storing unnecessary data locally to reduce potential privacy leakage risks. Before deleting data, the target plug-in should ensure that the server has indeed stored the data to prevent data loss.

[0084] Optionally, the target access data set may also be stored locally.

[0085] Local storage refers to saving data sets on the user's device instead of sending them to a server, for example, using the browser's LocalStorage, IndexedDB, Cookies, or the device's file system.

[0086] Among them, locally stored data sets can provide users with offline access capabilities, and users can access and use these data even if they are currently unable to connect to the Internet.

[0087] Optionally, after the target plug-in monitors and collects access data, it can be stored locally immediately before sending it to the server. Alternatively, when a connection with the server cannot be established, the target plug-in can save the data set locally first and upload it after the connection is restored.

[0088] It can be seen that this embodiment ensures that the user's access data in the browser can be securely transmitted to the server and properly stored on the server side, while leaving no trace locally, thereby protecting user privacy while achieving remote backup and centralized management of data.

[0089] It should be noted that, in each of the above-mentioned embodiments, there is not necessarily a certain order between the above-mentioned steps. A person skilled in the art can understand, based on the description of the embodiments of the present application, that in different embodiments, the above-mentioned steps may have different execution orders, that is, they may be executed in parallel, may be executed interchangeably, and so on.

[0090] As another aspect of the embodiment of the present application, the embodiment of the present application provides a data processing device in a browser privacy mode. The data processing device in the browser privacy mode can be a software module, and the software module includes a number of instructions, which are stored in a memory. The processor can access the memory and call the instructions for execution to complete the data processing method in the browser privacy mode described in the above-mentioned various embodiments.

[0091] See also Figure 2 , Figure 2 Schematic diagram of a data processing device in a browser privacy mode provided by an embodiment of the present application. Figure 2 As shown, the data processing device 200 in the browser privacy mode includes: A starting unit 201 is used to start a target browser, where the target browser is in a privacy mode; A loading unit 202, configured to load a target plug-in in the target browser, wherein the target plug-in is configured to receive access information of a user logging in through the target browser in the privacy mode; The running unit 203 is used to run the target plug-in to monitor the access process in the target browser and obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

[0092] This method allows monitoring and data collection of browser activities in privacy mode without infringing user privacy, ensuring the protection of user privacy while meeting security review requirements in specific environments. Further, the target plug-in can receive user access information in privacy mode, providing technical means for specific security review requirements, so that while protecting user privacy, it can also meet the needs of supervision or auditing. The target access data set is located in the target plug-in, which realizes centralized management and storage of access information, facilitates subsequent data analysis and processing, and also improves data security. Furthermore, since the target plug-in only runs in privacy mode, it will not interfere with the user's browsing experience in normal mode, thereby protecting user privacy while maintaining the fluency and ease of use of the browser.

[0093] In one embodiment, in loading the target plug-in in the target browser, the loading unit 202 is further used to: preload the target plug-in in the extension management page of the target browser according to the insertion instruction, the target plug-in including multiple permission rules; after the preloading is completed, display the multiple permission rules required for authorization on the display interface of the target browser; obtain a target instruction, the target instruction is used to indicate whether to agree to authorize the multiple permission rules; when the target instruction received is for agreeing to authorize, complete the preloading and obtain the loaded target plug-in, the loaded target plug-in performs a predetermined function in the privacy mode according to the multiple permission rules.

[0094] In one embodiment, the multiple permission rules include at least: allowing access to the current browser tab metadata, allowing storage of the browser page activity data in an offline environment, allowing temporary access to the currently activated tab, and allowing operation in the privacy mode.

[0095] In one embodiment, in the running of the target plug-in to monitor the access process in the target browser to obtain a target access data set, the running unit 203 is further used to: run the target plug-in to obtain at least one tab page that has been loaded in the target browser and the tab page metadata corresponding to each tab page in the at least one tab page; perform data processing on the at least one tab page according to a preset random algorithm to obtain the fuzzy access time corresponding to each tab page in the at least one tab page; determine the tab page metadata corresponding to each tab page and the fuzzy access time corresponding to each tab page as the access information of each tab page; store the access information of each tab page in the access record item corresponding to each tab page to obtain a target access data set, the target access data set is stored in the global data structure of the target plug-in, the target access data set includes multiple access record items, each access record item corresponds to a tab page, and the corresponding access information is stored in the access record item.

[0096] In one embodiment, after determining that the tab metadata corresponding to each tab page and the fuzzy access time corresponding to each tab page are the access information of each tab page, the running unit 203 is also used to: determine the access time corresponding to each tab page based on the tab metadata corresponding to each tab page; format the access time corresponding to each tab page to obtain the target access time corresponding to each tab page; determine the tab metadata corresponding to each tab page, the fuzzy access time corresponding to each tab page and the target access time corresponding to each tab page as the access information of each tab page.

[0097] In one embodiment, in the obtaining of at least one tab page that has been loaded in the target browser and the tab page metadata corresponding to each tab page in the at least one tab page, the running unit 203 is further used to: monitor the page status corresponding to each tab page in the target browser; when the page status of the target tab page is obtained as loading completed, collect data corresponding to the target tab page to obtain the tab page metadata corresponding to the target tab page; and continuously monitor each tab page in the target browser to obtain at least one tab page that has been loaded and the tab page metadata corresponding to each tab page in the at least one tab page.

[0098] In one embodiment, after the target access data set is obtained by running the target plug-in to monitor the access process in the target browser, the running unit 203 is further used to: send the target access data set to a server so that the server stores the target access data set, and the server has established a communication connection with the target browser; and upon receiving a storage success instruction sent by the server, delete the target access data set in the target plug-in.

[0099] It should be noted that the data processing device in the above-mentioned browser privacy mode can execute the data processing method in the browser privacy mode provided in the implementation mode of this application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not fully described in the implementation mode of the data processing device in the browser privacy mode, please refer to the data processing method in the browser privacy mode provided in the implementation mode of this application.

[0100] See also Figure 3 , Figure 3 3 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. The computer device includes one or more processors 31 and a memory 32. The memory 32 is connected to the one or more processors 31, for example, connected to the processor 31 via a bus.

[0101] The processor 31 is configured to support the computer device to perform the corresponding functions in the method in the above method embodiment. The processor 31 can be a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof. The above hardware chip can be an application specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0102] The memory 32 is used to store program codes, etc. The memory 32 may include a volatile memory (VM), such as a random access memory (RAM); the memory 32 may also include a non-volatile memory (NVM), such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); the memory 32 may also include a combination of the above-mentioned types of memories.

[0103] The memory 32 may be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions / modules corresponding to the data processing method in the browser privacy mode in the embodiment of the present application. The processor 31 executes the data processing method in the browser privacy mode and various functional applications and data processing of the data processing device in the browser privacy mode by running the non-volatile software programs, instructions and modules stored in the memory 32, that is, realizes the functions of the data processing method in the browser privacy mode and the various modules or units of the data processing device in the browser privacy mode provided in the above method embodiment.

[0104] The memory 32 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function. The data storage area may store data created according to the use of the data processing device in the browser privacy mode, etc. In some embodiments, the memory 32 may optionally include a memory 32 remotely arranged relative to the processor 31, and these remote memories 32 may be connected to the data processing device in the browser privacy mode via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0105] The one or more modules are stored in the memory 32, and when executed by the one or more processors 31, execute the data processing method in the browser privacy mode in any of the above-mentioned method embodiments, for example, execute the method steps described in the above-mentioned method embodiments to realize the functions of the modules described in the above-mentioned device embodiments.

[0106] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method described in the above embodiment.

[0107] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0108] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method in a browser privacy mode, characterized in that: The method comprises: Launching a target browser, wherein the target browser is in a privacy mode; Loading a target plug-in in the target browser, the target plug-in being used to receive access information of a user logging in through the target browser in the privacy mode; The target plug-in is run to monitor the access process in the target browser to obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

2. The method according to claim 1, characterized in that The step of loading a target plug-in in the target browser includes: Preloading the target plug-in in the extension management page of the target browser according to the insertion instruction, wherein the target plug-in includes a plurality of permission rules; After the preloading is completed, the multiple permission rules required for authorization are displayed on the display interface of the target browser; Obtaining a target instruction, where the target instruction is used to indicate whether to agree to authorize the multiple permission rules; When the target instruction received is for consent to authorization, the preloading is completed to obtain the loaded target plug-in, and the loaded target plug-in performs a predetermined function in the privacy mode according to the multiple permission rules.

3. The method according to claim 2, characterized in that The multiple permission rules include at least: allowing access to the current browser's tab metadata, allowing storage of the browser page's activity data in an offline environment, allowing temporary access to the currently activated tab, and allowing operation in the privacy mode.

4. The method according to claim 1, characterized in that: The running of the target plug-in to monitor the access process in the target browser to obtain a target access data set includes: Running the target plug-in to obtain at least one tab page that has been loaded in the target browser and tab page metadata corresponding to each tab page in the at least one tab page; According to a preset random algorithm, data processing is performed on the at least one tab page to obtain a fuzzy access time corresponding to each tab page in the at least one tab page; Determine the tab metadata corresponding to each tab and the fuzzy access time corresponding to each tab as the access information of each tab; The access information of each tab is stored in the access record item corresponding to each tab to obtain a target access data set. The target access data set is stored in the global data structure of the target plug-in. The target access data set includes multiple access record items, each access record item corresponds to a tab, and the corresponding access information is stored in the access record item.

5. The method according to claim 4, characterized in that After determining that the tab metadata corresponding to each tab and the fuzzy access time corresponding to each tab are the access information of each tab, the method further includes: Determining the access time corresponding to each tab page according to the tab page metadata corresponding to each tab page; Formatting the access time corresponding to each tab page to obtain the target access time corresponding to each tab page; The tab metadata corresponding to each tab, the fuzzy access time corresponding to each tab, and the target access time corresponding to each tab are determined as the access information of each tab.

6. The method according to claim 4, characterized in that The obtaining of at least one tab page that has been loaded in the target browser and tab page metadata corresponding to each tab page in the at least one tab page includes: Monitor the page status corresponding to each tab page in the target browser; When the page status of the target tab page is obtained to be loaded, data corresponding to the target tab page is collected to obtain tab page metadata corresponding to the target tab page; Each tab page in the target browser is continuously monitored to obtain at least one tab page that has been loaded and tab page metadata corresponding to each tab page in the at least one tab page.

7. The method according to claim 1 or 3, characterized in that: After running the target plug-in to monitor the access process in the target browser and obtaining the target access data set, the method further includes: Sending the target access data set to a server so that the server stores the target access data set, the server having established a communication connection with the target browser; After receiving a storage success instruction sent by the server, the target access data set is deleted in the target plug-in.

8. A data processing device in a browser privacy mode, the device comprising: A starting unit, used for starting a target browser, wherein the target browser is in a privacy mode; A loading unit, configured to load a target plug-in in the target browser, wherein the target plug-in is configured to receive access information of a user logging in through the target browser in the privacy mode; The running unit is used to run the target plug-in to monitor the access process in the target browser and obtain a target access data set, wherein the target access data set includes at least one access information and is located in the target plug-in.

9. A computer device, comprising a memory and a processor, wherein the memory is connected to the processor, and the processor is used to execute one or more computer programs stored in the memory, and when the processor executes the one or more computer programs, the computer device implements the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images