Terms of Service

This section applies to development sites, staging subdomains, and source access provisioned for a consulting or custom development engagement. It does not apply to a Cubite hosted site. Access to a hosted site is not tied to a project and does not end when a project ends.

Access to all development sites and subdomains under cubite.io and cubite.dev is granted solely in connection with active ongoing projects.

Upon project completion, expiration, or contract termination for any reason, your access will be revoked immediately.

Any attempt to access Cubite sites or services after contract termination is forbidden and may result in legal action.

This section applies only to consulting, custom development, migration, and other professional services engagements performed by Cubite under a separate statement of work or services agreement signed by both parties. It does not apply to a Cubite hosted site. Where a signed agreement between us (including a statement of work, subscription agreement, or license agreement) conflicts with these Terms, that agreement controls for that engagement.

You expressly authorize Cubite to charge your payment method on file for all invoices and authorized penalties without requiring further consent per invoice.

Payments are due on or before the invoice due date.

If payment is not received within one (1) calendar day after the due date (including weekends and holidays), Cubite will automatically charge the full unpaid invoice without further notice except two prior written reminders: 72 hours and 24 hours before auto-charging.

Failure to maintain a valid payment method authorizing such charges constitutes a material breach, permitting immediate contract termination.

This automatic payment authorization overrides any prior agreements or communications.

This section applies only to a consulting or custom development engagement under a signed statement of work, as set out at the start of Section 2. It does not apply to a Cubite hosted site.

Late payments trigger an automatic penalty equal to three (3) months' worth of the monthly contract payment, charged 24 hours after final notice.

These penalty charges are non-refundable except where a refund is required by law.

You acknowledge and accept these penalty amounts as reasonable pre-estimates of damages, not punitive excesses.

Removing or invalidating your authorized payment method while an invoice is outstanding is a material breach. Disputing a charge is not.

This section applies only to a consulting or custom development engagement under a signed statement of work, as set out at the start of Section 2. It does not apply to a Cubite hosted site.

Any failure to pay within the specified timeframe results in automatic contract cancellation.

Access to source code, platforms, and all related services will be revoked immediately.

You agree to cease all use and acknowledge that failure to comply may result in legal action.

This section applies only to a consulting or custom development engagement under a signed statement of work, as set out at the start of Section 2. It does not apply to a Cubite hosted site.

If you believe a charge is wrong, contact us first at hello@cubite.io. We will investigate and respond within five business days. Most billing disagreements are a mistake on someone's side and are faster to fix directly than through a third party.

Fees for professional services already performed are non-refundable, except where a refund is required by law or we agree one in writing.

Cubite may submit evidence of your acceptance of these Terms, invoice communications, and payment reminders in any dispute or arbitration process.

Nothing in these Terms limits rights you hold under applicable law. That includes your right to dispute a charge with your card issuer or payment provider, and your right to contact a regulator, data protection authority, or consumer protection agency at any time. We will not treat you doing either as a breach of this agreement.

You own the content in your site. That includes courses, lessons, pages, blog posts, images and files you upload, question banks, SCORM and xAPI packages, certificates, and the work your learners produce. Cubite claims no ownership of any of it.

You grant Cubite the limited right to host, copy, transmit, display, and back up that content for one purpose only: running the platform for you and supporting you when you ask. That right ends when you delete the content, except for copies in backups until those backups cycle out.

For learner personal data, you are the controller and Cubite is the processor. You decide what learner data is collected and why. We process it on your instructions to provide the platform, and not for our own purposes.

You are responsible for having a lawful basis to upload and process learner personal data, for giving your learners the notices they are entitled to, for collecting any consents required where they live, and for answering their requests about their own data. We will help you find, export, correct, or delete data held in your site so you can answer those requests.

Cubite uses the subprocessors listed in our Privacy Policy. By using the platform you authorize those subprocessors. We will update that list when we add a new one.

Do not upload health records, government identity documents, payment card numbers, or other special-category data unless we have agreed to it in writing first. If your learners are under 16, you must hold the consents required in their jurisdiction and tell us before you launch.

You confirm that you have the rights to the content you upload, that it does not infringe anyone else's copyright, trademark, or other rights, and that you are responsible for what the administrators, instructors, and integrations you authorize do inside your site.

You can export course and page content, and download learner reports as CSV, from the admin at any time. For a full site export including learner data, email hello@cubite.io and we will produce one.

Do not use Cubite to store, publish, or distribute content that is illegal where you or your learners are, that infringes someone else's copyright or trademark, that harasses or defames a person, or that sexualizes a minor. We remove that content and terminate the accounts behind it.

Do not upload or distribute malware. Content you upload runs in a browser on your own domain, so a SCORM or xAPI package, an embed, custom CSS, or custom JavaScript must not be used to attack your visitors, other tenants, or the platform. You are responsible for what your uploads do.

Do not try to reach another tenant's data, bypass authentication or permission checks, escalate your own access, or interfere with the operation of the platform.

Respect the rate limits returned in our API response headers. Do not scrape the platform, run load or stress tests against it, or automate the interface in a way that degrades service for other customers. If you need higher limits, ask us and we will look at it.

Do not resell or sublicense access to the Cubite platform itself to third parties as a hosting or LMS service, and do not use your access to replicate the platform. White-labeling your own site, selling your own courses, and charging your own learners are exactly what the product is for, and none of that is restricted.

Security research is welcome under our Security Policy at cubite.io/security-policy. Test only against your own site and your own data, do not run denial-of-service or volumetric tests, stop and report immediately if you reach anyone else's personal data, and send your report to security@cubite.io. Research that follows that policy is authorized and we will not pursue you for it, including for a good-faith mistake. Research that knowingly goes outside it is not authorized.

