Information processing device, method, program

Abstract

This will make it even easier for individuals to understand the matters they have agreed to. [Solution] The storage unit is configured to store user account information for the first service. It receives at least one of the following: information indicating that the user of the second service has agreed to the terms of use for using the second service, which is different from the first service, or information output by a service that manages contracts, indicating that the user has agreed to the contract terms related to the contract. The received information is stored in the storage unit in association with the account information of the first service user who agreed to the received information, and a list of information associated with the account information of the first service user, which indicates that the user has agreed to the terms of use, or information indicating that the user has agreed to the contract terms related to the contract, is output.

Description

Technical Field

[0001] This disclosure relates to an information processing apparatus, method, and program.

Background Art

[0002] Various services have been provided, and users start or stop using the services.

[0003] When using a service, it is common to request users to agree to the terms of use. Patent Document 1 describes a technique "aimed at providing a mechanism for making the terms of use easier to read even when registering a user on a mobile terminal such as a smartphone." Patent Document 1 describes "receiving registration of user information from a user", "display-controlling the terms of use in response to receiving the registration of user information", "receiving a mail address to which the terms of use are to be sent from the user", "receiving an instruction to send the terms of use to the received mail address", "when the instruction is received", "sending the terms of use to the received mail address", and "display-controlling a user information registration screen with the received mail address pre-entered."

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] These services include those that require payment, and users need to terminate the use of services they are not currently using. Furthermore, individuals enter into various contracts in their daily lives, such as lease agreements, insurance contracts related to lease agreements, and contracts with telecommunications providers, but it is difficult to keep track of all the contracts they have entered into. Therefore, it is difficult for users to grasp the overall picture of the rights and obligations stipulated by terms of service and contracts. Consequently, there is a need for technology that makes it easier for service users to understand the matters they have agreed to.

[0006] The purpose of this disclosure is to provide technology that makes it easier for individuals to understand the matters they have consented to. [Means for solving the problem]

[0007] To solve the above problems, a program is provided for operating a computer having one or more computer processors. The memory unit is configured to store user account information for a first service. The program causes one or more computer processors to perform the following steps: receive at least one of the following: information indicating that a user of a second service has agreed to the terms of use for using a second service different from the first service, or information output by a service that manages contracts indicating that a user has agreed to the terms and conditions of the contract; store the information received in the receiving step in the memory unit in association with the account information of the first service user who agreed to the received information; and output a list of information associated with the account information of the first service user, which includes at least one of the following: information indicating that the terms of use have been agreed to, or information indicating that the terms and conditions of the contract have been agreed to. [Effects of the Invention]

[0008] This disclosure makes it even easier for individuals to understand the matters they have consented to. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows the configuration of System 1. [Figure 2] Figure 2 shows the configuration of server 20. [Figure 3] Figure 3 shows the configuration of terminal 10. [Figure 4] Figure 4 shows the data structure of the user database 211. [Figure 5] Figure 5 shows the data structure of the account linking database 212. [Figure 6] Figure 6 shows the data structure of the approval request database 213. [Figure 7] Figure 7 shows the data structure of the review history database 214. [Figure 8] Figure 8 shows the data structure of the contract management database 215. [Figure 9] Figure 9 shows the data structure of the document management database 216. [Figure 10] Figure 10 shows the process flow for a general-purpose service with an integrated account, where the user calls other services while simultaneously agreeing to the terms of service for those other services. [Figure 11] Figure 11 shows the process flow in a general-purpose service with an integrated account, where a contract signing service is called and the user's agreement to the contract terms is accepted by that service. [Figure 12] Figure 12 shows the process flow for accepting a user's agreement to the terms of service in a specific service and linking it with the user ID of a general-purpose service. [Figure 13]FIG. 13 is a diagram showing the flow of a process that accepts an operation in which a user agrees to contract terms in a contract conclusion / document management service and associates it with the ID of a user of a general-purpose service. [Figure 14] FIG. 14 is a diagram showing the flow of a process that notifies a user's account of a general-purpose service that the service provider has changed the terms of use. [Figure 15] FIG. 15 is an example screen of an operation screen that accepts consent to the terms of use and consent to the contract terms while transitioning to a specific service in a service having an integrated account. [Figure 16] FIG. 16 is an example screen of an operation screen that accepts consent to the terms of use and consent to the contract terms in a service having an integrated account.. [Figure 17] FIG. 17 is an example screen when the service provider notifies the operation screen of a service having an integrated account that the terms of use have been updated.

Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, common components are denoted by the same reference numerals, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure. Also, each figure is a schematic diagram and is not necessarily drawn precisely.

[0011] Also, in the following description, a "processor" is one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

[0012] Also, at least one processor may be a processor in a broad sense, such as a hardware circuit (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0013] Also, in the following description, the expression such as "xxx table" may be used to describe information from which an output is obtained for an input. However, this information may be data with any structure or a learning model such as a neural network that generates an output for an input. Therefore, "xxx table" can be referred to as "xxx information".

[0014] Also, in the following description, the configuration of each table is an example. One table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0015] Also, in the following description, the "program" may be used as the subject to describe the processing. However, since the program is executed by the processor to perform the defined processing while appropriately using the storage unit and / or the interface unit, etc., the subject of the processing may be the processor (or a device such as a controller having the processor).

[0016] The program may be installed in a device such as a computer, or may be in, for example, a program distribution server or a computer-readable (e.g., non-temporary) recording medium. Also, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0017] Also, in the following description, an identification number is used as identification information for various objects, but identification information of other types (e.g., an identifier including letters and symbols) may be adopted.

[0018] Furthermore, in the following explanations, when describing similar elements without distinction, a reference code (or a common code among reference codes) may be used, and when describing similar elements with distinction, the element's identification number (or reference code) may be used.

[0019] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.

[0020] <Outline of the Embodiment> The following embodiment describes a technology that allows service users to easily understand their agreement status to contracts and terms of service for the services they use.

[0021] Furthermore, the following embodiments describe a technology that enables service providers (businesses, etc.) to easily notify service users of updates to the terms of service. This provides service users with an opportunity to decide whether or not to continue using the service after receiving notification of changes to the terms of service. This makes it easier for service users to understand their usage status of the services they are using.

[0022] Specifically, the system manages contracts and terms of service that users have agreed to (e.g., lease agreements and subscription services) in association with the identification information assigned to the user. Based on the assigned identification information, users can view, for example, a list of the contracts and terms of service they have agreed to. Here, the identification information assigned to a user may include the user's account information in a general-purpose service that is linked to various other services (hereinafter sometimes referred to as "general-purpose service"). Examples of general-purpose services may include the following: • A messaging service that provides the functionality for users to send and receive messages. • Payment application that provides payment functionality • A Social Network Service (SNS) that facilitates interaction among users, including unspecified individuals. • Ride-hailing application • Business tools that provide features such as email, video calls, and online storage. • Personal identification numbers issued by government agencies (e.g., My Number) • Air services Some of the applications mentioned above display icons or other prompts to call other services, allowing those services to be executed. In the following explanation, services that are provided but differ from general-purpose services may be referred to as "specific services." Specific services include those that interact with general-purpose services to send and receive data. For example, data can be sent and received between general-purpose services and specific services using the API (Application Programming Interface) provided by the general-purpose service.

[0023] Furthermore, the following may be the contracts to be managed in the following embodiments: • Electronic contract service. A service that manages concluded contracts by allowing users to affix electronic signatures when they agree to the terms and conditions stipulated in the contract. • Document management service that scans or reads paper contracts to manage contract periods and other details. <First Embodiment> <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.

[0024] System 1, shown in Figure 1, includes a server 20 that provides contract signing and document management services, a user terminal 10, a terminal 10B for the operator of a specific service, a server 92 that provides business support system services, a server 93 that provides document review services, a server 95 that provides artificial intelligence (large-scale language model) services, a server 96 that provides specific services, and a server 99 that provides general-purpose services. These devices are connected to each other via a network 80.

[0025] In the illustrated example, terminal 10 is shown as the terminal used by users of the contract signing and document management service provided by server 20, but each user operates their own terminal.

[0026] Server 20 is a device that provides services for concluding contracts electronically and for managing document data concluded electronically. It should be noted that in System 1, the contract conclusion service provided by Server 20 and the document data management service may be provided by separate devices or different service providers. For example, Server 20 provides a document management service and, in addition to electronically signed contract data, may also optically scan paper contracts with seals to extract information such as the contract period and whether the contract is automatically renewed, and manage this information along with the scanned contract data. This allows for notifications to be sent to the user when the contract period expires.

[0027] Server 20 may also be a server that provides services to support tasks such as submitting approval requests to organizations (business companies, etc.) that conduct business activities. For example, Server 20 provides a service to users that enables them to design a workflow for obtaining budget approval with multiple users.

[0028] Terminal 10 is a device operated by the user.

