Skip to main content
App review, readiness checks, and rejections Level: Intermediate 12 min read

Export Compliance & Encryption Attestation Guide (ITSAppUsesNonExemptEncryption)

A comprehensive developer guide to U.S. export compliance, encryption exemptions, ITSAppUsesNonExemptEncryption in Info.plist, and App Store Connect compliance attestations.

Published: 2026-11-02 • Last Updated: 2026-11-02 • Author: Kip Lawrence
Key MCP Tools: release_readiness_checkrelease_external_prerequisites_listrelease_external_prerequisite_attest

Overview: The Regulatory Landscape of App Encryption

Whenever you distribute an application globally through the Apple App Store, your software is subject to United States Export Administration Regulations (EAR) administered by the Bureau of Industry and Security (BIS) under the U.S. Department of Commerce. Because encryption technology is historically classified under Category 5, Part 2 of the Commerce Control List (CCL), Apple requires developers to declare the encryption characteristics of every uploaded binary before it can be distributed to TestFlight external testers or released on the public App Store.

For modern mobile developers, virtually every application uses encryption—whether querying REST APIs over HTTPS, authenticating with OAuth tokens, or calling Apple's native CryptoKit and CommonCrypto libraries.

However, developers frequently misunderstand two critical concepts:

  1. Using Encryption vs. Non-Exempt Encryption: Standard commercial applications using industry-standard web encryption (HTTPS/TLS) almost universally qualify for exemptions under U.S. export regulations (such as Note 4 to Category 5, Part 2).
  2. The ITSAppUsesNonExemptEncryption Flag: Setting <key>ITSAppUsesNonExemptEncryption</key><false/> in your Info.plist does not mean your application uses "no encryption." It certifies that your application uses only exempt encryption, automating Apple's compliance questionnaire and eliminating manual dialogs on every build upload.
TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   U.S. EXPORT COMPLIANCE DECISION TREE                 │
│                                                                        │
│   Does your app use cryptography?                                      │
│   ├── NO ──► Set ITSAppUsesNonExemptEncryption = false                 │
│   └── YES ──► Does it qualify for an Exemption?                        │
│                 ├── Standard HTTPS / TLS communication                 │
│                 ├── Standard authentication (OAuth, JWT, passwords)    │
│                 ├── Digital signatures and copyright protection        │
│                 └── System-provided encryption APIs (CryptoKit)        │
│                       │                                                │
│                       ├── YES (Exempt) ──► ITSAppUsesNonExempt = false │
│                       │                     (Zero BIS filing required) │
│                       │                                                │
│                       └── NO (Non-Exempt) ──► ITSAppUsesNonExempt=true │
│                             ├── File CCATS with U.S. BIS               │
│                             ├── Submit Annual Self-Classification Rpt │
│                             └── Upload Document to App Store Connect   │
└────────────────────────────────────────────────────────────────────────┘

[!CAUTION] Legal Disclaimer & Regulatory Compliance: This guide provides technical reference and workflow automation guidance. It does not constitute formal legal counsel. Setting ITSAppUsesNonExemptEncryption to false when your application implements proprietary, military-grade, or non-exempt customized ciphers violates Apple's Developer Agreement and U.S. export regulations. If your application implements novel cryptographic algorithms, end-to-end proprietary ciphers, or military communications, consult a qualified export compliance attorney.


Quick Answer: How to Resolve the Export Compliance Blocker

If your build is stuck with "Missing Export Compliance" in App Store Connect or flagged by FlightDeck's release_readiness_check:

  1. Audit Cryptographic Usage: Verify whether your app uses only standard HTTPS/TLS networking, standard authentication, or native Apple system APIs.
  2. Add Key to Info.plist: If your app qualifies for an exemption, add <key>ITSAppUsesNonExemptEncryption</key><false/> to your app's Info.plist.
  3. Re-Archive and Upload: Upload the new binary. Apple's ingestion scanner will detect the key and mark export compliance as complete automatically.
  4. Verify Readiness via FlightDeck: Run a readiness check to confirm that the EXPORT_COMPLIANCE check passes with status VALID.

The 5 Distinct Layers of Export Compliance

To avoid confusion, developers must distinguish five separate operational and legal layers:

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   THE 5 LAYERS OF EXPORT COMPLIANCE                    │
│                                                                        │
│  1. APP BUNDLE CONFIGURATION (Info.plist)                              │
│     `<key>ITSAppUsesNonExemptEncryption</key><false/>`                 │
│     Informs Apple's automated binary ingestion scanner.                │
│                                                                        │
│  2. APPLE APP STORE CONNECT QUESTIONNAIRE                              │
│     Web UI questions answered per build if Info.plist key is omitted.  │
│                                                                        │
│  3. U.S. GOVERNMENT REGULATION (BIS / EAR)                             │
│     Export Control Classification (ECCN 5D002) and Annual Self-        │
│     Classification Reports submitted to BIS/NSA if non-exempt.         │
│                                                                        │
│  4. FRENCH NATIONAL REGULATION (ANSSI)                                 │
│     Mandatory declaration filed with French cybersecurity agency       │
│     (ANSSI) if distributing non-exempt cryptography in France.         │
│                                                                        │
│  5. FLIGHTDECK LOCAL AUDIT LEDGER                                      │
│     `release_external_prerequisite_attest` stores immutable local      │
│     records for internal engineering audit trails. Does NOT submit     │
│     filings to Apple or government agencies.                           │
└────────────────────────────────────────────────────────────────────────┘
Important

