The questions we actually get.

No. A draft becomes publishable only once you approve it in the validate queue. Approval is recorded with the time and the person who gave it, and there is no code path from draft to platform that skips it.

You do, or a drafting agent proposes one from the brand’s voice and the article or event behind it. Either way what comes out is a draft. It is only ever a proposal until you approve it.

A transient failure is retried with a backoff. A permanent one is surfaced with the platform’s own error message, and the post is held. Nothing is dropped quietly, and the calendar shows the real state.

Yes, from inside Opal, against the same API that published it. The takedown writes its own audit row.

Yes. One draft can target several channels, formatted per platform, and each channel keeps its own settings and its own publish time.

Only accounts you connect yourself, through the platform’s own sign-in and consent screen, and only with the permissions that screen lists. Opal never asks for a platform password.

Disconnect the channel inside Opal, which deletes the stored token, or revoke Opal from the platform’s own app-permissions screen. Either one stops publishing immediately. Each integration page states where that screen is.

Opal tracks each token’s expiry, refreshes what can be refreshed, and warns you before a platform cuts access. Meta access in particular lapses about every 90 days. Posts on a dead channel are held until you reconnect.

No. On Facebook and LinkedIn it publishes as a Page or company page you administer. On the other platforms it publishes to the account that authorized it.

Opal trains nothing. Drafting assistance calls a third-party model API at the moment you ask for a draft, and Opal keeps no training corpus of your content. Connected-account data is never sold and never shared for advertising.

The access token, encrypted at rest, and the account’s public identity: its id, display name, username and avatar, so you can confirm which account is connected. Nothing else is read from the profile.

Yes. Disconnecting deletes the credentials for that channel. For everything else, write to hello@arthea.ai and we will delete it and confirm in writing.

On managed hosting and database infrastructure, reached over TLS, with every credential encrypted at rest. The security page has the detail.

Operators who publish for more than one brand and want one calendar, one approval queue and one audit trail instead of a tab per platform. Arthea built it to run its own brands and opens it to teams that work the same way.

Book a demo. We look at your channels and your calendar, connect what you want connected, and set up the approval queue with you.

Pricing depends on how many brands and channels you run. We quote it on the call rather than publishing a number that would be wrong for most people.