ENCRYPTION WORKSHEET - iOS AND macOS
Prepared 2026-11-20. Adapt to the shipped app, SQLCipher version and markets.
These are technical descriptions, not a completed export classification.

TECHNICAL ANSWERS COMMON TO THE TWO SQLCIPHER CASES
- Does the app use encryption? Yes.
- Proprietary/non-standard algorithms? No, IF the app uses only unmodified
  standard SQLCipher algorithms and has no other proprietary cryptography.
- Standard algorithms outside, or in addition to, Apple OS encryption? Yes:
  SQLCipher is a bundled third-party cryptographic implementation.
- Is it exempt? Determine for this app's functionality and destinations.
  A library classification or an absence of App Store document requests is
  not a blanket exemption for your app or for all export obligations.
- Available in France? Answer according to actual App Store availability.
- Only distributed in the United States? Answer Yes only if that is true.

CASE A - APP'S OWN LOCAL DATABASE
Use only if all these facts are correct; replace [APP_NAME] and version.

[APP_NAME] uses the SQLCipher [VERSION] library to encrypt its own local
SQLite application database at rest using standard AES-256 encryption.
This protects locally stored application data. The app does not expose
database encryption/decryption as a user-facing general utility. It does
not implement proprietary or non-standard cryptographic algorithms.

Optional sentence ONLY if verified:
The app does not transmit database contents, encryption keys or passwords
to the developer or to third-party services.

Internal protection can affect the classification analysis, but it does
not automatically establish an exemption. Verify key storage, backups,
sync, other SDKs and all other crypto before using this description.

CASE B - SQLITETOOLS USER DATABASE ENCRYPTION / DECRYPTION
Use only if this describes the released features; adapt version and scope.

SQLiteTools uses SQLCipher [VERSION] to let users encrypt and decrypt
SQLite databases locally. Users select a database file and supply the
required password or key. Encryption produces a SQLCipher-compatible
encrypted database using standard AES-256 encryption; decryption requires
the correct key and compatible cipher settings. The app does not implement
proprietary or non-standard cryptographic algorithms.

Optional sentence ONLY if verified:
Database files, passwords and encryption keys are processed on the user's
device and are not uploaded to the developer or to third-party services.

Do not claim it decrypts every encrypted SQLite format. SQLCipher does not
make arbitrary vendor-specific formats compatible. Do not describe this
case as only internal database protection: encryption is a user feature.
This difference can affect export classification and exemption eligibility.

APP STORE CONNECT ROUTE
Apps > your app > App Information > App Encryption Documentation (+), or
resolve Missing Compliance on the uploaded build. Set the description and
availability first. Answer the live questions using the actual app facts.
Apple's documentation table lists a French declaration for standard
algorithms outside Apple OS encryption if distributing in France; it lists
CCATS plus the French declaration (if France) for proprietary algorithms.
Follow the app-specific assessment and upload the requested documents.
The SQLCipher vendor's ANSSI declaration does not automatically cover your app.
Record Apple's outcome and any separate BIS/ANSSI analysis with the release.

INFO.PLIST - CONDITIONAL, NOT AUTOMATIC
ITSAppUsesNonExemptEncryption = NO only when the app has no encryption or
all its encryption is confirmed exempt. YES when it uses non-exempt
encryption. Omitting the key while assessing causes the questionnaire to
be asked. Do not select NO simply to remove the Missing Compliance warning.
If Apple approves documentation and provides an export compliance code,
set ITSEncryptionExportComplianceCode to that exact Apple-provided value.
It is not your own ECCN, a library ANSSI number or a value to invent.

EXTERNAL EXPORT CHECK
Apple acceptance does not replace applicable U.S./French legal obligations.
Determine classification, available exceptions, destinations and reporting
for the app. Applicable BIS self-classification reports are generally due
February 1 for the prior year; eligibility and exceptions matter. Obtain
export advice if the shipped functionality does not clearly fit the rules.

PRIMARY REFERENCES
https://developer.apple.com/help/app-store-connect/manage-app-information/overview-of-export-compliance
https://developer.apple.com/help/app-store-connect/manage-app-information/determine-and-upload-app-encryption-documentation
https://developer.apple.com/help/app-store-connect/reference/app-information/export-compliance-documentation-for-encryption
https://developer.apple.com/documentation/bundleresources/information-property-list/itsappusesnonexemptencryption
https://developer.apple.com/documentation/security/complying-with-encryption-export-regulations
https://www.zetetic.net/sqlcipher/design/
https://www.zetetic.net/sqlcipher/export-compliance/
https://media.bis.gov/learn-support/encryption-controls/annual-self-classification
https://cyber.gouv.fr/reglementation/reglementation-identite-confiance-numerique/controles-reglementaires-cryptographie/controle-moyen-de-cryptologie/
