Privacy

Data handling and enterprise boundaries

NOME treats identity, org membership, entitlements, billing linkage, and installability as control-plane state. Enterprise identity can be layered through WorkOS, but product access and private-owner-only rules remain NOME-owned.

Tenant isolation

Tenant and org boundaries are resolved through the canonical bootstrap and policy layers. Marketplace visibility, access objects, and release channels do not bypass those controls.

Audit vs telemetry

Audit and compliance trails stay distinct from product telemetry and evaluation traces. Evidence, approvals, and receipts are separate from marketing analytics.

Auth posture

WorkOS supports enterprise identity, SSO, SCIM, and broker flows. NOME still owns entitlements, billing linkage, operator state, and private-owner-only policy decisions.

Retention and agreements

Customer retention terms, enterprise onboarding, release channels, and connector scopes are governed by your account or enterprise agreement plus platform configuration.

For the current privacy packet or enterprise addenda, contact legal@nomadmaraud.co.