1. Our SDKs: Information We Collect and Services We Provide
We refer to the information we collect from our SDKs as the ‘SDK Information .” The SDK Information includes (or may include) the following:
Information Collected About End Users by Our Mobile SDKs
- When permitted by the operating system, Cheshmak may check to see if the device has specific applications installed, based on a limited list, for purposes that include attribution, relevancy of ads, and relevancy of notifications related to those applications.
- Purchases made within an app.
- Information about End User’s transactions and interactions with apps
- Mobile advertising identifiers, such as iOS IDFAs and Android Advertising IDs (“Mobile IDs”). These Mobile IDs may be associated with other Information, including with Data Segments.
- Precise Location information, generally an End User’s lat/long data (i.e., GPS-level data) or WiFi information, which we may associate with Mobile IDs, and which may be collected whether or not an app is in use.
- Email address, which we may (in our discretion) hash or otherwise deidentify.
- IP address as well as system configuration information
- Information associated with or related to devices, such as device type (e.g., mobile, tablet); type and version of operating system (e.g., Android, iOS); network provider; mobile browser (e.g. Safari, Chrome, etc.); language setting; time zone; and network status type (such as WiFi).
As noted above, we refer to all of the above collectively as the “SDK Information .”
2. How We Use the SDK Information
We use the SDK Information to provide a variety of Services to our Clients. This includes:
- To Provide Our App Services. We use the SDK Information to offer and support app features provided through the SDKs, including those related to push notifications. This includes, for instance, providing customer, technical and operational support for these features, detecting and protecting against errors, fraud, or other criminal activity; resolving disputes and enforcing our EULA and other rights we may have. It also includes analyzing, customizing, and improving the features we offer Clients.
- To provide information and analytics to our Clients about the use of these app features provided through the SDKs, or to help app developers erators create or enhance user profiles.
- To create inferences about End Users categorized into “Data Segments” or to help Clients do so. For instance, if SDK Information indicates that a particular device is frequently seen at restaurants, we might categorize a user for targeting of local restaurant offers. Or, if a user is frequently seen at sports stadiums, we might categorize the user as a “Sports Fan.”
- To develop and use “predictive models” – data models that try to predict End Users’ potential future behavior and interests on a per-device basis or across devices
- To analyze ad performance, for instance, by attributing End Users’ app installations, web visits, or store visits to ad campaigns.
- Sometimes, the SDK Information may be used (by us or ad and data platforms we work with) to resolve identities across multiple devices, such as to match IP addresses or hashed emails to link an End User across (for instance) browsers, mobile devices, tablets, set top boxes, or other devices.
- Sometimes the SDK Information may be combined (by us or ad and data platforms we work with), to perform any of the above functions, or other advertising, marketing or analytics services. Or, we may aggregate and create data “models” to do this – creating algorithms in order to predict certain trends and things that different End Users might have in common, for instance.
- We may provide End Users’ email addresses (which we generally “hash” or render non-human readable) to online data platforms that “match” this information to online cookies or Mobile IDs in their system, and tie the information (or associated IDs) to further interest-based or demographic data about End Users. This may be done, for instance, to target advertising or provide analytics to brands and other companies.
We, or ad and data platforms we work with, may deploy online cookies to track to associate users (and these cookies) with Mobile IDs. We or they may do this to resolve user identifies across platforms, and to better or more accurately target relevant ads to users (such as to a brand’s customers). You can learn more about cookies and similar technologies, such as web beacons and SDKs, in the Section titled “Cookies and SDKs .” We may also “append” or combine certain SDK Information (such as hashed email addresses) to other information provided by third party data providers, to learn more about End Users or to provide advertising and analytics services.
3. How and Why We Share the SDK Information.
To Provide Services to Apps Using the SDKs
- We share the SDK Information with service providers, contractors and other companies to fulfill your orders, operate our business, communicate with you and make available our Services and this Website. These service providers may help us perform any of the activities set forth in Section 2. For instance, we may share certain of the information we collect or receive with companies that help us with billing and payment, marketing, advertising and email marketing,
- data enhancement (e.g., to provide more relevant offers), website hosting, technology and customer support, web and marketing analytics, anti-fraud or security operations, and other operational, marketing or business support.
- We likewise may share the SDK Information or Data Segments we create with app developers (for instance, related to push notifications they send) for their advertising, analytics, or other purposes.
To Provide Services to Marketers, Advertisers and Platforms They Work With
We also share SDK Information to provide or help us to provide advertising and marketing services as we have described in Section 3, including as follows:
- With advertisers and their marketing providers, so they may provide targeted content and advertising to you on mobile applications with other third parties that target advertising. For those familiar with the online ad ecosystem, these may include demand-side and supply-side advertising platforms, data management platforms, advertising agency trading desks, proximity solution providers, and other advertising technology providers, so they may provide targeted content and advertising to End Users and others on third-party, mobile applications, and other advertising mediums (email, direct mail, display media), and so that they may measure the effectiveness of this marketing.
- Similarly, we may work with service providers who, to enhance consumer privacy, use a non-human readable “hashed” version of Information such as an email address when sending advertising offers by email or display advertising (which may be linked to a cookie as described above).
- Sometimes we provide information (such as IP address, but excluding precise lat/long coordinates) to third party platforms to help advertisers identify common users across different devices or browsers – for instance, to identify a common set of users on both mobile devices and tablets, as well as the web.
The processes we’ve described above often involves cookies or similar technologies, which may be associated with other information about you, e.g., your interests, demographics or transactions. This is known generally as “Interest-Based Advertising.” We encourage users who are interested in controlling or learning about this type of “interest-based advertising” to go to Section 6, titled “Consumer Control & Opt-Out Options , or go to this this page operated by the online ad industry trade association.
We may also share the SDK Information with third parties:
- If an End User or Client requests or authorizes
- If the disclosure is done as part of, including as part of due diligence for, a purchase, transfer, or sale of services or assets (e.g., in the event that substantially all of our assets are acquired by another party, any information we have may be one of the transferred assets) or in the event of bankruptcy