[0029] The business support system service server 92 provides users with tools that can be used for the organization's business operations. The business support system service server 92 provides users with a system for submitting approval requests as part of the organization's business operations. The business support system service server 92 may also communicate with server 20 to provide server 20 with data accumulated by the approval request service.

[0030] The document review service server 93 accepts document data such as contracts and term sheets that define contract terms, and provides users with information on whether each clause is advantageous or disadvantageous to the company, whether there are any missing clauses, and the importance of the review items, thereby supporting the review of the document data. The document review service server 93 provides the above review support service using rule-based or pre-trained models. As a rule-based approach, for example, it may be possible to perform rule-based reviews of document data by associating specific wording or expressions with pre-defined information on whether the conditions are advantageous or disadvantageous, and explanations. Alternatively, for example, it may be possible to provide the above review service by generating a pre-trained model that responds with review results to document data input, using data from expert reviews of contracts, term sheets, etc., as training data. Furthermore, the document review service server 93 can also summarize the contents of contracts and generate review comments using a large-scale language model, and provide the results to the user. For example, the document review service server 93 may prompt the large-scale language model service server 95 with the document data to be reviewed (such as contract data) and information indicating the review criteria, and instruct the server 95 to perform the review according to the review criteria. By receiving the output of the large-scale language model service server 95, the server 93 may generate review comments for the document data. The document review service server 93 may also communicate with server 20 to provide the server 20 with data accumulated by the document review service.

[0031] Server 95 of the Large-Scale Language Model Service is a server that executes language processing tasks using language models built through learning processes including artificial intelligence (AI). An LLM (Large Language Model) is a model that has been pre-trained on large amounts of data (such as text data), for example, a large amount of web content on the internet, or a large amount of data stored in a designated database, and can perform various language processing tasks by being given a task.

[0032] The AI ​​service server 95 (sometimes referred to as the "large-scale language model service server 95") accepts prompt input in the form of text, images, audio, etc., and generates and responds with answers to those prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0033] Server 96 for a specific service is a device for providing a specific service. Server 99 for a general-purpose service is a device for providing a general-purpose service. In the illustrated example, terminal 10B is shown as an example of a terminal operated by a user of a service provider operating a specific service.

[0034] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, the collection of each device can be considered as a single "information processing device," and System 1 may be formed as a collection of multiple devices. The way in which the multiple functions required to realize System 1 according to this embodiment are distributed to one or more hardware can be appropriately determined in view of the processing capacity of each hardware and / or the specifications required for System 1.

[0035] Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PCs (Personal Computers), Laptop PCs • Wearable devices worn by the user (watch-type, glasses-type, etc.) Terminal 10 includes a communication interface (IF) 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19.

[0036] The communication interface 12 is an interface for inputting and outputting signals so that terminal 10 can communicate with an external device.

[0037] The input device 13 is a device for receiving input operations from the user (for example, a touch panel, touchpad, pointing device such as a mouse, keyboard, etc.).

[0038] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0039] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0040] Storage 16 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0041] The processor 19 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0042] The server 20 includes a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29.

[0043] Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0044] Input / Output IF23 functions as an interface between an input device for receiving user input operations and an output device for presenting information to the user.

[0045] Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0046] Storage 26 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0047] The processor 29 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0048] <1.2 Functional Configuration of Server 20> Figure 2 shows the configuration of server 20. As shown in Figure 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0049] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

[0050] The memory unit 202 stores various databases, such as the user database 211, account linkage database 212, approval request database 213, review history database 214, contract management database 215, and document management database 216.

[0051] User database 211 is a database for managing users.

[0052] User database 211 contains information necessary for using the services provided by server 20, such as the user's name and employee number. Further details will be provided later.

[0053] The account linking database 212 is a database for managing the account linking status between services, as well as the agreement status of the terms of service for linked services and the status of contracts managed by the contract conclusion and document management service (server 20). Details will be described later. Although the account linking database 212 is described as being held on server 20, it may also be a database managed on server 99 of the general-purpose service, and server 20 may also hold the account linking database 212 by communicating with server 99 of the general-purpose service.

[0054] The approval request database 213 is a database that manages applications for approval, such as those for concluding contracts. For example, server 20 communicates with server 92 of the business support system service to obtain information related to the approval request and update the approval request database 213. Further details will be described later.

[0055] Review History Database 214 is a database that manages the history of reviews performed on document data such as contracts. Further details will be provided later.

[0056] The contract signing management database 215 is a database that manages the contract signing process carried out by the electronic contract service provided by server 20. Further details will be described later.

[0057] The document management database 216 is a database for managing document data and includes information for managing document data concluded through the electronic contract service provided by server 20. Further details will be described later.

[0058] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs the functions shown as the reception control module 2041, transmission control module 2042, user management module 2043, contract signing processing module 2044, document management module 2045, approval processing module 2046, LLM utilization module 2047, review processing module 2048, and cooperation processing module 2049.

[0059] The receive control module 2041 controls the process by which the server 20 receives signals from external devices according to a communication protocol.

[0060] The transmission control module 2042 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.

[0061] The user management module 2043 is a module for managing information for each user using System 1. Specifically, the user management module 2043 accepts registration of each user's information and updates the user database 211.

[0062] The contract signing module 2044 controls the process of parties approving document data as part of the process of concluding a contract electronically. Specifically, the contract signing module 2044 notifies each user approving the document data and updates the contract signing management database 215 in response to the operation of approving the document data.

[0063] The document management module 2045 controls the process of managing document data by referring to the document management database 216. Specifically, based on the contract period information set in the document data, the document management module 2045 notifies the user of whether to renew the contract upon the expiration of the contract period, and updates the document management database 216 in response to user actions (such as renewing the contract).

[0064] The approval processing module 2046 receives an operation from a user to submit an approval request and controls the process by which approvers approve the request. Specifically, the approval processing module 2046 notifies each user who approves the request and updates the approval request database 213 in response to the operation to approve the request.

[0065] The LLM utilization module 2047 is a program module that performs processing related to the use of LLM, such as generating prompts to send to the server 95 of the large-scale language model service, sending the generated prompts as instructions to the server 95 of the large-scale language model service, receiving the results output by the server 95 of the large-scale language model service in response to the instructions (prompts), and performing processing using the received results.

[0066] The review processing module 2048 records reviews of the document data to be reviewed (for example, each clause of a contract) and updates the review history database 214. The review processing module 2048 communicates with the document review service server 93 and sends the document data to be reviewed, causing the server 93 to perform the review process. The module receives the results and updates the review history database 214. The review processing module 2048 also accepts operations from the user performing the review (for example, operations to input comments in association with the entire contract or each clause of the contract) and updates the review history database 214.

[0067] The integration processing module 2049 is a program module that performs processes such as linking user accounts between services and sharing data between the linked services, such as the terms of service for each service and contracts managed by the contract signing and document management service. In the following example, the functions of the integration processing module 2049 are explained assuming that the general-purpose service server 99 performs them, but the processes such as linking accounts between services may be executed by each device such as the server 96 and server 20 of a specific service, or these devices may cooperate in sending and receiving user data managed by each service in conjunction with the linking of user accounts.

[0068] <1.3 Configuration of Terminal 10> Figure 3 shows the configuration of terminal 10.

[0069] As shown in Figure 3, terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units corresponding to each antenna (first communication unit 120, second communication unit 121), an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. Terminal 10 also has functions and configurations not specifically shown in Figure 3 (for example, a battery for maintaining power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in terminal 10 is electrically connected by a bus or the like.

[0070] Antenna 111 radiates signals emitted by terminal 10 as radio waves. Antenna 111 also receives radio waves from space and provides the received signals to first communication unit 120.

[0071] Antenna 112 radiates signals emitted by terminal 10 as radio waves. Antenna 112 also receives radio waves from space and provides the received signals to the second communication unit 121.

[0072] The first communication unit 120 performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 111 in order to communicate with other wireless devices. The second communication unit 121 also performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 112 in order to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are a communication module that includes a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first communication unit 120 and the second communication unit 121 perform modulation and demodulation, frequency conversion, etc., of the wireless signals transmitted and received by the terminal 10, and provide the received signal to the control unit 190.

[0073] The input device 130 has a mechanism for receiving user input operations. Specifically, the input device 130 is configured as a touchscreen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives user input operations of the terminal 10. The touch-sensitive device 131 detects the user's contact position with the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's contact position detected by the touch panel to the control unit 190 as an input operation.

[0074] The display 132 displays data such as images, videos, and text in accordance with the control of the control unit 190. The display 132 is implemented by, for example, an LCD or an organic EL display.

[0075] The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal received from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is implemented, for example, by an audio processing processor. The microphone 141 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 140. The speaker 142 converts the audio signal received from the audio processing unit 140 into sound and outputs the sound to the outside of the terminal 10.

[0076] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal 10, which is equipped with a GPS module, is detected based on the received signals.

[0077] Camera 160 is a device that receives light using a photodetector and outputs it as an image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the object being photographed.

[0078] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10.

[0079] The storage unit 180 is composed of, for example, flash memory and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0080] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the memory unit 180 and executing the instructions contained in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 performs the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a memory control unit 195.

