Privacy Policy

• Admin account records used to authenticate operators into the application.
• Workspace, content brief, content item, content variant, approval, export, and publishing records created during normal use.
• Connected social account metadata such as platform, external account identifier, username, nickname, publish mode, connection status, and timestamps.
• Operational metadata used for audit, scheduling, error investigation, and delivery history.

When a social account is connected through an official OAuth flow, the application stores encrypted access tokens and, where available, encrypted refresh tokens. These tokens are used to maintain account connectivity, fetch account profile details, and support authorized publishing or account management actions.

The application also stores token expiry information and granted scopes so the service can determine whether a connection remains valid and what actions it is allowed to perform.

Account metadata and workflow records are retained so operators can see which account was connected, which workspace used it, what approvals were granted, what content was exported or published, and what manual actions were required.

This metadata supports auditability, troubleshooting, schedule validation, duplicate prevention, risk controls, export packaging, and safe handoff between operators.

The service may store generated images, derived media, captions, titles, hashtags, slide plans, export bundles, and delivery notes to support review, manual posting, and content lifecycle management.

Operators should avoid submitting personal information that is not required for campaign execution or account administration.