Program, method, information processing apparatus and system

Abstract

To provide a program, a method, an information processing apparatus, and a system for identifying electronic contents relating to a legal revision or a change in interpretation of a law.SOLUTION: In a system 1, a program for causing a server as an information processing apparatus, which is a computer equipped with a processor and a storage unit, to manage electronic contents includes: a content acquiring step in which the processor acquires one or more contents; an amendment acquiring step for acquiring amendment information relating to an amendment of a law revision or a change in interpretation of the law; and an amendment specifying step for specifying, among one or more contents acquired in the content acquiring step, one or more predetermined contents relating to the amendment information acquired in the amendment acquiring step.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, an information processing device, and a system. [Background technology]

[0002] When providing web services, application programs, apps, games, etc. (hereinafter referred to as "web services, etc.") via the Internet, a technology is known in which a provider presents users with terms of use that describe the conditions of use and other rules regarding the use of the services they provide to users. Patent Document 1 discloses a technique for making terms of use easier to read even when registering as a user on a mobile terminal such as a smartphone. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-005442 A Summary of the Invention [Problem to be solved by the invention]

[0004] One challenge is the inability to identify electronic content that is related to changes in the law or changes in the interpretation of the law. Therefore, the present disclosure has been made to solve the above problem, and has an object to provide a technology for identifying electronic content related to legal amendments or changes in the interpretation of laws. [Means for solving the problem]

[0005] A program having a processor and a memory unit, which causes a computer to manage electronic content, wherein the processor executes a content acquisition step of acquiring one or more pieces of content, an amendment acquisition step of acquiring amendment information relating to legal amendments or changes in the interpretation of law, and an amendment identification step of identifying, from the one or more pieces of content acquired in the content acquisition step, one or more specified pieces of content that are related to the amendment information acquired in the amendment acquisition step. Effect of the Invention

[0006] In accordance with the present disclosure, electronic content related to changes in law or changes in the interpretation of law can be identified. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Diagram 3] 2 is a block diagram showing a functional configuration of a first user terminal 21. FIG. [Figure 4] 4 is a block diagram showing the functional configuration of a second user terminal 22. FIG. [Diagram 5] 2 is a block diagram showing a functional configuration of a third user terminal 23. FIG. [Figure 6] FIG. 13 is a diagram showing the data structure of a user table 1012. [Figure 7] 13 is a diagram showing the data structure of a group table 1013. FIG. [Figure 8] 13 is a diagram showing the data structure of a rules group table 1014. FIG. [Figure 9] FIG. 13 is a diagram showing the data structure of a rules table 1015. [Figure 10] 13 is a diagram showing the data structure of an approver table 1016. FIG. [Figure 11] FIG. 13 is a diagram showing the data structure of a consent table 1021. [Figure 12]FIG. 13 is a diagram showing the data structure of the revision master 1031. [Figure 13] 13 is a flowchart showing an operation of a rules editing process. [Figure 14] 13 is a flowchart showing the operation of a rules approval process. [Figure 15] 13 is a flowchart showing the operation of a rules agreement process. [Figure 16] 13 is a flowchart showing the operation of a revision specification process. [Figure 17] 13 is a screen example of a selection screen for a rules display rules group in rules editing processing. [Figure 18] 13 is a screen example of a terms of use selection screen in terms of use editing processing. [Figure 19] 13 is a screen example of an editing screen for a rules text in a rules editing process. [Figure 20] 13 is a screen example of a terms of use approval screen in the terms approval process. [Figure 21] 13 is a screen example of a user registration screen in the terms and conditions agreement process. [Figure 22] 13 is a screen example of a user consent screen for terms of use in the terms consent process. [Diagram 23] 13 is a screen example of a list screen of consent information in the agreement consent process. [Figure 24] 13 is a screen example showing the operation of the revision specification process. [Diagram 25] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In all the drawings explaining the embodiment, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiment does not unduly limit the contents of the present disclosure described in the claims. In addition, not all of the components shown in the embodiment are essential components of the present disclosure. In addition, each figure is a schematic diagram and is not necessarily illustrated strictly.

[0009] <System 1 Configuration> System 1 in the present disclosure is an information processing system that creates, stores, and manages terms of use that describe rules such as conditions of use regarding the use of services that operators provide to users when providing web services, application programs, apps, games, etc. (hereinafter referred to as web services, etc.) via the Internet. In this disclosure, the terms of use include a written summary of rules for using a service that a service provider organizes for users when providing the service, such as a web service, an application program, an app, or a game, to users. The terms of use include any rules or policies, such as a privacy policy. In addition, the services that a service provider provides to users are not limited to web services, but also include product sales, electronic commerce (EC), and the like. In this disclosure, as an example, a first user will be described as a creator who creates the terms of use, a second user as an approver who approves the terms of use created by the first user, and a third user as a user who uses a web service for which the terms of use created by the first user are set. The system 1 includes information processing devices, a server 10, a first user terminal 21, a second user terminal 22, and a third user terminal 23, which are connected via a network N. FIG. 1 is a block diagram showing the functional configuration of the system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. As shown in FIG. FIG. 3 is a block diagram showing the functional configuration of the first user terminal 21. As shown in FIG. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 22. As shown in FIG. FIG. 5 is a block diagram showing the functional configuration of the third user terminal 23. As shown in FIG.

[0010] Each information processing device is configured by a computer equipped with a calculation device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 21, the second user terminal 22, and the third user terminal 23, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0011] <Server 10 Configuration> The server 10 is an information processing device that provides a service of creating, storing, and managing terms of use. The server 10 includes a storage unit 101 and a control unit 104 .

[0012] <Configuration of the storage unit 101 of the server 10> The storage unit 101 of the server 10 includes an application program 1011 , a user table 1012 , a group table 1013 , a rules group table 1014 , a rules table 1015 , an approver table 1016 , an agreement table 1021 , and a revision master 1031 .

[0013] The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit.

[0014] User table 1012 is a table that stores and manages information about member users (hereinafter, users) who use the service. When a user registers to use the service, the user's information is stored in a new record in user table 1012. This allows the user to use the service according to the present disclosure. The user table 1012 is a table having the user ID as a primary key and columns of the user ID, user name, and group ID. FIG. 6 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0015] The user ID is an item for storing user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user. The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name. The group ID is an item for storing group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups.

[0016] The group table 1013 is a table for storing and managing information (group information) about groups to which a user belongs. The group can define any group to which a user belongs, such as a corporation, a company, a club, an organization, or a department within a company. The group table 1013 is a table having the group ID as a primary key, and columns of the group ID, group name, and administrator ID. FIG. 7 is a diagram showing the data structure of the group table 1013. As shown in FIG.

[0017] The group ID is an item for storing group identification information for identifying a group. The group identification information is an item for which a unique value is set for each group. The group name is an item for storing the name of a group. Any character string can be set as the group name. The group name can store any group name to which the user belongs, such as a corporate name, a company name, a club name, an organization name, or a department name within a company. The administrator ID is an item for storing user identification information of a user who has administrator authority in a group. A user with administrator authority can arbitrarily define and set a user who has a certain or higher position or authority in a group such as an organization.

[0018] The rules group table 1014 is a table for storing and managing information (rules group information) relating to a rules group consisting of one or more rules. Typically, a rules group consisting of multiple rules such as terms of use and privacy policy is set for each web service. It is common for multiple rules groups to be set for each web service. Note that a rules group may be associated with multiple web services rather than with one web service. The rules group table 1014 is a table having rules group ID as a primary key and columns of rules group ID, rules group name, group ID, service name, and publication date and time. FIG. 8 is a diagram showing the data structure of the rules group table 1014. As shown in FIG.

[0019] The rule group ID is an item for storing rule group identification information for identifying a rule group. The rule group identification information is an item for which a unique value is set for each rule group information. The rule group name is an item that stores the name of the rule group. Any character string can be set as the rule group name. The group ID is an item for storing group identification information to which a set of rules belongs. A user belonging to a group identified by the group identification information can refer to the set of rules associated with the group identification information. Note that a configuration may be adopted in which processing can be performed according to authority information such as editing authority, viewing authority, and deletion authority for each user. Furthermore, authority information such as editing authority, viewing authority, and deletion authority may be set for each rule, not for each set of rules. The service name is an item for storing the name of the web service to which the set of rules applies. Any character string can be set as the service name. Note that, instead of the service name, an application program name, an app name, a game name, or any other character string for identifying a service may be stored. The publication date and time is an item for storing the publication date and time of the rules group identified by the rules group identification information.

[0020] The rules table 1015 is a table for storing and managing information regarding the terms of use (rules information). The rules table 1015 is a table having a rules ID as a primary key and columns of rules ID, rules group ID, rules name, publication date and time, rules text, revision flag, policy data, and memo data. FIG. 9 is a diagram showing the data structure of the rules table 1015. As shown in FIG.

[0021] The "Terms ID" is an item for storing terms identification information for identifying the terms of use. The terms identification information is an item for which a unique value is set for each term information. The rule group ID is an item for storing rule group identification information for identifying a rule group. The "Terms of Use" field is an item for storing the name of the terms of use. Any character string can be set as the terms of use name. Character strings such as "Terms of Use" and "Privacy Policy" are stored as the terms of use name. The publication date and time is an item for storing the publication date and time of the rules information identified by the rules identification information. The terms and conditions text is an item that stores text related to the terms of use. The terms and conditions text may include text data in any format, such as text, rich text, html, markdown, Microsoft Word, PDF (Portable Document Format), XML, etc. Also, instead of the text data, an endpoint such as a URL that identifies the text data, a path, etc. may be stored. The revision flag is an item for storing information indicating whether or not there is an effect based on the revision information. Specifically, it includes the revision ID of the revision information described below, the relevant rule information, etc. The policy data is an item for storing policy information related to countermeasures taken in response to revision information. The policy information will be described in detail in relation to the revision master 1031, which will be described later. The memo data is an item for storing character string information such as memos input by the user for the revision information. Specifically, the user stores a response policy for the revision information by adding a memo.

