Acceptable Use Policy

1. Purpose

CMSPost is designed for lawful agency operations, client onboarding, content creation, SEO, website publishing, social media, communications, reviews, reputation workflows, and related business activities. Use must protect customers, third parties, connected platforms, and CMSPost infrastructure.

2. Lawful and authorized use

• Comply with applicable privacy, marketing, intellectual-property, consumer-protection, accessibility, export, and data-security laws.
• Obtain client authorization before connecting, publishing to, modifying, importing from, or communicating through a client account or website.
• Honor third-party terms, API rules, quotas, branding requirements, and content policies.
• Use accurate business, sender, account, and contact information.

3. Security and access

• No unauthorized access, credential sharing, account takeover, phishing, malware, destructive code, or security bypasses.
• No vulnerability scanning, penetration testing, scraping of protected areas, or exploitation without written authorization.
• No evasion of authentication, licensing, domain limits, rate limits, audit logs, update protections, or encryption.
• No exposure of OAuth tokens, API secrets, payment credentials, encryption keys, license keys, or protected customer data.
• No access to another agency's or client's workspace except through authorized roles.

4. Content, claims, and rights

You are responsible for content created, imported, scheduled, published, transmitted, or displayed through CMSPost. Do not use CMSPost for content that infringes rights; is fraudulent, materially deceptive, defamatory, threatening, exploitative, or unlawfully discriminatory; impersonates others; contains malicious code; manipulates reviews or metrics unlawfully; or makes unsubstantiated guarantees.

5. Email, social media, and communications

• No spam, purchased-list abuse, deceptive headers, misleading subject lines, or evasion of unsubscribe requests.
• No automated messages without the consent or lawful basis required for the channel and jurisdiction.
• Commercial email must include accurate sender information and required opt-out mechanisms.
• Referral, affiliate, sponsored, or compensated recommendations must include clear disclosures where required.
• Social publishing must comply with connected platform policies.

6. Connected platforms and APIs

Connect only accounts and resources you are authorized to administer. Do not evade third-party review, access approval, rate limits, spending limits, quotas, account restrictions, or platform enforcement. Disconnect accounts promptly when authorization ends.

7. Automation, scraping, and resources

• Do not run imports, crawlers, uploads, or scheduled tasks at a volume that degrades CMSPost, your host, a client website, or a third party.
• Do not scrape private, authenticated, access-controlled, copyrighted, or personal data without authorization and a lawful basis.
• Do not intentionally create duplicate, doorway, spun, low-value, or misleading content at scale.
• Do not use CMSPost for file distribution, cryptocurrency mining, proxies, attacks, surveillance, or unrelated bulk computing.
• Respect robots directives, rate limits, crawl delays, API quotas, and server limits where applicable.

8. Additional prohibited conduct

• Reselling, sublicensing, distributing, cloning, or transferring CMSPost except through an authorized program.
• Removing ownership notices or presenting CMSPost source code as your own.
• Using CMSPost for illegal goods or services, fraud, identity theft, exploitation, harassment, malware, unauthorized surveillance, or harmful activity.
• Interfering with another customer, partner, client, user, or provider.
• Submitting false support, refund, chargeback, referral, commission, identity, or account information.
• Using duplicate accounts to evade package or trial limits.

9. Reporting concerns

Report vulnerabilities, suspected abuse, intellectual-property concerns, unlawful content, or compromised credentials promptly through the contact or support channel on cmspost.com. Do not publicly disclose a vulnerability before a reasonable opportunity to investigate and address it.

10. Enforcement

CMSPost may investigate and may limit, suspend, or terminate accounts, licenses, integrations, updates, publishing access, or partner participation. CMSPost may preserve relevant records, notify affected customers or providers, require corrective action, or cooperate with lawful requests.