These Tokyo Public Transportation Open Data Challenge Entry Rules (hereinafter referred to as "these Entry Rules") set forth the qualifications and conditions for entering web systems, applications, IoT gadgets, or documents (hereinafter collectively referred to as "Work") to the Tokyo Public Transportation Open Data Challenge (hereinafter referred to as "this Challenge") held by the Association for Open Data of Public Transportation (hereinafter referred to as "Association") and others.

To enter this Challenge, please produce your Work using or referring to the public transportation data provided by the Public Transportation Open Data Center operated by the Association (such center shall be hereinafter referred to as "Center," and such data as "these Data," as defined in paragraph 9, Article 1 of the Tokyo Public Transportation Open Data Challenge API Use Permission Rules established separately) based on an agreement to the Tokyo Public Transportation Open Data Challenge API Use Permission Rules which the Public Transportation Open Data Center (hereinafter referred to as "the Center")operated by Association separately determines.

Entry Qualifications

1. Entrants in this Challenge must agree to both of these Entry Rules and the Tokyo Public Transportation Open Data Challenge API Use Permission Rules. Such entrants shall be hereinafter referred to as "Developers".
2. Entrants may be an individual, group, or corporation.
3. There is no limit on nationality, age, or place of residence; provided, however, that minor entrants must obtain the permissions of their guardians. Minors entering as part of club activities also need the permissions of the teachers in charge of the club, in addition to those of the guardians.
4. A single Developer, including a group or corporation, may enter more than one Work. Developers may also belong to more than one group.
5. No entry will be accepted by an organized crime group as defined in item 2, Article 2 of the Act on Prevention of Unjust Acts by Organized Crime Group Members (Act No. 77 of 1991), a member of an organized crime group as defined in item 6 of the same Act, a quasi-member of an organized crime group, a company associated with an organized crime group, a corporate racketeer, etc., a person engaging in criminal activities under the pretext of a social activist, etc., or a violent group specialized in intellectual crime, or any other group or individual who seeks economic profit by making full use of violence, force, or fraudulent methods, or any person equivalent thereto (hereinafter collectively referred to as "Antisocial Forces"), or a Developer who is judged by the host to be having some interaction or involved with Antisocial Forces in such manner as cooperating in or are involved with the maintenance, operation, or management of Antisocial Forces by offering funds, etc. In addition, no entry by a Developer who is judged by the host to be having some interaction or involved with Antisocial Forces in such manner will be cancelled, even after being once accepted.
6. Any person involved with the judgment in this Challenge may enter this Challenge, but will not win a prize.

Entry Conditions

