Privacy

Customers (“Customer(s)”, “you,” or “your”), as app developers and/or publishers, shall ensure compliance with applicable data privacy laws and regulatory guidelines while using Contentsquare SDK for your app.

This section explains the data processing involved in the use of Contentsquare SDK and provides information to help you comply with data protection laws, including the GDPR, e-privacy directive, and the French Data Protection authority (CNIL) guidelines on mobile applications ↗. This section is for informational purposes only and is not legal advice. If you are not sure of how to comply with data protection laws that apply to you, refer to legal counsel.

To learn about Contentsquare privacy practices, see our Privacy Center ↗ and Privacy Policy ↗.

Here is the list of categories of personal data Contentsquare collects by default that are part of our privacy manifests. All collected personal data listed below is linked to the end-user via the Contentsquare User ID we generate.

See how the data types and purposes are reflected in the privacy manifest ↗.

The SDK generates a unique user ID (UUID) (random hash) which is specific to users on their device. Contentsquare cannot identify a user across devices. This user ID and all collected data are stored for 13 months. We don’t persist the UUID when the app is deleted and re-installed. The SDK generates a new UUID after install or re-install. Contentsquare does not share this user ID with any third parties.

Contentsquare does not collect the IDFA (Advertising ID) or any ad related information to identify the user.

Check out our page about 10 Things to know about the Contentsquare solution’s data processing ↗.

Contentsquare provides the ability to search for session(s) associated with a specific visitor, based on an identifier provided by the customer. See User identifier feature for more information.

By default, end-users personal data are kept for 13 months. The retention of end-users personal data collected via the Session Replay is customizable by customers, from 3 to 24 months.

End-users personal data are stored in Europe or in the US, depending on your location. For more details on applicable hosting locations, refer to our subprocessors list ↗.

The Contentsquare SDK collects end-user’s personal data on your app. As a data controller, app developers, or app publishers, it is your responsibility to provide appropriate information to your end-users on how their personal data is handled when using the CSQ SDK, for example via a privacy policy or cookie banner.

Contentsquare provides a sample description of the services ↗ (including Experience Analytics and Product Analytics) to help customers meet their transparency obligations. This description is for information only and is not legal advice.

Contentsquare collects usage data on your app. By default, the SDK will consider every new user to be opted-out. To start tracking, the SDK Opt-in API must be called.

You are responsible for handling the UI asking end-users for their consent and allowing them to manage their privacy settings.

Use the following APIs to pass the user decision to the Contentsquare SDK.

Use the Opt-in API to get end-user consent. Calling this API will generate a user ID and initiate tracking.

import UIKit
import ContentsquareSDK

optinButton.addTarget(self, action: #selector(optInButtonTapped), for: .touchUpInside)

@objc func optInButtonTapped(_ sender: UIButton) {
    CSQ.start()
    CSQ.optIn()
    ...
}

#import <UIKit/UIKit.h>
#import <ContentsquareSDK/ContentsquareSDK.h>
[optinButton addTarget:self action:@selector(optInButtonTapped:) forControlEvents:UIControlEventTouchUpInside];

- (void)optInButtonTapped:(UIButton *)sender {
    [CSQ start];
    [CSQ optIn];
    // Additional initialization or navigation code...
}

When this API is called, tracking stops immediately, all settings are reset (Session number, Page number, and so on) and all files and directory including personal data collected via the SDK created by Contentsquare are deleted. This means that the user ID is deleted. The SDK will never track and collect any data from the user’s phone unless the Opt-in API is called again.

CSQ.optOut()

[CSQ optOut];

In case Contentsquare receives a request from an individual that identifies as an end-user of your app, Contentsquare will promptly refer such individual directly to you, as the data controller and will support you with any means available to resolve such request.

Contentsquare has launched a portal for managing data subject requests to its customers respond to data subjects within the legal deadlines. Therefore, you can forward any data subject request (such as data deletion or data access request) you receive to Contentsquare via this Data Subject Portal at https://contentsquare.com/privacy-center/data-subject-request-portal/ ↗.

Since Contentsquare SDK does not collect by default any directly identifiable personal data about your end-user, we cannot help you respond to an end-user’s data subject request without their Contentsquare User ID.

Use this API to get the Contentsquare User ID of your end-user and forward the end-user’s data subject request (such as data deletion or data access request) via Contentsquare’s portal ↗.

CSQ.metadata.userID

[CSQ metadata].userID

The Enrichment API allows for enriching the behavioural data tracked by Contentsquare client-side, with other session-based data that can be sent server-side.

During a visit on an app, you can interact with Contentsquare’s SDK to pull those identifiers with the following SDK APIs:

let projectID = CSQ.metadata.projectID
let sessionId = CSQ.metadata.sessionID
// store these Contentsquare session identifiers in your backend

NSString *projectID = [CSQ metadata].projectID;
NSString *sessionId = [CSQ metadata].sessionID;
// store these Contentsquare session identifiers in your backend

To completely stop data collection of your end-users of your app, use the pause and resume tracking APIs. When stop/pause is called, the Contentsquare SDK pauses all tracking (Analytics, Session Replay, Errors) of your end-users. When resume is called, the Contentsquare SDK resumes all tracking (Analytics, Session Replay, Errors) and starts collecting your end-users personal data again with the same Contentsquare user ID.

CSQ.stop()
// ...
CSQ.resumeTracking()

objective-c
[CSQ stop];
// ...
[CSQ resumeTracking];

If you don’t want to link the different sessions of a user to the same userID, reset the userID at each app start:

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) {
    CSQ.start()
    CSQ.optOut()
    CSQ.optIn()
    // ...
}

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    [CSQ start];
    [CSQ optOut];
    [CSQ optIn];
    // ...
    return YES;
}

Starting the SDK manually using start() will ensure that opt-out is called right after the start of the SDK (no event tracked in between).

Calling optOut() will delete the previous userID.

Calling optIn() will set a new one.

As part of Session Replay capabilities, Contentsquare provides masking mechanisms to prevent unwanted end-user’s personal data from the Session Replay module from being transmitted to Contentsquare. See Session Replay Personal data masking for more information.

As customer app developers, it is your responsibility to comply with the App Store Privacy guidelines ↗.

The Contentsquare SDK includes a privacy manifest ↗ describing the types of end-users personal data collected, the purpose of processing and the reasons for using APIs. See Apple’s website for more information ↗

App Store (Apple) requests App developers to receive end-users’ permission to track them or access Advertising ID using the AppTrackingTransparency framework ↗ (ATT).

It is not required to ask for end-users’ permission through the ATT when using Contentsquare, as it does not fall under the “tracking” definition of Apple ↗. The data collected by the Contentsquare SDK is not linked with Third-Party Data (as defined by Apple) for targeted advertising or advertising measurement purposes, nor shared with a data broker.