JP2024065540A - Rule management program, information processing apparatus, production method, and information processing method - Google Patents

Abstract

To provide a rule management program which allows a user to receive a presentation of appropriate terms of use according to attribute information, based on various terms of use provided by various business operators, an information processing apparatus, a production method, and an information processing method.SOLUTION: A rule management program executes: a rule acquisition step of acquiring rule information on a plurality of terms of use for each product or service provided by each business operator, from business operator servers which are managed by multiple different business operators; a rule storage step of storing, on a storage unit, each of the acquired multiple pieces of rule information in association with predetermined attribute information; a search reception step of receiving search conditions including at least attribute information from a user; a rule search step of searching for predetermined one or more pieces of rule information from the multiple pieces of rule information stored in the rule storage step, based on the received search conditions; and a rule presentation step of presenting, to the user, at least a part of the searched predetermined one or more pieces of rule information.SELECTED DRAWING: Figure 16

Description

This disclosure relates to a policy management program, an information processing device, a manufacturing method, and an information processing method.

2. Description of the Related Art 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 rules such as conditions of use for the use of the services they provide to users.
Patent Literature 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.

JP 2018-005442 A

Businesses that provide web services, etc. face the challenge of not being able to search for terms of use when creating them.
Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technique for searching for terms of use.

A terms management program for storing electronic terms of use in a computer having a processor and a storage unit, the processor executing a terms acquisition step of acquiring terms information relating to multiple terms of use for each product or service provided by a multiple business operator from multiple business operators' ...

According to the present disclosure, users can be presented with suitable terms of use based on their attribute information, based on various terms of use offered by various businesses.

FIG. 2 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. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 21. 2 is a block diagram showing a functional configuration of a second user terminal 22. FIG. 2 is a block diagram showing a functional configuration of a third user terminal 23. FIG. FIG. 13 is a diagram showing the data structure of a user table 1012. FIG. 11 is a diagram showing the data structure of a group table 1013. FIG. 13 is a diagram showing the data structure of a rules group table 1014. FIG. 13 is a diagram showing the data structure of a rules table 1015. FIG. 13 is a diagram showing the data structure of an approver table 1016. FIG. 13 is a diagram showing the data structure of a consent table 1021. FIG. 11 is a diagram showing the data structure of a clause table 1031. 13 is a flowchart showing the operation of a rules editing process. 13 is a flowchart showing the operation of a rules approval process. 13 is a flowchart showing the operation of a rules agreement process. 13 is a flowchart showing the operation of a rules collection process. 13 is a screen example of a selection screen for a rules display rules group in rules editing processing. 13 is a screen example of a terms of use selection screen in terms of use editing processing. 13 is a screen example of an editing screen for a rules text in a rules editing process. 13 is a screen example of a terms of use approval screen in the terms approval process. 13 is a screen example of a user registration screen in the terms and conditions agreement process. 13 is a screen example of a user consent screen for terms of use in the terms consent process. 13 is a screen example of a list screen of consent information in the agreement consent process. FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90.

Embodiments of the present disclosure will be described below with reference to the drawings. In all figures describing the embodiments, common components are given the same reference numerals, and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the contents of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each figure is a schematic diagram, and is not necessarily a precise illustration.

<Configuration of System 1>
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, 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, EC (Electronic Commerce), and the like.
In this disclosure, as an example, a first user is described as a creator who creates the terms of use, a second user is described as an approver who approves the terms of use created by the first user, and a third user is described 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.

Each information processing device is configured by a computer equipped with an arithmetic unit 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.

<Configuration of Server 10>
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 memory unit 101 and a control unit 104 .

<Configuration of storage unit 101 of server 10>
The memory 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 clause table 1031 .

The application program 1011 is a program that causes the control unit 104 of the server 10 to function as each functional unit.

The 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 the user table 1012. This allows the user to use the service according to the present disclosure.
The user table 1012 is a table having a user ID as a primary key and columns of a user ID, a user name, and a group ID.
FIG. 6 is a diagram showing the data structure of the user table 1012. As shown in FIG.

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.

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.

The group ID is an item for storing group identification information for identifying a group. The group identification information is an item in 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 who has administrator authority can arbitrarily determine and set a user who has a certain or higher position or authority in a group such as an organization.

The rules group table 1014 is a table for storing and managing information (rules group information) related 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 a rules group ID as a primary key and columns of rules group ID, rules group name, group ID, service name, posted page URL, and publication date and time.
FIG. 8 is a diagram showing the data structure of the rules group table 1014. As shown in FIG.

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 that stores 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 posting page URL is an item for storing the URL of the web page on which the rules group specified by the rules group identification information is posted. Typically, the URL of the user registration screen of the web service on which the rules group is set is 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.

The rules table 1015 is a table for storing and managing information on 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, and attribute information.
FIG. 9 is a diagram showing the data structure of the rules table 1015. As shown in FIG.

The "rules ID" is an item for storing rules identification information for identifying the terms of use. The rules identification information is an item for which a unique value is set for each rule 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 for storing text related to the terms of use. The terms and conditions text may specifically 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 specifies the text data, a path, etc. may be stored.
The attribute information is an item for storing attribute information of the terms of use. The attribute information of the terms of use includes the following information.
・Business attributes of the business providing the terms of use (name, business size, industry, number of employees, listing type (whether the business is listed or not), capital adequacy ratio, credit information, etc.)
- Product attributes related to the products or services to which the Terms of Use apply (service name, category, genre, number of users, whether or not the service handles personal information)
・Terms of use language, governing law, jurisdiction and legal source ・Terms of use version, revision date ・Number of characters in the terms of use, whether specific technical terms are included, etc.

The approver table 1016 is a table for storing and managing information on approvers of the rules information (approver information). One or more approver information can be assigned to one rules information.
The approver table 1016 is a table having columns for a rule ID, an approver ID, and approval/non-approval.
FIG. 10 is a diagram showing the data structure of the approver table 1016. As shown in FIG.

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.

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.

The user ID is an item for storing user identification information for identifying a user. The user identification information is a character string for specifying a user.
The IP address is an item for storing 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 that stores the date and time when the user identified by the user ID agreed to the rules information related to the rules ID.

The clause table 1031 is a table for storing and managing information relating to clauses (clause information).
The clause table 1031 is a table having a clause ID as a primary key and columns of clause ID, regulation ID, clause name, clause type, and clause text.
FIG. 12 is a diagram showing the data structure of the clause table 1031.

The clause ID is an item for storing clause identification information for identifying a clause. The clause identification information is an item in which a unique value is set for each clause information.
The rule ID is an item for storing rule identification information for identifying a rule.
The clause name is an item for storing the heading (clause name) of a clause.
The clause type is an item for storing clause type information indicating the type of clause. The clause type information is an item for storing type information of clauses constituting the terms of use, such as application, registration, management of user ID and password, usage fee and payment method, prohibited matters, suspension of provision of the service, etc., usage restrictions and cancellation of registration, withdrawal, change of service content, etc., change of terms of use, handling of personal information, etc.
The clause text is an item for storing text such as clauses, articles, etc. The clause text is a document that specifies the rights and obligations of a user when using a web service for which the terms of use specified by the terms of use identification information are set.

<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 rules collection unit 1051. The control unit 104 executes an application program 1011 stored in the storage unit 101 to realize each functional unit.

The user registration control unit 1041 performs a process of storing information about users who wish to use the service according to the present disclosure in the user table 1012 .
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, inputs 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.

The rules editing unit 1042 executes rules editing processing. Details will be described later.

The rules approval unit 1043 executes the rules approval process. Details will be described later.

The terms and conditions agreement unit 1044 executes the terms and conditions agreement process. Details will be described later.

The rules collection unit 1051 executes the rules collection process. Details will be described later.

<Configuration of First User Terminal 21>
The first user terminal 21 is an information processing device operated by a first user who uses the service. The first user terminal 21 may be, for example, a mobile terminal such as a smartphone or a tablet, a stationary personal computer (PC) or a laptop PC, or a wearable terminal such as a head mounted display (HMD) or a wristwatch terminal.
The first user terminal 21 includes a memory unit 211 , a control unit 214 , an input device 216 , and an output device 218 .

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

