Community Guidelines

GPTpost is a tool for publishing to other people's platforms. What you send through it lands in front of real audiences on Meta, TikTok, LinkedIn, Google, X, Pinterest, Reddit, Mastodon, and elsewhere, under our application credentials. That is why these guidelines exist and why we enforce them.

These guidelines sit alongside Acceptable Use Policy, which is the binding contractual rule set. Where the two overlap, the Acceptable Use Policy governs. This page is the plain-language version: what good use looks like, what gets you removed, and why.


1. The one rule underneath all the others

Publish as though the audience is a person, because it is.

Every other rule here follows from that. Automation is a convenience for you, not a licence to treat the people at the other end as a metric.


2. What good use of GPTpost looks like


3. Content that is never acceptable

This list is not exhaustive, and we apply it to content published through GPTpost as well as content stored in it.

Against people

Against children

Illegal and dangerous

Deception

Privacy

Adult and regulated content


4. Conduct that gets an account restricted

Content is only half of it. How you operate matters too.


5. Automation done responsibly

Automation is the point of the product. Doing it carelessly is what gets application credentials revoked, which harms every other customer.

Do

Do not


6. AI-assisted content

If you use the AI features:

  1. You are the author. Whatever the model wrote, you published it and you are responsible for it.
  2. Check it. Models get facts wrong confidently. Review before publishing, especially anything about health, money, law, or a named person.
  3. Do not use AI to impersonate a real individual, or to generate synthetic media of a real person without their clear consent.
  4. Follow platform disclosure rules. Several platforms now require AI-generated or AI-altered media to be labelled. That obligation is yours.
  5. Do not put other people's personal data into a prompt unless you have a lawful basis for doing so.
  6. Remember the AI provider is a subprocessor of your data, listed in Subprocessors.

7. Client and agency work

If you manage accounts for clients:


8. How we enforce

We act proportionately, and we prefer the smallest effective action.

StepAction
1Warning, with a specific description of what breached the rules
2Removal or quarantine of the specific content
3Disabling a connected account or a single capability
4Throttling publishing or API access
5Suspending a user, a workspace, or the account
6Termination
7Preserving evidence and reporting to a platform, a regulator, or law enforcement where the law requires it or the conduct is serious

We skip straight to the strongest action for child sexual abuse material, credible threats of violence, and active fraud or malware campaigns.

Platform-directed action. If a platform instructs us to remove content, disable a connection, or delete data, we comply, even if that removes content from your workspace. We have no discretion to refuse and we will tell you it happened.


9. Appeals

Enforcement decisions can be wrong. If you think yours was:

  1. Email legal@oraglegpt.org within 30 days, quoting the reference in the enforcement notice.
  2. Someone not involved in the original decision reviews it.
  3. We aim to respond within 10 business days.
  4. If we uphold the decision, we tell you which rule was breached and what, if anything, would let us restore access.

10. Reporting a problem

What you are reportingWhere
Abuse, spam, or a breach of these guidelineslegal@oraglegpt.org
Copyright or trade mark infringementlegal@oraglegpt.org, following Copyright and DMCA Policy
A privacy violation or exposed personal dataprivacy@oraglegpt.org
A security vulnerabilitysecurity@oraglegpt.org
Child safetylegal@oraglegpt.org, marked urgent. We escalate immediately

Include links, screenshots, timestamps, and the accounts involved. We acknowledge reports and act on them, though we cannot always tell you what action we took about someone else's account.


11. Changes

We update these guidelines as platform rules and abuse patterns change. Material changes are announced in-product and by email to workspace administrators. The date at the top always reflects the current version.


PageWhat it covers
Acceptable Use PolicyThe binding contractual rules
Terms of ServiceThe overall agreement
Copyright and DMCA PolicyNotice and takedown
Privacy PolicyWhat we do with personal data
GPT LLM ORAGLE Ltd. Liability Co.
30 N Gould St, Ste N
Sheridan, WY 82801
United States