Terms of Service

1. The agreement

These Terms of Service (the "Terms") are a binding agreement between:

GPT LLM ORAGLE Ltd. Liability Co.
A Wyoming close limited liability company (filing ID 2026-001932735)
Registered office: 30 N Gould St, Ste N, Sheridan, WY 82801, United States

referred to as "we", "us", "our", or "the Company", and the person or organisation that creates an account or is issued a workspace, referred to as "you" or "Customer".

By creating an account, clicking to accept, or using the Service, you accept these Terms. If you accept on behalf of an organisation, you confirm you are authorised to bind it, and "you" means that organisation.

The following documents are incorporated by reference and form part of these Terms:

• Privacy Policy
• Acceptable Use Policy
• Data Processing Addendum (applies where we process personal data on your behalf)
• Data Deletion Policy
• Cookie and Local Storage Policy
• Subprocessors
• The order form, plan page, or written quotation that sets out your commercial terms.

2. Definitions

• Service - the GPTpost platform made available at oraglegpt.org and, for the application itself and its API, at app.oraglegpt.org, including its web application, APIs, webhooks, MCP interface, mobile client, and documentation.
• Workspace / Tenant - the isolated environment in which your data lives.
• User - an individual you authorise to access your Workspace.
• Customer Content - everything you or your Users put into, or pull into, the Workspace: drafts, media, campaigns, schedules, contacts, inbox messages, analytics, AI prompts and outputs, and configuration.
• Connected Account - a social or publishing account you authorise the Service to act on.
• Platform - a third-party social network or publishing destination (Facebook, Instagram, Threads, LinkedIn, TikTok, YouTube, X, Pinterest, Reddit, Mastodon, Google Business Profile, Bluesky, Discord, Telegram, Tumblr, VK, Odnoklassniki, WordPress, and others we add).
• Platform Data - data we obtain from a Platform under your authorisation.

3. Eligibility and accounts

1. You must be at least 18 and legally able to enter contracts. The Service is for business use.
2. You must give accurate registration information and keep it current.
3. You are responsible for your Users' acts and omissions as if they were your own.
4. You must protect your credentials. Enable multi-factor authentication. Tell us immediately at security@oraglegpt.org if you suspect compromise.
5. Workspace administrators can add, remove, and change the permissions of Users and can access all Customer Content in the Workspace. If you are a User added by an organisation, that organisation controls your Workspace access and your Customer Content.

4. Plans, fees, and payment

1. Plan, price, currency, billing period, included usage, and overage rates are set out on the plan page in the Service or in the order form that applies to you. Where an order form and the plan page conflict, the order form governs.
2. Fees are payable in advance. Cancellation, refunds, and pro-rata treatment are governed by our Refund and Cancellation Policy at Refund and Cancellation Policy, which forms part of these Terms. Nothing in these Terms removes a statutory right of withdrawal or refund that applies to you under mandatory local law.
3. Fees exclude taxes. You are responsible for sales tax, VAT, GST, and equivalent charges, other than taxes on our net income.
4. We may meter usage (seats, connected accounts, publications, AI tokens and cost, storage) and bill overage at the published rates. AI usage is metered in tokens and cost micros against the monthly budget you configure.
5. Late payment: we may suspend the Service after 14 days' written notice of non-payment. We will not delete Customer Content during a suspension for non-payment without giving you the export window in section 17.
6. Price changes take effect at your next renewal, with at least 30 days' notice.
7. Payment processing is performed by a PCI-DSS compliant third-party processor, or by invoice and bank transfer. We do not store card numbers, expiry dates, or security codes. Any payment processor we engage is listed on our Subprocessors page at Subprocessors.

5. Trials, beta features, and fixture mode

1. Free trials and free plans are provided as-is, may be changed or withdrawn, and carry no service commitment.
2. Features labelled beta, preview, or experimental may change or be removed, are excluded from any service level commitment, and should not be relied on for production workloads.
3. The Service includes a fixture mode used for demonstration and local development. Fixture results are simulated and are not live delivery to a Platform. You must not present fixture output to a client, a regulator, or a Platform reviewer as evidence of live publishing.

6. Your content and the licence you grant us

1. You own your Customer Content. We claim no ownership.
2. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, encode, transcode, display, and transmit Customer Content to the Platforms and destinations you select, solely to operate and support the Service and only for as long as needed to do so. The licence ends when the content is deleted, except for backups pending rotation.
3. You represent that you have all rights, licences, releases, and consents needed for the Customer Content, including rights in music, stock media, fonts, likenesses, trademarks, and user-generated content you re-publish, and including any consent needed to message the recipients of outbound DMs.
4. We may access Customer Content only to operate the Service, to provide support you request, to enforce these Terms, or where legally compelled. Access is logged in the tenant audit trail.

