1. Who We Are
Quest2ROS is developed and maintained by Michael C. Welle.
Website: mcwelle.com
Contact: mwelle@kth.se
2. What Data the App Processes
The table below describes every category of data that flows through the application during normal use.
| Data type | Description | Sent to developers? |
|---|---|---|
| Controller pose | Position and orientation of each hand controller, captured at the VR frame rate. | No |
| Controller velocity | Linear and angular velocity (Twist) of each controller. | No |
| Controller inputs | Button states, thumbstick axes, and trigger values from each controller. | No |
| Network settings | IP address and port number of the user's ROS server. Stored locally on the device using Unity PlayerPrefs. Never transmitted to the developers. | No |
| Haptic commands | Frequency and amplitude values received from the user's ROS server to drive controller vibration. | No |
No personal data, device identifiers, usage analytics, crash reports, or any other information is collected by the developers. The application contains no analytics SDK, advertising SDK, or third-party tracking library.
3. How and Why Data Is Processed
Controller data is transmitted in real time over a direct TCP connection from the headset to the IP address and port that the user enters manually in the app. This connection goes to a ROS (Robot Operating System) server running on the user's own local network — it does not pass through any server operated by the developers.
The sole purpose of this data transmission is to enable robot teleoperation:
- Pose and velocity data allow a connected robot or simulation to mirror hand movements.
- Input data (buttons, triggers) lets the user send commands to the robot.
- Haptic feedback from the robot provides force or contact feedback to the user's hands.
Network settings (IP address and port) are stored locally on the device so the user does not have to re-enter them each session. This data never leaves the device.
4. Data Sharing and Third Parties
We do not share any data with third parties. The application does not integrate any third-party SDKs beyond:
- Meta Platform SDK (Oculus) — required to access VR controller input on Meta Quest hardware. Meta's own privacy practices are described at meta.com/privacy/policy.
- Unity Runtime — the game engine used to build the application. Unity's privacy practices are described at unity.com/legal/privacy-policy.
Neither of these integrations is used by this application to collect or transmit user data to the developers.
5. Data Retention
Because we do not collect any personal data, there is nothing for us to retain or delete.
The only data stored by the app is the network settings (IP address and port) saved locally in PlayerPrefs on the device. You can clear this at any time by:
- Uninstalling the Quest2ROS application from your headset, or
- Using the Meta Quest system settings to clear the app's local data.
6. Your Rights and Data Deletion
Because Quest2ROS does not collect or hold any personal data on our servers, there is no personal data for us to delete upon request.
If you wish to remove all data associated with the application from your device, uninstall Quest2ROS from your Meta Quest headset. This removes all locally stored settings at no cost and requires no request to the developers.
If you have any questions or concerns, contact us at mwelle@kth.se.
7. Children's Privacy
Quest2ROS is a research and robotics tool intended for adults. It is not directed at children under the age of 13. We do not knowingly collect any information from children. If you believe a child has used this application and has concerns, please contact us at mwelle@kth.se.
8. Security
All data stays on your local network. The TCP connection between the headset and the ROS server travels only over the network that you configure — typically a private local Wi-Fi network. The developers have no access to this connection at any point.
9. Changes to This Policy
If we make material changes to this policy, we will update the "Last updated" date at the top of this page. We encourage you to review this page periodically.
10. Contact
For any privacy-related questions please contact:
Michael C. Welle
mcwelle.com
mwelle@kth.se