Get2Post Terms of Service
Version: 1.0
Effective date: August 16, 2026
Get2Post, also referred to as G2P, is a service operated by 3CodeMonkeys, LLC.
These Terms of Service (the Terms) govern access to and use of Get2Post.
In these Terms, 3CodeMonkeys, we, us, and our mean
3CodeMonkeys, LLC, and Customer, you, and your mean the person or
organization using Get2Post.
1. Operator and contact information
3CodeMonkeys, LLC
1382 Thistle Lane
Shakopee, MN 55379, USA
Support, privacy, billing, security, abuse, and legal notices may be sent to support@get2post.com. This is the monitored public contact for the initial launch.
2. United States-only launch
Get2Post is initially offered and supported only in the United States. These Terms, the Privacy Policy, subscription and advertising practices, support, and acceptance process are prepared for that United States launch. We do not claim that Get2Post is available or suitable for use in other countries. International availability, localization, and additional jurisdiction-specific notices may be introduced only after separate implementation and validation.
3. Eligibility and authority
You must be at least 18 years old to create or use an account. If you accept these Terms or use Get2Post for an organization, you represent that you have authority to bind that organization. The organization is responsible for the accounts, workspaces, service identities, credentials, content, and activity it authorizes.
You must provide accurate account information, keep it current, protect account and recovery credentials, and promptly report suspected unauthorized access. You may not share a personal account in a way that defeats identity, authorization, audit, seat, or security controls. Organization owners and administrators control membership and role assignments within the permissions Get2Post provides.
4. The service
Get2Post is an API, workflow, automation, AI-assisted, bot, and Model Context Protocol (MCP) workspace service. Depending on the plan and enabled features, it may let authorized users and service identities:
- create, import, store, organize, test, and run API requests and collections;
- store workspace definitions, environments, variables, scripts, assertions, schemas, examples, and lifecycle versions;
- create and run workflows, scheduled Bot Runs, agents, automations, and other non-human executions;
- use AI-assisted drafting, revision, organization, or execution features;
- connect external tools through MCP, OAuth, webhooks, or other integrations;
- manage organization members, service identities, approvals, budgets, entitlements, and usage; and
- review results, logs, audit history, evidence, billing usage, and exports.
Features vary by plan, environment, configuration, and commercial state. A feature shown in documentation or a draft does not become available until it is implemented and enabled for the Customer. We may apply limits, approvals, budget controls, security checks, rate limits, or human authorization before an action is accepted or executed.
5. Customer Content and data ownership
Customer Content includes material submitted, stored, imported, generated, or directed by Customer through Get2Post, such as API definitions, endpoint URLs, request and response data, headers, query parameters, variables, cookies, scripts, tests, schemas, files, prompts, instructions, workflows, logs, and other workspace content. As between Customer and 3CodeMonkeys, Customer retains its ownership rights in Customer Content.
Customer grants 3CodeMonkeys a limited, non-exclusive right to host, copy, transmit, process, display, secure, back up, and otherwise use Customer Content only as reasonably necessary to provide, operate, support, troubleshoot, secure, and maintain Customer's Get2Post service; investigate customer-reported problems; comply with Customer's authorized instructions; enforce these Terms; and satisfy legal obligations. These Terms do not grant 3CodeMonkeys a general right to use Customer API payloads, prompts, workflows, requests, responses, credentials, or other Customer Content for unrestricted product improvement.
Get2Post may use aggregated or deidentified operational information and Usage Data to improve the service, provided that the information cannot reasonably identify Customer or its users or reveal or reconstruct Customer Content.
The limited right to process Customer Content ends when the content is deleted from active systems, except for information retained as permitted by these Terms or the Privacy Policy for legal, billing, tax, fraud-prevention, security, investigation, dispute, enforcement, audit, or backup purposes.
Customer represents that it has the rights and permissions needed for Customer Content and for each instruction it gives Get2Post. Customer is responsible for the legality, accuracy, and consequences of Customer Content and of the systems and people to which Customer sends it.
6. API payloads, credentials, and secrets
API requests may contain sensitive endpoint URLs, payloads, headers, authentication material, cookies, variables, scripts, and response data. Customer must minimize sensitive data, use designated secret mechanisms, assign least-privilege credentials, rotate exposed credentials, and avoid placing secrets in names, ordinary text fields, support messages, screenshots, or other surfaces not designed for secrets.
Get2Post may resolve and use an authorized credential to perform a requested execution without displaying the secret value back to users, tools, AI, MCP, general audit views, or support personnel. Redaction lowers risk but does not make an unsafe instruction safe. Customer remains responsible for the credentials, endpoints, and authority supplied to Get2Post.
7. AI, MCP, bots, automation, and diagnostics
AI features may send Customer-provided instructions and the minimum context needed for the selected operation to an enabled AI provider. AI output can be incomplete, inaccurate, insecure, or unsuitable. Customer must review and test output before relying on it, saving it as authoritative, or using it in a live system.
3CodeMonkeys does not use Customer Content to train or fine-tune general-purpose or shared AI models unless Customer separately and affirmatively opts in. Customer Content may be processed by an AI provider when Customer invokes an AI-powered Get2Post feature or when limited processing is reasonably necessary to provide support or investigate a specific customer problem. That processing remains subject to applicable provider terms, security controls, and data- protection requirements. AI-assisted diagnostic analysis is not permission to use Customer Content for model training. Any future Customer Content training program must require a separate affirmative opt-in and may not be introduced through a silent Terms or Privacy Policy update.
Get2Post may periodically use automated or AI-assisted diagnostic capabilities to identify software defects; investigate reliability, performance, security, accessibility, user-interface, or usability problems; debug customer-reported issues; and assist authorized personnel with support and incident investigations. These capabilities may be enabled or disabled depending on operational, testing, support, security, and investigation needs. They do not make final account-suspension, termination, billing, or other materially significant customer decisions without appropriate human review.
If limited Customer Content is reasonably necessary to investigate a specific customer issue, access must be restricted to authorized personnel and approved systems, limited to the minimum information reasonably necessary, used only for support, debugging, security, or investigation, recorded in appropriate audit evidence, and retained only for the applicable support or investigation period subject to the retention requirements in the Privacy Policy. Credentials, authorization headers, environment secrets, payment information, and other sensitive fields must be excluded or redacted by default where reasonably practicable.
MCP clients, service identities, bots, agents, scheduled runs, and automations can read or change workspace data or call external systems within their authorized scope. They may continue operating without a person actively viewing the application. Customer is responsible for:
- selecting the identity, workspace, permissions, approvals, schedule, limits, and credentials for each non-human execution;
- reviewing requested capabilities and delegated access;
- maintaining a human owner and recovery path for service identities;
- monitoring results, failures, spend, and security signals; and
- disabling access, schedules, or credentials when no longer needed.
Get2Post may deny an execution when trusted identity, tenant, authorization, approval, entitlement, commercial state, budget, or safety context is missing or inconsistent. Execution history and audit evidence may be retained to support security, billing, dispute, and compliance needs.
8. Third-party endpoints and integrations
Customer may direct Get2Post to interact with APIs, websites, identity providers, AI providers, MCP clients, webhooks, or other third-party services. Those services are not controlled by 3CodeMonkeys and may have their own terms, privacy notices, availability, limits, and charges. Customer is responsible for its relationship with each third party and for ensuring that Get2Post's access is authorized.
We do not guarantee third-party availability or results. We may suspend or disable an integration that creates security, legal, operational, billing, or abuse risk. Customer must not use Get2Post to bypass a third party's access, technical, payment, or acceptable-use controls.
9. Acceptable use and enforcement
This service is governed by the 3CodeMonkeys Universal Acceptable Use & Enforcement Policy. By using this service, you agree to comply with that Policy, which is incorporated into these Terms by reference.
Get2Post does not maintain a separate conflicting acceptable-use or enforcement policy. The following product-specific requirements are additive to the Universal Acceptable Use & Enforcement Policy:
- Do not use Get2Post for illegal activity or to facilitate unlawful conduct.
- Do not access or attempt to access another customer, organization, workspace, account, credential, or system without authorization.
- Do not evade authentication, authorization, approvals, tenant isolation, budget, metering, advertising, subscription, rate, or security controls.
- Do not introduce malware, disrupt the service, probe without authorization, destroy evidence, or interfere with other customers or providers.
- Do not infringe intellectual-property, privacy, publicity, confidentiality, contractual, or other rights.
- Do not generate fraudulent or artificial advertising impressions, clicks, or traffic, and do not ask others or automated systems to interact with ads.
Suspected unlawful activity, fraud, security harm, abuse, or risk of evidence destruction may result in immediate protective suspension while we investigate. Substantiated violations may result in permanent termination without refund, subject to applicable law. We may preserve evidence, cooperate with law enforcement, and disclose information when required or permitted by law.
We do not impose arbitrary punitive charges. Customer remains responsible for unpaid authorized fees, actual recoverable losses or costs, and remedies available under applicable law.
10. Plans, subscriptions, seats, and metered usage
Get2Post's launch model includes a Free with ads plan and paid plans. The paid catalog may include Pro, Team, Enterprise, and a custom Enterprise+ offering. The current Team plan has a five-seat minimum, and the current Enterprise plan has a twenty-five-seat minimum. Additional seats above a minimum may be billed at the applicable per-seat rate. The Account & Pricing page, checkout or order, and any written enterprise agreement state the price, billing interval, included usage, seat quantity, and plan features that apply at purchase.
Paid plans may renew monthly or yearly. Seat changes may change subscription quantity and may be prorated during a billing period as shown through the billing provider or order flow. A requested decrease may take effect only when permitted by the plan, existing member assignments, and the applicable billing period.
Paid plans may include allowances and optional metered overage for API request runs, workflow runs, bot, agent, or MCP executions, AI activities, and automation runs. The Get2Post billing ledger is the source of truth for whether usage occurred and for the quantity attributed to an organization. Current pricing and the Customer's authorized billing policy determine included allowances, overage rates, and budget behavior. Budget controls may stop work at an allowance or permit authorized overage only up to a configured cap.
11. Stripe billing
Stripe is Get2Post's initial payment and invoice provider for paid plans where billing is enabled. Get2Post may use Stripe to create or reuse a billing customer, create and update subscriptions, manage quantities, open a Stripe-hosted billing portal, submit authorized invoice items, finalize invoices, receive signed billing events, and reconcile provider state with the Get2Post billing ledger. Availability of a particular Stripe surface depends on it being configured and enabled.
Payment card and payment-method entry occurs on Stripe-hosted surfaces. Do not send card data to Get2Post or support. Stripe's terms and privacy notice also apply to its services.
Customer authorizes charges shown in the applicable checkout, order, billing portal, or Account & Pricing flow, including purchased subscriptions, seats, approved metered usage, and taxes that are legally required and displayed. Customer must keep an authorized payment method and billing information current.
12. Invoices, taxes, failed payments, cancellation, and refunds
Invoices and subscription state may be synchronized from Stripe. The Get2Post usage ledger remains authoritative for usage quantity, while Stripe is the payment and invoice provider. If the two differ, we may pause submission, investigate, correct a provider item, issue an authorized adjustment or credit, or ask Customer to contact support. Retries must not create a duplicate customer, usage submission, invoice item, invoice, or charge.
Customer is responsible for applicable taxes identified on an order or invoice, except taxes imposed on 3CodeMonkeys' income. Get2Post does not promise tax calculation or collection where that capability has not been configured.
Failed, disputed, or past-due payments may cause reminders, retry, restriction, suspension, plan change, or account closure consistent with the implemented commercial-state process and applicable law. Customer remains responsible for outstanding authorized charges.
Except where expressly provided in these Terms or an applicable written order, payment and subscription commitments are non-cancelable and fees paid are non- refundable. Cancellation stops future renewal but does not refund the current purchased term, completed usage, metered charges, or other amounts already incurred.
A refund, adjustment, or credit may be available only where: (a) these Terms or an applicable written order expressly provides it; (b) Get2Post confirms a billing error; (c) an express prorated remedy applies to a qualifying service termination or failure; or (d) applicable law requires it. To be eligible for an adjustment or credit for an alleged billing error, Customer must notify support@get2post.com no later than 10 days after the charge or invoice first appears, subject to Get2Post's review and confirmation of the error and subject to rights that cannot legally be waived.
Suspension or termination because of Customer's prohibited, fraudulent, abusive, illegal, or other violative conduct does not create a right to a refund, except where required by law. Nothing in this section limits mandatory consumer rights or other rights that cannot legally be limited.
13. Advertising and the Free with ads plan
The Free with ads plan may present Google advertising opportunities after eligible successful direct API request runs. The current product model counts successful direct GET and POST runs and uses the configured interval; failed or ineligible runs do not count. Paid plans bypass the Free with ads advertising gate.
The initial advertising provider is Google AdSense, the Google advertising service used by Get2Post. Provider advertising must remain disabled when the required configuration, allowed domain, or applicable advertising consent is unavailable or denied. Google advertising may use cookies, local storage, device or online identifiers, and activity information as described in the Privacy Policy and Google's notices.
For the United States launch, advertising is subject to implemented consent and privacy controls, applicable state targeted-advertising opt-outs, and recognized universal opt-out signals where required. Until those controls are implemented and validated, production advertising must not be activated.
14. Exports, deletion, and account closure
Authorized organization administrators can request an organization export, and authorized workspace users can export workspace definitions in the formats Get2Post makes available. Export packages may contain sensitive Customer Content and must be protected by Customer after download.
Authorized users may delete supported workspace content or a workspace. Personal account deletion removes the account and live memberships, linked sign-in providers, preferences, and matching invitations, but the last remaining organization owner must use the organization-closure process or transfer ownership first.
After account termination or an authenticated deletion request, Get2Post must delete Customer Content from active systems and complete deletion from ordinary backup systems no later than 90 days afterward. Narrow exceptions may apply where particular information must be retained for legal compliance, billing and tax records, fraud prevention, security investigations, dispute resolution, enforcement, or preservation of audit evidence. Any retained information must be limited to what is necessary, protected from unrelated use, and deleted or deidentified when the applicable need ends.
Deletion and privacy requests may also be submitted to support@get2post.com. We verify identity and authority before a protected export, correction, disclosure, or deletion. The Privacy Policy describes the operational retention schedule and additional retention and deletion details.
15. Security and incident responsibilities
We use administrative, technical, and organizational measures intended to protect Get2Post and Customer data. No system is completely secure. Customer must use appropriate access controls, least-privilege credentials, approvals, budgets, monitoring, and data minimization for its use case.
Customer must promptly notify support@get2post.com of suspected account compromise, credential exposure, unauthorized tenant access, security vulnerability, or harmful automation. We may take protective action, preserve evidence, and communicate with affected customers or authorities when required or permitted by law.
16. Get2Post ownership
3CodeMonkeys and its licensors retain all rights in Get2Post, including the software, user interface, documentation, trademarks, service data, and other materials that are not Customer Content. These Terms do not transfer ownership of Get2Post or grant a right to copy, resell, reverse engineer, or create a competing service except to the extent such a restriction is prohibited by law.
17. Service changes, availability, and support
We may add, change, limit, suspend, or discontinue features to address security, law, providers, reliability, abuse, pricing, or product needs. We will not silently convert a Customer to a paid plan or create a charge without an authorized purchase or usage policy.
Get2Post may be unavailable or experience errors, delays, third-party outages, or data-processing failures. No service-level commitment applies unless it is stated in a separate written agreement signed by 3CodeMonkeys.
Launch support is provided through support@get2post.com for general product help, bugs, account access, billing, privacy, security, abuse, and outages. We assess priority from impact. These Terms do not promise a fixed response or resolution time.
18. Warranties and limitation of liability
Except for an express commitment in these Terms or a separate written agreement, Get2Post is provided on an as available basis. We do not promise that every feature will be uninterrupted, error-free, or suitable for every Customer purpose. AI output, third-party services, Customer-configured endpoints, and automated actions require Customer review and control.
To the maximum extent permitted by applicable law, neither party will be liable to the other for any indirect, incidental, special, consequential, exemplary, punitive, or similar damages, or for loss of profits, revenue, business, goodwill, use, or data, or business interruption, arising out of or related to Get2Post or these Terms, even if the party knew or should have known that such damages were possible.
Except for the separate cap and exclusions stated below, the aggregate liability of either party for all claims arising out of or related to Get2Post or these Terms, regardless of legal theory, will not exceed the fees paid or owed by Customer for Get2Post during the 12 months immediately preceding the event giving rise to the claim. For Free services, trials, beta features, preview features, or other complimentary services for which no fee is charged, the aggregate liability of 3CodeMonkeys will not exceed US$100.
For claims arising from 3CodeMonkeys' breach of its confidentiality, privacy, or information-security obligations, the aggregate liability of 3CodeMonkeys will not exceed two times the general liability cap described in the preceding paragraph. If the general liability cap is US$100 because the applicable service is free, trial, beta, preview, or complimentary, the corresponding two-times cap is US$200.
The foregoing exclusions and caps do not apply to the extent prohibited by law or to liability arising from a party's gross negligence, willful misconduct, or fraud; a party's indemnification obligations to the extent stated in an applicable written agreement; infringement or misappropriation of another party's intellectual-property rights; Customer's payment obligations; or any other liability that cannot legally be excluded or limited. These limits apply even if a limited remedy fails of its essential purpose.
19. Suspension and termination
Customer may stop using Get2Post, cancel future renewal, delete eligible accounts or workspaces, or close an organization through available product or support processes. Amounts already incurred remain due, and termination does not create a refund right except as stated in Section 12 or required by law.
We may restrict or suspend access to protect customers, the service, providers, or evidence; respond to suspected unlawful activity, fraud, security harm, or abuse; address failed payment or commercial state; or comply with law. We may permanently terminate substantiated violations without refund, subject to applicable law.
Upon termination, Customer's right to use Get2Post ends. Provisions concerning ownership, authorized charges, evidence, enforcement, disclaimers, disputes, liability, and information that must be retained by their nature survive.
20. Informal dispute resolution and venue
Before filing a lawsuit, a party must send a written dispute notice to support@get2post.com and allow 30 days for a good-faith informal resolution. The notice should identify the parties, relevant account or organization, facts, and requested resolution without including passwords, secret keys, or unnecessary sensitive payloads.
The 30-day period does not prevent immediate court action reasonably necessary for urgent security, intellectual-property, confidentiality, evidence-preservation, or injunctive relief. Eligible small-claims procedures and mandatory consumer rights are preserved.
These Terms are governed by Minnesota law, without regard to conflict-of-law rules, except where mandatory applicable law requires otherwise. Subject to mandatory exceptions, exclusive venue is an appropriate Minnesota state court located in Scott County, Minnesota, or the United States District Court for the District of Minnesota when federal jurisdiction exists.
These Terms do not require pre-dispute mandatory arbitration and do not include a class-action waiver. After a dispute arises, all affected parties may voluntarily agree to arbitration.
21. Changes and versioned acceptance
We may revise these Terms. Each release will have a stable version and effective date. Material changes require notice and renewed acceptance through the implemented acceptance flow before continued use where required. Acceptance records may identify the user, organization, document version, time, and source, and historical acceptance must not be silently overwritten.
A future program that would use Customer Content to train or fine-tune a shared or general-purpose AI model requires a separate affirmative opt-in and may not be introduced through a silent update to these Terms or the Privacy Policy.
If Customer does not accept a required material update, Customer must stop use and may contact support about export, cancellation, or closure options. Changes do not retroactively authorize charges or conduct that was not authorized when it occurred.
22. Entire agreement and severability
These Terms, the Privacy Policy, the incorporated Universal Acceptable Use & Enforcement Policy, the Customer's applicable order, and any signed written agreement form the agreement for Get2Post. A signed written agreement controls only to the extent it expressly conflicts with these Terms.
If a provision is unenforceable, it will be applied to the maximum extent permitted and the remaining provisions remain in effect. A failure to enforce a provision once is not a waiver of future enforcement.
23. Contact
Questions or notices about these Terms may be sent to:
3CodeMonkeys, LLC
1382 Thistle Lane
Shakopee, MN 55379, USA
support@get2post.com