This RENBOTS User Agreement (“Agreement”) governs use of the RENBOTS ecosystem, including RENBOTS.com, REN and RENBOTS hardware, software, firmware, memberships, digital files, documentation, applications, development materials, assembly kits, physical products, community resources, and related technologies.

This Agreement is intended to serve as the primary umbrella agreement defining the relationship between RENBOTS and persons or organizations that interact with the RENBOTS ecosystem.

Please read this Agreement carefully.

By accessing, downloading, purchasing, assembling, installing, configuring, modifying, integrating, operating, testing, or otherwise using any RENBOTS Product or Service, you agree to the applicable provisions of this Agreement and the additional policies incorporated into it.

1. WHO PROVIDES RENBOTS
RENBOTS, REN, and RENBOTS.com are brand and platform representations associated with robotics hardware, software, digital materials, memberships, services, and related technologies within the BitForge Dynamics ecosystem.

BitNip LLC

BitNip LLC operates and publishes RENBOTS.com and serves as an authorized distributor, publisher, storefront operator, membership administrator, digital-content provider, and customer-facing platform operator for applicable RENBOTS products and services.

BitForge Dynamics LLC

BitForge Dynamics LLC develops, owns, licenses, or otherwise controls certain REN and RENBOTS:

• hardware;

• robotics designs;

• software;

• firmware;

• applications;

• technology;

• documentation;

• intellectual property;

• product designs; and

• related materials.

BitNip LLC is authorized to distribute, publish, market, license, and sell applicable BitForge Dynamics LLC products and materials through RENBOTS.com.

BitNip LLC is partially owned by BitForge Dynamics LLC.
However:

BitNip LLC and BitForge Dynamics LLC are separate legal entities.
References in this Agreement to “RENBOTS,” “we,” “us,” or “our” may refer to BitNip LLC, BitForge Dynamics LLC, or both depending upon the product, service, activity, or right involved.

2. WHO IS A RENBOTS USER?
For purposes of this Agreement, a “RENBOTS User” or “User” means any person or organization that accesses, possesses, interacts with, uses, builds, modifies, integrates, purchases, downloads, operates, or otherwise engages with any portion of the RENBOTS ecosystem.

A User may include, without limitation:

• a visitor to RENBOTS.com;

• a Free Member;

• a Pro Member;

• a purchaser;

• a preorder customer;

• a person downloading RENBOTS materials;

• a person fabricating RENBOTS hardware;

• an owner of a RENBOTS system;

• an operator of a REN or RENBOTS robot;

• a developer using RENBOTS software;

• a developer using an applicable API or SDK;

• a person modifying RENBOTS hardware;

• a person creating an accessory compatible with RENBOTS;

• a researcher;

• an educator;

• a student;

• a laboratory;

• a university;

• a business;

• a government organization;

• an integrator;

• a contractor;

• an authorized employee;

• a member of a development team; or

• another person interacting with the RENBOTS platform.

A person does not need to hold a paid membership to be considered a User.

3. THE RENBOTS ECOSYSTEM
For purposes of this Agreement, the “RENBOTS Ecosystem” may include:

• RENBOTS.com;

• REN;

• RENBOTS;

• CORE systems;

• HEAD systems;

• robotics bodies;

• modular hardware;

• accessories;

• development hardware;

• production hardware;

• physical kits;

• assembly kits;

• electronic systems;

• software;

• firmware;

• applications;

• downloadable files;

• CAD files;

• 3D-printing files;

• schematics;

• documentation;

• APIs;

• SDKs;

• AI integrations;

• local AI systems;

• third-party AI integrations;

• member resources;

• community content;

• educational resources; and

• future compatible RENBOTS products or services.

Not every component of the ecosystem is governed by the same license or access model.

Users must review the terms that apply to the particular product, version, file, software package, or service they are using.

4. PURPOSE OF RENBOTS
RENBOTS is intended to provide a modular robotics platform that supports activities such as:

• robotics development;

• experimentation;

• education;

• research;

• prototyping;

• software development;

• AI integration;

• hardware development;

• fabrication;

• community participation;

