Menu

NANIGANS PERSONAL DATA / COOKIE FAQ

This Cookie FAQ applies to cookies, identifiers (collectively referred to as the “Cookies”) and other tracking technologies used by Nanigans to collect personal data about web and app users in the operation of our Advertising platform. It does not pertain to information collected by and about our advertiser customers as they use our Advertising platform, or to information collected on our company website. It provides details on how Nanigans collects personal data and how you as our customer can control the collection.

What are Cookies?

Cookies are small data files (including tiny graphics files that contain a unique identifier) that are placed on and retrieved from the user’s computer or mobile device when the user visits a website.

Why does Nanigans use Cookies, tracking technologies, and collect personal data?

The Nanigans Advertising platform serves marketers looking to maximize the measurable business impact of their advertising efforts. This requires measuring how users interact with a marketer’s advertisements, website and/or app over time, as well as learning which products and services those users have shown interest in. Nanigans collects this information from the advertisements served by our Advertising platform and instrumentation on our customers’ websites and apps using Cookies and other tracking technologies (e.g. tracking identifiers, mobile ad identifiers) to link interactions together. These customer interaction traces are considered to be personal data under the General Data Protection Regulation (“GDPR”). For more information see our GDPR FAQ. Such data is considered personal, even when the customer interaction traces do not directly identify a person because they are specific to one individual and could conceivably be used to identify them. Nanigans does not collect information that directly identifies a person such as name, email address phone number, or any sensitive information such as health or financial information.

How does Nanigans use Cookies and other tracking technologies to collect personal data?

The Nanigans Advertising platform supports several options for data integration and uses the following Cookies and other tracking technologies:

  1. Ad-level data APIs with Facebook and Twitter.
    Facebook and Twitter each offer their own measurement solutions for advertisers, and the Nanigans platform can directly import that data. This data is aggregated rather than individually identifiable, so this type of integration does not collect any personal data.
  2. Mobile measurement provider (“MMP”) anonymized “event stream” integration.
    Many MMPs can share an event stream combining app analytics and advertising attribution information. While this data is unique to an individual, it cannot be linked to a person because the identifiers connecting records do not connect to a person’s devices.
  3. Nanigans mobile SDK integration.
    The Nanigans SDK is a “light” mobile measurement solution for Facebook and Twitter. The SDK utilizes Android IDs, Android Ad IDs, and iOS IDFAs for tracking, as well as an app-specific cookie-like identifier. The SDK makes calls directly from end user devices, so IP address information is also collected. A first-party login identifier may optionally be provided.
  4. Nanigans Javascript web pixel.
    The JS pixel issues cookie IDs for tracking. It sets a cookie in the advertiser’s domain when loaded and an identical cookie in the Nanigans domain when an event is triggered. Additional cookies may be created afterward based on retargeting settings. The JS pixel also collects a browser fingerprint, IP address, and User Agent string, which are used for short-term tracking when cookies are unreliable. A first-party login identifier may optionally be provided.
  5. Server-to-server API.
    All of the IDs used by the mobile SDK and JS pixel are supported by the server-to-server API. Most commonly these integrations do not include any cookie or browser information, but rather utilize mobile advertising IDs and/or login identifiers. MMP integrations that do pass advertising IDs should be considered server-to-server API integrations.
  6. Nanigans Redirector and View tag
    The Nanigans Advertising platform offers the ability to apply tracking rules to your advertisements, including automatically inserting the Nanigans Redirector into click links and adding a View tag to desktop web ads.

    Outside of the EEA: When a user clicks through the Nanigans Redirector, it issues a cookie ID in the Nanigans domain, compatible with the JS pixel. It also collects the browser IP address and User Agent string. The View tag issues a cookie in the Nanigans domain when it loads, but does not collect any personal data.

    Inside of the EEA: The Nanigans Redirector and View tag do not place cookies for users in the EEA.

How can I control the personal data Nanigans collects (e.g. for consent)?

  1. Ad-level data APIs with Facebook and Twitter.
    Nanigans collects no personal data.
  2. Mobile measurement provider anonymized “event stream” integration.
    MMPs generally send event stream data on an all-or-nothing basis, as an app-level setting. So, if you do not intend for Nanigans to collect this data for a specific user, you should not pass the data for that user to your MMP. Consult your MMP for other possible solutions.
  3. Nanigans mobile SDK integration.
    The Mobile SDK does not pass any data to Nanigans unless you call the SDK functions to record in app activity, so if you do not want Nanigans to collect personal data on a user, do not call SDK functions for that user. The SDK does not offer granular control over the set of data passed with events, except for the optional login ID.
  4. Nanigans Javascript web pixel.
    The JS pixel sets a cookie as soon as the library is loaded, but does not collect information until events are triggered by setting the NaN_api array or using its push function. If you do not wish to place any cookies in the user’s browser, wait to load the pixel library. If you do not want Nanigans to collect personal data on a user, do not trigger events for that user. The JS pixel does not offer granular control over the set of data passed with events, except for the optional login identifier ID.
  5. Server-to-server API.
    You have total control over what data is sent from your server to our server.
  6. Nanigans Redirector and View tag
    Generally, if you do not have permission to place cookies in the user’s browser, disable the Nanigans Redirector and View tag in tracking rules. To make this easy for the common GDPR use case, the Redirector and View tag do not place cookies in browsers detected to be in the EEA.

How long does Nanigans retain personal data?

Data may be retained for up to two years from a user’s last interaction with Nanigans.

How can users control the data Nanigans has collected about them?

Nanigans provides a web link and mobile apps for advertising opt-out, reachable from the privacy policy on our website. We also offer a web form that end users can utilize to request deletion of any personal data Nanigans has collected about them, and a separate form that can be used to request a report of that data. We also provide an API that advertisers can use to request that Nanigans delete data on a specific set of users for whom they have identifiers.