LEGAL - TERMS

OwnBot Terms of Service

Effective Date: July 6, 2026

These Terms of Service govern the services provided by OwnBot.

By requesting or approving a project, submitting payment, purchasing hosting, accepting a quote or project agreement, or otherwise using OwnBot’s services, you agree to these Terms.

Please read these Terms carefully before purchasing any service.

1. About OwnBot

OwnBot provides custom Discord bot development, deployment, hosting, maintenance, and related technical services.

OwnBot is an independent service and is not affiliated with, sponsored by, or endorsed by Discord Inc.

OwnBot is a custom development service. Customers describe the bot they want, receive a quote, and have the bot developed for them. OwnBot is not a self-service or no-code bot-building platform.

2. Customer Eligibility

You must be at least 18 years old and legally capable of entering into a binding agreement to purchase services from OwnBot.

If you are under 18, a parent or legal guardian must place the order, approve the project, accept these Terms, and make all required payments. The parent or legal guardian will be considered the customer under the agreement.

By purchasing services, you represent that:

  • The information you provide is accurate;
  • You are legally capable of entering into the agreement;
  • You have authority to make the purchase; and
  • You have authority to request the bot and provide any related server access, content, or materials.

If you purchase services on behalf of a company, organization, community, or Discord server, you represent that you have authority to bind that organization to the applicable agreement.

3. Project Scope

Before development begins, OwnBot and the customer will agree in writing on the project’s features, price, and general requirements.

The approved project scope may be documented through:

  • A project proposal;
  • A written quote;
  • An invoice;
  • A Statement of Work;
  • Discord or email communications;
  • A project summary; or
  • Another written agreement accepted by both parties.

Only features and services expressly included in the approved scope are included in the quoted price.

Informal ideas, suggestions, examples, assumptions, or discussions that are not included in the final approved scope are not automatically included in the project.

The customer is responsible for reviewing the project scope before approving it.

4. Changes to the Project Scope

A request is outside the original scope when it adds or materially changes the work OwnBot agreed to perform.

Examples may include:

  • Adding a new command;
  • Adding a new integration;
  • Redesigning an existing system;
  • Changing the purpose of a feature;
  • Making an existing feature behave substantially differently;
  • Supporting an additional platform or environment; or
  • Adding functionality that was not included in the approved scope.

OwnBot may provide a separate quote for work outside the approved scope.

Additional work may require:

  • Additional payment;
  • A revised development schedule;
  • A new deposit;
  • A separate project agreement; or
  • Other revised terms.

OwnBot is not required to perform work outside the approved scope.

OwnBot may also revise a quote or timeline if the customer provided incomplete, inaccurate, misleading, or materially different information when the original quote was prepared.

5. Payment Schedule

Unless OwnBot agrees to another payment schedule in writing, every project requires:

  1. Fifty percent of the total project price before development begins; and
  2. The remaining fifty percent after the completed project is presented for review, but before final delivery.

OwnBot is not required to begin development until the initial payment has cleared.

OwnBot may demonstrate the completed bot through:

  • A test server;
  • A temporary hosted environment;
  • Screen sharing;
  • A video;
  • Screenshots;
  • Live testing; or
  • Another reasonable demonstration method.

A demonstration does not constitute final delivery.

The remaining balance must be paid before OwnBot is required to provide:

  • Complete source code;
  • Production deployment;
  • Project files;
  • Database files;
  • Credentials;
  • Ownership rights; or
  • Other final deliverables.

Ownership of the delivered source code does not transfer until OwnBot has received full payment.

6. Refunds

Because OwnBot provides custom development services, payments are generally nonrefundable when the cancellation, delay, or dispute is caused by the customer.

Refunds will generally not be provided when the customer:

  • Changes their mind;
  • Decides they no longer want the bot;
  • Decides the project was a bad idea;
  • Loses interest in the project;
  • Changes their plans or budget;
  • No longer has a use for the bot;
  • Fails to provide required information, access, feedback, or approval;
  • Abandons the project;
  • Requests cancellation after OwnBot has reserved development time or begun work;
  • Requests features outside the approved scope; or
  • Is dissatisfied with something that matches the approved scope.

