Terms of Service

These Terms of Service constitute a legally binding agreement between [Company legal entity], registered at [Registered address] (“RoboTrace”, “we”, “us”, “our”), and you (“you”, “your”) governing your access to and use of the RoboTrace website, web portal, admin console, REST and ingest APIs, the robotrace Python SDK, command-line tools, dashboards, and any related features (collectively, the “Service”). By creating an account or using the Service, you agree to these Terms. If you do not agree, you must not use the Service. If you are using the Service on behalf of an organization, you represent that you have authority to bind that organization to these Terms.

1. What the Service does

RoboTrace provides observability and evaluation tooling for teams training and operating AI-powered robots. The Service lets you log episodes (synchronized video, sensor streams, action vectors, and metadata) from real or simulated robots, store and version those episodes, replay them frame-by-frame, and re-roll new policy versions against historical observations to measure regressions. Outputs of the Service — including evaluation reports, re-roll renders, scrubber states, and dashboards — are analytical artifacts derived from the inputs you provide. They are not safety certifications, compliance approvals, or guarantees that any policy is fit for deployment on a real robot in any environment. You are solely responsible for any decision to deploy a policy or robot in the physical world.

2. Eligibility and access

You must be at least 18 years old and able to enter into a binding contract to use the Service. The Service is currently invite-only and offered to a limited group of pilot teams. Access is granted through the access request flow and an admin approval. We may suspend or terminate access at any time, with or without cause, in our reasonable discretion, including to protect the Service, our users, or third parties.

3. Your account and API keys

You are responsible for the accuracy of the information you provide, for keeping your sign-in credentials and API keys confidential, and for all activity under your account, organization, or project. SDK ingest endpoints authenticate solely on the API key, so anyone who obtains a key can write episodes against your project until the key is rotated. Notify us promptly at security@robotrace.dev if you suspect any unauthorized use. You are responsible for rotating compromised keys, revoking access for departing teammates, and for scoping API keys to the minimum projects required.

4. Your data — episodes, datasets, and policies

“User Content” means anything you upload, submit, transmit, or generate through the Service — including episodes (video frames, sensor logs, action vectors, joint torques, action probability distributions, observation snapshots), policy weights and checkpoints you choose to attach, evaluation prompts, dataset manifests, project configuration, and metadata such as policy_version, env_version, git_sha, and seed.

You retain all rights you have in your User Content. You grant RoboTrace a worldwide, non-exclusive, royalty-free licence to host, store, process, transmit, encode, transcode, and display the User Content, and to compute aggregate or derivative metrics from it (loss curves, success rates, regression deltas, sensor health summaries), solely to the extent necessary to operate, secure, and improve the Service for you and to comply with law. We do not use your User Content — including episodes, sensor streams, video frames, or policy weights — to train publicly available or third-party general-purpose AI models for unrelated products, and we do not sell your User Content. You warrant that:

• You own or have all necessary rights, licences, and permissions to submit the User Content and to grant the licences above;
• The User Content does not infringe any third party’s intellectual property, trade secret, privacy, publicity, or other rights;
• The User Content does not contain personal data of identifiable third parties whose recording you are not legally entitled to submit (e.g. bystanders captured by a robot’s camera in a jurisdiction where their consent is required);
• You will not upload classified, export-controlled, or weapons- related materials, nor materials whose disclosure would violate a contract with your customers or employer.

5. Episode storage, retention, and signed URLs

Large binary objects (video files, sensor blobs, action arrays) are stored in object storage (Cloudflare R2 or, where you have configured it, your own S3-compatible bucket). The Service issues time-limited signed URLs to your authorized users and may issue signed PUT URLs to the SDK so that bytes do not pass through the RoboTrace origin. You are responsible for the contents of bring-your-own buckets, including their access controls, encryption configuration, region, retention, and any associated cloud costs.

Free-tier projects have a default retention window for episodes; paid plans, when available, may extend it. We will describe applicable retention windows in-product and in your plan’s documentation. You are responsible for exporting any episode you wish to retain beyond the retention window. Deletion of an episode deletes its underlying object(s) within a reasonable period subject to backups and legal retention obligations.

6. Re-rolls, evals, and replays