1. Developers will produce their Works based on the acceptance of these Entry Rules and the Tokyo Public Transportation Open Data Challenge API Use Permission Rules.
2. Developers will produce their Works using these Data; provided, however, that if the Work is other than a web system, application, or IoT gadget, it will be produced on the theme related to these Data.
3. If the Work is a web system or application, it will be made available to anybody without charge from entry to the awards ceremony.
4. These Data will be used in accordance with the Tokyo Public Transportation Open Data Challenge API Use Permission Rules and the guidelines for this Challenge.
5. The Work must be original and unpublished, which means it must be a work which has never been entered in the past or is planned to be entered, or is now under judgment of, any other contest, etc., and has never won a prize in any contest in the past.
6. The Works developed for this Challenge must not be entered to other contests.
7. The Works to be entered to this Challenge must be devised and produced by Developers.
8. Developers hereby warrant to the host and co-hosts of this Challenge, other groups to provide cooperation, special cooperation, or support for this Challenge, and open data partners (hereinafter collectively referred to as "Implementation Subject") that the copyrights on their Works have been properly handled in advance so that no problem will arise in the entry to this Challenge.
9. The Works may be produced by combining these Data and such other data as may cause no copyright problem.
10. Developers hereby agree that they will bear the costs pertaining to the entry to this Challenge such as the costs for building the development and execution environments for Works and Internet communication fees and connection costs.
11. The prizewinners in this Challenge will attend the awards ceremony and give presentations of their Works, in principle.
12. The prize money in this Challenge to an individual will be paid by transferring to the designated account in the name of the winner, that to a group will be to the designated account in the name of the representative, and that to a corporation will be to the designated account in the name of the corporation.
13. Web system or application Works will be entered by first registering the Developers' information in the exclusive website and then releasing the Works in Google Play, App Store, Windows Store, or any other website. Works other than web systems or applications may be entered by submitting a completed entry form provided in the web page designated by the Association, emailing to the designated email address, or sending or bringing to the designated address.
14. Developers hereby agree to be disqualified from entering this Challenge if their Works arrive at the address designated by the Association after the deadline.
15. Any iOS application Works will be deemed to have been entered to this Challenge as of the date of examination registration with Apple Inc.; provided, however, that if the Work is not registered with App Store as a result of the examination by Apple Inc., or if the re-examination registration with Apple Inc. due to a system revision or application name change is late for the deadline for submission to this Challenge, though the date of the first examination registration with Apple Inc. was before such deadline, the Work will be disqualified from judgment in this Challenge. For this reason, it is recommended that the entrants by iOS applications make their examination registrations with Apple Inc. allowing enough time, considering the possibility of revisions.
16. The applications entered to this Challenge will not be officially approved, released, or distributed, etc. as official applications or official services of the Implementation Subject.
17. Should any problem occur in relation to copyrights, moral rights, neighboring rights, design rights, trademark rights, utility model rights, patent rights or any other rights (hereinafter collectively referred to as "Intellectual Property Rights"), it will be settled upon the responsibility and at the cost of the relevant Developer. If the Implementation Subject or a third party other than the Implementation Subject incurs any damage for a reason attributable to a Developer, such Developer will be liable for the damage.
18. The Implementation Subject will neither warrant in any respect the accuracy, completeness, or fitness for particular purposes of the contents of these Data prepared by the Implementation Subject for this Challenge, nor be liable in any manner for the damage caused by the use of, or a failure to use, the relevant Data by Developers.
19. Developers hereby agree in advance that the provision of these Data prepared for this Challenge may be ceased or the contents of these Data may be changed for a reason of the Implementation Subject.
20. 20. Developers hereby agree that these Data prepared by the Implementation Subject for this Challenge will be planned to be provided until the end of this Challenge.
21. Any Work judged by the host that is or may be offensive to public order and morals or against the purpose of this Challenge will be disqualified from judgment in this Challenge.
22. The Intellectual Property Rights to the Works will be held by the Developers.
23. Developers will permit the Implementation Subject or a person designated by the Implementation Subject to disclose, duplicate, distribute, publicly transmit, publish, or otherwise use their Works, the names thereof, and the Developers’ names by electronic or any other means for the purpose of announcement, advertisement, or publicity of, or record for this Challenge without charge and for an indefinite period of time.
24. Developers may report the entries of their Works to this Challenge in their own websites or social networking sites, etc.; provided, however, that it will not be allowed to make a false indication or statement there as if their Works were developed, etc. by the Implementation Subject.
25. Developers entering web system or application Works will state in accordance with the guidelines prepared separately by the Implementation Subject their contact information to be used in inquiries regarding the contents or operation of such Works. Developers will thereby make their best efforts so that inquiries regarding the contents or operation of the Works produced by them will not be sent directly to the open data partners.
26. Developers must not use these Data prepared by the Implementation Subject for this Challenge for any purpose other than the development and writing of their Works to be entered to this Challenge and the use of these Data in such Works. Developers hereby agree in advance that, should it be found that they have used these Data prepared by the Implementation Subject for this Challenge for any purpose other than the above, the host will cease providing the relevant Data to such Developer(s) and may take legal actions thereagainst.
27. If any Work causes disadvantage or a bad reputation to the Implementation Subject, the host will cease providing information to the Developer of such Work immediately, and the relevant Developer will be disqualified from entering this Challenge.
28. Developers may neither provide a third party with or without charge, nor any application with charge using, these Data prepared by the Implementation Subject for this Challenge. Developers hereby agree in advance that, should any such act thereby be found, the host will cease providing the relevant Data to such Developer(s) and may take legal actions thereagainst.
29. Any Developer who made a misstatement in the entry will be disqualified from winning a prize.
30. If we fail to notify the Developer of his or her prizewinning because of a failure to contact him or her or for any similar reason, the entitlement of such Developer to the prize may be cancelled.
31. The information stated at the time of entry such as the name and contact information will be used exclusively for notification of prizewinning and contact in relation to the Works, and at the time of announcing the prize-winning Works; provided, however, that this will not apply in cases of using the same in the future within or outside Japan in a paper or electronic medium for the publicity, advertisement, or announcement of the Works, the name thereof, or Developers’ names.
32. Inquiries regarding the selection process in this Challenge cannot be responded to.
33. This Challenge may be cancelled without notice due to various reasons. In case of cancellation, the Implementation Subject will not be required to compensate for any cost spent by Developers to enter this Challenge before such Developers know the cancellation of this Challenge.
34. These Entry Rules shall be in Japanese, and translation thereof into any other languages shall be for reference only.
35. The formation, validity, and performance of these Entry Rules shall be completely governed by and construed under the laws of Japan.