FlightDeck Tool Boundaries: Tools like release_readiness_check read the build's compliance state from Apple (usesNonExemptEncryption), and release_external_prerequisite_attest records factual statements in FlightDeck's local database. FlightDeck never transmits legal filings to Apple or government bodies. Local attestations serve internal governance needs and do not substitute for official regulatory filings.


Copyable Prompts for Your AI Coding Assistant

1. Cryptographic Inventory and Code Audit

Run this prompt in your AI assistant to audit your workspace for cryptographic algorithms, third-party libraries, and network protocols:

MARKDOWN
Please perform a cryptographic and export compliance audit on our mobile codebase:
1. Search our codebase and dependency manifests (Package.swift, Podfile, pubspec.yaml, package.json) for cryptographic libraries (e.g., CommonCrypto, CryptoKit, libsodium, OpenSSL, WebRTC, custom AES implementations).
2. Scan our network configuration to verify whether all outbound connections use standard HTTPS/TLS.
3. Determine whether our cryptographic usage falls under standard U.S. export exemptions (e.g., mass-market consumer software using standard web encryption, authentication, or system-provided APIs under EAR Note 4).
4. Inspect our `Info.plist` files to check if `ITSAppUsesNonExemptEncryption` is currently configured.
5. Provide a compliance audit summary table before recommending any edits.

2. Configure ITSAppUsesNonExemptEncryption in Info.plist

Once the audit confirms that your application uses only exempt encryption:

MARKDOWN
Our cryptographic audit confirms that our application uses only standard HTTPS and system-provided authentication APIs, qualifying for an exemption under U.S. EAR Category 5 Part 2:
1. Update our project's `Info.plist` to add `<key>ITSAppUsesNonExemptEncryption</key><false/>`.
2. Ensure the key is placed under the root `<dict>` element alongside other standard metadata.
3. Validate that the XML syntax is well-formed using `plutil -lint`.
4. Explain how this change prevents the TestFlight export compliance prompt on future build uploads.

3. Verify Export Compliance via FlightDeck MCP

After uploading your build, verify that Apple recognizes the exemption:

MARKDOWN
Please inspect our active App Store Connect draft version and attached build using FlightDeck:
1. Check the export compliance status of our selected build to confirm whether `usesNonExemptEncryption` is registered as false.
2. Verify that our version has zero export compliance blockers preventing submission.
3. Record a local engineering audit record in FlightDeck confirming that our team reviewed the cryptographic usage.
4. Report any remaining submission blockers.

Under U.S. Export Administration Regulations (EAR), software containing encryption is regulated under ECCN 5D002 or 5D992. However, the vast majority of mobile applications qualify for exemptions:

1. Categories That Typically Qualify for Exemption (ITSAppUsesNonExemptEncryption = false)

  • Standard Network Security: Using HTTPS, TLS, SSL, or SSH for secure client-server communication.
  • User Authentication: Using cryptographic functions solely for user passwords, PINs, biometrics, OAuth 2.0, or JWT tokens.
  • Digital Signatures: Cryptography used strictly for data integrity, code signing, or copyright protection (DRM).
  • Native OS APIs: Utilizing standard Apple system APIs (CryptoKit, LocalAuthentication) without implementing proprietary cryptographic primitives.
  • Mass-Market Consumer Apps: General consumer applications (social media, productivity, e-commerce, casual games) that are widely available to the public.

2. Categories Requiring Formal BIS Filing (ITSAppUsesNonExemptEncryption = true)

  • Proprietary Encryption Algorithms: Implementing custom ciphers or modifying standard encryption algorithms.
  • Non-Standard Cryptographic Protocols: Developing novel point-to-point mesh networks or encrypted routing protocols.
  • Government or Defense End-Users: Applications specifically engineered for foreign military, intelligence, or governmental applications.
  • Financial Infrastructure: Certain specialized banking encryption systems outside standard consumer online banking.

If your application falls into Category 2, you must submit a Commodity Classification Automated Tracking System (CCATS) request to the U.S. BIS, obtain an encryption registration number (ERN), submit an Annual Self-Classification Report every February, and upload your official approval documentation directly into App Store Connect.


Special International Jurisdiction: France (ANSSI)