The first user ID 2111 is the 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 service according to the present disclosure to the first user. The first user ID 2111 includes information such as a session ID that is temporarily assigned by the server 10 when identifying the first user who is using the first user terminal 21.

The application program 2112 may be pre-stored 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.
Application programs 2112 include applications such as a web browser application.
The application program 2112 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the first user terminal 21 .

<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.

<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 .

<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 .

<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 personal computer (PC) or a laptop PC, or a wearable terminal such as a head mounted display (HMD) or a wristwatch terminal.
The second user terminal 22 includes a storage unit 221 , a control unit 224 , an input device 226 , and an output device 228 .

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

The second user ID 2211 is the 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 that is temporarily assigned by the server 10 when identifying the user using the second user terminal 22.

The application program 2212 may be pre-stored 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.
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 .

<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.

<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 .

<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 .

<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 personal computer (PC) or a laptop PC, or a wearable terminal such as a head mounted display (HMD) 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 .

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

The third user ID 2311 is the 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 that is temporarily assigned by the server 10 when identifying the user using the third user terminal 23.

The application program 2312 may be pre-stored 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.
Application programs 2312 include applications such as a web browser application.
The application program 2312 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the third user terminal 23 .

<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 the application program 2312 stored in the storage unit 231, thereby realizing each functional unit.

<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 .

<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 .

<Configuration of business entity server 40>
The business server 40 is an information processing device managed and operated by a business that provides web services, application programs, apps, games, and the like (hereinafter, web services, etc.) to users via the Internet.
The business entity server 40 includes a storage unit 401 and a control unit 404. The control unit 404 of the business entity server 40 executes an application program 4012 stored in the storage unit 401, thereby providing websites, web pages, etc. that can be viewed by users, and providing web services, etc.
The business server 40 can communicate with the server 10 and user terminals such as a first user terminal 21, a second user terminal 22, and a third user terminal 23 via the network N.

<Operation of System 1>
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 rules collection 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 usage agreement 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 shows an example of a screen displaying a list of consent information in the agreement consent process.

In the present disclosure, the terms editing process, terms approval process, and terms agreement process in the server 10 are described below. In the present disclosure, the first user associated with the creator performs the terms editing process via the first user terminal 21, the second user associated with the approver performs the terms approval process via the second user terminal 22, and the third user associated with 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, terms approval process, and terms agreement process may each be performed by any user.

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

<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 and the like, or to edit rules information that has already been created.

<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 group of terms and conditions, selects or creates terms of use to be included in the group of terms and conditions, edits the text of the terms and conditions 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.

<Details of the terms editing process>
The details of the rules editing process will be described below.

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

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

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 in the user table 1012 based on the first user ID 2111 and obtains the group ID (first group ID). The rules editing unit 1042 of the server 10 searches the group ID item in the rules group table 1014 based on the first group ID and obtains one or more rules group IDs (first rules group ID), rules group names (first rules group names), and service names (first service names). This identifies and accepts information (rules group information) related to a rules group consisting of one or more rules that can be referenced by the first user.

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 information in the information to be transmitted to the first user terminal 21.

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

The first user operates the input device 216 of the first user terminal 21 to select the group of rules D112, D113, etc. 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, etc. 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.

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.

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 .

18 is an example of a screen 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 name input field D131 for editing the terms of use 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 group 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.

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 fields of the rules group information record of the rules group table 1014 identified in step S101, respectively, and updates the information.

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 the terms 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 ID to the server 10. The terms editing unit 1042 of the server 10 receives and identifies the terms ID from the first user terminal 21.

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 editing unit 1042 of the server 10 creates and stores a record related to the new terms information in the terms table 1015. The terms editing unit 1042 of the server 10 identifies and stores the terms ID of the new record.

In step S103, 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 accepts edits 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.

19 is an example of a screen for editing 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.
The first user can edit the terms of use text of the terms of use identified in step S102 by operating the input device 216 of the first user terminal 21 and editing the terms of use text input field D153.

The terms editing screen D15 includes an attribute information input field D171 for inputting and specifying attribute information when searching for terms of use.

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 fields of the rule information record of the rule table 1015 identified in step S102, respectively, and updates the information.

<Terms Search Process (First Embodiment)>
In step S103, the rules editing unit 1042 of the server 10 executes a search receiving step of receiving search conditions including at least attribute information from the user.
Specifically, the first user operates the input device 216 of the first user terminal 21 to input attribute information into the attribute information input field D171. The attribute information in the terms of use is similar to the attribute information column in the rules table 1015. The control unit 214 of the first user terminal 21 transmits the attribute information input into the attribute information input field D171 to the server 10. The rules editing unit 1042 of the server 10 accepts the attribute information received from the first user terminal 21 as a search condition.

In step S103, the search receiving step may include a step of receiving search conditions including product attribute information related to the product or service.
Specifically, the first user operates the input device 216 of the first user terminal 21 to input product attributes (service name, category, genre, number of users) related to the product or service to which the terms of use apply, into the attribute information input field D171. The control unit 214 of the first user terminal 21 transmits the attribute information input into the attribute information input field D171 to the server 10. The terms editing unit 1042 of the server 10 accepts the attribute information received from the first user terminal 21 as a search condition.

In step S103, the rules editing unit 1042 of the server 10 executes a rules search step to search for one or more pieces of specified rules information from the multiple rules information stored in the rules storage step based on the search conditions received in the search reception step.
Specifically, the rules editing unit 1042 of the server 10 searches the attribute information items in the rules table 1015 based on the attribute information received from the first user terminal 21, and acquires the rules name and the rules text. The rules table 1015 stores rules information on multiple terms of use for each product or service, which are collected from business servers operated by various businesses by a rules collection process described later.
In addition, when searching the terms and conditions table 1015, the terms and conditions collection unit 1051 of the server 10 may search only for terms of use collected by the terms and conditions collection process described below based on the group ID item, which is the group ID to which the operator of the system 1 disclosed herein belongs, or information indicating that it is not associated with a specific group, such as null.

<Terms Search Process (Second Embodiment)>
In step S103, a search receiving step executes a step of receiving search conditions including user attribute information related to the user.
Specifically, in the rules search process (second embodiment), the first user operates the input device 216 of the first user terminal 21 and does not input anything into the attribute information input field D171. In the rules search process (second embodiment), the rules editing screen D15 may be configured not to include the attribute information input field D171.
In the rules search process (second embodiment), the rules editing unit 1042 of the server 10 searches the user ID field in the user table 1012 based on the first user ID 2111 of the first user, and obtains and identifies a group ID. The rules editing unit 1042 of the server 10 searches the group ID field in the group table 1013 based on the identified group ID, and obtains a group name. Note that in the present disclosure, the group name will be described as an example of the corporate name or company name of the company to which the first user belongs.
The terms and conditions editing unit 1042 of the server 10 queries corporate databases such as Teikoku Databank and Nikkei Telecom, and search engines such as Google and Yahoo, based on the corporate name and company name of the company to which the first user belongs, and identifies the business attributes of the company to which the first user belongs (name, company size, industry, number of employees, listing type whether the company is listed or not, capital adequacy ratio, credit information, etc.) as the user attributes of the first user. In addition, an external database in which information on various services and the like is stored may be consulted to identify product attributes (name, category, genre, number of users of the service) related to the product or service provided by the company to which the first user belongs, as the user attributes of the first user.
In other words, the user attributes of the first user may include business attributes of the company to which the first user belongs (name, company size, industry, number of employees, listing type (whether the company is listed or not), equity ratio, credit information, etc.), product attributes related to the product or service provided by the company to which the first user belongs (name, category, genre, number of users of the service), etc.
In addition, the user attributes of the first user may be configured to be stored in advance in the memory unit 101 of the server 10 by the first user separately operating the input device 216 of the first user terminal 21, inputting the user attributes in advance on a predetermined setting page or the like provided by the service disclosed herein, and transmitting the input attributes to the server 10.

