Terms of Service
These terms cover two things: AIffiliate, the Meta Threads app you register and authorize, and Affiliate Threads, the plugin in this repository that publishes through it. The plugin is self-hosted. You run it on a machine you control, with accounts you own, and by installing it or using the app you agree to these terms.
Last updated
The short version
- The code is open source under the MIT License, and it comes as is, with no warranty.
- You run it yourself, with accounts you own. The maintainers operate no service and hold no data for you.
- Every post is approved by a human before it is published. What you approve, and how it fits Meta's rules and the law where you live, is your responsibility.
- Nothing in these terms adds to or takes away from what the MIT License grants you in the code.
1.What these terms cover
These terms describe the deal between you and the maintainers of this repository when you use the project's software and the AIffiliate app. They sit next to the MIT License that covers the code; where the two meet, the licence governs what you may do with the code itself.
Affiliate Threads is self-hosted. The maintainers operate no service for it, so there is no account to create and nothing running on their side to suspend.
These terms do not replace the terms of Hermes Agent, Meta Threads, Google Sheets, Telegram, or the AI provider you configure. Each of those governs its own part.
2.Who may use it
You install the plugin on a machine you control and connect accounts you own. Meta's own terms set the age required to hold a Threads account; this plugin is a publishing tool for the person operating it.
Keep that machine and those accounts secure. Anyone with access to your machine or your credentials can publish to your Threads profile.
3.Licence
The plugin and this site are open source under the MIT License. That licence permits use, copying, modification, and redistribution, including commercially, provided the licence text and copyright notice stay with copies of the code.
Forks are welcome. If you modify the code, the modified behaviour is yours: the maintainers cannot vouch for a build they did not write. A fork should not present itself as this project, or imply that the maintainers endorse it.
4.Your accounts and credentials
You bring your own: a Meta app with the Threads use case, a long-lived Threads access token, authorization for Google Sheets, and a Telegram bot you control.
Keep the credentials private. No maintainer needs them, and anyone who asks you to send your Threads token is not acting for this project.
You can revoke access at any moment. Section 7 of the privacy policy describes how.
5.What you are responsible for
The software is built so that publishing waits for a human decision. From there, the responsibilities are yours:
- Every post is approved by you before it goes out, and what you approve is your content, published from your account.
- Verify before you publish. The AI drafts and researches, but research can be wrong, and a claim about a product becomes yours once you approve it.
- Follow Meta's rules — the Meta Platform Terms and the terms that come with the Threads product — along with the terms of the other services you connect.
- Follow the law that applies to you. Affiliate content can carry advertising-disclosure or endorsement requirements where you live, and the plugin deliberately does not decide that for you.
- Keep the products and links in your sheet legitimate: your affiliate relationships, your URLs, and the claims you bring.
6.Acceptable use
Use the software for its purpose: drafting and publishing affiliate content you are willing to stand behind. In practice, that rules out:
- Spam, bulk unsolicited posting, and attempts to game Threads engagement or reach.
- Content Meta's terms prohibit, or publishing in a way those terms prohibit.
- Invented first-hand claims. The pipeline refuses experience claims your own stored testimony does not support; if you modify the code, do not use that freedom to publish claims you cannot back.
- Publishing without the approval step. The pipeline is built so a human decides what goes out; if you remove that, the decisions become yours alone.
7.Third-party services
The plugin works through services the maintainers do not control: Meta Threads (terms), Google Sheets (terms), Telegram (terms), your AI provider, and whatever research or image tools you connected in Hermes. Each governs your use on its own terms, and each has its own privacy policy.
The maintainers cannot grant you rights in those services or promise they stay available. What each service does with your use is between you and that service.
8.No warranty
The software is provided "as is", without warranty of any kind, as the MIT License says in full. In plain terms: drafts can be wrong, research can miss what matters, a publish can fail, and nothing here promises reach, clicks, sales, or income. You keep the approval step — it is what decides what actually goes out.
9.Limitation of liability
To the fullest extent the law allows, the maintainers are not liable for damages arising from this software or the app, including failed or lost posts, lost sales or income, actions Meta takes on your account, or lost data. This matches the limitation in the MIT License, which applies in full.
10.Changes to these terms
These terms live in the repository next to the code they describe. When they change, the date at the top changes with them, and the repository's history shows what changed. Continuing to use the project after a change means the new version applies.
11.Ending these terms
You can stop at any time: uninstall the plugin, revoke the app's access in Threads, and delete the local records. Section 7 of the privacy policy has the exact steps.
The MIT License is not revocable, so it continues to cover copies already made. Nothing obliges you to keep using the software, and the maintainers may stop maintaining it at any point.
12.Contact
Questions about these terms: open an issue at github.com/msyamsularif/affiliate-threads-generator/issues.