Consent, Subscriptions, and Privacy

The integration is deliberately conservative about consent: syncing data never changes who you are allowed to email.

Email subscription status

• Importing and syncing clients does not subscribe anyone. Profiles are created and enriched without touching Klaviyo's email consent, so your deliverability and compliance posture is unchanged by turning the sync on.
• Mindbody's six communication preferences (account, promotional, and schedule notifications, each for email and text) are mirrored onto the profile as reference properties (for example "MB Send promotional emails"). Use them in segments: the provisioned Promo Opt-In segment is built from exactly this.
• Optional email consent sync. If you want Mindbody's email opt-in to drive Klaviyo subscription status, that can be enabled for your account on request. It is off by default, and it only ever subscribes; it is designed never to mass-unsubscribe your list because of a data quirk on the Mindbody side.

SMS

The integration never writes SMS consent. Text-message consent has carrier-level compliance requirements that belong in your Klaviyo signup flows, not in a data sync.

What data is stored where

• Your client data lives in your Mindbody account and your Klaviyo account; Klaviyo becomes a second system of record for the synced fields listed in the Data reference.
• APIANT's managed environment processes records in transit and stores the operational state needed to run the sync (identifiers, the location naming table, sync bookmarks). It is not a marketing database and is never used for anything except operating your integration.
• Credentials (your Mindbody authorization and your Klaviyo API key) are stored encrypted, and you can revoke the Klaviyo key at any time from your Klaviyo settings, which stops the integration immediately.

Deleting a client

Deleting or anonymizing a client is done in both systems of record: remove or anonymize them in Mindbody, and suppress or delete the profile in Klaviyo. On request, APIANT purges any operational references from the integration's own storage.