Skip to main content

MPS Data Lifecycle


Researchers can upload data collected by Project Aria glasses to Meta for cloud-based Machine Perception Services (MPS) processing.

This page provides information about how all Aria sequences submitted to Meta for MPS are processed, handled and stored.

How sequences are processed

  1. Raw Aria sequences (VRS files) are uploaded to secure cloud storage via the Desktop Companion app
  2. The data is only uploaded to Meta servers to serve MPS requests and is deleted after 30 days
  3. The MPS output is saved in the cloud
    • User account that requested the MPS gets the token necessary to access MPS outputs
    • This derived data is persisted in the cloud
  4. Raw data is deleted from the cloud
    • Meta’s data management processes mandate that this raw data cannot be stored for more than 30 days
Diagram of MPS Processing lifecycle, as described above

Figure 1: MPS Processing Lifecycle

Data storage and use

  • Partner data is only used to serve MPS requests. Partner data is not available to Meta researchers or Meta’s affiliates.
  • Raw partner data (VRS files) is stored for no more than 30 days.
  • The whole process is automated and only engineers in the core MPS team can access the pipeline.
  • All MPS output (trajectories, semi-dense point clouds, gaze vectors etc.) continue to be stored in secure cloud storage, so that users can re-download the data at any time. MPS output is not available to Meta researchers or Meta’s affiliates.
    • Only the user account that requested the MPS output gets the token necessary to download the derived data
    • Our goal is for this data to always be available to the user who requested it, however, if the Desktop App’s local cache is cleared you may no longer have the token necessary to access the data.
  • The MPS pipeline generates statistics about how the algorithms are performing as well as the console logs from processing. These aggregated statistics are used by the Project Aria MPS team to help improve our offerings.