Established December 7, 2017,
Effective the same date

These Tokyo Public Transportation Open Data Challenge API Use Permission Rules (hereinafter referred to as "these Rules") are established between the Association for Open Data of Public Transportation (hereinafter referred to as "Association") operating the Public Transportation Open Data Center (hereinafter referred to as "Center") and the developers to set forth the rules pertaining to the use of the API for the public transportation opening data or public transportation data with specific terms of use provided by the Center to the developers in the application contest titled "Tokyo Public Transportation Open Data Challenge" (hereinafter referred to as "this Challenge") held by the Association for Open Data of Tokyo Public Transportation (hereinafter referred to as "Association").

Article 1 (Definitions)
For the purposes of these Rules, the following terms will have the meanings as defined in the respective items:

1. The term "Public Transportation Data" means data related to public transportation such as operation information, route information, and facilities information of transportation, which collectively refers to the public transportation data neither used in these Data as defined in item 9 hereof nor the Public Transportation Data API as defined in item 3 hereof.
2. The term "Public Transportation Data Provider" means a person who created and provided the Center with Public Transportation Data or provided the Center with Public Transportation Data under the entrustment by a creator of such Public Transportation Data.
3. The term "Public Transportation Data API" means the API for the Center to provide Public Transportation Data.
4. The term "Developer" means a person provided with the Public Transportation Data API by the Center.
5. The term "Work" collectively means the web systems, applications, IoT gadgets, and documents created by Developers using or referring to the Public Transportation Data API.
6. The term "Public Transportation Open Data" means the Public Transportation Data used for the Public Transportation Data API and provided to Developers by the Center which are not restricted in use except by the provisions of these Rules and the guidelines for Public Transportation Data API Developers (hereinafter referred to as "Guidelines") and available free of charge.
7. The term "Specific Terms of Use" means the terms of use established independently by a Public Transportation Data Provider in the provision of their Public Transportation Data.
8. The term "Public Transportation Data with Specific Terms of Use" collectively means such Public Transportation Data used for the Public Transportation Data API that is provided to Developers by the Center under Specific Terms of Use.
9. The term "these Data" collectively means the Public Transportation Open Data and the Public Transportation Data with Specific Terms of Use.
10. The term "Public Transportation Data Catalogue Site" means the website for the Center to provide information on these Data for Developers.
11. The term "Public Transportation Data Developers Site" means the website for the Center to provide the functions required in the use of the Public Transportation Data API and technical information for Developers.
12. The term "Service" collectively means the web service provided by the Center for Developers, which collectively refers to the Public Transportation Data API, the Public Transportation Data Catalogue Site, and the Public Transportation Data Developers Site.
13. The term "Industrial Property Rights" collectively means patent rights, utility model rights, design rights, trademark rights, and the rights thereto and know-how, etc.
14. The term "Intellectual Property Rights" collectively means Industrial Property Rights and copyrights.
15. The term "User" means a person who uses or reads a Work.
16. The term "Account" means the information specific to a Developer and protected by an authentication password used for the Public Transportation Data API and the Public Transportation Data Developers Site to identify the Developer.

