Dimensional App Review Guidelines

Effective as of September 1, 2026

These App Review Guidelines (these “Guidelines”) form part of the Dimensional Developer Terms and apply to every App submitted to or distributed through the Dimensional Platform. Capitalized terms have the meanings given in the Developer Terms.

1. Review Process

1.1 Developer submits each App and each update through the Platform with: a description of what the App does; the Permissions it requests and why each is needed; what Robot Data leaves the robot, where it goes, and for how long it is kept; any server-side components and their location; the DimOS versions supported; and test credentials or instructions sufficient for Dimensional to exercise all functionality.

1.2 Dimensional reviews for compliance with these Guidelines and the Data Access Policy. Review may include static analysis, running the App on test robots, inspecting network traffic, and verifying Permission use. Dimensional may ask questions or request changes, and the review clock pauses until Developer responds.

1.3 Target turnaround: five (5) business days for a new App; three (3) business days for an update; one (1) business day for an update that changes no Permission, data flow, or robot-control behavior. These are targets, not commitments.

1.4 An update that adds or broadens a Permission, changes where Robot Data is sent or how long it is kept, or changes robot-control behavior is reviewed as a new submission. A fix for a Safety Issue may be released on notice to Dimensional and is reviewed after release; if it fails review, Dimensional may suspend it.

1.5 Dimensional will give reasons for a rejection in writing and will consider a resubmission that addresses them. Developer may request a second review of a rejection by a different reviewer. Dimensional will not withhold approval in bad faith.

1.6 An Official Supported App may not download or execute code, models, or configuration that change its Permissions, data flows, or robot-control behavior from what was reviewed, other than through an update submitted under this Section. Server-side model updates that do not change Permissions, data flows, or the App’s declared control behavior are not updates for this purpose.

2. Safety

2.1 The App must operate within the Safety Requirements at all times and must not bypass, disable, or interfere with any DimOS or Platform safety control, including velocity, acceleration, workspace, force, and emergency-stop limits.

2.2 The App must use only the documented DimOS and Platform interfaces, and must not call internal or undocumented interfaces. The App must send robot-control commands only through the interfaces DimOS provides and at the rates and formats those interfaces specify. The App must not write to firmware, actuator controllers, or safety-rated components directly.

2.3 The App must behave safely when it loses connectivity to any server-side component, including by stopping or holding the robot in a safe state. An App that depends on a remote model must declare its fallback behavior.

2.4 Any functionality that moves a robot autonomously must be disclosed in the submission and must be capable of being interrupted by the operator through the Platform at any time.

2.5 Developer must report Safety Issues and respond within the times in Section 8 of the Developer Terms. An App with an unresolved Safety Issue will be suspended.

3. Permissions and Sensor Access

3.1 The App must declare every Permission it uses. The App may access a Robot Data source only after the Customer has granted the corresponding Permission through the Platform and only while that Permission is granted.

3.2 The App must request only the Permissions needed for the functionality it provides to the Customer. Dimensional may reject an App whose Permissions exceed its stated functionality.

3.3 The App may access camera, microphone, and other sensor data only during active use that the Customer has initiated, such as running a task, teleoperating, or recording a demonstration. The App must not capture sensor data in the background, while idle, or when the operator would not reasonably expect it.

3.4 Any recording or capture mode must be explicit: the operator turns it on, both the App and the Platform interface show that it is on, and it ends when the operator turns it off or the session ends. The App may not record continuously by default.

3.5 Where an App processes audio, it must disclose that in the submission and in the Customer-facing description. Audio capture requires its own Permission.

4. Data Leaving the Robot

4.1 The submission must state what Robot Data the App transmits off the robot, to which endpoints, for what purpose, and for how long it is retained. The App may transmit only what it declares.

4.2 The App must process Robot Data on the robot where that is feasible for its functionality. Transmitting full sensor streams to a remote endpoint is permitted only where the App’s core functionality requires it (for example, remote inference) and the submission says so.

4.3 The App must not transmit Robot Data to any endpoint other than those declared, and must not relay Robot Data to third parties except subprocessors disclosed under the Data Access Policy.

4.4 Dimensional may inspect the App’s network traffic during review and in production to verify compliance with the declared data flows.

5. Compatibility and Updates

5.1 The App must declare the DimOS versions and robot platforms it supports and must not be listed for robots it has not been tested on.

5.2 Developer must give Dimensional ten (10) business days’ notice of any update that materially changes the App’s functionality, robot-control behavior, or data processing, and must test it on Dimensional’s test robots or its own Dimensional Robots before submission.

5.3 The App must remain compatible with each new generally available DimOS and Platform release within the window in Section 8 of the Developer Terms.

6. Metering and Identity

6.1 The App must authenticate every request from a Dimensional Robot against a valid Robot Identity and must not serve requests that lack one.

6.2 The App must not attempt to identify, fingerprint, or track robots or Customers outside the Robot Identity mechanism, and must not circumvent or degrade metering.

7. Content and Conduct

7.1 The App must not contain malicious code, undisclosed data collection, or functionality hidden from review. The App’s listing must accurately describe what it does and what data it uses.

7.2 The App must not impersonate Dimensional, DimOS, or another developer, and must not use Dimensional’s marks other than as Section 12 of the Developer Terms permits.

7.3 The App must not be used, and must not enable Customers, to violate Applicable Law, including surveillance of individuals without lawful basis, operation in prohibited locations, or weaponization.

7.4 The App must not interfere with, disrupt, damage, or access without authorization any other App, any Dimensional Robot, the Platform, or any third party’s devices, servers, or networks. Developer must not engage in fraudulent, deceptive, or manipulative practices on the Platform, including fake reviews, misleading listings, or incentivized ratings.

8. Third-Party Terms

8.1 If the App requires Customers to accept Developer’s own terms, those terms must be presented through the Platform’s acceptance flow in a form Dimensional approves, may not conflict with these Guidelines, and may not grant Developer rights in Robot Data beyond those the Data Access Policy permits. Dimensional is not a party to Developer’s terms with Customers.