• compatible accessory development;

• automation;

• commercial applications where properly licensed; and

• development of new robotics technologies.

RENBOTS is designed to be modular and extensible.
Users may therefore interact with RENBOTS in ways that were not specifically anticipated by BitNip LLC or BitForge Dynamics LLC.
Such flexibility does not eliminate the User's responsibility to evaluate whether a particular use is appropriate and safe.
5. AGREEMENT STRUCTURE
This User Agreement serves as the umbrella agreement for RENBOTS.
Depending upon how a User interacts with RENBOTS, additional terms may apply.
These may include:

• RENBOTS Website Terms & Conditions;

• RENBOTS Website Privacy Policy;

• RENBOTS Cookie Policy;

• RENBOTS Member Terms & Conditions;

• RENBOTS Disclaimers;

• RENBOTS Disclaimers & Safety Policy;

• RENBOTS Digital File License;

• software licenses;

• firmware licenses;

• open-source licenses;

• open-hardware licenses;

• preorder terms;

• warranty terms;

• product-specific terms;

• SDK or API terms;

• commercial licensing agreements; or

• other written agreements.

These documents are incorporated into this Agreement where applicable.
If a specific written license or product agreement conflicts with this general User Agreement regarding a particular product or file, the more specific applicable agreement controls that subject.
6. DIFFERENT USERS HAVE DIFFERENT RIGHTS
Not every User receives the same rights.
Rights depend on factors such as:

• membership level;

• purchase status;

• file version;

• license type;

• product type;

• software license;

• commercial authorization;

• account permissions; and

• applicable third-party licenses.

For example:
A public Website visitor may have fewer rights than a registered member.
A Pro Member may have earlier access to development materials than a Free Member.
A commercial licensee may receive rights not granted to ordinary members.
A publicly released open-source version may provide broader redistribution rights than a member-only development version.
Users must not assume that access to one RENBOTS product or file grants rights to unrelated products or files.
7. MEMBERSHIP IS NOT OWNERSHIP
A RENBOTS membership provides access to the benefits offered for that membership level.
Membership does not by itself transfer ownership of:

• RENBOTS intellectual property;

• BitForge Dynamics intellectual property;

• BitNip intellectual property;

• CAD designs;

• robotics designs;

• trademarks;

• software;

• firmware;

• patents;

• documentation;

• manufacturing rights; or

• commercial reproduction rights.

Digital materials are licensed according to the terms applicable to the particular material.
8. MEMBER-ACCESSIBLE SOURCE MATERIALS
Certain RENBOTS development files may be made available through Free or Pro membership before broader public release.
These materials may include editable:

• CAD;

• 3D models;

• STL files;

• STEP files;

• source files;

• documentation;

• firmware;

• software;

• diagrams; or

• other development materials.

Access to source material does not automatically mean that the material is formally open source.
Member-restricted material remains subject to the applicable Member Terms and Digital File License.
9. OPEN-SOURCE AND OPEN-HARDWARE RELEASES
RENBOTS may formally release certain versions or components under identified open-source or open-hardware licenses.
When a particular release carries such a license, that license controls the rights granted for that particular release.
A genuine open-source software license generally permits redistribution and modification according to its terms.
Accordingly, Users should distinguish between:
Member-Accessible Source Materials
and
formally licensed Open-Source or Open-Hardware Materials.
A later public release does not automatically change the licensing status of earlier or newer member-only versions.
10. VERSION-SPECIFIC RIGHTS
RENBOTS licenses may apply on a version-specific basis.
For example:
Version 0.7 may be publicly released.
Version 0.8 may remain restricted to Pro Members.
Version 1.0.0 may later become the production release.
Each version may have:

• different features;

• different documentation;

• different compatibility;

• different safety characteristics;

• different licensing; and

• different distribution rights.

Users must verify the version they possess.
11. NOT ALL RENBOTS TECHNOLOGY IS OPEN SOURCE
RENBOTS may include a combination of:

• openly licensed technology;

• member-accessible technology;

• proprietary technology;

• licensed third-party technology;

• commercial software;

• closed-source software;