We may remove content or suspend access to enforce this section. Where the problem is fixable, we tell you what to change first.

Cubite provides a REST API and a public Model Context Protocol server so you can operate your site from your own code or from an AI assistant such as Claude, ChatGPT, or Gemini. Access uses either OAuth 2.1 or a scoped API key, and every credential is bound to a single site that you choose when you connect.

API keys and OAuth tokens are credentials. Treat them the way you treat a password. Do not commit them to source control, paste them into a shared document, or ship them in a browser bundle or mobile app. Rotate a credential if you think it has leaked, and revoke it when a person, tool, or agent no longer needs access.

Anything done with your credential is treated as done by you. That includes actions taken by an AI assistant, an autonomous agent, a script, or a contractor you handed a key to. We cannot tell an intended call from an unwanted one, and you are responsible for the result, including content published, users created, enrollments changed, and data deleted. This does not apply where the credential was used by someone else because of a security failure on our side.

Permissions limit what a credential can do. They do not make it safe. A connection with write permission can create, change, and delete real data in your live site, and a connection with user, member, or enrollment permission can read your learners' names and email addresses. Grant the narrowest set of permissions that does the job, and review your active connections regularly.

The API and the MCP server are included at no extra charge. No uptime commitment, response time, or support obligation applies to them unless we have agreed one with you in writing. We may rate limit, throttle, change, or version these interfaces, and we will give reasonable notice of breaking changes where we can.

We may revoke a credential or block a client at any time if it is abusing the platform, threatening its stability, or being used outside these Terms. You can revoke any key or connection yourself from your site's Integrations settings in the Cubite admin, and revocation takes effect immediately.

An MCP connection can be ended by either side at any time and for any reason. Removing the connector inside the assistant stops that client from calling Cubite. Revoking in Cubite invalidates the credential itself. Neither of us owes the other notice or a reason for doing so.

Writes made through the API and the MCP server are logged against the credential that made them. We use those logs to investigate abuse and to answer your questions about what changed in your site and when. Retention is described in our Privacy Policy.

Cubite includes optional AI features, such as AI drafting of course and page content, an AI tutor for learners, prompt practice activities, and the MCP connection that lets an outside assistant operate your site. These features are off until you choose to use them.

AI output can be wrong. It can invent facts, cite sources that do not exist, misstate a regulation or standard, produce an assessment item with no correct answer, or reproduce text it should not. Review AI output before you publish it, and check anything with a safety, medical, legal, compliance, or accreditation consequence against the underlying source.

You are responsible for what you publish. Once you save or publish AI-assisted content in your site, it is your content under Section 6, on the same footing as content you wrote yourself. Cubite is not its author or its publisher.

When you use an AI feature, the prompt, the content, and the surrounding context needed for that feature are sent to the AI provider that powers it. The providers we use are listed in our Privacy Policy. That processing happens under the provider's own terms and Cubite does not control it. If you use an MCP connection, data returned to your assistant is handled by the vendor of that assistant, not by Cubite.

Cubite does not warrant that AI output is accurate, complete, current, original, or fit for any particular purpose, including certification, regulated compliance training, or accreditation. Do not rely on it as the only basis for a decision that affects a person's employment, certification, qualification, or safety.

AI features depend on third-party models. We may change, add, or remove a model or a provider, and a feature can be unavailable while a provider is down. We keep the provider list in the Privacy Policy current.

This section applies to custom deliverables produced by Cubite under a statement of work. It does not apply to the content, media, or learner data in your Cubite site, which you own under Section 6, and which Cubite never holds back for non-payment.

All custom code, designs, and deliverables created by Cubite remain the intellectual property of Cubite until full payment is received. Upon receipt of full payment, ownership of custom deliverables transfers to the client as specified in the project agreement.

Cubite retains the right to use general techniques, knowledge, and non-proprietary components developed during your project for other clients.

Open-source components used in your project remain subject to their respective licenses.

Cubite will maintain detailed audit logs of all invoice issuances, payment reminders, customer consents, charges, and communications.

You agree to receive all billing-related communications electronically and acknowledge their validity.

To the maximum extent permitted by law, Cubite's total liability for any claim arising from or related to our services shall not exceed the total fees paid by you during the twelve (12) months preceding the claim.

Cubite shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, or business opportunities, regardless of the cause of action.

This section applies only to a consulting or custom development engagement under a signed statement of work, as set out at the start of Section 2. It does not apply to a Cubite hosted site.

In the event that Cubite is unable to collect any unpaid invoices, penalties, or other charges through automatic collection via Stripe, both parties agree to resolve the dispute exclusively through binding arbitration on the Brief platform (thinkbrief.com).

This arbitration shall be conducted under Brief's rules and procedures and aims to provide an efficient, affordable, legally binding resolution without resorting to courts or traditional litigation.

Both parties waive any right to litigate such payment disputes in any court, agreeing instead to resolve all claims, controversies, or disputes regarding payment obligations through this arbitration process.

A statement of work or services agreement signed by both parties may only be modified by a further written agreement signed by both parties. These Terms themselves may be updated by us as described below.

These Terms are governed by the laws of the State of Delaware, United States, without regard to its conflict of law provisions. Except for payment disputes covered by the arbitration section above, you agree that the exclusive venue for any dispute arising out of or relating to these Terms is the state and federal courts located in Delaware, and you waive any objection to that venue.

We reserve the right to update these Terms at any time. Changes will be posted on this page with an updated "Last updated" date. Continued use of our services after changes constitutes acceptance of the revised Terms.

These Terms are entered into with Cubite Technologies Corp, a corporation organized under the laws of the State of Delaware, United States, which operates cubite.io and the Cubite platform.

If you have questions about these Terms, please contact us at hello@cubite.io.