Workspace access
Account sessions are protected with secure cookie settings in production. Workspace roles limit who can edit, approve, connect channels, or manage billing.
Security without certification theater
Publishing security.
Control access, trace delivery.
PostOnce.co is designed to minimize credential exposure, preserve human checkpoints, and keep a reviewable record of publishing activity.
Ask a security question01Least necessary access
Connect only the destinations and permissions a workflow needs.
02Purpose-bound credentials
Use platform authorization, app passwords, API keys, bots, or webhooks. Lemmy beta briefly accepts only a dedicated bot password to mint a one-week JWT; it never stores that password.
03Visible automation
Attempts, responses, destination states, and retries remain attached to the campaign.
04Honest assurance
We do not claim a certification or audit that has not been completed.
Security model
Defense in layers, stated in plain English.
Security is a product behavior, an operating practice, and a shared responsibility—not a badge in the footer.
Platform credentials
Where available, PostOnce.co uses the platform’s authorization flow. App passwords, API keys, bot tokens, and webhook secrets should be scoped and revocable.
Encrypted in transit
Production traffic must use HTTPS. The deployment owner is responsible for valid TLS termination, security updates, backups, and restricted administrative access.
Role and queue boundaries
Viewers cannot change content; editors can prepare it; owners and admins control credentials, workflows, and billing. Multi-step team approvals shown in the demo are a product preview. The separate API and MCP reviewed-publish flow enforces browser approval of an exact publish plan before delivery; hosted MCP cannot bypass that review.
Payment separation
Payment card details are entered with the payment provider. PostOnce.co stores subscription identifiers and billing status, not complete card numbers.
Recovery and response
Operational logs support troubleshooting, and access should be limited to authorized operators. Confirmed incidents are assessed, contained, and communicated as required.
Before connecting a channel
Use credentials you can revoke without disrupting everything.
- 01Prefer a platform authorization flow
When OAuth or an equivalent consent screen is available, review the requested permissions and connect the correct account.
- 02Scope keys and webhooks
Create a dedicated app password, API key, bot, or webhook for PostOnce.co. Avoid reusing an administrator credential.
- 03Keep high-impact routes manual
Do not enable automatic workflows for regulated, client, legal, or brand-sensitive destinations until approval gates are launch-ready.
- 04Revoke when no longer needed
Disconnect the channel in PostOnce.co and revoke its grant from the destination platform when a workflow ends.
Current assurance
What we do not claim.
No SOC 2 or ISO 27001 claim
PostOnce.co does not currently claim SOC 2, ISO 27001, PCI DSS certification for the application, a public penetration-test report, or a formal bug-bounty program. Payment processing may be covered by the payment provider’s own compliance program.
Security practices and this page will be updated as independent assurance becomes available.
Responsible disclosure
Found a security issue?
Send a concise report with the affected URL or feature, reproduction steps, impact, and a safe way to contact you.
Security contact[email protected]
Use the subject “Security report”. Do not access other users’ data, disrupt the service, run denial-of-service tests, or publish sensitive details before we have had a reasonable opportunity to respond.
We will acknowledge a credible report as soon as practical. No reward is promised unless a written bounty program says otherwise.Publish widely. Authorize narrowly.
Explore the product with sample data, then connect only the destinations and permissions your workflow needs.