33 lines
1009 B
Markdown
33 lines
1009 B
Markdown
# Export compliance (encryption)
|
|
|
|
Apple may require an "Export Compliance" statement upload when submitting to the Mac App Store.
|
|
|
|
This folder contains:
|
|
|
|
- `EXPORT_COMPLIANCE.txt`: a template statement (fill-in placeholders)
|
|
- `make_pdf.sh`: a helper to fill the template and generate a PDF you can upload
|
|
|
|
## Generate the PDF
|
|
|
|
From the repo root:
|
|
|
|
```bash
|
|
./build_tools/macos/export_compliance/make_pdf.sh \
|
|
--bundle-id com.dryark.strawberry \
|
|
--version 1.2.3 \
|
|
--developer "Dry Ark LLC" \
|
|
--contact "support@example.com"
|
|
```
|
|
|
|
Outputs:
|
|
|
|
- `build_tools/macos/export_compliance/EXPORT_COMPLIANCE.filled.txt`
|
|
- `build_tools/macos/export_compliance/EXPORT_COMPLIANCE.pdf`
|
|
|
|
## Important
|
|
|
|
This template assumes the app uses **only standard OS-provided encryption** (e.g. TLS/HTTPS via system frameworks) and does **not** ship proprietary or standalone crypto libraries.
|
|
|
|
If you bundle your own crypto library (e.g. OpenSSL) or implement custom encryption, you likely need different answers/documentation.
|
|
|