The rules editing unit 1042 of the server 10 accepts the identified first user attribute as a search condition.

In step S103, a rule search step executes a step of searching for one or more pieces of predetermined rule information associated with attribute information equivalent to or similar to the user attribute information.
Specifically, the rules editing unit 1042 of the server 10 searches the attribute information items in the rules table 1015 based on at least a portion of the attribute information included in the received first user attribute, and obtains the rule name and rule text.

For example, the server 10's rules editing unit 1042 searches the attribute information items in the rules table 1015 based on the company size included in the first user attribute, and obtains the names of rules and the text of rules issued by companies of the same or similar size. This makes it possible to obtain the names of rules and the text of rules of the terms of use issued by companies of the same or similar size to the company to which the first user belongs.
For example, the server 10's rules editing unit 1042 searches the attribute information items in the rules table 1015 based on the business type included in the first user attributes, and acquires the name of the rules and the text of the rules issued by a company in the same or similar business type. This makes it possible to acquire the name of the rules and the text of the rules of the terms of use issued by a company in the same or similar business type as the company to which the first user belongs.
For example, the terms editing unit 1042 of the server 10 searches the attribute information items in the terms table 1015 based on the category and genre of the product or service included in the first user attribute, and obtains the names and texts of terms to which the target product or service is equivalent or similar. This makes it possible to obtain the names and texts of terms of use that apply to products or services of the same or similar category and genre of the product or service provided by the company to which the first user belongs.
This allows the first user to obtain a contract text that can be used as a reference when editing or creating the terms of use.

<Terms Search Process (Third Embodiment)>
In the terms and conditions search process (first embodiment) and the terms and conditions search process (second embodiment), terms and conditions information related to the terms of use is searched for based on attribute information, but it is also possible to configure the search to be possible for each clause constituting the terms of use, rather than for each term of use.
Specifically, when the first user operates the input device 216 of the first user terminal 21 to edit the terms sentence input field D153, the control unit 214 of the first user terminal 21 transmits words, terminology, etc. included in the terms sentence input by the first user to the server 10. The terms editing unit 1042 of the server 10 searches for the clause name, clause type, clause text, etc. in the clause table 1031 based on the received words, terminology, etc., and acquires the clause name and clause text. Note that the search conditions may include attribute information in the terms search process (first embodiment) and the terms search process (second embodiment), and attribute information of the terms of use to which the clause information is associated by the terms ID.
This allows the first user to obtain clause information that is useful when editing or creating the terms of use. The first user can create the terms of use while referring to the terms of use of other companies on a clause-by-clause basis.

<Terms presentation process>
In step S103, the rules editing unit 1042 of the server 10 executes a rules presenting step of presenting to the user one or more pieces of predetermined rules information searched for in the rules search step.
Specifically, the terms editing unit 1042 of the server 10 transmits terms information including the terms names and terms texts of one or more terms of use acquired by the terms search process (first embodiment) and the terms search process (second embodiment) to the first user terminal 21. The control unit 214 of the first user terminal 21 displays the received one or more terms of use information on the display 2181 of the first user terminal 21 in a manner selectable by the first user, and presents it to the first user. For example, the control unit 214 of the first user terminal 21 displays the terms names of one or more terms of use acquired by the terms search process in a selectable manner on the display 2181 of the first user terminal 21, and presents it to the first user.

<Terms Presentation Processing (First Embodiment)>
In step S103, a rule presentation step executes a step of presenting one or more pieces of rule information in order of the company size of the business entity that provides the rule information.
Specifically, the control unit 214 of the first user terminal 21 sorts the attribute information of one or more terms of use acquired by the terms search process based on the company size, such as sales, number of branches, number of employees, etc., included in the attribute information, and displays it on the display 2181 of the first user terminal 21 to present it to the first user. For example, the control unit 214 of the first user terminal 21 displays the one or more terms of use in order of sales, with the terms of use issued by companies with larger sales being displayed at a higher position where the first user can easily select them, and presents them to the first user.
This allows the user to receive terms of use in the order of the size of the business. In general, the larger the business scale, the more reliable the terms of use is considered to be, so the user can receive terms of use in the order of the most reliable terms of use.

<Terms Presentation Processing (Second Embodiment)>
In step S103, the rule presentation step executes a step of presenting one or more pieces of rule information in order of the most recent revision date of the rule information.
Specifically, the control unit 214 of the first user terminal 21 sorts the attribute information of one or more terms of use acquired by the terms search process based on the revision date, displays it on the display 2181 of the first user terminal 21, and presents it to the first user. For example, the control unit 214 of the first user terminal 21 displays the one or more terms of use in order of revision date, with the more recent the terms of use being displayed at a higher position that makes it easier for the first user to select them, and presents them to the first user.
In addition, when multiple different versions of terms of use are obtained for the same terms of use through the terms search process, the latest version of the terms of use may be obtained preferentially, and other older versions of terms of use may be excluded from the obtained results, thereby identifying the terms of use.
This allows the user to receive the terms of use in the order of the most recently revised terms of use. Also, when there are multiple different versions of one term of use, the user can receive the terms of use related to the newest version.

<Terms Presentation Processing (Third Embodiment)>
In step S103, a rule presentation step executes a step of presenting one or more pieces of rule information in order of priority of the rule information.
Specifically, the control unit 214 of the first user terminal 21 rearranges one or more terms of use acquired by the terms search process based on the priority calculated in the attribute information specification process (third embodiment) described later, displays them on the display 2181 of the first user terminal 21, and presents them to the first user. For example, the control unit 214 of the first user terminal 21 displays one or more terms of use in order of priority, with terms of use with higher priority displayed in a position that makes it easier for the first user to select them, and presents them to the first user.
This allows the user to receive terms of use from multiple terms of use collected from different businesses, in an order of priority based on changes in wording, such as the frequency of appearance of words, and trends.

In step S103, the terms and conditions editing unit 1042 of the server 10 executes a terms and conditions editing step of displaying a terms and conditions editing screen for editing the terms and conditions text to the user.
Specifically, the first user operates the input device 216 of the first user terminal 21 to select a terms of use name from one or more terms of use names displayed on the display 2181 of the first user terminal 21. The control unit 214 of the first user terminal 21 inputs the terms of use text of the terms of use specified by the selected terms of use name into the terms of use text input field D153. This allows the first user to efficiently edit and create his or her own terms of use by referring to the terms of use created by other companies found by the terms of use search process.

In step S103, a rules editing step executes a step of displaying a rules editing screen together with one or more pieces of rules information presented in the rules presentation step.
Specifically, the control unit 214 of the first user terminal 21 may display one or more terms of use in the terms presentation process, together with the terms text input field D153, on the display 2181 of the first user terminal 21 and present them to the first user.
This allows the user to edit the text of their own terms of use while checking the search results of the terms of use of other businesses, allowing the user to efficiently create and edit the text of their terms of use.

<Terms Presentation Processing (Fourth Embodiment)>
In the terms and conditions presentation process (first embodiment), the terms and conditions search process (second embodiment), and the terms and conditions search process (third embodiment), the terms and conditions are configured to present the terms of use, but it is also possible to present at least a part of the terms of use, such as one or more clauses, rather than the terms of use, or each clause information constituting the terms of use searched in the terms and conditions search process (third embodiment).
For example, in step S103, the rules editing unit 1042 of the server 10 executes a rules presentation step of presenting to the user one or more pieces of predetermined clause information searched for in the rules search step.
In addition, the terms and conditions editing step may execute a step of displaying a terms and conditions editing screen together with at least a portion of one or more terms and conditions information presented in the terms and conditions presentation step, or together with clause information constituting the terms of use searched in the terms and conditions search process (third embodiment).

