Nami Public Documentation
Sign In
Nami Documentation
Nami Documentation
  • Get Started
    • Overview
      • Key Concepts
      • Data Collection
      • Built for Privacy
    • Evaluating Nami
    • SDKs
      • Apple Native SDK
      • Android Native SDK
      • Amazon Native SDK
      • Roku Native SDK
      • React Native Cross-Platform SDK
      • Flutter Cross-Platform SDK
      • Unity Cross-Platform SDK
      • Release Notes
        • Find Nami SDK Version
    • Quickstart Guide
  • Subscription Management
    • Overview
    • Products
      • Archive Products
      • Sync Products
    • Entitlements
    • Customer Screen
    • Accounts and Login/Logout
    • Advanced Use Cases
      • Upgrades and Downgrades
      • Supported Purchase Change States by Platform
      • Restoring Purchases
      • Working with Consumable IAPs
  • No Code Paywalls
    • Overview
    • Paywall Creator
      • Using the Creator
      • Paywall Layout
      • Components
        • Editing, Deleting, Reordering
        • Hiding Components
        • Video
        • Collapse
      • Editable Properties
        • Focused Styling
        • Safe Area
      • Conditions
        • Notched Devices
        • Product Entitlements
      • Adding Products
      • Repeating Product Group
      • Product Fields
      • Capabilities
        • Featured Styling
        • Selected Styling
        • Custom Brand Fonts
        • Carousel
        • Trial Eligibility
        • Deeplink Button
        • Introductory Offer Eligibility
        • Login Check
        • Product Groups
        • Conditional Product Groups
        • Offer Eligibility and Purchasing
        • Screenreader Text
        • Personalization Tokens
        • Custom Variables
        • Multipage
        • Custom Data Source
        • Advanced Video Features
        • Product Error States
      • ❓FAQs
        • Designing Paywalls in Figma
        • Guide to Building a Paywall from Scratch
      • 🎁Releases
        • Roadmap
    • Paywall Templates
      • Pacific
      • Pacific Premium
      • Trident
      • Starfish
      • Mantis
      • Venice
      • Venice Premium
      • Honest
      • Catalina
      • Oyster
      • Puffin
      • Marina
      • Beluga
      • Driftwood
      • Lagoon
      • Pisces
      • Aquarius
      • Conch
      • Lionfish
      • Moray
      • Tetra
      • Lighthouse
      • Puffin Tablet
    • Managing Paywalls
      • Archiving a Paywall
      • Duplicate a Paywall
    • Paywall Smart Text
    • Pricing Eligibility States
    • Pricing Eligibility by Platform
    • Nami Paywalls in Different Languages
    • Legacy Paywalls
  • Campaigns
    • Placements
      • Create a Placement
      • Deeplink Placements
      • Archiving a Placement
      • Managing Lots of Placements
      • Export Placements
    • Campaigns
      • Campaign Filters
        • Campaign Use Cases
      • Archiving a Campaign
      • Scheduling a Campaign
      • Campaign Conversion Events
      • Managing Lots of Campaigns
      • Campaign Troubleshooting
    • A/B and Multivariate Testing
      • Selecting an A/B test winner
      • A/B Test Allocation
  • Integrations
    • All Integrations
    • Billing Platforms
      • Apple Integration
        • App Store Setup
          • Privacy Details
        • Platform Integration
        • App Store Server Notifications
        • Store Credentials
          • App Store Connect Shared Secret
          • Apple App Store Connect API
          • Apple In App Purchase
        • Add a Product
        • Platform Sync
        • SDK Integration
        • Troubleshooting
        • Testing and Development
          • Apple Testing Environments
          • Setting up Device Sandbox Test Environment
          • Setting up StoreKit config in Xcode
      • Google Integration
        • Google Play Store Setup
        • Platform Integration
        • Service Account
        • Real-time Developer Notifications
        • Add a Product
        • Platform Sync
        • SDK Setup
        • Troubleshooting
          • Supporting Android minSdkVersion 25 or lower
          • Requested product is not available for purchase
          • Unsupported Version of Play Billing
      • Amazon Appstore Integration
        • Create Amazon Android App
        • Platform Integration
        • Shared Key
        • Real-time Event Notifications
        • Add a Product
        • SDK Integration
        • Testing
      • Roku Integration
        • Platform Integration
        • API Key
        • Transaction Notifications
        • Add a Product
        • SDK Integration
      • Web Integration
    • Analytics Tools
      • Adobe Analytics
      • Amplitude
      • Google Analytics
      • mParticle
      • 3rd-Party Analytics
    • Subscription Management
      • Nami Subscription Management
      • Bring your Own Payment Code
    • CDP Integrations
      • Adobe CDP Integration
      • Amplitude CDP Integration
      • Custom CDP Integration
      • Generic CDP Integration
    • Other Integrations
      • Wicket Labs
      • Webhooks
        • Introduction to the Nami ML Event System
        • Event Types
          • Purchase Status Updates
          • Events for Upgrades, Downgrades, and Crossgrades
        • Event Subscriptions
        • Understanding Transferred Events and Accounts
      • API Access
    • Events Feed
  • Analytics
    • Using Charts
    • Paywall Analytics
      • Impressions
      • Paywall Conversion Rate
      • Sessions
      • Active Devices
    • Subscription Analytics
      • Revenue
      • MRR
      • Purchases
      • Trial Starts
  • Nami Account
    • Manage your Apps
      • Find your Nami App Platform ID
      • Setting up Legal Text for your Apps
    • Organization
      • Configuring Organization Security Policies
      • Billing
    • Invite your Team
      • Roles
    • Manage your Account
      • Two-Factor Authentication (2FA)
