日本語

Footstep Log Privacy Policy

Applies to: Footstep Log — com.x91932.pedometer
Effective: August 4, 2026
Last updated: October 15, 2026

QuickServe Inc. ("we", "us") sets out below how user information is handled in Footstep Log (the "App"), our pedometer and activity-tracking app (this "Policy").

1. Company information (data controller)

Where the GDPR or similar laws apply, QuickServe Inc. is the data controller for the App.

2. Scope and authoritative version

This Policy applies only to the App. Our other apps are covered by our common app privacy policy. This document is independent of the privacy policy on our corporate website. The Japanese version of this Policy is authoritative; if there is any discrepancy with a translation, the Japanese version prevails.

3. Information the App stores on your device

The App can be used without creating an account, and we do not directly collect your name or similar information. The data below is stored on your device and is never sent to our servers (except for the backups described in Section 5). We cannot access this data.

DataSourcePurpose
Location (GPS)
including background collection
Your device's location servicesRecording and displaying routes on a map; automatically classifying activities (walking, running, cycling, driving, train, staying)
Step dataApple Health (HealthKit) / Android Health Connect, and your device's motion sensorsDisplaying step counts, daily statistics and charts
Motion and activity dataYour device's motion sensors (e.g. CoreMotion)Improving the accuracy of activity classification
Activity logs and saved placesGenerated in the App from the data above, and entered by youDisplaying and editing your activity records; naming saved places automatically
App settingsYour actions in the AppStoring your step goal, display preferences and similar settings

You can delete this data from within the App, and uninstalling the App removes it from your device (except for the backups described in Section 5).

4. How location data is handled

The core function of the App is to record your routes and activities automatically, which requires location access in the background so that recording continues while the App is closed. Location is only collected if you grant permission in your operating system's dialog, and you can change or revoke it at any time in your device settings.

Location data is used solely for recording, classification and display on your device. It is never sent to our servers, and it is never used for advertising or ad targeting, nor provided to third parties for any other purpose.

5. How backups are handled

The App offers a feature that lets you back up your location, step and activity data to iCloud yourself (iOS). If you use it, the data is stored in your own iCloud account — storage provided by Apple — and we cannot access its contents.

The App also lets you export a backup as a file yourself (iOS and Android). The exported file is saved, via your operating system's share screen, to a location you choose (such as Google Drive, iCloud Drive or your device). The App itself never sends the file anywhere, and we cannot access its contents. Data stored there is handled under that service's own terms and policies.

In addition, on iOS a copy of the App's data may be kept on Apple's servers and restored when you reinstall if iCloud Backup (the OS feature) is enabled. On Android, the location and activity log database is excluded from Google Backup, so only app settings are backed up. These copies and any exported files remain even after you delete the App, so please remove them from your OS backup settings or the save location if you no longer need them.

6. How health data is handled

With your permission, the App reads step data from Apple Health (HealthKit) or Android Health Connect. It requests read access only and does not write data back to them.

We never use health data for advertising or marketing, and we never provide or sell it to third parties. It is used solely to display step counts and statistics on your device. You can revoke this permission at any time in your device's health settings.

7. Information collected by third-party SDKs

The App uses the following third-party SDKs for advertising, ad measurement, quality improvement and map display. These SDKs automatically collect the information below and send it to servers operated by Google LLC and its affiliates ("Google").

SDKMain information collectedPurpose
Google AdMob
(ad delivery)
Advertising ID (IDFA on iOS / Advertising ID on Android — collected only where permitted by OS settings, applicable law and your consent), ad impression and interaction events, IP address (including inference of approximate location), device information (model, OS version, etc.)Delivering ads, measuring their performance, preventing fraud
Firebase Analytics
(ad measurement)
App instance ID, advertising ID (collected only where permitted by OS settings, applicable law and your consent), app usage (automatically collected events such as first launch, sessions, engagement time and app updates), IP address (masked, used to infer an approximate region), device information (model, OS version, etc.)Measuring the effectiveness of the App's own Google Ads campaigns (counting installs), analysing usage
Firebase Crashlytics
(crash reporting)
Crash logs, diagnostic and performance information, installation UUID, device and OS informationDiagnosing defects, improving quality
Google Maps SDK
(map display)
Requests for map data of the area being displayed, IP address, device information (model, OS version, etc.), an SDK identifier (pseudonymous), map interactions (panning, zooming, etc.), crash informationDisplaying maps, understanding SDK usage, improving quality

