Compliance & Consent

Consent controls non-essential data scopes such as analytics, storage, personalization, and ads.

What consent does not block

Two things still work regardless of consent state:

• response collection itself
• imperative flow display

That matters because you can keep the feedback channel working while still tightening analytics or storage behavior.

Start with pending when you need a stricter default

const client = createClient({
  apiKey: "YOUR_API_KEY",
  defaultConsent: "pending",
});

With pending, non-essential scopes are treated as effectively denied until you update them.

Update consent at runtime

client.configure({
  consent: ["analytics.measurement", "analytics.storage"],
});

You can also set pending, denied, granted, or revoked.

Practical rollout rule

If your product already has a CMP or cookie banner, keep getuserfeedback in sync with that source of truth instead of creating a second privacy state machine.