Privacy Policy

Privacy Policy

Effective date: July 17, 2026

Interval Running is a running app focused on local storage. It does not use email/password registration, social login, or advertising SDKs. Workout records and settings are stored on your device by default. The App also uses an anonymous server identifier for user initialization and plan sharing, and uses Firebase Analytics and Crashlytics for reliability and usage analysis.

1. Information We Process

• Workout date and time, duration, distance, average speed or pace, estimated calories, interval phases, sets, workout title, and goal data.
• Weight, height, gender, goals, theme, language, audio, haptic, health integration, and other app settings stored on your device.
• GPS location, distance, speed, pace, and device sensor movement data used while a workout is active.
• Workout start and end time, duration, distance, and estimated calories written to Apple Health or Android Health Connect when you enable health auto-save.
• A random user ID generated by the App, operating system type, selected language, and server feature state such as invitation code, token balance, and invitation participation status.
• Plan title, interval settings, category, creation time, and sharing identifier when you choose to share a plan.
• App launch, session, screen view, approximate device and OS details, app version, app instance identifiers, crash logs, stack traces, and related diagnostic information processed through Firebase Analytics and Crashlytics.

The App does not use microphone recordings, contacts, photos, camera, or calendar information.

Information is obtained when you enter settings, start or complete a workout, grant an operating-system permission, enable health auto-save, choose to share or import a plan, or use the App. The random user ID and basic technical or diagnostic information may be generated automatically by the App, its server, or an integrated SDK.

2. How We Use Information

• To run the interval timer and provide phase, voice, haptic, notification, background, and lock-screen guidance.
• To calculate and display workout distance, speed, pace, estimated calories, goals, history, and reports.
• To save completed workouts to Apple Health or Android Health Connect when you explicitly enable the feature.
• To initialize an anonymous app user, synchronize server feature state, create plan-sharing links, and import shared plans.
• To understand basic app usage, improve reliability, diagnose crashes, and prioritize fixes.

Firebase Analytics and Crashlytics are not used for advertising targeting or tracking you across other companies' apps or websites.

3. Location, Sensors, and Health Data

Location and movement sensors are used only while needed to track an active workout, including when the screen is off or the App is in the background. Raw location paths are not sent to the App's own server. You can revoke location permission in device settings, but distance, speed, and pace features may be limited.

Health auto-save is off by default. If enabled, the App writes only workouts completed in this App to Apple Health or Android Health Connect. The App does not read existing health records or transmit health data to its own server or Firebase. Health permissions can be revoked in the operating system's health settings.

4. Server, Sharing, and Third-Party Processing

The App does not sell personal information. Information is processed or transferred only to provide requested features, operate and protect the service, comply with law, or work with the following service providers and platforms:

• RYNYUL server API: processes the random user ID, operating system, language, server feature state, and plans you intentionally share. Plans are not uploaded merely because they are stored locally.
• Google Firebase Analytics and Crashlytics: may process install or first-open events, launches, sessions, active-user counts, screen views, event timestamps, app version, device model, OS version, language, approximate country or region, app instance identifiers, Crashlytics installation UUID, crash logs, stack traces, and related app or device diagnostic state.
• Apple Health and Android Health Connect: receive completed workout data only after you enable health auto-save and grant the relevant write permission. Their processing follows the platform settings and policies.

Firebase information may be processed on Google's global infrastructure, including outside your country or region. As a rule, the App is designed not to send names, email addresses, phone numbers, raw workout routes, body profile values, or workout and health details through Firebase events or crash reports.

For more information, see the Google Privacy Policy and Firebase Privacy and Security documentation.

5. Permissions and Background Features

The App may request location, notification, background execution, battery optimization, and health write permissions when required by a feature. Notifications and background services keep the timer visible and provide phase or completion alerts. Permissions can be changed at any time in device settings.

6. Storage, Retention, and Deletion

• Local app data: workout history, saved plans, and settings remain on the device until you delete them or uninstall the App, subject to operating-system backup and restore behavior.
• Anonymous server state: the random user ID and related server feature state are retained while needed to provide the server feature or until a verified deletion request is completed, unless longer retention is required by law, security, fraud prevention, or dispute resolution.
• Shared plans: plans you intentionally upload remain until the sharing link expires, service cleanup removes them, or a verified deletion request is completed.
• Firebase data: analytics and diagnostic information is retained according to the configured Firebase retention settings and Google's applicable policies.
• Health data: workouts written to Apple Health or Health Connect are retained and can be managed under the operating system's health data settings.

To request deletion of server-side information, email taesis.inc@gmail.com with the subject “Interval Running Data Deletion Request.” We may request limited information needed to locate the anonymous record and verify the request.

7. Your Choices

• Change or revoke location, notification, and health permissions in device settings.
• Turn health auto-save and other optional features off in the App.
• Delete workout records in the App or uninstall the App to remove local app data, subject to platform backups.
• Stop creating new sharing links and request access to or deletion of server-side information through the privacy contact below.
• Change body profile, goals, theme, language, and other settings in the App, and use privacy controls provided by the operating system.

Revoking a permission or deleting information may limit related features. Already aggregated or de-identified analytics information may not be removable for an individual user.

8. Security Measures

• Own-server API traffic is transmitted over HTTPS and uses request validation.
• Workout history and settings are stored locally by default, and access to protected platform data is controlled through operating-system permissions.
• We seek to minimize processed information, restrict operational access, and avoid including raw routes, health details, or body profile values in analytics events and diagnostic logs.
• No internet transmission or storage method is completely secure, so absolute security cannot be guaranteed.

9. Children's Privacy

The App is not designed to intentionally collect personal information from children. Children under 14, or under the applicable child age in their country or region, should use the App under the consent and guidance of a parent or guardian. A parent or guardian may contact us to request deletion.

10. Changes to This Policy

We may update this policy when app features, laws, platform requirements, or service practices change. An updated policy will be posted with a revised effective date, and material changes may also be announced in the App, store listing, or another appropriate channel.

11. Privacy Contact