Operate the service
Authenticate owners, route approved content to the exact connected account, run explicit schedules and expose scoped agent operations.
root@poststeward:~$ cat privacy
Privacy Policy
This policy explains how PostSteward handles information when an owner connects social accounts, gives an AI agent scoped publishing authority, schedules work or inspects publishing evidence.
Effective date: 19 September 2026 · Contact: community@oneclickpostfactory.com
1. Information PostSteward processes
- —Owner identity: sign-in subject, verified email and the minimum session records needed to authenticate the workspace.
- —Connected social accounts: provider, stable account identity, account alias, granted capabilities and encrypted OAuth credentials or refresh material where the provider supplies them.
- —Publishing data: projects, exact campaign copy, schedules, idempotency keys, delivery states, provider post identifiers, published links, readback evidence and available metrics.
- —Agent access: grant identifiers, scopes, expiry and revocation state. Plaintext agent tokens are shown once and are not returned later.
- —Optional source connections: selected repository identifiers and encrypted owner-authorised credentials when an owner deliberately connects a supported private source.
- —Billing records when enabled: subscription/customer references and entitlement state from the payment processor. PostSteward does not store full payment-card details.
- —Security and recovery state: bounded OAuth state, deletion/recovery state, request identifiers and minimal records needed to prevent deleted authority from being resurrected.
2. Why the data is used
Keep publishing safe
Verify identities and scopes, prevent blind duplicate retries, detect authority drift and preserve ambiguous outcomes for inspection.
Provide evidence
Keep durable receipts so owners and agents can distinguish scheduled, verified, unverified, failed and uncertain provider effects.
Support and security
Investigate faults, enforce limits, respond to deletion/privacy requests and protect workspaces against unauthorised access.
3. Service providers and external platforms
PostSteward may interact with services chosen by the owner, including identity providers, social networks such as X, Threads/Meta and LinkedIn, Cloudflare infrastructure, GitHub for an optional connected source, and Stripe when paid billing is enabled. Those providers process information under their own terms and privacy policies.
Posting to a social network is an external effect: once content is published, that network may retain copies, engagement, logs or other information independently of PostSteward.
4. Security
- —Provider credentials are encrypted at rest with authenticated encryption and workspace-specific context.
- —Browser mutations require an authenticated session plus origin/CSRF checks.
- —Agent grants are scoped, expiring and revocable; owner-level admin authority is not delegated through the agent grant endpoint.
- —Sensitive OAuth codes, access tokens and refresh tokens are not intended for application logs or browser storage.
- —Uncertain provider writes are preserved as uncertain rather than retried blindly.
5. Retention and deletion
Operational records are retained while they are useful to the workspace and within service safety ceilings. Owners can request workspace erasure. A completed deletion removes locally usable provider credentials, sessions, grants, workspace application records, linked private-source credentials, provider OAuth state and related workspace mappings.
A minimal completed-deletion tombstone may be retained to prevent restored historical state from resurrecting deleted publishing authority. Provider-side posts and provider-side authorisation grants are controlled by the relevant external platform and may require separate deletion or revocation there.
6. Your choices and requests
Depending on applicable law, you may have rights to request access, correction, export, restriction or deletion of personal data. You may also disconnect a social account or revoke an agent grant from the connected workspace.
For a privacy request, email community@oneclickpostfactory.com. Include the email address used to sign in and the nature of the request. Do not send passwords, access tokens, API keys or social-provider secrets by email.
7. Changes to this policy
This policy may be updated as PostSteward's production capabilities, providers or legal obligations change. Material changes will be reflected by updating this page and its effective date.
Optional model preparation
If you connect a workspace-owned OpenAI or Cloudflare model account, PostSteward encrypts its key and sends the selected release evidence, approved context and drafts to the selected Cloudflare-hosted model or OpenAI route for preparation and checking. Your selected account funds the configured inference route. Private or unreleased source disclosure requires explicit owner approval. Keys are not given to agents or included in generation input or workspace export.
OpenAI responses are requested with storage disabled and Cloudflare Gateway prompt/response logging is suppressed; metadata-only logging is optional. Cloudflare account-wide gateway token scopes and shared account billing require deliberate owner review. These controls do not guarantee zero retention under the provider’s terms. Inspect your provider’s data-processing and billing terms before connecting an account. Preparation records remain private; removing an exported preparation retains immutable campaigns, receipts, spending and existing operation history. Workspace erasure remains the separate reviewed process.