Add encryption export compliance documentation for macOS build

This commit introduces two new files: EXPORT_COMPLIANCE.filled.txt and EXPORT_COMPLIANCE.pdf, detailing the encryption export compliance statement for the Strawberry app. The text file outlines the app's use of encryption, confirming it qualifies for exemption under U.S. export regulations. The PDF provides a formatted version of the same information, ensuring compliance documentation is readily available for developers and reviewers.

build_tools/macos/export_compliance/EXPORT_COMPLIANCE.filled.txt

@@ -0,0 +1,26 @@
+Encryption Export Compliance Statement (EAR)
+
+App Name: Strawberry
+Bundle ID: com.dryark.strawberry
+Version: 0.0.0
+Developer: Dry Ark LLC
+Date: 2026-01-22
+Contact: support@example.com
+
+Statement
+---------
+This app uses encryption only for standard network communications security (for example, TLS/HTTPS connections to web services).
+
+The app does not implement proprietary or non-standard encryption algorithms, and it does not ship its own cryptographic library in place of Apple’s operating system encryption.
+
+The app uses only encryption provided by Apple’s operating system (e.g., Apple-provided TLS stacks accessed through system frameworks used by the app and its dependencies).
+
+The app is not a VPN client/server, does not provide end-to-end encrypted messaging, and does not provide user-controlled key management or custom cryptographic functionality beyond standard transport security.
+
+Accordingly, the app’s use of encryption is believed to qualify as exempt under U.S. export regulations for mass-market software using standard OS-provided encryption.
+
+Reference
+---------
+Apple: Complying with Encryption Export Regulations
+https://developer.apple.com/documentation/security/complying-with-encryption-export-regulations
+