The Service may execute re-rolls — running a specified policy version against a historical episode’s observations and producing a new action sequence and evaluation report. Re-rolls are simulations against logged observations; they do not place a robot in the physical world. Pass / fail / regression labels are computed from the metrics and acceptance criteria you supply. They are useful proxies but are not guarantees that a policy will behave the same way on a real robot, in a different environment, or under out-of-distribution conditions. You are solely responsible for any decision to deploy a policy on hardware based on a RoboTrace eval or re-roll.

7. The Python SDK and the SDK contract

The Service includes a Python SDK published as robotrace on PyPI. The SDK is licensed under the licence shipped with the package and may include components licensed by third parties. Your use of the SDK is governed by these Terms in addition to that package licence and any provider terms it references. We treat the signature of robotrace.log_episode and other public SDK entry points as a stable contract; we will bump major versions for breaking changes and ship deprecation warnings for at least one minor version where reasonable. You are responsible for pinning the SDK version your training or robot stack depends on.

The Service supports a defined set of robot stacks (currently ROS 2 Humble and Jazzy, LeRobot datasets, and raw NumPy episodes). ROS 1 is out of scope. We may add or remove supported integrations; we will give reasonable notice for removals where practical.

8. Reproducibility metadata

The Service stores reproducibility metadata you attach to each episode (including policy_version, env_version, git_sha, seed, timestamps, and SDK version). You are responsible for the accuracy of those values. Misreporting them may make later evaluations or re-rolls misleading. You agree not to deliberately misreport reproducibility metadata in a way that could materially mislead another organization’s decision to deploy a policy.

9. Acceptable use

You agree that you will not, and will not permit anyone to:

• Use the Service to log, train, or evaluate policies for systems designed primarily as weapons or to autonomously target, harm, or kill people;
• Upload User Content that is unlawful, that you do not have rights to, or that contains personal data of third parties without a lawful basis;
• Reverse engineer, decompile, scrape, or attempt to derive the source code, model weights, internal prompts, or training data of the Service (other than the open-source SDK as permitted by its licence);
• Use the Service to interfere with another customer’s data, escape tenant isolation, or attempt to access data your account is not entitled to;
• Send malware, automated scrapers, denial-of-service traffic, or excessive ingest volumes designed to exhaust the Service’s capacity, beyond your plan’s documented limits;
• Use the Service in violation of applicable export, sanctions, or dual-use laws, or to provide the Service to embargoed parties;
• Resell, white-label, or sublicense the Service to third parties without our prior written agreement.

We may suspend or terminate accounts, refuse ingest, or remove content that we reasonably believe violates these Terms or applicable law.

10. Plans, fees, and the invite-only pilot

The Service is currently offered as an invite-only pilot and is provided at no charge for every tier during the pilot. We do not currently bill through a payment processor. If we introduce paid plans, we will give clear in-product and email notice of pricing and obtain your explicit agreement before charging you. Any cloud costs you incur on your own infrastructure (for example, on a bring-your-own R2 / S3 bucket) are your responsibility.

11. Third-party infrastructure and subprocessors

The Service relies on third-party infrastructure to operate, including hosting (Vercel), database and authentication (Supabase), and object storage (Cloudflare R2 or, where you opt in, your own S3-compatible bucket). Your use of the Service must comply with these Terms and with any provider restrictions or acceptable-use rules we or the provider publish. If a provider’s terms or policies change, we may need to change or suspend a feature. See our Privacy Policy (when published) for the current list of subprocessors and any international transfer mechanisms that apply.

12. Security and incident response

We take reasonable technical and organizational measures to protect the Service, including encrypted transport, isolated tenant access through Row-Level Security, scoped API keys, audit logging of admin-sensitive actions, and regular dependency hygiene. No service is perfectly secure. If we discover a security incident affecting your User Content, we will notify you without undue delay in accordance with applicable law and contract. You will report suspected vulnerabilities responsibly to security@robotrace.dev and will not exploit them beyond the minimum needed to demonstrate the issue.

13. Confidentiality

