As part of our commitment to privacy, here's an overview of the data that Nami collects on users of your app after you install the SDK, as well as why we collect these data.
The Nami SDK has a few ways it identifies a device or a user across devices.
- A Nami generated device level UUID
- A transaction or purchase ID provided by the Store Platform that may be used to track related purchases made by a single customer account.
- (Optional) An external ID provided by you in an anonymized format (e.g. Numeric, SHA256, UUID) that means something to you, but is meaningless to Nami other than as a mechanism to link multiple devices together.
- (Optional) A Customer Data Platform (CDP ID) identifier used for paywall personalization
The UUID generated by Nami for the device is not a "fingerprint." That is, it is not directly tied to the device in any way. If an app user were to delete all data for your app from their device and then reinstall the app, Nami would see this as a new device.
User IDs provided by you when integrating our SDK must always be de-anonymized. Nami's Platform will reject any customer identifiers you try to provide us that are not in an acceptable format such as Numeric, UUID or SHA256.
Not all purchase platforms provide a transaction ID of the form described in #2, but when available Nami does make use of it.
These IDs will be attached to all data collected in the following sections.
- New purchases and purchase history
- Paywall screen impressions
- Behavioral data for Machine Learning
Behavioral data for machine learning includes data sets autogenerated by Nami while the app is in use as well as specific instrumentations you provide via our methods for Core Content and Core Actions.
Further, any log-level data around behaviors that powers Nami's machine learning is only stored on your user's devices. We only transmit aggregated behavioral data to our servers to provide an extra layer of privacy for your app users.
Each store platform such including App Store, Google Play, Amazon Appstore, Roku provides a server-to-server event feed. Nami uses this feed along with the transaction or purchase ID referred to in the Identifiers section above to populate a user's purchase history.
This is used to power the anonymous Customer module, which provides a value customer service tool. It is also used to provide comprehensive subscription and purchase analytics
On each API call we also collect the following data about the device:
- Device model
- Device form factor
- OS name and version
- SDK version
- App version
These data are used to ensure our SDKs are able to support the device ecosystems of your app.
Updated 4 months ago