Article 2 (Consent to Rules)

1. A Developer who used the Public Transportation Data API, the Public Transportation Data Developers Site, or these Data will be deemed to have agreed to these Rules. A Developer who checked the "Agree" box for these Rules at user registration will be deemed to have agreed to these Rules.
2. A Developer will be deemed to have agreed to these Rules at the earlier point of time of those set forth in the preceding paragraph.

Article 3 (Creation, Renewal, and Deletion of Account)

1. Each Developer will, when using the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data, create an Account to use for communications with the Center.
2. A Developer may delete his/her own Account.
3. A Developer will use his/her Account with the due care of a good manager, and in order to protect it, not disclose or provide the password therefor to a third party.
4. A Developer will not reuse for the Account the password same as those used for other services or applications.

Article 4 (Permission on Use of Center)

1. The Center will, subject to compliance with these Rules, the Guidelines, and the Specific Terms of Use of the Public Transportation Data with Specific Terms of Use, grant a non-exclusive right to use the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data to a Developer who has obtained a proper Account.
2. The provider connection fees and communication expenses to use the Service will be borne by the person who established communication.
3. No Intellectual Property Rights other than those granted under this Article will be assigned or licensed to Developers by these Rules either explicitly or implicitly.
4. The Center may decide at its own discretion the restrictions on the numbers of Developers' calling or access time to the Public Transportation Data API.

Article 5 (Use of Public Transportation Data API, Public Transportation Data Developers Site, and These Data)

1. Developers may, by agreeing to these Rules and only for the purpose of producing Works with an aim to enter this Challenge, use the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data non-exclusively in accordance with the provisions set forth below without the obligation to enter the Works to this Challenge; provided, however, that if the organizer of this Challenge judges that any Developer is using the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data for a purpose other than producing a Work with an aim to enter this Challenge, the Center may stop such Developer from using the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data, and take legal actions against such Developer.
2. Developers will use the Public Transportation Data API, the Public Transportation Data Developers Site, and these Data in accordance with the following items:
   (1) to use the Public Transportation Data API in a manner as set forth in these Rules and the Guidelines at each access;
   (2) to use these Data in accordance with these Rules and the Guidelines; provided, however, that in case these Data are the Public Transportation Data with Specific Terms of Use, Developers will comply with Article 6;
   (3) not to use the Public Transportation Data API, the Public Transportation Data Developers Site, or these Data in a manner that may cause disadvantage or a bad reputation to the Center, the Association, or the Public Transportation Data Providers;
   (4) not to decompose or modify these Data in a manner that may damage the original meaning;
   (5) not to display all or part of these Data anywhere other than in the Work;
   (6) if all or part of these Data are renewed, to renew the relevant part of these Data used in the Work immediately in accordance with the Guidelines;
   (7) not to violate the Intellectual Property Rights of the Center, the Association, or the Public Transportation Data Providers when using the Public Transportation Data API or these Data; and
   (8) not to make any representation to the effect that the Center, the Association, or any Public Transportation Data Provider will give any guarantee or assume any responsibility concerning the Work.
3. Developers will make sure that the contents of the Public Transportation Data displayed in their Work will reflect those of these Data provided by the Center accurately in accordance with the Guidelines.
4. Developers may combine these Data with other data on condition that they will not infringe any Intellectual Property Rights of a third party.
5. The Center may change the formats of the Public Transportation Data API and these Data at any time; provided, however, that Developers will be notified in advance of such change at the email addresses declared by the Developers at registration.
6. When using the Service, Developers may use the trademarks of the Public Transportation Data API and Public Transportation Open Data in accordance with the Guidelines.
7. Developers may not use these Data for profit.

Article 6 (Use of Public Transportation Data with Specific Terms of Use)

1. To the terms of use for the Public Transportation Data with Specific Terms of Use, the Specific Terms of Use of the relevant data will be applied in addition to the provisions of these Rules; provided, however, that if there is any difference between the Specific Terms of Use and these Rules, the Specific Terms of Use will take priority.

