1. Using PostPlugin.org
By using PostPlugin.org, you agree to these Terms of Service, the Privacy Policy, and the Refund Policy. If you use the service for an organization, you confirm that you have authority to accept these terms for it. If you do not agree, do not use the service.
2. Accounts and security
- Provide accurate account information and keep your password, session cookie, and connected sign-in method secure.
- You are responsible for activity performed through your account, except where that responsibility cannot legally be assigned to you.
- Do not impersonate another person or try to access another account, chat, attachment, generated project, JAR, source ZIP, billing record, or refund ticket.
- We may suspend or restrict access when reasonably necessary to protect users, PostPlugin.org, its providers, or third parties.
3. Requests, attachments, and content rights
You may submit Minecraft plugin specifications, follow-up messages, images, and supported text files. You must have the rights and permissions needed to submit that material. Do not upload malware, credentials, private keys, unlawful content, or material that infringes another person’s rights.
You retain rights you already have in submitted material. You give PostPlugin.org and the providers needed to operate it a limited permission to host, copy, analyze, transform, build, validate, and return that material only as needed to provide, secure, support, and improve the requested service.
To the extent permitted by law, you may use generated project output for your own purposes. We do not promise that generated output is unique or free of third-party rights. You are responsible for any third-party code, assets, names, APIs, dependencies, or licenses included in a request or result.
4. Generated plugin files and testing
PostPlugin.org can produce answers, Java source, resource files, plugin.yml, compiled JAR files, source ZIP files, build progress, and validation results. Generated output can contain mistakes, omissions, unsafe behavior, licensing issues, or compatibility problems that automated checks do not detect.
The current validated build target is Paper 1.21.4 with Java 21. Compatibility with another Minecraft version, Paper build, Bukkit or Spigot environment, proxy, Fabric or Forge mod loader, server fork, third-party plugin, database, or external API is not promised unless PostPlugin.org expressly provides and validates that target.
Review the source and configuration, inspect permissions and commands, keep backups, and test each revision on a separate server before production use. You are responsible for deployment, server security, player data, licensing, dependencies, and the consequences of running a generated plugin.
5. Acceptable use
You may not use PostPlugin.org to violate law or another person’s rights; create, conceal, or distribute malware or deceptive software; steal credentials or player data; evade server or service restrictions; disrupt systems; probe or bypass security controls; overload the service; manipulate credits or billing; or request another user’s private chat, attachment, project, internal instruction, or credential.
Do not use generated plugins for unauthorized surveillance, harassment, fraud, destructive server access, or circumvention of third-party rules. We may reject unsafe files or requests and remove content or access when reasonably necessary.
6. Plans and output credits
Only reported generated output is charged as PostPlugin.org credits. Prompt text, supported input files, cached input, and reasoning metrics are not charged as output credits. The account screen shows the balance and recorded output-credit usage available to the service.
Monthly plan credits reset by UTC calendar month, which may not be the same date as a Stripe subscription renewal. Signup or promotional credits can have separate rules. Deleting a chat, attachment, project, or failed request does not automatically restore credits already used.
A model answer or generated source can consume output credits before a later compilation or package-validation step fails. In that situation, reported output credits may still be recorded. A one-credit temporary hold can be placed while a request is accepted and released or reconciled when processing finishes.
The plan, allowance, price, tax, billing frequency, and purchase terms shown at checkout control a completed order. A display-only or planned feature is not a completed purchase, and a plan label does not promise a particular plugin count, queue position, response time, support time, file limit, or project outcome unless the checkout terms expressly say so.
7. Subscription payments and cancellation
Stripe processes paid subscriptions on Stripe-hosted pages. PostPlugin.org does not store full payment-card details. The price, applicable taxes, billing frequency, and renewal terms shown at checkout apply to the purchase. A subscription renews until it is cancelled or otherwise ended under those terms.
The linked Stripe billing portal can be used to review eligible billing details, update eligible payment information, and cancel future renewals. Cancellation normally affects a future renewal; it does not itself reverse a prior payment or create a refund ticket.
8. Refund requests
Refund requests must be submitted from the Contact section of the signed-in account. The form creates an in-app support ticket for manual review. It does not automatically approve a refund, move money, cancel a subscription, or instruct Stripe to reverse a payment.
Recorded output-credit use can be considered during review. We generally do not offer a full refund when 100 or more output credits are verified for the relevant paid period. The ticket system does not automatically prove or apply that threshold, and using fewer than 100 output credits does not guarantee a full or partial refund.
Ticket statuses describe the support workflow, not a Stripe transaction. A Closed ticket does not by itself mean that a refund was approved, issued, or settled. Nothing in these terms limits a consumer right that applicable law does not allow us to limit. The detailed process is in the Refund Policy.
9. Third-party services and non-affiliation
Authentication, hosting, infrastructure, generation, building, and payments may rely on third-party services with separate terms and privacy practices. Their availability and independent processing are outside our control. You are responsible for third-party services and software that you choose to connect to a generated project.
PostPlugin.org is an independent service and is not affiliated with, endorsed by, or sponsored by Mojang Studios or Microsoft. Minecraft and related names and assets belong to their respective owners.
10. Availability and service changes
We work to keep PostPlugin.org available, but accounts, generation, build tools, downloads, billing features, and provider integrations may be interrupted for maintenance, capacity, security, legal, or technical reasons. We may change, pause, or discontinue a feature and may update limits or compatibility targets prospectively.
11. Disclaimers and liability
To the fullest extent permitted by law, PostPlugin.org is provided on an “as available” basis without a promise that every answer or generated result will be accurate, secure, compatible, uninterrupted, or fit for a particular purpose. Nothing in these terms excludes a warranty or liability that applicable law does not allow us to exclude.
To the fullest extent permitted by law, we are not responsible for indirect, incidental, special, consequential, or exemplary losses arising from use of the service, or for server damage, data loss, downtime, player impact, third-party conflicts, or decisions made from generated output. Where liability cannot be excluded, any limitation applies only to the extent allowed by applicable law.
12. Ending use
You may stop using the service at any time. We may suspend or end access when these terms are violated, when required by law, when a provider relationship ends, or when needed to protect the service. Sections that should reasonably continue—including content rights, acceptable use, billing, disputes, disclaimers, and liability—continue after access ends.
13. Changes to these terms
We may update these terms as PostPlugin.org changes. The updated date appears at the top. Where appropriate, we will provide additional notice before a material change applies to future use or purchases. A completed purchase remains subject to mandatory rights and the purchase terms that legally control it.
14. Contact and related policies
Questions about these terms can be sent to eftasmare@gmail.com. Review the Privacy Policy, Refund Policy, and Policy Center for related information.