<Terms of Use Presentation Process (Modified Example)>
In step S103, a terms presentation step generates a standard draft of terms of use based on one or more pieces of terms information searched in the terms search step, and executes a step of presenting the draft to the user.
Specifically, the control unit 214 of the first user terminal 21 transmits the terms of use IDs of the multiple terms of use acquired by the terms search process to the server 10. The terms of use editing unit 1042 of the server 10 searches the terms of use ID item in the terms table 1031 based on the received terms of use IDs, and acquires clause information consisting of multiple clause names and clause texts.
The terms and conditions editing unit 1042 of the server 10 performs clustering for equivalent or similar clause texts for each clause name based on multiple clause information associated with multiple terms of use acquired by the terms and conditions search process, and identifies clause texts used in many terms of use for each clause name. The server 10 creates one standard draft of terms of use by combining the clause information for each clause name used in many terms of use out of the clause information included in multiple different terms of use.
For example, the terms and conditions editing unit 1042 of the server 10 identifies one of the multiple terms and conditions acquired by the terms and conditions search process that matches the search conditions the most. The terms and conditions editing unit 1042 of the server 10 references the terms and conditions table 1031 to acquire multiple terms and conditions names included in the one term and conditions. For each acquired term, the terms and conditions editing unit 1042 of the server 10 identifies the terms and conditions text that is used in the most common terms and conditions for each term and conditions name among the multiple terms and conditions acquired by the terms and conditions search process, and replaces each term and condition of the one term and conditions with the terms and conditions text. This allows the terms and conditions editing unit 1042 of the server 10 to create one standard term and conditions in which each term and condition of the one term and conditions that matches the search conditions is replaced with the terms and conditions text that is used in many terms and conditions.
In addition, a single standard set of terms of use may be created by combining, replacing, merging, etc., in any manner, the terms information of multiple terms of use searched in the terms search process (first embodiment), terms search process (second embodiment), and terms search process (third embodiment), and the multiple clause texts for each clause that make up multiple terms of use.

The terms and conditions editing unit 1042 of the server 10 transmits the created standard 1 terms and conditions to the first user terminal 21. The control unit 214 of the first user terminal 21 inputs the terms and conditions text related to the received standard 1 terms and conditions into the terms and conditions text input field D153. This allows the first user to efficiently edit and create their own company's terms and conditions by referring to the standard 1 terms and conditions proposal generated in the terms and conditions presentation process (variant example).

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 information public immediately after approval by the approver, or "published at a specified date and time," which makes it possible to publish the information 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.

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

In step S105, the rules editing unit 1042 of the server 10 receives 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.

The rules editing unit 1042 of the server 10 searches the user ID field of the user table 1012 based on the second user ID, and obtains contact information such as a second email address of the second user.
The rules editing unit 1042 of the server 10 sends a message to the email address of the second user, 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 in 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 obtained by arbitrarily encrypting 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.

It is possible to omit input of the approver information. In that case, the terms of use are made public to the user 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 approval screen in the terms agreement process described below, which can be referenced by users, etc.

<Terms approval process>
The terms of use approval process is a process in which a second user, who is an 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.

<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 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 the user.

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