7. Connected Accounts and Platform terms

This section matters. Read it.

1. Your authority. You represent that you are authorised to connect each Connected Account and to act on it, including where the account belongs to a client of yours. You must have a written mandate from any client whose account you connect.
2. Platform terms flow down. Your use of each Platform through the Service is also governed by that Platform's own terms, developer policies, community standards, automation rules, and messaging policies. You must comply with them. Breach of a Platform's terms is a breach of these Terms.
3. We are not the Platform. We do not control Platform availability, APIs, rate limits, review outcomes, content moderation, account suspensions, or metric definitions. Platforms change and deprecate APIs without notice.
4. No guarantee of delivery. Scheduling a post is a request. Delivery depends on Platform availability, token validity, scope grants, rate limits, content review, and account standing. We surface the attempt outcome, including failures. We are not liable for a post that a Platform rejects, delays, throttles, down-ranks, or removes.
5. App review and credentials. Live publishing requires the operator of the Service to hold approved Platform applications and credentials. Where a Platform application is not approved, the affected capability is unavailable or restricted, and the Service will say so rather than simulate success. The current status is published at site/platform-limitations and in our social platform capability matrix.
6. Revocation. You or the account holder may revoke access at any time from the Platform or from integrations/accounts. Revocation destroys stored credentials; it does not by itself erase stored content or account metadata. Disconnecting in the Service overwrites and deletes every stored token for that Connected Account, and, if you choose Delete account record, the local account record too; separately stored content, history and other Platform Data is not swept up in that action. Revoking only at the Platform is not an authenticated instruction to us to erase anything, and may reach us only as a later token failure. For a deterministic result, use the self-serve controls or the verified request route. Data Deletion Policy section 4 states the exact effect of each signal, and section 3 the routes.
7. Platform-directed deletion. Where a Platform sends a deletion or deauthorisation callback that we can verify, we act on it, even if that removes content or history from your Workspace. A verified deletion callback queues erasure of the Platform Data we hold for that platform user; a verified deauthorisation callback destroys the affected stored credentials and marks the connection revoked, but is not by itself a full deletion request. Only Meta's signed-request callbacks, for Facebook, Instagram and Threads, are implemented in this release; Data Deletion Policy sections 5.1 and 5.3 say which routes answer and which do not.

7.1 YouTube

YouTube cannot be connected in this release. The connector has no authoritative account-identity resolver, so the authorisation flow refuses to start and no YouTube channel can be linked to a Workspace. This clause therefore binds nobody today, and is stated in advance so that it is in force the moment the connector is enabled.

If and when you connect a YouTube channel, GPTpost uses YouTube API Services, and the connector is upload-only: it uploads one video or Short with the title, description, tags and privacy status you supply. It makes no comment call and no analytics call to YouTube. By using those features you agree to be bound by the YouTube Terms of Service at https://www.youtube.com/t/terms. Google's handling of your information is governed by the Google Privacy Policy at http://www.google.com/policies/privacy. You may revoke our access to your YouTube data at any time at https://myaccount.google.com/permissions.

7.2 Other Platform terms incorporated

By connecting an account you also agree to be bound by that Platform's terms.

Most of the Platforms named below cannot be connected in this release, for the same reason as YouTube in section 7.1: the connector has no authoritative account-identity resolver, or a policy block stands in the way, so the authorisation flow refuses to start. Where that is the case the row binds nobody today, and is stated in advance so that it is in force the moment the connector is enabled. The live answer for any Platform is GET /api/v1/capabilities, which reports oauth_connectable and, when it is false, the reason.

Where a Platform's terms conflict with these Terms in respect of that Platform's data, the Platform's terms govern that data.

8. AI features

1. AI features run only against an AI provider you configure in your Workspace, subject to the tenant policy you set (allowed providers, allowed models, allowed tools, output limits, monthly budget, data region, and whether autonomous public actions are permitted).
2. You own AI outputs you generate, to the extent they are ownable, and you are responsible for reviewing them before publication. AI output can be wrong, biased, infringing, or non-compliant.
3. We do not warrant that AI output is accurate, original, non-infringing, or fit for any purpose. Outputs may be similar to outputs generated for others.
4. Your prompts and content are transmitted to the AI provider you configure. That provider's terms, including any terms about training on submitted data, govern what it does with them. Review them before enabling a provider.
5. You must not use AI features to generate content that violates Acceptable Use Policy, including impersonation, synthetic media presented as real, or content that a Platform prohibits.
6. Where a Platform requires disclosure of AI-generated or synthetic content, you must make that disclosure.
7. Autonomous publishing without human approval is off unless you explicitly enable it. If you enable it, you accept responsibility for what is published.