Article 7 (Copyrights)

1. The copyrights to the Public Transportation Data API will be held by Yokosuka Telecom Research Park YRP Ubiquitous Networking Laboratory (hereinafter referred to as "UNL").
2. The Center hereby warrants that it has obtained from UNL the permissions concerning the establishment of non-exclusive rights of use and reuse of the Public Transportation Data API.
3. The Center hereby warrants to Developers that the copyrights to these Data are held by the Public Transportation Data Providers or those who provided these Data to the Public Transportation Data Providers (hereinafter collectively referred to as "Public Transportation Data Providers, etc."), and that it has obtained from the Public Transportation Data Providers, etc. the permissions concerning the establishment of non-exclusive rights of use and reuse of these Data.

Article 8 (Intellectual Property Rights)

1. The ownership of the technical results of the inventions, devices, designs, know-how, and works newly obtained by Developers developing the Works (hereinafter collectively referred to as "Inventions") and the Intellectual Property Rights pertaining thereto will be as set forth below:
   (1) The ownership of the Inventions made independently by the Center or a Developer and the Intellectual Property Rights pertaining thereto will be held independently by the party who made such Inventions.
   (2) The ownership of the Inventions made jointly by the Center and a Developer or Developers and the Intellectual Property Rights pertaining thereto will be shared by the Center and the Developer(s).
2. The details of practice of the Inventions shared by the Center and the Developer(s) pursuant to the preceding paragraph and the Intellectual Property Rights pertaining thereto will be determined through separate consultation.

Article 9 (Prohibitions)

1. Developers may not use these Data or the Service against the manner as set forth in these Rules and the Guidelines.
2. Developers may not use the Public Transportation Data with Specific Terms of Use against the manner as set forth in the Specific Terms of Use of such Data.
3. Developers may not:
   (1) violate, in the use of the Service, the laws and regulations of Japan or the country or region where the Developer is living;
   (2) destroy or interfere with the functions of the server, data, or network of the Center;
   (3) illegally use or cause a third party to use these Data and the Service against these Rules, the Guidelines, or the Specific Terms of Use;
   (4) collect or accumulate personal information, etc. on other Developer(s) without the prior written permission of the relevant Developer(s);
   (5) access the server of the Center illegally;
   (6) use the Account of a third party; and
   (7) acquire the password for the Account of a third party.
4. Except as there is a prior written approval of the Center and as separately set forth in the Specific Terms of Use of the Public Transportation Data with Specific Terms of Use, Developers hereby consent that the following acts are prohibited:
   (1) to release, reproduce, redistribute, publicly transmit, or assign these Data in a form reusable by a third party; and
   (2) to release, reproduce, redistribute, publicly transmit, or assign these Data incorporated in the Work without irreversible processing.

Article 10 (No Warranty, Indemnification)

1. The Center, the Association, and the Public Transportation Data Providers will try to maintain the accuracy of these Data and the information on the Service.
2. Developers hereby agree the following items:
   (1) that these Data and the Service will be provided to Developers on an "as is" basis;
   (2) that the Center, the Association, and the Public Transportation Data Providers will not be liable in any manner for any direct, accidental, consequential, or indirect damage caused to Developers due to the use of, or a failure to use, these Data or the Service; this will apply in cases where the Center, the Association, or the Public Transportation Data Providers were informed of the possibility of such damage; and
   (3) that the Center, the Association, and the Public Transportation Data Providers will not make any warranty in any manner except those contained in Article 7, including, but not limited to, that these Data and the Service are free of defect and will not be interrupted in use, as well as their merchantability, fitness for a particular purpose, and non-infringement of third party rights.
3. The Center will make its best efforts so that these Data will satisfy the following items:
   (1) that these Data will not contain any slander against a third party or illegal contents; and
   (2) that these Data contained in these Data will not contain any computer virus.
4. The Center, the Association, and the Public Transportation Data Provider will not be liable for the following items in any manner:
   (1) any illegal act of Developers using these Data and the Service;
   (2) any damage or disadvantage to Developers resulting from the use of these Data and the Service; and
   (3) any damage or disadvantage to users resulting from the use of a Work.
