Acceptable Use Policy

Core rule: use PostOnce.co to distribute content you are authorized to publish, to audiences and destinations where it belongs. Automation does not excuse spam, deception, rights violations, or platform-policy evasion.

1. Authorization

You may connect and publish only to accounts, pages, sites, bots, channels, webhooks, groups, and communities you own or are expressly authorized to manage. Do not obtain, share, or use credentials without permission, and do not bypass a destination’s access controls or review process.

2. Prohibited content and conduct

You may not use PostOnce.co to create, upload, coordinate, or distribute:

• Content or activity that violates applicable law or a binding legal order.
• Child sexual abuse material, sexual exploitation, or grooming.
• Credible threats, incitement to violence, targeted harassment, stalking, or doxxing.
• Deceptive impersonation, fraud, phishing, scams, or materially misleading identity or affiliation claims.
• Malware, ransomware, credential theft, malicious code, or instructions primarily intended to compromise systems.
• Content that infringes copyright, trademark, privacy, publicity, or other rights.
• Unlawful sales or promotion of weapons, controlled substances, stolen goods, or regulated products.
• Non-consensual intimate imagery or sexual content prohibited by the destination.
• Content designed to suppress rights, unlawfully discriminate, or exploit vulnerable people.

3. Spam and platform manipulation

You may not:

• Send repetitive, irrelevant, deceptive, or unsolicited content at scale.
• Use misleading links, fake engagement, coordinated inauthentic behavior, or undisclosed account networks to manipulate reach.
• Evade rate limits, account restrictions, platform review, moderation, or technical safeguards.
• Automatically repost content into communities where automation, self-promotion, or that content is prohibited.
• Use scraped, purchased, or improperly obtained audiences or credentials.
• Continue publishing after a destination owner, recipient, or platform has withdrawn permission.

4. Responsible automation

Review every automated workflow before enabling it. Keep destination permissions current, use human approval where context or risk warrants it, and monitor delivery errors and audience responses. Do not create retry loops outside PostOnce.co to defeat platform backoff or safety limits.

You remain responsible for content published through a scheduled, triggered, API, webhook, feed, or evergreen workflow.

5. High-risk and regulated use

Do not use PostOnce.co as the sole control for emergency alerts, public-safety instructions, financial transactions, medical decisions, election administration, or other activity where a delayed, duplicated, or incorrect publish could cause substantial harm.

If you publish advertising, endorsements, political content, financial promotions, health claims, contests, age-restricted content, or regulated offers, you are responsible for required review, targeting, disclosures, records, and destination permissions.

6. System and service abuse

You may not interfere with the service, probe it without authorization, run denial-of-service tests, distribute malicious payloads, bypass plan limits, create accounts to evade enforcement, reverse engineer except where law permits, or use the service to build or benchmark a competing model through unauthorized bulk extraction.

Reasonable security research should follow the guidance on our Security page.

7. Enforcement

We may investigate suspected violations and may warn, rate-limit, remove content from our systems, disable a workflow or connector, suspend access, or terminate an account. We consider severity, intent, scale, recurrence, potential harm, platform requests, and whether a violation can be safely cured.

We may preserve and disclose information when reasonably necessary to comply with law, protect people or systems, prevent fraud, or enforce our agreements. Where appropriate and lawful, we will provide notice and an opportunity to appeal by contacting support.

8. Reporting

Report suspected abuse to [email protected] with the relevant workspace, destination, URL, content, reason for concern, and a safe way to contact you. Do not include sensitive personal information unless necessary.

9. Changes

We may update this policy to respond to product changes, platform requirements, emerging abuse, or law. Material changes will be dated and noticed when required.