> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-sdk/android/standalone-modules/cafsmartauth.md).

# Smart Auth

Enables you to integrate live facial verification and fingerprint authentication technology into your Android applications, offering a seamless and secure way to authenticate users.

The CafSmartAuth SDK provides configurable policies, allowing you to integrate live facial verification, SMS and e-mail into your Android applications, offering a seamless and secure way to authenticate users.

## Terms & Policies

When using our SDKs, please make sure that you agree with our [Privacy Policy](https://en.caf.io/politicas/politicas-de-privacidade) and our [Terms and Conditions of Use](https://en.caf.io/politicas/termos-e-condicoes-de-uso).

## SDK Dependencies

CafSmartAuth leverages the following external SDKs:

| SDK                         | Version |
| --------------------------- | ------- |
| `Caf FaceLiveness`          | 4.1.1   |
| `iProov Biometrics Android` | 9.1.2   |
| `Fingerprint Pro Android`   | 2.7.0   |

* [iProov Biometrics Android](https://github.com/iProov/android): Enables the integration of live facial verification technology.
* [Fingerprint Pro Android](https://github.com/fingerprintjs/fingerprintjs-pro-android): Provides fingerprint authentication capabilities to enhance security features in your app.
* [Rudderstack](https://www.rudderstack.com/docs/): Provides user metrics to deliver trustworthy real-time data.

**Important:** If you plan to publish your app on the *Google Play Store*, you must complete a data safety form. Since we integrate with the *FingerPrintJS SDK*, you'll need to provide the following information:

| Question in Google Play Console's data safety form                  | Response                                    |
| ------------------------------------------------------------------- | ------------------------------------------- |
| Does your app collect or share any of the required user data types? | Yes.                                        |
| What type of data is collected?                                     | Device or other identifiers.                |
| Is this data collected, shared, or both?                            | Collected.                                  |
| Is this data processed ephemerally?                                 | Yes.                                        |
| Why is this user data collected?                                    | Fraud Prevention, Security, and Compliance. |

### Runtime Permissions

| Permission             | Reason                                                                                    | Required |
| ---------------------- | ----------------------------------------------------------------------------------------- | :------: |
| CAMERA                 | Capturing the selfie in live facial verification policies.                                |     ✅    |
| INTERNET               | Internet connection is needed in order to the authentication workflow work.               |     ✅    |
| ACCESS\_FINE\_LOCATION | Provides precise location data, required for location-based services in the verification. |     ✅    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/caf-sdk/android/standalone-modules/cafsmartauth.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.