Data Stored In The App
Release Binder stores the information you enter about projects, releases, checklists, App Store metadata, screenshots, privacy worksheets, dependency inventories, and review notes.
Do not put passwords, API keys, private keys, or other secrets in binder fields, notes, screenshots, or exports. Optional App Store Connect credentials are handled separately as described below.
Local Storage And iCloud Sync
Release Binder is local-first. On Apple devices, app data is stored using Apple's native persistence technologies. Signed Apple builds use CloudKit-backed SwiftData to sync data through your private iCloud account when you are signed in to iCloud and iCloud is available.
The public Android build stores release packets locally and opens or saves files only when you explicitly choose those actions. It does not use iCloud or automatically sync with the Apple versions. Release Binder does not operate a custom backend for this data.
Third-Party Services
The app does not send your release data to a custom web service. iCloud sync is provided by Apple through CloudKit in signed Apple builds. The public Android build does not include CloudKit transport.
If you choose to connect App Store Connect, the Apple app stores your API key ID, issuer ID, and private key in the local device Keychain. These credentials are not included in binder data, iCloud sync, or release packet exports. The app uses them to authenticate directly with Apple when you fetch app information or confirm a previewed metadata push. A confirmed push sends the selected listing fields to App Store Connect. The connection is optional.
App Store bundle ID: com.teamadler.releasebinder. Android package: com.teamadler.releasebinder. CloudKit container for Apple builds: iCloud.com.teamadler.releasebinder.
Contact
For privacy questions, contact support@releasebinder.com.