• closed-source hardware;

• cloud services;

• AI systems;

• security components; and

• other technology.

Some portions of the core robotics platform may ultimately be publicly released while other portions remain proprietary.
The applicable license controls.
12. ACCEPTABLE USE
Users may use RENBOTS for lawful purposes consistent with:

• applicable licenses;

• applicable product terms;

• safety requirements;

• intellectual-property rights;

• applicable law; and

• this Agreement.

Users are encouraged to:

• build;

• experiment;

• learn;

• develop;

• research;

• create accessories;

• test;

• modify authorized materials;

• provide feedback;

• develop compatible technology; and

• contribute to the community.

13. PROHIBITED USE
Users may not use RENBOTS to:

• violate applicable law;

• intentionally circumvent applicable licensing restrictions;

• steal or misappropriate intellectual property;

• fraudulently obtain member materials;

• distribute restricted member files without authorization;

• impersonate BitNip LLC or BitForge Dynamics LLC;

• falsely represent unofficial products as official RENBOTS products;

• access another person's account without authorization;

• bypass Website security;

• intentionally introduce malicious software into RENBOTS services;

• knowingly interfere with another User's systems without authorization; or

• knowingly use RENBOTS in a manner that violates rights of another person.

14. HARDWARE USE
Users operating RENBOTS hardware are responsible for understanding the characteristics of the system they operate.
RENBOTS hardware may include:

• motors;

• servos;

• actuators;

• gearboxes;

• linkages;

• moving joints;

• wheels;

• batteries;

• electrical wiring;

• computers;

• controllers;

• cameras;

• sensors;

• networking equipment; and

• fabricated components.

Robotics systems may move unexpectedly or generate substantial forces.
Users must follow the RENBOTS Disclaimers & Safety Policy and applicable component manufacturer instructions.
15. DIY AND USER-FABRICATED HARDWARE
Users may fabricate RENBOTS hardware themselves where permitted.
User-manufactured systems may differ substantially from factory-manufactured products.
Factors affecting performance and safety may include:

• material;

• printer;

• print settings;

• machining;

• tolerances;

• assembly;

• fasteners;

• wiring;

• soldering;

• component quality;

• batteries;

• modifications;

• maintenance; and

• software configuration.

A user-fabricated RENBOTS system is the responsibility of the person or organization assembling and operating it to the extent permitted by law.
16. DEVELOPMENT HARDWARE
Development-stage RENBOTS hardware should not be treated as finalized production hardware.
Development hardware may:

• contain unresolved design issues;

• undergo revision;

• have incomplete documentation;

• require adjustment;

• use experimental components;

• require additional safety testing; or

• differ from future production versions.

Users who participate in early development accept that iteration is part of the process.
17. PRODUCTION HARDWARE
Hardware expressly identified as production hardware may be subject to:

• production specifications;

• warranty terms;

• safety documentation;

• assembly instructions;

• support terms; and

• additional product-specific requirements.

Production status does not mean that a product is suitable for every possible application.
Users remain responsible for selecting an appropriate product for their intended use.
18. USER MODIFICATIONS
RENBOTS is intentionally designed to support customization.
Users may modify authorized hardware and software subject to applicable licenses.
However, modification may change:

• structural integrity;

• electrical load;

• torque;

• stability;

• motion limits;

• battery consumption;

• thermal behavior;

• software behavior;

• safety characteristics;

• sensor performance; and

• compatibility.

Users are responsible for evaluating modifications before use.
19. ORIGINAL USER-CREATED COMPONENTS
Users may independently create compatible:

• accessories;

• attachments;

• tools;

• modules;

• software;

• brackets;

• mounts;

• enclosures;

• electronics;

• payload systems; or

• other components.

RENBOTS does not automatically claim ownership over genuinely independent User creations merely because they interface with RENBOTS.
However, Users must respect applicable RENBOTS intellectual-property rights and licenses.
20. COMPATIBILITY CLAIMS
A User may truthfully state that an independently developed product is:

• compatible with RENBOTS;

• designed for RENBOTS; or

• intended for use with RENBOTS,