5. These Rules will not oblige the Center or the Public Transportation Data Providers to provide support or upgrades of any type such as failure corrections, support by telephone, fax, or email, and technical services.

Article 11 (Responsibility of Developers)

1. Developers will use these Data and the Service upon their own responsibilities.
2. Developers will make their best efforts to keep the information registered in their Accounts such as the association name, department, name, phone number, and email address (hereinafter referred to as "Account Information") correct and updated; provided, however, that Developers entering to this Challenge individually will not need to register their association names or departments in their Accounts.
3. Developers hereby agree that if the user name or email address and the password to be used to log in to the Service match the Account Information of a Developer, the relevant Developer will be deemed by the Center to have used the Service and charged if such Service is a paid service.
4. Developers will be liable for the costs incurred by the Center, the Association, or any Public Transportation Data Provider due to their illegal act or breach of their obligations as set forth in these Rules including the costs paid by the Center, the Association, and/or any Public Transportation Data Provider to restore the damage inflicted by such illegal act, and the damages, attorney's fees, etc. paid by the Center, the Association, and/or any Public Transportation Data Provider to third parties due to such illegal act.
5. Developers will announce to the users that the Center, the Association, and the Public Transportation Data Provider will not be responsible for the accuracy or integrity of these Data.

Article 12 (Compensation)

1. If any Work infringes any rights of a third party, the relevant Developer will take all responsibilities for the response to the third party claiming such infringement, and the Center, the Association, or the Public Transportation Data Providers will not be responsible or liable therefor in any manner.
2. If any Work causes disadvantage or a bad reputation to the Center, the Association, or the Public Transportation Data Providers, the relevant Developer will take all responsibilities and liabilities for such disadvantage or a bad reputation.

Article 13 (Deletion Authority)

1. If all or part of a Work developed by a Developer using these Data and the Service is, or may be, as judged by the Center, in violation of these Rules, the Specific Terms of Use, the Guidelines, or the privacy policy, the Center may suspend, discontinue, terminate, or delete, the use of these Data and the Service by such Developer without notifying such Developer.
2. If a Developer corresponds to any of the following, the Center may suspend, discontinue, terminate, or delete, the use of these Data and the Service by such Developer without notifying such Developer:
   (1) when a petition for seizure, provisional seizure, provisional disposition, or auction has been filed, or the Developer is subject to tax delinquency disposition or any other disposition by public authority, or a petition for bankruptcy, corporate reorganization, or civil rehabilitation proceedings or any similar proceedings has been filed;
   (2) when a bill or check drawn or accepted by the Developer was dishonored or the Developer has otherwise suspended payments;
   (3) when the Developer has resolved to dissolve, discontinue business, or assign all or any important part of the business;
   (4) when the financial condition has otherwise been, or there are reasonable grounds to believe that it is likely to be, deteriorated;
   (5) when the use of the Account has not been confirmed for a certain period of time;
   (6) when the Center judges that the trust relationship between the Center and the Developer cannot be restored; and
   (7) when it placed a considerable burden on the Center in using the Service such as exceeding the number of times of use prescribed in the Guidelines.

Article 14 (Term, Termination, and Change)

1. These Rules will start being applied to a Developer at the time when the Developer agrees to these Rules and sends the application notice to the Center, and the Center sends the approval notice to such Developer.
2. These Rules will terminate being applied to a Developer at the time when the Center or the Developer sends the notice of termination of these Rules to the other party.
3. The Center may change, suspend, or discontinue providing the Public Transportation Data API and these Data to a Developer and terminate applying these Rules to such Developer at any time regardless of the reason.
4. With the termination of the application of these Rules, the Developer will immediately cease the use of the Public Transportation Data API using the Work and these Data and delete these Data.
5. The Center may change all or part of the terms of use of these Rules, the Guidelines, and these Data, as necessary, without obtaining the prior consents of Developers; provided, however, that any material change will be effected after giving a prior notice to Developers and a reasonable period has passed.
6. In the preceding paragraph, if these Rules, Guidelines, or the Specific Terms of Use of the Public Transportation Data with Specific Terms of Use are changed and a Developer uses the Public Transportation Data API after the Center gives a notice of such change to Developers, such Developer will be deemed to have agreed to these Rules, the Guidelines, and the Specific Terms of Use of such Data after the change.

