Privacy
What this console keeps about you and the content you write, and why.
What the console stores
- Your name, work email, role, and a salted hash of your password. The password itself is never stored.
- The content you write, every saved version of it, review decisions and comments, and publishing history.
- An audit log of actions taken in the console: who, what, when, and the state before and after a change.
- For connected channels, the access token the channel issues. It is stored encrypted and never sent to your browser.
Why
- To run the approval workflow, to prove what was approved and published, and to answer questions from regulators and internal auditors.
Where it is kept
- In your organisation's own MySQL database. If AI drafting is switched on, the brief and draft text are sent to Groq using your organisation's API key to generate a draft.
- Live post watch reads published pages and posts back from the platforms they were published to.
How long
- Content, versions and the audit log are kept for as long as your organisation's records policy requires. The audit log cannot be edited or deleted from inside the console.
Your choices
- Ask your admin to correct your details or deactivate your account. Questions about this notice go to your organisation's data protection officer.