provided that the representation does not imply official endorsement, certification, sponsorship, or manufacture by BitNip LLC or BitForge Dynamics LLC unless such authorization exists.
21. SOFTWARE
RENBOTS software may include:

• desktop applications;

• mobile applications;

• firmware;

• robotics software;

• control software;

• libraries;

• example code;

• plugins;

• SDKs;

• APIs;

• scripts;

• AI systems; and

• local services.

Software use may be subject to additional license terms.
Users must not assume that software is open source unless it is expressly distributed under an identified open-source license.
22. SOFTWARE UPDATES
Software may change over time.
Updates may:

• add features;

• remove features;

• change behavior;

• correct bugs;

• modify compatibility;

• improve security;

• change interfaces;

• change APIs; or

• alter hardware behavior.

Users should review applicable release information before deploying updates to important or safety-sensitive systems.
23. ARTIFICIAL INTELLIGENCE
REN may support artificial-intelligence systems.
AI functionality may include:

• language models;

• speech recognition;

• speech generation;

• computer vision;

• planning;

• automation;

• command interpretation;

• robotics control;

• memory systems; and

• third-party integrations.

Artificial-intelligence output can be wrong.
AI systems may:

• misunderstand instructions;

• provide inaccurate information;

• produce incomplete answers;

• generate incorrect commands;

• misclassify objects;

• misunderstand sensor data; or

• behave unpredictably.

Users should not treat AI-generated output as infallible.
24. AI AND PHYSICAL CONTROL
Where artificial intelligence influences physical robotics, Users must maintain appropriate safeguards.
AI should not be the sole safety system preventing dangerous motion.
Appropriate controls may include:

• hardware emergency stops;

• current limits;

• torque limits;

• speed limits;

• deterministic safety controllers;

• motion boundaries;

• mechanical stops;

• power isolation;

• human supervision;

• watchdog systems; and

• other engineering controls.

A conversational AI response is not a safety interlock.
25. LOCAL AI PROCESSING
REN may support compatible locally operated artificial-intelligence systems.
When processing occurs entirely on the User's own device and is not transmitted to RENBOTS or another service provider, BitNip LLC and BitForge Dynamics LLC do not automatically receive that content.
The User controls their local configuration.
26. THIRD-PARTY AI AND CLOUD SERVICES
Users may choose to connect REN or RENBOTS software to third-party:

• AI providers;

• APIs;

• speech services;

• cloud services;

• storage services;

• computer-vision providers;

• automation systems;

• web services; or

• other network services.

Information intentionally transmitted to such a provider may be subject to that provider's:

• privacy policy;

• terms of use;

• retention policies;

• security practices;

• account settings; and

• technical systems.

BitNip LLC and BitForge Dynamics LLC do not control independent third-party providers.
27. PRIVACY
Use of RENBOTS.com is subject to the:
RENBOTS Website Privacy Policy
and
RENBOTS Cookie Policy.
Creating a Website account, purchasing a product, or becoming a member does not by itself give BitNip LLC or BitForge Dynamics LLC automatic access to locally stored:

• microphone recordings;

• camera feeds;

• prompts;

• conversations;

• files;

• sensor information;

• locally processed AI activity; or

• private device telemetry.

Any future optional cloud feature that transmits device information to RENBOTS should be disclosed according to applicable privacy requirements.
28. USER DATA RESPONSIBILITY
Users are responsible for deciding what information they provide to:

• REN;

• local AI systems;

• external AI providers;

• cloud services;

• third-party software;

• APIs; and

• integrations.

Users should not transmit information they are not authorized to disclose.
This is particularly important for:

• confidential business information;

• regulated information;

• third-party personal information;

• trade secrets;

• export-controlled information;

• classified information;

• protected research information; or

• other sensitive material.

29. CAMERAS, MICROPHONES, AND SENSORS
RENBOTS hardware may include cameras, microphones, or sensors.
Users are responsible for complying with applicable:

• privacy laws;

• recording laws;

• surveillance laws;

• workplace policies;

• consent requirements; and

• property rules

