# Security: How BuildFerry Protects Your Apple Key and Builds

> How BuildFerry stores your App Store Connect key, signs builds in short-lived containers, and controls who can install your app.

Last updated: 2026-11-01
Canonical: https://buildferry.app/security

BuildFerry holds an Apple key that can act on your developer account, so here's exactly how it's handled.

## Your Apple key

- Keys and certificates are encrypted at rest.
- A signing container receives the key only for your job and deletes it when the job ends.
- Each team's jobs run in that team's own short-lived container, which exits soon after the work finishes.
- A container's access is limited to its own team and expires, so it can't reach another customer's key or builds.
- You can use an App Store Connect key limited to what signing needs, and revoke it in App Store Connect at any time.

## Your builds

- Builds are stored in private object storage and are only available through signed-in or per-tester links.
- App Store downloads are encrypted and are refused.

## Who can install

- A share link only lets people ask. Nothing reaches Apple until you approve that iPhone, unless you turn on auto-approve.
- Share links can have a PIN and an expiry date.
- You can revoke a tester at any time.

## Reporting a problem

If you find a security issue, email [support@buildferry.app](mailto:support@buildferry.app). Please give us time to fix it before sharing details publicly.