Rook← Back to home

Rook — Acceptable Use Policy

Effective date: 2026-06-07

This Acceptable Use Policy (the "AUP") governs your use of Rook, the multi-publish service operated by Obsidian Labs LLC ("Rook," "we," "us," or "our"). Rook lets you compose a post once and publish it to channels you control on Discord, X (Twitter), and Telegram through a tap-to-approve flow, and optionally lets your own systems submit drafts to your approval inbox through an HMAC-signed inbound webhook. Rook bills on a monthly subscription (Free, Pro, and Studio tiers) through Stripe; Rook is not a payment processor for you, takes no cut of your revenue, and is not in the money flow between you and your own subscribers or audience.

This AUP is incorporated by reference into, and forms part of, the Rook Terms of Service (the "Terms"). Capitalized terms not defined here have the meaning given in the Terms. A violation of this AUP is a material breach of the Terms. If there is a conflict between this AUP and the Terms, the Terms control except where this AUP is more specific about prohibited conduct.

By accessing or using Rook, you agree to this AUP. If you use Rook on behalf of an organization, you agree on its behalf and confirm you have authority to do so.

1. Your core responsibility for what you publish

Rook is a publishing tool. You — the account holder — are solely responsible for the content you compose, submit through the inbound webhook, approve, and publish, and for the consequences of publishing it. In particular, you are responsible for:

  • Rights to the content. You must have all rights, licenses, and permissions necessary to publish the content you publish through Rook, including any text, headline, structured attributes, image, or webhook payload.
  • Lawful control of the channels. You must lawfully own or control the Discord, X, and Telegram accounts, bots, and channels you connect to Rook, and you must be authorized to publish to them.
  • Your own legal, regulatory, and tax compliance. You are responsible for your own jurisdictional, regulatory, and tax compliance. Rook publishes to channels you control — not to your individual end subscribers — and Rook therefore structurally cannot and does not enforce per-jurisdiction or per-recipient visibility of what you publish. You must not rely on Rook to perform any such filtering.

Rook does not review, endorse, verify, or vouch for your content. Nothing about publishing through Rook constitutes Rook's approval of, or agreement with, what you publish.

2. Prohibited content and conduct

You may not use Rook to create, compose, submit, approve, store, publish, or distribute any of the following, and you may not use Rook to engage in any of the following conduct.

2.1 Illegal content and activity

You may not use Rook for any activity that is unlawful under any applicable local, state, national, or international law, or to create, post, transmit, or promote unlawful content. This expressly includes:

  • child sexual abuse or exploitation material (CSAM), or any content that sexualizes minors;
  • content that incites, threatens, facilitates, or glorifies violence or terrorism;
  • fraud, deceptive schemes, or other unlawful financial activity; and
  • any other content or activity prohibited by applicable law.

2.2 Intellectual property infringement

You may not use Rook to infringe the intellectual property rights of others, including copyright, trademark, patent, or trade secret rights, and you may not publish content you do not have the right to distribute. Because Rook stores and re-publishes the content you supply to third-party platforms, you are responsible for clearing all such rights before you publish.

DMCA. Rook responds to notices of alleged copyright infringement under the U.S. Digital Millennium Copyright Act and maintains a repeat-infringer policy under which we may terminate the accounts of users who repeatedly infringe. Notices of claimed infringement should be sent to our designated agent at legal@postrook.com (or as otherwise published in the Terms or on our site). We will respond to valid notices expeditiously and operate a counter-notification process consistent with the DMCA.

2.3 Spam and unsolicited messaging

You may not use Rook to send spam, chain messages, or unsolicited bulk or commercial messages that you do not have permission or consent to send, and you may not use Rook to harvest recipient data. Because Rook is the mechanism through which your messages are published, you must have lawful authority and any required consent to publish to every channel you connect.

Anti-spam law compliance. You are the sender (and, where applicable, the "initiator") of every message you publish through Rook, and you are responsible for complying with all anti-spam laws that apply to your messages, including:

  • CAN-SPAM Act (US) for commercial messages — no false or misleading header or routing information, no deceptive subject lines, identification of the message as an advertisement where applicable, inclusion of a valid physical postal address, a clear opt-out mechanism, and honoring opt-out requests promptly (within 10 business days); and
  • CASL (Canada), where messages are sent within, from, or to Canada — obtaining the required consent (CASL is opt-in) before sending commercial electronic messages, identifying the sender, and providing an unsubscribe mechanism.

You remain the responsible party for these obligations even though Rook performs the publishing on your instruction.

2.4 Malware and harmful code

You may not use Rook to upload, transmit, distribute, or link to viruses, worms, Trojans, spyware, ransomware, or any other malicious or harmful code, or to publish content or links designed to damage, disrupt, or gain unauthorized access to any system or data.

2.5 Harassment, abuse, and hateful conduct

You may not use Rook to stalk, track, monitor, harass, bully, intimidate, threaten, defame, or dox any person, or to publish content that promotes discrimination, hatred, or harm against people based on protected characteristics.

2.6 Impersonation, misrepresentation, and fraud

You may not use Rook to:

  • misrepresent your identity or impersonate any person or entity;
  • disguise or falsify the origin of content, or engage in phishing;
  • misrepresent machine-generated content as human-authored or as something it is not; or
  • otherwise deceive or defraud any person.