Each party may receive non-public information of the other in connection with the Service (“Confidential Information”). Confidential Information includes, without limitation, your User Content, policy weights, training datasets, eval criteria, and non-public roadmaps; and our non-public pricing, security documentation, and product designs. Each party will (a) protect the other’s Confidential Information using at least the same degree of care it uses for its own confidential information of like importance, and in any case not less than a reasonable standard of care; (b) use it only as needed to perform under these Terms; and (c) not disclose it except to employees, contractors, and advisers bound by similar confidentiality obligations. Disclosures required by law are permitted, with prompt notice where lawful.

14. Our intellectual property

The Service, including the website, web portal, admin console, web APIs, dashboards, models, prompts, training pipelines, brand assets, and documentation (excluding User Content and the open-source SDK), is owned by RoboTrace or our licensors and is protected by intellectual property laws. We grant you a limited, non-exclusive, non-transferable right to use the Service for the purposes described in these Terms. No other rights or licences are granted. No ownership of our name, brand, or non-public model weights is transferred to you.

15. Feedback

If you choose to send us feedback, suggestions, or feature requests, you grant us a perpetual, worldwide, royalty-free licence to use that feedback to operate and improve the Service, without obligation to you. You are not required to provide feedback.

16. Privacy

Our handling of personal data — including any personal data incidentally captured in episode video, audio, or sensor logs — is described in our Privacy Policy (when published). By using the Service you acknowledge that you are responsible for any personal data you submit and for any consents required from your end users or bystanders captured by the robot. Processing is limited to the purposes described in these Terms and the Privacy Policy, subject to your consents and applicable law.

17. Pilot status; changes to the Service

The Service is currently offered as an invite-only pilot. Features may change, be added, or be removed without notice; uptime, ingest latency, eval throughput, and re-roll turnaround times are not guaranteed during the pilot. We may modify, suspend, or discontinue the Service (or parts of it) at any time. Where we make material changes that adversely affect you, we will use reasonable efforts to give you advance notice and a path to export your User Content.

18. Termination

You may close your account or organization at any time by writing to support@robotrace.dev. We may suspend or terminate your access for violation of these Terms, for legal, security, or abuse reasons, or where the Service is being discontinued. On termination, the licences granted to you cease and we will delete your account data in accordance with our Privacy Policy and any applicable retention obligations. Provisions of these Terms that by their nature should continue (including rights and obligations regarding intellectual property, confidentiality, disclaimers, limitation of liability, indemnity, governing law, and dispute resolution) will survive termination.

19. Disclaimers

To the maximum extent permitted by applicable law, the Service and all outputs, evals, re-rolls, dashboards, and SDK responses are provided “as is” and “as available” without warranties of any kind, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, accuracy, non-infringement, or title, or that the Service will be uninterrupted, error-free, or secure. We do not warrant that any eval, re-roll, or metric is a reliable predictor of real-world robot behavior.

Some jurisdictions do not allow certain disclaimers; in such jurisdictions, our liability is limited to the maximum extent allowed. Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under applicable mandatory law.

20. Limitation of liability; exclusive remedy

To the maximum extent permitted by applicable law, in no event will RoboTrace (or our directors, officers, employees, contractors, or licensors) be liable for any indirect, incidental, special, consequential, punitive, or exemplary damages, or for any loss of profits, revenue, data, goodwill, or business opportunity, or for any loss of or damage to reputation, or for any property damage, personal injury, or harm caused by a physical robot, arising out of or related to your use of or inability to use the Service or any output, even if we have been advised of the possibility of such damages, and even if a limited remedy fails of its essential purpose.

To the maximum extent permitted by applicable law, our aggregateliability for all claims arising out of or related to the Service in any twelve (12) month period will not exceed the greater of (a) the fees you paid us in that period or (b) one hundred US dollars (USD $100). The pilot is currently provided at no charge, so for many pilot users this cap will be USD $100. This liability cap is an essential basis of the bargain. Your sole and exclusive remedy for dissatisfaction with the Service is to stop using the Service and close your account, subject to any non-waivable rights you have under law.

21. Your indemnity to us

