Security Overview
ScheduleMySocial is built to store and operate the data required for a collaborative social media scheduler. That includes account details, brand setup, draft and scheduled content, approval history, publishing workflows, and integration configuration needed to connect third-party channels.
Because we also offer MCP and CLI access, our security program is designed to cover browser-based usage, API-connected workflows, token-based access, and authenticated requests triggered through those interfaces.
Data We Protect
- Account profiles, authentication data, and workspace membership records.
- Brand settings, content calendars, drafts, approvals, comments, and publishing history.
- Connected platform credentials, API tokens, refresh tokens, and permissions required to publish or sync with supported services.
- MCP and CLI credentials, request metadata, logs, and configuration details needed to operate those tools.
- Operational logs, audit events, and support records used for reliability and incident investigation.
Security Controls and Response
- We use commercially reasonable administrative, technical, and organizational safeguards designed to protect data in transit and data stored in our systems.
- Access to production systems and sensitive data is intended to follow least-privilege principles and role-based access controls.
- We use logging, monitoring, and operational alerting to investigate reliability issues, suspicious behavior, and security events.
- We investigate suspected security incidents and take steps intended to contain, remediate, and recover affected systems.
Stored Data, Backups, and Shared Responsibility
Unlike a transient connector-only product, ScheduleMySocial stores workspace content and scheduling records so teams can collaborate over time. We may also keep backups, logs, and billing records needed for recovery, troubleshooting, compliance, and service continuity.
You are responsible for choosing appropriate teammates, roles, and permissions inside each workspace, protecting your endpoints and local CLI environment, and revoking access promptly when a teammate leaves or when a connected account is no longer authorized for use.