when operating those devices.
Ownership of a robot does not automatically provide permission to record another person.
30. ACCOUNT RESPONSIBILITY
Registered Users are responsible for maintaining reasonable security over their account credentials.
Users should not:

• share credentials to circumvent access restrictions;

• allow unauthorized use;

• attempt to access another User's account;

• resell membership credentials; or

• knowingly compromise Website security.

Account access may be restricted in cases of fraud, security threats, or material violations of applicable terms.
31. THIRD-PARTY COMPONENTS
RENBOTS may interact with or incorporate components manufactured by other companies.
Third-party manufacturers are responsible for their own:

• specifications;

• warranties;

• safety instructions;

• product representations;

• support; and

• independent legal obligations.

A reference to a third-party component does not necessarily constitute a guarantee that it will remain available indefinitely.
32. THIRD-PARTY SOFTWARE LICENSES
RENBOTS may incorporate third-party software distributed under independent licenses.
Users must comply with applicable third-party licenses.
This Agreement does not revoke rights independently granted through a third-party open-source license.
Where third-party licensing grants broader rights than a RENBOTS general policy, those independently granted rights remain effective for the applicable third-party material.
33. INTELLECTUAL PROPERTY
Except where otherwise licensed, applicable RENBOTS technology and materials may be protected by:

• copyright;

• trademark;

• patent;

• patent application;

• trade dress;

• contract;

• trade-secret law; and

• other intellectual-property rights.

Rights may belong to:

• BitForge Dynamics LLC;

• BitNip LLC;

• third-party licensors; or

• other applicable owners.

Access does not equal ownership.
34. TRADEMARKS AND BRANDING
RENBOTS, REN, applicable logos, graphics, product names, and other brand identifiers may constitute protected marks or branding.
Users may truthfully discuss or identify RENBOTS products.
Users may not falsely claim:

• official partnership;

• official certification;

• official distribution status;

• official manufacture;

• endorsement; or

• authorization

without written permission.
35. USER CONTENT
Users may create or submit:

• photographs;

• videos;

• comments;

• build logs;

• reviews;

• feedback;

• bug reports;

• suggestions;

• designs; or

• other community content.

Users retain ownership of independently created content subject to rights contained in any material incorporated into that content.
Users should not submit material they do not have permission to provide.
36. FEEDBACK
RENBOTS encourages Users to submit development feedback.
By voluntarily submitting ordinary:

• suggestions;

• bug reports;

• compatibility information;

• measurements;

• testing results;

• comments;

• usability observations; or

• improvement ideas,

the User grants BitNip LLC and BitForge Dynamics LLC a non-exclusive, worldwide, perpetual, royalty-free right to use that feedback for purposes including:

• research;

• development;

• documentation;

• testing;

• manufacturing;

• product improvement;

• support; and

• commercialization.

This does not transfer ownership of unrelated pre-existing intellectual property belonging to the User.
Users should not submit confidential inventions or trade secrets through ordinary feedback channels unless a separate written confidentiality agreement exists.
37. SAFETY
All Users interacting with RENBOTS hardware must follow applicable safety practices.
Robotics risks may include:

• electrical shock;

• battery fire;

• burns;

• pinch points;

• crushing;

• impact;

• entanglement;

• cuts;

• falling equipment;

• unexpected movement;

• structural failure;

• equipment damage; and

• other hazards.

The RENBOTS Disclaimers & Safety Policy provides additional requirements.
38. EMERGENCY STOPS AND SAFETY CONTROLS
Robotics systems capable of dangerous movement should use safety controls appropriate to their application.
Where appropriate, these may include:

• emergency stops;

• physical power disconnects;

• motor disable systems;

• torque limits;

• current limits;

• software watchdogs;

• motion boundaries; and

• supervisory controls.

Safety mechanisms should be designed so that failure of an AI model does not automatically eliminate critical protection.
39. NO USE AS A SOLE SAFETY-CRITICAL SYSTEM
Unless expressly certified for a particular application, RENBOTS development and DIY systems should not serve as the sole safety mechanism for applications in which failure could reasonably result in death, serious injury, or substantial property damage.
Examples may include:

• life support;

