⚠️ Legacy feature. Compliance Policies (along with Templates, which apply them) are a legacy Esper product. For new device configuration work, use Blueprints instead — Compliance Policies remain available for existing Template-based deployments. See Introduction to Compliance Policies: https://help.esper.io/hc/en-us/articles/12653153592977-Introduction-to-Compliance-Policies

Deletes a Compliance Policy.

Permanently removes the specified Compliance Policy. All devices must be removed prior to deleting the policy. Apply a different policy to all devices prior to calling the Delete endpoint.

About Compliance Policies A Compliance Policy is a set of device-configuration permissions and restrictions — screen and unlock behavior (keyguard, safe boot), connectivity (USB, tethering, NFC), communication (SMS, outgoing/incoming calls, dialer), hardware (camera, screenshots), and system controls (factory reset, ADB, side-loading, Play Store, app uninstall, date/time configuration) — that gets applied to a device after it has already been provisioned through a Template. They're commonly used to make a post-provisioning change to a Kiosk-mode device, such as temporarily re-enabling the status bar or ADB to pull a bug report, without re-provisioning the device. Templates and Compliance Policies are legacy Esper products; Blueprints are the current, recommended way to define device configuration for new work.

Key Fields / Query Parameters

• policy_id — UUID of the Compliance Policy to delete

Common Use Cases

• Removing an outdated or unused legacy policy during cleanup
• Retiring a Compliance Policy after its devices have been migrated to a Blueprint
• Correcting a policy created in error

Best Practices

• Remove all devices from the policy before calling delete

Workflow

1. GET the policy to confirm device_count and review its configuration
2. Reassign or migrate affected devices as needed
3. DELETE the policy once it's safe to remove