Sign in with Apple(連携を含む):Apple が本アプリ向けに発行するユーザー識別子、Apple から提供されるメールアドレス(「メールを非公開」を選んだ場合は Apple の転送用アドレス)、氏名(最初の認証時にあなたが提供した場合のみ。認証基盤のユーザー情報に保存しますが、アプリ内では表示・利用しません)。Apple ID のパスワードを当方が受け取ることはありません。
「共通の足あと」の共有をオンにした場合に限り、訪れた内蔵の名所(アプリに収録された公開の名所)の ID 一覧も友だちと共有され、ふたりとも訪れた場所の表示に使われます。初期設定はオフで、マイページからいつでも変更できます。自分で登録した場所、現在地、写真、メモは共有されません。
最近行ったところ:公開をオンにした場合に限り(初期設定はオフ)、最近記録した内蔵の名所のうち最大 30 件の ID と訪れた日付(日のみ)を当方のサーバーに保存し、互いに友だちになっている相手だけが閲覧できます。自分で登録した場所、場所の検索で追加した場所、現在地や座標、時刻、メモ、写真は共有されません。設定は結縁帳とマイページから変更でき、オフにするとサーバー上の公開データはすぐに削除されます。
あなたが相手の QR コードを読み取ると、相手の「結縁のお誘い」一覧に、あなたのプロフィール名と眷属が表示されます。
ログインしていて、アプリ内の説明を確認のうえ同意した場合に限り(かつ機能が提供されている場合に限り)、眷属との会話に AI を使います。同意しない場合、ゲストの場合、利用回数を使い切った場合、オフラインの場合などは、端末内の定型の応答に切り替わり、何も送信されません。
Apple アカウントの連携:不正利用(無料の利用回数の大量取得)を防ぐため、当方が定める日付より後に作成されたアカウントでは、AI 旅のおともの利用に Apple アカウントの連携(Sign in with Apple)が必要な場合があります。この判定には、アカウントの作成日時と Apple 連携の有無のみを使います。連携が必要な場合、メッセージは OpenAI に送信されず、利用回数も減りません。
送信する情報:入力したメッセージ(500 文字まで)と同じ会話の直近 12 件、一緒にいる眷属とあなたが付けた呼び名・絆の段階、言語、端末の日付、ホームの国(日本/台湾)、記録数、訪れた都道府県・地域名、最近訪れた内蔵名所の ID(最大 60 件)、よく記録する分類・地域の上位件数、進行中または予定の旅のタイトル・日程・国・状態、会話中の行程案。旅の画面から相談した場合は、その旅のタイトル・日程・国と各立ち寄り先(名所 ID または名前、何日目、時刻、滞在時間)。
Sign in with Apple を使っているアカウント(Apple を連携したアカウントを含む)では、削除の前に Apple の認証画面がもう一度表示され、当方のサーバーを通じて、本アプリに対する Sign in with Apple の認可の取り消しを Apple に依頼します。この取り消しは可能な範囲で行うもので、認証画面を閉じた場合や取り消しに失敗した場合もアカウントは削除されます。その場合は、iPhone の「設定」→ Apple アカウント →「サインインとセキュリティ」→「Apple でサインイン」から、本アプリの使用を停止できます。
建立帳號與登入:新帳號只能以「使用 Apple 登入」(Sign in with Apple)建立。先前以電子郵件建立的帳號,仍可用電子郵件與密碼登入,也可以在「我的」頁連結 Apple 帳號。
我們取得的資訊:建立帳號時分配的使用者 ID(隨機識別碼),以及依登入方式而定的下列資訊。
使用 Apple 登入(含連結):Apple 為本 App 發給的使用者識別碼、Apple 提供的電子郵件地址(若你選擇「隱藏我的電子郵件」,則為 Apple 的轉寄地址)、姓名(僅限第一次授權時你有提供;存於認證服務的使用者資訊中,App 內不會顯示或使用)。我們不會取得你的 Apple ID 密碼。
最近去過的地方:只有在你開啟公開時(預設為關閉),我們才會把你最近記錄的內建景點中最多 30 個的 ID 與造訪日期(只有日期)存到我們的伺服器,且只有互為好友的人能看到。自建地點、透過地點搜尋加入的地點、目前位置或座標、時刻、筆記、照片都不會分享。可在結緣帳與「我的」頁變更;關閉後,伺服器上的公開資料會立即刪除。
傳送對象:經由我們的伺服器(Supabase,東京區域)傳送至 OpenAI 的 API(美國)以產生回覆。傳給 OpenAI 的不是使用者 ID 本身,而是由使用者 ID 產生的單向雜湊值,用於協助偵測濫用。為了產生回覆,我們的伺服器可能會查詢公開景點資料,並以景點座標查詢天氣(MET Norway)。規劃行程時,可能會用 AI 產生的搜尋詞進行地點搜尋(第 12 節),並以搜尋結果(公開地圖資料)產生回覆。
OpenAI 的處理:依 OpenAI 的 API 資料政策,傳送至 API 的資料預設不會用於訓練 OpenAI 的模型,並可能為濫用監控保留最多 30 天。我們的請求設定為不在 OpenAI 端儲存回應。
使用「使用 Apple 登入」的帳號(含已連結 Apple 的帳號),刪除前會再出現一次 Apple 驗證畫面,並透過我們的伺服器請 Apple 撤銷本 App 的「使用 Apple 登入」授權。撤銷會盡力進行;即使你關閉驗證畫面或撤銷失敗,帳號仍會被刪除。此時可到 iPhone「設定」→ 你的 Apple 帳號 →「登入與安全性」→「使用 Apple 登入」停止本 App 的使用。
This policy explains what information the developer of the iOS app "Haretabi (晴れ旅)" (the "App"; "we", "us") handles, why, and where.
If you use the App without an account (as a guest), your records stay on your device only and are not sent to our server.
Your records are backed up to the cloud only if you create an account. New accounts are created with Sign in with Apple (Section 3).
Photos (the images themselves) are never uploaded to the cloud.
We do not show ads, use analytics, or track you, and we do not sell personal information.
You can delete your account in the App at any time (Section 16).
2. Using the App without an account (guest)
Your records, photos, notes, trip plans, companion progress and settings are all stored on your device (the App's database and documents folder) and are not sent to our server.
Features that need an account (cloud backup/restore, friends ("kizuna"), shared trips, the AI travel companion, sharing community routes) are not available. Guests can still browse shared community routes (Section 5).
Even as a guest, the App connects to the external services listed in Sections 12 and 6 for maps, weather, app settings, place search, app updates and purchases. To count how many people use the App, it also sends an anonymous "opened today" record to our server once a day (Section 13).
Deleting the App deletes all data on the device. We cannot restore a guest's data.
3. Account and cloud backup
Creating an account is optional.
Creating an account and signing in: new accounts can be created only with Sign in with Apple. Accounts created earlier with an email address can still sign in with their email address and password, and can link an Apple Account on My Page.
What we collect: a user ID assigned when the account is created (a random identifier), plus the following, depending on how you sign in.
Sign in with Apple (including linking): the user identifier Apple issues for the App; the email address Apple provides (an Apple private relay address if you choose "Hide My Email"); and your name, only if you share it the first time you authorize (stored in the authentication service's user information; not shown or used in the App). We never receive your Apple Account password.
Email accounts: your email address and your password (stored hashed by the authentication service; we cannot see it in plain text).
What is backed up: visit records (date and time, season and weather, companions, notes, fields you filled in); places you registered yourself (name, category, region, coordinates; "register a new place" uses your current location's coordinates); places you added from place search (name, coordinates, type, address); goshuin book, goshuin and souvenir records (notes, prices, etc.; not the images themselves); wishes; titles; trips (title, dates, country, budget, note); itineraries; packing lists; trip diaries; bookings (name, confirmation number, date and time, place, address, note); expenses (amount, currency, category, note, names of who paid and who shares the cost); your want-to-go list; companion progress, outfits and nicknames; your profile name; the friend cards saved in your kizuna book; and other game progress.
What is not sent to the cloud: the images of photos, goshuin and souvenirs; your AI chat history; step counts; per-device settings such as notifications, sound and display; the location stored in your photos.
Purpose: backup, restoring your data (e.g. when you change phones), and providing the features described in this policy.
Where: Supabase, the cloud database and authentication service we use; data is stored in the Tokyo, Japan region.
Retention: kept while your account exists. Records you delete in the App are marked as deleted in the cloud and are never restored; they are permanently erased during our periodic cleanup or, at the latest, when you delete your account.
Signing out: the cloud backup and the data on your device both remain.
Technical logs: for operation, abuse prevention and troubleshooting, Supabase may record technical logs such as IP address, access time and app/device information for a short period (according to its retention settings).
4. Friends (kizuna)
You add a friend by scanning each other's friend-card QR code with the camera. The QR code contains your profile name, current companion, bond level, outfit, number of cleared regions, number of records, an on-device identifier and, when signed in, your user ID. Anyone you show the QR code to can read this information.
When you are signed in, your card information (profile name, companion, bond level, outfit, cleared regions, record count) is stored on our server and can be viewed only by mutual friends.
Only if you turn on "shared footprints" is the list of IDs of built-in places you have visited (public places included in the App) shared with friends, to show places you have both visited. It is off by default and can be changed at any time on My Page. Places you registered yourself, your current location, photos and notes are never shared.
Recently visited: only if you turn on sharing (it is off by default), we store on our server the IDs of up to 30 built-in places you recorded most recently, with the visit dates (date only), and only mutual friends can see them. Places you registered yourself, places added from place search, your location or coordinates, times, notes and photos are never shared. You can change this in the kizuna book and on My Page; turning it off deletes the shared data on our server immediately.
When you scan someone's QR code, your profile name and companion appear in that person's list of friend invitations.
To prevent abuse (mass friend-adding), we record when friend links are made.
You can remove or block a friend from the kizuna book. Once removed, mutual viewing stops immediately.
Retention: friend links, card information, blocks, these records and your shared "recently visited" data are deleted when you delete your account.
5. Shared trips, sending itineraries, community routes, and PDF
Shared trips (plan together)
Signed-in users can share a trip and edit it together. When you share a trip, the following is stored on our server (Supabase) and visible to all members of that trip (including view-only members): trip title, dates and country; itinerary (names of places/stops, times, length of stay, notes, completion status; built-in places use their public coordinates); packing list; shared expense ledger (amount, currency, category, note, who paid and who shares the cost); shared bookings (name, confirmation number, date and time, place, address, note); members' profile names, companions and roles; and records of who changed what and when.
The trip's overall note is not uploaded. Places you registered yourself as free records are shared by name only, never with coordinates. Places you add to the itinerary with “Drop a pin on the map” are shared with all members of that trip, including their name, coordinates and note, and members who can edit may change them. Places you added from place search are shared with their name and coordinates from public map data (OpenStreetMap).
Changes are delivered to other members' devices in real time.
Anyone who has an invite code or link (valid by default for 72 hours and up to 5 uses) can join the trip, and can see the trip title and the inviter's profile name and companion before joining. Please share invite codes only with people you trust.
You can also invite a mutual friend to a trip from the kizuna book. Only the invited person can see and accept this invitation, which shows the trip's title and dates and the inviter's profile name and companion. The inviter can cancel it. Invitations expire after 14 days, and expired invitations are deleted periodically.
Retention and deletion: a shared trip is kept until the organizer deletes it or no members remain. Expenses and bookings deleted within a trip are marked as deleted and permanently erased when the trip is deleted. If you leave a trip or delete your account while other members remain, the content you added stays as part of the trip, no longer linked to your name.
Sending an itinerary (link, QR code, text code)
This converts an itinerary and packing list into a link, QR code or text code that you send by a method you choose (such as a messaging app). It does not pass through our server. It contains no records, photos, expenses or companions; places you registered yourself are included by name only.
Community routes (shared routes)
While the feature is offered, signed-in users can share a trip as a public route. The following then becomes visible to users of the App (including guests): the places (guide spots built into the App and public places chosen through place search) with their names, locations, order, day and suggested length of stay; the number of days, country and area; the options picked from the menus when sharing (trip style, who with, pace, getting around, season, cover and highlight stops); when the route was shared and updated; and the like and "used" counts.
Places you registered yourself, photos, notes, expenses, bookings, companions, and the trip's title and dates are never shared. There are no free-text fields. For pins you dropped on the map, the name and location are never shared; you can choose to share only a purpose picked from a menu (such as a meal or lodging) and the prefecture or county, as an open slot (if you don't choose, the pin isn't shared).
The author's name (profile name) is shown only to people who are mutual friends with them in the kizuna book; everyone else sees "Traveler". Account IDs are never shown to other users (the server keeps them to allow editing, deletion and rate limits).
Your likes and "used" records are also stored on our server; activity logs used for rate limits are deleted after 7 days.
You can stop sharing at any time (the route and its likes and "used" records are deleted). Copies that others already added to their own trips stay on their devices.
We may remove routes that we judge to violate the law or the purpose of the service without notice.
Trip book (PDF)
PDFs are created on your device. You choose where to share them.
6. Purchases
In-app purchases are processed by Apple. We never receive your credit card number or other payment details.
We use RevenueCat (RevenueCat, Inc., USA) to manage purchases. RevenueCat receives a user identifier used by the App (our user ID when you are signed in; a random anonymous ID for guests), purchase information such as products, transaction IDs, dates and prices, and technical information needed for processing, such as device, OS and app version, and country/region.
For purchases made while signed in, we also record the product ID, transaction ID, displayed price and time on our server, for customer support and to prevent duplicate grants.
"Soudan-fuda" (extra AI companion turns) are granted by our server after it checks your purchases with RevenueCat; we record your balance and its history (including transaction IDs).
We keep records of compensation granted through customer support, and of redeem-code use (when signed in: a hash of the code and the time).
Retention: purchase, grant and redemption records on our server are deleted when you delete your account. Transaction records held by Apple and RevenueCat are kept according to their policies and legal requirements (e.g. accounting and tax). To request deletion of your RevenueCat record, please contact us (Section 21).
7. AI travel companion
AI is used in chats with your companion only if you are signed in and have agreed after reading the in-app explanation (and only while the feature is offered). If you have not agreed, are a guest, have used up your turns, or are offline, the App switches to built-in on-device replies and sends nothing.
Linking an Apple Account: to prevent abuse (mass collection of free turns), accounts created after a date we set may need a linked Apple Account (Sign in with Apple) to use the AI travel companion. This check uses only the account's creation time and whether Apple is linked. When linking is required, your message is not sent to OpenAI and no turns are used.
What is sent: your message (up to 500 characters) and the last 12 messages of the same conversation; your current companion, the name you gave it and its bond level; language; the device date; your home country (Japan/Taiwan); your record count; names of prefectures/regions you have visited; IDs of built-in places you visited recently (up to 60); your top categories and regions (counts); the title, dates, country and status of your current or upcoming trip; and the itinerary draft under discussion. When you ask from a trip's page, also that trip's title, dates and country and each stop (place ID or name, day, time, length of stay).
What is not sent: your email, password, photos, goshuin, notes/impressions, companions' names, expenses, bookings, wishes, the names and coordinates of places you registered yourself, your current location, or device identifiers.
Where it goes: through our server (Supabase, Tokyo region) to OpenAI's API (USA) to generate replies. OpenAI receives not your user ID but a one-way hash derived from it, to help detect abuse. To reply, our server may look up public place data and fetch weather for a place's coordinates (MET Norway). When planning an itinerary, it may run a place search (Section 12) with search terms written by the AI and use the results (public map data) in its reply.
At OpenAI: under OpenAI's API data-usage policy, data sent to the API is not used to train OpenAI's models by default and may be retained for up to 30 days for abuse monitoring. We send requests with response storage at OpenAI turned off.
Storage: chat history is stored only on your device (the latest 50 messages per conversation, up to 5 conversations) and is not included in the cloud backup. Our server does not store chat content; it records only usage counts, token counts, cost, the number of off-topic refusals, and your soudan-fuda balance and history, which are deleted with your account. Our server logs do not contain message content either.
You can withdraw consent or delete chat history on My Page at any time.
Please do not enter information that identifies you or others. AI replies may be inaccurate.
8. Location
We ask only for "While Using the App" location permission. Location is never collected in the background.
Purposes: showing nearby places and your position on the map, checking distance at check-in, the coordinates of a place you register, and fetching weather.
We never send your current location itself to our server. However, when you are signed in, the coordinates of places you registered at your current location are backed up to the cloud as part of your records (Section 3).
Place search: the coordinate used to rank search results by distance is derived from the places in your trip (its itinerary, destination or recorded places), not from your current location (Section 12).
Weather: coordinates rounded to two decimal places (roughly 1 km) are sent to MET Norway, with nothing that identifies you. If location permission is not granted, a representative point for your home country (Tokyo/Taipei) is used.
The main features work without location permission.
9. Photos and camera
Camera: for taking photos of goshuin and memories, and for scanning friend-card and trip-invite QR codes.
Photo library: for attaching photos you choose to your records. Photos are copied into the App and stored only on your device.
Automatic photo matching: when you use this feature, the App reads the capture date/time and location of photos in your library on the device, matches them with your records and shows candidates. This information and the photos are never sent off the device. Only the photos you add to a record are copied into the App.
When you save a trip card or trip-book image to your photo library, the App asks for permission to save.
Photos are not backed up to the cloud. When you change phones, photos remain on the original device.
10. Steps and motion
The App uses your device's pedometer (Motion & Fitness) data to show step counts and for in-game features (such as remote visits using distance walked). Step data is processed and stored only on your device and is never sent off the device.
11. Notifications, widgets and Live Activities
All notifications are local notifications scheduled on your device. We do not use push notifications and do not obtain push tokens. You can turn notifications off at any time.
Home Screen widgets and Live Activities show step counts, your companion, days until your next trip, your next destination, and similar information. This data is passed only within your device (a storage area shared by the App and its widgets). Note that it may also appear on your Lock Screen.
12. Connections to external services (including guests)
Maps: map tiles are loaded from OpenFreeMap. Normal connection information such as your IP address and the map area being displayed are sent.
Weather: rounded coordinates are sent to MET Norway (the Norwegian Meteorological Institute) (Section 8).
App settings: a settings file describing which features are available is loaded from GitHub Pages (GitHub, Inc.). Only normal connection information such as your IP address is sent.
App updates: app updates are loaded from Expo (EAS Update). The app version, device type, a random identifier generated by the update mechanism, and connection information such as your IP address may be sent.
External websites: links such as "Official website" and "Wikipedia" on place pages open in an in-app browser; the privacy policy of that website applies.
Directions: "How to get there" passes the coordinates of the destination (and of the starting place) to Google Maps (app or web); Google's privacy policy applies from there.
We do not send your email address or user ID in these connections (other than to Supabase, RevenueCat and OpenAI as described in Sections 3–7 and under place search in this section).
13. Ads, analytics and tracking
We do not use any advertising, analytics or crash-reporting SDKs.
Usage count: once on each day you open the App, it sends our server (Supabase) a random identifier the App creates itself (not an advertising ID or device identifier; it is recreated if you delete the App), the device type (iOS/Android), the App version and whether you are signed in. We use this only to count daily and weekly users, including guests. No user ID, email address, location or record content is sent, and it is not linked to your account.
We do not track you across other companies' apps or websites, and we do not provide or sell information to third parties for advertising.
14. Service providers and international transfers
We entrust the handling of information to, or send information to, the following providers:
Supabase, Inc.: database, authentication and server processing (data stored in Tokyo, Japan). Accounts, backups, friends, shared trips, community routes, purchase records, AI usage counts, relaying place searches.
RevenueCat, Inc. (USA): purchase management.
OpenAI (USA): AI travel companion (only with your consent).
Apple Inc. (USA): App Store, payments and Sign in with Apple.
MET Norway (Norway): weather.
komoot GmbH (Germany): place search (Photon).
Wikimedia Foundation, Inc. (USA): adding place names (Wikidata).
OpenStreetMap Foundation (UK): adding place names (Nominatim).
OpenFreeMap: map tiles.
Expo / 650 Industries, Inc. (USA): app update delivery.
GitHub, Inc. (USA): settings file delivery.
Some of these involve transfers to providers in other countries, whose data-protection laws may differ from those where you live. Each provider handles information under its own privacy policy.
15. Retention and deletion at a glance
Data on your device: kept until you delete the App. Individual records can be deleted in the App.
Cloud backup: kept until you delete your account. Deleted records are erased during periodic cleanup or, at the latest, when you delete your account.
Friends and card information: kept until you remove the friend or delete your account.
Shared trips: kept until the trip is deleted (Section 5).
Shared "recently visited" data: kept until you turn sharing off or delete your account.
Trip invitations from friends: kept until accepted, declined or cancelled; they expire after 14 days and are deleted periodically.
Community routes: kept until you stop sharing or delete your account; rate-limit activity logs for 7 days.
Purchase, grant and redemption records (our server): kept until you delete your account. Apple's and RevenueCat's records follow their policies.
AI: chat history on your device only (deletable on My Page); usage records until you delete your account; up to 30 days at OpenAI.
Place search: search text and coordinates are not stored (temporary in-memory caching for up to 10 minutes). Added place names are kept in memory for up to 7 days, not linked to you. Places you add from the results are saved as part of your records.
Technical logs: deleted automatically after a short period.
After deletion, data may remain for a short period in the disaster-recovery backups of the cloud services we use.
16. Deleting your account
You can delete your account at any time from My Page (マイページ) → Account (アカウント) → Delete account (アカウントを削除).
Deleting your account deletes the account (sign-in information such as your email address, password, Apple user identifier and name) and your data in the cloud (backup, card information, friend links, blocks, purchase/grant/redemption/AI usage records, shared-trip memberships and invite codes you created, your shared "recently visited" data, and your shared routes with your like and "used" records). This cannot be undone.
For accounts that use Sign in with Apple (including accounts with a linked Apple Account), the Apple sign-in sheet appears once more before deletion, and our server asks Apple to revoke the App's Sign in with Apple authorization. This is done on a best-effort basis: if you close the sheet or the revocation fails, your account is still deleted. In that case, you can stop using Sign in with Apple for the App in iPhone Settings > your Apple Account > Sign-In & Security > Sign in with Apple.
Data on your device remains; delete the App if you no longer need it. For content in shared trips, see Section 5.
If you cannot delete your account in the App, please contact us (Section 21).
17. Security
All communication is encrypted (HTTPS). Cloud data is protected by access controls so that only you (and, for shared features, authorized members) can read or write it. Server secret keys are not included in the App.
However, no method of transmission or storage over the internet is completely secure.
18. Children
The App is intended for a general audience. Minors should obtain a parent's or guardian's consent before creating an account, using the AI travel companion or making purchases.
If you are a parent or guardian and want your child's information deleted, please contact us (Section 21).
19. Your requests
You can view, correct and delete your records, and delete your account, in the App.
To request disclosure of information we hold, suspension of its use, or similar, please contact us (Section 21). We will respond in accordance with applicable law after verifying your identity.
20. Changes to this policy
We may update this policy when we add features or when laws change. The updated policy will be posted on this page with a new date at the top, and important changes will be announced in the App or elsewhere as appropriate.
21. Contact
Please use the support contact on the App's App Store page.