On-device photo processing
The app reads the image, capture date, and GPS metadata from photos you select. Original photos are not sent to the provider.
Privacy notice · 2026
This policy explains how the Tabiato iOS app (bundle ID: jp.artplace.Tabiato) and this policy website handle data.
The app reads the image, capture date, and GPS metadata from photos you select. Original photos are not sent to the provider.
When you request a route, photo-derived coordinates and the travel mode are sent to Apple.
Rewarded ads for an additional theme are optional. There are no persistent banners, and original photos or photo-derived locations are not sent for advertising.
01 / Scope
This policy applies to the Tabiato iOS app (the “App”) provided by HARA Takahiko (the “Provider”) and the website that publishes this policy (the “Site”). Apps and services you select through the iOS share sheet are governed by their respective privacy policies.
02 / Data
| Data | How and why it is used | Destination or storage |
|---|---|---|
| Photos you select | The App reads the image, thumbnail, capture date, and GPS coordinates from photos explicitly selected with the iOS Photos picker, or from up to 200 photos in a collection explicitly chosen by the user, to create locations, routes, and artwork. | Working data remains on the device. Original photos are not sent to the App provider or its servers. |
| Route request data | When you tap the route-search control, the App uses consecutive photo locations as origins and destinations and classifies each segment as walking or driving based on distance. | Sent to Apple Maps. |
| Map display data | The App uses the visible map area and related request information to display maps and generate still images and videos. | Sent to Apple Maps. |
| Created artwork and record metadata | Finished files, thumbnails, title, creation date, photo and location counts, distance, and export settings are used to save and display your work. | Stored on device. Saving to Photos or sharing happens only when you choose it. |
| App usage and identifiers | Screen views; success or failure of photo import and route calculation; bucketed photo, location, and similar counts; saving still images or videos; rewarded-theme unlocks; and app, device, OS, language, approximate-region, and app-instance information are used to understand usage and improve the App. | Google Analytics for Firebase. Photos, GPS coordinates, journey titles, filenames, free-form text, and raw error messages are not sent. |
| Advertising, consent, and diagnostics | If you choose to view an ad for an additional theme, Google may process approximate location derived from IP address, device and app information, device- or app-scoped identifiers, ad interactions such as impressions and video views, SDK crash and performance information, and advertising-consent status. | Google Mobile Ads (AdMob) and Google User Messaging Platform. Original photos, GPS coordinates read from photos, and created artwork are not sent to the advertising service. |
| Site request information | IP address, request URL, user agent, referrer, timestamps, response metadata, and approximate country or city may be processed to deliver the Site, detect abuse, and analyze operations. | Google Firebase Hosting. This data is not sent by the App. |
The App does not request Core Location permission for your current location and does not use accounts or contacts. It does not request App Tracking Transparency permission. Firebase Analytics is enabled, but Analytics collection of IDFA and IDFV and use of Analytics data for ad personalization are disabled. Firebase Crashlytics is not used. Identifiers processed by Google Mobile Ads vary with consent, device settings, and Google's serving configuration.
03 / Purpose
If data is used for a materially incompatible purpose, the Provider will give notice and obtain consent where required.
04 / Service providers
The App uses Apple MapKit and Apple Maps for map display, map imagery, and directions. Apple may process the request time, device and software information, visible map boundaries, route origin and destination, and travel mode under its policies. See Apple Maps & Privacy.
The App uses Google Analytics for Firebase to collect screen views, use of key features, processing outcomes, and coarsely bucketed counts. Photos, GPS coordinates, journey titles, filenames, free-form text, and raw error messages are not included in Analytics events. The App uses an Analytics SDK configuration without IDFA collection capability, disables IDFV collection, and disables the use of Analytics data for ad personalization. You can stop future collection from the App's Settings screen. See Privacy and Security in Firebase and the Google Privacy Policy.
The Site is delivered through Google Firebase Hosting. Google states that Firebase Hosting processes incoming request IP addresses for abuse detection and detailed usage analysis and retains IP data for a few months. See Privacy and Security in Firebase and the Google Privacy Policy. The App includes Firebase Core and Firebase Analytics, but does not use Firebase Crashlytics, Authentication, or cloud storage.
The App uses the Google Mobile Ads SDK to show a rewarded ad only after you choose to view one for an additional theme. Google may process IP address, approximate location, device and app information, device- or app-scoped identifiers, ad impressions and video views, crash logs, and performance information for ad delivery, frequency control, fraud prevention, measurement, and service improvement. Google User Messaging Platform presents advertising choices where required and lets eligible users revisit those choices from the App's settings. See How Google uses advertising data and the Google Privacy Policy.
When you use the iOS share sheet, the created image or video is passed to the app or person you choose. The recipient’s terms and policies apply after sharing. The Provider does not automatically choose a destination or publish your work without your action.
The Provider does not disclose personal data to other parties except as described here, with your consent, when required by law, or when necessary to protect life, safety, property, or legal rights. Where the Provider appoints a processor, it will require protections consistent with this policy and applicable law through appropriate terms and oversight.
05 / Retention
The App has no user account or Provider-operated cloud storage for your artwork, so the Provider does not hold a server-side copy it can delete on request. Uninstalling the App deletes its app-container data. Copies in Photos or at share destinations must be deleted separately.
06 / Your choices
07 / Security
The App performs processing on device where practical and limits transmissions to data needed for map, routing, and usage-analytics features. iOS file protection is applied to Journey Records, and communications with external services use the encrypted transport provided by those platforms. No method of electronic storage or transmission is completely secure.
08 / International processing
Apple Maps, Google Analytics for Firebase, Firebase Hosting, and Google Mobile Ads may process data outside your country or region. Each provider handles that data under its applicable terms, data-protection commitments, and privacy policy.
09 / Children
The App is not directed primarily to children and does not collect age, name, or contact details. Minors should use the App with parental consent or supervision where appropriate.
10 / Changes
This policy may be updated when features, service providers, or legal requirements change. Material changes will be explained clearly on the Site or in the App, and renewed consent will be obtained where required. The latest version and update date will be posted here.
11 / Contact
For questions about this policy or data handling, contact:
Provider: HARA Takahiko
Contact: programmingfeelsgood@gmail.com