Integration

Expo builds your mobile app in the cloud, prepares store submissions, and ships over-the-air updates.

What it does

• Starts a cloud build of the app the agent changed.
• Reads build and submission status back into Selfbase.
• Prepares an over-the-air update when a Plan you approved calls for one.
• Submits to a store only when you tap submit. Apple requires that the submission comes from you.

Connecting

Open Workspace settings, then Connections, and choose Expo. Paste an access token from expo.dev, under Account settings, then Access tokens.

What each permission is for

• An Expo access token Acts on your Expo account as you. The token carries the permissions of the account that created it.
• A read of your Expo account One call when you paste the token, to confirm it works and to name the account.

We do not ask for your Expo password, and we never create a token of our own.

How your credentials are held

Your credential is encrypted with a key that belongs to your workspace and stored as ciphertext. It is decrypted only at the moment it is used, and never inside a sandbox where code runs. We never log it.

Removing it

Disconnect under Workspace settings, then Connections, which deletes our copy. Revoke the token at expo.dev under Account settings, then Access tokens, which ends our access immediately.

To have everything Selfbase holds about you deleted, see data deletion.

Support

Email hello@selfbase.com. Our privacy policy and terms cover every integration.