How your workspace is protected.

Every row of content, media, calendar entry, social account and analytics record belongs to an organisation. Access is enforced in the database itself, not just in the interface, so a request for another organisation's data returns nothing - even if someone crafts the request by hand.

• Connecting an account happens through the network's own authorisation screen. We never ask for, see or store your social password.
• The resulting tokens are exchanged server-side, encrypted before they are stored, and decrypted only inside the publishing worker.
• The browser is not permitted to read credential or token records at all, for any role.
• Disconnecting an account deletes its stored credentials.

Team members are admins, editors, approvers or viewers. Publishing can require approval, and approval decisions are recorded against the post. Ownership transfer and member removal are protected so a workspace cannot be left without an owner.

Significant actions - invitations, role changes, approvals, publishes, disconnections, deletions - are written to an audit log with the actor and timestamp, so you can answer "who did that, and when".

Scheduled publishing and metrics collection run as background jobs that authenticate with a server-side secret and refuse unauthenticated calls. Jobs are idempotent, retried with backoff, and recorded so a failure is visible on your publishing health page rather than silently swallowed.

Invitation links are single-use and stored as a hash, so the raw link cannot be recovered from the database after it is created. Expired or revoked invitations stop working immediately.

You can export your workspace from Settings and delete your organisation with a typed confirmation. Deletion removes workspace content, media and stored social credentials. See the privacy notice for retention detail.

If you believe you have found a vulnerability, tell us before telling anyone else. Use the contact form with enough detail to reproduce it. We will acknowledge, investigate and keep you informed. We do not currently run a paid bug-bounty programme, and we make no certification or compliance-audit claims.