You will defend, indemnify, and hold harmless RoboTrace, its affiliates, and its directors, officers, employees, and agents from and against any and all third-party claims, actions, demands, damages, losses, liabilities, costs, and expenses (including reasonable attorneys’ fees and court costs) arising out of or related to: (a) your User Content, including any episode, policy, or sensor log; (b) your breach of these Terms or applicable law; (c) your decision to deploy any policy on a physical robot, including any property damage or personal injury that follows; (d) any claim that your User Content or use of the Service infringes or violates any third party’s intellectual property, trade secret, privacy, publicity, or other rights. We may assume exclusive defense and control of any matter subject to indemnification, at your expense, and you will cooperate fully.

22. Time limit to bring claims

To the maximum extent permitted by applicable law, any claim or cause of action you may have arising out of or related to the Service or these Terms must be filed within one (1) year after the claim arose, or be forever waived and barred, unless a longer period is required by mandatory law in your jurisdiction.

23. Notices

We will give you notices by email to the address associated with your account, by posting in the web portal, or by updating this page. You will give us legal notices (including for disputes) by emailing legal@robotrace.dev with “Legal Notice” in the subject line, except where a statute requires another method.

24. Governing law, jurisdiction, and informal resolution

24.1 Governing law. These Terms are governed by the laws of [Governing jurisdiction / state / country], without regard to its conflict-of-laws principles, subject to the subsections below.

24.2 EEA, UK, and Switzerland — consumers. If you are a consumer habitually resident in the European Economic Area, the United Kingdom, or Switzerland, you benefit from any mandatory rights under the laws of your country of residence. Nothing in these Terms (including the limitation of liability, governing law, or dispute forum clauses) is intended to deprive you of those rights. You may also bring legal proceedings in the courts of your place of residence.

24.3 Informal resolution. Before filing a formal claim, the party seeking relief will send a written description of the dispute to legal@robotrace.dev and the parties will attempt in good faith to resolve the dispute for at least thirty (30) days (unless urgent injunctive relief is needed to prevent irreparable harm to intellectual property or security).

24.4 Exclusive jurisdiction (non-EEA/UK/CH or non-consumer). Subject to Section 24.2, the courts of [Governing jurisdiction — courts and venue] will have exclusive jurisdiction over any disputes arising out of or relating to these Terms or the Service, and you submit to the personal jurisdiction of those courts, except that RoboTrace may bring suit for equitable or injunctive relief in any court of competent jurisdiction to protect our intellectual property, confidential information, or the security of the Service.

24.5 United States — class action and jury (where valid). If you are not a consumer in the EEA, UK, or Switzerland and you are resident in the United States, to the maximum extent permitted by law: (a) you and RoboTrace waive the right to a jury trial in any proceedings arising out of or relating to the Service or these Terms; and (b) you and RoboTrace agree that each may bring claims only in an individual capacity, not as a plaintiff or class member in any purported class, consolidated, or representative action, unless we both agree otherwise in writing. If a court finds this subsection unenforceable as to a particular claim, that claim may proceed, but the remainder of these Terms remains in effect.

25. Force majeure

RoboTrace is not liable for any delay or failure to perform resulting from events beyond our reasonable control, including natural disasters, war, terrorism, labor disputes, utility failures, supply chain issues, pandemic, or failures of the internet, hosting, or third-party infrastructure (including cloud, storage, or AI providers, within reason).

26. General

These Terms, together with our Privacy Policy and any other terms we present in-product, constitute the entire agreement between you and RoboTrace regarding the Service and supersede prior understandings on the same subject. You agree that the electronic version of these Terms and any records we send by email or through the Service have the same effect as signed paper documents, to the extent allowed by law. If any provision is held unenforceable, the remaining provisions remain in effect, and the unenforceable provision is modified to the minimum extent needed to be enforceable. Our failure to enforce a provision is not a waiver. You may not assign these Terms without our prior written consent; we may assign them in connection with a merger, sale of assets, or reorganization, with notice where required. There are no third-party beneficiaries to these Terms except that our affiliates may enforce rights that benefit us.

We may update these Terms from time to time. Material changes will be communicated by email or in-product notice at least thirty (30) days before they take effect, unless a shorter period is required by law. Your continued use of the Service after the effective date constitutes acceptance of the updated Terms. If you do not agree, you must stop using the Service and close your account.