Play Store Data Security | ClearSale Docs

Privacy and Security

The Google PlayStore requests that the application made available clearly share which information is collected from the user. To achieve this goal, each application must complete a data security form on privacy and security practices.

Every developer who has an application published on Google Play needs to complete the Data Security form. This includes internal, closed, open, or production testing range applications.

Important

Starting in February 2022, Play Store users have access to the "Data Security" section. Therefore, privacy policies and data security forms are required for all application updates and new application submissions.

Requirements

Your answers must follow Google Play's user data policy and any applicable regulations.

You are entirely responsible for keeping your answers accurate and up-to-date. If your practices change, remember to update your answers on Google Play.

What you need to know

We recommend that you review the Google Play guidelines and submit the Data Security form as soon as possible. This ensures that you can receive feedback and make necessary changes before a rejected form prevents you from publishing new app updates.

To learn more about Clearsale's privacy policies and end-user opinions, check out the Clearsale Privacy Policy.

Data Collection

To complete the Data Security form, it is necessary to have knowledge of the data collected by the application, such as those from external partners, including the Clearsale Fingerprint SDK.

The Clearsale Fingerprint SDK is configurable in terms of which data we collect for you. This means that you are choosing, for the most part, the data that the Clearsale Fingerprint SDK can access in your application based on how you have configured and implemented the SDK code.

Play Store Form

When submitting your application for approval, the Google Play Store will require you to fill out a form that should be answered as indicated in this documentation.

The collection of additional information and responses that differ from what is indicated is the sole responsibility of the user.

We recommend that you review the Google Play guidelines and submit the Data Security form as soon as possible. This ensures that you can receive feedback and make necessary changes before a rejected form prevents you from publishing new app updates.

Data Collection by Type

The following table lists the different types of data and indicates which ones are collected by the Clearsale Fingerprint SDK by default. However, please compare them with your specific Clearsale Fingerprint SDK configuration and your data collection practices in your application to confirm if your answers are correct.

For example: The Clearsale Fingerprint SDK does NOT collect "Personal Information" by default. However, if your application collects email addresses from users (or any other type of personal information) and sends that data to the Clearsale Fingerprint SDK using custom parameters, then you should answer "Yes" to that field in the form. This is because the Clearsale Fingerprint SDK will be collecting personal information that you send to your specific application, including if the email address is encrypted.

In the table below, you can see which data the Clearsale Fingerprint SDK collects or does not collect by default. In instances where the data types are marked as "Yes" or "Optional", you can see exactly how the SDK handles that data in the items below.

Tipo de dados

Category	Data Type	Description	Purpose	Collected by SDK?
Location	Approximate location	It is the physical location of the user or device in an area equal to or greater than three square kilometers, such as the city they are in or the location provided by the Android ACCESS_COARSE_LOCATION permission.	Fraud prevention	Yes, Optional
Location	Exact location	It is the physical location of the user or device in an area less than three square kilometers, such as the location provided by the Android ACCESS_FINE_LOCATION permission.	Fraud prevention	Yes, Optional
Personal information	Name	It is how a user refers to themselves (first name, last name, or nickname).		No
	Email address	It is the user's email address.		No
	User IDs	They are identifiers related to a specific person, such as ID, account number, or name.		No
	Address	It is the user's address, such as a residential or mailing address.		No
	Phone number	It is the user's phone number.		No
	Race and ethnicity	They are information about the user's race or ethnicity.		No
	Political affiliation or religious beliefs	These are information about the user's religious beliefs or political affiliation.		No
	Sexual orientation	These are information about a user's sexual orientation.		No
	Other information	Any other personal information, such as date of birth, gender identity, veteran status, etc.		No
Financial information	User payment information	These are user financial information, such as credit card number.		No
	Purchase history	These are information about purchases or transactions made by the user.		No
	Credit score	These are information about a user's credit score.		No
	Other financial information	These are other financial information, such as user salaries or debts.		No
Health and fitness	Health information	Information about the user's health, such as medical history or symptoms.		No
Health and fitness	Fitness information	Information about the user's fitness, such as what exercises or physical activities they engage in.		No
Messages	Emails	The user's emails, including subject, sender, recipients, and email content.		No
	SMS or MMS	The user's text messages, including sender, recipients, and message content.		No
	Other in-app messages	Any other types of messages. For example, instant messages or chat content.		No
Photos and videos	Photos	The user's photos.		No
Photos and videos	Videos	The user's videos.		No
Audio files	Voice or sound recordings	The user's voice, such as a voicemail or sound recording.		No
	Music files	The user's music files.		No
	Other audio files	Any other audio files created or provided by the user.		No
Files and documents	Files and documents	The user's files or documents or information related to them, such as file names.		No
Calendar	Calendar events	Information from the user's calendar, such as events, event notes, and guests.		No
Contacts	Contacts	These are user contact information. For example: names, message history, and social graph data such as user names, time to return, frequency of contact, interaction duration, and call history.		No
App activity	In-app interactions	These are information about how the user interacts with the app. For example: the number of times they access a page or the sections they tap on.		No
	In-app search history	These are information about how the user used search within the app.		No
	Installed apps	These are information about the apps installed on the user's device.	Fraud prevention	Yes, Optional
	Other user-generated content	Includes any other user-generated content not listed here or in other sections. For example: user biographies, notes, or open-ended responses.		No
	Other actions	These are any other user activities or actions within the app not listed here, such as game sessions, likes, and dialog box options.		No
Web browsing	Web browsing history	These are information about the websites the user visited.		No
App information and performance	Crash logs	These are app crash log data. For example, the number of times the app crashed, stack traces, or other information directly related to a crash.	Analysis	Yes
	Diagnosis	These are information about the app's performance. For example: battery life, loading time, latency, frame rate, or any technical diagnosis.	Fraud prevention	Yes
	Other app performance data	Includes any other app performance data not listed here.		No
Device identifiers and others	Device identifiers and others	These are identifiers that relate to a specific device, browser, or app. For example: IMEI numbers, MAC addresses, Widevine device IDs, Firebase installation IDs, or advertising identifiers.	Fraud prevention	Yes