These circumstances do not automatically entitle the customer to recover payments already made. OwnBot may have reserved development time, declined other work, incurred expenses, or performed custom work specifically for the customer.

A customer may be eligible for a partial or full refund when:

  • OwnBot determines that it cannot complete the project;
  • OwnBot cancels the project for reasons not caused by the customer;
  • OwnBot materially fails to deliver the agreed project scope; or
  • OwnBot and the customer mutually agree that a refund is appropriate.

The amount of any refund will depend on the circumstances, including:

  • The amount of work already completed;
  • The amount of development time already spent;
  • The value of any work or materials already delivered;
  • Any usable portions of the project;
  • Any nonrecoverable third-party costs;
  • The reason the project could not be completed; and
  • Whether the customer contributed to the failure or delay.

A full refund may be appropriate if OwnBot is unable to provide any meaningful part of the agreed service.

A partial refund may be appropriate if part of the project was completed, delivered, or remains usable.

Refund eligibility and refund amounts will be determined on a case-by-case basis, except where applicable law requires a different result.

A bug, delay, disagreement, outage, or other problem does not automatically entitle the customer to a refund. OwnBot must be given a reasonable opportunity to investigate and correct a covered problem before failure to deliver is established.

7. Project Timelines

Any development timeline or completion date provided by OwnBot is an estimate unless OwnBot expressly guarantees a deadline in writing.

Estimated timelines may change because of:

  • Changes to the project scope;
  • Delayed customer responses;
  • Missing information or access;
  • Technical complications;
  • Unexpected development requirements;
  • Third-party outages;
  • Discord platform changes;
  • Illness or emergencies;
  • Events outside OwnBot’s reasonable control; or
  • Other circumstances affecting development.

OwnBot will make reasonable efforts to communicate significant delays.

A delayed estimated completion date does not automatically constitute failure to deliver and does not automatically entitle the customer to a refund.

Customer-caused delays automatically extend any estimated project timeline by a reasonable amount.

8. Customer Responsibilities

The customer is responsible for:

  • Providing complete and accurate requirements;
  • Reviewing the agreed project scope;
  • Responding to reasonable questions;
  • Providing approvals when requested;
  • Providing required server access, accounts, content, and permissions;
  • Ensuring they have authority to provide those materials;
  • Testing the completed bot during the review period;
  • Paying all invoices when due;
  • Maintaining lawful control of any server involved;
  • Protecting delivered credentials and files; and
  • Using the bot lawfully and in accordance with platform rules.

OwnBot is not responsible for delays, defects, missing functionality, or additional costs caused by inaccurate instructions, missing information, unavailable access, or the customer’s failure to cooperate.

9. Abandoned Projects

An active project may be considered abandoned when the customer leaves a communication from OwnBot requiring a response unanswered for more than 14 consecutive calendar days.

Communications requiring a response may include:

  • Questions about project requirements;
  • Requests for access or information;
  • Requests for customer approval;
  • Requests to review completed work;
  • Payment notices; or
  • Other communications necessary to continue the project.

A project will not be considered abandoned if the customer gives OwnBot advance notice of a reasonable absence or expected delay, such as travel, illness, or temporary unavailability.

When a project is abandoned:

  • OwnBot may stop working on the project;
  • Payments already made generally remain nonrefundable;
  • OwnBot is not required to preserve the original timeline;
  • OwnBot may reallocate the reserved development time;
  • Resuming the work may require a revised quote or timeline; and
  • OwnBot may require payment of outstanding amounts before resuming or releasing completed work.

Abandonment applies only to the current project or work order.

It does not prevent the customer from returning later to purchase a separate update, upgrade, or new project.

10. Seven-Day Quick-Change Period

After OwnBot presents the substantially completed bot for review, the customer will have seven calendar days to test it and submit one consolidated list of minor change requests.