[0081] The operation reception unit 191 processes input operations from the user to an input device such as a touch-sensitive device 131. Based on the coordinate information of the touch-sensitive device 131 where the user's finger or the like has made contact, the operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation.

[0082] The transmitting / receiving unit 192 performs processing to enable the terminal 10 to send and receive data with an external device such as a server 20 in accordance with a communication protocol.

[0083] The data processing unit 193 performs calculations on the data received as input by the terminal 10 according to the program and outputs the calculation results to memory or other locations.

[0084] The notification control unit 194 performs the following processes: displaying the display image on the display 132, outputting sound to the speaker 142, and generating vibrations.

[0085] The memory control unit 195 controls the storage of data to the memory unit 180.

[0086] The various types of information stored by the memory unit 180 will now be explained. In a given situation, the memory unit 180 stores various types of information, such as user information 181.

[0087] User information 181 is information about a user who uses the services of server 20. User information 181 includes, for example, the user's employee number, name, and other information.

[0088] <2 Data Structure> Figure 4 shows the data structure of the user database 211. The user database 211 includes the fields "User ID", "Business ID", "Name", "Email Address", "Department", "Position", "Date of Employment", "Date of Resignation", and "Qualifications Held".

[0089] The "User ID" field is information that identifies each user.

[0090] The "Business ID" field contains information that identifies each business.

[0091] The "Name" field contains the user's name information.

[0092] The "Email Address" field is information that identifies the user and serves as their contact information.

[0093] The "Department" field contains information about the user's department.

[0094] Specifically, the "Department" field may include the following information about the department to which the user belongs: • Departments that do not primarily handle legal affairs, such as business divisions and sales divisions. • Departments that primarily handle legal affairs, such as legal affairs departments and intellectual property departments. The "Job Title" field contains information about the user's job title.

[0095] The "Date of Joining" field contains information about the date the user joined the organization.

[0096] The "Resignation Date" field contains information about the date the user left the organization.

[0097] The "Qualifications Held" item contains information about the qualifications the user holds.

[0098] Specifically, the item "Qualifications Held" includes the following information regarding the qualifications held by the user. • Qualifications that are expected to demonstrate expertise in reviewing contracts, similar to that of a lawyer. • Qualifications that demonstrate knowledge of business activities, such as a Certified Management Consultant for Small and Medium Enterprises. • Qualifications such as Certified Public Accountant and Tax Accountant, which indicate that the individual possesses the necessary knowledge in accounting, taxation, and related fields. Figure 5 shows the data structure of the account linking database 212.

[0099] The item "Integrated User ID" is information that identifies a user in a general-purpose service that has an integrated ID.

[0100] In the illustrated example, the item "Integrated User ID" shows a messaging service as an example of a service with an integrated ID, as indicated in the item "Service Usage Data Log". Here, a general-purpose service with an integrated ID is one that provides the functionality to connect with other services, starting from that general-purpose service.

[0101] Examples of general-purpose services include the following: • Messaging service (a function for sending and receiving messages between users). Within the messaging service, various services are provided, including point management, securities services, and payment functions. • Payment applications. Some payment applications offer features such as payment processing while also providing services like item rentals. • SNS (Social Network Service). Some SNS may offer various services, such as gift sending services and services that send points with monetary value. • Ride-hailing services. These services may include services that arrange passenger cars, provide food delivery functions, and also offer functions such as restaurant reservations. • Business communication tools. For example, services that provide various functions to advance business activities, such as email, video calls, and document tools. • A personal identification number issued by an administrative agency after verifying the individual's identity. This number may be used to provide functions such as checking a patient's prescription history. • Air services. Some companies may provide air travel services along with ancillary services such as travel insurance and transportation reservations. The item "Verified Identification Information" refers to the type of information issued after identity verification.

[0102] In the illustrated example, the item "Verified Identification Information" shows an example of information issued after identity verification, specifically a telephone number, and the example shows the storage of the telephone number itself. Other examples of information issued after identity verification that identifies an individual include personal identification numbers (e.g., "My Number") assigned to citizens by administrative agencies.

[0103] The item "Service Usage Data Log" refers to information about the types and content of data accumulated in response to user actions in general-purpose services.

[0104] In the illustrated example, the item "Service Usage Data Log" shows a messaging service as a general-purpose service, illustrating an example where logs of messages sent and received by the messaging service are stored in the "Service Usage Data Log" item.

[0105] The item "Identification information for linked services" is information that identifies a specific service that links with a general-purpose service.

[0106] The item "User ID for linked service" is information that identifies a user in a specific service that is linked with a general-purpose service.

[0107] The item "Timing of Integration of Linked Services" contains information about the timing of integration between a general-purpose service and a specific service.

[0108] More specifically, the item "Timing of Linked Services" refers to information such as the timing when a specific service is called from a general-purpose service, and the timing when a user agrees to the terms of service of a specific service after calling it from a general-purpose service. Linking between a general-purpose service and a specific service means, for example, that in a database such as the account linking database 212, the user identification information of the general-purpose service (item "Integrated User ID") and the user identification information of the specific service are associated and stored in the database (account linking database 212).

[0109] The item "Agreement Status to Terms of Service for Linked Services" provides information on whether the user has agreed to the terms of service for specific services that link with the general service.

[0110] More specifically, the item "Agreement Status to Terms of Use for Linked Services" stores information on the version of the terms of use for specific services that link with the general service that has been agreed to.

[0111] In the item "Consent Status to Terms of Service for Linked Services," it is also possible to retain information such as which version of the terms of service the user has agreed to, and the timing of the user's action to agree to the terms of service for each version of the terms of service.

[0112] The item "Contract Management Service Identification Information" is information of at least one type of service that works in conjunction with general-purpose services, either a contract signing service or a document management service that manages documents for which contracts have been signed.

[0113] The item "Identification information for contract management services" may include the following as a contract signing service or a document management service that manages contracted documents and works in conjunction with general-purpose services: • A service for electronically concluding contracts. Specifically, for document data subject to approval (such as contracts), the user performing the approval operation affixes an electronic signature, and the electronically signed document data is managed. This service accepts scans of paper contracts that were concluded by affixing a seal, and also accepts registration of information for managing the contract (such as the date of conclusion, renewal date, and information of the parties involved). The item "Management Data for Contract Management Services" contains information about contracts approved by the user, which is associated with the user ID of the general-purpose service (item "Integrated User ID").

[0114] In the illustrated example, the item "Management data for contract management services" includes information that identifies the flow of electronic contracts provided by the contract signing service (server 20) (signing management database 215), information on links for referencing signed contracts (document management database 216), and so on.

[0115] The item "Timing of Integration with Contract Management Service" refers to the timing at which the user ID of the general-purpose service is associated with information such as contracts managed by the contract management service.

[0116] Figure 6 shows the data structure of the approval request database 213. The approval request database 213 includes the fields "Approval Request ID", "Applicant ID", "Approver ID", "Application Date", "Approval Date", "Application Details", and "Contract ID".

[0117] The item "Approval Request ID" is information that identifies each approval request.

[0118] The "Applicant ID" field is information that identifies the user who submitted the approval request.

[0119] Specifically, the item "Applicant ID" may be associated with user information (User ID) managed in the user database 211.

[0120] The "Approver ID" field is information that identifies the user who is the approver of the proposal.

[0121] Specifically, the item "Approver ID" may be associated with user information (User ID) managed in the user database 211.

[0122] The "Application Date" field contains information about the date and time when the system received the operation from the user who will be submitting the approval request data, in order to request approval of the approval request data from each user.

[0123] The "Approval Date" field contains information about the date and time when the user approved the data in the approval request.

[0124] The item "Application Details" contains information that shows the content of the approval request.

[0125] Specifically, the item "Application Details" includes the following types of approval requests. • Conclusion of a contract • Approval of the budget (including approval of the business plan) • Expense claim The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0126] Specifically, the item "Contract Signing ID" may be associated with information (Contract Signing ID) that identifies each contract signing procedure, which is managed in the contract signing management database 215. This links the approval application data in the approval application database 213 with the contract signing data in the contract signing management database 215.

[0127] Figure 7 shows the data structure of the review history database 214. The review history database 214 includes the following items: "Review ID", "Document Data", "Document Management ID", "Review Date and Time", "Reviewing User", "Review Content", and "Review Requester's Rating".

[0128] The "Review ID" field is information that identifies each review performed on the document data.

[0129] The item "Document Data" contains information about the document data that will be reviewed.

[0130] The "Document Management ID" field is information that identifies each document data being managed.

