Data and permissions

What Quorra asks macOS for, what it stores, and where.

Quorra asks macOS for two approvals. Nothing else.

What crosses which boundary

SurfaceWhat Quorra uses it forScope
Your AWS folderImports sessions and profiles once; writes them back only if you enable export~/.aws, or a folder you choose
Network ExtensionForwards outbound TCP for the metadata address to Quorra’s local backend169.254.169.254:80 only
macOS KeychainStores Identity Center tokens and temporary role credentialsNever in Quorra’s own files
Local endpointsServe a chosen profile to toolsBound to 127.0.0.1, never your network
The app itselfRuns as you, notarized and hardened; no root process or privileged helperYour user account

Credentials

Identity Center access tokens and temporary role credentials are stored in the macOS Keychain. They are not written into Quorra’s application files, and they are minted on demand rather than held indefinitely.

Your AWS files

With Export to AWS folder off, which is the default, Quorra never writes to your AWS files.

With it on, Quorra updates only the sso-session and profile sections it manages, and keeps your other sections, keys and comments as they are.

The network

IMDS backends bind to 127.0.0.1 and are not reachable from your local network. The default endpoint is reachable only through the exact 169.254.169.254:80 Network Extension rule.