[0022] The approver table 1016 is a table for storing and managing information (approver information) related to approvers of the rules information. One or more pieces of approver information can be assigned to one piece of rules information. The approver table 1016 is a table having columns for a regulation ID, an approver ID, and approval status. FIG. 10 is a diagram showing the data structure of the approver table 1016. As shown in FIG.

[0023] The rule ID is an item for storing rule identification information for identifying a rule. The approver ID is an item for storing approver identification information for identifying the approver. The approval status is an item for storing whether the rules information specified by the rules identification information has been approved by the user specified by the approver identification information. The approval status stores information indicating that the rules information has been approved by the approver, or information indicating that the rules information has not been approved by the approver.

[0024] The consent table 1021 is a table for storing and managing information (consent information) indicating that a user has consented to the terms of use. The consent table 1021 is a table having columns for user ID, IP address, agreement ID, and consent date and time. FIG. 11 is a diagram showing the data structure of the consent table 1021. As shown in FIG.

[0025] The user ID is an item for storing user identification information for identifying a user. The user identification information is a character string for identifying a user. The IP address is an item that stores the IP address of the user. The rule ID is an item for storing rule identification information for identifying a rule. The agreement date and time is an item for storing the date and time when the user identified by the user ID agreed to the terms and conditions information related to the terms and conditions ID.

[0026] The amendment master 1031 is a table for storing and managing information (amendment information) relating to amendments to laws or changes in the interpretation of laws. The revision master 1031 is a table having the revision ID as a primary key and columns of the revision ID, title, revision content, rule data, and policy data. FIG. 12 is a diagram showing the data structure of the revision master 1031.

[0027] The revision ID is an item for storing revision identification information for identifying revision information. The revision identification information is an item in which a unique value is set for each revision information. The title is an item for storing the title, name, etc. of the revision information. The revision content is an item for storing the content of the revision information. Specifically, in the case of a legal amendment, the amendment includes the legal provisions and clauses before the amendment and the legal provisions and clauses after the amendment. It may also include sentences explaining the interpretations of the legal provisions and clauses before the amendment and the legal provisions and clauses after the amendment. In addition, in the case of a change in the interpretation of the law, it includes sentences explaining the legal interpretation before the change and the legal interpretation after the change. Changes in the interpretation of the law include sentences explaining the legal interpretation before the change and the legal interpretation after the change. Changes in the interpretation of the law include, for example, cases in which the range of interest that was previously interpreted as lawful in the interest regulations of money lending companies is interpreted as illegitimate due to a judicial decision, etc. The rule data is an item for storing rule information related to conditions. The revision information may include multiple pieces of rule information. The rule information includes information regarding conditions that specify content information including the regulation information that is affected based on the revision information. The content information includes information for identifying the type of content, such as: Terms of Use (Terms of Use information is stored and managed by the terms of use table 1015, etc.) - White papers, etc., which are annual reports issued by governments, public institutions, companies, etc. IR (Investor Relations) materials used by companies to publicize their business status, financial status, performance results, future outlook, etc. to shareholders and investors Web manuals for web services, video manuals, etc. When the type of content is a term of use, the rule information includes information on conditions that specify a product or service to which the term of use applies. For example, the rule information may include information on conditions that specify a type of product or service, such as a "contract review service." The rule information may include conditions that specify the clauses or provisions that are affected based on the revision information. For example, the rule information may include information regarding conditions that specify the terms of use that include specific clauses or provisions such as "damage compensation clauses," "late interest," and "exemptions from liability." The rule information may include information on conditions related to the contents of clauses and provisions of the terms and conditions information that are affected based on the revision information. For example, the rule information may include information on conditions that specify the terms and conditions including a clause or provision such as "no compensation will be provided to consumers." The rule information may include information on the condition that the content information includes a specific keyword such as "Consumer Contract Law." In addition, the rule information may include information on the condition that specifies property information and meta information (including information written in any markup language such as JSON) that are stored in association with any content information. The policy data is an item for storing policy information related to measures taken in response to the revision information and rule information. Specifically, the policy information includes information related to the content information to be revised in accordance with the revision details. For example, the policy information includes information such as "When a service specifies a waiver of compensation for customers, it is necessary to add a special note that the waiver does not apply to consumers as defined by the Consumer Contract Act." The policy information may store information on a countermeasure for each revision information, or may store information on a countermeasure for each of a plurality of rule information included in the revision information. For example, a countermeasure corresponding to information that specifies the type of content included in the rule information may be stored. The policy data may include information regarding a deadline according to the revision information, such as "urgent action is required," "revision is required before the implementation date," or "revision is required by a certain date."

[0028] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a rules editing unit 1042, a rules approval unit 1043, a rules agreement unit 1044, and a revision unit 1051. The control unit 104 executes an application program 1011 stored in the storage unit 101 to realize each functional unit.

[0029] The user registration control unit 1041 performs processing to store, in the user table 1012, information on users who wish to use the service according to the present disclosure. The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, enters information into a specific input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service. Before the user registration control unit 1041 registers user information in the user table 1012, the service provider may carry out a predetermined examination to restrict whether or not the user is permitted to use the service. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or an arbitrary character string or number may be automatically set by the user registration control unit 1041.

[0030] The rules editing unit 1042 executes rules editing processing, the details of which will be described later.

[0031] The rules approval unit 1043 executes rules approval processing, the details of which will be described later.

[0032] The rules agreement unit 1044 executes rules agreement processing, the details of which will be described later.

[0033] The revision unit 1051 executes revision specific processing, the details of which will be described later.

[0034] <Configuration of First User Terminal 21> The first user terminal 21 is an information processing device operated by a first user who uses a service. The first user terminal 21 may be, for example, a mobile terminal such as a smartphone or a tablet, a stationary PC (Personal Computer), or a laptop PC. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal. The first user terminal 21 includes a storage unit 211 , a control unit 214 , an input device 216 , and an output device 218 .

[0035] <Configuration of the storage unit 211 of the first user terminal 21> The storage unit 211 of the first user terminal 21 includes a first user ID 2111 and an application program 2112 .

[0036] The first user ID 2111 is an account ID of the first user. The user transmits the first user ID 2111 from the first user terminal 21 to the server 10. The server 10 identifies the first user based on the first user ID 2111 and provides the first user with the service according to the present disclosure. The first user ID 2111 includes information such as a session ID temporarily assigned by the server 10 when identifying the first user who is using the first user terminal 21.

[0037] The application program 2112 may be stored in advance in the storage unit 211, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. The application programs 2112 include applications such as a web browser application. The application program 2112 includes an interpretive programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the first user terminal 21.

[0038] <Configuration of the control unit 214 of the first user terminal 21> The control unit 214 of the first user terminal 21 includes an input control unit 2141 and an output control unit 2142. The control unit 214 executes an application program 2112 stored in the storage unit 211, thereby realizing each functional unit.

[0039] <Configuration of the input device 216 of the first user terminal 21> The input device 216 of the first user terminal 21 includes a camera 2161 , a microphone 2162 , a position information sensor 2163 , a motion sensor 2164 , and a touch device 2165 .

[0040] <Configuration of the output device 218 of the first user terminal 21> The output device 218 of the first user terminal 21 includes a display 2181 and a speaker 2182 .

[0041] <Configuration of second user terminal 22> The second user terminal 22 is an information processing device operated by a second user who uses the service. The second user terminal 22 may be, for example, a mobile terminal such as a smartphone or a tablet, a stationary PC (Personal Computer), or a laptop PC. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type terminal. The second user terminal 22 includes a storage unit 221 , a control unit 224 , an input device 226 , and an output device 228 .

[0042] <Configuration of the storage unit 221 of the second user terminal 22> The storage unit 221 of the second user terminal 22 includes a second user ID 2211 and an application program 2212 .

[0043] The second user ID 2211 is a user's account ID. The second user transmits the second user ID 2211 from the second user terminal 22 to the server 10. The server 10 identifies the second user based on the second user ID 2211 and provides the second user with the service according to the present disclosure. The second user ID 2211 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the second user terminal 22.

[0044] The application program 2212 may be stored in advance in the storage unit 221, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. The application programs 2212 include applications such as a web browser application. The application program 2212 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the second user terminal 22.

[0045] <Configuration of the control unit 224 of the second user terminal 22> The control unit 224 of the second user terminal 22 includes an input control unit 2241 and an output control unit 2242. The control unit 224 executes an application program 2212 stored in the storage unit 221, thereby realizing each functional unit.

[0046] <Configuration of the input device 226 of the second user terminal 22> The input device 226 of the second user terminal 22 includes a camera 2261 , a microphone 2262 , a position information sensor 2263 , a motion sensor 2264 , and a touch device 2265 .

[0047] <Configuration of the output device 228 of the second user terminal 22> The output device 228 of the second user terminal 22 includes a display 2281 and a speaker 2282 .

[0048] <Configuration of third user terminal 23> The third user terminal 23 is an information processing device operated by a third user who uses the service. The third user terminal 23 may be, for example, a mobile terminal such as a smartphone or a tablet, a stationary PC (Personal Computer), or a laptop PC. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal. The third user terminal 23 includes a storage unit 231 , a control unit 234 , an input device 236 , and an output device 238 .

[0049] <Configuration of the storage unit 231 of the third user terminal 23> The storage unit 231 of the third user terminal 23 includes a third user ID 2311 and an application program 2312 .

[0050] The third user ID 2311 is an account ID of the third user. The third user transmits the third user ID 2311 from the third user terminal 23 to the server 10. The server 10 identifies the third user based on the third user ID 2311 and provides the third user with the service according to the present disclosure. The third user ID 2311 includes information such as a session ID temporarily assigned by the server 10 when identifying the user using the third user terminal 23.

[0051] The application program 2312 may be stored in advance in the storage unit 231, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. The application programs 2312 include applications such as a web browser application. The application program 2312 includes an interpretive programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the third user terminal 23.

[0052] <Configuration of the control unit 234 of the third user terminal 23> The control unit 234 of the third user terminal 23 includes an input control unit 2341 and an output control unit 2342. The control unit 234 executes an application program 2312 stored in the storage unit 231, thereby realizing each functional unit.

[0053] <Configuration of the input device 236 of the third user terminal 23> The input device 236 of the third user terminal 23 includes a camera 2361 , a microphone 2362 , a position information sensor 2363 , a motion sensor 2364 , and a touch device 2365 .

