Pathly Privacy Policy

1. Information collected automatically

Pathly does not ask you to provide a name, email address, account details, contacts, photographs, recordings, or precise GPS location. It does, however, use Firebase Analytics and Firebase Crashlytics. When those services operate, technical, usage, and diagnostic information is sent to Google rather than remaining only on your device.

Depending on the event and device, this information may include an app-instance or installation identifier, session information, timestamps, app version, operating system, device model or category, language, screen or activity class, engagement information, approximate geographic region derived from network information, and crash-related diagnostics. These identifiers identify an app installation and are not an account or a name supplied by you.

2. Firebase services used

Pathly initializes Firebase and uses Firebase Analytics to measure app use and Firebase Crashlytics to diagnose fatal errors. Crashlytics receives fatal Flutter framework errors and uncaught asynchronous errors recorded by the app.

The audited source does not implement Firebase Performance Monitoring, Remote Config, Cloud Messaging, Authentication, Firestore, Realtime Database, Cloud Storage, App Check, or another Firebase product. Firebase Installations is included transitively to support Firebase services; Pathly does not directly retrieve or expose its installation ID.

3. Analytics and event tracking

Firebase Analytics collection starts with Firebase initialization. Pathly does not provide an in-app analytics switch or consent control. Analytics may automatically record events such as first use, sessions, user engagement, app updates, screen or activity information, and app exceptions.

Pathly also sends two categories of custom events to understand feature engagement and improve gameplay and usability:

• Sharing interaction: a tap on the Share Pathly button. The event has no custom parameter.
• Level completion: the level identifier, season number, level number, move count, and completion time in seconds.

4. Crash and diagnostic data

Crashlytics may process crash timestamps, stack traces, relevant application state, app identifier and version, Crashlytics and Firebase installation identifiers, session identifiers, device model, operating-system details, processor architecture, memory and disk information, device orientation, and rooted or jailbroken status. Analytics events from the same session may also appear as Crashlytics breadcrumbs, including the custom event parameters described above.

Pathly does not set a Crashlytics user ID or add names, email addresses, contact details, or other profile fields to crash reports. Firebase Performance Monitoring is not included, so Pathly does not use that service to collect performance traces or network-performance metrics.

5. Why this information is processed

Damo Studio uses the Firebase information to understand app and session usage, measure sharing and level engagement, evaluate puzzle difficulty and completion patterns, improve gameplay and usability, diagnose crashes and technical problems, and improve app stability. It is not used by Pathly to create an account or player profile.

6. Data stored on your device

Pathly stores completed level identifiers, best move counts, and best completion times in local app preferences so it can display progress and personal records. This local progress is not included in the custom Firebase events as a complete saved profile, although individual level completions and their measurements are sent when they occur.

7. Networking and data sharing

Pathly communicates with Google/Firebase for Analytics and Crashlytics. Google generally handles Firebase customer data as a data processor or service provider under the applicable Firebase terms. Google may use subprocessors to provide these services. Damo Studio does not sell Pathly data.

On Android, the Share Pathly action opens the operating system's sharing interface with fixed promotional text and a Google Play link. Pathly does not read your contacts or share history and does not attach gameplay data. Any further handling is controlled by the app and recipient you choose.

8. Advertising and ad personalization

Pathly contains no advertising SDK or AdMob integration and does not display ads. Its Android configuration removes the advertising-ID permission and disables Google Analytics advertising-ID collection. The app does not set analytics user properties for ad personalization.

Firebase or Google Analytics console settings and account links are controlled outside the app and cannot be verified from the source code. Pathly's source therefore does not establish that every server-side advertising feature is disabled.

9. Accounts and device permissions

Pathly has no account creation or login. Its release manifest does not request access to contacts, camera, microphone, photos or media, precise location, or notifications. The app has no uploads, forms, or purchases.

10. Children and general audience

Pathly is intended for a general audience of all ages. It does not ask children or adults to submit personal information, but Firebase identifiers, usage information, and diagnostics are processed automatically as described above. Pathly has no age gate or child-specific analytics consent flow. This policy does not claim compliance with any particular child-privacy law or app-store program.

11. Retention and deletion

Local progress remains until app storage is cleared or Pathly is uninstalled; operating-system backups may retain a copy under the platform provider's rules. Clearing storage or uninstalling stops that installation from sending future data, but it does not by itself delete Analytics events or crash reports already processed by Google.

Google Analytics retention for user-level and event-level data is controlled in the Analytics property and may differ from retention of aggregated reports. Crashlytics documentation states that crash stack traces, extracted crash data, and associated identifiers are retained for 90 days before removal begins. Pathly does not implement an in-app Firebase installation deletion or Analytics data-deletion function, and this policy does not promise deletion of already processed remote data on request.

12. International processing

Google's Firebase Data Processing and Security Terms state that customer data may be processed in countries where Google or its subprocessors maintain facilities, subject to applicable data-location commitments and transfer safeguards.

13. Security

Damo Studio limits custom analytics to the gameplay and sharing fields listed above and does not attach a user account to them. Google describes technical and organizational safeguards for Firebase data. No transmission or storage system can be guaranteed completely secure.

14. Changes to this policy

Damo Studio may update this Privacy Policy if Pathly's features, Firebase configuration, or data practices change. The updated policy will be published on this page with a revised effective date.

15. Contact

For questions about this Privacy Policy or Pathly's privacy practices, contact Damo Studio.

[email protected]