[0131] Specifically, the item "Document Management ID" may be associated with information (Document Management ID) that identifies each document data managed in the document management database 216.

[0132] The "Review Date and Time" field contains information about the date and time the review was performed.

[0133] The item "Reviewing User" contains information about the user who conducted the review.

[0134] The item "Review Content" contains information that shows the results of the review.

[0135] Specifically, the item "Review Content" may include the following as a result of the review: • Results of the review by server 93 of the document review service (e.g., advantages / disadvantages of conditions, importance, proposed revisions) • Comments and suggested revisions entered by users (including information about the user who entered the review comment) The item "Review Requester's Rating" is information that shows the user's rating of the reviewer's review content.

[0136] Specifically, the item "Review Requester's Rating" includes the results of the user who requested the review evaluating the reviewer based on the actions they took with respect to the review results, and may include the following: • The user who requested the review sets a score for the review results. • The number of "likes" and other reactions on posts made to contact users about reviewing a product via messaging tools, etc. Figure 8 shows the data structure of the contract management database 215. The contract management database 215 includes the following fields: "Contract ID", "Sender ID", "Recipient ID", "Contract Target Data", "First Email Address", "Second Email Address", "Sending Date and Time", "User Signature Date and Time", "Contract Completion Date and Time", and "Status".

[0137] The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0138] Specifically, the item "Contract ID" includes identification information issued by server 20 when a new registration is accepted for the process of concluding an electronic contract by specifying an approver for document data that is subject to approval by the parties.

[0139] The "Sender ID" field is information that identifies the party who will be sending the document data when the party approves it.

[0140] Specifically, the item "Sender ID" may be associated with information about a business operator (Business ID) or information about a user (User ID) managed in the user database 211.

[0141] The "Recipient ID" field is information that identifies the recipient when they approve document data.

[0142] Specifically, the item "Recipient ID" is information that identifies the party designated as the recipient by the sender's user, and like the sender ID, it may be associated with information about a business operator (business operator ID) or information about a user (user ID) managed in the user database 211.

[0143] The item "Data Subject to Agreement" refers to the document data that the parties are required to approve.

[0144] Specifically, the item "Data subject to conclusion" refers to data (files such as PDFs) of transaction documents such as contracts, application forms, and quotations.

[0145] The item "First Email Address" is information that identifies the user who will be the sender in the process of concluding a contract by approving document data, and is the email address that serves as the contact address for that user.

[0146] Specifically, the item "First Email Address" is the email address of the user who performs the operation of sending the document data as the sender.

[0147] The item "Second Email Address" is information that identifies the user who approves the document data as the recipient in the process of concluding a contract by approving the document data, and is the email address that serves as the contact address for that user.

[0148] Specifically, the item "Second Email Address" is the email address of the user who approves the document data as the recipient. Note that there may be multiple users approving the document on each party's side, and if the user sending the document data specifies the email addresses of multiple users who will approve the document data, the contract management database 215 will also manage each of the specified email addresses.

[0149] The "Sending Date and Time" field contains information about the date and time when the sender, a user, initiated the process of requesting approval of the document data from each user.

[0150] The "User Signature Date and Time" field contains information about the date and time when the user performed an approval operation on the document data.

[0151] Specifically, the item "User Signature Date and Time" includes information about the timing when a user who has been requested to approve the document data reviews and approves the document data, and the server 20 accepts this operation, thereby electronically signing the document data. The server 20 electronically signs the document data each time a user performs the approval operation, and stores the timing information in the signing management database 215.

[0152] The item "Date and Time of Contract Completion" contains information about the date and time when the contract was completed.

[0153] Specifically, the item "Contract Completion Date and Time" is recorded in the contract management database 215 when the contract is concluded using the electronic contract service provided by server 20. The contract is considered concluded when all users designated to approve the document data complete the approval process.

[0154] The "Status" field indicates the stage in the contract signing process.

[0155] Specifically, the item "Status" may include the following as stages in the contract signing process: • Before sending: Indicates that the document data has been registered on server 20 by the sender, but has not yet been sent to the recipient. • In Progress: Indicates that the document data has been sent, but approval by each user has not yet been completed. • Completed: Indicates that the contract has been finalized. • Rejected, Returned: Indicates a situation where the contract was not finalized due to circumstances such as the user not approving the document data, or a timeout occurring after a certain period of time had elapsed before approval was complete. Figure 9 shows the data structure of the document management database 216. The document management database 216 includes the following items: "Document Management ID", "Contract Signing ID", "Document Title", "Contract Start Date", "Contract Expiration Date", "Automatic Renewal Status", and "Viewing Permission".

[0156] The "Document Management ID" field is information that identifies each document data being managed.

[0157] The "Contract Signing ID" field is information that identifies each contract signing procedure performed by the parties to approve the document data.

[0158] Specifically, the item "Contract Signing ID" may be associated with information (Contract Signing ID) that identifies each contract signing, which is managed in the contract signing management database 215.

[0159] The "Document Title" field contains information about the title of the document data being managed.

[0160] Specifically, the item "Document Title" may be a term used as the type or name of a contract, such as a confidentiality agreement, a sales agreement, or a license agreement.

[0161] The item "Contract Start Date" is the information shown in the document data as the contract start date.

[0162] Specifically, the item "Contract Start Date" may be set to the following value: • When the contract is finalized, Server 20 reads the contract start date from the contract data. • Information received from the user as the contract start date The same applies to the following items: "Contract Expiration Date" and "Automatic Renewal Status".

[0163] The item "Contract Expiration Date" is the information shown in the document data as the contract's expiration date.

[0164] The item "Automatic Renewal Status" indicates, in the document data, whether or not the contract period will be automatically extended (automatically renewed) without the parties specifically renegotiating a new contract upon the expiration of the contract period.

[0165] The item "Viewing Permission" is information about users who are set to have viewing permission for documents (e.g., contracts) managed in the document management database 216. Server 20 may allow users set as stakeholders of a document to view the document, and may not allow users who are not set to view the document to view it.

[0166] Specifically, the "Viewing Permissions" item may be used to manage the following users as stakeholders in the document data. - Users recorded in the contract management database 215 as users who approve document data. Note that the server 20 may identify the parties involved in the document data by referring to the users who approved the document data in the contract management database 215, rather than retaining the information of the parties involved in the document management database 216. • In the contract signing service provided by Server 20, in addition to the user who approves the document data, the server also accepts the designation of users to whom the data will be shared once the contract is signed. These designated users (the users to whom the data is transferred) are the ones specified. For example, in the case of minutes of a board meeting, a director may approve the document data, and then share the approved minutes with other users such as executive officers. • Other users designated by users who approve the document data, users who have permission to view the document data, etc. Furthermore, the "Viewing Permissions" item may be configured to include information that identifies departments or divisions within an organization, rather than individuals. For example, it may be possible to configure information corresponding to the "Department" item in user database 211. In other words, by defining which departments or divisions can view documents, users in those departments or divisions within the organization can view the documents.

[0167] <3 operations> Figure 10 shows the process flow for a general-purpose service with an integrated account, where the user calls other services while simultaneously agreeing to the terms of service for those other services.

[0168] As described above, Server 99 is a server that provides general-purpose services with an integrated ID.

[0169] In step S1021, the server 99 presents the user on terminal 10 with a service operation screen that includes a specific service invocation section (which makes a specified service available on the user's terminal 10 in response to user operations).

[0170] As described above, the server 99 is configured to store user account information for the first service (general-purpose service; a service provided by the server 99 in the illustrated example) in the account linkage database 212.

[0171] In the account linking database 212, the first service is a service in which an account is created based on identification information issued after identity verification, as user account information for the first service. A messaging service where accounts are issued based on phone numbers, and users send and receive messages with each other. A payment service that issues accounts based on phone numbers and provides payment functionality. Services using personal identification numbers issued by government agencies, It may also be configured to store account information for at least one of the following services. Thus, the server 99 may provide at least one of the messaging service, payment service, or personal identification number service.

[0172] Furthermore, if a user of a service provided by server 20 has linked their user account for the server 20 service with their user account for the general-purpose service of server 99, server 20 may also be able to obtain the user account information for the server 99 service.

[0173] In step S1011, terminal 10 displays the general-purpose service operation screen of server 99 and accepts an operation on the operation screen to specify that a particular service should be used. For example, the operation screen displays one or more icons representing a particular service, and an operation on the icon executes the specific service corresponding to the icon. For example, the icon has a link such as a URL set to it for using the particular service, and in response to the user's operation of specifying the icon, terminal 10 performs processing such as accessing the service site of the particular service via the link such as the URL, or launching the application of the particular service installed on terminal 10.

[0174] In step S1023, server 99 connects to server 96 of a specific service specified by the user of terminal 10 and receives information from server 96 to allow the user to use the specific service. For example, the icon representing the specific service may include a URL containing information that identifies the specific service, and accessing this URL may allow access to server 96 of the specific service via server 99. Server 99 may also obtain user account information for the specific service from server 96.

[0175] In step S1025, the server 99 presents the user of terminal 10 with an operation screen for using a specific service.

[0176] In step S1013, terminal 10 accepts an action to begin using a specific service, including agreeing to the terms of service.

[0177] In step S1027, server 99 registers in the account linking database 212 that the user has agreed to the terms of service for the specific service, associating it with the user ID of the general-purpose service.

[0178] In this way, server 99 receives information indicating that a user of the second service (specific service), which is different from the first service, has agreed to the terms of use for that second service. Server 99 associates the received information with the account information of the user of the first service who gave their consent, and stores in the account linkage database 212 that the user has agreed to the terms of use for the second service.

[0179] As described above, the server 99 stores the information received in steps S1013 and S1027 in the account linkage database 212, associating it with the account information of at least one of the following users: a messaging service where accounts are issued based on telephone numbers and users send and receive messages; a payment service where accounts are issued based on telephone numbers and payment functions are provided; and a service using personal identification numbers issued by government agencies.

[0180] In this way, the server 99 accepts an operation to agree to the terms of use for the second service on the operation screen of the first service, thereby identifying the information of the first user account associated with the information received in steps S1013 and S1027, and stores the information received in steps S1013 and S1027 and the identified first service account information in the account linkage database 212.

[0181] In step S1029, the server 99 outputs to the terminal 10 information for each specific service whose terms of service have been agreed upon and which are associated with the user account of the general-purpose service.

[0182] Server 99 outputs to each user a list of information associated with the user account information of the first service, which indicates that each user has agreed to the terms of service (a list of specific services for which the terms of service have been agreed).

[0183] In step S1015, terminal 10 displays a list of specific services whose terms of service have been agreed to and are associated with the user account of the general service.

[0184] This allows users to view a list of specific services for which they have agreed to the terms of service through a general-purpose service, making it even easier to see a list of services they are using.

[0185] Figure 11 shows the process flow in a general-purpose service with an integrated account, where a contract signing service is called and the user's agreement to the contract terms is accepted by that service.

[0186] In step S1121, the server 99 presents the user of terminal 10 with a service operation screen that includes a call unit for the contract signing service.

[0187] In step S1111, terminal 10 receives an operation from the user to designate the use of the contract signing service.

[0188] In step S1123, server 99 connects to the contract signing service (server 20) specified by the user and receives information from the server (server 20) for the service that allows the user to use the contract signing service (such as information on the operation screen that accepts the operation to sign a contract, and a list of contracts associated with the user's account in the contract signing service).

[0189] In step S1125, the server 99 presents the user of terminal 10 with an operation screen for using the contract signing service.

[0190] Here, the first service (general-purpose service provided by server 99) may be a service based on an individual number issued by an administrative agency, and an electronic certificate may be issued to the individual to whom the individual number is issued. In this case, the service that manages contracts (server 20) may accept an operation to agree to the contract terms using the electronic certificate issued to the individual in association with the individual number, thereby affixing an electronic signature to the information indicating the contract terms (for example, contract data) (there are various ways of affixing the electronic signature, such as a business signature type (witness type) by a business that provides contract conclusion services via electronic contracts, and a party signature type where the parties concluding the contract sign), and outputting information indicating that the user has agreed to the contract terms (such as outputting the information of the electronically signed contract).

[0191] In step S1113, terminal 10 receives an operation from the user to approve the contract terms in the contract signing service. Terminal 10 transmits data relating to the signed contract.

[0192] In step S1127, server 99 associates the contract data with the user ID of the general-purpose service and registers it in the account linkage database 212. For example, server 99 may obtain the contract data via the electronic contract service (server 20).

[0193] In this way, the server 99 receives information output by the service that manages contracts, which indicates that the user has agreed to the contract terms and conditions relating to the contract. The server 99 stores the information received in steps S1113 and S1127 in the account linkage database 212, associating it with the account information of the user of the first service who agreed to the received information.

[0194] In steps S1113 and S1127, the server 99 may receive information output by a service that manages contracts, which indicates that the user has agreed to the contract terms relating to the contract. This may include receiving contract information from an electronic contract service in which each user concludes a contract by performing an electronic approval operation on the document data subject to the conclusion of the contract, or receiving contract information from a service that manages contracts concluded on paper.

[0195] As described above, the server 99 stores the information received in steps S1113 and S1127 in the account linkage database 212, associating it with the account information of at least one of the following users: a messaging service where accounts are issued based on telephone numbers and users send and receive messages; a payment service where accounts are issued based on telephone numbers and payment functions are provided; and a service using personal identification numbers issued by government agencies.

[0196] In steps S1113 and S1127, the server 99 may provide the user with a screen for using the first service, and call the contract management service from the first service to identify the information output by the contract management service and the account information of the first service. The server 99 associates the information received in steps S1113 and S1127 with the identified account information of the first service and stores it in the account linkage database 212.

[0197] In this way, in steps S1113 and S1127, the server 99 accepts an operation to conclude a contract on the operation screen of the first service, thereby identifying the information of the first user account associated with the information received in steps S1113 and S1127, and storing the identified information of the first service account in the account linkage database 212 in association with it.

[0198] In step S1129, the server 99 outputs to the terminal 10 information for each contract whose terms and conditions have been agreed upon and are associated with the user account of the general-purpose service.

[0199] Server 99 outputs to terminal 10 a list of information associated with the user account information of the first service, which indicates that the user has agreed to the contract terms and conditions relating to the contract.

[0200] For example, the account linkage database 212 may be configured to store account information of users of airlines providing air travel services as a first service. In steps S1113 and S1127, the server 99 may receive information indicating that the user has agreed to a contract (including travel insurance contracts, etc.) associated with the use of air travel services in the contract management service. The server 99 may output a list that includes information on the air travel services used by the user (information such as passengers, flight schedules, and boarding gates related to the ticket) and information on contracts associated with the use of air travel services that the user has entered into.

[0201] In step S1115, terminal 10 displays a list of contracts whose terms and conditions have been agreed to and are associated with the user account of the general-purpose service.

[0202] This allows users to view a list of signed contracts and other agreements through a general-purpose service, making it even easier for them to review the contracts and other agreements they have agreed to.

[0203] Figure 12 shows the process flow for accepting a user's agreement to the terms of service in a specific service and linking it with the user ID of a general-purpose service.

[0204] In step S1221, the server 96 for the specific service presents the user of terminal 10 with an operation screen to start using the specific service.

[0205] In step S1211, terminal 10 accepts an operation from the user to agree to the terms of service.

[0206] In step S1223, server 96 records that the user has agreed to the terms of service. As a result, server 96 issues the user's account information for the specific service.

[0207] In step S1225, the server 96 presents an operation screen for specifying a general-purpose service with an integrated ID. For example, on the operation screen for a specific service, an icon representing a general-purpose service is displayed, and the user is allowed to select that icon. This icon contains information such as a link for connecting to the general-purpose service.

[0208] In step S1213, terminal 10 accepts an operation from the user to specify a general-purpose service and link the general-purpose service account with the specific service account.

[0209] In step S1229, server 96 transmits to the general service specified by the user the identification information of the specific service (such as the identification code assigned to the specific service by server 99 and the name of the specific service) and information indicating that the user has agreed to the terms of service. This allows the account linkage database 212 to store information indicating that a user has agreed to the terms of service of the specific service in association with users who have an account in the general service.

[0210] Furthermore, server 96 may choose not to link the account information of a specific service with server 99 of the general-purpose service (i.e., it may not retain the account information of users of a specific service in the account linkage database 212), but may retain in the general-purpose service that the user has agreed to the terms of service of the specific service. This allows the general-purpose service to confirm that a user has agreed to the terms of service of a specific service, even for users who do not want the general-purpose service to retain their account information of a specific service.

[0211] Figure 13 shows the process flow for receiving a user's agreement to contract terms in the contract signing and document management service and linking it with the user ID of the general-purpose service.

[0212] In step S1321, the server 20 presents the user of terminal 10 with an operation screen for using the contract signing and document management service.

[0213] In step S1311, terminal 10 receives an operation from the user to agree to the contract terms.

[0214] In step S1323, the server 20 records that the terms and conditions of the contract have been agreed upon and updates the contract management database 215 and the document management database 216.

[0215] In step S1325, the server 20 presents the user of terminal 10 with an operation screen that allows them to specify a general-purpose service having an integrated ID. For example, on the operation screen for the contract signing and document management service, an icon representing a general-purpose service is displayed, and the user is allowed to select that icon. This icon contains information such as a link for connecting to the general-purpose service.

[0216] In step S1313, terminal 10 accepts an operation from the user to specify a general-purpose service and link the general-purpose service account with the specific service account.

[0217] In step S1329, the server 20 transmits the identification information of the contract signing and document management service and information indicating that the user has agreed to the contract terms to the general-purpose service specified by the user. This allows the server to associate information indicating that a user has agreed to the contract terms in the contract signing and document management service with users who have an account in the general-purpose service and store it in the account linkage database 212. For example, a user can refer to a list of contracts whose terms they have agreed to via the general-purpose service, further improving user convenience.

[0218] Figure 14 shows the process flow for notifying users of a general-purpose service account that a service provider has changed its terms of service.

[0219] In step S1421, the server 99 presents an operation screen for the operator of a service linked to a general-purpose service to the user of that operator. The following description assumes that the user of the operator of a specific service is operating terminal 10B.

[0220] In step S1411, terminal 10B receives an operation from the user to register the terms of service that have been changed for a specific service.

[0221] In step S1423, server 99 registers information about the changed terms of service for a specific service in the database. The database holds information such as the version of the terms of service and the timing (date) when the terms of service are applied, for each service provider and for each service provided by that provider.

[0222] Server 99 receives information indicating that a user of a specific service, the second service, has agreed to its terms of service, and updates the account linkage database 212 (item "Terms of Service Agreement Status") based on the received information.

[0223] Furthermore, as described above, server 99 receives information from the operator of the second service indicating that the terms of service for the second service have been updated.

[0224] In step S1425, the server 99 refers to the account linking database 212 and notifies users who link their accounts for a specific service to a general-purpose service that the terms of service for that specific service have been changed.

[0225] In this way, upon receiving information indicating that the terms of service for a specific service, the second service, have been updated through the processing in steps S1411 and S1423, the server 99 refers to the account linkage database 212 and notifies the users of the first service associated with the information that they have agreed to the terms of service for the second service, through the first service, that the terms of service for the second service have been updated. For example, the first service may notify the user that the terms of service for the second service have been updated through a push notification to the user.

[0226] In step S1427, server 99 receives an operation from a user using a specific service indicating their agreement to the revised terms of service and updates the account linkage database 212 (item "Agreement Status of Linked Service Terms of Service").

[0227] In this manner, the server 99, in response to the updated terms of service for the second service, obtains an action from the user of the first service to agree to the updated terms of service, and in response to obtaining the action to agree to the updated terms of service, stores in the account linkage database 212 that the action to agree to the updated terms of service has been obtained, in association with the account information of the first user.

[0228] In step S1429, the server 99 notifies the users of the specific service operator of the status of each user's agreement to the amended terms of service. For example, the server 99 may refer to the account linkage database 212 and notify the user of terminal 10B of information such as the percentage of users who agree to the amended terms of service (which may be the percentage of users who agree to the amended terms of service relative to the total number of accounts, or the percentage of users who agree to the amended terms of service relative to the total number of active users who have logged into the service within a certain period), and the time-series change of that percentage (for example, the time-series change between the number of days elapsed since the terms of service were amended and the percentage of users who agree to the amended terms of service).

[0229] In step S1413, terminal 10B displays the status of each user's agreement to the revised terms of service. This allows the operator of a specific service to notify users of changes to the terms of service through a general-purpose service, making it easier to obtain agreement to the revised terms of service from users who frequently use the general-purpose service.

[0230] <4. Screen Example> Figure 15 shows an example of a screen in a service with an integrated account where users are prompted to agree to the terms of service and contract terms while transitioning to a specific service.

[0231] The general-purpose service operation screen 1500 is the operation screen for the general-purpose service.

[0232] In the illustrated example, the general-purpose service operation screen 1500 contains operation buttons for calling other services (specific services). It displays an operation screen (specific service display area 1520) for the user to agree to the terms of service when using the called specific service. In the illustrated example, the general-purpose service is described as a messaging service that provides messaging functionality.

[0233] The function list display area 1502 is an area that displays each function provided by the general-purpose service.

[0234] The account display area 1504 is an area that displays account information for users who use general-purpose services.

[0235] The messaging call operation unit 1506 is an operation component that accepts operations to execute the functions of the messaging service, as a function provided by the general-purpose service.

[0236] In the illustrated example, the messaging call operation unit 1506 accepts an operation to call up a chat screen that allows sending and receiving messages with other accounts (other users' accounts, advertiser accounts, etc.) as a messaging function provided by the messaging service.

[0237] The payment call operation unit 1508 is an operating component that accepts operations to execute the functions of a payment service, as a function provided by the general-purpose service.

[0238] The service usage confirmation operation unit 1509 displays a list of specific services linked by the user within the general-purpose service, in response to the user's operation. For example, the service usage confirmation operation unit 1509 may display a list of services for which the user has agreed to the terms of service, or it may distinguish and display services that the user is using but for which they have not yet agreed to the revised terms of service from services that they are not using. This makes it even easier to identify services for which the terms of service have been changed and require agreement.

[0239] The linked service display area 1510 is an area that displays a specific group of services that can be linked with general-purpose services.

[0240] In the illustrated example, the linked service display area 1510 shows an example in which four specific services, such as the first service designation unit 1512, can be executed. The linked service display area 1510 may also display operating members for using one or more specific services.

[0241] The first service designation unit 1512 is an operating member that accepts the designation of a specific service that is linked to a general-purpose service.

[0242] In the illustrated example, the first service designation unit 1512 activates and provides a securities service to the user as a specific service in response to user operation.

[0243] The second service designation unit 1514 is an operating component that accepts the designation of a specific service that is linked to a general-purpose service.

[0244] In the illustrated example, the second service designation unit 1514, in response to user operation, activates and provides to the user a service that manages value (points) that can be used for payment as a specific service.

[0245] The third service designation unit 1516 is an operating component that accepts the designation of a specific service that is linked to a general-purpose service.

[0246] In the illustrated example, the third service designation unit 1516 activates and provides a game service to the user as a specific service in response to user operation.

[0247] The fourth service designation unit 1518 is an operating member that accepts the designation of a specific service that is linked to a general-purpose service.

[0248] In the illustrated example, the fourth service designation unit 1518 activates and provides an EC (electronic commerce) service to the user as a specific service in response to user operation.

[0249] In each specific service corresponding to these first service designation units 1512, etc., it may be possible to send and receive messages between users in the specific service, perform payment processing, etc., by utilizing the messaging function (messaging call operation unit 1506), payment function (payment call operation unit 1508), etc., provided by the general-purpose service.

[0250] The specific service display area 1520 is an area that displays information for using a specific service designated by the user in a general-purpose service.

[0251] In the illustrated example, the specific service display area 1520 shows an example where the game service corresponding to the third service designation unit 1516 has been designated by the user from among the specific services displayed in the linked service display area 1510.

[0252] The terms and conditions agreement operation unit 1522 is an operating component that accepts the operation of reviewing and agreeing to the terms of use for using a specific service.

[0253] In the illustrated example, the terms and conditions agreement operation unit 1522 displays information indicating whether the user has agreed to the terms of service for a specific service (in the illustrated example, "agreement"). In response to user input to the terms and conditions agreement operation unit 1522, the terms of service for the specific service are displayed as an overlay or the like, and the user's operation to agree to the terms of service is accepted.

[0254] The linkage initiation operation unit 1524 is an operation component that accepts an operation to associate and store the user's account information for a general-purpose service with the user's agreement to the terms of service for a specific service.

[0255] The linkage initiation operation unit 1524 corresponds to the processes in steps S1013, S1027, etc., in Figure 10.

[0256] The service start operation unit 1526 is an operation member that accepts an operation to start using a specific service without the user using a function of associating consent to the terms of use of the specific service with information of the user's account of the general service.

[0257] FIG. 16 is an example screen of an operation screen for accepting consent to the terms of use and consent to the contract conditions in a service having an integrated account.

[0258] The contract conclusion service display area 1528 is an area that displays information for providing the functions of the contract conclusion / document management service (server 20) according to the user's operation in the general service with the user experience of the general service.

[0259] The contract conclusion service display area 1528 corresponds to the processes such as steps S1125 and S1113 in FIG. 11.

[0260] The talk target display area 1530 is an area that displays information of the account of the contract conclusion / document management service in the messaging function on the premise that the user uses the contract conclusion / document management service by the messaging function of the general service. For example, an operator providing the contract conclusion / document management service (server 20) creates an operation account for the general service.

[0261] In the illustrated example, the talk target display area 1530 displays that it is a talk screen with the account of the contract conclusion / document management service.

[0262] The talk content display area 1532 is an area that displays messages from the contract conclusion / document management service.

[0263] In the illustrated example, the talk content display area 1532 displays the following as messages from the account of the contract conclusion / document management service. • Information on the terms and conditions (including links to the terms and conditions; accessing these links will display the details of the terms and conditions). • Notification content prompting agreement to contract terms • Agreement to the contract terms will be retained in the contract signing and document management service (server 20). The consent operation unit 1534 is an operating member that accepts an operation to agree to the terms and conditions of the contract.

[0264] In the illustrated example, the consent operation unit 1534 accepts an operation indicating agreement to the contract terms. Alternatively, the user may agree to the contract terms by accepting the input of talk content via free text or the like to the input content specification unit 1540 described later (for example, by entering keywords such as "agree").

[0265] The input content display area 1536 is the area that displays the content of the post that the user has entered.

[0266] The chat content display area 1538 is an area that indicates that a contract has been concluded in response to the user performing an action to agree to the contract terms.

[0267] In the illustrated example, the talk content display area 1538 shows that the user can check each contract to which they have agreed through a general-purpose service.

[0268] The input content specification unit 1540 is an operating member that accepts the specification of input content in free text format.

[0269] The transmission operation unit 1542 is an operation component that accepts an operation to confirm the content entered by the user in the input content specification unit 1410, and to transmit the content entered by the user to the contract conclusion and document management service via the messaging function of the general-purpose service.

[0270] The list confirmation operation unit 1544 is an operation component that accepts operations to display the account information of a user of a general-purpose service and a list of concluded contracts associated with that account information.

[0271] The service activation unit 1546 is an operating component that accepts operations to execute contract signing and document management services.

[0272] In the illustrated example, the service activation unit 1546 executes a specific service, the contract signing and document management service, to allow users to view contracts and other documents related to contracts managed by the contract signing and document management service.

[0273] Figure 17 shows an example screen where a service provider notifies users that they have updated their terms of service through the user interface of a service with an integrated account.

[0274] The Terms of Service Management Display Area 1548 is an area within a general-purpose service that displays the management status of the terms of service for each specific service linked to the general-purpose service, for the operators of specific services.

[0275] The account display area 1550 is the area that displays the user accounts of the operator of a specific service.

[0276] The managed display area 1552 is the area that displays each specific service that manages the terms of service within the general-purpose service.

[0277] The first service details display area 1554 is an area that displays the history of changes to the terms of service for a specific service.

[0278] In the illustrated example, the first service details display area 1554 is displayed in a different manner from the specific service shown in the second service details display area 1556, indicating that it has been specified by the user. When a specific service corresponding to the first service details display area 1554 is specified by the user, the specified service display area 1558 displays details of the management status of the terms of service for that specified service.

[0279] The second service details display area 1556 is an area for displaying the history of changes to the terms of use for a specific service.

[0280] The specified service display area 1558 is an area for displaying a specific service specified by the user among the specific services subject to the management of the terms of use.

[0281] The registration operation unit 1560 is an operation member that accepts an operation to register the terms of use for the specified specific service.

[0282] The registration operation unit 1560 corresponds to the processes such as steps S1411 and S1423 in FIG. 14.

[0283] The change history display area 1562 is an area for displaying the history of changes to the terms of use.

[0284] In the illustrated example, the change history display area 1562 displays, for each version of the terms of use, the timing of registration on the management screen of the terms of use in the general service, the timing of notifying the users of the specific service of the changed terms of use, and the status of the terms of use being agreed.

[0285] The notification schedule specifying unit 1564 is an operation member that accepts the specification of a schedule for notifying the users of the specific service of the changed terms of use.

[0286] In the illustrated example, the notification schedule specifying unit 1564 displays an operation member for specifying the date and time for notifying that the terms of use have been changed in response to the user's operation.

[0287] The status confirmation operation unit 1566 is an operation member that accepts an operation to notify the users of the specific service of the change to the terms of use and confirm the status of the users agreeing to the changed terms of use.

[0288] More specifically, the status confirmation operation unit 1566 displays, in response to user operations, the percentage of users who have agreed to the revised terms of service, on a time axis starting from the date and time the terms of service were changed.

[0289] Depending on the timing of the notifications configured in this way, it is possible to notify users of a general service that the terms of service for a specific service have been changed.

[0290] The route confirmation operation unit 1568 is an operating component that accepts operations from users of a specific service to confirm the route to which they have agreed to the terms of service.

[0291] More specifically, the route confirmation operation unit 1568 aggregates and outputs the percentage of users of a specific service who have agreed to the terms of service, depending on the means by which the changes to the terms of service are notified. Means of notifying users of changes to the terms of service include, as described above, notifying users of the general-purpose service by ID, as well as notifying users of the specific service by contact information (email address, etc.) specified by the user when registering for that specific service. When notifying users of changes to the terms of service by these means, an operation component for confirming the terms of service is included in the notification, and the link associated with the above operation component is different for each notification method. For example, the URL for confirming the terms of service may have parameters added to it that are set according to the means of notifying users of changes to the terms of service. This makes it possible to accumulate information on the route by which each user performed the operation to agree to the terms of service (which notification method they used to confirm the terms of service).

[0292] <Summary> As explained above, users can review the terms of service and contractual agreements they have agreed to for the services they use through a general-purpose service, making management even easier.

[0293] For example, even if a will is digitized and stored in a contract signing and document management service (server 20), it becomes easy to check the contents of the will through the user's general-purpose service ID that manages the will.

[0294] Furthermore, service providers can use a generic service ID to notify users of changes to their terms of service.

[0295] Furthermore, it becomes easier for the parties entering into a contract to communicate matters such as contract renewal. For example, in a lease agreement, the landlord or property management company can notify the tenant of the upcoming contract renewal via a general-purpose service ID, and the renewal procedure can be carried out through the general-purpose service. It also becomes easier to notify the tenant of renewals of fire insurance and other related policies associated with the lease agreement.

[0296] Furthermore, as described above, managing both electronically concluded contracts and paper-based contracts makes it even easier to manage the status of contracts involved through general-purpose services.

[0297] General-purpose services have operational components for performing various specific services, and if a user frequently uses a general-purpose service (for example, if they use the messaging function of a general-purpose service on a daily basis), they will have more opportunities to check through the general-purpose service whether the terms of service for a specific service have been updated or whether there is a notification of renewal of an existing contract, and it may be easier to prevent them from overlooking such information. In the above embodiment, an example was described in which an individual can check the terms of service, contracts, etc., of the services they use through a general-purpose service. In addition, organizations such as businesses may also be able to check the terms of service and contractual conditions of services they use through a general-purpose service. For example, in the above description, an organization's user may be able to manage the services for which they have agreed to the terms of service using their organization's user account. Furthermore, an organization's user may be able to check the contracts they have entered into using their organization's account.

[0298] A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0299] Furthermore, by distributing all or part of each hardware configuration across multiple computers and connecting them to each other via a network, computer 90 can be virtually realized. Thus, the concept of a computer includes not only computers housed in a single enclosure or case, but also virtualized computer systems.

[0300] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters.

[0301] Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0302] Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.

[0303] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) 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.