[0054] <Configuration of the output device 238 of the third user terminal 23> The output device 238 of the third user terminal 23 includes a display 2381 and a speaker 2382 .

[0055] <System 1 Operation> Each process of the system 1 will be described below. FIG. 13 is a flowchart showing the operation of the rules editing process. FIG. 14 is a flowchart showing the operation of the rules approval process. FIG. 15 is a flowchart showing the operation of the agreement consent process. FIG. 16 is a flowchart showing the operation of the revision specification process. FIG. 17 shows an example of a screen for selecting a rules display rules group in the rules editing process. FIG. 18 shows an example of a screen for selecting terms of use in the terms editing process. FIG. 19 shows an example of a screen for editing the terms of use text in the terms of use editing process. FIG. 20 shows an example of a terms of use approval screen in the terms approval process. FIG. 21 shows an example of a user registration screen for the user in the agreement consent process. FIG. 22 shows an example of a screen on which the user agrees to the terms of use in the terms agreement process. FIG. 23 is an example of a screen showing a list of consent information in the agreement consent process. FIG. 24 is a screen example showing the operation of the revision specification process.

[0056] In the present disclosure, the terms editing process, the terms approval process, and the terms agreement process in the server 10 will be described below. In the present disclosure, the first user related to the creator performs the terms editing process via the first user terminal 21, the second user related to the approver performs the terms approval process via the second user terminal 22, and the third user related to the user performs the terms agreement process via the third user terminal 23, but this is not limited to the above. The terms editing process, the terms approval process, and the terms agreement process may each be performed by any user.

[0057] The first user and the second user are described as employees of a company (business operator) that operates a web service, etc. In this disclosure, the first user is an employee who is engaged in editing the terms of use, etc., and the second user is described as a manager such as a manager who has a certain approval authority within the company. The third user is a user who uses the web service operated by the business operator.

[0058] <Regulations editing process> The rules editing process is a process for a first user, who is a creator, to create new rules information related to the terms of use etc., or to edit already created rules information.

[0059] <Overview of the terms editing process> The terms and conditions editing process is a series of processes in which a first user related to the creator selects or creates a set of terms and conditions, selects or creates terms of use to be included in the set of terms and conditions, edits the text of the selected or created terms of use, sets a publication date for the terms and conditions, and sets an approver. Note that the approver setting may be omitted. If the approver setting is omitted, the edited terms of use will be made available to users without executing the terms approval process.

[0060] <Details of the terms editing process> The details of the rules editing process will be explained below.

[0061] In step S101, the rules editing unit 1042 of the server 10 receives information (rules group information) on a rules group consisting of one or more rules from a first user.

[0062] Specifically, the first user operates the input device 216 of the first user terminal 21 to execute a browser application or the like, and opens the terms of use editing page D1 by inputting the URL of a web page (terms of use editing page) for executing the terms of use editing process. The control unit 214 of the first user terminal 21 transmits a request including the first user ID 2111 for opening the terms of use editing page to the server 10.

[0063] When the rules editing unit 1042 of the server 10 receives a request from the first user terminal 21, it searches the user ID item of the user table 1012 based on the first user ID 2111 and acquires the group ID (first group ID). The rules editing unit 1042 of the server 10 searches the group ID item of the rules group table 1014 based on the first group ID and acquires one or more rules group IDs (first rules group IDs), rules group names (first rules group names), and service names (first service names). In this way, it identifies and accepts information (rules group information) related to a rules group consisting of one or more rules that the first user can refer to.

[0064] The rules editing unit 1042 of the server 10 transmits the first rules group ID, the first rules group name, and the first service name to the first user terminal 21. The control unit 214 of the first user terminal 21 displays the first rules group name and the first service name on the display 2181 of the first user terminal 21. The information that the rules editing unit 1042 of the server 10 transmits to the first user terminal 21 includes at least the first rules group ID. The information displayed on the display 2181 of the first user terminal 21 may include any one of the information included in the rules information, such as the rules ID, rules name, publication date and time, rules text, etc., of the terms of use included in the rules group, in addition to the rules group name and service name. For example, the rules editing unit 1042 of the server 10 can obtain the rules information by searching the items of the rules group ID in the rules table 1015 based on the first rules group ID, and include the obtained rules information in the information to be transmitted to the first user terminal 21.

[0065] 17 is an example of a screen for selecting a rule display rule group in the rule editing process. A rule editing page D1 is displayed on the display 2181 of the first user terminal 21. The rule editing page D1 includes a rule group list display screen D11 that displays a list of rule groups that the first user can refer to. The rule group list display screen D11 includes a new rule group creation button D111 for creating a new rule group, and one or more rule groups D112, D113,... that the first user can refer to. The rule groups D112, D113,... each include a rule group name that is the name of the rule group, and the rule names of one or more terms of use included in the rule group.

[0066] The first user operates the input device 216 of the first user terminal 21 to select the group of rules D112, D113,..., to be edited. The control unit 214 of the first user terminal 21 identifies the group of rules ID corresponding to the selected group of rules D112, D113,.... The control unit 214 of the first user terminal 21 transmits the identified group of rules ID to the server 10. The rules editing unit 1042 of the server 10 receives and identifies the group of rules ID from the first user terminal 21.

[0067] The first user can also create a new set of rules by operating the input device 216 of the first user terminal 21 and pressing the new rules group creation button D111. In this case, the rules editing unit 1042 of the server 10 creates and stores a record related to the new rules group information in the rules group table 1014. The rules editing unit 1042 of the server 10 identifies and stores the rules group ID of the new record.

[0068] In step S102, the rules editing unit 1042 of the server 10 accepts information (rules information) relating to a predetermined set of terms of use. Specifically, the rules editing unit 1042 of the server 10 searches the rules group ID item in the rules table 1015 based on the rules group ID identified in step S101, obtains the rules IDs and rules names of one or more terms of use associated with the rules group ID, and transmits them to the first user terminal 21. The control unit 214 of the first user terminal 21 displays the received one or more rules IDs and rules names on the display 2181 of the first user terminal 21. It should be noted that when a new set of rules is created, if there is no rules information associated with the rules group ID, the rules information is not transmitted to the first user terminal 21.

[0069] 18 is a screen example of a selection screen of terms of use in the terms of use editing process. A terms of use editing page D1 is displayed on the display 2181 of the first user terminal 21. The terms of use editing page D1 includes a terms of use editing screen D13. The terms of use editing screen D13 includes a terms of use group name input field D131 for editing the terms of use group name of the terms of use group identified in step S101, a publication date and time input field D132 for setting the publication date and time of the terms of use group identified in step S101, terms of use D133, D134, and D135 included in the terms of use group identified in step S101, a terms of use creation button D136 for creating new terms of use, an approver input field D161 for inputting an approver, an approval request button D162 for sending an approval request to the approver, and a button D163 for saving the terms of use information being edited. The terms of use D133 include a terms name D1331, buttons D1332 and D1333 for changing the display order of a plurality of terms, and a button D1334 for deleting the terms of use. The first user can change the order of the terms of use D133 and the terms of use D134 by operating the input device 216 of the first user terminal 21 and pressing the button D1333. The first user can edit the rule group name of the identified rule group by operating the input device 216 of the first user terminal 21 and editing the rule group name input field D131. The first user can edit the publication date and time of the specified set of rules by operating the input device 216 of the first user terminal 21 and editing the publication date and time input field D132. The publication date and time can be selected from either "As soon as approved," which makes the rules public immediately after approval by the approver, or "Public at a specified date and time," which makes the rules public by specifying a specific publication date and time. When "Publish at a specified date and time" is selected, a dialog for inputting a date and time is presented to the first user, and the first user can input and specify the publication date and time of the group of rules.

[0070] The first user operates the input device 216 of the first user terminal 21 to input and edit the contents of the rules group name input field D131 and the publication date and time input field D132. The control unit 214 of the first user terminal 21 transmits the contents of the rules group name input field D131 and the publication date and time input field D132 to the server 10. The rules editing unit 1042 of the server 10 stores the contents of the rules group name input field D131 and the publication date and time input field D132 in the rules group name and publication date and time items of the rules group information record of the rules group table 1014 identified in step S101, respectively, and updates the information.

[0071] The first user operates the input device 216 of the first user terminal 21 to select the terms of use D133, D134, D135 to be edited. The control unit 214 of the first user terminal 21 identifies a terms of use ID corresponding to the selected terms of use D133, D134, D135. The control unit 214 of the first user terminal 21 transmits the identified terms of use ID to the server 10. The terms of use editing unit 1042 of the server 10 receives and identifies the terms of use ID from the first user terminal 21.

[0072] The first user can also create new terms of use by operating the input device 216 of the first user terminal 21 and pressing the terms of use creation button D136. In this case, the terms of use editing unit 1042 of the server 10 creates and stores a record related to the new terms of use information in the terms of use table 1015. The terms of use editing unit 1042 of the server 10 identifies and stores the terms of use ID of the new record.

[0073] In step S103, the rules editing unit 1042 of the server 10 executes a rules receiving step of receiving rules information related to the terms of use from the user. The rules editing unit 1042 of the server 10 presents a screen for editing the rules information to the first user. The rules editing unit 1042 of the server 10 receives the edit of the rules information from the first user. Specifically, the rules editing unit 1042 of the server 10 searches the item of the rules ID in the rules table 1015 based on the rules ID identified in step S102, obtains the rules name, publication date and time, and rules text, and transmits them to the first user terminal 21. The control unit 214 of the first user terminal 21 displays the received rules ID, rules name, publication date and time, and rules text on the display 2181 of the first user terminal 21.

[0074] 19 is a screen example of an editing screen for the terms text in the terms editing process. A terms editing page D1 is displayed on the display 2181 of the first user terminal 21. The terms editing page D1 includes a terms editing screen D15. The terms editing screen D15 includes a terms name input field D151 for editing the terms name of the terms of use specified in step S102, a publication date and time input field D152 for setting the publication date and time of the terms of use specified in step S102, a terms text input field D153 for inputting and editing the terms text of the terms of use specified in step S102, an approver input field D161 for inputting the approver of the terms of use specified in step S102, and an approval request button D162 for sending an approval request to the approver.