9. Acceptable use

You must comply with Acceptable Use Policy. We may remove content, disable a Connected Account, throttle, suspend, or terminate where we reasonably believe there is a violation, a security risk, a legal risk, or a Platform-relationship risk. Where practical we give notice and an opportunity to cure; where the risk is urgent we act first and notify promptly.

10. Service levels, support, and the operating boundary

1. Support is provided by email at support@oraglegpt.org. Our published support channels, hours, and target first-response times are set out at Support. Unless a written service level agreement is signed in an order form, the Service is provided without a contractual availability commitment, and the targets on the support page are goals rather than guarantees.
2. We may perform maintenance. We give advance notice for planned maintenance where practical.
3. Documented operating boundary. Tenant data is held in an encrypted PostgreSQL database, which is authoritative for the Service. Tenant-owned tables are protected by PostgreSQL FORCE ROW LEVEL SECURITY in addition to application authorization, background work runs on a durable database-backed job queue, external event delivery uses a transactional outbox, and the audit log is hash-chained. Backups are encrypted, taken daily, and each one is restored into a clean environment and checked against production before it is retained; write-ahead log archiving is enabled. The boundary that remains, disclosed rather than hidden: the Service runs a single primary database with no high-availability cluster and no automatic failover, and while write-ahead log archiving is in place, recovery to an arbitrary point in time has not yet been rehearsed end to end. We therefore do not offer a recovery-point or recovery-time objective, and the availability and recovery commitments above are stated accordingly.

11. Your obligations on data protection

1. Where we process personal data on your behalf, Data Processing Addendum applies and you are the controller.
2. You are responsible for having a lawful basis for ingesting comments, DMs, and contact records into your Workspace, for any outbound messaging you send, for your own privacy notices, and for honouring the rights of the individuals whose data you process.
3. You must not upload special category data, health data, payment card data, government identifiers, or data subject to sector-specific regimes (for example HIPAA, PCI-DSS, FERPA, or GLBA) unless separately agreed in writing.

12. Intellectual property

1. We and our licensors own the Service, its software, interfaces, documentation, and trademarks. Nothing here transfers those rights.
2. Subject to these Terms and payment of fees, we grant you a non-exclusive, non-transferable, non-sublicensable right to use the Service during the term.
3. You must not copy, modify, translate, reverse engineer, decompile, create derivative works from, resell, or provide the Service to a third party as a service, except where a reseller or OEM agreement expressly permits it, or where reverse engineering is permitted by mandatory law.
4. You must not remove proprietary notices, benchmark and publish results without consent, or use the Service to build a competing product.
5. Feedback. If you send us suggestions, we may use them without restriction or obligation.
6. Third-party components. Open-source components are licensed under their own terms; see docs/SBOM.spdx.json.

13. Confidentiality

Each party will protect the other's non-public information with at least reasonable care, use it only for the agreement, and disclose it only to personnel and advisers who need it and are bound to confidentiality. The obligation does not apply to information that is public through no fault of the recipient, independently developed, or lawfully received from a third party. A party compelled to disclose will give notice where legally permitted.

14. Warranties and disclaimers

1. Each party warrants it has authority to enter this agreement.
2. We warrant that we will provide the Service with reasonable skill and care.
3. Otherwise, the Service is provided "AS IS" and "AS AVAILABLE". To the maximum extent permitted by law we disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose, title, non-infringement, and any warranty arising from course of dealing or usage of trade.
4. We do not warrant that the Service will be uninterrupted or error free, that any post will be delivered, that any Platform will remain available or keep its current API, that analytics figures will match a Platform's own reporting, or that AI output will be accurate.
5. Some jurisdictions do not allow certain exclusions; those exclusions apply only to the extent permitted.

15. Limitation of liability