Article 15 (Handling of Personal Information)

1. Developers will disclose and register their Account Information to the Center in using these Data and the Service.
2. The Center may use and reproduce the Account Information disclosed by Developers for the communications regarding the use of these Data and the Service, and the maintenance of and improvement in these Data and the Service.
3. Developers hereby agree that the Center will use cookie and other technologies for confirming the use of the same Account for the purpose of the operation and analysis of the services and systems to improve the Works using these Data and the Service as well as the convenience of the server, obtain the traffic data between web services or applications and the server to analyze, and use such data statistically processed so that the users cannot be identified.
4. The Center will provide the Public Transportation Data Providers, as necessary, with information on the Works using these Data and the Service, web services statistically processed so that the users cannot be identified, and the traffic data between applications and the server.
5. The handling of the Account Information and the personal information pertaining to the use of the Public Transportation Data API not set forth herein will be governed by the privacy policy established separately by the Center.

Article 16 (Elimination of Antisocial Forces and Prohibition of Violent Acts, etc.)

1. Developers hereby represent and warrant that they themselves, or, in case of a corporation or group (hereinafter referred to as "Corporations"), any person belonging to a group operated by such Corporations including part-timers, do not at present, or will not in the future, correspond to an organized crime group, or a member or quasi-member of an organized crime group, a person who was a member of an organized crime group within the past five (5) years, a company associated with an organized crime group, a corporate racketeer, etc. a person engaging in criminal activities under the pretext of a social activist, etc., or a violent group specialized in intellectual crimes, or any person equivalent thereto (hereinafter collectively referred to as "Organized Crime Group Member, etc.") or have any of the following relationships:
   (1) relationship where it is recognized that an Organized Crime Group Member, etc. is controlling their management;
   (2) relationship where an Organized Crime Group Member, etc. is substantially involved in their management;
   (3) relationship where it is recognized that they are unreasonably using an Organized Crime Group Member, etc. to seek their own, the Corporations', or a third party's illicit gains, or cause damage to a third party;
   (4) relationship where it is recognized that they are involved with an Organized Crime Group Member, etc. by such means as offering funds, etc. or providing favors; and
   (5) relationship to be socially criticized which their officers or any other person substantially involved in their management has with an Organized Crime Group Member, etc.
2. Developers hereby warrant that they will not perform any of the following acts for themselves or by using a third party:
   (1) act of violent demands against a member, officer, observer, or the Secretariat of the Center or the Public Transportation Open Data Association, the Public Transportation Data Providers, or any person involved in this Challenge;
   (2) act of unreasonable demands beyond legal responsibilities against a member, officer, observer, or the Secretariat of the Center or the Public Transportation Open Data Association, the Public Transportation Data Providers, or any person involved in this Challenge;
   (3) act of using threatening speech or behavior or violence in relation to business;
   (4) act of discrediting or obstructing the business of the Center, the Association, or the Public Transportation Data Providers by spreading rumors or using fraudulent means or force; and
   (5) any other act similar to the above.
3. If a Developer is found to be in violation of any of the provisions hereof, the Center may suspend, without any notice or demand, the use of the Service and these Data by such Developer or any person involved therewith. The Developer will not make any objection to such action of suspension.

Article 17 (Severability)

1. Should any part of the provisions of these Rules be judged invalid, illegal, or unenforceable by a court as set forth in Article 19, the effectiveness, legality, and enforceability of the remaining provisions of these Rules will not be affected in any respect.

Article 18 (Survival Provision)

1. The provisions of paragraph 3 of Article 4, Article 6, Article 8 to Article 10, paragraph 3 to paragraph 5 of Article 11, Article 12, Article 13, and Article 15 to Article 19 will survive the termination of the Developers' use of these Data and the Service pursuant to these Rules.

