Skip to main content
Security, approvals, and advanced automation Level: Beginner 11 min read

Zero-Relay Privacy Guarantee: How FlightDeck Connects Directly to Apple

Why FlightDeck uses a zero-relay architecture, how network requests travel directly from your Mac to Apple without intermediary cloud servers, and how to verify traffic locally.

Published: 2026-11-03 • Last Updated: 2026-11-03 • Author: Kip Lawrence
Key MCP Tools:

Overview: The Third-Party Cloud Relay Dilemma

When engineering organizations connect automated developer tooling to Apple’s App Store Connect API, security and compliance teams face a critical question:

"Does this tool upload our App Store Connect private keys (.p8), proprietary app metadata, or binary assets to an external cloud backend?"

For most web-based developer tools and CI/CD SaaS platforms, the answer is unfortunately yes: you must upload your .p8 private key to their cloud databases, where it is stored on remote servers, decrypted in their worker nodes, and relayed through their infrastructure to contact Apple.

FlightDeck is architected on a Zero-Relay Privacy Guarantee for App Store Connect credentials and operations.

FlightDeck operates strictly as a native macOS desktop application. Every App Store Connect API request, every cryptographic token generation, and every binary asset upload originates directly on your local workstation and travels directly over HTTPS to Apple’s official endpoints. There are no intermediary proxy servers, no central databases, and no cloud relays handling your Apple credentials.

TEXT
┌─────────────────────────────────────────────────────────────────────────────┐
│                    ZERO-RELAY VS. CLOUD RELAY ARCHITECTURES                 │
├─────────────────────────────────────────────────────────────────────────────┤
│ TYPICAL CLOUD RELAY MODEL (HIGH ATTACK SURFACE)                             │
│ [Your Mac] ──(Upload .p8 Key)──> [Third-Party Cloud] ──> [Apple API]        │
│                                  • Remote storage of keys                   │
│                                  • Intermediary logging & MITM risk         │
│                                                                             │
│ FLIGHTDECK ZERO-RELAY MODEL (DIRECT CREDENTIAL ISOLATION)                   │
│ [Your Mac] ────────────────────────────────────────────> [Apple API]        │
│   ├── Private Key in macOS Keychain                                         │
│   ├── In-Memory Ephemeral JWT Signing                                       │
│   └── Direct HTTPS to api.appstoreconnect.apple.com                         │
└─────────────────────────────────────────────────────────────────────────────┘

Architectural Principles of Zero-Relay Privacy

FlightDeck’s security architecture adheres to four non-negotiable principles:

1. Direct Network Path for Apple API Traffic

All outbound App Store Connect HTTP communication initiated by FlightDeck connects directly to:

  • API Endpoints: https://api.appstoreconnect.apple.com (enforcing strict HTTPS scheme and host locking via ProductionHttpTransport).
  • Asset Upload Storage: Apple’s presigned cloud endpoints (such as developer-store-us-east-1.s3.amazonaws.com or Apple CDN targets specified dynamically in Apple API responses).

At no point does App Store Connect API traffic, request headers, authorization tokens, or binary data transit through a FlightDeck-operated cloud proxy or logging relay.

2. Differentiating Auxiliary Traffic vs. Credential Zero-Relay

To maintain complete architectural transparency, developers should understand the exact scope of network traffic generated on their machine:

  • Zero-Relay for Apple Credentials: Your App Store Connect .p8 private keys, Issuer IDs, Key IDs, and generated JWT tokens NEVER leave your local Mac.
  • Desktop Software Licensing (RevenueCat): Like many native desktop applications, FlightDeck contacts api.revenuecat.com solely to verify software subscription entitlements and trial validity. This traffic uses anonymous device tokens and contains zero Apple credentials, bundle IDs, or release metadata.
  • AI Model Provider Communication: Your AI editor (Cursor, Claude Code, Windsurf) connects to its respective model provider (e.g. Anthropic, OpenAI) to generate prompts. While private keys are strictly withheld from MCP tool outputs, app metadata returned in tool responses (such as app names, version numbers, and localized strings) is naturally processed by your LLM to answer your questions.

3. Local Loopback MCP Server