A minor change is a small adjustment to an existing feature that already operates according to the approved scope.

Examples may include:

  • Changing the wording of a command response;
  • Adjusting labels;
  • Changing basic colors or formatting;
  • Correcting simple text;
  • Changing a configuration default; or
  • Making another small adjustment that does not materially change the feature.

The quick-change period does not include:

  • New commands;
  • New features;
  • New integrations;
  • Major redesigns;
  • Requests to change the purpose of a feature;
  • Requests to make a feature operate materially differently;
  • Changes requiring substantial additional development; or
  • Work outside the approved scope.

For example, asking OwnBot to change the wording displayed by a working command may qualify as a quick change.

Asking OwnBot to change what the feature actually does generally constitutes additional paid work.

The customer must submit quick-change requests as one consolidated list unless OwnBot agrees otherwise.

Unused quick-change rights expire after the seven-day period.

The quick-change period does not provide unlimited revisions.

Requests outside the quick-change period or project scope may require an additional quote and payment.

If the customer does not submit change requests or report a material issue during the seven-day period, OwnBot may consider the project accepted and require the remaining balance.

11. Final Delivery

Final delivery occurs when OwnBot provides the agreed final deliverables after receiving full payment.

Depending on the project, delivery may include:

  • Source code;
  • Project files;
  • Database files;
  • Setup instructions;
  • Deployment;
  • Discord application access;
  • Bot credentials; or
  • Other materials included in the approved scope.

The customer is responsible for securely storing all delivered files, code, tokens, passwords, credentials, databases, and backups.

Unless hosting or maintenance is purchased separately, OwnBot has no continuing obligation to operate, monitor, update, back up, or maintain the bot after delivery.

12. Thirty-Day Bug Warranty

OwnBot provides a 30-calendar-day limited bug warranty beginning on the date of final delivery.

During this period, OwnBot will correct qualifying bugs in the original delivered work without charging an additional development fee.

A qualifying bug is a reproducible defect caused by OwnBot’s original code that prevents an agreed feature from functioning substantially as described in the approved scope during normal intended use.

A bug exists when the bot does not perform the function OwnBot agreed to provide.

A change request exists when the bot operates according to the agreement, but the customer wants it to operate differently.

The customer must provide enough information for OwnBot to reasonably investigate the issue. This may include:

  • Error messages;
  • Screenshots;
  • Logs;
  • Affected commands;
  • Expected behavior;
  • Actual behavior; and
  • Steps for reproducing the issue.

The bug warranty does not cover:

  • New features;
  • Preference changes;
  • Features not included in the approved scope;
  • Changes to the intended behavior of a working feature;
  • Customer modifications;
  • Modifications made by another developer;
  • Incorrect installation;
  • Incorrect configuration;
  • Unsupported self-hosting environments;
  • Misuse;
  • Use outside the bot’s intended purpose;
  • Deleted, exposed, lost, or mishandled credentials;
  • Discord outages or changes;
  • Discord API or policy changes;
  • Third-party outages or changes;
  • Interference from another bot or system;
  • Security incidents occurring after delivery;
  • Attacks, exploits, or unauthorized access;
  • Problems caused by customer-controlled hosting;
  • Problems OwnBot cannot reasonably reproduce; or
  • Issues first reported after the warranty period expires.

The warranty is a promise to correct qualifying defects. It is not a guarantee that the bot will always operate without interruption, error, vulnerability, or incompatibility.

OwnBot may charge for investigation or work that is determined not to be covered by the warranty.

Work outside the warranty may require a new quote and payment.

13. Source-Code Ownership

After OwnBot receives full payment, the customer owns the complete source code delivered for their project.

OwnBot does not retain partial ownership of the delivered source code merely because portions of the code contain reusable or commonly used components.

However, software projects commonly use general-purpose concepts, structures, techniques, patterns, functions, utilities, modules, and components that may also be useful in other projects.

