Privacy Policy
This translation is provided for reference only. If it differs from the Japanese version, the Japanese version prevails.
YOTEMY (hereinafter referred to as "we" or "us") will appropriately handle, in accordance with the Act on the Protection of Personal Information (個人情報の保護に関する法律; hereinafter referred to as the "APPI") and other relevant laws, regulations and guidelines, the personal information as defined in the APPI that is included in the information concerning persons who use the services we operate (hereinafter referred to as the "Service") (such persons hereinafter referred to as "you") and that we acquire in connection with the Service.
This Privacy Policy (hereinafter referred to as this "Policy") sets out how we acquire personal information, for what purposes we use it, how we manage it, in what cases we provide it to third parties, and how we respond to requests for disclosure, etc.
Article 1 Scope of Application of this Policy
This Policy applies to all services provided by us. The scope of information actually acquired by each individual service shall be limited to the extent necessary in light of the content of the Service, and the specific details thereof will be made clear in the terms of use or information page of the relevant service.
Article 2 Information We Acquire
1. Information You Provide to Us Directly
The information that you enter when using the Service, and the information that we receive in connection with your operations, includes the following.
- Name, email address and other registration information
- Information used to identify accounts
- The usage status of the Service, times of operations, frequency of use of features, time taken to respond to notifications, and other usage logs
- Identifiers necessary for delivering push notifications (such as FCM tokens)
- Schedules, setting values and other data on your device required for the functions of the Service
- Location information (latitude and longitude measured by GPS or other means) and information regarding travel
- The content of inquiries and other information you have communicated to us
- Other information necessary for providing, operating or improving the Service
2. Information Received via External Services or Third Parties
We receive the following information from external services whose linkage you have authorized, or from such external services or other third parties.
- Channel information, tokens and other authentication-related information necessary for linkage with supported calendar services (meaning Google Calendar, iCloud Calendar and other calendar services that we indicate as supported for linkage), map and route search services, and other external services
- Schedules, locations and other related information acquired through linkage with external services
- Other information acquired within the scope of the linkage you have authorized
3. Acquisition of Location Information (Including Acquisition in the Background)
The Service acquires location information even while the Service's app is not running (in the background) only if you have selected "Allow all the time" in your device's location permission settings.
The purposes of acquiring location information in the background are limited to the following three.
- Detecting that you have departed
- Recalculating the time required for travel
- Confirming that you have arrived at your destination
We do not acquire or use location information in the background for any purpose other than these three. We do not use acquired location information for delivering advertisements or measuring the effectiveness of advertisements, nor do we sell it to third parties.
You may at any time change the location permission from your device settings to "Allow only while using the app" or "Don't allow." In this case, the countdown will not be updated and arrival will not be detected while the app is not running.
4. Step Count and Device Motion (Morning Alarm)
Only if you turn on the morning alarm, the Service reads the step count and device motion from your device's step counter (Motion & Fitness on iOS) to check whether you have moved away from where you slept after the alarm rings.
The step count and device motion are used on your device solely to dismiss the morning alarm and are not sent to our servers. Records of the decision, such as the time the alarm rang and the time it was dismissed, are stored on your device for troubleshooting, but they are not sent outside your device unless you export them using the "Export this device's status" feature.
You can revoke the Physical activity permission (Motion & Fitness on iOS) at any time in your device settings. In that case, the morning alarm stops when you tap Dismiss.
Article 3 Form in Which Information Is Stored
1. We may store part of the information described in the preceding Article in a form linked to you personally, or in a form not directly linked to you personally.
2. When storing information in a form not directly linked to you personally, we will manage it so that no information that can directly identify you is attached to it.
Article 4 Purposes of Use
1. We use acquired information within the scope of the following purposes.
(1) For providing, operating and running the Service (including determining departure, calculating travel time, measuring actual travel segments, detecting arrival and delivering notifications)
(2) For authenticating users, delivering notifications and responding to inquiries
(3) For understanding usage status, statistical analysis, quality enhancement, feature improvement and addressing defects
(4) For ensuring security, preventing unauthorized use and responding to failures
(5) For improving the Service and for research
2. With respect to item (5) of the preceding paragraph, we process the travel data and behavioral data we have acquired (including places of departure, places of arrival, time taken for travel, means of transportation, operation history and other similar information) into a form not directly linked to you personally, and then use such data for improving the Service and for analysis and research concerning time management, travel or cognitive characteristics. Such analysis and research are conducted for the purpose of enhancing the functions and improving the quality of the Service.
3. We use names, email addresses, information used to identify accounts, usage logs, information used for delivering notifications, information regarding linkage with external services, data on devices, location information and travel data to the extent necessary to achieve the purposes set forth in paragraph 1.
Article 5 Provision to Third Parties
1. We will not provide your personal information to third parties except in the following cases.
(1) Where we have obtained your prior consent
(2) Where the provision is based on laws and regulations
(3) Where we entrust the handling of personal information to a third party in order to achieve the purposes of use
(4) Where it is necessary for the protection of the life, body or property of a person and it is difficult to obtain your consent
(5) Where we receive a formal inquiry based on law from a court, the police or another public authority and respond to it
(6) Where we provide anonymized or statistical data to research institutions or other third parties
2. We may provide to third parties, for the purpose of improving the Service or for research, data that has been processed so that you cannot be directly identified, out of the information set forth in Articles 2 and 4. In such case, we will appropriately manage such data so that no information that would make it possible to identify individuals again is attached to it.
Article 6 Outsourcing of Operations
1. We outsource to external business operators all or part of the provision, operation, maintenance and analysis of the Service, the delivery of notifications, the display of maps, route searches, linkage with calendars, the operation of cloud infrastructure, and other operations necessary for the Service.
2. When outsourcing, we will thoroughly examine the suitability of the contractor, stipulate confidentiality obligations, the handling of personal information and other necessary matters in the contract, and carry out necessary and appropriate supervision to ensure that information is properly managed by the contractor.
Article 7 Security Control Measures
With respect to personal data that we have acquired or plan to acquire, we take necessary and appropriate measures to prevent leakage, loss or damage and otherwise to manage such data securely. An outline of these measures is as follows.
1. Organizational Measures
We establish internal rules on the handling of personal data, and check the status of handling, manage access rights, and establish systems for reporting and responding to incidents, among other things.
2. Human Measures
We provide necessary and appropriate supervision over persons who handle personal data and provide them with education on proper handling.
3. Physical Measures
We appropriately manage equipment, documents and recording media used to handle personal data, and take measures to prevent theft, loss, destruction, unauthorized removal and the like.
4. Technical Measures
We take access control for personal data, measures against unauthorized access, encryption of communications and other necessary and appropriate technical measures.
5. Understanding the External Environment
When we handle personal data in a foreign country, or use servers or external services located in a foreign country, we take necessary and appropriate measures after understanding the systems for the protection of personal information and other necessary aspects of the external environment in that foreign country (as of the establishment of this Policy, the United States).
Article 8 Response to Requests for Disclosure, etc.
1. If the person concerned makes a request under the APPI for disclosure, correction, addition, deletion, suspension of use, erasure or cessation of provision to third parties (hereinafter collectively referred to as "Disclosure, etc.") with respect to personal data held by us, we will respond without delay in accordance with verification of identity and other procedures prescribed by us.
2. The preceding paragraph does not apply where we are permitted under the APPI or other laws and regulations not to comply with such request.
3. The procedures, documents to be submitted and other details required for requests for Disclosure, etc. will be provided by the method prescribed by us. Please submit requests to the contact point set forth in Article 11.
4. The specific procedures for deleting your account and data are summarized on the "Account and Data Deletion" page.
Article 9 Use by Persons Under 16
1. The Service is not intended for use by persons under 16 years of age. If a person under 16 uses the Service, please do so after obtaining the consent of a person with parental authority or other legal representative.
2. If we confirm use by a person under 16, we will take appropriate measures regarding the personal information acquired, except where retention is required by law or in other cases we deem necessary.
Article 10 Revision of this Policy
1. We may revise this Policy as necessary, including in response to amendments to laws and regulations or changes in the content or operation of the Service.
2. If we revise this Policy, we will notify you of the revised content by a method we deem appropriate.
Article 11 Contact Point for Inquiries
Please direct inquiries regarding this Policy and our handling of personal information to the following contact point.
Our name and address are published on the "Notation Based on the Act on Specified Commercial Transactions (特定商取引法)" page of this website, and we will also respond without delay if you request them from the contact point above.
Please note that, depending on the content of your inquiry, it may take up to approximately 7 business days for us to respond.
Article 12 Information Transmitted from Your Device to External Parties (Matters Published Pursuant to the External Transmission Rules)
We use external services provided by third parties for the provision, operation and quality enhancement of the Service and the analysis of its usage status. Accordingly, information may be transmitted from your device to the providers of such external services. The information transmitted, etc. is as follows.
| Service name | Service provider | Information transmitted | Our purpose of use | Service provider's purpose of use |
|---|---|---|---|---|
| Firebase Crashlytics | Google LLC | App instance ID, stack traces at the time of crashes, device information, app version, date and time of crashes | To identify and fix the causes of defects in the app | Same as above. Firebase Privacy and Security / Google Privacy Policy |
| Linkage with supported calendar services (Google Calendar) | Google LLC | Authentication information (such as access tokens), request information necessary for retrieving and synchronizing schedules, and the content of schedules you have created or edited in the app (when writing is performed) | To import schedules from your calendar and display and manage them in the Service, and to reflect in your calendar the schedules you have created or edited in the app | Provision of calendar services by Google. Google Privacy Policy |
| Map and route search services | NAVITIME JAPAN Co., Ltd. (NAVITIME API), Google LLC (Routes API), Val Laboratory Corporation (Ekispert API) | Location information of the departure and arrival points, means of transportation, search time | To obtain estimates of routes and travel times | Provision, maintenance and improvement of services by each provider |
| Voice input and AI reading (natural language processing services) | Google LLC | ・Content you have input by voice, device information ・Only if you set "Read with AI" in the app to "Use", the following: Text you type when adding schedules or tasks Images you capture to read schedules and tasks (Android: screens and paper you capture; iOS: paper you photograph and images you choose) Titles of tasks linked to a schedule, and their estimated time Titles of travel schedules (schedules containing words such as "Shinkansen" or "flight") Location information is not transmitted. If you set "Read with AI" to "Don't use", the information above that is sent only when set to "Use" is not transmitted, and reading is done on your device only. You can change "Read with AI" at any time in the app's settings. |
To read dates, times, places, details, durations, the train or flight you will take, and similar details from the text and images you provide, and to help you register schedules and tasks We do not store this information on our servers. Images you capture are not saved to your device's photos and are deleted from your device once reading is finished. |
Provision of services by Google (including abuse monitoring). The information transmitted is not used to train AI models (under the terms of Google Cloud's Vertex AI). Google Privacy Policy |
| Yotemy research data collection (transmission of anonymous travel records) | YOTEMY (us) *Google LLC (Google Cloud / Firebase) is entrusted as the storage infrastructure | An anonymous token generated on the device, records of travel segments (departure and arrival stations/points, time required, means of transportation, time of day), and device information. These are not linked to user IDs such as Google accounts | To create statistics for improving the accuracy of travel time predictions, and for research on developmental characteristics and time perception | Provision of infrastructure only within the scope of the entrustment. Firebase Privacy and Security |
| Yotemy behavior log (anonymous) | YOTEMY (us) *Google LLC (Google Cloud / Firebase) is entrusted as the storage infrastructure | A pseudonymous token generated on the device, and app usage logs. Specifically: the time at which a departure confirmation operation was performed and the stage at that time, the time at which travel was detected, the time taken for travel, the approximate distance from the reference point, the urgency level, the means of transportation, the day of the week and time of day, the time from registering a schedule to its start, the settings items changed and their values before and after the change, operations on screens and widgets, how far you progressed through each initial setup screen, whether features such as notifications, widgets, overlay display and calendar linkage are enabled, calendar synchronization failures and re-authentication requests, and the days on which the app was launched. Usage status of the task feature (that a suggestion was shown and its type, the category of a task, ranges of the estimated and actual time required, whether the deadline was met (as a range), ranges of the length of free time, and ranges of the time from the end of a schedule to an operation). These are not linked to user IDs such as Google accounts. Raw text such as titles, notes and place names of schedules and tasks, deadline dates, and location information are not transmitted as part of this log. | To understand usage status by feature and to make decisions on notification design and feature improvements, and to improve the quality of the Service | Provision of infrastructure only within the scope of the entrustment. Firebase Privacy and Security |
| Delivery of updates to your Yotemy device (iOS) | YOTEMY (us) ※Delivery infrastructure outsourced to Google LLC (Firebase Cloud Messaging) | Identifiers required to deliver push notifications, an on-device number for each event, the times at which to wake the device, the times at which to start and to change the Live Activity display, the display stage at that time (e.g. preparing, on the way), and fixed notification phrases shown when the display changes (e.g. "Time to begin preparing"). Start times are sent only for events beginning within the next 24 hours. Event titles, place names and location information are not sent. Wake-up times are deleted after the device is woken; information about when to start the Live Activity is deleted once the display has started or is no longer needed (for example, because the event changed); information about the Live Activity display is deleted after the display ends (at the latest about 8 hours after it starts). Identifiers required to deliver push notifications are deleted once we confirm they are no longer valid as a delivery destination. | To keep the remaining time until departure up to date even while the app is not running | Provision of delivery infrastructure only, within the scope of the outsourcing. Firebase Privacy and Security |
| RevenueCat (upon launch of paid plans) | RevenueCat, Inc. (United States) | Billing management ID generated in the app, device information, purchase, cancellation and renewal status, receipt information | To determine and restore the purchase status of paid plans, and to carry it over when you change devices | Provision of services and fraud prevention by RevenueCat. RevenueCat Privacy Policy |
Article 13 Handling of Google User Data
1. If you have authorized linkage with your Google account, the Service handles information in your Google Calendar (hereinafter referred to as "Google User Data") through Google APIs. The scope of permissions (scopes) we request is as follows.
- https://www.googleapis.com/auth/calendar.events
1. Reading
We read the start time, end time, title and location of your schedules, calculate backward the departure time necessary to be in time for each schedule, and then display the countdown and deliver notifications. We read the location field of schedules for the purpose of estimating the time required for travel.
2. Writing
We write to your Google Calendar only when reflecting in your Google Calendar the schedules that you have created or edited in the Service's app. We do not change the content of, or delete, schedules that you have not created or edited in the Service's app.
3. Scope of Use
We use Google User Data only to the extent necessary to provide the functions of the Service, among the purposes set forth in Article 4, paragraph 1. We do not use Google User Data for delivering advertisements or measuring the effectiveness of advertisements, and do not sell it to third parties. In addition, our personnel do not view Google User Data except where we have obtained your explicit consent, for security purposes, where necessary to comply with laws and regulations, or where the data is processed into a form that cannot identify individuals and aggregated.
4. Revoking Linkage
You may revoke the Service's access rights at any time from the permissions management page of your Google account (https://myaccount.google.com/permissions).
5. Compliance with the Google API Services User Data Policy
The Service's use of information received from Google APIs and its transfer to other apps will comply with the Google API Services User Data Policy, including the Limited Use requirements.
Yotemy's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Article 14 Retention Period of Information
1. We retain acquired information only for the period necessary to achieve the purposes of use set forth in Article 4, and after that period has elapsed, we delete it without delay or process it into a form that cannot identify individuals. However, where retention is required by law, we retain such information for the period prescribed by such law.
2. The retention periods for the main types of information are as follows.
- Location information (latitude and longitude): For detecting departure, recalculating travel time and confirming arrival, we store the following points in the database on your device, namely: the coordinates of the destination, the point used as the reference for travel, the point at which departure was detected, and the point at which a stay was confirmed upon arrival. Because these are stored as information for each schedule, they are deleted together with the schedule information after the relevant schedule ends.
- Actual measurement records of travel segments: For the purpose of improving the accuracy of travel time estimates, we store the coordinates of the start and end points of the segments traveled and the time required in the database on your device. Because these records are not linked to schedules, they are not erased when schedules are deleted; they are deleted together with the database on your device when you delete the Service's app from your device.
- Transmission to our servers: We do not transmit latitude and longitude themselves to our servers. What we transmit to our servers is limited to values that do not identify a specific point, such as mesh codes that coarsely divide areas, codes identifying groups of stations, times of passage or travel, means of transportation, time taken for travel, and the approximate accuracy of positioning. Note that, for searching routes and travel times, we transmit the latitude and longitude of the departure and arrival points to the providers of the map and route search services listed in Article 12.
- Schedule information acquired from calendars: Stored in the database on your device and automatically deleted after the relevant schedule ends (or, if arrival cannot be confirmed, after a certain grace period has elapsed). At the time of deletion, only the name and address of the destination and the means of transportation continue to be stored, for the purpose of improving the accuracy of subsequent travel time estimates. Schedule titles and dates and times are not stored.
- Results of route and travel time searches: These expire and are deleted 6 hours after acquisition.
- Registration information and information used to identify accounts: Retained while the account exists, and deleted from our servers through the "Delete account" operation in the app.
- Behavior logs ("Yotemy behavior log (anonymous)" in Article 12): Stored on our servers. They are not linked to your Google account and are grouped only by a pseudonymous token held by your device. When you perform the "Delete account" operation in the app, your device communicates that token to us, and we delete the corresponding behavior logs. If you delete the app from your device first, we have no means of knowing that token and therefore cannot individually delete the behavior logs. Even in this case, you cannot be identified from such logs.
- Research data processed into a form not directly linked to you personally: Because we do not hold any means of linking such data to you personally, we cannot individually delete it. Please acknowledge this in advance.
3. You may request deletion of stored information through the contact point set forth in Article 11. Our response in such case is governed by Article 8.
Established: August 12, 2026
Revised: August 17, 2026
Revised: October 14, 2026
Revised: October 16, 2026
Revised: October 17, 2026
Revised: October 22, 2026
Revised: October 28, 2026