Article 19 (Miscellaneous Provisions)

1. The formation, validity, and performance of these Rules will be governed by and construed in accordance with the laws of Japan in every respect.
2. These Rules shall be in Japanese, and translation thereof into any other languages shall be for reference only.
3. Any dispute regarding the contents and performance of these Rules, the Guidelines, and the Specific Terms of Use of the Public Transportation Data with Specific Terms of Use will be subject to the agreed exclusive jurisdiction of the Tokyo District Court or the Tokyo Summary Court in the first instance.

Established December 7, 2017,
Effective the same date

Specific Terms of Use
Refer to the Japanese version of the "Specific Terms of Use" in "Tokyo Public Transportation Open Data Challenge API Use Permission Rule".

1. Overview

These guidelines are required to be followed by developers when developing applications using public transportation-related data ("data of public transportation") obtained through the Open Data Challenge for Public Transportation in Tokyo API ("API"). These provide API specification rules, which are not defined in the Open Data Challenge for Public Transportation in Tokyo Permission Rules ("Permission Rules"). Developers must read the Permission Rules and API Specification and follow the rules below.

2. Implementation Rules

Developers must observe the following rules.

2.1. Access Token

Do not publish the access token to third parties. When you publish a sample code to a third party in particular, do not include the access token in the code. (Example: Take appropriate action, such as replacing the token with acl:consumerKey=ACL_CONSUMERKEY.)

2.2 Dynamic Data

Dynamic data, such as train location information, train status information, bus location information, and real-time arrival/departure information, change as time goes by. Displaying old information may mislead or confuse application users. To prevent this, observe the following.

2.2.1. Displaying Time
When you show dynamic data or data generated from dynamic data to users, display the data generation time information (dc:date) obtained through the API on the screen.

2.2.2. Displaying Latest Information
When you show dynamic data or data generated from dynamic data to users, display information as latest as possible. To help you display the latest information, an API response includes an update interval and valid range. Update data to be displayed on the screen at a time interval specified in odpt:frequency. Do not use data out of valid range (dct:valid). For dynamic data, do not display out-of-date data, such as data before update.

2.3. Static Data

Static data, which excludes dynamic data such as train location information, train status information, bus location information, and real-time arrival/departure information, may be updated by traffic operators. Displaying old information may mislead or confuse application users. To prevent this, observe the following.

2.3.1. Displaying Obtained Date and Time
When you show static data or data generated from static data to users, display the obtained date and time on an area of the screen where application users can easily access.

2.3.2. Updating Periodically
When you show static data or data generated from static data to users, update the data periodically by obtaining the latest one through the API. Unless otherwise provided in the specific terms of use, the data must be updated within one week after the Public Transportation Open Data Center notifies you of a data update.

2.4. Notification to your users

Please make sure to notify your users of the following when you make available your application(s) that use the data provided for the Open Data Challenge for Public Transportation in Tokyo.

1. The source of the data in this app is the Open Data Challenge for Public Transportation in Tokyo.
2. The accuracy and integrity of the data in this app shall not be guaranteed.
3. Please provide the email address of the developer for inquiries on the app, so your user(s) will not contact the public transportation operators directly.

E.g.
----
The source of the public transportation data in this app, etc. is the Open Data Challenge for Public Transportation in Tokyo.
They are based on the data provided by the public transportation operators. The accuracy and integrity of the data shall not be guaranteed. Please do not contact the public transportation operators directly regarding the content of the app.
For inquiries on the app, please contact the following email address.
[E-mail address of the developer]
----

2.5. Using Logo Images and Railway Line Colors

When you use logo images or railway line colors contained in their respective railway lines, do not modify them unless otherwise provided in the specific terms of use.

2.6. Machine Translation

When you provide machine-translated data, state that machine translation was used on an area of the screen where application users can easily access.

3. Support

For any questions, refer to the documents in the Developers Site first. If you are unable to find an appropriate answer, post your question to the forum in the Developers site. The Secretariat Office will answer the posted question wherever possible. Please refrain from making a direct contact with the public transportation operators.

December 7, 2017