Salamnder Social Studio uses least-privilege connector access, OAuth 2.0 authorization code flow with PKCE, short-lived signed authorization codes, server-side token storage, and explicit user confirmation before publishing.
Connector safety
- Reading and saving drafts never publishes them.
- Publishing and scheduling are separate, intentional actions.
- Social-network access tokens are never returned to MCP clients or browsers.
- OAuth redirects are restricted to an audited allowlist and HTTPS outside localhost.
- Tool calls require an authenticated workspace and are rate limited.
Data protection
Workspace data is isolated by user id. Provider credentials are handled only by trusted server routes and are excluded from exports. See the Privacy Policy for retention, subprocessors, and deletion rights.
Reporting a vulnerability
Email sal@salamndersocialstudio.com with the subject “Security report.” Include the affected URL, impact, and reproduction steps. Do not include live access tokens or another person's data. We will acknowledge valid reports and coordinate remediation before public disclosure.