OwnBot retains the right to use, recreate, adapt, improve, and reuse general-purpose:

  • Programming concepts;
  • Development techniques;
  • Architectural patterns;
  • Functions;
  • Utilities;
  • Reusable modules;
  • Templates;
  • Internal tools;
  • Technical knowledge; and
  • Non-customer-specific components.

The customer’s ownership of the delivered code is not reduced because OwnBot separately uses or recreates reusable components in another project.

OwnBot may not simply copy the customer’s complete bot and resell it to another customer as a custom project.

OwnBot will not intentionally reuse or disclose the customer’s:

  • Confidential information;
  • Private data;
  • Credentials;
  • Private branding materials;
  • Proprietary content; or
  • Customer-specific business information.

The customer’s ownership does not include ownership of:

  • Discord;
  • Discord APIs;
  • Third-party platforms;
  • Open-source libraries;
  • Third-party software packages;
  • External APIs;
  • Licensed assets; or
  • Materials owned by another person or company.

Those materials remain subject to their respective terms and licenses.

14. Customer Modifications

After ownership transfers, the customer may:

  • Modify the delivered code;
  • Operate the bot;
  • Self-host the bot;
  • Hire another developer to modify it; or
  • Use the bot for its intended lawful purpose.

Once the customer or another party modifies the code, OwnBot is not responsible for defects, security issues, compatibility problems, data loss, downtime, or other consequences caused by or related to those modifications.

OwnBot is not required to support a modified version unless OwnBot separately agrees to do so in writing.

The customer may not falsely represent that OwnBot endorses, maintains, or remains responsible for a modified version.

15. Portfolio Use

Unless the customer asks for the project to remain private, OwnBot may identify and display completed work in its portfolio, website, social media, proposals, and marketing materials.

Portfolio materials may include:

  • The customer’s server or project name;
  • The customer’s logo;
  • Screenshots;
  • Recordings;
  • A general project description;
  • Publicly available information; and
  • General, nonconfidential performance information.

A customer may request in writing that a project remain private.

OwnBot will make reasonable efforts to honor the request for future portfolio and marketing use.

OwnBot will not intentionally publish:

  • Private credentials;
  • Private source code;
  • Confidential customer information;
  • Nonpublic personal information; or
  • Private user data.

16. Hosting Services

Hosting is a separate recurring service and is not included in development unless specifically stated in writing.

Hosting prices are determined individually based on factors such as:

  • Bot features;
  • Expected usage;
  • Actual usage;
  • Processing requirements;
  • Storage requirements;
  • Traffic;
  • Database size;
  • External service costs; and
  • Other technical requirements.

Hosting may renew automatically according to the billing period presented to the customer.

The customer may cancel hosting at any time.

Cancellation stops future renewal charges but does not automatically refund the current or previous billing period.

Hosting payments for a billing period that has already begun are generally nonrefundable, except where required by law or where OwnBot expressly agrees otherwise.

17. Hosting Price Changes

OwnBot may increase the price of hosting when:

  • The bot receives substantially more usage;
  • Resource requirements increase;
  • Storage or database requirements increase;
  • Processing requirements increase;
  • Infrastructure costs increase;
  • Third-party costs increase; or
  • The original hosting level is no longer sufficient.

OwnBot will notify the customer at least 14 calendar days before the next charge date on which the increased price will apply.

The notice will identify the new price or provide enough information for the customer to understand the change.

The customer may cancel hosting before the next charge date if they do not accept the new price.

Continued use of hosting after the new price takes effect constitutes acceptance of the updated price, except where applicable law requires another form of consent.

18. Hosting Availability

OwnBot does not guarantee uninterrupted or error-free hosting and does not promise a specific uptime percentage unless a separate written agreement expressly provides one.

OwnBot may temporarily limit, restart, maintain, or suspend hosting when reasonably necessary because of:

  • Maintenance;
  • Technical problems;
  • Security concerns;
  • Excessive resource usage;
  • Nonpayment;
  • Abuse;
  • Illegal activity;
  • Platform violations;
  • Infrastructure problems;
  • Third-party outages; or
  • Risks to OwnBot, its accounts, its infrastructure, or other customers.

