YAMATOMO Operations (hereinafter referred to as "the Company"; the term "the Company" includes its officers, employees, subcontractors, and all other persons who perform work on behalf of the Company) hereby establishes this Privacy Policy (hereinafter referred to as "this Policy") regarding the handling of personal information and other privacy-related information (hereinafter collectively referred to as "Personal Data") of users (hereinafter referred to as "Users"; the term "Users" includes registered users, non-registered users, former users, and persons considering the use of the Service) in connection with the mountain community application "YAMATOMO" (hereinafter referred to as "the Service"; the term "the Service" includes all services, features, content, websites, applications, and all ancillary services related thereto that the Company plans, develops, operates, and provides).
In providing the Service, the Company may collect, use, store, share, transfer, disclose, delete, or otherwise handle (hereinafter collectively referred to as "handle" or "handling") Users' Personal Data. The Company respects Users' privacy and positions the protection of Personal Data as one of its highest management priorities. The Company complies with the Act on the Protection of Personal Information (Act No. 57 of 2003, as amended; hereinafter referred to as the "Personal Information Protection Act"), the Telecommunications Business Act (Act No. 86 of 1984, as amended), and other laws, regulations, guidelines, self-regulatory rules, and other norms related to the protection of personal information (hereinafter collectively referred to as "Applicable Laws"), and handles Personal Data appropriately in accordance with this Policy.
When Users use the Service (including, but not limited to, creating an account for the Service, accessing the Service, using features of the Service, or engaging in any other activities related to the Service), Users shall be deemed to have fully understood and agreed to this Policy. If Users do not agree to this Policy, they may not use the Service.
The Company considers it important that Users fully understand the content of this Policy and consent based on their own free will. If you have any questions about the content of this Policy, please contact us using the contact information provided at the end of this Policy before using the Service.
This Policy sets forth the basic principles governing the Company's handling of Personal Data. In addition to this Policy, the Company may provide separate privacy-related explanations, notices, or obtain consent (hereinafter referred to as "Separate Notices") in connection with specific features, services, or campaigns of the Service. In the event of any conflict or inconsistency between Separate Notices and this Policy, the content of the Separate Notices shall prevail.
This Policy applies to all of the following:
(1) Personal Data that the Company collects, uses, stores, shares, transfers, discloses, deletes, or otherwise handles through the Service (the iOS application "YAMATOMO")
(2) Personal Data that the Company collects, uses, stores, shares, transfers, discloses, deletes, or otherwise handles through websites related to the Service (including corporate sites, landing pages, campaign sites, and other websites operated by the Company)
(3) Personal Data that the Company collects, uses, stores, shares, transfers, discloses, deletes, or otherwise handles through customer support, inquiry responses, and other customer interactions related to the Service
(4) Personal Data that the Company collects, uses, stores, shares, transfers, discloses, deletes, or otherwise handles through marketing activities, advertising activities, events, campaigns, and other promotional activities related to the Service
(5) All other Personal Data that the Company collects, uses, stores, shares, transfers, discloses, deletes, or otherwise handles in connection with the Service
This Policy does not apply to the following:
(1) The handling of Personal Data by third-party services, websites, or applications other than those of the Company (including cases where the Service links to such third-party services)
(2) The handling of Personal Data by other Users within the Service
(3) The handling of Personal Data that the Company has collected for purposes other than the Service
When Users access third-party services, websites, or applications from the Service, the privacy policies and other terms of such third parties shall apply. The Company assumes no responsibility whatsoever for the content of such third parties' privacy policies, the handling of Personal Data by such third parties, or any damages incurred by Users arising from or related to the foregoing.
The Service is, in principle, provided to Users residing in Japan. When Users residing outside of Japan use the Service, the laws of their country of residence may apply. The Company will handle the Personal Data of Users residing outside of Japan appropriately in accordance with this Policy; however, the exercise of rights based on the laws of such Users' countries of residence will be addressed on an individual basis.
The definitions of terms used in this Policy are as set forth below. For terms not defined in this Policy, the definitions in the Personal Information Protection Act and other Applicable Laws shall apply.
"Personal Information" refers to "Personal Information" as defined in Article 2, Paragraph 1 of the Personal Information Protection Act, meaning information relating to a living individual that falls under either of the following:
(1) Information that can identify a specific individual by name, date of birth, address, telephone number, email address, facial photograph, or other descriptions (meaning all matters described or recorded in documents, drawings, or electromagnetic records, or expressed by voice, actions, or other methods) contained therein (including information that can be easily cross-referenced with other information to identify a specific individual)
(2) Information that contains an individual identification code (as defined in Article 2, Paragraph 2 of the Personal Information Protection Act)
"Personal Data" refers to "Personal Data" as defined in Article 16, Paragraph 3 of the Personal Information Protection Act, meaning personal information constituting a personal information database, etc. (as defined in Article 16, Paragraph 1 of the Personal Information Protection Act).
"Retained Personal Data" refers to "Retained Personal Data" as defined in Article 16, Paragraph 4 of the Personal Information Protection Act, meaning personal data over which the Company has the authority to disclose, correct, add to, delete, suspend the use of, erase, and cease third-party provision of.
"Special Care-Required Personal Information" refers to "Special Care-Required Personal Information" as defined in Article 2, Paragraph 3 of the Personal Information Protection Act, meaning personal information that includes descriptions prescribed by Cabinet Order as those requiring special care in handling so as to prevent unjust discrimination, prejudice, or other disadvantage to the individual, such as the individual's race, creed, social status, medical history, criminal record, or the fact of having suffered damage from a crime.
"Pseudonymously Processed Information" refers to "Pseudonymously Processed Information" as defined in Article 2, Paragraph 5 of the Personal Information Protection Act, meaning information relating to an individual obtained by processing personal information so that a specific individual cannot be identified unless cross-referenced with other information, by taking measures prescribed according to the category of personal information.
"Anonymously Processed Information" refers to "Anonymously Processed Information" as defined in Article 2, Paragraph 6 of the Personal Information Protection Act, meaning information relating to an individual obtained by processing personal information so that a specific individual cannot be identified, by taking measures prescribed according to the category of personal information, in such a way that the original personal information cannot be restored.
"Personal Data" as used in this Policy collectively refers to personal information, personal data, retained personal data, special care-required personal information, pseudonymously processed information, anonymously processed information, and even information that does not fall under any of these categories but is related to a specific individual (including, but not limited to, device identifiers, location data, behavioral history, and other information that may be associated with a specific individual).
"Individual" refers to a specific person who is identified by personal information.
"User" refers to any individual who uses the Service, including registered users (persons who have created an account in the Service), non-registered users (persons who use some features of the Service without creating an account), former users, and persons considering the use of the Service.
"Third Party" refers to all persons other than the Company and the User, including other Users, the Company's subcontractors, the Company's group companies, public authorities, and all other corporations, organizations, and individuals.
The Company collects the following Personal Data in providing the Service. The Personal Data collected by the Company is broadly categorized into information provided directly by Users, information automatically collected through the use of the Service, and information obtained from third parties.
When Users create an account for the Service, the Company collects the following information:
| Type of Information | Detailed Description | Required/Optional | Purpose of Collection |
|---|---|---|---|
| Apple ID-Related Information | User identifier, email address (if the User permits sharing), and name (if the User permits sharing) provided by Apple Inc. when creating an account using the Sign in with Apple feature. Users may also use a randomly generated email address to hide their actual email address through Apple Inc.'s feature. | Required (when registering with Apple ID) | Identity authentication, account creation and management, sending important notifications |
| Google Account-Related Information | User identifier, email address, display name, and profile image URL provided by Google LLC when creating an account using the Sign in with Google feature. Google Sign-In uses AppAuth authentication based on the OAuth 2.0 protocol. | Required (when registering with Google account) | Identity authentication, account creation and management, sending important notifications |
| Nickname | A name displayed to other Users within the Service. Users must set a nickname between 2 and 10 characters. It does not need to be the User's real name. | Required | User identification within the Service, communication |
| User ID | A unique identifier automatically assigned by the Company (in ID:XX format). Users cannot set this arbitrarily. | Automatically assigned | User identification, data management |
Users may optionally register the following profile information from the My Page and profile editing screens within the Service. Registration of this information is not mandatory, and Users can use the basic features of the Service without registering it. However, completing profile information may facilitate smoother communication with other Users.
Additionally, Users may change their profile visibility settings (public/private). When the profile is set to "private," basic information such as nickname, User ID, and profile image will continue to be displayed to other Users, but the visibility of detailed profile information will be restricted.
| Type of Information | Detailed Description | Character Limits, etc. | Visibility |
|---|---|---|---|
| Self-Introduction | A free-text description for Users to introduce themselves. It is intended for information such as hiking experience, preferred mountain areas, and hiking style. | Up to 200 characters | Visible to all Users |
| Profile Image | An image for identifying the User. Users may set any image, such as a face photo, hiking photo, or landscape photo. | JPEG format, saved after compression | Visible to all Users |
| Background Image | An image displayed as the background of the profile screen. | JPEG format, saved after compression | Visible to all Users |
| Birth Decade | Information indicating the User's age group. Users select from "1950s," "1960s," "1970s," "1980s," "1990s," "2000s," or "2010s." | Selection-based | Visible to all Users |
| Residential Area | The prefecture where the User resides. Users select from Japan's 47 prefectures. | Selection-based | Visible to all Users |
| Occupation | Information about the User's occupation or job type. | Free text | Visible to all Users |
| School | Information about the school the User attended or is currently attending. | Free text | Visible to all Users |
| Favorite Mountain | The name of a mountain the User particularly likes. | Free text | Visible to all Users |
| Current Interests | Information about hobbies or activities the User is currently interested in. | Free text | Visible to all Users |
| Favorite Quote | A saying or proverb that the User values. | Free text | Visible to all Users |
| Gender | Information about the User's gender. | Selection-based | Visible to all Users |
| Special Skills | Information about skills or abilities the User excels at. | Free text | Visible to all Users |
| External Link 1 | A link to an external website, social media account, blog, etc. operated or used by the User. Set as a combination of a label (display name) and URL. | Label + URL | Visible to all Users |
| External Link 2 | An additional external link similar to the above. Can be set as a second link. | Label + URL | Visible to all Users |
The Company provides a feature for Users to verify their identity. The use of the identity verification feature is entirely optional, and Users can use the basic features of the Service without completing identity verification. Users who have completed identity verification will have a "Verified" badge displayed on their profile, which is expected to enhance their credibility with other Users.
When using the identity verification feature, the Company collects the following information:
| Type of Information | Detailed Description | Special Handling Notes |
|---|---|---|
| Type of ID Document | The type of identification document the User uses for identity verification. Users select from driver's license, passport, My Number Card (Individual Number Card), or other government-issued ID. | Used only for verification purposes |
| ID Document Image | An image of the identification document captured by the User using the camera function. Contains information such as the name, date of birth, address, and photograph printed on the ID document. | Stored encrypted, retained for a set period after verification is completed |
| Facial Photo (Selfie) | A facial photo of the User captured using the camera function. Used for matching against the photograph on the ID document. | Stored encrypted, retained for a set period after verification is completed |
| Verification Result | The result of the identity verification review (approved, rejected, under review) and the date and time of the review. | Stored as account information |
| Rejection Reason | The reason if the identity verification review was rejected. | Stored as reference information for reapplication |
[Important Notes Regarding Identity Verification Information]
The ID document images and facial photos submitted for identity verification are handled with particular care as follows:
(1) This information is used solely for the purpose of conducting identity verification reviews and will not be used for any other purpose.
(2) This information is stored on servers in an encrypted state and is accessible only to authorized personnel with limited access rights.
(3) This information is retained for a set period (as a rule, one year) after the review is completed for the purpose of preventing fraudulent use and handling re-reviews, after which it is deleted using appropriate methods.
(4) This information will not be provided to third parties (except as required by law).
(5) When using a My Number Card, the Company does not collect the My Number (Individual Number) itself and uses only the information necessary for identity verification (name, date of birth, address, and photograph).
The Company provides a feature for Users who hold mountain guide certifications to verify their qualifications. The use of the guide certification feature is entirely optional, and Users can use the basic features of the Service without completing guide certification. Users who have completed guide certification will have a "Guide Certified" badge displayed on their profile.
When using the guide certification feature, the Company collects the following information:
| Type of Information | Detailed Description | Special Handling Notes |
|---|---|---|
| Certification Document Image | An image of the guide certification document captured by the User using the camera function. May contain information such as the type of certification, issuing organization, and expiration date. | Stored encrypted, retained for a set period after review is completed |
| Review Result | The result of the guide certification review (approved, rejected, under review) and the date and time of the review. | Stored as account information |
| Rejection Reason | The reason if the guide certification review was rejected. | Stored as reference information for reapplication |
[Important Notes Regarding Guide Certification Information]
(1) The Company conducts a certain level of verification based on the submitted certification document images; however, it cannot fully verify the authenticity, validity, or currency of the certification.
(2) Guide certification indicates that the Company has reviewed the certification document image and does not guarantee the actual guiding ability, skills, experience, or safety management capabilities of the User.
(3) Certification document images are not used for purposes other than the review process.
When Users create or join communities within the Service, or use any chat features, the Company collects the following information:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Community Creation Information | Information about communities created by Users. Includes community type (companion recruitment, group, event, guide request), title, description, activity schedule, activity location, meeting point, capacity, participation requirements, difficulty level, required equipment, participation fee, and other settings. | Until account deletion |
| Community Participation Information | Information about the list of communities the User has joined, date and time of joining, and participation status (pending approval, approved, withdrawn, etc.). | Until account deletion |
| Community Images | Images posted by Users in connection with communities. Includes community cover images, icon images, reference images, etc. | Until account deletion |
| Mountain Chat Messages | Messages sent by Users in mountain chat rooms for specific mountains on specific dates. Includes text, images (up to 4), thread replies, and reactions (emoji responses). | Until account deletion* |
| DM Messages | One-on-one direct messages with other Users. Includes text and images. | Until account deletion* |
| Group Chat Messages | Messages sent in group chats with multiple participants. Includes text, images, thread replies, and reactions. | Until account deletion* |
| Community Chat Messages | Messages sent in community-dedicated chat rooms. Includes text, images, thread replies, and reactions. | Until account deletion* |
| Shared Community Cards | Community information cards shared within chats. | Until account deletion* |
| Shared User Profiles | User profile cards shared within chats. | Until account deletion* |
| Shared Partner Shop Cards | Partner shop information cards shared within chats. | Until account deletion* |
*Chat messages may remain viewable by other Users participating in the same chat room even after the sender has deleted their account. This is to maintain the context of the chat and ensure the convenience of other Users.
When Users share photos using the album feature of the Service, the Company collects the following information:
| Type of Information | Detailed Description | Storage Location | Restrictions |
|---|---|---|---|
| Album Photos | High-quality photos uploaded by Users through the album feature. Includes mountain landscapes, activity scenes, commemorative photos, etc. | Firebase Cloud Storage | 500MB per day limit |
| Album Metadata | Metadata related to photos. Includes upload date and time, information about the uploading User, associated community information, etc. | Firebase Firestore | - |
| GPX Files | GPX files (GPS Exchange Format) uploaded as hiking routes for communities. Contains location data such as latitude, longitude, and altitude, as well as timestamps. | Firebase Cloud Storage | Maximum 50MB per file |
[About Image Metadata (EXIF Information)] Uploaded photos may contain EXIF information (shooting date and time, location data of the shooting location, camera information, etc.). The Company performs image compression processing but does not guarantee the complete removal of EXIF information. When uploading photos that contain location data, we recommend disabling the addition of location data to photos in your device settings or removing EXIF information before uploading.
When Users review or rate other Users or partner shops, the Company collects the following information:
| Type of Information | Detailed Description | Visibility |
|---|---|---|
| Star Rating | A 1 to 5 star rating for other Users or partner shops. | Visible to all Users |
| Review Comment | A comment accompanying the rating (minimum 10 characters). | Visible to all Users |
| Reviewed Community | Information about the community that was the subject of the review (for user reviews). | Visible to all Users |
| Review Date and Time | The date and time the review was posted. | Visible to all Users |
| Review Reports | Report (complaint) information about reviews. Includes the reason for the report and additional comments. | Private (operators only) |
When Users report other Users, communities, or reviews, the Company collects the following information:
| Type of Information | Detailed Description | Visibility |
|---|---|---|
| Reported Target | Information about the reported User, community, or review. | Private (operators only) |
| Report Reason | The reason for the report (category selection). | Private (operators only) |
| Additional Comments | Additional explanation regarding the report. | Private (operators only) |
| Report Date and Time | The date and time the report was made. | Private (operators only) |
When Users use the AI assistant feature (AI community creation support feature) of the Service, the Company collects the following information:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| User Input Messages | Text messages entered by Users in interactions with the AI assistant. Includes desired conditions for community creation, questions, answers, etc. | Until session ends (temporarily stored on device) |
| AI Responses | Response text generated by the AI assistant based on User input. Includes community description drafts, activity proposals, etc. | Until session ends (temporarily stored on device) |
| AI Usage Count | The number of times a User has used the AI assistant feature per day. Free members are limited to 3 times per day; premium members have additional usage available. | Recorded daily, reset the next day |
| AI Usage Date and Time | The date and time the AI assistant feature was used. | Retained for a set period for usage limit management |
[Important Notes Regarding the AI Assistant Feature]
(1) The AI assistant feature is provided by calling the Claude API provided by Anthropic, PBC (hereinafter referred to as the "AI Service") through Cloud Functions running on the Company's servers. User input messages and conversation history are sent to the AI Service and used to generate AI responses.
(2) Data sent to the AI Service is limited to User input information related to community creation. Users' account information, profile information, location data, and other Personal Data are not directly sent to the AI Service.
(3) Content generated by the AI assistant feature (such as community description drafts) is saved as community information only after Users review and edit it. AI-generated content is never automatically published without User review.
(4) AI usage counts are stored in Firebase Firestore and used for usage limit management.
When Users contact the Company with inquiries, the Company collects the following information:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Inquiry Content | The content of the inquiry entered by the User. | 3 years after inquiry resolution |
| Inquiry Date and Time | The date and time the inquiry was made. | Same as above |
The Company collects location information through the device's GPS function in the following cases. The collection of location information requires the User to grant permission for location services on their device.
(A) Discover Feature (Nearby Yamatomo)
The Company collects current location information through the device's GPS function when Users use the "Discover" feature (Nearby Yamatomo). The collection of location information is essential for using this feature.
| Type of Information | Detailed Description | Collection Conditions | Privacy Protection Measures |
|---|---|---|---|
| GPS Location Information | Latitude and longitude information obtained from the device's GPS function. | Only while the "Discover" tab is displayed | Offset of 50-200m applied |
| Location Acquisition Date and Time | The date and time the location information was acquired. | Same as above | - |
| Location Information Expiration | The expiration time for location information validity. In nearby discovery mode, it is automatically deleted 15 minutes after acquisition; in Mountain Mode, it is automatically deleted 6 hours after acquisition. | Same as above | Automatically deleted after expiration |
(B) Mountain Chat Auto-Join Feature
When the Mountain Chat Auto-Join Feature is enabled (default: ON), the app acquires current location information from the device's GPS function while running in the foreground to detect nearby mountains (within a 5km radius).
| Type of Information | Detailed Description | Collection Conditions | Privacy Protection Measures |
|---|---|---|---|
| GPS Location Information | Latitude and longitude information used to calculate the distance to nearby mountains. | While the app is in the foreground and the feature is enabled | Local processing only; not transmitted to the Company's servers |
| Joined Room IDs | Room IDs of Mountain Chats auto-joined through this feature, stored locally on the device. | Same as above | Automatically reset at midnight JST daily |
[Important Information Regarding the Mountain Chat Auto-Join Feature]
(1) Location information used by the Mountain Chat Auto-Join Feature is not transmitted to the Company's servers, unlike the "Discover" feature. All location processing is completed locally on the device.
(2) Users may disable the Mountain Chat Auto-Join Feature at any time from the settings screen within the Service. When disabled, location information acquisition for this feature is stopped.
For details on the handling of location information, please refer to Article 12 "Handling of Location Data" of this Policy.
The Company may automatically collect the following device and communication information for the provision and improvement of the Service:
| Type of Information | Detailed Description | Purpose of Collection |
|---|---|---|
| FCM Token | A device-specific token issued by Firebase Cloud Messaging (FCM). Used for sending push notifications. | Push notification delivery |
| APNs Device Token | A device-specific token issued by Apple Push Notification service (APNs). | Push notification delivery |
| App Version | Version information of the Service installed by the User. | Service provision, compatibility verification |
| OS Version | iOS version information installed on the User's device. | Service provision, compatibility verification |
| Device Model | Model information of the device used by the User (e.g., iPhone 15 Pro). | Service provision, compatibility verification |
| Language Settings | The language set on the User's device. | Service localization |
| Time Zone | The time zone set on the User's device. | Optimization of date and time display |
The Company collects the following information for the provision of the YAMATOMO Premium Plan and management of free member usage limits:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Subscription Status | Premium plan enrollment status (enrolled/not enrolled). Verified through the StoreKit 2 Transaction API. | Until account deletion |
| Purchase Transaction Information | Transaction ID, purchase date and time, and expiration date for purchases made through the App Store. Obtained through Apple Inc.'s StoreKit framework. | Until account deletion |
| Free Tier Usage Status | Mountain chat participation count, community creation count, community participation count (monthly). Used for managing free member usage limits. | Until account deletion |
Important Notes:
(1) All payment processing is conducted through Apple Inc.'s App Store payment infrastructure (In-App Purchase). The Company does not directly collect or store credit card numbers, bank account information, or other payment method details.
(2) Subscription management (cancellation, stopping automatic renewal, etc.) is handled through Apple Inc.'s system.
(3) Free tier usage status is stored in Firebase Firestore and reset monthly.
The Company uses the services of Stripe, Inc. (hereinafter referred to as "Stripe"), a payment processing service provider, for processing payments for paid community participation fees and providing revenue collection functionality, and collects the following information:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Stripe Customer ID | A unique identifier issued by Stripe for each User. Used for payment processing when joining paid communities. | Until account deletion |
| Stripe Account ID | A Stripe Connect account identifier issued to Users (community creators) who use Stripe Connect to receive community revenue. | Until account deletion |
| Stripe Account Status | The status of the Stripe Connect account (not created, under review, onboarding, active, restricted, disabled). | Until account deletion |
| Payment History | Records of payments made for joining paid communities. Includes payment amount, platform fee (10% of payment amount), payment date and time, payment status (completed, refunded, etc.), and associated community information. | Until account deletion |
| Revenue Receipt History | Records of revenue received by community creators. Includes revenue amount, amount after platform fee deduction, and receipt date and time. | Until account deletion |
Important Notes:
(1) Payment processing for paid communities is conducted through Stripe, Inc.'s payment infrastructure. Credit card numbers, bank account information, and other payment method details are directly collected and stored by Stripe, and the Company does not directly collect or store this information.
(2) Information entered by community creators when creating a Stripe Connect account (name, address, date of birth, bank account information, etc.) is directly collected and managed by Stripe. The Company stores only limited information provided by Stripe, such as account ID and account status.
(3) The platform fee is 10% of the payment amount (minimum payment amount: ¥500; maximum payment amount: ¥500,000).
(4) Refunds for paid community participation fees are available only within 7 days of payment completion. Refund processing is conducted through Stripe.
(5) For information about the handling of personal information by Stripe, Inc., please refer to Stripe's Privacy Policy (https://stripe.com/jp/privacy).
The Company may automatically collect the following usage information to understand how the Service is used and to improve it:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Mountain Chat Participation History | A list of mountain chat rooms the User has joined (combinations of mountain name and date). | Until account deletion |
| Unread Message Count | The number of unread messages in each chat room (mountain chat, DM, group chat, community chat). | Updated in real time |
| Read Status | The date and time of the last read message in each chat room. | Until account deletion |
| Notification History | History of notifications sent to the User. Includes Yamatomo friend requests, community invitations, approval notifications, etc. | Until account deletion |
| Yamatomo List | A list of Users who are in a Yamatomo (friend) relationship with the User. | Until account deletion |
| Yamatomo Request History | History of sent and received Yamatomo requests and approval/rejection history. | Until account deletion |
When Users use the block feature or notification mute feature for other Users, the Company collects the following information:
| Type of Information | Detailed Description | Retention Period |
|---|---|---|
| Block List | A list of other Users blocked by the User. Blocked Users are restricted from sending DMs, and their visibility in search results and within communities is limited. | Until the User removes the block, or until account deletion |
| DM Mute List | A list of DM senders whose notifications the User has muted. When muted, notification banners are not displayed, but messages are still received and badge counts are updated. | Until the User removes the mute, or until account deletion |
| Chat Mute List | A list of mountain chats, group chats, and community chats whose notifications the User has muted. | Until the User removes the mute, or until account deletion |
The Company may automatically collect the following information through Firebase Crashlytics (provided by Google LLC) for the purpose of improving the quality of the Service and fixing defects:
| Type of Information | Detailed Description | Purpose of Collection |
|---|---|---|
| Crash Logs | Technical information when the application terminates unexpectedly. Includes the type of error, location of occurrence, and state at the time of occurrence. | Identifying and fixing defects |
| Stack Traces | Technical information about the program execution path at the time of the crash. | Root cause analysis of defects |
| Device Information | Model name, OS version, app version, etc. of the device on which the crash occurred. | Identifying environment-specific defects |
The Company may automatically collect the following information through Firebase Analytics (provided by Google LLC) for the purpose of improving the Service:
| Type of Information | Detailed Description | Purpose of Collection |
|---|---|---|
| App Launch and Usage Events | Aggregated usage statistics such as app launch counts, session duration, and screen transitions. | Understanding service usage, improvement |
| Aggregated Attribute Information | Attribute information such as the language settings, regional settings, and device category of Users' devices. Not used for the purpose of identifying individuals. | Service optimization |
Data collected by Firebase Analytics is processed as aggregated statistical information and is not used for the purpose of identifying individual Users. For details, please refer to Article 15.3 of this Policy.
The Company sends the following mountain location data to external weather data providers for the provision of the weather information service.
| Type of Information | Detailed Description | Destination | Storage |
|---|---|---|---|
| Mountain Latitude/Longitude | The latitude and longitude information of the mountain for which weather forecasts are obtained. This is information from the mountain database built into the app and is not the User's current location information. | Open-Meteo API (for mountains outside Japan only) | Firestore (temporarily stored as cache, 6-hour TTL) |
| Mountain Elevation | The elevation information of the mountain, sent to improve the accuracy of weather forecasts. | Open-Meteo API (for mountains outside Japan only) | Firestore (temporarily stored as cache, 6-hour TTL) |
| JMA Area Code | The area code used to obtain weather forecasts and weather warnings from the Japan Meteorological Agency for mountains within Japan. | JMA (Japan Meteorological Agency) API | Firestore (temporarily stored as cache, weather forecast 3-hour TTL / warnings 10-minute TTL) |
[Important Notes Regarding Weather Information Service]
(1) The data sent to external APIs in the weather information service consists solely of mountain location information (latitude, longitude, elevation, area code), and Users' personal information, current location information, account information, or other Personal Data is never sent to external APIs.
(2) Retrieved weather forecast data and weather warning data are temporarily stored as cache in Firebase Firestore and are automatically updated after a set period (weather forecasts: 6 hours, JMA weather forecasts: 3 hours, weather warnings: 10 minutes).
(3) Weather information retrieval is performed by Cloud Functions (server-side), and no direct communication from the User's device to external APIs takes place.
When Users create an account using the Sign in with Apple feature, the Company obtains the following information from Apple Inc.:
| Type of Information | Detailed Description | User Control |
|---|---|---|
| User Identifier | A unique user identifier issued by Apple Inc. | Not controllable (required) |
| Email Address | The email address associated with the User's Apple ID. | Can be anonymized with the "Hide My Email" option |
| Name | The name registered to the User's Apple ID. | Can choose whether to share |
When Users create an account using the Sign in with Google feature, the Company obtains the following information from Google LLC based on the OAuth 2.0 protocol:
| Type of Information | Detailed Description | User Control |
|---|---|---|
| User Identifier | A unique user identifier issued by Google LLC. | Not controllable (required) |
| Email Address | The email address associated with the User's Google account. | Not controllable (required) |
| Display Name | The name registered to the User's Google account. | Can be changed in Google account settings |
| Profile Image URL | The URL of the profile image set in the User's Google account. | Can be changed in Google account settings |
The Company does not currently obtain Users' Personal Data from third parties other than those described above. If the Company obtains Personal Data from third parties in the future, this Policy will be revised to provide notice accordingly.
The Company collects Personal Data through the following methods:
Collected through direct input by Users on the Service's account registration screens, profile editing screens, community creation screens, chat input screens, and other input forms.
Collected through Apple Inc.'s system when Users create an account using the Sign in with Apple feature. Apple Inc.'s privacy policy and terms of service also apply.
Collected through Google LLC's OAuth 2.0 authentication system (AppAuth) when Users create an account using the Sign in with Google feature. Google LLC's privacy policy and terms of service also apply.
Collected through the camera function, photo library, GPS function, and other features installed on the User's device. To use these features, Users must grant permission for the Service to access these features in their device settings.
Collected automatically through the technical mechanisms of the Service without explicit User action. This includes the acquisition of FCM tokens, recording of usage data, calculation of unread counts, etc.
Collected through the Firebase SDK (Software Development Kit) integrated into the Service. The Firebase SDK provides database functions, authentication functions, push notification functions, storage functions, analytics functions, crash reporting functions, remote configuration functions, and other capabilities.
The Company uses the collected Personal Data within the scope of the purposes of use set forth below. The Company will not use Personal Data beyond the scope of these purposes of use, except when User consent has been obtained in advance or when permitted by law.
The Company uses Personal Data for the following purposes to provide and operate the Service:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Account Creation and Management | Creating, authenticating, and managing User accounts, and updating account information as necessary. | Account registration information, authentication information |
| Identity Authentication | Verifying that Users are the legitimate account holders. Authentication is performed through Sign in with Apple. | Apple ID-related information |
| Profile Display | Displaying Users' profile information to other Users within the Service. | Profile information |
| Mountain Chat Feature | Providing mountain chat rooms related to specific mountains on specific dates, enabling communication between Users. | Chat information, participation history |
| DM Feature | Providing one-on-one direct messaging functionality between Users. | DM messages |
| Group Chat Feature | Providing group chat functionality with multiple participants. | Group chat messages |
| Community Feature | Providing community creation, participation, management, and community chat functionality. | Community information, community chat messages |
| Discover Feature | Displaying communities that are active near the User's current location. | Location information |
| Mountain Chat Auto-Join Feature | Automatically joining Users to a mountain's daily Mountain Chat when within a 5km radius, and automatically exiting when leaving the area. Location processing is performed locally on the device. | Location information (local processing only) |
| Album Feature | Providing an album feature that allows Users to upload and share photos. | Album photos, metadata |
| Partner Shop Feature | Providing partner shop information and coupons to Users. | Location information (optional) |
| Yamatomo Feature | Providing functionality for building and managing friend relationships (Yamatomo) between Users. | Yamatomo list, request history |
| Review Feature | Providing review and rating functionality between Users and for partner shops. | Review information |
| QR Code Feature | Generating the User's profile information as a QR code, providing functionality for other Users to scan with their camera for direct access to the profile. The QR code encodes a deep link containing the User ID (in yamatomo://user/{userId} format). | User ID |
| Subscription Management | Verifying premium plan enrollment status, managing free tier usage, and applying appropriate feature restrictions. | Subscription information, free tier usage status |
The Company uses Personal Data for the following purposes to conduct identity verification and guide certification:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Identity Verification Review | Conducting identity verification reviews based on ID documents and facial photos submitted by Users. | Identity verification information |
| Identity Verification Badge | Awarding a "Verified" badge to Users who pass the review. | Review result |
| Guide Certification Review | Conducting guide certification reviews based on certification documents submitted by Users. | Guide certification information |
| Guide Certification Badge | Awarding a "Guide Certified" badge to Users who pass the review. | Review result |
| Impersonation Prevention | Preventing the creation of accounts impersonating other individuals. | Identity verification information |
| Re-review Handling | Handling re-reviews when identity verification or guide certification has been rejected. | Identity verification information, guide certification information, rejection reason |
The Company uses Personal Data for the following purposes to send notifications and communications to Users:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Push Notification Delivery | Sending notifications for new messages, Yamatomo requests, community invitations, and other notifications to Users' devices. | FCM token, APNs device token |
| Important Announcements | Notifying Users of important service changes, terms of service revisions, privacy policy revisions, and other important matters. | Email address (if set), push notifications |
| Maintenance Information | Notifying Users of planned maintenance or service interruptions. | Push notifications |
| Inquiry Response | Communicating as necessary to respond to User inquiries. | Email address, account information |
The Company uses Personal Data for the following purposes to improve and develop the Service:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Usage Analysis | Analyzing how the Service is being used and identifying areas for improvement. | Usage information (after anonymization) |
| New Feature Development | Developing new features and services based on User needs. | Usage information (after anonymization) |
| User Experience Enhancement | Improving the user interface, performance, and usability of the Service. | Usage information (after anonymization) |
| Bug Fixing | Identifying and fixing defects in the Service. | Device information, usage information |
The Company uses Personal Data for the following purposes to provide the AI assistant feature:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| AI Community Creation Support | Based on User input, the AI assistant generates community description drafts, activity proposals, etc. User input messages and conversation history are sent to the AI Service to generate responses. | User input messages, conversation history |
| Usage Count Management | Managing the usage count of the AI assistant feature and applying the daily usage limit (3 times) for free members. | AI usage count, AI usage date and time |
The Company uses Personal Data for the following purposes to ensure the safety of the Service:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Fraud Prevention and Detection | Preventing and detecting fraudulent use of the Service (impersonation, spam, fraudulent activities, etc.). | Account information, usage information |
| Terms of Service Violation Response | Identifying actions that violate the terms of service and taking appropriate measures. | Chat information, community information |
| Review Report Response | Reviewing problematic reviews reported by Users and taking appropriate measures. | Review information, report information |
| Account Security | Protecting User accounts from unauthorized access. | Authentication information |
The Company may use Personal Data for the following purposes to fulfill legal obligations:
| Purpose of Use | Detailed Description | Information Used |
|---|---|---|
| Response to Legal Requests | Responding to inquiries based on law from courts, prosecutors' offices, police, and other public authorities. | Personal Data to the extent necessary |
| Response to Legal Proceedings | Responding to litigation, arbitration, mediation, and other legal proceedings. | Personal Data to the extent necessary |
| Exercise and Defense of Rights | Exercising the Company's legal rights or defending against legal claims. | Personal Data to the extent necessary |
Due to the nature of the Service, some Personal Data is disclosed to other Users. The following shows the information disclosed and the scope of disclosure:
| Type of Information | Disclosure Scope | Purpose of Disclosure | User Control |
|---|---|---|---|
| Nickname | All Users | User identification, communication | Can be changed |
| User ID | All Users | User identification | Cannot be changed |
| Profile Image | All Users | User identification | Can be deleted |
| Self-Introduction | All Users | Self-introduction | Can be deleted |
| Detailed Profile Information | All Users | Self-introduction, matching | Each item can be deleted |
| Identity Verification Badge | All Users | Display of trustworthiness | Identity verification application is optional |
| Guide Certification Badge | All Users | Display of certification status | Guide certification application is optional |
| Reviews and Ratings | All Users | Trustworthiness assessment | Reviews are posted by others |
| Yamatomo Count | All Users | Display of activity status | No hide option |
| Joined Communities | All Users | Display of activity status | Depends on community visibility settings |
| Chat Messages | Participants in the same chat room | Communication | No deletion feature after sending |
| Location Information (with offset applied) | Nearby Users using the "Discover" feature | Safety feature | Not collected unless the feature is used |
[Important] Users should understand that providing profile information is optional and should not enter information they do not wish to make public. Once information is made public, it may be saved by other Users through screenshots or similar means, and the Company cannot completely prevent such actions. Users can limit the visibility of detailed profile information by changing their profile visibility settings (public/private). However, basic information such as nickname, User ID, and profile image will remain visible to other Users regardless of the setting.
The Company will not provide Users' personal data to third parties except in the following cases:
When Users have given explicit consent to the provision of personal data to third parties, the Company may provide personal data to third parties within the scope of such consent.
The Company may provide personal data to the following authorities when disclosure is required by law:
(1) Courts: When responding to inquiries, orders, etc. based on the Code of Civil Procedure, the Code of Criminal Procedure, or other laws
(2) Prosecutors' Offices: When responding to inquiries, etc. based on the Code of Criminal Procedure or other laws
(3) Police: When responding to inquiries, etc. based on the Code of Criminal Procedure or other laws
(4) Bar Associations: When responding to inquiries, etc. based on Article 23-2 of the Attorney Act
(5) Other Public Authorities: When responding to inquiries, etc. based on law from tax offices, labor standards inspection offices, the Japan Fair Trade Commission, the Consumer Affairs Agency, and other administrative agencies
When the provision of personal data is necessary for the protection of life, body, or property of a person in situations such as distress, missing persons, the need for emergency medical treatment, and other situations, and it is difficult to obtain the consent of the individual, the Company may provide personal data to the following organizations:
(1) Police: When cooperating with search and rescue operations for distressed or missing persons
(2) Fire Departments: When cooperating with emergency medical and rescue operations
(3) Japan Coast Guard: When cooperating with maritime search and rescue operations
(4) Medical Institutions: When providing information necessary for emergency medical treatment
(5) Other Rescue Organizations: When cooperating with mountain rescue teams, helicopter rescue operations, etc.
The Company outsources part of the operations necessary for providing the Service to external business operators and provides personal data to such subcontractors to the extent necessary for the outsourced operations.
| Subcontractor | Description of Outsourced Operations | Information Provided | Country | Security Measures |
|---|---|---|---|---|
| Firebase (Google LLC) | Cloud infrastructure provision, database service (Firestore), user authentication service (Firebase Authentication), cloud storage service (Cloud Storage), push notification delivery service (Cloud Messaging) | Account information, profile information, chat information, location information, album photos, and all other data handled by the Service | United States | SOC 1/2/3, ISO 27001, ISO 27017, ISO 27018 certified, data encryption, access control |
| Apple Inc. | Push notification delivery service (Apple Push Notification service), user authentication service (Sign in with Apple), in-app purchase service (App Store In-App Purchase) | APNs device token, Apple ID-related information, subscription purchase information | United States | ISO 27001, ISO 27018 certified, data encryption |
| Firebase Crashlytics (Google LLC) | App crash report collection and analysis service | Crash logs, device information (model name, OS version), app version, stack traces at the time of crash | United States | SOC 1/2/3, ISO 27001 certified, data encryption, access control |
| Firebase Analytics (Google LLC) | App usage statistical analysis service | Aggregated usage statistics such as app launch counts, session duration, screen transitions, and device attribute information. Does not include information that identifies individuals. | United States | SOC 1/2/3, ISO 27001 certified, data encryption, access control |
| Firebase Remote Config (Google LLC) | Dynamic management service for app feature settings (such as premium plan feature restrictions) | Configuration value delivery only. No User personal information is collected. | United States | SOC 1/2/3, ISO 27001 certified |
| Google LLC (Google Sign-In) | OAuth 2.0-based user authentication service (Sign in with Google) | Google account user identifier, email address, display name, profile image URL | United States | SOC 1/2/3, ISO 27001, ISO 27017, ISO 27018 certified, data encryption, access control |
| Gmail SMTP (Google LLC) | Processing and delivery service for emails received through the contact form | Inquiry content, email address (if set) | United States | SOC 1/2/3, ISO 27001 certified, data encryption, access control |
| Anthropic, PBC (AI Service Provider) | Provision of AI model API (Claude API) for the AI assistant feature (AI community creation support) | Text messages and conversation history entered by Users in the AI assistant feature. Users' account information, profile information, and other Personal Data are not sent. | United States | SOC 2 certified, data encryption, access control, input data not used for training (per API terms of service) |
| Stripe, Inc. | Payment processing service for paid communities (Stripe Payments), revenue collection service for community creators (Stripe Connect) | Stripe Customer ID, Stripe Account ID, payment amount, payment status, platform fee information. Credit card numbers, bank account information, and other payment method details are directly collected and managed by Stripe and are not provided to the Company. | United States | PCI DSS Level 1 certified, SOC 1/2 certified, data encryption, access control |
| Open-Meteo GmbH | Provision of weather data API (Open-Meteo API) for the weather information service (for mountains outside Japan only) | Mountain latitude, longitude, and elevation information only. Users' personal information, account information, or other Personal Data is not sent. | Switzerland (Europe) | HTTPS/TLS encrypted communication, no transmission of personal data, open-source API |
| Japan Meteorological Agency (JMA) | Retrieval of weather forecast and weather warning data as the sole data source for mountains within Japan for the weather information service | JMA area codes only. Users' personal information, account information, or other Personal Data is not sent. | Japan | Public data from a government agency, HTTPS/TLS encrypted communication, no transmission of personal data |
The Company has entered into agreements with these subcontractors regarding the handling of personal data, requiring the following obligations:
(1) Not to use personal data for purposes other than the outsourced operations
(2) Not to provide personal data to third parties (including in the case of sub-outsourcing)
(3) To implement appropriate security measures
(4) To return or delete personal data upon completion of the outsourced operations
(5) To cooperate with audits by the Company
If the Company succeeds its business to a third party due to merger, company split, business transfer, or other reasons, the Company may provide personal data associated with such business to the third party. In such cases, the Company will take measures to ensure that the successor handles personal data appropriately.
In connection with the partner shop feature of the Service, the Company does not directly provide Users' personal data to partner shops. However, the following information may be provided to partner shops as statistical information:
| Information Provided | Detailed Description | Possibility of Individual Identification |
|---|---|---|
| Coupon Usage Count | Statistics on the number of times a specific partner shop's coupons have been used. | Not identifiable |
| User Attribute Distribution | Statistical distribution of attributes such as age group and region of Users who have used coupons. | Not identifiable |
| Page Views | Statistics on the number of times the partner shop page has been viewed. | Not identifiable |
| Review Content | Content of reviews posted by Users for the partner shop (published together with the User's nickname). | Identifiable by nickname |
This statistical information (excluding review content) has been processed so that individuals cannot be identified and does not constitute personal data.
In providing the Service, the Company uses servers operated by its subcontractors Firebase (Google LLC), Apple Inc., and Stripe, Inc., and these servers are located in the United States of America. Therefore, Users' Personal Data is transferred to and handled in the United States of America.
Additionally, in providing the weather information service, the Company uses the API of Open-Meteo GmbH (Switzerland). However, the data sent to the Open-Meteo API consists solely of mountain latitude, longitude, and elevation information, and Users' personal information is not sent.
The transfer of Personal Data to the United States of America is based on the following legal grounds:
(1) User consent has been obtained pursuant to Article 28, Paragraph 1 of the Personal Information Protection Act (by consenting to this Policy, Users are deemed to have consented to the international transfer of Personal Data)
(2) The subcontractors Google LLC, Apple Inc., and Stripe, Inc. have implemented appropriate measures for the protection of personal data
Google LLC, Apple Inc., and Stripe, Inc. have implemented the following protective measures:
(1) Obtained international security certifications such as SOC 1/2/3, ISO 27001, ISO 27017, and ISO 27018
(2) Implemented technical security measures such as data encryption, access control, and log management
(3) Entered into agreements with the Company regarding the handling of personal data
The Company stores Users' Personal Data on cloud servers provided by Firebase (Google LLC), a subcontractor of the Company. Specifically, the following services are used:
| Service | Purpose | Data Center Location |
|---|---|---|
| Firebase Firestore | Storage of account information, profile information, chat information, and other structured data | United States |
| Firebase Cloud Storage | Storage of large files such as album photos, identity verification document images, and guide certification document images | United States |
| Firebase Authentication | Storage of user authentication information | United States |
The Company implements the following security measures to prevent the leakage, loss, or damage of Personal Data:
(1) Communication Encryption: Communications between the Service and servers are encrypted using TLS (Transport Layer Security).
(2) Stored Data Encryption: Data stored on servers is encrypted using industry-standard encryption algorithms such as AES-256.
(3) Access Control: Access to Personal Data is limited to the scope necessary for business operations and is controlled through appropriate authentication and authorization mechanisms.
(4) Security Rules: Firebase Firestore security rules ensure that Users can only access their own data and cannot access other Users' data except as permitted.
(5) Image Data Compression and Protection: Images of identity verification documents and guide certification documents are compressed and stored in an encrypted state.
(6) App Attest: In the production environment, Apple Inc.'s App Attest technology is used to verify that requests originate from the legitimate application. This protects User data from tampered applications and unauthorized requests.
(1) Access Rights Management: Personnel who can access Personal Data are limited, and access rights are reviewed regularly.
(2) Employee Training: Employees who handle Personal Data receive regular security training.
(3) Incident Response Plan: An incident response plan has been established in preparation for security incidents.
While the Company strives to protect Personal Data to the best of its ability, the Company does not guarantee the following:
(1) That the Service is completely secure
(2) That leakage, loss, or damage of Personal Data will never occur
(3) That unauthorized access or cyberattacks by third parties can be completely prevented
In the event of a leakage, loss, damage, or other security incident involving Personal Data (hereinafter referred to as "Data Breach"), the Company will take the following actions:
(1) Notification: Within 72 hours of becoming aware of the Data Breach, the Company will notify affected Users through in-app notifications, email, or other appropriate means.
(2) Notification Content: Notifications will include the following information to the extent possible:
(3) Reporting to Authorities: When reporting to the Personal Information Protection Commission or other supervisory authorities is required under the Personal Information Protection Act or other laws, the Company will promptly file such reports.
(4) Prevention of Recurrence: The Company will investigate the cause of the Data Breach and implement measures to prevent recurrence.
The Company retains Personal Data only for the period necessary to achieve the purposes of use. The following shows the retention periods for major categories of Personal Data:
| Type of Information | Retention Period | Basis for Retention Period |
|---|---|---|
| Account Registration Information | Until account deletion | Period necessary for service provision |
| Profile Information | Until account deletion | Period necessary for service provision |
| Chat Messages | May partially remain after account deletion | For maintaining chat context |
| Album Photos | Until account deletion | Period necessary for service provision |
| Identity Verification Information (review documents) | 1 year after review completion | For fraud prevention and re-review handling |
| Guide Certification Information (review documents) | 1 year after review completion | For fraud prevention and re-review handling |
| Location Information | 15 minutes after acquisition | For privacy protection |
| Notification History | Until account deletion | Period necessary for service provision |
| Inquiry Information | 3 years after inquiry resolution | For maintaining response records |
| Report Information | 3 years after resolution | For maintaining response records |
| Subscription Information / Free Tier Usage Status | Until account deletion | Period necessary for service provision |
| Stripe Payment History | Until account deletion | Period necessary for service provision and accounting |
| AI Usage Count | Recorded daily, reset the next day | For usage limit management |
| Block / Mute Lists | Until the User removes the setting, or until account deletion | For maintaining User settings |
| Crash Reports | 90 days after collection (Firebase Crashlytics standard retention period) | For identifying and fixing defects |
When retention is required by law, the Company will retain Personal Data for the period prescribed by such law.
Personal Data for which the retention period has expired will be deleted or anonymized using appropriate methods.
When a User deletes their account, chat messages (including messages in mountain chats, DMs, group chats, and community chats) are handled as follows:
(1) Removal of Profile Information: The deleted User's profile photo and profile name will be replaced with a display such as "Deleted User" in chats, and the original profile information will be deleted.
(2) Retention of Messages: To maintain the context of chats and ensure the convenience of other Users, the text of messages sent by the deleted User may be retained.
(3) Anonymization: One year after account deletion, any remaining messages will be anonymized so that the identity of the sender cannot be determined.
(4) Deletion Request: Even after account deletion, the former User may request the Company to delete their chat messages. However, please note that immediate deletion of all messages may be technically difficult due to the need to maintain chat context.
Under the Personal Information Protection Act, Users have the following rights regarding their retained personal data held by the Company:
Users may request the Company to disclose their retained personal data held by the Company.
When the content of the User's retained personal data held by the Company is not factually accurate, Users may request the Company to correct, add to, or delete such retained personal data.
When the Company is handling the User's retained personal data beyond the scope necessary to achieve the purposes of use, or when it was obtained through deception or other improper means, Users may request the Company to suspend the use of or erase such retained personal data.
When the Company is providing the User's retained personal data to third parties without the User's consent, Users may request the Company to cease the provision of such retained personal data to third parties.
To exercise the above rights, please contact us using the contact information provided at the end of this Policy. When exercising your rights, you may be asked to submit prescribed documents for identity verification purposes.
Users can manage the following data within the Service:
(1) Editing and Deleting Profile Information: Users can edit or delete their profile information from My Page.
(2) Changing Profile Visibility Settings (Public/Private): Users can change their profile visibility settings from My Page. When set to private, the visibility of detailed profile information is restricted.
(3) Managing Block and Mute Settings: Users can manage blocking of specific Users and notification mute settings for various chats.
(4) Account Deletion: Users can delete their account from the settings screen. Upon account deletion, the User's Personal Data held by the Company will be deleted after the retention period specified in this Policy has expired.
(1) The Company does not engage in automated decision-making (including profiling) that produces legal effects concerning Users or similarly significantly affects them.
(2) Decisions regarding identity verification, guide certification, content moderation, and similar matters are made based on human review.
(3) However, the management of free member usage limits (free tier) is performed automatically by the system. This automated processing is applied uniformly to all free members and is not based on individual profiling.
(4) The AI assistant feature of the Service generates content (such as community description drafts) based on information input by Users and does not perform profiling based on Users' past behavioral history or profile information. Content generated by AI is used only after Users review and edit it, and AI output does not automatically produce legal effects concerning Users or similarly significantly affect them.
The Company collects Users' location information in the following cases. The collection of location information requires the User to grant permission for location services on their device.
(1) When the "Discover" feature (Nearby Yamatomo) is used
(2) When the Mountain Chat Auto-Join Feature is enabled (default: ON) and the app is running in the foreground
Collected location information is used only for the following purposes:
(1) To display communities that are active near the User's current location in the "Discover" feature
(2) To enable contact with nearby Users or communities in case of emergency
(3) To detect whether the User is within a 5km radius of a mountain and automatically join them to the corresponding Mountain Chat through the Mountain Chat Auto-Join Feature
(A) Discover Feature Protection Measures
The Company applies the following offset processing to location information to protect Users' privacy:
(1) Offset Range: A random offset of approximately 50 to 200 meters is added to the precise location information collected. As a result, the location displayed to other Users differs from the actual location.
(2) Expiration: The expiration of location information varies depending on the mode used. In "nearby discovery mode," the information is automatically deleted 15 minutes after acquisition; in "Mountain Mode," it is automatically deleted 6 hours after acquisition.
(3) Collection Timing: Location information is collected only while the "Discover" tab is displayed and is not collected on other screens.
(4) Update Interval: Location information is updated at approximately 30-second intervals. This provides location information with reasonable accuracy while conserving battery consumption.
(B) Mountain Chat Auto-Join Feature Protection Measures
(1) Local Processing: All location information processing for the Mountain Chat Auto-Join Feature is performed locally on the User's device and is not transmitted to the Company's servers.
(2) Foreground Only: Location information is acquired only while the app is running in the foreground. Location information is not acquired while the app is in the background or terminated.
(3) User Control: Users may disable the Mountain Chat Auto-Join Feature at any time from the settings screen within the Service. When disabled, location information acquisition for this feature is immediately stopped.
(4) Daily Reset: Locally stored room IDs of auto-joined Mountain Chats are automatically reset at midnight Japan Standard Time (JST) each day.
(1) The offset processing does not guarantee complete concealment of the User's precise location.
(2) By using the "Discover" feature, the User's approximate location will be displayed to other Users. If privacy is a concern, please refrain from using the "Discover" feature.
(3) To stop the collection of location information, please disable location access for the Service in your device settings. To stop only the Mountain Chat Auto-Join Feature, you may disable the feature from the settings screen within the Service, which allows you to continue using the "Discover" feature while stopping auto-join only.
(4) If location information collection is not permitted, the "Discover" feature and the Mountain Chat Auto-Join Feature will not be available. However, manual participation in Mountain Chats remains possible.
When using the identity verification feature, the Company collects the following information:
(1) Type of ID document (driver's license, passport, My Number Card, other)
(2) Image of the ID document (Base64 encoded, after compression processing)
(3) Facial photo (selfie) image (Base64 encoded, after compression processing)
Collected identity verification information is used only for the following purposes:
(1) To conduct identity verification reviews
(2) To prevent impersonation
(3) To handle re-reviews
Identity verification information (ID document images and facial photos) is retained for one year after the review is completed and then deleted using appropriate methods. However, review results (approved/rejected) and rejection reasons are stored as account information.
Identity verification information is rigorously protected through the following methods:
(1) Image data is compressed and limited to a maximum of 700KB
(2) Stored in an encrypted state in Firestore
(3) Accessible only to authorized personnel with limited access rights
When a My Number Card is used for identity verification, the Company does not collect the My Number (Individual Number) itself. Only the name, date of birth, address, and photograph printed on the My Number Card are used for identity verification.
When using the guide certification feature, the Company collects the following information:
(1) Image of the guide certification document (Base64 encoded, after compression processing)
Collected guide certification information is used only for the following purposes:
(1) To conduct guide certification reviews
(2) To handle re-reviews
Guide certification information (certification document images) is retained for one year after the review is completed and then deleted using appropriate methods. However, review results (approved/rejected) and rejection reasons are stored as account information.
(1) The Company cannot fully verify the authenticity, validity, or currency of the submitted certification documents.
(2) Guide certification indicates that the Company has reviewed the certification document image and does not guarantee the actual guiding ability, skills, experience, or safety management capabilities of the User.
(3) Even when requesting guide services from a user with guide certification, Users must verify the guide's ability and reliability at their own responsibility.
Since the Service is an iOS application, it does not directly use cookies commonly used on websites.
The Service uses the following technologies to identify Users and provide the Service:
(1) Firebase Authentication: Authentication tokens are used to maintain the User's authentication state.
(2) FCM Token: Device-specific tokens are used for sending push notifications.
(3) Local Storage (UserDefaults): App settings, coupon usage status caches, and other information are stored in the device's local storage (UserDefaults).
(4) Keychain: Security-sensitive information such as FCM tokens is stored in iOS Keychain (encrypted secure storage).
(5) Image Cache: To improve display speed, downloaded images are temporarily stored in a memory cache (up to 100 images) and a disk cache (up to 50MB, with a 7-day expiration).
(6) Firebase Remote Config: Firebase Remote Config (provided by Google LLC) is used to dynamically manage service feature settings (such as premium plan feature restrictions). Remote Config is a mechanism that delivers server-side configured values to the app and does not collect User personal information.
(7) Deep Links (Custom URL Scheme): The Service uses a custom URL scheme yamatomo:// to provide functionality for directly navigating to specific screens such as User profiles when reading QR codes or linking between apps. Deep links contain User IDs for identifying the destination, but the URLs themselves are not stored on the Company's servers.
The Company has adopted the following policies regarding the handling of Users' Personal Data:
(1) Prohibition of Data Sales: The Company does not sell Users' Personal Data to third parties.
(2) No Use of Advertising SDKs: The Service does not use third-party advertising SDKs or ad networks. Users' behavioral data is not transmitted to third parties for advertising purposes.
(3) Analytics Tools: The Company uses Firebase Analytics (provided by Google LLC) for the purpose of improving the Service. Data collected by Firebase Analytics is processed as aggregated statistical information and is not used for the purpose of identifying individual Users.
(4) Statistical Information for Partner Shops: Information provided to partner shops is limited to the statistical information specified in Article 7.3 and does not include information that can identify individuals.
The Service uses the Sign in with Apple feature provided by Apple Inc. for account creation and authentication. When using this feature, Apple Inc.'s privacy policy applies.
The Service uses the Sign in with Google feature (OAuth 2.0-based AppAuth authentication) provided by Google LLC for account creation and authentication. When using this feature, Google LLC's privacy policy (https://policies.google.com/privacy) applies. For details on the information obtained through Google Sign-In, please refer to Article 4.3.2 of this Policy.
The Service uses the Firebase platform provided by Google LLC to deliver services. Google LLC's privacy policy applies to the use of Firebase.
The Service uses payment services (Stripe Payments, Stripe Connect) provided by Stripe, Inc. for processing payments for paid communities and providing revenue collection functionality to community creators. When processing payments for joining paid communities and creating/managing Stripe Connect accounts, Stripe, Inc.'s privacy policy (https://stripe.com/jp/privacy) and terms of service apply. The Company does not have access to credit card numbers, bank account information, or other payment method details collected and managed by Stripe.
The AI assistant feature of the Service uses the Claude API provided by Anthropic, PBC. When using the AI assistant feature, text messages and conversation history entered by Users are sent to Anthropic, PBC's servers. Anthropic, PBC guarantees, under its API terms of service, that submitted data will not be used for AI model training. For details on the handling of data by Anthropic, PBC, please refer to their privacy policy (https://www.anthropic.com/privacy).
The Service uses the following external weather data providers for the provision of the weather information service.
(1) Open-Meteo (Open-Meteo GmbH)
The Open-Meteo API is used to obtain weather forecast data for mountains outside Japan. The Open-Meteo API is not used for mountains within Japan. The data sent to the Open-Meteo API consists solely of mountain latitude, longitude, and elevation information, and Users' personal information is never sent. Open-Meteo GmbH is located in Switzerland, and the API it provides is published as open source.
(2) Japan Meteorological Agency (JMA)
As the sole data source for mountains within Japan, the data API published by the Japan Meteorological Agency is used to obtain weather forecast data and weather warning/advisory data. The data sent to the JMA API consists solely of JMA area codes, and Users' personal information is never sent. The use of JMA data is subject to the terms of use of the Japan Meteorological Agency website.
When Users click on external links set in profiles or shared within chats, the privacy policies of those external sites apply. The Company assumes no responsibility whatsoever for the handling of Personal Data on external sites.
The Service may be used by minors; however, minors should obtain the consent of their legal guardian (parent, etc.) before using the Service.
When a minor uses the Service, the Company shall deem that the consent of the legal guardian has been obtained.
Legal guardians may exercise the rights set forth in Article 11 of this Policy on behalf of minors.
(1) The Service is not intended for children under the age of 13, and the Company does not intentionally collect personal information from children under 13.
(2) If the Company becomes aware that it has collected personal information from a child under 13, the Company will promptly delete such information.
(3) If you are a parent or guardian who is aware that a child under 13 is using the Service, please contact us through the following methods:
The Company may change this Policy as necessary due to changes in laws, changes in service content, or other reasons.
When making material changes to this Policy, the Company will notify Users of the changes through in-app announcements, push notifications, posting on the Company's website, or other methods the Company deems appropriate.
The revised Policy shall take effect from the effective date specified by the Company. If Users continue to use the Service after the effective date, they shall be deemed to have agreed to the revised Policy.
This Policy shall be governed by and construed in accordance with the laws of Japan.
In the event of any dispute arising between a User and the Company in connection with this Policy, the Tokyo District Court shall have exclusive jurisdiction as the court of first instance.
For inquiries regarding this Policy or requests for disclosure of retained personal data, please use the following method:
[How to Contact Us]
Please contact us through the "Contact Us" form within the Service.
[Operator Information]
YAMATOMO Operations
The Company will review the content of inquiries and, as a rule, respond by email or through in-app notifications. Depending on the nature of the inquiry, a certain period of time may be required to respond.
This Policy shall take effect on January 23, 2026.
| Version | Revision Date | Summary of Revisions |
|---|---|---|
| 1.0 | January 23, 2026 | Initial version established |
| 1.1 | January 30, 2026 | Added Article 14 "Handling of Guide Certification Information"; added provisions regarding partner shop review feature |
| 1.2 | February 1, 2026 | Added subscription and billing information to Article 4; added provisions regarding YAMATOMO Premium |
| 1.3 | February 9, 2026 | Added Section 9.4 "Response to Data Breaches," Section 10.4 "Handling of Chat Messages After Account Deletion," Section 11.4 "Automated Decision-Making and Profiling," and Section 15.3 "Analytics and Data Monetization"; added Firebase Crashlytics to subcontractor table in Section 7.2.4; added Section 17.4 "Children Under 13" |
| 1.4 | February 24, 2026 | [Major Additions] Added Section 4.2.4 "Stripe Payment Information"; added Google account authentication information to Section 4.1.1; added Section 4.3.2 "Information Obtained from Google LLC (Google Sign-In)"; added Section 4.1.9 "AI Assistant Usage Information"; added Section 6.5 "Provision of the AI Assistant Feature." [Moderate Additions] Added gender information and profile public/private settings to Section 4.1.2; added Section 4.2.6 "Block and Mute Information"; added Section 4.2.7 "Crash Report Information"; added Section 4.2.8 "Analytics Information"; added GPX file and EXIF information handling to Section 4.1.6; added QR code feature provisions. [Subcontractor Additions] Added Stripe, Inc., AI Service Provider, Firebase Analytics, Firebase Remote Config, Google LLC (Google Sign-In), and Gmail SMTP to Section 7.2.4. [External Service Integration Additions] Added Section 16.2 "Google Sign-In," Section 16.4 "Stripe," and Section 16.5 "AI Service." [Other] Added Mountain Mode (6-hour) location information provisions; added App Attest provisions to Section 9.2.1; added Keychain, image cache, Remote Config, and deep link provisions to Section 15.2; added Stripe payment history, AI usage count, block list, and crash report to retention period table in Article 10; added clarification on the relationship between AI features and automated decision-making to Section 11.4 |
| 1.5 | February 28, 2026 | Added Section 4.2.9 "Weather Information Service Data" (disclosure of data sent to Open-Meteo API and JMA API); added Section 16.6 "Weather Information Service (Open-Meteo / JMA)"; added Open-Meteo GmbH and Japan Meteorological Agency (JMA) to the subcontractor table in Section 7.2.4; added Open-Meteo (Switzerland) data transfer to Section 8.1; revised Section 2.3 to clarify international user access and multilingual support (7 languages); added country selection for international users to residential area in Section 4.1.2 |
| 1.6 | March 1, 2026 | Updated weather information service data source architecture: Limited Open-Meteo API destination to mountains outside Japan only in Section 4.2.9, changed weather warning cache TTL from 30 minutes to 10 minutes, limited Open-Meteo usage to mountains outside Japan in Section 16.6(1), designated JMA as sole data source for Japanese mountains in Section 16.6(2) |
| 2.0 | March 19, 2026 | Added Mountain Chat Auto-Join Feature location data to Section 4.2.1; added Mountain Chat Auto-Join Feature row to Section 6.1 usage purpose table; updated Section 12 to cover both Discover feature and Mountain Chat Auto-Join Feature (split 12.3 into (A) Discover and (B) Auto-Join protection measures, added auto-join purpose to 12.2, updated 12.4 notes) |
YAMATOMO Operations
The Japanese version of this Privacy Policy shall be the authoritative text.
End of Document
