Android privacy policy

Applies to Footprints for Android 1.3.0 · Effective date: September 13, 2026

Individual developer Shin Dongnyeok explains how Footprints for Android processes information and the choices available to you. Footprints is an on-device walking and places journal for people aged 14 and older. It has no member accounts or public profiles and does not provide medical advice, diagnosis, or treatment.

1. Operator and contact

Operator and privacy contact: Shin Dongnyeok
Email: contact@nyeok.co
Public policy: footprints.nyeok.co/us/legals/policy

2. Information and purposes

  • Location and walks. When you start a recording, location, time, accuracy, altitude, speed, direction, routes, distances, excluded points and their reasons support your journal, maps, visited regions and statistics. A recording you started can continue with the screen off or another app open. An ongoing notification shows its status and lets you stop it.
  • Motion. Step-sensor changes during a recording help detect walking and automatic pauses. Sensor readings are not retained as a separate activity history. Recording can use location signals if motion permission is denied.
  • Photo visits and representative photos. Permitted photo dates and locations are read on your device. Stored photo-visit data includes dates, derived visited regions and one-way fingerprints. Original photos and raw EXIF coordinates are neither stored nor uploaded. Representative-photo references and dot colors are encrypted on the device; crop and place links support display and restoration. Original photos are not changed or deleted. One-time imports and automatic synchronization, which is off by default, are separate choices. You can also import selected photos through the system photo picker.
  • Notes, profile and settings. Record identifiers and summaries, note text, place links and drafts, a local profile identifier and selected regional badge, and settings are stored on your device. The local profile is not a server-side account.
  • External records. A Google Timeline JSON file you choose is processed on your device. Supported visits retain location, time and place links. The source file, file path and account credentials are not kept permanently. Imported visits do not become distances or routes you walked.
  • App lock. Your optional app passcode is protected using Android Keystore. Android performs biometric authentication; the app does not receive original fingerprints, face data or biometric templates.
  • Images and videos. Requested badge/dot-map PNGs and visit-timeline MP4s are generated on your device and saved to its media storage. Videos do not include original photos, raw coordinates or actual GPS routes.

3. Storage, backups, retention and deletion

Records, notes, visits and profiles are stored in app-private SQLite; settings are stored on the device until app data is deleted. Individual records, notes, photo visits and external visits can be managed within the deletion scopes explained by the app. Photo-visit exclusion markers may remain to prevent reimporting. Deleting app data or uninstalling the app removes its private data.

Automatic Android cloud backup and automatic device transfer are disabled. Personal backups you explicitly export are encrypted with a password you create and passed to the document provider you choose. They may include routes, notes, visits, profiles and some representative-photo settings. They exclude original photos, device-local photo URIs, app passcodes, backup passwords, biometric information and note drafts. If you select a cloud provider, it may store the encrypted file. Android backups are not compatible with iOS iCloud backups.

Deleting app data does not automatically delete exported backups or saved images/videos. Manage them separately with their document or media provider. Your photo-sync settings may synchronize media to other services. Representative photos may need to be linked again if access is revoked or you change devices.

4. Network connections and providers

This Android build has no Firebase Analytics, advertising, Play Billing or account SDK, and sends no analytics events or ad requests. Location recordings, photos and notes are not uploaded to a developer server.

When you request a detailed country map, the app downloads public files from footage.nyeok.co over HTTPS using Amazon Web Services CloudFront and S3. Servers process connection information such as IP addresses, requested files and access times. These requests do not contain recordings, photo content or notes.

The developer does not collect or retain CloudFront standard or real-time access logs or S3 server access logs, and no WAF logging is attached to this distribution. There is no developer retention period for per-request access logs. Aggregate CDN request and transfer metrics support service operations. This does not mean AWS performs no internal processing needed to provide and secure its services.

Public map files originate in US East (Northern Virginia, us-east-1). Requests may be processed across the AWS global CloudFront network, including South Korea and the United States. IP addresses and request information are sent to AWS over HTTPS when you request a file, to deliver it and operate the connection. Skipping country-map downloads avoids this download connection but prevents obtaining new detailed country maps. See the AWS data privacy information and service providers and processing locations.

Storage and synchronization by document and photo providers depend on the services and settings you choose. Contact details and messages you email us are processed to respond to your inquiry. We do not sell personal information.

Google Play installation, updates and testing are governed by Google Play terms and privacy policies. When you join a test program, Google may share your email and app-usage information with the developer. You can leave the test program through Google Play.

5. Your choices and safeguards

Manage location, motion, photo and notification permissions in Android settings. You can stop recordings and change automatic photo synchronization and app lock in the app. Personal backups run only when you request them. Contact the privacy contact about access, correction, deletion, processing restrictions or withdrawal of consent. The developer cannot remotely access or restore local records that are not stored on a server.

Safeguards include the app sandbox, device-backed encryption, encrypted personal backups, HTTPS, download-integrity checks and temporary-file cleanup. Coordinates, routes, notes, photo URIs and passwords are not written to diagnostic logs. Policy changes and their effective date will be published on this page.