PII & scope

Scope

Your API account is configured with two lists:

  • Allowed clients — your token sees every event under these client organizations.
  • Allowed events — individual events granted explicitly, in addition to anything covered by the client list.

Your token's full reach is the union of those two lists. Within that scope, narrow per request with ?clientCode= and ?eventCode=:

GET /v1/participants?clientCode=acme&eventCode=acme-2026

Naming a client or event outside your scope returns 403 Forbidden.

PII

Each account has a single canAccessPii flag. When it is false, every PII-tagged field is stripped from responses before they leave the server. Counts and non-PII fields remain — so integrations can answer questions like "how many participants registered?" without touching personal data.

What counts as PII

Personal data categories tagged in the schema, including:

  • Names — first/last/middle/preferred/badge/display
  • Email addresses
  • Phone numbers
  • Mailing / billing / shipping addresses
  • Identifiers — auth ids, external participant ids
  • Payment method last-4, brand, expiry
  • Loyalty program numbers
  • Accessibility needs
  • Transcripts of conversations
  • Geolocation, health, and financial identifiers

How fields are removed

  • Object fields tagged as PII are omitted from the response entirely (the key is absent, not null).
  • Arrays whose element type is PII (e.g. lists of email addresses) come back as [].
  • Nested objects are walked recursively; non-PII siblings remain.

If you need PII access, ask a Jade administrator to flip canAccessPii on your account. The change is logged.