• medical treatment;

• human transportation;

• industrial safety;

• emergency shutdown;

• critical infrastructure;

• hazardous equipment; or

• similar safety-critical systems.

40. CHILDREN AND UNTRAINED USERS
RENBOTS DIY robotics systems are not toys.
Users should ensure appropriate supervision where children or inexperienced persons are present.
Children should not independently:

• assemble;

• wire;

• energize;

• charge;

• modify;

• repair; or

• operate

robotics systems involving potentially hazardous components.
41. USER RESPONSIBILITY
Users are responsible for decisions within their control concerning:

• assembly;

• fabrication;

• wiring;

• modifications;

• component selection;

• software configuration;

• API configuration;

• network configuration;

• safety controls;

• operation;

• maintenance; and

• use environment.

User responsibility does not eliminate obligations legally imposed upon BitNip LLC, BitForge Dynamics LLC, a manufacturer, distributor, or another party where applicable law does not permit those obligations to be waived.
42. DOCUMENTATION
Documentation is intended to assist Users.
However, documentation may occasionally:

• contain errors;

• become outdated;

• apply only to a particular version;

• contain incomplete information;

• rely on third-party specifications; or

• require engineering judgment.

Users should verify critical specifications before energizing or operating a system.
43. COMMUNITY INFORMATION
Information supplied by another RENBOTS User should not automatically be considered official RENBOTS documentation.
Community information may be:

• incorrect;

• incomplete;

• outdated;

• unsafe;

• applicable only to another revision; or

• based on a different configuration.

Users should verify community instructions before relying upon them.
44. NO PROFESSIONAL RELATIONSHIP
Ordinary use of RENBOTS does not create an:

• employer-employee relationship;

• partnership;

• joint venture;

• fiduciary relationship;

• franchise;

• professional engineering relationship;

• agency relationship; or

• investment relationship

between a User and BitNip LLC or BitForge Dynamics LLC.
Separate written agreements may create different relationships where expressly stated.
45. COMMERCIAL USE
Commercial rights depend on the applicable license.
Certain publicly released materials may permit commercial use.
Certain Member Files may prohibit commercial reproduction.
Certain proprietary products may require separate licensing.
Users seeking commercial manufacture, integration, distribution, or licensing should verify the applicable license or contact RENBOTS through:
www.RENBOTS.com/contact
46. COMMERCIAL INTEGRATORS
A person or company integrating RENBOTS into another system is responsible for evaluating the integrated product as a whole.
Integration may create new:

• electrical risks;

• software risks;

• mechanical risks;

• security risks;

• regulatory requirements;

• privacy requirements;

• certification requirements; or

• safety requirements.

Authorization to use one RENBOTS component does not automatically constitute certification of an integrated commercial product.
47. ORGANIZATIONAL USERS
If a person uses RENBOTS on behalf of a:

• company;

• university;

• school;

• laboratory;

• nonprofit;

• government organization; or

• other legal entity,

that person represents that they have appropriate authority to use RENBOTS on behalf of that organization where required.
Organizations are responsible for their own internal:

• access policies;

• safety procedures;

• account controls;

• data policies;

• employee permissions; and

• regulatory requirements.

48. EXPORT, SANCTIONS, AND REGULATED USE
Users are responsible for complying with applicable laws concerning:

• exports;

• imports;

• economic sanctions;

• controlled technologies;

• restricted parties;

• restricted destinations; and

• regulated technical information.

Availability through a public Website does not itself establish that every technology may lawfully be exported or used in every jurisdiction.
49. SECURITY
Users are responsible for reasonable security of systems they control.
Users should consider:

• strong authentication;

• secure networking;

• appropriate permissions;

• software updates;

• physical security;

• API-key protection;

• encryption where appropriate;

• backup procedures; and

• limiting unnecessary network exposure.

No connected robotics platform can be guaranteed to be completely secure.
50. CREDENTIALS AND API KEYS
Users should not publicly expose:

• API keys;

• passwords;

• authentication tokens;

• private cryptographic keys;

• cloud credentials; or

• other security credentials.

