IntervalFlow Privacy Policy

Overview

Adstar Labs is the developer brand responsible for IntervalFlow. This Privacy Policy explains how the IntervalFlow mobile application handles information.

IntervalFlow is a focused health & fitness — interval timer app. Its core purpose is to run prepare, work, rest, set-break and cooldown phases. It does not require an account, does not contain in-app advertising, and does not sell personal information. After iOS ATT authorization, the limited data described below may be used for analytics, installation attribution, advertising measurement, and crash diagnosis.

Information you provide

Depending on how you use IntervalFlow, you may enter or create:

• Custom interval settings and active-session settings
• Active run state, elapsed time and scheduled notification identifiers
• Completed-session history with duration, rounds, sets and timestamps
• Language preference

This content, together with your language and other app preferences, is stored in the app’s local storage on your device. Adstar Labs does not operate an account or cloud-sync service for IntervalFlow and does not receive this content through the app.

Device access and user-directed exports

IntervalFlow may request the following device access only when needed for a feature you choose:

• Optional notification permission for phase-boundary alerts
• Exact-alarm scheduling on Android for interval boundaries
• Vibration for phase changes while the app is open

Permission-dependent processing is performed for the requested feature. Denying a permission may limit that feature but does not create an account or send your app content to Adstar Labs.

Analytics and diagnostics

On iOS, IntervalFlow uses Apple’s App Tracking Transparency (ATT) framework. The app requests Apple’s system prompt only while the ATT status is not determined and rechecks that status at launch and whenever the app becomes active. ATT is the sole telemetry gate; there is no separate custom in-app consent prompt.

Firebase is not configured, and Google Analytics for Firebase, Firebase Crashlytics, and FirebaseSessions remain disabled, unless the iOS system status for IntervalFlow is authorized. Collection remains disabled while the status is not determined, denied, or restricted. All app features remain available regardless of ATT status.

On Android, the current shared telemetry path is disabled, so this version does not configure Firebase Analytics or Crashlytics there.

Analytics and installation attribution

After ATT authorization, full Google Analytics for Firebase with AdSupport may collect the iOS advertising identifier (IDFA), pseudonymous app or installation identifiers, general app, device, operating-system, version and language information, approximate location derived from a masked IP address, lifecycle or session information, and campaign or installation-attribution data.

The shared custom screen_view event uses only non-content screen_name and screen_class values for a screen or section. Analytics may associate IDFA and limited app activity with campaign information to measure which advertising led to an installation. Apple defines this advertising measurement as tracking.

Crashlytics and FirebaseSessions

After ATT authorization, Firebase Crashlytics may collect crash stack traces and relevant application state; crash, session and installation identifiers; app, device and operating-system information; and available Analytics breadcrumbs immediately before a crash. FirebaseSessions supports Crashlytics and may process the app’s bundle ID, operating-system and Firebase SDK information, network connection type, and background or session timing metadata.

Firebase Performance Monitoring is not included, and Performance Data is not declared in the iOS privacy manifest.

IntervalFlow does not set a custom Firebase user ID and does not send the content you enter or create as Analytics event parameters, Crashlytics custom keys, logs, user IDs, or diagnostic fields.

iOS privacy manifest

The iOS privacy manifest declares exactly the following six data categories for this shared implementation:

How we use information

When iOS ATT is authorized, we use the limited Analytics, Crashlytics, and session-support information described above to understand app usage and session quality, measure installation attribution, prioritize improvements, diagnose crashes, and protect app integrity.

IntervalFlow does not include an ad-display SDK, does not show in-app ads, does not personalize ads, does not build remarketing audiences, does not set a custom Firebase user ID, and does not use Firebase information for employment, insurance, credit, or other eligibility decisions.

Sharing and service providers

We do not sell personal information. When iOS ATT is authorized, Google LLC processes the limited Analytics, Crashlytics, and FirebaseSessions information described above under the applicable Google Analytics and Firebase terms. Google may associate IDFA and limited app activity with campaign information for installation attribution and advertising measurement.

The iOS privacy manifest declares exactly three tracking domains used for authorized Analytics and installation attribution:

• app-analytics-services-att.com
• region1.app-analytics-services-att.com
• www.googleadservices.com

These endpoints are not used to display in-app ads. IntervalFlow does not send user-entered app content to Google, an ad-display network, or a data broker. Google’s handling of authorized telemetry is also governed by its Firebase Privacy and Security documentation.

We may disclose information if required by law, to respond to valid legal process, or to protect users, the public, our rights, or the security of our services.

Retention and deletion

Local app data

Local content remains in app storage until you delete entries, clear the app’s data through device settings, or uninstall IntervalFlow. User-directed exports or system backups are controlled separately by you and the destination or backup provider.

Google Analytics data

Absent property-setting evidence for a shorter period, user- and event-level Google Analytics data may be retained for up to 14 months. Standard aggregated reports may remain as aggregated statistics.

Firebase Crashlytics data

Google states that Crashlytics keeps crash reports and associated identifiers for 90 days before removal begins from live and backup systems. When ATT is not authorized, IntervalFlow keeps automatic Crashlytics collection disabled and requests deletion of unsent Crashlytics reports stored on the device.

Withdrawal and deletion requests

Withdrawing ATT stops future collection, resets Analytics data stored on the device, and requests deletion of unsent Crashlytics reports. It does not automatically delete data already uploaded. You may contact us to request deletion, but because IntervalFlow has no account and does not set a custom Firebase user ID, we may need a technical identifier and may not be able to associate a particular record with you.

Children’s privacy

IntervalFlow is not directed to children under 13 or the minimum age required by local law. We do not knowingly collect personal information from children. If you believe a child has provided information to us, contact us so we can review the matter.

Security

We use reasonable technical and organizational safeguards appropriate to the limited information we process. Firebase data is transmitted using encrypted connections. No method of electronic storage or transmission is completely secure.

Your choices

• Tracking, analytics, and diagnostics on iOS: manage IntervalFlow under Settings > Privacy & Security > Tracking. The app rechecks the system status when it becomes active and at launch. If authorization is withdrawn, future Analytics and Crashlytics collection stops, on-device Analytics data is reset, and deletion of unsent crash reports is requested. Previously uploaded information remains subject to the retention and deletion terms above.
• Telemetry on Android: the current shared telemetry path remains disabled.
• Local data: use available delete controls, clear app data in device settings, or uninstall the app.
• Device permissions: manage permissions through your operating-system settings.
• System backup: manage app backup behavior through operating-system or backup-provider settings.
• Privacy rights: depending on where you live, you may have rights to request access, correction, deletion, restriction, or objection regarding information we process.

International processing

International processing can occur only when iOS ATT is authorized and Google processes the limited telemetry described above. User-entered app content is not included in this transfer. Google Firebase may process that telemetry in countries other than the country where you live. Where required, service providers use recognized safeguards for international data transfers.

Changes to this policy

We may update this Privacy Policy when IntervalFlow changes or when legal requirements change. The “Last updated” date above identifies the latest revision.

Contact

For privacy questions or requests, contact Adstar Labs: