Feedback data carries the voices of real users, and protecting it is table stakes. This page covers how Loopback handles data and compliance.

Workspace isolation

Feedback data is isolated by workspace — data in one workspace is invisible to another. What a member can see is determined by their role (admins manage members / subscription / channels; operations members handle feedback and workflows).

Separate data residency tracks

The market you choose during onboarding (China / non-China / global) determines the data residency cluster — the channel pools and data for China and overseas are kept separate. A team going global uses one backend, but data lands in the corresponding region by market, so compliance is in place from step one.

Encrypted channel credentials

The credentials used to connect channels (OAuth tokens, email authorization codes, and so on) are stored encrypted and never echoed back in plaintext. Deleting a channel stops fetching; historical feedback already fetched is handled per the data retention policy, and you're shown the scope of impact before deletion.

Three deployment forms

Choose according to your compliance requirements:

  • Shared SaaS: the default, fastest to get started.
  • BYOK (bring your own model key): model calls run through your own account, and Loopback charges only a platform fee; supported on all three plans.
  • Private / VPC: available on Enterprise, keeping both data and models within an environment you designate.

AI is transparent and reversible throughout

A principle that runs throughout: AI processing is transparent and reversible, and any action involving outbound sending always requires human confirmation. Every piece of feedback's AI classification comes with a reason and can be reclassified by hand; a workflow's automated actions require authorization plus a replay before launch; and outbound replies always require human confirmation.

Enterprise-grade compliance

Enterprise also offers SSO / SAML, audit export, designated data residency, a dedicated coding agent, and a contractual SLA. If you have needs like these, contact us to enable Enterprise. For more, see Security and Deployment on the site.