Privacy

Running Machine Privacy Policy

This privacy policy explains how Running Machine (RunCapture) accesses, collects, uses, stores, and shares data when you sign in, submit treadmill images for extraction, save runs, or contact support.

App
Running Machine (RunCapture)
Effective date
April 8, 2026

Developer and contact

Running Machine is provided by Jaeyeon. Privacy or support questions can be sent to contact@jaeyeon.com.

The app name Running Machine and the alternate name RunCapture refer to the same product in this policy.

Data we access and collect

Depending on how you use the app, Running Machine accesses or collects information needed to authenticate your account, process treadmill photo extraction, save run history, and support account deletion or troubleshooting.

  • Account information such as your email address, display name, profile photo, authentication provider, Firebase user identifier, and sign-in state.
  • Treadmill photos that you explicitly capture with the camera or select from the gallery for metric extraction.
  • Run history and fitness-related records such as duration, distance, speed, calories, timestamps, manually corrected values, and saved history entries.
  • Limited service metadata needed to protect backend requests, such as App Check validation and extraction rate-limit records.
  • Device, app version, diagnostic, and error information needed to investigate failures or support requests.
  • Support inquiries and any information you voluntarily include when contacting support.

How we use data

  • To authenticate users and maintain signed-in sessions.
  • To extract treadmill run metrics from submitted photos through backend processing after the user confirms the extraction disclosure.
  • To let users review, edit, save, and sync run records across devices.
  • To generate history, cumulative statistics, personal bests, and related app features.
  • To protect the service from abuse, validate requests, and enforce operational limits.
  • To troubleshoot bugs, investigate failures, and improve product quality.

Third-party processing and sharing

Running Machine uses third-party infrastructure to operate core features. Data is shared only as needed to provide the service, secure the platform, or comply with legal obligations.

  • Firebase Authentication for Google or Apple sign-in and session management.
  • Cloud Firestore for synced run history, user records, and limited backend operational records.
  • Firebase Functions and App Check for protected backend processing and request validation.
  • OpenAI, through the backend function only, to help extract treadmill metrics from submitted images.
  • Other service providers or authorities when required for security, fraud prevention, or legal compliance.

Data handling and security

The app is designed to send data through protected network channels and to rely on Firebase authentication and App Check controls where supported.

No security measure is perfect, but reasonable technical and organizational steps are taken to reduce unauthorized access, disclosure, or misuse.

  • Data sent between the app and backend services is intended to be transmitted over HTTPS.
  • Backend extraction is routed through a callable function rather than direct client-side model access.
  • Access to synced account data is intended to be scoped to the authenticated user and authorized backend systems.

Retention

Data is retained only for as long as reasonably necessary to operate the app, provide synchronization, maintain security controls, resolve disputes, and meet legal obligations.

  • Local run history remains on the device until it is deleted by the user, the app is removed, or local storage is otherwise cleared.
  • Synced run history and user records may remain until the user deletes the account or the account-linked data is otherwise removed.
  • Operational logs, backups, and diagnostic records may persist for a limited period before routine deletion or overwrite.

User choices and deletion

Users may manually edit extracted run data before saving it, choose whether to submit an image for extraction, and delete their account directly from the app's Account screen.

If account deletion is completed successfully in the app, the backend deletes the Firebase-authenticated account, synced user records, and associated operational records used to support the service. The app also clears local cached history on the device that completed the deletion.

  • You can use the in-app Account → Delete Account flow while signed in.
  • If you cannot access the app, you can use https://jaeyeon423.com/apps/running-machine/delete-account or email contact@jaeyeon.com for help.
  • Some residual records may temporarily remain in backups or logs before final expiry.
  • If you used multiple devices, local data already stored on another device may need to be cleared from that device separately.

Children and sensitive data

The app is not intended to collect personal data from children in violation of applicable law. If you believe data was submitted in error, contact the developer.

Run metrics and treadmill photos may be sensitive depending on how you use the service. Submit only images and information necessary for the app's functionality.

Policy updates

This privacy policy may be updated as the app, infrastructure, or legal requirements change. Material updates should be reflected through an updated effective date and, where appropriate, in-app or store-facing updates.