> ## Documentation Index
> Fetch the complete documentation index at: https://docs.privy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy declaration

> Understand the Privy Swift SDK privacy manifest and its App Store privacy nutrition label values.

Privy's Swift SDK privacy declaration describes data used for authentication, embedded wallets, and SDK analytics. This guide explains how those behaviors map to Apple's App Store privacy nutrition labels.

> [!NOTE]
>
> The declarations on this page are the full set of data types the SDK may handle. What an app
> actually collects depends on how it uses Privy, such as the login methods and wallet features it
> enables. Base the app's disclosures on its actual usage.

## Privacy manifest and App Store labels

Apple's [privacy manifest](https://developer.apple.com/documentation/bundleresources/privacy-manifest-files) is a machine-readable `PrivacyInfo.xcprivacy` file. It declares collected data, tracking practices, and reasons for accessing certain system APIs.

The App Store privacy nutrition label is the user-facing summary configured in **App Store Connect > App Privacy**. The SDK manifest informs that summary; it does not replace the app's privacy disclosures.

> [!WARNING]
>
> The values below describe Privy's SDK declaration, not the entire app. The app's disclosures must
> also account for its own data collection, backend services, and other third-party SDKs. Review the
> manifest in the exact SDK version included in the app, since declarations can change between
> releases.

## Declared data types

The declaration marks every data type below as **linked to the user's identity** and **not used for tracking**.

| App Store category | Data type | Declared purposes | SDK behavior |
| - | - | - | - |
| Identifiers | Device ID | Analytics, App functionality | The SDK generates an app-scoped client analytics ID, persists it in `UserDefaults`, and sends it with Privy requests and analytics events. |
| Identifiers | User ID | Analytics, App functionality | Privy user IDs identify authenticated accounts and associate authentication and wallet activity with those accounts. |
| Contact info | Name | App functionality | Google, Apple, X (Twitter), and Telegram login can supply a name as part of the user's linked account profile. |
| Contact info | Email address | App functionality | Email login and account linking use email addresses. Supported social login providers can also supply an email address. |
| Contact info | Phone number | App functionality | SMS login and account linking use phone numbers to deliver verification codes and identify the linked account. |
| Financial info | Other financial info | App functionality | Embedded wallets and linked external wallets associate wallet addresses with the user's account. Wallet operations use wallet and transaction information. |
| Diagnostics | Other diagnostic data | Analytics, App functionality | SDK initialization analytics include the operating system and version, plus the host app's Xcode build version when available. Privy requests also identify the SDK platform and version. |

Contact information depends on the login methods enabled by the app and the information supplied by the provider. Declaring a data type does not mean every user supplies it or every SDK call collects it.

### Device ID does not mean advertising ID

The client analytics ID is a randomly generated UUID, not Apple's advertising identifier (IDFA).

### Linked data is different from tracking

**Linked to the user** means the data can be associated with a user's identity or account. For example, a wallet address or email address is part of a Privy user account. Authenticated requests also carry the client analytics ID, so the declaration treats that identifier as linked rather than anonymous.

**Tracking** has a separate [Apple-defined meaning](https://developer.apple.com/app-store/user-privacy-and-data-use/), including linking app data with third-party data for targeted advertising or advertising measurement.

The declaration sets:

* `NSPrivacyTracking` to `false`.
* `NSPrivacyTrackingDomains` to an empty array.
* `NSPrivacyCollectedDataTypeTracking` to `false` for all seven data types.

These values describe Privy's practices. They do not determine whether another part of the app performs tracking or requires App Tracking Transparency permission.

### Analytics and app functionality

**App functionality** covers providing authentication, maintaining accounts, and enabling wallet operations.

**Analytics** covers understanding SDK usage and the environments where it runs. The SDK sends analytics events that include the client analytics ID and environment metadata.

## Required-reason API access

The SDK uses `UserDefaults.standard` to store its client analytics ID. It declares `NSPrivacyAccessedAPICategoryUserDefaults` with reason **`CA92.1`**: accessing preferences only accessible to the app itself.

This API-access reason is separate from the Device ID collection entry, which covers transmitting the identifier. Apple lists approved reasons in [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/describing-use-of-required-reason-api).

## Prepare App Store disclosures

1. Review `PrivacyInfo.xcprivacy` in the SDK version used by the app. Confirm that the manifest is included in the archived app's SDK resources.
2. Generate a privacy report for the app archive in Xcode Organizer. Review the combined declarations from the app and its dependencies.
3. Use the data types, purposes, linkage, and tracking values above to inform the app's **App Privacy** responses in App Store Connect.
4. Include any additional collection or tracking performed by the app, its backend, and other dependencies. Keep the app's privacy policy consistent with those practices.

For Apple's definitions and submission guidance, refer to [App privacy details on the App Store](https://developer.apple.com/app-store/app-privacy-details/).