FlightDeck embeds a Model Context Protocol (MCP) server (StreamableHttpTransport) that listens strictly on the local IPv4 loopback interface:

  • Endpoint: http://127.0.0.1:51122/mcp
  • DNS Rebinding Defense: The server evaluates the incoming HTTP Host header. Any request carrying an origin other than localhost, 127.0.0.1, or ::1 is rejected with HTTP 400 Bad Request.
  • Origin Validation: Evaluates browser Origin headers to defend against cross-site request forgery.
  • Optional Bearer Authentication: Supports 256-bit session credentials verified in constant time.
  • No External Ingress: The server does not bind to 0.0.0.0 or public network adapters; external computers on your local network cannot connect to your MCP endpoint.

4. Local Keychain Storage & Ephemeral Signing

Your App Store Connect .p8 private keys are never written to disk in plaintext, configuration files, or database caches. They are stored natively in the macOS login Keychain using Apple’s Security.framework (kSecClassGenericPassword). When an operation requires authentication, FlightDeck retrieves the key into memory, signs an ephemeral ES256 JSON Web Token (JWT) with a maximum 20-minute lifetime, and sends the bearer token directly to Apple.


Empirical Verification: How to Audit FlightDeck Traffic

You do not have to take FlightDeck’s privacy claims on faith. You can verify network behavior directly on your Mac using standard macOS diagnostic tools:

Step 1: Verify Loopback Socket Binding

Open Terminal and inspect the network listening state of the FlightDeck MCP server:

BASH
lsof -nP -iTCP:51122 -sTCP:LISTEN

Expected Output:

TEXT
COMMAND    PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
FlightDeck ...  ...   ...  IPv4 0x...           0t0  TCP 127.0.0.1:51122 (LISTEN)

The binding strictly displays 127.0.0.1:51122, confirming that the server does not accept connections from external IP addresses.

Step 2: Inspect Outbound Connections

While performing an App Store Connect operation (such as listing apps or inspecting versions), inspect FlightDeck’s active outbound network sockets:

BASH
netstat -anv -f inet | grep -E "FlightDeck|51122|apple"

You will observe outbound connections directed exclusively to Apple network subnets (17.0.0.0/8) and official Apple domain endpoints. Zero connections are made to third-party analytics, tracking, or proxy hosts.

Step 3: Deep Packet Inspection with Proxyman or Little Snitch

For enterprise audit teams:

  1. Configure an HTTP monitoring proxy such as Proxyman, Charles, or Little Snitch.
  2. Trigger an automated release task via your AI assistant.
  3. Review the complete HTTP flow: - Source IP: Localhost (127.0.0.1) - Destination IP: api.appstoreconnect.apple.com - Zero intermediary webhook dispatches.

Enterprise Compliance & Risk Mitigation

For security teams navigating SOC 2, ISO 27001, or internal InfoSec audits, FlightDeck’s zero-relay architecture simplifies vendor compliance reviews:

Risk Category Cloud Relay Approach FlightDeck Zero-Relay Approach
Credential Breach Exposure High (Key stored on vendor servers) Zero (Key never leaves local Mac Keychain)
Subprocessor Audit Burden High (Vendor is a subprocessor handling keys) Zero (FlightDeck is local software, not a subprocessor)
Data Residency Compliance Complex (Data transits vendor regions) Simple (Data moves only between client and Apple)
Vendor Server Outage Impact Outage disables deployment pipeline Zero impact (Pipeline depends only on Apple uptime)

Security Best Practices for Developers

Even with a zero-relay architecture, maintain strict local workstation hygiene:

  1. Protect Your Mac Account: Ensure your macOS user account requires a strong password and utilizes FileVault disk encryption.
  2. Never Paste .p8 Keys into AI Prompts: Even though FlightDeck is zero-relay, pasting private keys directly into an AI chat window exposes them to your AI model provider's context logs. Store keys in FlightDeck once, and let the desktop app sign requests behind the scenes.
  3. Keep Approval Center Enabled: Always review staged mutations in the FlightDeck Desktop Approval Center before giving execution permission to autonomous AI agents.

Official References


Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store