1. Neither party is liable for indirect, incidental, special, consequential, or exemplary damages, or for lost profits, lost revenue, lost goodwill, lost data, or business interruption, even if advised of the possibility.
2. Each party's total aggregate liability arising out of or relating to this agreement is limited to the greater of (a) the fees you paid or owed for the Service in the 12 months before the event giving rise to the claim, and (b) USD 100.
3. The limits do not apply to your payment obligations, to either party's indemnity obligations, to breach of confidentiality, or to liability that cannot be limited by law (including fraud, fraudulent misrepresentation, and death or personal injury caused by negligence).
4. Claims must be brought within one year of the date the claim arose, unless mandatory law provides otherwise.

16. Indemnities

1. You indemnify us against third-party claims, and resulting losses, arising from: your Customer Content; your use of a Connected Account without proper authority; your breach of a Platform's terms; your breach of Acceptable Use Policy; your outbound messaging; and your violation of law or third-party rights.
2. We indemnify you against third-party claims that the Service, as provided by us and used in accordance with these Terms, infringes a third party's intellectual property rights. This does not apply to claims arising from Customer Content, from combination with anything not supplied by us, from modification, or from continued use after we provide a non-infringing alternative.
3. The indemnified party must give prompt notice, allow the indemnifying party to control the defence, and cooperate reasonably.

17. Term, suspension, and termination

1. The agreement runs for the subscription term and renews automatically for equal periods unless either party gives notice at least 30 days before the end of the current term. You can cancel at any time from the billing screen in the Service; cancellation takes effect at the end of the paid period unless our Refund and Cancellation Policy says otherwise.
2. Either party may terminate for material breach that is not cured within 30 days of written notice, or immediately on the other's insolvency.
3. We may suspend immediately where there is a security threat, a legal requirement, a Platform demand, or a serious acceptable-use violation.
4. On termination: your access ends; you may export Customer Content for 30 days; after that we delete it in accordance with Data Deletion Policy. Accrued fees remain payable.
5. Sections that by nature should survive do survive, including sections 6.1, 12, 13, 14, 15, 16, 17.4, 18, and 19.

18. Compliance, export control, and sanctions

You represent that you are not located in, organised under the laws of, or ordinarily resident in a country or territory subject to comprehensive US sanctions, and that you are not on a US, UK, EU, or UN restricted-party list. You must not use the Service in breach of export control or sanctions law, or on behalf of a restricted party. We may screen you and terminate immediately if a screening hit is confirmed.

19. Governing law and disputes

1. These Terms are governed by the laws of the State of Wyoming, United States, without regard to conflict of law rules. The UN Convention on Contracts for the International Sale of Goods does not apply.
2. The courts located in Wyoming have exclusive jurisdiction, and each party consents to that venue.
3. We do not impose binding arbitration and we do not impose a class-action waiver. Disputes are resolved in the courts identified above, or by agreement between the parties. Before filing, each party will try in good faith for 30 days to resolve the dispute by writing to legal@oraglegpt.org.
4. Nothing here removes a consumer's mandatory local-law protections where they apply.
5. Either party may seek injunctive relief in any competent court to protect its intellectual property or confidential information.

20. General

1. Changes. We may update these Terms. Material changes take effect at your next renewal, or 30 days after notice for month-to-month plans. Continued use after the effective date is acceptance. If you do not accept, stop using the Service and, where applicable, request a pro-rata refund of prepaid unused fees.
2. Notices. To you: by email to your workspace administrators, or in-product. To us: legal@oraglegpt.org, with a copy to the registered office in section 1.
3. Assignment. You may not assign without our written consent. We may assign to an affiliate or in connection with a merger or asset sale.
4. Subcontracting. We may use subprocessors, listed in Subprocessors, and remain responsible for their performance.
5. Force majeure. Neither party is liable for failure caused by events beyond its reasonable control, excluding payment obligations.
6. Severability. If a provision is unenforceable, the rest stands.
7. No waiver. Failure to enforce is not a waiver.
8. No third-party beneficiaries, except as expressly stated.
9. Independent contractors. Nothing creates a partnership, joint venture, agency, or employment relationship.
10. Entire agreement. These Terms and the incorporated documents are the entire agreement and supersede prior discussions. Your purchase order terms do not apply.
11. Order of precedence. A signed order form or master agreement, then Data Processing Addendum, then these Terms, then the other incorporated policies.
12. Publicity. We will not use your name or logo publicly without your prior written consent.

21. Contact

GPT LLM ORAGLE Ltd. Liability Co.
30 N Gould St, Ste N
Sheridan, WY 82801
United States

Legal:    legal@oraglegpt.org
Privacy:  privacy@oraglegpt.org
Security: security@oraglegpt.org
Support:  support@oraglegpt.org