> For the complete documentation index, see [llms.txt](https://docs.sentiance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sentiance.com/important-topics/faq.md).

# FAQ

Welcome to the Sentiance FAQ. Here you’ll find answers to common questions about integrating and using the Sentiance SDK and products. This section helps you understand key capabilities, resolve issues, and ensure a smooth implementation.

#### Sentiance SDK

<details>

<summary><strong>What is the Sentiance SDK?</strong></summary>

The Sentiance SDK runs quietly in the background of your mobile app and uses the phone's sensors — GPS, accelerometer, gyroscope — to automatically detect and classify trips, driving behavior, and transport modes. \
\
From this raw data, it produces insights like:

* Driving Insights
* Mobility Insights
* Lifestyle Insights
* Crash Insights

</details>

<details>

<summary><strong>Which driving scores and insights are available?</strong></summary>

On-device, the SDK produces primary scores (legal, smooth, focus, overall).

Crash detection, phone usage events, harsh driving events, and transport classification are also available. Engagement features like streaks and challenges run in the cloud and are accessible via API.

</details>

<details>

<summary><strong>Does Sentiance support crash detection?</strong></summary>

Yes. Our crash detection runs on-device and analyzes motion and GPS data to identify sudden impact events. When a crash is detected, the SDK surfaces it with severity, magnitude, speed, and delta-v fields. Clients can trigger in-app notifications or post-crash workflows using this data.

</details>

<details>

<summary><strong>What is the minimum trip length required for scoring?</strong></summary>

A trip must be at least 2 km in distance and 3 minutes in duration, and the intiial geofence must be broken for driving scores to be computed.&#x20;

Short trips below these thresholds will not produce scoring results.

</details>

<details>

<summary><strong>How long do we retain trip data on the SDK?</strong></summary>

Data is retained for 9 weeks in on-device.

</details>

<details>

<summary><strong>Are there rate limits on API usage?</strong></summary>

There are no enforced rate limits on the API. You can send and retrieve data without predefined caps on requests or event volume.

</details>

#### Detections

<details>

<summary><strong>What is the minimum requirement for optimal detection for a trip?</strong></summary>

**I have installed the app less than 3 days ago** Our platform needs a certain amount of data before we can start identifying your events, moments & segments correctly. Please make sure you've been tracking with the permissions set correctly for at least a few days. Specific venues, like home and work, could take up to a week to detect correctly.

**I have installed the app more than 3 days ago** Make sure your device has the required specifications. The device must have an accelerometer at the least and it is best if it also has a gyroscope present. Make sure you've given the right [permissions](https://docs.sentiance.com/a-complete-integration/android-sdk/permissions).

Also, specific android devices may require whitelisting. If none of this works or you need more information, contact <support@sentiance.com> for assistance.

</details>

<details>

<summary><strong>Why is a trip incorrectly or not at all detected?</strong></summary>

When a trip is incorrectly detected or not detected at all, it might be because:

* The phone was in flight mode during the trip.
* The trip was very short in duration (< 3 min).
* The trip was very short in distance (< 2 km or 1.25 mi).
* The phone was in battery-saving mode during the trip.
* The app did not get the required permissions (always-on) during the trip.

</details>

<details>

<summary><strong>Why was phone usage falsely detected during a trip?</strong></summary>

Our algorithm that detects phone usage while driving might sometimes detect phone usage when the phone is moving in the pocket while driving, or when it hits a sequence of speed bumps. We optimize for precision. i.e. it should happen less than 10% of the time.

</details>

#### Insights Control Tower (ICT)

<details>

<summary><strong>What is the Insights Control Tower?</strong></summary>

The Insights Control Tower (ICT) is Sentiance's web-based client portal where you can view and monitor the data collected by the SDK — including trips, driving insights, and active user activity across your project.

</details>

<details>

<summary><strong>How is an Monthly Active User (MAU) defined?</strong></summary>

Monthly Active Users (MAU) are defined based on the following criteria:

* The Sentiance SDK is initialized within the user’s app
* The user has granted all required permissions
* At least one transport has been recorded in the specific month

</details>

<details>

<summary><strong>How long does an admin user exist on the ICT Admin page?</strong></summary>

User accounts remain active indefinitely. However, to comply with our privacy and security policies:

* If an account is inactive for **3 months**, all assigned roles will be removed.
* If an account remains inactive for **6 months**, it will be permanently deleted.

</details>

<details>

<summary><strong>How long do we retain trip data on ICT?</strong> </summary>

The Insights Control Towers (ICT) stores data for 90 days.

</details>

#### Integration

<details>

<summary><strong>Which mobile platforms do you support?</strong></summary>

We support both Android and iOS. Both platforms support React Native, Flutter, and native development frameworks

</details>

<details>

<summary><strong>What permissions does my app need to ask users for?</strong></summary>

**Location and Background permission set to Always Allow** is required for the SDK to detect trips.&#x20;

Motion/activity permissions are recommended for improved detection accuracy but are not strictly mandatory.

</details>

<details>

<summary><strong>How do I receive events during start and end of a trip?</strong></summary>

Please look into the [Implementing Features](/implementing-features/insights.md) page. Each page includes a dedicated section for “Subscribe” events.

</details>

<details>

<summary><strong>How do I stop the SDK from tracking a user?</strong></summary>

The SDK has a built-in enable/disable detection functionality, that can be used to manually stop the SDK from tracking when certain parameters are met. You can find more information [here.](https://docs.sentiance.com/sdk/appendix/controlled-detections)

</details>

#### Security, Privacy and Terms of Service

<details>

<summary><strong>Where can I find the terms of service for using Sentiance products?</strong></summary>

Navigate to the following pages to see the Terms of Service for each of our respective products.

[SDK Standard License<br>](https://www.sentiance.com/terms/sdk-standard/)[Journeys License](https://www.sentiance.com/terms/journeys/)\
[Insights-by-Sentiance License](https://www.sentiance.com/data-privacy/journeys-privacy-policy/)

</details>

<details>

<summary><strong>How do I make sure all data of a specific user is removed from the Sentiance platform?</strong></summary>

If a specific user's data needs to be permanently removed from the Sentiance platform (i.e. after receiving a GDPR data removal request), please contact <support@sentiance.com>.

</details>