In step S201, the agreement approval unit 1043 of the server 10 accepts information (agreement information) on the predetermined terms of use 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 the URL listed in the received message, thereby opening a web page (terms and conditions 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 and conditions editing process.

Figure 20 is an example of a terms of use approval screen in the terms approval process. A terms of use approval page D2 is displayed on the display 2281 of the second user terminal 22. 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 revert button D216, related parties D217, and related terms D218 that display other terms of use, terms of use, etc. that are related to the terms of use displayed on the terms of use approval screen D21 and that will be affected by changes.

In step S202, the second user checks the content 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 contents of the terms of use text by operating the input device 226 of the second user terminal 22 and inputting and editing the contents of the input field for the terms of use 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 the terms of use to the first user.

In step S203, if the second user has no problem with the contents of the confirmed terms and conditions 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 and conditions to the server 10.

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 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 approved by the approver.
As a result, it is stored 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 approval screen in the terms of use agreement process described later, which can be referenced by users, etc.

<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, and D315 for opening the respective rules texts are displayed in an embedded form in the user registration screen D31.
In addition, the user registration screen D31 may be generated by dynamically embedding the 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 the term group is added, deleted, or the term name is changed in the term editing process, the links D313, D314, and D315 embedded in the user registration screen D31 are automatically added, deleted, and 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 the HTML text, etc.
Using the service disclosed herein, users can efficiently and centrally manage policy information relating to terms of use that is distributed across one or more web services.

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 sends a message to the first user via email, chat service, etc., 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 sent to the first user. The first user then resolves the reason for the return and executes the terms editing process again.

<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.

<Overview of terms and conditions agreement process>
The terms and conditions agreement process is a series of processes in which a third user related to a user opens a specified web service, application program, app, game, etc., selects the terms of use from the user registration or login screen, checks the contents of the terms and conditions text of the selected terms of use, and agrees to the terms and conditions.

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

In step S301, a third user opens a website operated by an operator other than 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 operator. The control unit 234 of the third user terminal 23 transmits a request to open the user registration page to the operator server 40 operated by the 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 rules 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 rules information to the server 10 based on the predetermined HTML tag capable of identifying a predetermined rules group ID, a markup language such as JavaScript (registered trademark), and a programming language written on the received user registration page. The rules agreement unit 1044 of the server 10 searches for the rules group ID item in the rules table 1015 based on the received rules group ID, acquires the rules ID and rules name, and transmits them to the business server 40. The business server 40 embeds a link including the acquired rules name and rules ID in the user registration page to generate a user registration screen D31, and displays it on the display 2381 of the third user terminal 23.
In addition, 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, sending 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 that can identify 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.

21 shows 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 of 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 of 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.

In step S302, 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 identification information (terms 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 name of the rules and the text of the rules.
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 agreement page, but the business server 40 may inquire about the terms information of the server 10 and generate the terms of use agreement page.

Figure 22 shows an example of a terms of use consent screen displayed by a user during the terms consent process. The 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.

In step S303 , 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 .
Specifically, 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 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 fields in the agreement table 1021, respectively.

The third user operates the input device 236 of the third user terminal 23 to select all of 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 rules group ID of the third user to the server 10.
The rules agreement unit 1044 of the server 10 searches the agreement table 1021 based on the IP address included in the request, and acquires the rules ID (agreed rules 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 terms and conditions consent unit 1044 of the server 10 compares the consent terms and conditions ID with the terms and conditions IDs of all the terms and conditions included in the set of terms and conditions of the web service to determine whether the third user has consented to all the terms and conditions displayed on the user registration screen D31. Specifically, if the consent terms and conditions ID includes all the terms and conditions IDs of all the terms and conditions included in the set of terms and conditions of the web service, it is determined that the third user has consented to all the terms and conditions displayed on the user registration screen D31.
If the terms and conditions agreement unit 1044 of the server 10 determines that the third user has agreed to all of the terms and conditions 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 and conditions displayed on the user registration screen D31.
When the business entity 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 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 registers the user in the web service operated by the business based on the received email address and password.

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 is associated with the terms and conditions ID and the date and time of agreement to the terms and conditions identified by the terms and conditions ID and stored. As a result, the fact that the third user has agreed to the terms and conditions is stored in the agreement table 1021.
In the present 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 email address of the user to the terms of use management service disclosed herein.

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, storage of the IP address may be omitted. This makes it possible to omit collection and storage of unnecessary information such as the third user's IP address.

<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, etc., 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.

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 field 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 field 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 rules ID.
The rules consent unit 1044 of the server 10 searches the rules ID in the consent table 1021 based on the acquired rules ID, and acquires the user ID and the date and time of consent.
The terms and conditions consent unit 1044 of the server 10 identifies a 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 received user ID, rules group name, and agreement date and time as user identification information D421, rules group name D422, and date and time D423, respectively, and displays the agreement information D411, D412, D413, and D414 for each user on the list display page D4.

<Terms collection process>
The policy collection process is a process of collecting (scraping) policy information regarding multiple terms of use for each product or service provided by various businesses from business servers operated by those businesses and storing the information.
The rules collection process may be performed by an employee of the operator of the information processing system according to the present disclosure, or the rules collection unit 1051 of the server 10 may be configured to perform the process periodically (hourly, daily, weekly, or monthly).

<Overview of the Terms of Use Collection Process>
The rules collection process is a series of processes that access a web page on which rules information relating to the terms of use is posted, acquires the rules information, identifies attribute information of the terms of use, and stores the attribute information in association with the rules information.

<Details of the Terms of Use Collection Process>
The details of the rules collection process will be described below.

In step S501, the terms and conditions collection unit 1051 of the server 10 executes a terms and conditions acquisition step of acquiring, from multiple business server operated by multiple different business operators, terms and conditions information regarding multiple terms of use for each product or service provided by each business operator.
Specifically, the terms and conditions collection unit 1051 of the server 10 refers to a database (not shown) that stores URLs of web pages on which products or services provided by various businesses are posted, and acquires and identifies the URL of the web page on which the terms and conditions are posted. The terms and conditions collection unit 1051 of the server 10 may also acquire and identify the URL of the web page on which the terms and conditions are posted, by referring to search results of a search using a keyword such as "terms of use" in a search engine such as Google or Yahoo, and the links of the web pages listed in the search results.
In addition, the URL of the web page may be obtained and identified by having an employee of the operator of the information processing system disclosed herein search for various products, services, etc. in advance using a search engine or the like, and creating a list of URLs of web pages on which the terms of use are posted based on the search results, and then obtaining and identifying the URL based on the list.
The terms and conditions collection unit 1051 of the server 10 accesses the specified URL and acquires the terms and conditions text of the terms and conditions posted on the web page. The terms and conditions text may be text data in any format such as HTML, Word, PDF, XML, etc. Also, if multiple terms and conditions are prepared for one product or service, the terms and conditions text of each of the terms and conditions is acquired.

In step S502, the rules collection unit 1051 of the server 10 executes a rules storage step in which the multiple rules information acquired in the rules acquisition step is associated with predetermined attribute information and stored in the storage unit.

The rule storage step executes a step of storing in the storage unit, in which a business attribute related to a business providing the rule information is associated with each of the plurality of rule information.
The rule storage step includes a step of storing in the storage unit a name of a provider of the rule information in association with each of the plurality of rule information.
The rule storage step executes a step of storing, in the storage unit, information on the type of business or the size of the company of the provider of the rule information in association with each of the plurality of rule information.
The rule storage step executes a step of associating each of the plurality of rule information with product attribute information related to the product or service to which the rule information applies, and storing the information in the storage unit.
The rule storage step executes a step of storing, in the storage unit, a step of associating each of the plurality of rule information with the name of the product or service to which the rule information applies.
The rule storage step executes a step of storing, in the storage unit, a step of associating each of the plurality of rule information with a category of a product or service to which the rule information applies.
The rules storage step executes a step of storing, in a storage unit, rules attribute information relating to any one of the language, governing law, court of jurisdiction, and source of law of the multiple rules information acquired in the rules acquisition step in association with each other.
The rules storage step executes a step of storing, in the storage unit, information on the corporate size of the business entity that provided the rules information in association with each of the plurality of rules information.
The rules storage step executes a step of storing each of the different versions of the multiple rules information acquired in the rules acquisition step in association with a revision date of the rules information.

Specifically, the rules collection unit 1051 of the server 10 creates and stores a record relating to new rules group information for one product or service in the rules group table 1014. The rules collection unit 1051 of the server 10 identifies and stores the rules group ID of the new record.
The rules collection unit 1051 of the server 10 stores arbitrary character strings such as the name of one product or service, the name of a business operator, etc., in the rules group name and service name fields of a record related to new rules group information. In the posting page URL field of the record related to new rules group information, the URL of a user registration screen, etc., of one product or service is stored.
The rules collection unit 1051 of the server 10 stores the group ID to which the operator of the system 1 according to the present disclosure belongs as the group ID of the record related to the new rules group information. In addition, since the terms of use collected by the rules collection unit 1051 of the server 10 are not terms of use created by the user of the information processing system according to the present disclosure in a rules editing process or the like, the group ID may be configured to store information indicating that the group ID is not associated with a specific group, such as null.

The terms and conditions collection unit 1051 of the server 10 analyzes the text data of the terms and conditions acquired in step S501, and identifies information such as the terms and conditions name, which is the name of the terms and conditions, and the publication date.
The terms and conditions collection unit 1051 of the server 10 identifies attribute information of the terms and conditions based on the terms and conditions text of the terms and conditions acquired in step S501, the URL of the webpage on which the terms and conditions are posted, the contents of other webpages posted on the webpage on which the terms and conditions are posted, etc. The identification of the attribute information of the terms and conditions will be described later in the attribute information identification process.

The rules collection unit 1051 of the server 10 stores the rules group ID of the new record, the identified rules name, publication date, the rules text of the terms of use acquired in step S501, and the identified attribute information in the rules group ID, rules name, publication date and time, rules text, and attribute information fields of the record related to the new rules information in the rules table 1015. The rules collection unit 1051 of the server 10 identifies and stores the rules ID of the new record. Note that the record related to the new rules information may be configured to be stored in association with a URL where the terms of use of the rules information are posted.

The terms and conditions collection unit 1051 of the server 10 analyzes the terms and conditions text of the terms of use acquired in step S501, divides each clause contained in the terms and conditions text into clause text, and identifies the clause name and clause type for each clause text. The terms and conditions collection unit 1051 of the server 10 stores the terms and conditions ID, clause name, clause type, and clause text of the new record in the terms and conditions ID, clause name, clause type, and clause text fields of the record related to the new clause information in the clause table 1031. The terms and conditions collection unit 1051 of the server 10 identifies and stores the clause ID of the new record.

<Attribute Information Identification Processing>
In step S502, the rules storage step identifies specific attribute information by analyzing the contents of web pages included in the website from which the multiple rules information acquired in the rules acquisition step was obtained, and executes a step of associating the identified attribute information and storing it in a memory unit.
The process of acquiring and identifying attribute information of the terms of use acquired in step S501 will be described below.

<Attribute Information Identification Process (First Embodiment)>
The rule storage step executes a step of identifying predetermined attribute information by analyzing each rule sentence of the plurality of rule information, and storing the identified attribute information in the storage unit in association with the predetermined attribute information.

Specifically, the terms and conditions collection unit 1051 of the server 10 identifies the attribute information of the terms and conditions by analyzing the contents of the text data of the terms and conditions acquired in step S501.

For example, the terms and conditions collection unit 1051 of the server 10 identifies the name of the business providing the terms of use based on a character string identifying the business issuing the terms of use, which is written at the end of the terms of use, etc. The terms and conditions collection unit 1051 of the server 10 queries business databases such as Teikoku Databank and Nikkei Telecom, and search engines such as Google and Yahoo, based on the name of the business, and identifies the business attributes of the business, such as company size, industry, number of employees, listing type (whether the company is listed or not), capital adequacy ratio, credit information, etc.
For example, the terms and conditions collection unit 1051 of the server 10 analyzes the contents of the text data of the terms of use acquired in step S501 to identify the name of the product or service to which the terms of use apply. The terms and conditions collection unit 1051 of the server 10 also analyzes other pages of the website on which the terms of use acquired in step S501 are posted, and identifies the category, genre, whether the service handles personal information, and the like of the product or service to which the terms of use apply, based on keywords and the like listed on the website. Additionally, the terms and conditions collection unit 1051 of the server 10 may refer to an external database or the like storing information on various services, based on the name of the service, and identify the category, genre, whether the service handles personal information, and the number of users as product attributes.
For example, the terms and conditions collection unit 1051 of the server 10 analyzes the contents of the text data of the terms of use acquired in step S501 to identify terms and conditions attributes related to any one of the language of the terms of use, the governing law, the competent court, the source of law, the number of characters in the terms of use, and whether or not a specific technical term is included. Specifically, the terms and conditions collection unit 1051 of the server 10 can identify the governing law and the competent court by analyzing the character string of the clause on the governing law and the character string of the clause on the competent court included in the terms of use, respectively.
For example, the terms and conditions collection unit 1051 of the server 10 identifies the version and revision date of the terms and conditions by analyzing the content of the text data of the terms and conditions acquired in step S501. Specifically, the terms and conditions collection unit 1051 of the server 10 can identify the version and revision date by analyzing the character string of the version of the terms and conditions and the character string of the revision date written at the end of the terms and conditions, etc. Also, by including the version and revision date of the terms and conditions in the terms and conditions attribute information for one term of use, different versions of the terms and conditions are stored in association with the revision date of the term of use.
For example, the terms and conditions collection unit 1051 of the server 10 analyzes the content of the text data of the terms and conditions acquired in step S501 to determine the number of characters in the terms and conditions, whether or not specific technical terms are included, and the like.

<Attribute Information Identification Process (Second Embodiment)>
In step S502, the rules storage step identifies specific attribute information based on the domain name of the website from which the multiple rules information acquired in the rules acquisition step was obtained, and executes a step of associating the identified attribute information and storing it in a memory unit.
In step S502, the rules storage step identifies specific attribute information by analyzing the URL from which the multiple rules information acquired in the rules acquisition step was obtained, and executes a step of associating the identified attribute information and storing it in a memory unit.

Specifically, the terms and conditions collection unit 1051 of the server 10 acquires the domain name of the URL from which the terms and conditions acquired in step S501 were acquired. Based on the domain name, the terms and conditions collection unit 1051 of the server 10 queries a database such as WHOIS that stores domain names associated with businesses operating the domains, and identifies the name of the business that provides the terms and conditions.
The terms and conditions collection unit 1051 of the server 10 queries corporate databases such as Teikoku Databank and Nikkei Telecom based on the name of the business in question, and identifies the business attributes of the business in question, such as company size, industry, number of employees, listing type (whether the company is listed or not), capital adequacy ratio, credit information, etc.

<Attribute Information Identification Process (Third Embodiment)>
In step S502, the rules storage step includes a step of storing each of the different versions of the multiple rules information acquired in the rules acquisition step in association with the revision date of the rules information, and a step of calculating the priority of the rules information in accordance with changes in the frequency of appearance of words and phrases in each of the different versions of the multiple rules information.
Specifically, in the present disclosure, the terms and conditions collection process is periodically executed. Therefore, when one term of use for a given product or service is revised, the terms and conditions collection unit 1051 of the server 10 collects terms and conditions for each different version of the one term of use, and stores the terms and conditions information and clause information for the term of use in the terms and conditions table 1015 and clause table 1031 of the server 10, respectively. At this time, the version and revision date of the one term of use are stored in the attribute information item of the terms and conditions table 1015, and each different version of the one term of use is stored in the terms and conditions table 1015 in association with the revision date of the term of use.
The terms and conditions collection unit 1051 of the server 10 analyzes the text data of the terms of use for each different version of the terms of use using morphological analysis or the like to identify information such as the content of words such as nouns, adjectives, etc. contained in the text data, and the types of words, and stores this information in a column (not shown) of the terms and conditions table 1015 in association with each version of the terms of use.

The terms and conditions collection unit 1051 of the server 10 analyzes and accumulates a large number of terms and conditions related to various products and services by version and revision date, and by analyzing changes in the frequency of appearance of words in different versions of a large number of terms and conditions, it is possible to analyze changes (trends) over time in words, legal terms, phrases, etc. that appear frequently in the terms of use.
For example, by comparing the text data of the most recent year's terms of use with the text data of older terms of use, it is possible to identify words, legal terms, phrases, etc. that have come to be used in recent revisions to the terms of use.

The terms and conditions collection unit 1051 of the server 10 calculates the priority of terms and conditions that include words, legal terms, phrases, etc. in the text data, which have been used in recent revisions to the terms and conditions, to be higher than the priority of terms and conditions that do not include words, legal terms, phrases, etc. in the text data.
For example, the terms and conditions collection unit 1051 of the server 10 may be configured to assign an importance to each of words, legal terms, phrases, etc., and calculate the priority of the terms and conditions by adding the importance according to the number of each word, legal term, phrase, etc. included in the text data of the terms and conditions. Note that the importance of words, legal terms, phrases, etc. may be calculated by comparing the frequency of appearance in the text data of the terms and conditions for the most recent year with the frequency of appearance in the text data of the terms and conditions for an older year, and by assigning a higher importance to words, legal terms, phrases, etc. that have changed more frequently in frequency of appearance.

In step S103, the terms and conditions editing unit 1042 of the server 10 executes a notification step of notifying the user of information indicating that a change has occurred in the frequency of appearance of the term in accordance with the change in the frequency of appearance of the term in different versions of the multiple terms and conditions information.
Specifically, when the terms and conditions collection unit 1051 of the server 10 finds a word, legal term, phrase, etc. with an importance level higher than a predetermined value during the attribute information identification process (third embodiment), it sends a message to users of the system 1 disclosed herein, such as the first user and the second user, indicating that a change has occurred in the frequency of appearance of the word, legal term, phrase, etc., in accordance with the change in frequency of appearance.
In addition, when the terms of use having a priority higher than a predetermined value is found during the attribute information identification process (third embodiment), the terms of use collection unit 1051 of the server 10 sends a message to users of the system 1 disclosed herein, such as the first user and the second user, including the terms of use or a link to a web page on which the terms of use are published.
This allows a user of the system 1 according to the present disclosure to grasp changes in the frequency of appearance of words and phrases from the collected multiple terms of use of different businesses, and to confirm changes and trends in wording, such as what phrases have recently become more commonly used.In addition, it is possible to confirm trends in terms of use, such as changes in wording and wording in the terms of use due to legal amendments, incidents, etc.
This enables users of the system 1 according to the present disclosure to create suitable terms of use that are in line with the latest legal changes and industry trends.

<Basic computer hardware configuration>
24 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.

The processor 901 is hardware for executing a set of instructions written in a program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, etc.

The main memory device 902 is used to temporarily store programs and data processed by the programs. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for saving data and programs. For example, it is a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, etc.

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 through a predetermined 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 directly connected by a USB (Universal Serial Bus) cable, etc.

The computer 90 can be realized virtually by distributing all or part of each hardware configuration across multiple computers 90 and connecting them together via a network. In this way, the concept of computer 90 includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

<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. 24) of the computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

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

The control unit is realized by the processor 901 reading various programs stored in the auxiliary storage device 903, expanding them in the main storage device 902, and executing processing 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.

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 for adding, updating, and deleting data stored in the storage unit in accordance with various programs.

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, it is possible to set relationships between tables and masters and associate them with each other.
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.

In addition, the databases and masters in this disclosure may include any data structure (such as a list, dictionary, associative array, or object) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by the communication IF 991. The communication unit realizes the 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.

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

(Appendix 1)
A terms management program for storing electronic terms of use in a computer having a processor and a memory unit, the processor executing a terms acquisition step (S501) of acquiring terms information relating to multiple terms of use for each product or service provided by a multiple business operator from multiple business servers operated by multiple different businesses, a terms storage step (S502) of associating each of the multiple terms of use information acquired in the terms acquisition step with specified attribute information and storing it in the memory unit, a search reception step (S103) of accepting search conditions including at least the attribute information from a user, a terms search step (S103) of searching for one or more specified terms of use information from the multiple terms of use information stored in the terms storage step based on the search conditions accepted in the search reception step, and a terms presentation step (S103) of presenting to the user at least a portion of the one or more specified terms of use information searched in the terms search step.
This allows the user to be presented with suitable terms of use according to the attribute information, based on various terms of use provided by various businesses.

(Appendix 2)
The rules storage step (S502) is a step of identifying specific attribute information by analyzing the website from which the multiple rules information acquired in the rules acquisition step was obtained, and associating the identified attribute information and storing it in a memory unit, in the rules management program described in Appendix 1.
This makes it possible to identify attribute information of the terms of use information by taking into consideration information on other web pages of the website on which the terms of use are posted, and thus makes it possible to identify attribute information of the terms of use more accurately.

(Appendix 3)
The rules storage step (S502) is a step of identifying specific attribute information by analyzing the content of web pages contained in the website from which the multiple rules information acquired in the rules acquisition step was obtained, and associating the identified attribute information and storing it in a memory unit, in the rules management program described in Appendix 2.
This makes it possible to identify the attribute information of the terms of use based on the document contents of the webpages included in other webpages of the website on which the terms of use are posted, and therefore makes it possible to identify the attribute information of the terms of use more accurately.

(Appendix 4)
The rules storage step (S502) is a step of identifying specific attribute information based on the domain name of the website from which the multiple rules information acquired in the rules acquisition step was obtained, and associating the identified attribute information and storing it in a memory unit, the rules management program described in Appendix 2.
This makes it possible to identify attribute information of the terms of use based on the domain of the website on which the terms of use are posted, and therefore makes it possible to identify attribute information of the terms of use more accurately.

(Appendix 5)
The rules storage step (S502) is a step of identifying specific attribute information by analyzing the rules text of each of the multiple rules information, and storing the identified attribute information in association with the specified attribute information in a memory unit, according to the rules management program described in Appendix 1.
This makes it possible to identify attribute information of the terms of use information based on the terms of use text, and therefore makes it possible to identify attribute information of the terms of use more accurately.

(Appendix 6)
The rules storage step (S502) is a step of identifying specific attribute information by analyzing the URL from which the multiple rules information acquired in the rules acquisition step was obtained, and associating the identified attribute information and storing it in a memory unit, in the rules management program described in Appendix 1.
This makes it possible to specify attribute information of the terms of use information based on the URL of the terms of use, and therefore makes it possible to specify attribute information of the terms of use more accurately.

(Appendix 7)
A regulation management program according to any one of appendices 1 to 6, wherein the regulation storage step (S502) is a step of associating each of the multiple regulation information with an operator attribute related to the operator that provided the regulation information and storing the associated information in the storage unit.
This allows the terms of use to be managed in association with the business attributes of the business that provides the terms of use, allowing the user to search for terms of use according to the business attributes.
For example, it is possible to search for suitable terms of use according to the user's business content, business scale, industry, etc.

(Appendix 8)
8. The rules management program according to claim 7, wherein the rules storage step (S502) is a step of storing in the storage unit a name of a provider of the rules information in association with each of the multiple rules information.
This allows the terms of use to be managed in association with the name of the business providing the terms of use, allowing the user to search for terms of use according to the name of the business providing the terms of use.

(Appendix 9)
The rules management program according to claim 7, wherein the rules storage step (S502) is a step of associating each of the multiple rules information with information on the industry or company size of the business entity that provided the rules information and storing the information in the storage unit.
This allows the terms of use to be managed in association with the business type and size of the business providing the terms of use, allowing users to search for terms of use according to the business type and size of the business.
For example, it is possible to search for suitable terms of use according to the user's business scale, industry, etc.

(Appendix 10)
A regulation management program described in any one of appendices 1 to 6, wherein the regulation storage step (S502) is a step of associating each of the multiple regulation information with product attribute information regarding the product or service to which the regulation information applies and storing the associated information in a memory unit.
This allows the terms of use to be managed in association with product attributes related to the product or service to which the terms of use apply, and allows users to search for terms of use according to product attributes.
For example, the user can search for suitable terms of use that correspond to the product or service that the terms of use that he or she plans to create or edit are intended to cover.

(Appendix 11)
11. The contract management program according to claim 10, wherein the contract storage step (S502) is a step of associating each of a plurality of contract information with the name of a product or service to which the contract information applies and storing the associated name in the storage unit.
This allows the terms of use to be managed in association with the name of the product or service to which the terms of use apply, allowing the user to search for terms of use according to the name of the product or service.
For example, the user can search for suitable terms of use that correspond to the product or service that the terms of use that he or she plans to create or edit are intended to cover.

(Appendix 12)
11. The policy management program according to claim 10, wherein the policy storage step (S502) is a step of associating each of a plurality of policy information with a category of a product or service to which the policy information applies, and storing the associated information in the storage unit.
This allows terms of use to be managed in association with the category of the product or service to which the terms of use apply, and allows users to search for terms of use according to the category of the product or service.
For example, the user can search for suitable terms of use that correspond to the product or service that the terms of use that he or she plans to create or edit are intended to cover.

(Appendix 13)
The rules storage step (S502) is a step of associating rules attribute information regarding one of the language, governing law, court of jurisdiction, source of law, number of characters in the terms of use, and whether or not specific technical terms are included with the multiple rules information acquired in the rules acquisition step and storing it in a memory unit, the rules management program described in Appendix 5.
This allows the terms of use to be managed in association with various terms attribute information regarding the terms of use, such as the language of the terms of use, the governing law, the jurisdiction, and the source of law (whether common law, civil law, etc.). Users can search for terms of use according to the terms attribute information.
For example, the user can search for suitable terms of use that correspond to the target language, country, and legal source of the terms of use that he or she plans to create or edit.

(Appendix 14)
A rules management program as described in Appendix 1, in which the rules storage step (S502) is a step of associating each of the multiple rules information with information regarding the company size of the business that provided the rules information and storing the information in a memory unit, and the rules presentation step (S103) is a step of presenting one or more rules information in order of the company size of the business that provided the rules information.
This makes it possible to manage the terms of use in association with the business size of the business operator providing the terms of use.
For example, the user can receive terms of use in the order of the size of the business. In general, the larger the business scale, the more reliable the terms of use is considered to be, so the user can receive terms of use in the order of the most reliable terms of use.

(Appendix 15)
11. The contract management program according to claim 10, wherein the search acceptance step (S103) is a step of accepting search conditions including product attribute information relating to a product or service.
This allows the user to search for suitable terms of use that correspond to the product or service that the terms of use that the user plans to create or edit are intended to cover.

(Appendix 16)
A rules management program as described in Appendix 1, in which a rules storage step (S502) is a step of storing each of the different versions of the rules information acquired in the rules acquisition step in association with the revision date of the rules information, and a rules presentation step (S103) is a step of presenting one or more rules information in order of the most recent revision date of the rules information.
This allows the user to receive the terms of use in the order of the most recently revised terms of use. Also, when there are multiple different versions of one term of use, the user can receive the terms of use related to the newest version.

(Appendix 17)
A rules management program as described in Appendix 16, in which a rules storage step (S502) is a step of storing each of the different versions of the rules information acquired in the rules acquisition step in association with the revision date of the rules information, and a notification step (S503) is executed by the processor to notify the user of information indicating that a change has occurred in the frequency of appearance of the word in accordance with the change in the frequency of appearance of the word in each of the different versions of the rules information.
This allows users to understand changes in the frequency of appearance of words and phrases from multiple terms of use collected from different businesses, as well as to see which phrases have recently become more commonly used, and to confirm changes and trends in wording.

(Appendix 18)
A rules management program as described in Appendix 1, wherein the rules storage step (S502) includes a step of storing, for each different version of the multiple rules information acquired in the rules acquisition step, the multiple rules information in association with the revision date of the multiple rules information, and a step of calculating a priority of the rules information in accordance with changes in the frequency of appearance of words in each different version of the multiple rules information, and the rules presentation step (S103) is a step of presenting one or more rules information in order of priority of the rules information.
This allows the user to receive terms of use from multiple terms of use collected from different businesses, in an order of priority based on changes in wording, such as the frequency of appearance of words, and trends.

(Appendix 19)
A terms and conditions management program as described in Appendix 1, in which a processor executes a terms and conditions editing step (S103) of displaying to a user a terms and conditions editing screen on which the user can edit the terms and conditions text, the terms and conditions editing step (S103) being a step of displaying the terms and conditions editing screen together with at least a portion of one or more pieces of terms and conditions information presented in the terms and conditions presentation step.
This allows the user to edit the text of their own terms of use while checking the search results of the terms of use of other businesses, allowing the user to efficiently create and edit the text of their terms of use.

(Appendix 20)
The terms and conditions presentation step (S103) is a step of generating a standard draft of terms and conditions based on one or more terms and conditions information searched for in the terms and conditions search step, and presenting the draft to the user.
This allows the user to receive a proposal of a suitable set of terms of use based on the terms of use of other businesses.
For example, it is possible to receive proposals for standard terms of use that correspond to the terms of use of other businesses, which can streamline the work of creating terms of use.

(Appendix 21)
A regulation management program as described in Appendix 20, wherein the search acceptance step (S103) is a step of accepting search conditions including user attribute information relating to a user, and the regulation search step (S103) is a step of searching for one or more pieces of specified regulation information associated with attribute information equivalent to or similar to the user attribute information.
This allows the user to receive a proposal for a suitable set of terms of use based on the user's own attribute information and user attribute information such as the business content, business scale, industry, etc. of the company or organization to which the user belongs.
For example, the user can receive proposals for standard terms of use used by other companies that are similar to the business content, business scale, industry, etc., of the company to which the user belongs. This can improve the efficiency of the work of creating terms of use.

(Appendix 22)
An information processing device comprising a processor and a memory unit, wherein the processor executes a regulation management program according to any one of appendices 1 to 6, 13 to 14, and 16 to 21.
This allows the user to be presented with suitable terms of use according to the attribute information, based on various terms of use provided by various businesses.

(Appendix 23)
A manufacturing method for an information processing system including an information processing device having a processor and a memory unit, wherein the processor executes a regulation management program described in any one of appendices 1 to 6, 13 to 14, and 16 to 21.
This allows the user to be presented with suitable terms of use according to the attribute information, based on various terms of use provided by various businesses.

(Appendix 24)
An information processing method executed by a computer having a processor and a memory unit, the computer executing a regulation management program according to any one of appendices 1 to 6, 13 to 14, and 16 to 21.
This allows the user to be presented with suitable terms of use according to the attribute information, based on various terms of use provided by various businesses.

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 (24)

A terms of use management program for storing electronic terms of use in a computer having a processor and a storage unit,
The processor,
A terms acquisition step of acquiring, from a plurality of business server operated by a plurality of different business operators, terms information regarding a plurality of terms of use for each product or service provided by each of the business operators;
a rules storage step of associating predetermined attribute information with each of the plurality of rules information acquired in the rules acquisition step and storing the information in the storage unit;
a search receiving step of receiving search conditions including at least attribute information from a user;
a rules search step of searching for a predetermined one or a plurality of pieces of rules information from the plurality of rules information stored in the rules storage step based on the search conditions received in the search reception step;
a rules presentation step of presenting to the user at least a part of the one or more pieces of predetermined rules information searched in the rules search step;
Execute
Terms and conditions management program. the regulation storage step is a step of identifying the predetermined attribute information by analyzing a website from which the plurality of regulation information pieces acquired in the regulation acquisition step were acquired, and storing the identified attribute information in the storage unit in association with the predetermined attribute information;
The policy management program according to claim 1. the regulation storage step is a step of identifying the predetermined attribute information by analyzing the contents of a web page included in a website from which the plurality of regulation information pieces acquired in the regulation acquisition step are acquired, and storing the identified attribute information in the storage unit in association with the predetermined attribute information;
3. The policy management program according to claim 2. the regulation storage step is a step of identifying the predetermined attribute information based on a domain name of a website from which the plurality of regulation information pieces acquired in the regulation acquisition step are obtained, and storing the identified attribute information in the storage unit in association with the predetermined attribute information;
3. The policy management program according to claim 2. The rule storage step is a step of identifying the predetermined attribute information by analyzing a rule sentence of each of the plurality of rule information, and storing the identified attribute information in the storage unit in association with the predetermined attribute information.
The policy management program according to claim 1. The rules storage step is a step of identifying the predetermined attribute information by analyzing URLs of the sources of the plurality of rules information acquired in the rules acquisition step, and storing the identified attribute information in the storage unit in association with the predetermined attribute information.
The policy management program according to claim 1. The rule storage step is a step of storing, in the storage unit, a business attribute related to a business that provides each of the plurality of rule information items in association with the corresponding rule information item.
7. The policy management program according to claim 1. The rule storage step is a step of storing, in the storage unit, a name of a provider of the rule information in association with each of the plurality of rule information.
The policy management program according to claim 7. The rule storage step is a step of storing information on the industry or the business size of a business entity that provides each of the plurality of rule information items in association with the corresponding rule information item in the storage unit.
The policy management program according to claim 7. The regulation storage step is a step of storing, in the storage unit, product attribute information relating to a product or service to which each of the plurality of regulation information is applied in association with the product attribute information.
7. The policy management program according to claim 1. The rule storage step is a step of storing, in the storage unit, a name of a product or service to which each of the plurality of rule information is applied in association with the name of the product or service to which the rule information is applied.
The policy management program according to claim 10. The rule storage step is a step of storing, in the storage unit, each of the plurality of rule information items in association with a category of a product or service to which the rule information applies.
The policy management program according to claim 10. The rules storage step is a step of storing, in the storage unit, rules attribute information relating to any one of a language, a governing law, a court of jurisdiction, a source of law, a number of characters in the terms of use, and whether or not a specific technical term is included, of the plurality of rules information acquired in the rules acquisition step in association with each other.
6. The policy management program according to claim 5. the rules storage step is a step of storing information on the scale of a company that provides each of the plurality of rules information in the storage unit in association with the information,
The rule presentation step is a step of presenting the one or more pieces of rule information in order of the company size of the business entity that provides the rule information.
The policy management program according to claim 1. The search receiving step is a step of receiving search conditions including product attribute information related to a product or service.
The policy management program according to claim 10. The rule storage step is a step of storing each of the different versions of the plurality of rule information acquired in the rule acquisition step in association with a revision date of the rule information.
The rule presentation step is a step of presenting the one or more pieces of rule information in order of the most recent revision date of the rule information.
The policy management program according to claim 1. the regulation storage step is a step of storing, for each different version of the plurality of regulation information acquired in the regulation acquisition step, the regulation information in association with a revision date of the corresponding regulation information;
The processor,
a notification step of notifying the user of information indicating that a change has occurred in the appearance frequency of a phrase in accordance with a change in the appearance frequency of the phrase in each of the multiple versions of the agreement information;
Execute
17. The policy management program according to claim 16. The rule storage step includes:
storing the different versions of the plurality of pieces of agreement information acquired in the agreement acquisition step in association with a revision date of the pieces of agreement information;
calculating a priority of the plurality of pieces of the rules information according to a change in the frequency of appearance of a word or phrase in each of different versions of the plurality of pieces of the rules information;
Including,
The rule presentation step is a step of presenting the one or more pieces of rule information in the order of priority of the rule information.
The policy management program according to claim 1. The processor,
a terms of use editing step of displaying a terms of use editing screen for editing a terms of use text for the user;
Run
The rules editing step is a step of displaying the rules editing screen together with at least a part of the one or more pieces of rules information presented in the rules presentation step.
The policy management program according to claim 1. The terms and conditions presentation step is a step of generating a standard one-term terms and conditions proposal based on the one or more terms and conditions information searched in the terms and conditions search step, and presenting the standard one-term terms and conditions proposal to the user.
The policy management program according to claim 1. The search receiving step is a step of receiving search conditions including user attribute information related to the user,
The rule search step is a step of searching for the one or more pieces of predetermined rule information associated with attribute information equivalent to or similar to the user attribute information.
21. The policy management program according to claim 20. An information processing device including a processor and a storage unit,
The processor executes a regulation management program according to any one of claims 1 to 6, 13 to 14, and 16 to 21.
Information processing device. A method for manufacturing an information processing system including an information processing device having a processor and a storage unit,
The processor executes a regulation management program according to any one of claims 1 to 6, 13 to 14, and 16 to 21.
A method for manufacturing an information processing system. An information processing method executed by a computer including a processor and a storage unit,
The computer executes a regulation management program according to any one of claims 1 to 6, 13 to 14, and 16 to 21.
Information processing methods.