[0075] In step S103, the rules editing unit 1042 of the server 10 executes a rules storage step of storing the rules information accepted in the rules acceptance step. The first user operates the input device 216 of the first user terminal 21 to input and edit the contents of the rule name input field D151 and the rule text input field D153. The control unit 214 of the first user terminal 21 transmits the contents of the rule name input field D151 and the rule text input field D153 to the server 10. The rule editing unit 1042 of the server 10 stores the contents of the rule name input field D151 and the rule text input field D153 in the rule name and rule text items of the rule information record of the rule table 1015 identified in step S102, respectively, and updates the information.

[0076] In step S104, the rules editing unit 1042 of the server 10 presents a screen for editing the publication date and time of the rules information. The rules editing unit 1042 of the server 10 accepts the publication date and time of the rules information. Specifically, the first user can edit the publication date and time of the terms of use specified in step S102 by operating the input device 216 of the first user terminal 21 and editing the publication date and time input field D152. The publication date and time can be selected from either "as soon as approved," which makes the content public immediately after approval by the approver, or "published at a specified date and time," which allows the content to be published by specifying a specific publication date and time. When "Publish at a specified date and time" is selected, a dialog for inputting a date and time is presented to the first user, and the first user can input and specify the publication date and time of the terms of use.

[0077] The first user operates the input device 216 of the first user terminal 21 to transmit the selection of the publication date and time input field D152 to the server 10. The rules editing unit 1042 of the server 10 stores the selection of the publication date and time input field D152 in the publication date and time item of the rules information record of the rules table 1015 identified in step S102, and updates the information.

[0078] In step S105, the rules editing unit 1042 of the server 10 accepts approver information related to the approver of the rules information. Specifically, the first user operates the input device 216 of the first user terminal 21, and inputs at least one of the user's name, user name, user identification information, email address, etc., for identifying the user related to the approver, into the approver input field D161. In the present disclosure, a configuration in which the second user ID of the second user is input into the approver input field D161 will be described as an example. The first user operates the input device 216 of the first user terminal 21, and selects the approval request button D162. The control unit 214 of the first user terminal 21 transmits the second user ID input into the approver input field D161 to the server 10.

[0079] The rules editing unit 1042 of the server 10 searches the user ID item of the user table 1012 based on the second user ID, and acquires contact information such as a second email address of the second user. The server 10's rules editing unit 1042 sends a message to the second user's email address, notifying the second user that a request to confirm the rules information has been sent from the first user, by a communication means such as email. Note that the contact is not limited to an email address, and may be any communication means such as a telephone number, an ID for a chat service, etc. The message to be notified to the second user includes information on a uniform resource locator (URL) including a rules ID for identifying the contract information. The URL may directly include the rules ID, or may include information such as a character string that is an arbitrary encryption of the rules ID, or a character string that can identify the rules ID by referring to a table (not shown). The URL may also include information for identifying the second user.

[0080] Note that input of approver information may be omitted. In that case, the terms of use are made public to users with the terms of use text and publication date and time input or set in steps S103 and S104. In that case, the terms of use approval process described later can be omitted. In addition, when approver information is input, the terms of use edited by the terms editing process will not be made public even if the publication date and time has passed unless the approver approves the terms of use by the terms approval process described below. In other words, the results of editing the terms of use by the first user in the terms editing process will not be reflected in the terms of use consent screen in the terms consent process described below, which can be referenced by users, etc.

[0081] <Terms approval process> The terms of use approval process is a process in which the second user, who is the approver, approves the terms of use created or edited by the creator. The terms of use created or edited by the creator are made public to users by being approved by the approver.

[0082] <Overview of terms approval process> The terms and conditions approval process is a series of processes in which a second user who is an approver selects the terms and conditions created or edited by the creator, checks the terms and conditions text of the selected terms and conditions, approves the terms and conditions, and makes the terms and conditions public to users.

[0083] <Details of the terms and conditions approval process> The details of the agreement approval process are explained below.

[0084] In step S201, the agreement approval unit 1043 of the server 10 accepts information (agreement information) relating to a predetermined agreement to be approved from the second user. Specifically, the second user, who is the approver, operates the input device 226 of the second user terminal 22 or the like to select a URL included in the received message, thereby opening a web page (terms of use approval page) in the browser application of the second user terminal 22 for approving the terms of use edited by the creator identified by the URL through a terms of use editing process.

[0085] 20 is an example of a screen of the approval screen of the terms of use in the terms of use approval process. The display 2281 of the second user terminal 22 displays the terms of use approval page D2. The terms of use approval page D2 includes a terms of use approval screen D21, which includes a terms of use name D211, a publication date and time D212, terms of use text D213, a comment input field D214, an approval button D215, a return button D216, a related party D217, and related terms of use D218 that displays other terms of use that are related to the terms of use displayed on the terms of use approval screen D21 and that will be affected by changes, etc.

[0086] In step S202, the second user checks the contents of the agreement information displayed on the display 2281 of the second user terminal 22. Note that the second user may be configured to be able to edit the agreement name D211, the publication date and time D212, the agreement text D213, and the like by operating the input device 226 of the second user terminal 22. Specifically, the second user can edit the name of the terms of use by operating the input device 226 of the second user terminal 22 and inputting and editing the content of the input field for the term name D211. Specifically, the second user can edit the publication date and time of the terms of use by operating the input device 226 of the second user terminal 22 and inputting and editing the content of the input field for publication date and time D212. Specifically, the second user can edit the content of the agreement text of the terms of use by operating the input device 226 of the second user terminal 22 and inputting and editing the content of the input field of the agreement text D213. The control unit 224 of the second user terminal 22 transmits the edited terms and conditions information to the server 10. The terms and conditions approval unit 1043 of the server 10 stores the contents of the input field for terms and conditions name D211, the contents of the input field for publication date and time D212, and the contents of the input field for terms and conditions text D213 in the items for terms and conditions name, publication date and time, and terms and conditions text of the terms and conditions information record of the terms and conditions table 1015 identified in step S301, respectively, and updates the information. This allows the second user to make edits such as corrections to the terms of use edited by the first user without returning it to the first user.

[0087] In step S203, if the second user has no problem with the content of the confirmed agreement information, the second user operates the input device 226 of the second user terminal 22 to press the approval button D215. The control unit 224 of the second user terminal 22 transmits a request to approve the terms of use to the server 10.

[0088] In step S204, the rules approval unit 1043 of the server 10 stores the rules information to be approved and information indicating that the rules information has been approved by the approver in association with each other. Specifically, the rules approval unit 1043 of the server 10 stores in the approver table 1016 the rules ID of the rules information to be approved, which are included in the request received from the second user terminal 22, the second user ID 2211, and information indicating that the rules information has been approved by the approver. This stores the fact that the terms of use specified by the terms ID have been approved by the user associated with the approver ID. The terms of use information approved in step S204 is made public to the user with the terms of use text and publication date and time input or set in steps S103 and S104 of the terms of use editing process. In other words, the results of editing the terms of use by the first user in the terms of use editing process are reflected in a terms of use consent screen in the terms of use consent process described later, which can be referenced by users, etc.

[0089] <Embedding rules into the user registration screen> When the terms of use are approved, the business providing the web service embeds a predetermined HTML (HyperText Markup Language) tag including the rules group ID in the HTML (HyperText Markup Language) text of the user registration screen D31 of the web service provided by the business. As a result, when the user opens the user registration screen D31 of the web service on his / her information processing terminal, the names of the rules of the terms of use included in the rules group specified by the rules group ID and the links D313, D314, D315 for opening the respective rules texts are displayed in an embedded form in the user registration screen D31. Also, the user registration screen D31 may be generated by dynamically embedding links D313, D314, and D315 using JavaScript (registered trademark) instead of HTML. This allows the terms of use created and edited by the terms of use editing process according to the present disclosure to be embedded in the user registration screen D31 of the web service provided by the business operator. When a term of use associated with a set of terms is added, deleted, or the term name is changed in the terms editing process, the links D313, D314, and D315 embedded in the user registration screen D31 are automatically added, deleted, or the term name is automatically changed in response to the change. This allows the user to edit the terms of use without having to individually edit the HTML text, etc., of the user registration screen, and thus omits the troublesome task of editing HTML text, etc. Using the service disclosed herein, users can efficiently and centrally manage terms and conditions information related to the terms of use that are distributed across one or more web services.

[0090] If the second user has a problem with the content of the confirmed terms and conditions information, the second user operates the input device 226 of the second user terminal 22 to press the reject button D216. The control unit 224 of the second user terminal 22 transmits a request to reject the terms and conditions to the server 10. The rules approval unit 1043 of the server 10 stores in the approver table 1016 the rules ID of the rules information to be approved, which is included in the request received from the second user terminal 22, the second user ID 2211, and information indicating that the rules information has been returned by the approver. The terms approval unit 1043 of the server 10 transmits a message to the first user via e-mail, chat service, or the like, indicating that the approval of the terms of use edited by the terms editing process has been returned. The second user may input a comment on the reason for the return in the comment input field D214, and include the input comment in the message to be transmitted to the first user. Thereafter, the first user resolves the reason for the return and executes the terms editing process again.

[0091] <Terms and conditions agreement process> The terms and conditions consent process is a process in which a user browses predetermined terms and conditions, confirms the contents of the terms and conditions, and consents (agrees) to the predetermined terms and conditions.

[0092] <Overview of Terms and Conditions Agreement Processing> The terms and conditions consent process is a series of processes in which a third-party user related to a user opens a specified web service, application program, app, game, etc., selects the terms and conditions from the user registration or login screen, checks the contents of the terms and conditions of the selected terms and conditions, and consents to the terms and conditions.

[0093] <Details of the terms and conditions agreement process> The details of the agreement process are explained below.