[0304] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.

[0305] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, and Java (registered trademark).

[0306] Furthermore, the program code for the software that implements the functions of the embodiment may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the computer's processor may read and execute the program code stored in the storage means or storage medium.

[0307] The functions realized by the components described herein may be implemented in a circuit or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor is considered to be a circuit or processing circuitry, including transistors and other circuits. A processor may be a programmed processor that executes a program stored in memory.

[0308] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.

[0309] If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.

[0310] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0311] (Note) The details described in each of the above embodiments are noted below.

[0312] (Note 1) A program for operating a computer having one or more computer processors, wherein the memory unit is configured to store user account information for a first service, and the program causes one or more computer processors to perform the following steps: receiving at least one of the following: information indicating that a user of a second service has agreed to the terms of use for using a second service different from the first service, or information output in a service that manages contracts indicating that a user has agreed to the terms and conditions relating to a contract; storing the information received in the receiving step in the memory unit in association with the account information of the user of the first service who has agreed to the received information; and outputting a list of information associated with the account information of the user of the first service, which indicates that the user has agreed to the terms of use, or information indicating that the user has agreed to the terms and conditions relating to a contract.

[0313] (Note 2) The program described in Appendix 1, which, in the acceptance step, accepts information output by a service that manages contracts, which indicates that the user has agreed to the contract terms relating to the contract, and includes at least one of the following: accepting contract information from an electronic contract service in which each user electronically approves the document data subject to the conclusion of the contract, or accepting contract information from a service that manages contracts concluded on paper.

