Location |
Approximate location |
User or device physical location accurate to within an area greater than or equal to three square kilometers, such as the city a user is in, or location provided by Android’s ACCESS_COARSE_LOCATION permission. |
No |
Yes.
If you have configured to transmit this data type, respond accordingly. CleverTap Android SDK starting v3.1.9 and above (released in May 2018) has stopped tracking approximate location by default. Approximate location is captured only if the Device Network Information Reporting is enabled. |
|
Precise location |
User or device physical location accurate to within an area less than three square kilometers, such as location provided by Android’s ACCESS_FINE_LOCATION permission. |
No |
Yes.Precise Location is captured only if the user integrates the CleverTap GeoFencing SDK. |
Personal info |
Name |
The way users refer to themselves, such as their first or last name, or nickname. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Email address |
The user’s email address. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
User IDs |
Identifiers that relate to an identifiable person. For example, an account ID, account number, or account name. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Address |
The user’s address, such as a mailing or home address. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Phone number |
The user’s phone number. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Race and ethnicity |
Information about the user’s race or ethnicity. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Political or religious beliefs |
Information about the user’s political or religious beliefs. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Sexual orientation |
Information about the user’s sexual orientation. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other info |
Any other personal information, such as date of birth, gender identity, veteran status, and so on. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Financial info |
User payment info |
Information about the user’s financial accounts, such as credit card number. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Purchase history |
Information about purchases or transactions a user has made. |
No |
Yes.If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Credit score |
Information about the user’s credit score. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other financial info |
Any other financial information such as user salary or debts. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Health and fitness |
Health info |
Information about the user’s health, such as medical records or symptoms. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Fitness info |
Information about the user’s fitness, such as exercise or other physical activity. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Messages |
Emails |
The user’s emails, including the email subject line, sender, recipients, and the content of the email. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
SMS or MMS |
The user’s text messages including the sender, recipients, and the content of the message. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other in-app messages |
Any other types of messages. For example, in instant messages or chat content. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Photos or videos |
Photos |
The user’s photos. |
No |
No. |
|
Videos |
The user’s videos. |
No |
No. |
Audio files |
Voice or sound recordings |
The user’s voice such as a voicemail or a sound recording. |
No |
No. |
|
Music files |
The user’s music files. |
No |
No. |
|
Other audio files |
Any other user-created or user-provided audio files. |
No |
No. |
Files and docs |
Files and docs |
The user’s files or documents, or information about their files or documents such as file names. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Calendar |
Calendar events |
Information from a user’s calendar such as events, event notes, and attendees. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Contacts |
Contacts |
Information about the user’s contacts such as contact names, message history, and social graph information such as usernames, contact recency, contact frequency, interaction duration, and call history. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
App activity |
App interactions |
Information about how users interact with the app. For example, the number of times they visit a page or the sections that they tap on. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
In-app search history |
Information search performed by the user in your app. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Installed apps |
Information about the apps installed on the user’s device. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other user-generated content |
Any other user-generated content not listed here, or in any other section. For example, user bios, notes, or open-ended responses. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other actions |
Any other user activity or actions in-app not listed here such as gameplay, likes, and dialog options. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Web browsing |
Web browsing history |
Information about the websites that a user has visited. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
App info and performance |
Crash logs |
Crash log data from user’s app. For example, the number of times your app has crashed, stack traces, or other information directly related to a crash. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Diagnostics |
Information about the performance of your app. For example battery life, loading time, latency, framerate, or any technical diagnostics. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
|
Other app performance data |
Any other app performance data not listed here. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |
Device or other IDs |
Device or other IDs |
Identifiers that relate to an individual device, browser,
or an app. For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or advertising identifier. |
No |
Yes.
If you have configured to transmit this data to CleverTap, respond accordingly. |