[0094] In step S301, a third user opens a website operated by an operator different from the service provider according to the present disclosure. Specifically, the third user operates the input device 236 of the third user terminal 23, executes a browser application or the like, and opens a user registration page by inputting the URL or the like of a web page (user registration screen) for performing user registration or the like in a web service operated by the business operator. The control unit 234 of the third user terminal 23 transmits a request to open the user registration page to the business operator server 40 operated by the business operator. Upon receiving the request, the business server 40 generates a user registration page and transmits it to the third user terminal 23. It is assumed that the business operator has written in advance on the user registration page a predetermined HTML tag capable of identifying a predetermined rule group ID according to the present disclosure, a markup language such as JavaScript (registered trademark), and a programming language in advance. The business server 40 transmits a request requesting rule information to the server 10 based on the predetermined HTML tag capable of identifying a predetermined rule group ID, a markup language such as JavaScript (registered trademark), and a programming language written on the received user registration page. The rule agreement unit 1044 of the server 10 searches for the rule group ID item in the rule table 1015 based on the received rule group ID, acquires the rule ID and the rule name, and transmits them to the business server 40. The business server 40 embeds a link including the acquired rule name and rule ID in the user registration page, generates a user registration screen D31, and displays it on the display 2381 of the third user terminal 23. The inquiry of the rules group based on the predetermined rules group ID may be made by the third user terminal 23, not the business entity server 40, in such a configuration that the third user terminal 23 transmits a request for rules information to the server 10 based on a predetermined HTML tag, a markup language such as JavaScript (registered trademark), or a programming language capable of identifying the predetermined rules group ID. In this case, the third user terminal 23 obtains the rules information directly from the server 10 without going through the business entity server 40, and displays it on the display 2381 of the third user terminal 23.

[0095] 21 is an example of a user registration screen displayed by a user in the agreement consent process. A user registration screen D31 is displayed on the display 2381 of the third user terminal 23. The user registration screen D31 includes an email address input field D311, a password input field D312, and a user registration button D316. The user registration screen D31 includes the names of the terms of use included in the rules group identified by the rules group ID, and links D313, D314, and D315 for opening the respective rules texts. The third user can operate the input device 236 of the third user terminal 23 to select one of the links D313, D314, and D315 displayed on the display 2381 of the third user terminal 23, thereby displaying the selected terms of use. The user registration button D316 is not in a state where it can be pressed unless the third user agrees to all the terms of use corresponding to the links D313, D314, and D315 displayed on the user registration screen D31, and the third user cannot proceed to user registration. Note that the user registration button D316 may be in a state where it can be pressed even if the third user does not agree to all the terms of use corresponding to the links D313, D314, and D315 displayed on the user registration screen D31, and the third user may proceed to user registration.

[0096] <Terms presentation process> In step S302, the rules consent unit 1044 of the server 10 executes a rules presentation step of presenting the rules information stored in the rules storage step to the user. Specifically, the third user operates the input device 236 of the third user terminal 23 to select one of the links D313, D314, and D315 displayed on the display 2381 of the third user terminal 23. Each of the links D313, D314, and D315 includes terms of use identification information (terms of use ID) for identifying the corresponding terms of use. The control unit 234 of the third user terminal 23 executes a process of opening the selected link in a browser application or the like. In the present disclosure, the control unit 234 of the third user terminal 23 transmits the rules IDs corresponding to the selected links D313, D314, and D315 to the server 10. The rules agreement unit 1044 of the server 10 searches the item of the rules ID in the rules table 1015 based on the rules ID, and acquires the rules name and the rules text. The terms and conditions agreement unit 1044 of the server 10 generates a terms and conditions agreement page based on the acquired terms and conditions name and terms and conditions text, and transmits it to the third user terminal 23. The control unit 234 of the third user terminal 23 displays a terms and conditions agreement screen D32 on the display 2381 of the third user terminal 23 based on the received terms and conditions agreement page. In the present disclosure, the server 10 is configured to generate the terms of use consent page, but the business server 40 may inquire about the terms of use information of the server 10 and generate the terms of use consent page.

[0097] 22 is an example of a terms of use consent screen displayed by a user in terms consent processing. A terms of use consent screen D32 is displayed on the display 2381 of the third user terminal 23. The terms of use consent screen D32 includes a terms text D321, an agree button D322, and an agree radio button D323.

[0098] In step S303, the terms and conditions consent unit 1044 of the server 10 executes a consent storage step of storing the user in association with information indicating that the user has consented to the terms of use in response to the user's consent operation on the consent screen presented to the user in the terms and conditions presentation step. Specifically, the third user operates the input device 236 of the third user terminal 23 to agree to the terms of use displayed on the display 2381 of the third user terminal 23 . The third user operates the input device 236 of the third user terminal 23 to press the Agree button 322 displayed on the display 2381 of the third user terminal 23. This causes the control unit 234 of the third user terminal 23 to transmit to the server 10 a request including the terms of use ID of the terms of use selected by the user in step S301 and information indicating that the user agrees to the terms of use selected by the user. When the server 10's agreement agreement unit 1044 receives a request, it stores the IP address of the third user terminal 23 based on the request, the agreement ID contained in the request, and the date and time the request was received in the IP address, agreement ID, and agreement date and time items in the agreement table 1021, respectively.

[0099] The third user operates the input device 236 of the third user terminal 23 to select all the links D313, D314, and D315 displayed on the user registration screen D31, and agrees to the terms of use. The business server 40 transmits a request including the IP address and the policy group ID of the third user to the server 10. The agreement agreement unit 1044 of the server 10 searches the agreement table 1021 based on the IP address included in the request, and acquires the agreement ID (agreed agreement ID). The terms and conditions agreement unit 1044 of the server 10 acquires one or more terms and conditions IDs from the terms and conditions table 1015 based on the acquired terms and conditions group ID. As a result, the terms and conditions agreement unit 1044 of the server 10 acquires and identifies the terms and conditions IDs of all the terms and conditions included in the terms and conditions group of the web service identified by the terms and conditions group ID acquired from the business server 40. The agreement agreement unit 1044 of the server 10 judges whether the third user has agreed to all the terms of use displayed on the user registration screen D31 by comparing the agreed terms ID with the terms IDs of all the terms of use included in the set of terms of the web service. Specifically, if the agreed terms ID includes all the terms IDs of all the terms of use included in the set of terms of the web service, it is judged that the third user has agreed to all the terms of use displayed on the user registration screen D31. If the server 10's agreement section 1044 determines that the third user has agreed to all of the terms of use displayed on the user registration screen D31, it sends a request to the business server 40 indicating that the third user has agreed to all of the terms of use displayed on the user registration screen D31. When the business server 40 receives the request, it changes the state of the user registration button D316 on the user registration screen D31 to one that can be pressed. In addition, if the condition "agreement is not mandatory" is selected in the terms presentation process, the user registration button D316 on the user registration screen D31 is changed to a state where it can be pressed without consenting to the terms of use.

[0100] In step S304, the third user operates the input device 236 of the third user terminal 23 to input his / her own email address and desired password in the email address input field D311 and password input field D312 of the user registration screen D31, respectively. The third user operates the input device 236 of the third user terminal 23 to press the user registration button D316. The control unit 234 of the third user terminal 23 transmits the input email address and password to the business server 40. The business server 40 performs user registration in a web service operated by the business based on the received email address and password.

[0101] The business server 40 transmits the IP address and email address of the third user to the server 10. The terms and conditions agreement unit 1044 of the server 10 searches the IP address field of the agreement table 1021 based on the received IP address, and stores the received email address in the user ID field of the identified record. As a result, the email address for identifying the user, the terms and conditions ID, and the date and time of agreement to the terms and conditions identified by the terms and conditions ID are stored in association with each other. As a result, the fact that the third user has agreed to the terms and conditions is stored in the agreement table 1021. In this disclosure, the email address of the third user is stored as the user ID, but any character string such as a user name or name (user identification information) in a web service operated by the business operator, or any other character string for identifying the third user may be stored. This allows the business operator to manage the consent status of each user to the terms of use without sending personal information such as the user's email address to the terms of use management service disclosed herein.

[0102] In addition, in the present disclosure, when the third user presses the consent button D322, the consent information is stored in the consent table 1021. However, when the third user presses the user registration button D316, it is assumed that the third user has agreed to each of the terms of use included in the group of rules associated with the web service, and the business server 40 transmits the third user's email address entered in the email address input field D311, and the rules ID corresponding to the links D313, D314, and D315 to the server 10. The rules consent unit 1044 of the server 10 may store the received email address and rules ID of the third user in the user ID and rules ID items of the consent table 1021, respectively. In this case, the storage of the IP address may be omitted. This makes it possible to omit the collection and storage of unnecessary information such as the third user's IP address.

[0103] <List display process for consent information> 23 is an example of a screen of a list of consent information in the agreement consent process. An employee of a business operating a web service such as a first user or a second user operates an input device of his / her user terminal, executes a browser application, and opens the list display page D4 by inputting the URL of a web page (list display page) for executing the list display process of consent information. The list display page D4 displays, in association with each other, user identification information D421 of a user who has agreed to the terms of use, a rules group name D422 of a rules group to which the terms of use agreed by the user belongs, and a date and time D423 when the user agreed to the terms of use.

[0104] In the present disclosure, the display of a list screen of consent information by a first user will be described as an example. Note that, in addition to the second user, an employee of a business operator that operates a web service may also be configured to be able to display a similar list screen of consent information. The control unit 214 of the first user terminal 21 transmits to the server 10 a request including the first user ID 2111 for opening the list display page. When the rules agreement unit 1044 of the server 10 receives a request from the first user terminal 21, it searches the user ID item of the user table 1012 based on the first user ID 2111 and acquires a group ID (first group ID). The rules agreement unit 1044 of the server 10 searches the group ID item of the rules group table 1014 based on the first group ID and acquires one or more rules group IDs (first rules group IDs), rules group names (first rules group names), and service names (first service names). The rules consent unit 1044 of the server 10 searches the rules table 1015 for a rules group ID based on the acquired first rules group ID, acquires a rules ID, and stores the rules ID included in the first rules group ID in association with the first rules group ID. The agreement unit 1044 of the server 10 searches the agreement table 1021 for the agreement ID based on the acquired agreement ID, and acquires the user ID and the agreement date and time. The terms and conditions consent unit 1044 of the server 10 identifies the set of terms and conditions for which all terms and conditions have been agreed to for each user ID, and transmits the user ID, the name of the set of terms and conditions for which all terms and conditions have been agreed to, and the date and time of agreement to the first user terminal 21. Note that the date and time of agreement may be the date and time of agreement for the most recent set of terms and conditions among multiple terms and conditions included in the set of terms and conditions. This is because the date and time of agreement for all terms and conditions can be regarded as the date and time of agreement for the set of terms and conditions. The control unit 214 of the first user terminal 21 displays the consent information D411, D412, D413, and D414 for each user on the list display page D4 using the received user ID, rules group name, and consent date and time as user identification information D421, rules group name D422, and date and time D423, respectively.

