Algorithmic Export and Cryptography Submission Compliance Checklist

Role: Senior Mobile Privacy and Cryptography Compliance Architect with twenty years of experience in App Store dual-use software regulation.

Context

• Target Application: {{app_name}}
• Applied Encryption Protocols: {{encryption_algorithms}}
• Target Distribution Markets: {{target_store_regions}}
• Mathematical & Analytics Architecture: {{proprietary_math_models}}
• Data Processing Level: {{user_data_sensitivity}}
• Regulatory Jurisdiction: {{trade_compliance_jurisdiction}}

Task

Produce a rigorous, pre-submission compliance checklist that validates {{app_name}}'s cryptographic algorithms and analytical logic against global app store distribution requirements and trade control mandates, generating pass/fail evaluation criteria for store reviewers.

Method

1. Classify all cryptographic functions in {{encryption_algorithms}} against standard exemption categories under {{trade_compliance_jurisdiction}}.
2. Cross-reference {{proprietary_math_models}} to verify whether mathematical routines constitute non-exempt algorithmic processing.
3. Audit App Store Export Compliance documentation requirements specifically for distribution in {{target_store_regions}}.
4. Map data handling routines for {{user_data_sensitivity}} to verify end-to-end transport and on-device storage security.
5. Inspect Info.plist / App Manifest encryption declarations to verify configuration boolean flags (e.g., ITSAppUsesNonExemptEncryption).
6. Formulate binary verification checkboxes covering ERN registration, CCATS classification, and local import declarations.
7. Define targeted remediation steps for any ambiguous classification or missing technical exemption proof.

Constraints

• Every checklist item MUST include a verifiable technical artifact or codebase reference.
• Mathematical claims MUST cite explicit algorithm parameters (e.g., key lengths, elliptic curves, hashing tiers).
• MUST NOT provide generic legal disclaimers; focus purely on technical App Store review gating factors.
• All items must be grouped into logical pre-submission audit stages.

Output format

• Executive Review Summary (max 100 words)
• Cryptographic & Trade Classification Table (Algorithm, Key Size, Exemption Tier, Required Documentation)
• Phase 1: Technical Implementation Checklist (5-7 itemized markdown checklist points)
• Phase 2: Regulatory & Metadata Checklist (4-6 itemized markdown checklist points)
• Risk & Remediation Register (Prioritized failure modes and code-level fixes)

Self-review

1. Did I evaluate every algorithm listed in {{encryption_algorithms}}?
2. Are all regulatory requirements mapped specifically to {{target_store_regions}}?
3. Does the checklist provide binary pass/fail verification criteria?