Users connecting third-party services are responsible for securing those credentials.
51. SERVICE AVAILABILITY
RENBOTS does not guarantee uninterrupted availability of:

• RENBOTS.com;

• memberships;

• downloads;

• online services;

• third-party APIs;

• cloud AI services;

• payment providers; or

• external integrations.

Systems may become temporarily unavailable due to maintenance, security events, provider outages, updates, or circumstances outside our reasonable control.
52. PRODUCT AVAILABILITY
Products, components, files, designs, memberships, and services may change.
RENBOTS may:

• introduce products;

• discontinue products;

• revise products;

• archive files;

• replace components;

• update software;

• alter membership benefits; or

• change compatibility.

Existing contractual and consumer obligations remain subject to applicable law.
53. PREORDERS
Preorder products may remain under development.
A preorder may involve:

• final engineering;

• component sourcing;

• manufacturing preparation;

• tooling;

• documentation;

• packaging;

• quality control; or

• production scheduling.

Preorder-specific terms displayed during purchase apply to that transaction.
Estimated dates are estimates unless expressly guaranteed.
54. WARRANTIES
Applicable warranties are governed by product-specific warranty terms.
Where RENBOTS offers a written consumer warranty, additional federal and state requirements may apply, including requirements concerning pre-sale availability and implied warranties.
Nothing in this Agreement eliminates:

• an applicable express warranty;

• mandatory implied warranties;

• statutory consumer rights; or

• remedies that cannot legally be waived.

55. DEVELOPMENT MATERIALS
Unless covered by a separate written warranty, development files, experimental designs, community materials, prototypes, and similar development resources may be provided on an:
“as available”
and, where legally permitted,
“as is”
basis.
Such terminology does not eliminate responsibilities that applicable law does not permit a provider to waive.
56. LIMITATION OF LIABILITY
To the maximum extent permitted by applicable law, BitNip LLC and BitForge Dynamics LLC will not be responsible for indirect, incidental, special, exemplary, punitive, or consequential damages arising solely from use of Website materials, development materials, or unauthorized User modifications.
Product-specific agreements may contain additional terms.
Nothing in this Agreement excludes liability that applicable law prohibits from being excluded.
57. ASSUMPTION OF RISK
Users acknowledge that robotics, electrical systems, batteries, fabrication, software development, and experimental engineering involve inherent risks.
Users voluntarily choosing to perform such activities accept responsibility for risks reasonably associated with activities under their control.
This clause does not waive rights or liability that applicable law does not permit to be waived.
58. INDEMNIFICATION
To the extent permitted by applicable law, Users agree to be responsible for claims or losses resulting from their:

• unlawful use of RENBOTS;

• intentional violation of another person's rights;

• unauthorized commercial reproduction;

• unauthorized distribution of protected materials;

• malicious modification;

• fraudulent conduct; or

• material violation of this Agreement.

This section does not require a consumer to indemnify BitNip LLC or BitForge Dynamics LLC for conduct for which such indemnification would be prohibited by law.
59. SUSPENSION AND TERMINATION
RENBOTS may suspend access to Website or membership services when reasonably necessary because of:

• fraud;

• security threats;

• unlawful use;

• unauthorized redistribution;

• account abuse;

• payment abuse;

• malicious activity; or

• material violations of applicable agreements.

Where appropriate and reasonably possible, RENBOTS may provide notice.
Termination does not erase licensing restrictions applying to previously obtained restricted material.
60. SAFETY REMOVAL OR RECALL OF MATERIALS
RENBOTS may withdraw or replace:

• files;

• documentation;

• firmware;

• software;

• products; or

• instructions

when a significant technical, safety, security, or legal concern is identified.
Users should follow applicable safety notices, product corrections, recalls, or updated instructions.
61. REPORTING SAFETY OR SECURITY ISSUES
Users are encouraged to report potential:

• safety defects;

• dangerous hardware behavior;

• battery problems;

• electrical faults;

• security vulnerabilities;

• documentation errors;

• software defects; or

• other significant issues.