OwnBot is not responsible for missed commands, lost server activity, lost revenue, or other consequences caused by temporary hosting interruptions, except to the extent liability cannot legally be excluded.

19. Hosting Cancellation and Data

When hosting is canceled:

  • Future renewal charges will stop;
  • Previously charged billing periods generally remain nonrefundable;
  • The bot may be taken offline at the end of the paid billing period;
  • OwnBot may remove the bot from its infrastructure; and
  • Associated data may eventually be deleted.

The customer is responsible for requesting and maintaining any source-code, database, or data copies they require before hosting ends.

OwnBot does not guarantee indefinite retention of hosted data after cancellation or termination.

20. Security and Credentials

The customer is responsible for protecting all bot tokens, passwords, API keys, account credentials, source code, database files, and other sensitive materials after delivery or transfer.

The customer must not publicly expose credentials or provide them to unauthorized individuals.

OwnBot is not responsible for unauthorized access, hacking, exploitation, abuse, data loss, server damage, or other security incidents that occur after delivery or after the customer assumes control of:

  • The code;
  • Credentials;
  • Hosting environment;
  • Discord application;
  • Database; or
  • Related accounts.

No software or hosting system can be guaranteed to be completely secure.

OwnBot does not guarantee that a bot will be immune from every:

  • Vulnerability;
  • Exploit;
  • Attack;
  • Misuse;
  • Unauthorized modification;
  • Configuration error; or
  • Security incident.

The customer should promptly rotate any credential that may have been exposed.

21. Discord and Third-Party Services

OwnBot’s services may depend on Discord and other third-party:

  • Platforms;
  • APIs;
  • Libraries;
  • Hosting providers;
  • Databases;
  • Payment processors;
  • Authentication providers; or
  • Integrations.

OwnBot does not control those services and is not responsible for their:

  • Outages;
  • Downtime;
  • Service discontinuation;
  • API changes;
  • Rate limits;
  • Permission changes;
  • Policy changes;
  • Pricing changes;
  • Account restrictions;
  • Server restrictions;
  • Bans;
  • Lost access; or
  • Removed functionality.

A bot that functions correctly at delivery may later require changes because Discord or another third party modifies its systems.

Unless covered by the limited bug warranty or a separate maintenance agreement, compatibility work caused by later third-party changes may require additional payment.

The customer remains responsible for complying with the rules and terms of every third-party service used with the bot.

22. Prohibited Projects and Uses

OwnBot may reject, suspend, or terminate any project or service that OwnBot reasonably believes involves:

  • Illegal activity;
  • Fraud;
  • Scams;
  • Spam;
  • Unsolicited mass messaging;
  • Harassment;
  • Threats;
  • Abuse;
  • Credential theft;
  • Phishing;
  • Malware;
  • Malicious code;
  • Unauthorized access;
  • Self-bots;
  • User-account automation;
  • Account farming;
  • Artificial engagement;
  • Platform manipulation;
  • Unauthorized collection of private data;
  • Intellectual-property infringement;
  • Circumvention of platform restrictions;
  • Violations of Discord’s rules;
  • Risks to OwnBot’s infrastructure, accounts, security, legal compliance, or reputation; or
  • Other harmful or inappropriate activity.

OwnBot is not required to complete work that becomes prohibited, dangerous, unlawful, or incompatible with third-party rules.

If a project is rejected or terminated because of the customer’s instructions, conduct, misuse, misrepresentation, or violation of these Terms, payments already made will generally remain nonrefundable.

23. Customer-Provided Materials

The customer retains ownership of materials they provide to OwnBot.

The customer represents that they have all necessary rights and permissions to provide and use those materials.

Customer-provided materials may include:

  • Logos;
  • Images;
  • Text;
  • Audio;
  • Videos;
  • Databases;
  • User information;
  • Server content;
  • API credentials;
  • Branding; and
  • Other intellectual property.