Firebase Analytics is used to measure whether the App's ads on Google Ads lead to installs; the App does not send any custom events. In regions where consent is required (the EEA, the UK and Switzerland), it is used only if you consent in the consent form. The location, step and activity data described in Section 3 is never passed to AdMob, Firebase Analytics or Crashlytics. On the map screen, the App passes the locations of your recorded routes and current position to the Google Maps SDK to display them on the map. To display the map, map data for the visible area is fetched from Google. The "approximate location" inferred by AdMob and Firebase Analytics is derived from your IP address and is separate from the GPS location the App collects.

If you contact us, we collect your contact details (such as name and email address), the content of your enquiry and, where necessary, device and OS information, for the purpose of responding. We delete this information after a reasonable period once your enquiry has been resolved.

8. Disclosure to third parties and external transmission

We do not provide collected information to third parties, except as required by law and for transmission to the external service providers (such as Google) described in this Policy.

Information sent through the SDKs in Section 7 is handled by Google under its own privacy policy. Depending on the processing, Google may act as an independent controller. Personalized advertising and cross-app tracking are carried out in accordance with applicable law and your consent status (iOS ATT, consent forms). First-launch information measured by Firebase Analytics is linked with Google Ads to measure ad effectiveness.

In place of a Google AdMob ad, the banner slot in the App may show a promotion for one of our other apps. Such a promotion only displays information we have prepared (app name, description, icon and a link to the store) and involves no collection or transmission of information about you.

To show these promotions, the App periodically retrieves the promotion information (app name, description and icon) from our website (qkserve.github.io, hosted on GitHub Pages operated by GitHub, Inc.). As with viewing any web page, connection information such as your IP address reaches GitHub's servers during this retrieval; we do not collect or store it, and the location data, steps and activity logs described in Section 3 are never transmitted.

9. International data transfers

The SDKs in Section 7 transmit data to Google servers located in the United States and other countries outside Japan. Google applies appropriate safeguards, including compliance with the EU Standard Contractual Clauses. Details of the destinations and safeguards are available in "Privacy and Security in Firebase" and the other references above.

10. Managing consent and opting out

11. Additional information for users in the EEA and the UK (GDPR / UK GDPR)

The legal bases for processing are as follows.

ProcessingLegal basis
Recording location, step and activity data on your device (on-device processing only)Consent (OS permission grant)
Storing and reading identifiers on your device (advertising ID, etc.)Consent
Delivering personalized adsConsent
Delivering ads without consent (limited ads) and preventing fraudLegitimate interests (sustaining the free App, security)
Ad measurement and usage analysis (Firebase Analytics)Consent
Crash reporting (Crashlytics)Legitimate interests (maintaining quality on a data-minimizing basis)
Map display (Google Maps)Performance of a contract (displaying the map screen you open)
Complying with legal obligationsLegal obligation

12. Users in other regions

Depending on the laws of your region, you may have rights such as access, deletion and opt-out. Requests to exercise these rights are accepted at the contact point in Section 14.

13. Children

The App is not designed for children.

14. Requests for disclosure and contact point

Requests for disclosure, correction or suspension of use of retained personal data, and enquiries about this Policy, are accepted at the contact point below. We may ask for documentation to verify your identity. There is no fee.

QuickServe Inc. — Personal Data Enquiries
Email: info@91932.com
Tel: +81-3-6450-5141 (weekdays 10:00–19:00 JST)
Address: Sakurai Bldg. 2F, 2-8-19 Fukagawa, Koto-ku, Tokyo 135-0033, Japan

15. Changes to this Policy

We may revise this Policy in response to changes in law or in the App's functionality. For material changes (such as adding a new SDK, purpose or recipient, or changing how consent is handled), we will post a notice on this page and, where necessary, notify you in the App or obtain your consent again. A revised Policy takes effect when it is posted on this page.