Social Studio Privacy
Last updated: June 23, 2026
Social Studio uses official provider sign-in to connect social accounts chosen by the user. The broker is used to keep provider client secrets out of the iOS and macOS app bundles.
The broker forwards authorization requests and token exchanges between the native app and the selected provider. It does not ask users for provider API keys, client secrets, provider passwords, or dashboard settings.
Access tokens and refresh tokens are stored on the user's device in the system Keychain by the native app. The broker does not persist provider access tokens.
- Provider account identity and permission scopes are used to show connection status and available publishing targets.
- Post drafts, queues, manual exports, and audit records are stored locally by the native app unless a future sync feature is explicitly enabled.
- Operational logs and recovery diagnostics are designed to exclude tokens, passwords, authorization headers, callback codes, and post content.
- Users can disconnect accounts in Social Studio and can revoke access from each provider's account settings.
Service base URL: https://socialstudio.audia.systems/oauth