Know who holds the keys and what happens when an agent acts.

OpenPMM is built and operated by Heyora UG (haftungsbeschränkt), a registered German company. The public imprint names the company, managing director, Berlin address, commercial register number, VAT ID, and contact address.

A CLI-managed agent works through the openpmm command and never reads its credential store. A direct API client uses a separate scoped credential. Provider OAuth tokens stay server-side and are not returned in Post content, CLI output, webhook payloads, or the writing context.

An agent can prepare text, media, a Destination, and timing. Publishing and scheduling require an explicit confirmation value. OAuth also remains a browser checkpoint. This keeps the person responsible for the account in the loop when access is granted or content reaches an audience.

A publish response means that OpenPMM accepted or completed the state change. It does not always mean that the provider finished. OpenPMM documents bounded CLI waiting, Post state, receipts, idempotency keys, ETags, stable errors, and request IDs.

Workspace webhooks sign Post events with an endpoint secret. OpenPMM documents payload verification, endpoint testing, delivery inspection, and secret rotation. The previous secret remains valid during a documented overlap when a secret is rotated.

The privacy policy describes account, publishing, provider, analytics, feedback, and website processing separately. It names relevant processors and transfer safeguards. OpenPMM does not describe all processing as EU-only because publishing necessarily sends content to the social providers a user selects.