Esper MDM US Export Classification (ECCN / EAR / Encryption): EAR99 — No License Required

Android

This article provides the official US Export Classification statement for Esper. If your organization requires export control documentation or compliance certification, use this information to understand Esper's classification under US Export Administration Regulations (EAR).

US Export Classification for Esper

Esper's platform and the Esper Agent component are classified as follows:

• ECCN: Not applicable
• EAR Classification: EAR99 (for the Esper Agent component)
• License Requirement: None for standard trading conditions
• Encryption Registration: Not required

Classification Details

Hosted SaaS Platform (Console and APIs)

The Esper Console and APIs are accessed via a web browser and do not require ECCN classification. The platform itself is not subject to export restrictions in the traditional sense because no standalone software binary is exported across borders.

Data transmitted through the platform is encrypted and managed by AWS infrastructure. You can review Esper's security and compliance controls at your Esper Trust Center.

Esper Agent (On-Device Component)

The Esper Agent is installed on your managed Android devices and is the only downloadable component that physically travels with devices. The Agent is classified as EAR99 based on an assessment conducted with outside export controls counsel.

Key points about the Esper Agent:

• It does not independently perform cryptographic functions
• Encryption for data in transit and at rest is handled by the Android OS and AWS infrastructure — not the Agent itself
• Because it is not an encryption item under EAR, no encryption review registration or CCATS filing is required
• EAR99 items are not subject to destination-based export license requirements for most jurisdictions under standard trading conditions
• No BIS acknowledgement letter is required or available

When You Need Export Documentation

If your organization is completing compliance reviews, trade compliance filings, or vendor onboarding processes that require export control documentation, you can reference this information in your filings.

For export compliance purposes, you can state:

The only downloadable component is the Esper Agent, which when installed on managed devices functions as a lightweight client that communicates with Esper's cloud-hosted MDM platform. The Agent itself does not independently perform cryptographic functions; encryption for data in transit and at rest is handled by the underlying device operating system and the AWS-hosted cloud infrastructure. Based on an assessment conducted with outside export controls counsel, the Esper Agent is not an encryption item under the EAR and falls under the default EAR99 designation. EAR99 items are not subject to destination-based export license requirements.

Formal Legal Certification

If your compliance team requires a formal signed export classification letter or legal declaration on Esper letterhead (rather than this support documentation), contact Esper Support and specify that you need formal legal certification. Your request will be escalated to the Esper Legal or Compliance team.

Special Circumstances

The following situations require special handling:

• Device OEM pre-installed software: If you have questions about software pre-installed by a device manufacturer (not the Esper Agent), contact the OEM directly — this is outside Esper's scope.
• Restricted or embargoed jurisdictions: If you are operating in a restricted or embargoed jurisdiction and need to know whether Esper can be used, contact Esper Support immediately for legal guidance.
• Disputes about EAR99 classification: If your compliance team disputes the EAR99 designation and requires supporting documentation from export controls counsel, contact Esper Support.

Still Need Help?

If you have additional questions about Esper's export classification or need formal legal documentation, submit a support ticket and we'll connect you with the appropriate team.