How does Lingue store my App Store and Google Play credentials?

You choose when you connect. Cloud storage encrypts your Apple .p8 or Google service-account JSON at rest with AES-256-GCM, with the encryption key held outside the database. Local storage encrypts the key with a passphrase you choose and keeps it only in your browser, never reaching our servers' storage. In both modes the key travels over TLS during validation and sync, is held in memory only, and is never logged.

What happens when I sync screenshots to the stores?

Lingue renders each locale and device at exact resolution and uploads them, replacing the screenshots currently in the store for those locales and devices. App Store changes land on the editable version and only go public when you submit for review; Google Play changes are committed as one atomic edit.

Can I import my existing store listing?

Yes. On a connected store, use Import app to create a project mirroring the store's listing text for every locale, the active locales, the app icon, and the app category.

Store Sync help

Connect your App Store Connect and Google Play accounts to Lingue to import your existing store listings and publish the screenshots you design straight to both stores, per locale and device.

How we handle your store credentials

You choose how your store key is stored when you connect:

Cloud (recommended). Your key (the Apple `.p8` or the Google service-account JSON) is encrypted at rest with AES-256-GCM. The encryption key is held outside the database, so a database compromise alone can't reveal it. Cloud storage lets sync run without re-entering your key.
Local. Your key never reaches our servers' storage. It's encrypted with a passphrase you choose and kept only in this browser. You re-enter the passphrase each time you sync, and you'll re-upload the key on another device or after clearing site data. If you lose the passphrase it can't be recovered.

In both modes the key travels over TLS to our servers during validation and sync, because Apple's JWT signing and Google's upload flows can't run from a browser. There it's held in memory only for the duration of the request, and it's never logged.

Keep your own backup of the Apple `.p8`. App Store Connect only lets you download it once.
You can revoke a key any time in App Store Connect or Google Cloud. "Disconnect" in Lingue erases the stored key immediately while keeping your sync history.

Set up your store

Set up App Store Connect. Create an App Store Connect API key with the App Manager role.
Set up Google Play. Create a service account and invite it to your Play Console.

Connect & validate

Open the account menu in the top bar and choose Integrations (or go to Settings → Integrations), then pick App Store Connect or Google Play Store.
Enter your credentials, pick a storage mode, and click Validate.
A green check means the connection is healthy. A yellow warning means it needs attention. Read the error (common causes: agreements not accepted, wrong key role, API not enabled, or the service account not invited).

Import an existing listing

On a connected store, click Import app, choose the app (App Store: pick from the list; Google Play: enter the package name), and Import.
Lingue creates a project mirroring the store's listing: the listing text for every locale, the active locales, the app icon, and the app category.

Publish your screenshots

Design your screenshots, open Export, and use Sync to App Store / Google Play alongside Export locally.
Lingue renders each locale × device at exact resolution and uploads them, replacing the screenshots currently in the store for those locales and devices.
App Store changes land on the editable version and only go public when you submit for review. Google Play changes are committed as one atomic edit.
Watch live progress; if some uploads fail you'll see why and can retry just the failures.

Troubleshooting

Agreements not accepted / wrong key role (Apple). Accept pending agreements in App Store Connect and make sure the API key has the App Manager role.
No editable version (Apple). Create the next version in App Store Connect first, then sync.
API not enabled / service account not invited (Google). Enable the Google Play Android Developer API and invite the service-account email with Draft apps + Manage store presence.
Some screenshots were rejected. Check the per-device limit (10 on the App Store, 8 on Google Play) and that images match the device's exact dimensions.