Privacy Policy
Strolloria reads your total step count for the current day from HealthKit or Health Connect only with your permission. Your step count, walking history, and town progress data are stored on your device and are not sent to Firebase or any other external service. To improve app quality, non-health information about app usage, crashes, and performance is sent to Google's Firebase services.
This Privacy Policy explains how Takamasa Mizukami (the “Operator”) handles information in connection with Strolloria (the “App”).
1. Information the App Accesses or Stores
Step-count information
- Your total step count for the current day, obtained from Apple HealthKit on iOS or Health Connect on Android
- Daily step records generated to reflect your steps in town growth and walking history within the App
The App accesses your step count only when you grant read permission through your operating system. When you first connect the App, it reads only the total steps recorded between midnight on that day and the current time; it does not import step counts from previous days. The App may subsequently read the current day's total when it starts, when the connection is completed, or when it returns to the foreground. The App does not write health data to HealthKit or Health Connect.
Information generated and stored within the App
- Your selected town, town growth stage, journey progress, completion records, and replay records
- Daily step history and town growth history
- Onboarding status, language preferences, and other app settings
Device settings
The App uses your display language, date, and time to present the appropriate language, manage step counts by date, and automatically adjust the town's lighting and weather. The App does not access precise location, your name, postal address, telephone number, or contacts.
Information collected and transmitted through Firebase
To understand and improve app quality, the App uses Google Analytics for Firebase, Firebase Crashlytics, and Firebase Performance Monitoring, which are provided by Google LLC. These services may automatically collect and transmit the following information to Google:
- Usage information: app launches, screen views, sessions, feature usage, app version, operating system, device model, language, time zone, country or region inferred from the IP address, and a pseudonymous app-instance ID generated for each installation of the App
- Crash and diagnostic information: the date and time of a crash or exception, stack traces, exception messages, app state, logs, app version, operating system, device model and conditions such as performance and available storage, Firebase Installation ID, Crashlytics Installation UUID, and session ID
- Performance information: app startup time, screen rendering time, operation duration, CPU and memory usage, network type, request URLs (excluding query parameters and content), response time, response code, transferred data size, app version, operating system, device model, country or region inferred from the IP address, Firebase Installation ID, and session ID
The App does not include step counts, information obtained from HealthKit or Health Connect, daily walking history, or town progress, completion, or replay records in Firebase events, user properties, crash logs, custom keys, performance traces, or any other transmitted fields. The App does not collect advertising identifiers (Apple's IDFA or Android's Advertising ID), and Firebase information is not used for advertising, personalized advertising, or tracking across apps.
Information you provide when contacting us
If you contact the Operator by email, the Operator receives your email address, the contents of your message, and any other information you choose to provide.
2. How Information Is Used
The App and the Operator use the information described above only for the following purposes:
- To provide the App's primary feature of growing towns based on your steps
- To display and maintain daily steps, town growth, completion, and replay records on your device
- To apply your selected language and settings
- To prevent duplicate step counting and maintain accurate step synchronization and town progress
- To understand app usage in aggregate and improve screen design, features, and usability
- To detect and analyze crashes and defects and to investigate and resolve their causes
- To measure startup, rendering, processing, and network performance and improve stability and responsiveness
- To respond to inquiries and investigate reported problems
- To comply with applicable legal obligations
Step-count information is not used for advertising, marketing, user tracking, credit assessment, insurance pricing, or third-party data analysis.
3. Storage, External Transmission, and Retention
- Step history, town progress records, and app settings are stored in the App's private storage on your device.
- Step counts, walking history, and town progress records are not transmitted to or stored on the Operator's servers or Firebase.
- Information stored on your device is retained until you delete the App.
- Depending on your operating system's backup settings, locally stored information may be included in a backup managed by Apple or Google. You can manage and delete backups through your operating system settings.
- Google Analytics user-level and event-level data is configured to be automatically deleted 14 months after collection. This retention setting may not apply to standard aggregated reports.
- Firebase Crashlytics retains crash information and associated identifiers for 90 days before beginning the process of removing them from live and backup systems.
- Firebase Performance Monitoring retains IP-associated performance events for 30 days, and installation-associated and de-identified performance data for 60 days, before beginning the process of removing them from live and backup systems.
- Information included in inquiries is retained for as long as needed to respond, keep appropriate records, and comply with legal obligations, and is deleted when it is no longer needed.
4. Service Providers and Disclosure to Third Parties
The Operator does not receive, sell, or disclose to third parties the step information or progress records stored by the App on your device. Google processes information transmitted to Firebase as a service provider acting on the Operator's behalf. Other information may be handled in accordance with applicable law when necessary to comply with a lawful disclosure request, protect life, health, or property, or engage a service provider.
The App and this policy use or relate to the following external services:
- Apple HealthKit / Google Health Connect: used to read step counts with your permission. Health data remains under the control of the applicable service and your device.
- Google Analytics for Firebase (provided by Google LLC): used to statistically analyze app usage and improve features and usability.
- Firebase Crashlytics (provided by Google LLC): used to detect and analyze crashes and defects and improve stability.
- Firebase Performance Monitoring (provided by Google LLC): used to measure and analyze startup, rendering, processing, and network performance and improve responsiveness. For details about how Firebase handles information, see Privacy and Security in Firebase and the Google Privacy Policy.
- GitHub Pages: used to publish this policy. GitHub may process information such as your IP address, browser information, and access date and time when you view this page. For details, see the GitHub General Privacy Statement.
- Email services: used to send and receive inquiry emails. The policies of the email service providers used by you and the Operator apply to the handling of those emails.
Information transmitted to Firebase may be processed or stored by Google LLC and its subprocessors in countries or regions outside Japan, wherever Google or its agents maintain facilities. Google handles this information under the applicable Firebase Data Processing and Security Terms and data protection laws.
5. Security
The App stores step history and progress records in private storage provided by the operating system so that other apps cannot directly access them. It minimizes the health information it handles by requesting read-only access to total step counts. Health and step information is kept separate from information transmitted to Firebase, and access to the Firebase console is limited to what is necessary. Communications with Firebase use HTTPS, and the relevant Firebase services encrypt stored data at rest.
6. Your Choices and Deletion
- You can review or revoke step-count access at any time through Health or system settings on iOS, or through Health Connect settings on Android.
- After permission is revoked, the App can no longer read new step data. Previously stored step history and town progress are not automatically deleted.
- You can delete information stored within the App by deleting the App from your device. Data in operating-system backups must be deleted separately through the applicable operating system or cloud-service settings.
- Deleting the App does not delete the original step data stored in HealthKit or Health Connect. You can manage that data through the applicable service settings.
- Deleting the App stops new transmissions from that device to Firebase. If you reinstall the App, new app-instance identifiers will generally be generated.
The App does not provide user accounts, and the Operator does not store your step or progress records on its servers. The Operator therefore cannot remotely access or delete this locally stored information.
Where applicable law requires prior consent for Firebase data collection, the App will not begin collection through the relevant services until consent is obtained. To withdraw consent, request deletion of information transmitted to Firebase, or exercise other data-protection rights, contact the Operator using the details below. Because the App does not provide user accounts, the Operator may be unable to identify Firebase pseudonymous data as belonging to you based on the information you provide. In that case, the Operator will still explain the options reasonably available.
7. Changes to This Policy
The Operator may update this policy to reflect changes to the App, external services, or applicable laws. Material changes will be announced through the App or on this page by an appropriate method. The revised policy takes effect when posted on this page or on a separately stated effective date.
8. Contact
For questions about this policy or the handling of information, contact:
mizukami2005@gmail.com
9. Operator
Takamasa Mizukami