App Store Connect security

How we store your App Store Connect credentials

LocalizeASO needs an App Store Connect API key only to load and update your app data through Apple's official API. The private key is treated as a secret, encrypted before it is written to the database, and never stored in your browser.

What we store

Issuer ID and Key ID, so we know which Apple API key to use.
The .p8 private key, encrypted server-side before database storage.
App Store Connect app cache for your account, removed when credentials are deleted.

How it is protected

The private key is encrypted with AES-256-GCM before it is stored.
Encryption metadata is stored separately from the encrypted private key value.
Credentials are loaded only by authenticated backend requests for your account.

What we do not do

We do not store the .p8 key in browser storage.
We do not send App Store Connect credentials to analytics tools.
We do not expose the private key back to the dashboard or Figma plugin.

Your controls

You can replace or disconnect credentials in the dashboard at any time.
You can revoke the API key in App Store Connect whenever you want.
You should create a dedicated API key and use the minimum role your workflow needs.

When the key is decrypted

The encrypted private key is decrypted in backend memory only when LocalizeASO needs to create a short-lived Apple API token for an action you requested, such as reading app metadata, updating localizations, uploading screenshots, or checking pricing data.

Recommended Apple setup

Create a dedicated App Store Connect API key for LocalizeASO instead of reusing a key from another tool. For publishing workflows, Apple may require the App Manager role. If you only use read-only workflows, choose the least privileged role that still allows the Apple API operations you need.

Questions

If your company needs a security review or a more detailed data handling answer, contact us at [email protected].