Powered by GitBook
On this page
  • Data Collected by Nami
  • Entering your Privacy Information
  • Summary
  1. Integrations
  2. Billing Platforms
  3. Apple Integration
  4. App Store Setup

Privacy Details

Last updated 1 year ago

Apple's App Store requires that all apps disclose what data they collect and how they use it. This requirement includes disclosing any data collection by third-party partners such as Nami.

Below we'll outline what data Nami collects and how that must be disclosed in Apple's platform. Also see our general guide on for more information.

Data Collected by Nami

On the data collection screen, the following items may need to be selected depending on how you are using the Nami SDK in your product.

The first list includes data collected for all implementations.

Data Element
Notes

Identifiers - Device ID

Nami generates a unique UUID for each device. This identifier is not tied to the device through any type of fingerprinting or other similar techniques.

Purchases

Collected to power your in-app purchases.

The following data elements may be collected if you are using certain capabilities of our SDK.

Data Element
Notes

Identifiers - User ID

Collected if you are using our External Identifiers functionality.

Usage Data - Product Interaction

If you use our Core Content and Core Action functionality, you will need to check this box.

Entering your Privacy Information

Log in to , and select the app you wish to enter privacy details for.

On your app page, click App Privacy and then the Get Started button to add your privacy information.

If you have already set up your App Privacy and need to modify it, simply click the Edit button next to Data Types.

Nami does collect data from your app, so please select "Yes, we collect data from this app" on the next screen.

Select the correct set of Data Collection items based on the tables in the previous section. If you added all the different Data Types your screen will now look like the one below.

We'll go through each box below and select the correct information for the Nami SDK.

📘 Note that these options are below are only true solely as related to your use of the Nami SDK in your app.

Other SDKs or your app implementation may require different answers to these questions.

Identifiers - Device ID

Under Device ID, the following selections describe Nami's use of Device IDs.

  1. Select Analytics, Product Personalization, and App Functionality.

  2. Select "No, device IDs collected from this app are not linked to the user's identity."

  3. Select "No, we do not use device IDs for tracking purposes".

Identifiers - User ID

Under Identifiers - User ID, the following selections describe Nami's use of User IDs.

  1. Select Analytics, Product Personalization, and App Functionality on the first screen.

  2. Select "No, user IDS collected from this app are not linked to the user's identity."

  3. Select "No, we do not use user IDs for tracking purposes."

Purchases

The selection of items on the Purchase History data will depend on how you are using the Nami platform.

  1. All apps must select the following items Analytics, Product Personalization, and App Functionality.

    1. If you use Nami capabilities around the purchase state, entitlement state, or customer journey for marketing or advertising, you must check Developer's Advertising or Marketing. This includes sending any Nami data to other third-parties through our integrations.

    2. If you use Nami's integrations to send device.transaction or any user.* events to other 3rd parties for advertising purposes, you must check Third-Party Advertising.

  2. Select "No, purchase history data collect from this app is not linked to the user's identity."

  3. Select "No, we do not use purchase history data for tracking purposes."

Usage Data - Product Interaction

If you are using our Machine Learning in our SDK and in particular our Core Content and Core Action capabilities, you'll need to make the following selections for Usage Data - Product Interaction.

  1. Select Analytics and Product Personalization on the first screen.

  2. Select "No, product interaction data collected from this app is not linked to the user's identity".

  3. Select "No, we do not use product interaction data for tracking purposes".

Summary

When complete, your App Privacy based on usage of the Nami SDK should look like the example below under App Privacy > Product Page Preview.

If you click the See Details button you should see the following information.

Data Collection
App Store Connect