Example of Bootstrap 3 Accordion

Please give permission for us to collect app diagnostics and crash reports. This will help us to help you.

We only use this information to help fix crashes and to understand how people use the app. We won’t share it with anyone else.

Privacy Policy

We want you to get the most from Afleet. To do that we collect some information about your usage. This policy describes what we collect, and how we will (and won’t) use that information.

Information about crashes

We work very hard to keep crashes to an absolute minimum. If your app crashes we want to know about it, so we can find the problem and release fixes. We use Firebase Crashlytics to collect:

  • Crashlytics Installation UUIDs (Unique Identifiers)
  • Crash Traces
  • Breakpad minidump formatted data (NDK crashes only)
  • How it helps: Firebase Crashlytics uses crash stack traces to associate crashes with a project, send email alerts to us and display them in the Firebase Console, and help us debug crashes. It uses Crashlytics Installation UUIDs to measure the number of users impacted by a crash and minidump data to process NDK crashes. The minidump data is stored while the crash session is being processed and then discarded.

    Retention: Firebase Crashlytics retains crash stack traces, extracted minidump data, and associated identifiers (including Crashlytics Installation UUIDs) for 90 days.

    Under normal circumstances we won’t know who the user was, at the time of the crash. But if you contact us for help, we may use additional information that you supply to identify which crash came from your device.

    We will not use information collected to send you promotional material.

    Note: parts of this section have been extracted from Privacy and Security in Firebase. Please visit that page for more details. “Examples of stored device information” (on that page) illustrate the types information collected.