The customer is responsible for claims or harm arising from materials, instructions, or data they provided without proper authorization.

24. Support and Additional Work

Unless included in hosting, maintenance, or another written agreement, ongoing support after the bug-warranty period is not included in the original project price.

OwnBot may charge for:

  • New features;
  • Behavior changes;
  • Redesigns;
  • New integrations;
  • Discord compatibility updates;
  • Migration work;
  • Customer-caused issues;
  • Third-party changes;
  • Security reviews;
  • Recovery work;
  • Reinstallation;
  • Data restoration;
  • Hosting changes; or
  • Other work outside the approved scope.

OwnBot may refuse additional work based on availability, technical limitations, project risk, customer conduct, or other reasonable business considerations.

25. Customer Cancellation

The customer may request cancellation by contacting OwnBot.

Customer-requested cancellation does not automatically create a right to a refund.

Payments already made will generally remain nonrefundable when cancellation results from:

  • A change of mind;
  • Buyer’s remorse;
  • Changed plans;
  • Loss of interest;
  • Budget changes;
  • Failure to cooperate;
  • Abandonment;
  • Dissatisfaction with work that matches the approved scope; or
  • Another reason caused by the customer.

Cancellation does not remove the customer’s obligation to pay any amount already earned or owed.

26. Cancellation or Termination by OwnBot

OwnBot may reject, suspend, cancel, or terminate a project or service because of:

  • Nonpayment;
  • Abandonment;
  • Abusive or threatening conduct;
  • Misrepresentation;
  • Illegal or prohibited requests;
  • Security risks;
  • Platform violations;
  • Failure to cooperate;
  • Fraudulent payment activity;
  • Chargebacks;
  • Misuse of the service; or
  • A material violation of these Terms.

When OwnBot terminates a project because of the customer’s conduct or violation of these Terms, payments generally remain nonrefundable.

When OwnBot cancels a project for reasons not caused by the customer, or when OwnBot determines it cannot materially complete the agreed scope, OwnBot may issue a partial or full refund.

Any refund will account for:

  • Work already completed;
  • Development time already spent;
  • Value already delivered;
  • Third-party expenses; and
  • The circumstances surrounding the cancellation.

27. Payment Disputes and Chargebacks

Customers should contact OwnBot and make a good-faith effort to resolve billing concerns before initiating a chargeback or payment dispute.

This does not remove any dispute right that cannot legally be waived.

OwnBot may suspend development, delivery, hosting, support, or access when a chargeback or payment dispute is filed.

OwnBot may provide relevant records to the payment processor or financial institution, including:

  • Accepted Terms;
  • Quotes;
  • Invoices;
  • Project communications;
  • Demonstrations;
  • Customer approvals;
  • Delivery records; and
  • Usage information.

Fraudulent or abusive chargebacks may result in permanent termination of services.

28. Privacy and Bot Data

OwnBot’s handling of personal information may be further described in a separate Privacy Policy.

The customer is responsible for determining whether their bot requires:

  • A privacy notice;
  • User disclosures;
  • User consent;
  • Data-retention rules;
  • Moderation policies; or
  • Other legal documentation.

When the customer owns or operates a delivered bot, the customer is responsible for the bot’s collection and use of Discord user data, except where OwnBot separately agrees to manage that data as part of hosting or maintenance.

29. Disclaimer of Warranties

To the fullest extent permitted by law, OwnBot provides its services, code, bots, hosting, and deliverables on an “as is” and “as available” basis, except for the express 30-day limited bug warranty stated in these Terms.

OwnBot does not guarantee that a bot or service will:

  • Be completely error-free;
  • Be completely secure;
  • Operate without interruption;
  • Meet unstated expectations;
  • Remain compatible with future Discord changes;
  • Prevent every form of misuse or attack;
  • Produce a particular business result;
  • Increase server membership, activity, revenue, or engagement; or
  • Remain available indefinitely.