[0105] <Revised specific processing> The amendment specification process is a process of collecting amendment information related to legal amendments or changes in legal interpretation, storing it in the amendment master 1031, and specifying and presenting content information related to the amendment information. In this disclosure, the amendment specification process for content information in general will be described, and the amendment specification process for regulations information, which is one type of content information, will be described in detail in particular.

[0106] <Outline of revised specific processing> The amendment identification process is a series of processes that collect amendment information regarding legal amendments or changes in the interpretation of law and store it in the amendment master 1031, acquire content information, calculate information regarding the impact of the amendment information on the content information based on the amendment information and the content information, store the information regarding the impact in association with the content information, and present the information regarding the impact in association with the content information. In addition, measures to be taken in response to the revision information may be suggested to the user in association with the content information, and comments such as memos on the content information may be accepted from the user.

[0107] <Details of the revised specific processing> The details of the amendment specific processing are explained below.

[0108] In step S501, the revision unit 1051 of the server 10 executes a revision acquisition step of acquiring revision information related to legal revisions or changes in the interpretation of laws. Specifically, the revision unit 1051 of the server 10 stores revision information including the title, revision content, rule data, and policy data in the revision master 1031 in response to legal revisions or changes in legal interpretation. Specifically, an administrator of an information processing service or the like according to the present disclosure inputs information regarding the title, revision content, rule data, and policy data via his / her own information processing terminal, and transmits the information to the server 10. The revision unit 1051 of the server 10 stores the received title, revision content, rule data, and policy data in the title, revision content, rule data, and policy data items of a new record in the revision master 1031, respectively. In addition, the revision unit 1051 of the server 10 collects (scrapes) information regarding legal revisions from websites etc. provided by the government, competent ministries and agencies, and generates title, revision content, rule data, and policy data from the collected information by using any natural language processing technology based on a large-scale language model (LLM), deep learning technology, machine learning technology, artificial intelligence technology, etc., and stores the generated title, revision content, rule data, and policy data in the title, revision content, rule data, and policy data fields of a new record in the revision master 1031, respectively. That is, the amendment information stored in the amendment master 1031 may be stored by being manually input and edited by a user or the like, or may be automatically edited and stored by the amendment unit 1051 of the server 10. Note that the storage process in the amendment master 1031 does not necessarily have to be executed in the amendment specification process, and may be configured to be executed at any timing such as legal amendment, or periodically.

[0109] The amendment acquisition step executes a step of acquiring amendment information including conditions related to the content, conditions related to the type of content, conditions related to the terms and conditions information, conditions related to the type of terms and conditions, conditions related to clauses or provisions included in the terms and conditions information, and the like. The amendment acquisition step executes a step of acquiring amendment information including a condition related to the content of the agreement included in the content and information regarding a corresponding measure associated with the condition. The amendment acquisition step executes a step of acquiring amendment information including conditions related to the contents of the agreement included in the regulation information and information regarding countermeasures associated with the conditions. Specifically, the revision unit 1051 of the server 10 refers to the revision master 1031 and acquires revision information including revision contents, rule data, and policy data. At this time, the revision unit 1051 of the server 10 acquires policy data associated with each of the rule data.

[0110] In step S502, the revision unit 1051 of the server 10 acquires and identifies the content. Specifically, the correction unit 1051 of the server 10 may collect (scrape), acquire, and identify information regarding content from the Internet, etc., by referring to a Uniform Resource Locator (URL) stored in advance by a user who uses the information processing service disclosed herein. The correction unit 1051 of the server 10 may collect, acquire, and identify information regarding content from within a specific LAN (Local Area Network) by referring to paths, etc. within the LAN that have been pre-stored by a user who uses the information processing service disclosed herein. In addition, the user may set conditions for scraping such as file names, titles of websites, attribute information attached to files: property information, meta information (including information written in any markup language such as JSON), tags, creator information, save date and time, update date and time, file size, file format (image, video, text), file extension, description language, link information to other pages and resources, whether a website contains a specific character string, whether a website contains specific content, etc. The revision unit 1051 of the server 10 may collect, acquire, and identify information about the content by referring to any network such as the Internet or a LAN based on the set conditions.

[0111] In step S502, the revision unit 1051 of the server 10 executes a content acquisition step of acquiring one or more pieces of content. The content acquisition step includes a rules acquisition step of acquiring rules information related to the terms of use. Specifically, the revision unit 1051 of the server 10 refers to the rules table 1015 and acquires one or more pieces of rules information. The acquired rules information may be all the rules information stored in the rules table 1015, or may be configured to acquire only the rules information related to the revision information acquired in step S501, for example. For example, when the rule data included in the revision information acquired in step S501 includes a condition related to a specific type of regulations, the revision unit 1051 of the server 10 may be configured to acquire only the regulation information included in that type. Similarly, when the rule data included in the revision information includes a condition related to the content of a specific clause or article, the revision unit 1051 of the server 10 may be configured to acquire only the contract information including the content of the specific clause or article.

[0112] The correction unit 1051 of the server 10 stores the content acquired in the content acquisition step in the storage unit 101. Specifically, the correction unit 1051 of the server 10 stores the acquired and specified content in a table or the like (not shown) of the storage unit 101.

[0113] In step S503, the revision unit 1051 of the server 10 executes a revision identification step of identifying one or more predetermined contents related to the revision information acquired in the revision acquisition step, from among the one or more contents acquired in the content acquisition step. Specifically, the revision unit 1051 of the server 10 calculates whether the content acquired in step S502 may be affected by the amendment of the law or the change in the interpretation of the law, based on the amendment details and rule data included in the amendment information.

[0114] In step S503, the revision identifying step executes a step of identifying one or more pieces of predetermined regulations information related to the revision information acquired in the revision acquiring step, from among one or more pieces of regulations information acquired in the content acquiring step. Specifically, the revision unit 1051 of the server 10 calculates whether the regulation information acquired in step S502 may be affected by the amendment of the law or a change in the interpretation of the law, based on the amendment contents and rule data included in the amendment information.

[0115] <Influence Calculation Process (First Embodiment)> The revision identification step executes a step of identifying one or more predetermined contents that are affected based on the revision information among the plurality of contents. The revision identification step includes an impact calculation step of calculating an impact level based on the revision information for the plurality of contents, and an identification step of identifying the predetermined content according to the impact level calculated in the impact calculation step. Specifically, the revision unit 1051 of the server 10 can calculate whether or not a given piece of content may be affected by legal amendments or changes in legal interpretation by using any natural language processing technology based on a large-scale language model (LLM), deep learning technology, machine learning technology, artificial intelligence technology, etc. For example, the impact on a combination of content and amendment information can be calculated based on document data, amendment contents, and rule data included in the content. In addition, this allows one or more pieces of content that may be affected by legal amendments or changes in legal interpretation to be acquired and identified from the multiple pieces of content acquired in step S502. In addition, an index (score) of the degree of influence, etc., may be calculated for each piece of content according to the degree to which it may be affected by legal amendments or changes in the interpretation of the law. Such an impact degree can be calculated by inputting the file name of the content, the title of the website, etc. if the content is a website, attribute information attached to the content file, the content of the content (content of clauses and articles in the case of terms of use), the amendment contents, and rule data into a large-scale language model. Specifically, the impact degree is calculated according to the type of content and the degree of relevance to the specific content based on the amendment contents and rule data. The revision unit 1051 of the server 10 acquires and identifies the content whose influence degree is equal to or greater than a predetermined value as one or more pieces of content that may be affected by legal revisions or changes in the interpretation of the law.

[0116] <Influence Calculation Process (Second Embodiment)> In step S503, the revision identifying step includes a step of determining whether each of the plurality of contents satisfies a condition included in the revision information, and a step of identifying a predetermined content that satisfies the condition. The revision identification step includes a step of determining whether a condition included in the revision information is satisfied for each of one or more pieces of regulations information, and a step of identifying predetermined regulations information that satisfies the condition. The revision identification step includes a step of determining whether the product or service covered by each of the one or more pieces of regulation information satisfies the conditions included in the revision information, and a step of identifying the specific regulation information that satisfies the conditions. Specifically, the revision unit 1051 of the server 10 may obtain and identify one or more pieces of content that may be affected by changes in law or interpretations of law, based on whether the content contained in the content matches the conditions contained in the rule data. For example, in the case where the rule information includes a condition related to a predetermined type of content, the revision unit 1051 of the server 10 may be configured to acquire and specify only the content included in the type. Similarly, if the content is terms of use and the rule data included in the amendment information includes conditions regarding specified contract clauses, contract articles, or the contents of the agreement, the amendment unit 1051 of the server 10 may be configured to obtain and identify only the terms of use that include the specified contract clauses, contract articles, or the contents of the agreement. Also, it is assumed that the rule data included in the revision information includes a condition for identifying a product or service to which the terms of use are applied. The revision unit 1051 of the server 10 acquires and identifies the terms of use information that is included in the conditions for identifying the product or service, based on the service name stored in the rules group table 1014 that is stored in association with the rules group ID of the acquired rules information or other information for identifying the product, service, etc. linked to the terms of use (service identification information). Note that the conditions for identifying the product or service do not need to directly include the service identification information, and the terms of use information may be identified based on the conditions for identifying the product, service type, etc., by referring to a table (not shown) that associates the service identification information with the product, service type, etc. It should be noted that if only the contents that satisfy the conditions included in the rule data have already been acquired in step S502, this step may be omitted.

