> 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/ios/standalone-modules/cafsmartauth.md).

# Smart Auth

The CafSmartAuth SDK enables seamless and secure user authentication by dynamically adapting to backend-driven policy rules. The backend specifies which authentication methods—such as live facial verification, SMS, or email—should be requested, allowing you to integrate flexible and configurable authentication policies directly into your iOS applications.

## Terms & Policies

When using our SDKs, please ensure 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).

## Installation

Refer to this [Documentation](/caf-sdk/ios/standalone-modules/cafsmartauth/installation.md)

## SDK Dependencies

CafSmartAuth leverages the following external SDKs:

| SDK                     | Version |
| ----------------------- | ------- |
| `FaceLiveness`          | 7.3.0   |
| `iProov Biometrics iOS` | 13.1.0  |
| `Fingerprint Pro iOS`   | 2.7.0   |
| `CafSolutions`          | 2.0.5   |

* [Faceliveness](https://github.com/combateafraude/Faceliveness): Enables the integration of live facial verification technology for secure user authentication.
* [iProov Biometrics iOS](https://github.com/iProov/ios): Dependency of Faceliveness SDK for facial verification
* [Fingerprint Pro iOS](https://github.com/fingerprintjs/fingerprintjs-pro-ios): Provides fingerprint authentication capabilities to enhance security in your app.
* [Rudderstack](https://www.rudderstack.com/docs/): Provides user metrics to deliver trustworthy real-time data.
* [CafSolutions](https://github.com/combateafraude/CafSolutions): Package of common solutions for the Caf\`s Framework

**Important:** If you plan to publish your app on the *Apple App Store*, you must include the SDK data usage in your App Store privacy disclosures. Since we integrate with the *FingerprintJS SDK*, here’s the information you need to provide:

| Privacy Disclosure in Apple App Store | Response                                   |
| ------------------------------------- | ------------------------------------------ |
| Data collected                        | Device or other identifiers                |
| Purpose                               | Fraud Prevention, Security, and Compliance |
| Usage type                            | Collected but not shared                   |
| Processing                            | Processed ephemerally                      |

### Runtime Permissions

| Permission   | Reason                                                     | Required |
| ------------ | ---------------------------------------------------------- | :------: |
| CAMERA       | Capturing the selfie in live facial verification policies. |     ✅    |
| LOCALIZATION | Capturing the location of the device for context rules     |     ✅    |

For [permission details](https://docs.caf.io/caf-sdk/ios/standalone-modules/pages/GvE4o4wWX8N4FTWBmIwZ#id-3.-what-permissions-are-required-to-use-the-sdk)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.