In addition to U.S. regulations, the French government enforces specialized national cryptographic declarations administered by the Agence nationale de la sécurité des systèmes d'information (ANSSI).

  • When It Applies: If your app is distributed on the French App Store (FR) and uses proprietary encryption or cryptographic functions beyond standard authentication, French law requires filing a declaration with ANSSI.
  • App Store Connect Requirement: When configuring export compliance for non-exempt apps in App Store Connect, Apple provides a dedicated upload field for your approved French declaration document.
  • Exempt Apps in France: Standard consumer apps that only use HTTPS/TLS and qualify for U.S. exemptions are generally exempt from French ANSSI filings as well.

Step-by-Step Implementation in Xcode and FlightDeck

MERMAID
sequenceDiagram
    autonumber
    actor Dev as Developer
    participant AI as AI Assistant (IDE)
    participant Xcode as Xcode Project (Info.plist)
    participant FD as FlightDeck MCP
    participant Apple as App Store Connect

    Dev->>AI: "Audit cryptography and resolve export compliance"
    AI->>AI: Scans dependencies (Found: standard HTTPS, zero custom ciphers)
    AI->>Xcode: Inserts ITSAppUsesNonExemptEncryption = false
    Dev->>Apple: Uploads binary archive (xcodebuild / FlightDeck)
    Apple->>Apple: Ingestion scanner detects Info.plist key
    Apple-->>Apple: Sets build.usesNonExemptEncryption = false
    Dev->>AI: "Verify submission readiness"
    AI->>FD: release_readiness_check(versionId: "...")
    FD->>Apple: Preflight readiness validation
    Apple-->>FD: Export Compliance check: PASS
    FD-->>AI: Status: READY_FOR_SUBMISSION (0 Blockers)
    AI->>FD: release_external_prerequisite_attest(statement: "Exempt per EAR Note 4")
    Note over FD: Stores local audit trail entry
    FD-->>Dev: Compliance attestation recorded locally

Step 1: Adding the Key to Info.plist

Open your Info.plist file (or ios/Runner/Info.plist for Flutter, ios/App/App/Info.plist for Capacitor/React Native):

XML
<dict>
    <key>CFBundleIdentifier</key>
    <string>quest.kip.companion</string>
    <key>CFBundleShortVersionString</key>
    <string>1.2.0</string>
    <key>CFBundleVersion</key>
    <string>10</string>
    
    <!-- Export Compliance Exemption Declaration -->
    <key>ITSAppUsesNonExemptEncryption</key>
    <false/>
</dict>

Step 2: Validating XML Syntax

Verify that the Info.plist file remains well-formed:

BASH
plutil -lint ios/Runner/Info.plist
# Expected output: ios/Runner/Info.plist: OK

Step 3: Verifying Readiness via FlightDeck MCP

Once the build is uploaded and attached to your draft version, run release_readiness_check:

JSON
{
  "code": "EXPORT_COMPLIANCE",
  "title": "Export Compliance Documentation",
  "status": "PASS",
  "evidence": "Encryption exemption declared: usesNonExemptEncryption = false."
}

Step 4: Recording a Factual Local Attestation

For engineering audit trails and governance compliance, record a factual attestation in FlightDeck:

JSON
{
  "appId": "6812899314",
  "prerequisiteId": "EXPORT_COMPLIANCE_REVIEW",
  "statement": "Application verified to use only standard HTTPS and Apple CryptoKit APIs; declared exempt under EAR Category 5 Part 2.",
  "notes": "Audited by engineering team on 2026-11-02."
}

This stores an immutable local record in FlightDeck's audit database, confirming that a human operator evaluated the regulatory requirements before submission.


Troubleshooting Common Export Compliance Issues

1. "Build is missing export compliance information"

  • Cause: The binary was archived without ITSAppUsesNonExemptEncryption in Info.plist.
  • Fix: In App Store Connect, click the build row and answer the web questionnaire manually. To avoid this on future builds, add the key to Info.plist permanently.

2. "Setting ITSAppUsesNonExemptEncryption to false but build still blocked"

  • Cause: You uploaded a new build, but your draft version is still pointing to the older build number that lacked the Info.plist key.
  • Fix: Select the newly uploaded build in your draft version using FlightDeck or the web portal.

3. "French ANSSI declaration rejected by Apple"

  • Cause: The uploaded PDF document was not issued by ANSSI or did not match the legal entity name on your Apple Developer Account.
  • Fix: Ensure your ANSSI dossier matches your registered company legal entity exactly before submitting.

Security & Regulatory Safeguards

  • Audited Declarations: FlightDeck records local factual compliance attestations with timestamps, preserving evidence for corporate compliance audits.
  • Zero Automated Bypasses: FlightDeck does not make automated legal determinations; human developers must physically approve all version submissions.
  • Direct TLS Communication: All compliance metadata communicates directly with Apple's secure servers over TLS 1.3.

Official Apple & Regulatory Documentation

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store