[0314] (Note 3) The program described in either Appendix 1 or 2, wherein the memory unit is configured to store information about a user's account in the first service, which is a first service in which an account is created based on identification information issued after identity verification, and which includes a messaging service in which an account is issued based on a telephone number and users send and receive messages, a payment service in which an account is issued based on a telephone number and payment functionality is provided, and a service using a personal identification number issued by a government agency, and in the step of storing the information, the program stores in the memory unit the information received in the receiving step in association with information about a user's account in at least one of the messaging service in which an account is issued based on a telephone number and users send and receive messages, a payment service in which an account is issued based on a telephone number and payment functionality is provided, and a service using a personal identification number issued by a government agency.

[0315] (Note 4) A program as described in any of Appendix 1 to 3, wherein in the receiving step, a screen for using the first service is provided to the user, and the first service calls a service for managing contracts, thereby identifying and storing the information output by the service for managing contracts and the account information of the first service, and in the step of associating the information received in the receiving step with the identified account information of the first service and storing it in a memory unit.

[0316] (Note 5) The first service is a service based on individual numbers issued by administrative agencies, in which an electronic certificate is issued to the individual to whom an individual number is issued, and in a service for managing contracts, the program described in Appendix 4 accepts an operation to agree to the contract terms using the electronic certificate issued to the individual, and outputs information indicating that the user has agreed to the contract terms.