The customer accepts the technical and operational risks associated with owning and operating custom software.

30. Limitation of Liability

To the fullest extent permitted by law, OwnBot will not be liable for any indirect, incidental, special, exemplary, punitive, or consequential damages.

OwnBot is not responsible for losses involving:

  • Revenue;
  • Profits;
  • Business opportunities;
  • Discord members;
  • Server activity;
  • Reputation;
  • Data;
  • Databases;
  • Credentials;
  • Server access;
  • Business interruption;
  • Hosting downtime;
  • Security incidents;
  • Unauthorized access;
  • Hacking;
  • Exploitation;
  • Discord bans or restrictions;
  • Third-party outages;
  • API changes;
  • Customer misuse;
  • Customer modifications; or
  • Decisions made based on the bot’s output.

Once the customer controls the delivered code, credentials, application, or hosting environment, the customer assumes responsibility for operating and securing those materials.

The occurrence of a defect, outage, security incident, data loss, platform action, or other problem does not automatically entitle the customer to a refund.

If OwnBot is found legally liable for a claim that cannot lawfully be excluded, OwnBot’s maximum total liability will not exceed the amount the customer paid OwnBot for the specific project or hosting service directly giving rise to the claim.

Some jurisdictions do not permit certain warranty disclaimers or liability limitations. In those jurisdictions, these provisions apply only to the maximum extent permitted by law.

31. Indemnification

To the extent permitted by law, the customer agrees to defend, indemnify, and hold OwnBot harmless from claims, damages, liabilities, losses, and reasonable expenses arising from:

  • The customer’s use or misuse of the bot;
  • The customer’s content, data, or instructions;
  • The customer’s violation of these Terms;
  • The customer’s violation of law;
  • The customer’s violation of third-party rights;
  • Activity occurring through customer-controlled credentials or infrastructure; or
  • Modifications made after delivery by the customer or another party.

32. Electronic Communications and Acceptance

The customer agrees that electronic communications may be used to conduct business with OwnBot.

Electronic acceptance may include:

  • Checking an acceptance box;
  • Clicking an acceptance button;
  • Approving a written quote;
  • Approving a project through Discord or email;
  • Submitting payment;
  • Signing electronically; or
  • Continuing a recurring service after receiving applicable notice.

Electronic acceptance has the same effect as a physical signature to the extent permitted by law.

The customer is responsible for maintaining accurate contact information and reviewing messages relating to their project or service.

33. Changes to These Terms

OwnBot may update these Terms from time to time.

The updated Terms will display a revised effective date.

Changes generally apply to:

  • Future purchases;
  • New projects; and
  • Continued recurring services after the revised Terms take effect.

Changes will not retroactively alter an existing project’s agreed scope, ownership terms, or payment terms unless:

  • OwnBot and the customer agree otherwise; or
  • The change is required by law.

OwnBot may provide notice of material changes through its website, email, Discord, or another communication method associated with the customer.

34. Project-Specific Agreements

A written quote, proposal, invoice, Statement of Work, or other project-specific agreement may contain additional terms.

If a project-specific agreement directly conflicts with these Terms, the project-specific agreement controls for that project regarding the conflicting subject.

All other provisions of these Terms remain effective.

35. Severability

If any provision of these Terms is found invalid, unlawful, or unenforceable, that provision will be enforced to the greatest extent legally permitted.

The remaining provisions will continue in effect.

36. No Waiver

If OwnBot does not enforce a provision of these Terms in one situation, that does not waive OwnBot’s right to enforce it later or in another situation.

37. Entire Agreement

These Terms, together with the applicable project scope, quote, invoice, Privacy Policy, and any other written agreement accepted by the customer, form the complete agreement between OwnBot and the customer regarding the applicable services.

They replace prior discussions or understandings concerning the same subject, except for obligations expressly preserved in writing.

38. Contact

Questions, cancellation requests, legal notices, and other communications regarding these Terms should be submitted by contacting OwnBot through an available official support or communication channel.