Verisoul iOS SDK – App Store Privacy Manifest Instructions

Last updated: May 18, 2025

Beginning May  2024 Apple rejects any build whose App Privacy answers or Privacy Manifest don’t line up with the data that your app or any embedded SDK collects. The Verisoul iOS SDK already ships with its own manifest, but you still have to finish a few check‑boxes in App Store Connect.

1. Include Verisoul Privacy Manifest

  • Use Verisoul iOS SDK 

  • In Build Phases ▸ Copy Bundle Resources confirm VerisoulPrivacyManifest.plist is listed.
    No edits required - just include it.

<!-- excerpt (already inside the SDK) -->
<key>NSPrivacyTracking</key>               <false/>
<key>NSPrivacyCollectedDataTypes</key>
  <array>
    <dict>
      <key>NSPrivacyCollectedDataType</key>
      <string>NSPrivacyCollectedDataTypeDeviceID</string>
      <key>NSPrivacyCollectedDataTypePurposes</key>
      <array><string>NSPrivacyCollectedDataTypePurposeAppFunctionality</string></array>
    </dict>
  </array>
<key>NSPrivacyAccessedAPITypes</key>
  <array>
    <dict>
      <key>NSPrivacyAccessedAPIType</key>
      <string>NSPrivacyAccessedAPICategorySystemBootTime</string>
      <key>NSPrivacyAccessedAPITypeReasons</key>
      <array><string>35F9.1</string></array>
    </dict>
  </array>

(This satisfies Apple’s “Required‑Reason API” declaration.)

2. App Store Connect ▸ App Privacy

Question

What to pick

Does your app collect data?

Yes

Is data used to track users?

No (Verisoul doesn’t track across apps)

Is data linked to the user?

No

3. Add exactly these four rows 

For every row below set: Collected = Yes • Linked = No • Tracking = No • Purpose → App Functionality → Security & Fraud Prevention

Apple Data Bucket

When to include

Identifiers ▸ Device ID (IDFV)

Always

Usage Data ▸ Product Interaction

Always

Diagnostics ▸ Other diagnostic data

Always

Location ▸ Precise / Approximate

Only if your app already requests Core Location permission

(Do not add Contact Info, Health, Financial, etc. unless your app already uses them; Verisoul never touches them.)

4  Save & submit

  1. Review the four rows in the summary table.

  2. Upload the build and press Submit for review.

If Apple flags something

Review Note

Potential Cause

Fix

“Missing privacy manifest for required‑reason API.”

The plist was stripped from the bundle.

Re‑add VerisoulPrivacyManifest.plist to Copy Bundle Resources.

“Tracking flag required.”

A row is set to Linked = Yes or you ticked “Ads.”

Reset Linked / Tracking to No.

“Undeclared data type: Device ID.”

You skipped the Identifiers row.

Add Identifiers ▸ Device ID.

Need help? Send the rejection note and your build number to support@verisoul.ai.

That’s it. Keep the manifest file, fill the four check‑boxes, and your Verisoul‑enabled iOS app remains 100 % compliant with Apple’s May 2024 privacy rules.