[0317] (Note 6) A program as described in any of Appendix 1 to 5, wherein in the acceptance step, the program accepts an operation to agree to the terms of use of the second service on the operation screen of the first service, or accepts an operation to conclude a contract on the operation screen of the first service, thereby identifying the account information of the first user associated with the information accepted in the acceptance step, and in the storage step, the program associates the information accepted in the acceptance step with the identified account information of the first service and stores it in a storage unit.

[0318] (Note 7) In the receiving step, the program receives information indicating that a user of the second service has agreed to the terms of use of the second service, and the program causes one or more computer processors to perform the following steps: receiving information from the operator of the second service indicating that the terms of use of the second service have been updated; and, in response to receiving the information indicating that the terms of use of the second service have been updated, notifying the user of the first service to whom the information agreeing to the terms of use of the second service is associated, through the first service, that the terms of use of the second service have been updated. (A program as described in any of Appendix 1 to 6.)

[0319] (Note 8) The program, as described in Appendix 7, further performs on one or more computer processors the following actions: to obtain an action from a user of the first service in the first service to agree to the updated terms of service for the second service; and, in response to obtaining the action to agree to the updated terms of service, to store in a memory unit, in association with the account information of the first user, that an action to agree to the updated terms of service has been obtained.

[0320] (Note 9) A program as described in any of Appendix 1 to 8, wherein the memory unit is configured to store, as a first service, information of the user account of an airline that provides air travel services; in the receiving step, the service that manages contracts receives information indicating that the user has agreed to a contract (including contracts such as travel insurance) associated with the use of air travel services; and in the outputting step, the program outputs a list that includes information of the air travel services used by the user and information of the contracts associated with the use of air travel services that the user has entered into.

[0321] (Note 10) A method performed by a computer having one or more computer processors, wherein a storage unit is configured to store user account information for a first service, the method comprising: one or more computer processors receiving at least one of the following: information indicating that a user of a second service has agreed to terms of use for using a second service different from the first service, or information output in a service that manages contracts indicating that a user has agreed to the terms and conditions relating to a contract; storing the information received in the receiving step in a storage unit in association with the account information of a user of the first service who has agreed to the received information; and outputting a list of information associated with the account information of a user of the first service, which relates to at least one of the following: information indicating that the user has agreed to terms of use, or information indicating that the user has agreed to the terms and conditions relating to a contract.

[0322] (Note 11) Information processing device, wherein a storage unit is configured to store user account information for a first service, and the control unit of the information processing device performs the following steps: receiving at least one of the following: information indicating that a user of a second service has agreed to the terms of use for using a second service different from the first service, or information output in a service that manages contracts indicating that a user has agreed to the contract terms relating to the contract; storing the information received in the receiving step in the storage unit in association with the account information of the first service user who has agreed to the received information; and outputting a list of information associated with the account information of the first service user, which indicates that the user has agreed to the terms of use, or information indicating that the user has agreed to the contract terms relating to the contract.

Claims

1. A program for operating a computer having one or more computer processors, The memory unit is configured to store user account information for the first service. The program is configured on one or more computer processors. A step of receiving at least one of the following: information indicating that the user of the second service has agreed to the terms of use for using the second service, which is different from the first service; or information output by a service that manages contracts, indicating that the user has agreed to the terms and conditions of the contract; A step of storing the information received in the aforementioned receiving step in the storage unit in association with the account information of the user of the first service who gave consent regarding the received information, A program that performs the step of outputting a list of information relating to the account information of a user of the first service, which includes at least one of the following: information indicating that the user has agreed to the terms of service, or information indicating that the user has agreed to the terms and conditions relating to the contract.

2. In the aforementioned acceptance step, information is received from the service that manages the contract, which indicates that the user has agreed to the contract terms and conditions relating to the contract. Receiving contract information from an electronic contract service that concludes a contract by having each user perform an electronic approval operation on the document data subject to the conclusion of the contract, or Receiving information on the aforementioned contract from a service that manages contracts concluded on paper, The program according to claim 1, comprising at least one of the following.

3. In the storage unit, the first service creates an account based on identification information issued after identity verification, as user account information for the first service, A messaging service where accounts are issued based on phone numbers, and users send and receive messages with each other. A payment service that issues accounts based on phone numbers and provides payment functionality. Services using personal identification numbers issued by government agencies, It is configured to store account information for at least one of the following services: In the step of storing the information, the information received in the receiving step is A messaging service where accounts are issued based on phone numbers, and users send and receive messages with each other. A payment service that issues accounts based on phone numbers and provides payment functionality. Services using personal identification numbers issued by government agencies, The program according to claim 1, which is stored in the storage unit in association with the account information of at least one of the users.

4. In the aforementioned acceptance step, while providing the user with a screen for using the first service, the first service calls the service for managing the contract, thereby identifying the information output by the service for managing the contract and the account information for the first service. The program according to claim 1, wherein in the step of storing, the program stores in the storage unit the information received in the receiving step and the information of the account for the specified first service in association with each other.

5. The first service mentioned above is a service based on individual numbers issued by administrative agencies, and an electronic certificate is issued to the individual to whom an individual number is issued. The program according to claim 4, which, in a service for managing the aforementioned contract, accepts an operation to agree to the terms of the contract using an electronic certificate issued to the aforementioned individual, and outputs information indicating that the user has agreed to the terms of the contract.

6. In the aforementioned acceptance step, by performing at least one of the following: accepting an operation on the operation screen of the first service to agree to the terms of use of the second service, or accepting an operation on the operation screen of the first service to conclude a contract, the information of the first user account associated with the information accepted in the aforementioned acceptance step is identified. The program according to claim 1, wherein in the step of storing, the program stores in the storage unit the information received in the receiving step and the information of the account for the specified first service in association with each other.

7. In the aforementioned acceptance step, information is received indicating that the user of the second service has agreed to the terms of use for the second service. The program further provides the following to one or more computer processors: The steps include receiving information from the operator of the second service indicating that the terms of use for the second service have been updated, The program according to claim 1, which, upon receiving information indicating that the terms of use for the second service have been updated, causes the program to perform the step of notifying a user of the first service, whose information is associated with their agreement to the terms of use for the second service, through the first service that the terms of use for the second service have been updated.

8. The program further provides the following to one or more computer processors: With respect to the updated terms of service for the second service, the first service obtains an action from the user of the first service to agree to the updated terms of service, The program according to claim 7, wherein, upon obtaining an operation to agree to the updated terms of service, the storage unit stores in association with the first user's account information that an operation to agree to the updated terms of service has been obtained.

9. The storage unit is configured to store account information of users of airlines providing air service as the first service. In the aforementioned acceptance step, the service that manages the contract receives information indicating that the user has agreed to the contract (including contracts such as travel insurance) associated with the use of the air service, The program according to claim 1, wherein in the step of outputting the list, the list includes information on the air services used by the user and information on contracts associated with the use of the air services that the user has entered into.

10. A method performed by a computer having one or more computer processors, The memory unit is configured to store user account information for the first service. The above method involves one or more computer processors, A step of receiving at least one of the following: information indicating that the user of the second service has agreed to the terms of use for using the second service, which is different from the first service; or information output by a service that manages contracts, indicating that the user has agreed to the terms and conditions of the contract; A step of storing the information received in the aforementioned receiving step in the storage unit in association with the account information of the user of the first service who gave consent regarding the received information, A method for performing the steps of: outputting a list of information relating to the account information of a user of the first service, which includes at least one of the following: information indicating that the user has agreed to the terms of service, or information indicating that the user has agreed to the terms and conditions relating to the agreement.

11. An information processing device, The memory unit is configured to store user account information for the first service. The control unit of the information processing device, A step of receiving at least one of the following: information indicating that the user of the second service has agreed to the terms of use for using the second service, which is different from the first service; or information output by a service that manages contracts, indicating that the user has agreed to the terms and conditions of the contract; A step of storing the information received in the aforementioned receiving step in the storage unit in association with the account information of the user of the first service who gave consent regarding the received information, An information processing device that performs the step of outputting a list of information relating to the account information of a user of the first service, which includes at least one of the following: information indicating that the user has agreed to the terms of service, or information indicating that the user has agreed to the terms and conditions relating to the contract.

Images