Reports should be submitted through:
www.RENBOTS.com/contact
Safety reports should be identified as:
PRODUCT SAFETY REPORT
Security issues should be identified as:
SECURITY REPORT
Users should not intentionally recreate a hazardous failure merely to document it.
62. CHANGES TO THE RENBOTS ECOSYSTEM
RENBOTS is expected to evolve.
Future versions may differ significantly from current versions.
The ecosystem may gain or lose:

• hardware modules;

• software systems;

• integrations;

• AI systems;

• services;

• APIs;

• membership benefits;

• compatibility;

• licensing models; or

• other capabilities.

No User should assume that an experimental feature will remain permanently available.
63. CHANGES TO THIS AGREEMENT
This Agreement may be updated to reflect:

• new products;

• new software;

• licensing changes;

• safety requirements;

• legal requirements;

• Website changes;

• privacy changes;

• membership changes; or

• development of the RENBOTS ecosystem.

The Last Updated date at the beginning of this Agreement identifies the current version.
Where appropriate, material changes may be communicated through:

• RENBOTS.com;

• member accounts;

• email;

• product documentation;

• application notices; or

• another reasonable method.

64. SEVERABILITY
If any provision of this Agreement is found invalid, unlawful, or unenforceable, the remaining provisions remain effective to the fullest extent permitted by applicable law.
An invalid provision should be limited or interpreted only to the extent necessary to make it enforceable where legally permissible.
65. NO WAIVER
Failure by BitNip LLC or BitForge Dynamics LLC to enforce a provision on one occasion does not permanently waive that provision or another right.
66. GOVERNING LAW
This Agreement will be governed according to the governing-law provision established for the RENBOTS contractual framework, subject to mandatory laws applicable to individual Users.
[INSERT FINAL GOVERNING STATE, VENUE, AND DISPUTE LANGUAGE AFTER LEGAL REVIEW]
Nothing in this section deprives consumers of rights that cannot legally be waived.
67. ENTIRE RENBOTS AGREEMENT FRAMEWORK
This User Agreement, together with all applicable incorporated policies, licenses, purchase terms, and product-specific agreements, forms the contractual framework governing a User's interaction with RENBOTS.
The exact documents applicable to a User depend on what the User does.
For example:
A Website visitor may primarily be subject to:

• Website Terms;

• Privacy Policy; and

• Cookie Policy.

A Member may additionally be subject to:

• Member Terms; and

• applicable Digital File Licenses.

A DIY builder may additionally be subject to:

• Disclaimers;

• Safety Policy; and

• applicable hardware documentation.

A software User may additionally be subject to:

• software licenses;

• API terms;

• SDK terms; or

• third-party licenses.

A purchaser may additionally be subject to:

• purchase terms;

• warranty terms;

• shipping terms; and

• product-specific terms.

A commercial licensee may additionally be subject to:

• a separately executed commercial agreement.

68. A SIMPLE RULE FOR USERS
The RENBOTS ecosystem is intentionally designed to encourage building, learning, experimentation, development, and innovation.
The general expectation is straightforward:
Use the system responsibly.
Respect the license attached to the version you are using.
Do not redistribute restricted Member Files merely because you were allowed to download them.
Do not represent unofficial products as official RENBOTS products.
Do not assume experimental hardware is finished production hardware.
Do not assume AI output is always correct.
Use appropriate safety controls when operating physical robotics.
Respect other people's privacy, property, intellectual property, and safety.
And when you create something genuinely new:
build it, test it, document it, and show people what you made.
That kind of experimentation is a fundamental part of what RENBOTS is intended to enable.
69. CONTACT
Questions concerning:

• this User Agreement;

• RENBOTS use;

• memberships;

• licensing;

• software;

• hardware;

• development materials;

• commercial use;

• privacy;

• safety;

• intellectual property;

• support; or

• other RENBOTS matters

should be submitted through:
www.RENBOTS.com/contact
RENBOTS.com is operated and published by BitNip LLC, an authorized distributor and publisher of applicable hardware, software, technology, designs, and related RENBOTS materials developed or licensed by BitForge Dynamics LLC.
BitNip LLC and BitForge Dynamics LLC are separate legal entities.