[0117] In step S503, the revision identifying step includes a notification step of notifying the predetermined content identified in the identifying step, according to the degree of impact calculated in the impact calculation step. Specifically, the revision unit 1051 of the server 10 may acquire and identify one or more pieces of content that may be affected by the revision of the law or the change in the interpretation of the law in step S503, and may notify the user of the content. For example, the revision unit 1051 may be configured to notify any user involved in the procedure such as the creator of the content, a verifier, or the like, a manager in an organization to which the contracting party of the content belongs, or any other user having authority such as an administrator. For example, the revision unit 1051 of the server 10 notifies the user of text or summaries, etc., that associate the content included in the content, the title included in the revision information, the revision details, rule data, and policy data, via e-mail, chat service, etc.

[0118] In step S504, the revision unit 1051 of the server 10 stores information on the impact of the revision information on the content based on the revision information and the content calculated in step S503 in the revision flag item of the record of the content (if the content is terms of use, the record of the applicable terms information in the terms table 1015). The revision flag item may include basic information for calculating the impact in response to legal revisions or changes in the interpretation of the law, such as the revision ID, title, revision content, and rule data of the revision information. The revision unit 1051 of the server 10 also stores the policy data stored in association with the rule data in the revision master 1031 in the policy data item of the terms table 1015. This makes it possible to store, in association with each of one or more pieces of content that may be affected by legal amendments or changes in legal interpretation, related amendment information (amendment content) and policy information regarding the amendment content. This makes it possible to quickly identify contracts that need to be reviewed in response to legal changes, etc., as well as identify response measures that need to be taken, such as "urgent action is required," "revisions are required before the enforcement date," or "revisions are required by a certain date."

[0119] In step S505, the revision unit 1051 of the server 10 executes a presentation step of presenting the predetermined content identified in the revision identification step.

[0120] The first user operates the input device 216 of the first user terminal 21 to input the URL of a page for executing the revision presentation processing (revised presentation processing page) into a web browser or the like, and opens the revision presentation processing page. The control unit 214 of the first user terminal 21 sends a request to the server 10 to open the revision presentation processing page. The control unit 104 of the server 10 generates a revision presentation processing page based on the received request, and sends it to the first user terminal 21. The control unit 214 of the first user terminal 21 displays the received revision presentation processing page on the display 2181 of the first user terminal 21. The revision presentation process may be configured to be executable by any user, such as a manager or administrator in the organization or group to which the first user belongs, in addition to the second user.

[0121] 24 is an example of a revision presentation screen in the revision presentation process. A revision presentation page D5 is displayed on the display 2181 of the first user terminal 21. The revision presentation page D5 includes contents D51, D52, D53... The contents D51, D52, D53... include content types D511, D521, D531... indicating the types of content, impact levels 512, D522, D532..., revision contents D513, D523, D533..., rule data D514, D524, D534..., and policy data D515, D525, D535....

[0122] In step S505, a presentation step executes a step of presenting the predetermined content in association with a countermeasure associated with the content. Specifically, each of the contents D51, D52, D53, etc. is presented in association with the policy data D515, D525, D535, etc. This allows you to quickly identify the contents that need to be checked in response to legal changes, etc., and also to identify the countermeasures that need to be taken, such as "urgent action required," "revision required before the enforcement date," and "revision required by a certain date."

[0123] Users who receive content through the amendment identification process of the present disclosure will refer to the details of the response measures and revise the content by the deadline. This will save a huge amount of work time that was previously required to inventory, organize, and consider the degree of impact of all content related to the company in response to legal amendments or changes in legal interpretation. Users of the information processing service of the present disclosure can quickly identify affected content in response to amendment information and take appropriate legal action.

[0124] <Terms of Use Revision Process> This disclosure provides a detailed explanation of the revision of the Terms of Use. The revision unit 1051 of the server 10 executes a revision receiving step of receiving revised content for the predetermined content identified in the revision identifying step. Specifically, when rule information related to the terms of use is identified in the revision identification process in the present disclosure, the revision unit 1051 of the server 10 transmits a notification informing the first user terminal 21 of the revision work. The control unit 214 of the first user terminal 21 displays a revision notification screen including the received notification on the display 2181 of the first user terminal 21. The revision notification screen includes a button such as "Start revision work." The user operates the input device 216 of the first user terminal 21 to select a button such as "Start revision work" included in the notification content displayed on the display 2181 of the first user terminal 21. The control unit 214 of the first user terminal 21 transmits a request to start the revision work to the server 10. The revision unit 1051 of the server 10 receives the request. The revision unit 1051 of the server 10 searches the item of the rule ID in the rule table 1015 based on the rule ID included in the rule information to be revised (the rule information to be revised notified in step S505, hereinafter, the target rule information) and acquires the rule information. The revision unit 1051 of the server 10 also searches the item of the rule ID in the approver table 1016 based on the rule ID and acquires the approver information. The revision unit 1051 of the server 10 stores the acquired rules information in a new record of the rules table 1015 (revised rules information). The revision unit 1051 of the server 10 assigns a new rules ID to the revised rules information stored in the rules table 1015. The revision unit 1051 of the server 10 may store the date and time when the legal amendment, such as the enforcement date included in the rule data of the target amendment information, is applied (date and time specified based on the deadline included in the rule data of the target amendment information) in the item of the publication date and time of the revised rules information stored in the rules table 1015. In addition, when the enforcement date, etc. is not determined, the revision unit 1051 of the server 10 may be configured to set the item of the publication date and time of the revised rules information stored in the rules table 1015 to "shortest number of days" and "blank" and to accept the specification of the publication date and time from a separate user. Alternatively, the first user may input the date and time related to the enforcement date of the legal amendment at the publication date and time of the revised rules information. As a result, a duplicate (copy) of the target terms and conditions information is stored in the terms and conditions table 1015. In addition, the effective date is automatically entered as the publication date of the duplicated target terms and conditions information. This allows the user to publish the revised terms and conditions at an appropriate date and time without having to check details such as the effective date of the legal amendment.

[0125] Furthermore, the revision unit 1051 of the server 10 may store the acquired approver information in the approver table 1016 in association with the new regulation ID. At this time, the item of approval or non-approval is reset (information indicating that approval has not been granted is stored). This allows the first user to use the terms and conditions information regarding the terms and conditions before the revision in the revision work, and makes it possible to prevent input errors when revising the terms and conditions.

[0126] The first user can edit the revised terms and conditions information stored in the terms and conditions table 1015 by operating the input device 216 of the first user terminal 21. Specifically, the first user edits the revised terms and conditions information by executing the processes from step S102 onwards of the terms and conditions editing process. The first user refers to the policy information presented in step S505 and makes additions or corrections to the parts of the revised terms and conditions information that require revision. The first user may edit the name of the rules, the sentence of the rules, the rules group ID, etc. included in the revised rules information according to the revision contents. The first user may edit the approver ID, etc. included in the approver information according to the revision contents. For example, the first user may change the approval route of the approver according to the revision contents.

[0127] The revision unit 1051 of the server 10 executes a revision publishing step of publishing the revised content at a date and time specified based on the revision information acquired in the revision acquisition step.

[0128] When the terms editing process and the terms approval process are executed for the revised terms information, the terms of use are published according to the publication date and time of the revised terms information. Note that if the publication date and time of the revised terms information is stored as a date and time specified based on a deadline, etc. included in the rule data, etc. of the revision information that is the subject of the enforcement date, etc., the revised terms information is published at that date and time.

[0129] The revision publishing step includes a step of publishing the revised content by replacing the predetermined content with the revised content. The revising unit 1051 of the server 10 may execute a process of making the target rules information private when the revised rules information is made public. Specifically, in a case where the rules table 1015 is capable of managing rules information for each of a plurality of versions, the revising unit 1051 may execute a process of making only the latest one of the rules information (revised rules information) public based on the publication date and time, and making older rules information private. Alternatively, the target terms and conditions information may be kept publicly available, instead of being kept private, by posting it on a specified page or the like that posts past terms and conditions information, etc. In this case, when a visitor accesses the URL, etc. that was used to publish the target terms and conditions information after the enforcement date, the revised terms and conditions information will be viewable, not the target terms and conditions information. This allows users of the information processing service disclosed herein to avoid having to replace the terms of use, etc., on the enforcement date of the legal amendment.

[0130] In the process of revising the terms of use, the revision work of the terms of use has been described in detail, but the same applies to the revision work of content other than the terms of use. In the revision work of content other than the terms of use, the revised content may be stored in a storage such as a table or memory unit (not shown), and the revised content may be made public on the publication date (implementation date). For example, the pre-revision content may be replaced with the revised content on the publication date (implementation date).

[0131] <Basic computer hardware configuration> 25 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 includes at least a processor 901, a main storage device 902, an auxiliary storage device 903, and a communication IF 991 (interface). These are electrically connected to each other by a communication bus 921.

[0132] The processor 901 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0133] The main memory device 902 is for temporarily storing programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0134] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0135] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard. The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet via a specified access point (e.g., Wi-Fi (registered trademark)), etc. In the case of wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. In the case of wired connection, the network also includes a network that is directly connected by a USB (Universal Serial Bus) cable or the like.

[0136] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration among multiple computers 90 and connecting them together via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0137] <Basic functional configuration of computer 90> A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 25) of computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

[0138] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 connected to each other via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0139] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding the programs in the main storage device 902, and executing processes according to the programs. The control unit can realize functional units that perform various information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0140] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with a program. Furthermore, the control unit can cause the processor 901 to execute processes of adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0141] The term database refers to a relational database, which is used to manage sets of data called masters and tables in a tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table or master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Usually, a column that serves as a primary key for uniquely identifying a record is set in each table and each master, but setting a primary key in a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in a specific table or master stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0142] In addition, the database and master in this disclosure may include any data structure (such as a list, a dictionary, an associative array, or an object) in which information is structurally defined. The data structure also includes data that can be considered as a data structure by combining data with a function, class, method, or the like written in any programming language.

[0143] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0144] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0145] (Appendix 1) A program having a processor and a memory unit, which causes a computer to manage electronic content, wherein the processor executes a content acquisition step (S502) of acquiring one or more pieces of content, an amendment acquisition step (S501) of acquiring amendment information relating to legal amendments or changes in the interpretation of law, and an amendment identification step (S503) of identifying, from the one or more pieces of content acquired in the content acquisition step, one or more specified pieces of content related to the amendment information acquired in the amendment acquisition step. This makes it possible to identify electronic content related to legal amendments or changes in legal interpretation, and quickly identify electronic content that needs to be checked in response to legal amendments, etc.