2.7 No misrepresentation of Rook's role

Rook is a publishing tool, not an attestation, verification, or endorsement service, and Rook is not a financial adviser, broker, or investment service. You may not:

  • represent or imply that Rook reviews, endorses, verifies, certifies, or vouches for your content;
  • represent or imply that any post is "verified by Rook" or carries Rook's approval; or
  • represent or imply that Rook provides financial, investment, legal, tax, or other professional advice, or that Rook is responsible for the accuracy of what you publish.

The only attribution Rook adds is a plain "via Rook" footer shown on Free-tier posts (paid tiers publish without it). You may not alter, remove, or obscure that footer where it applies, and you may not add any Rook mark, branding, or attribution that we have not provided.

3. Respecting the destination platforms

When you publish through Rook, you are acting on the Discord, X, and Telegram accounts you connect, and your activity is subject to those platforms' own terms of service, developer policies, and community rules. You are responsible for reviewing and complying with those rules, and your use of each connected platform is governed by that platform's own terms and privacy policy. You may not use Rook to:

  • violate the terms of service, developer policies, community rules, or other usage rules of Discord, X, Telegram, or any other third-party platform you connect or publish to;
  • use Rook with the primary purpose of circumventing any restriction, usage limit, or rate limit imposed by a third-party platform;
  • bypass any platform's security measures or usage limitations; or
  • take action on a connected account that you have not been authorized by that platform and the account owner to take.

Rook's tap-to-approve flow is the step at which you give your express, informed consent to publish a specific post to your connected platforms; you must not attempt to publish on any account without completing that authorization. Merely connecting or authenticating an account does not by itself authorize Rook to publish — each publish action requires your separate approval. Conduct that puts Rook's own standing or API access with a destination platform at risk is a serious violation of this AUP.

4. Protecting Rook's systems and limits

You may not:

  • probe, scan, or test the vulnerability of any Rook system or network, or breach or attempt to breach any authentication or security measure;
  • interfere with or disrupt the integrity or performance of Rook, or the use of Rook by any other user;
  • overwhelm or attempt to overwhelm Rook's infrastructure, including through excessive automated requests, denial-of-service activity, or abnormal storage or compute consumption;
  • circumvent, or attempt to circumvent, any usage limit, rate limit, plan cap (including install counts, monthly post limits, and per-day publishing limits), or other security or technical limitation we apply, whether through automation, creating multiple accounts, or any other means;
  • create multiple accounts to evade a limitation imposed by Rook or by a third-party platform; or
  • reverse engineer, decompile, scrape, resell, or sublicense the service except to the extent permitted by the Terms or applicable law.

Rook applies and enforces usage limits, rate limits, and plan caps — including per-IP and per-install limits on the inbound webhook — and reserves the right to set, adjust, and enforce such limits.

5. Security of your connected accounts and secrets

You are responsible for safeguarding your Rook account credentials and the connected-account credentials, OAuth tokens, and webhook signing secrets associated with your account, and for all activity that occurs under your account. Rook stores connected-channel OAuth tokens and webhook signing secrets encrypted at rest. You must promptly notify us at support@postrook.com of any suspected unauthorized access to or use of your account or connected channels. You may disconnect a connected platform or revoke access at any time, both within Rook and directly at the third-party platform; on disconnection or account deletion, the associated tokens and secrets are deleted.

6. Enforcement

We may take any of the following actions, with or without prior notice, if we reasonably determine that you have violated this AUP or the Terms, or that action is necessary to protect Rook, our users, a third-party platform, or any other person:

  • remove, disable access to, or decline to publish violating content;
  • throttle, restrict, suspend, or terminate your access to Rook or any feature, including connected channels and the inbound webhook;
  • suspend or terminate your account; and
  • report unlawful activity to law enforcement or other authorities, and cooperate with lawful requests.

For serious violations — including illegal content or activity, security threats, or conduct that harms other users, a destination platform, or Rook's systems or standing — we may suspend or terminate immediately and without prior notice. For violations that appear inadvertent and that do not pose an immediate risk, we will generally aim to give you notice and an opportunity to cure before suspending or terminating, but we are not obligated to do so. Our decision not to enforce any provision of this AUP in a given instance is not a waiver of our right to enforce it later.

You remain responsible for the content you have composed, submitted, approved, or published through Rook, including after any suspension, termination, or removal, and including content already delivered to a destination platform. Publishing through Rook is not reversible by Rook once a post has been delivered to a destination platform; removing or editing a published post is an action you must take yourself, on the destination platform or through Rook where supported. Suspension or termination does not relieve you of obligations or liabilities accrued before it took effect.

7. Reporting violations and contact

To report a suspected violation of this AUP, to send a copyright notice, or to ask a question about this policy, contact us at:

8. Changes to this policy

We may update this AUP from time to time. If we make a material change, we will provide notice (for example, by email or in-app) and state the new effective date; changes apply on a forward-looking basis from that date. Your continued use of Rook after a change takes effect, following conspicuous notice, constitutes your acceptance of the updated AUP. This AUP remains governed by, and incorporated into, the Terms, including their governing-law and venue provisions (Nevada).