Privacy policy

Chronicle Robotics, Inc. runs Enactive. Teams post recording tasks, and contributors record them with a Meta Quest headset. One account can do both, for example to record data for yourself. This policy covers this website and the Enactive for Quest headset app. If you have a question or a request about your data, email [privacy contact email].

Your account

Your name, email address and profile photo, which you give us when you sign in through Clerk, and whether you chose to start by recording or by posting tasks. For teams, we also keep the team's name and its members.

Your recordings

The headset records only after you start a recording, and only what the task asks for. Before you start, the headset lists what the recording will capture. A recording can include:

• Video from both headset cameras, with each frame's timing and camera settings.
• Your movement as the headset estimates it: where your head is, your hand joints and your body pose.
• Raw readings from the headset's motion sensors, its accelerometer and gyroscope, if Horizon OS makes them available.
• The depth of your surroundings, if the task asks for it.
• The room layout from Space Setup, such as walls, surfaces and labeled furniture, if the task asks for it.
• Microphone audio, if the task asks for it and you allow it.
• Which step you were on, and problems like lost tracking.

Camera video shows whatever is in view: your hands, your home and anything or anyone around you, including reflections, screens and paperwork.

Your headset

The headset model, Horizon OS and app versions, a random ID the app creates when it's installed, and the headset's camera calibration, which is needed to line the cameras up with the depth and tracking data.

Joining, pairing and linking

When you joined each task, the exact consent text you agreed to, the pairing codes you create, and your headset's sign-in to the task. When you start recording for yourself, when you agreed to its terms. If you open a task through an invite link, that the link gave you access, and when. If you link a headset to your account, its model and OS version, and when it was linked and last used. We also note the IP address of each code attempt so we can block code guessing.

What we make from your recordings

Preview videos, thumbnails, a 3D point cloud of the room built from the headset's depth and colored from the camera video, a 3D recording that plays the cameras, depth and movement back together, data tables, automatic quality checks, the team's review decision and notes, and descriptions of detected actions written by Sense, with a search index built from them.

• To run the service: sign-in, pairing or linking your headset, uploading and processing recordings.
• To deliver your recordings to the team whose task you joined, for the uses described in that task's consent text.
• To check that recordings match the task, describe what happens in them, make them searchable and answer the team's questions about them, using automatic checks and Sense, which uses external AI services described below.
• To keep the service secure, prevent abuse and meet our legal obligations.

We don't:

• sell or rent your data to anyone, or use it for advertising;
• try to identify you or anyone else from a recording, including through face, voice or gait recognition;
• combine your recordings with other data about you;
• use your recordings for anything not described here or in the task you joined.

• The team that posted the task sees your recordings for that task and everything made from them. They see you as a pseudonym like “Contributor 4F2A9C”, not your name or email. They can review, annotate and download recordings, copy them to their own storage, and use them as the task's consent text describes.
• Team-only and invite-only tasks are shown only to members of the team that posted them, or to the people it invited with a link. If you leave that team, or the team removes you from a task, you can no longer record for it. Recordings you already sent stay with the team unless you delete them.
• Your own recordings, the ones you record for yourself or with your own robot, are just for you. No team can see them.
• You see your own recordings, in video and in 3D, whether each one was approved, and Sense's short summary of it.
• Service providers that process data for us under contract: Clerk for accounts and sign-in, Amazon Web Services for servers and file storage, and Google and Anthropic for the AI services that Sense uses. For each recording Sense checks, Google receives a copy of one camera's video without sound, at most 720 pixels tall, with the task's instructions and its example video, if it has one; for a robot recording, also the robot model, camera name, substep names and timings, outcome label, tags and quality warnings. When the team asks Sense a question or runs a saved procedure, Anthropic receives their messages and what Sense looks up to answer: frames from any camera's sound-free copy, a recording's details and notes, and measurements from its tracking data; when Sense watches a stretch of video to answer, Google receives that sound-free video. To run search, Google receives the text of descriptions, notes and searches. When the team builds an object for the simulator, Anthropic receives its photos, links, the pages read from them and its description; Google receives some of those photos, the product's name and views of the object as built, to predict the sides no photo shows. We delete each video we upload to Google as soon as the request that uses it finishes. Anthropic doesn't keep prompts or answers by default, but may keep a request its safety systems flag for up to 2 years, or when the law requires it, and doesn't use what it keeps to train models without our express permission.
• Meta makes the headset and its platform, but we don't send your recordings to Meta. Meta's own privacy policy covers your headset and your Meta account.
• Authorities or others, when the law requires it or to protect someone's safety.
• A new owner, if Enactive is merged or sold. This policy would still apply to your data.

Only record people who have agreed to it. If someone appears in a recording without agreeing, discard the recording on the headset, or delete it after it uploads.

• Before anything uploads, you can redo or discard each recording on the headset. Redone and discarded recordings never leave the headset.
• Watch or delete a recording you sent from My recordings under Record.
• Leave a task from its page. This signs your headset out of the task, and you can also delete every recording you sent for it.
• Unlink a headset from Your headsets in your account menu, or on the headset itself. This signs it out of every task.
• Delete your account from your account settings. This deletes all your recordings, your profile and your paired and linked headsets.

When you delete something, it disappears from the site right away and is erased from our storage and from the datasets we built with it within a day. If the team already downloaded a dataset that includes it, or copied it to their own storage, that copy is in the team's hands. Ask the team, or email us and we'll pass your request on.

You can also ask for a copy of your data, ask us to correct it, or object to how we use it, by emailing [privacy contact email]. We reply within one month. You can also complain to your local data protection authority.

Where the law asks for one, such as in the EU and UK: we record and share recordings because you consented to that when you joined the task, and you can withdraw consent at any time by leaving the task. We run your account to provide the service you signed up for, and we protect the service from abuse because we have a legitimate interest in doing so.

• Recordings: until you delete them, leave the task and delete them, delete your account, or the team that posted the task closes its account.
• Account details: until you delete your account.
• Consent records: after you leave a task or delete your account, we keep the task you joined, when you agreed and a fingerprint of the exact text you agreed to, without your recordings or contact details. This proves that you agreed.
• Pairing and link codes expire after 10 minutes. Headset sign-ins expire after 3 days or when you leave the task. A linked headset stays linked until you unlink it.
• The IP addresses of code attempts are deleted after a day.

You must be 18 or older to contribute. We don't knowingly collect recordings from anyone younger. If you think a minor has sent us recordings, email [privacy contact email] and we'll delete them.

Data is encrypted in transit. Teams can only reach recordings from their own tasks, download links expire after an hour, and codes work once. We store data in us-west-2 (Oregon, USA). Our service providers may process it in other countries, and where the law requires it we use safeguards like the EU Standard Contractual Clauses.

We'll post changes here and update the date at the top. If a change affects how we use recordings you've already sent, we'll tell you before it applies.