[0146] (Appendix 2) The program described in Appendix 1, wherein the content acquisition step (S502) includes a terms acquisition step (S502) for acquiring terms information related to the terms of use, and the amendment identification step (S503) is a step for identifying one or more specified terms information related to the amendment information acquired in the amendment acquisition step from among one or more terms information acquired in the terms acquisition step. This allows you to identify terms of use related to legal amendments or changes in legal interpretation. You can quickly identify terms of use that need to be checked in response to legal amendments, etc.

[0147] (Appendix 3) A program described in Appendix 2, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to the regulations information, and the amendment identification step (S503) includes a step of determining whether each of one or more regulations information satisfies the conditions included in the amendment information, and a step of identifying specific regulations information that satisfies the conditions. This allows the terms of use to be identified according to the conditions included in the amendment information. Specifically, the terms of use are identified according to the contents of the terms of use and the conditions included in the amendment information.

[0148] (Appendix 4) The program described in Appendix 3, wherein the revision identification step (S503) includes a step of determining whether the product or service covered by each of the one or more pieces of regulation information satisfies the conditions included in the revision information, and a step of identifying specific regulation information that satisfies the conditions. This allows users to identify the terms of use for products or services that are affected by the amendment information from among the multiple terms and conditions information they manage. This makes it possible to quickly identify the terms of use that need to be checked in response to legal amendments, etc.

[0149] (Appendix 5) The program according to appendix 3, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to clauses or provisions included in the terms and conditions information. This allows users to identify the terms and conditions information that includes the clauses or provisions that are affected by the amendment information from among the multiple terms and conditions information they manage. This makes it possible to quickly identify the terms and conditions information that needs to be checked in response to legal amendments, etc.

[0150] (Appendix 6) The program according to claim 1, wherein the revision identifying step (S503) is a step of identifying one or more predetermined contents that are affected based on the revision information, among the plurality of contents. This allows one or more pieces of content that are affected based on a change in law or a change in the interpretation of the law to be identified. Depending on the amendment information, the affected content can be identified.

[0151] (Appendix 7) The program described in Appendix 6, wherein the revision identification step (S503) includes an impact calculation step of calculating an impact level for a plurality of contents based on revision information, and an identification step of identifying a specified content according to the impact level calculated in the impact calculation step. This allows content to be identified according to the degree of impact calculated based on changes in the law or changes in the interpretation of the law, and allows content with a large or large impact to be identified while content with no or little impact is excluded.

[0152] (Appendix 8) The program according to appendix 7, wherein the revision identification step (S503) includes a notification step of notifying the specified content identified in the identification step according to the degree of impact calculated in the impact calculation step. This allows the user to be notified of content that has a significant or significant impact based on changes in the law or changes in the interpretation of the law, and the user can take prompt action based on the changes in the law or changes in the interpretation of the law.

[0153] (Appendix 9) A program as described in Appendix 1, wherein the revision acquisition step (S501) is a step of acquiring revision information including conditions related to the content, and the revision identification step (S503) includes a step of determining whether each of a plurality of contents satisfies the conditions included in the revision information, and a step of identifying a specific content that satisfies the conditions. In this way, the content can be specified according to the condition included in the revision information. Specifically, the content is specified according to the content description and the condition included in the revision information.

[0154] (Appendix 10) The program according to claim 9, wherein the revision acquisition step (S501) is a step of acquiring revision information including conditions related to the type of content. This allows users to identify the content that is affected by the amendment information from among the multiple contents they manage. This allows users to quickly identify the content that needs to be checked in response to legal amendments, etc.

[0155] (Appendix 11) The program according to claim 9, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to the details of the agreement included in the content and information related to corresponding measures associated with the conditions. This makes it possible to quickly identify content that needs to be checked in response to changes in laws, etc., and also to identify measures that should be taken, such as changing the content, renewing contracts, and retroactive contracts.

[0156] (Appendix 12) The program described in Appendix 11, wherein the processor executes a presentation step (S505) of presenting the specified content identified in the revision identification step, the presentation step (S505) being a step of presenting the specified content in association with the response measures associated with the content. This makes it possible to quickly identify content that needs to be checked in response to changes in laws, etc., and also to check what measures should be taken, such as changing content, renewing contracts, and retroactive contracts.

[0157] (Appendix 13) A program as described in Appendix 1, in which a processor executes a revision reception step (S505) for accepting revised content for a specified content identified in the revision identification step, and a revision publication step (S505) for publishing the revised content at a date and time specified based on the revision information acquired in the revision acquisition step. This allows the user to prepare revised content for the identified content, and automatically publish the revised content at a predetermined timing, such as the enforcement date of the legal amendment.

[0158] (Appendix 14) The program according to claim 13, wherein the revision publishing step (S505) is a step of publishing the revised content by replacing the predetermined content with the revised content. This allows the user to prepare revised content for the identified content, and automatically replace the specified content with the revised content at a predetermined timing, such as the enforcement date of the legal amendment.

[0159] (Appendix 15) A method implemented on a computer having a processor and a memory, the processor performing all the steps performed in the invention according to any one of claims 1 to 14. This allows you to identify content that is related to legal changes or changes in the interpretation of the law. You can quickly identify content that needs to be checked in response to legal changes, etc.

[0160] (Appendix 16) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 14. This allows you to identify content that is related to legal changes or changes in the interpretation of the law. You can quickly identify content that needs to be checked in response to legal changes, etc.

[0161] (Appendix 17) A system comprising means for performing all the steps performed in any one of claims 1 to 14. This allows you to identify content that is related to legal changes or changes in the interpretation of the law. You can quickly identify content that needs to be checked in response to legal changes, etc. [Explanation of symbols]

[0162] 1 System, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 21 First user terminal, 211 Memory unit, 214 Control unit, 216 Input device, 218 Output device, 22 Second user terminal, 221 Memory unit, 224 Control unit, 226 Input device, 228 Output device, 23 Third user terminal, 231 Memory unit, 234 Control unit, 236 Input device, 238 Output device

Claims

1. A program for causing a computer to manage electronic content, the program comprising: a processor; and a storage unit; the processor: a content acquisition step of acquiring one or more pieces of content; an amendment acquisition step of acquiring amendment information regarding amendments to laws or changes in the interpretation of laws; a revision identification step of identifying one or more predetermined contents related to the revision information acquired in the revision acquisition step from among the one or more contents acquired in the content acquisition step; A program that executes.

2. the content acquisition step includes a terms acquisition step of acquiring terms information regarding terms of use; The amendment identification step is a step of identifying one or more predetermined regulation information related to the amendment information acquired in the amendment acquisition step from the one or more regulation information acquired in the regulation acquisition step. The program according to claim 1.

3. the amendment acquisition step is a step of acquiring the amendment information including conditions related to the regulation information, The amendment specifying step includes: determining whether the one or more pieces of regulation information each satisfy the condition included in the revision information; Identifying the predetermined rules information that satisfies the condition; Including, The program according to claim 2.

4. The amendment specifying step includes: determining whether the products or services covered by each of the one or more pieces of regulation information satisfy the conditions included in the amendment information; Identifying the predetermined rules information that satisfies the condition; Including, The program according to claim 3.

5. The revision identification step is a step of identifying predetermined content related to the revision information based on information output by inputting the content and the revision information into a large-scale language model. The program according to claim 1.

6. The amendment acquisition step is a step of acquiring the amendment information including the conditions related to the clauses or provisions included in the regulation information. The program according to claim 3.

7. The revision identification step is a step of identifying one or more of the predetermined contents that are affected based on the revision information among the plurality of contents. The program according to claim 1.

8. The amendment specifying step includes: an impact calculation step of calculating an impact level based on the revision information on the plurality of contents; a specifying step of specifying the predetermined content in accordance with the degree of influence calculated in the influence calculation step; Including, The program according to claim 7.

9. The impact calculation step is a step of calculating the impact by inputting the content and the revision information into a large-scale language model. The program according to claim 8.

10. The amendment specifying step includes: a notification step of notifying the predetermined content identified in the identification step in accordance with the degree of impact calculated in the impact calculation step; Including, The program according to claim 8.

11. The notification step is a step of notifying the user of information related to the predetermined content identified in the identification step via email or a chat service. The program according to claim 10.

12. the revision acquisition step is a step of acquiring the revision information including a condition related to the content; The amendment specifying step includes: determining whether each of the plurality of contents satisfies the condition included in the revision information; identifying the predetermined content that satisfies the condition; Including, The program according to claim 1.

13. the revision acquisition step is a step of acquiring the revision information including the condition related to the type of content; The program according to claim 12.

14. The amendment acquisition step is a step of acquiring the amendment information including the conditions related to the details of the agreement included in the content and information related to countermeasures associated with the conditions. The program according to claim 12.

15. The amendment acquisition step is a step of collecting information on legal amendments by scraping from websites provided by the government or competent ministries and agencies, and acquiring the amendment information generated by applying natural language processing technology including a large-scale language model to the collected information. The program according to claim 1.

16. the processor: a presentation step of presenting the predetermined content identified in the revision identification step; Run the presenting step is a step of presenting the predetermined content in association with the response measures associated with the content; The program according to claim 14.

17. the processor: a revision receiving step of receiving revised content for the predetermined content identified in the revision identifying step; a revision publishing step of publishing the revised content at a date and time specified based on the revision information acquired in the revision acquisition step; To execute The program according to claim 1.

18. the revision publishing step is a step of publishing the revised content by replacing the predetermined content with the revised content; 18. The program of claim 17.

19. A method implemented on a computer having a processor and a memory, wherein the processor performs all of the steps performed in any of the inventions according to claims 1 to 18.

20. 19. An information processing device comprising a control unit and a storage unit, wherein the control unit executes all of the steps executed in any one of the inventions according to claims 1 to 18.

21. A system comprising means for executing all steps performed in an invention according to any one of claims 1 to 18.

Images