Privacy & Consent

Two separate mechanisms both get called “consent” — don’t conflate them.

Gating surveys entirely: consentRequired

An init() option (see each platform’s Configuration page). When true, surveys start disabled — equivalent to calling setSurveysEnabled(false) immediately — until you explicitly re-enable them, presumably once your own consent flow (a cookie banner, an app permission screen, whatever your app already has) completes. This gates the SDK’s own survey overlays; it does not gate event tracking.

In-survey consent: the Consent Screen

Separately, a survey can be configured with its own consent message/screen — shown as part of the survey flow itself (optionally embedded into the survey’s start screen), which the end user can accept or decline. This is authored per-survey on the backend, not an SDK configuration option — the SDK just renders whatever consent configuration the survey’s config carries.

Data collected

The SDK collects device, app, network, and screen information as part of normal event tracking (to power targeting and analytics) — the usual categories relevant to GDPR/CCPA/NDPR compliance obligations, which sit with the integrator’s own privacy policy and consent flow, not with SDK configuration alone.