configure-bs

A notebook-first research pipeline for privacy-preserving Beat Saber telemetry.

User identification accuracy chart before adding synthetic data

Even anonymized XR motion telemetry can retain enough behavioral signal to re-identify the person who generated it.

Inside the experience

What someone can actually do

  1. Beat Saber / SteamVR telemetry preprocessing
  2. Raw-data identification baseline
  3. Synthetic-data privacy and utility evaluation
  4. Differential privacy experiments
  5. Homomorphic-encryption notebook direction

How the idea took shape

A five-stage research pipeline: Unity and SteamVR telemetry capture, a raw-motion re-identification baseline, WGAN-GP synthetic generation, differential-privacy experiments, and CKKS homomorphic-encryption analytics evaluated as a separate track.

Removing names is not enough: the way a person moves in VR can itself become an identifying signature.
Feature-importance analysis for identification from XR telemetry
Feature importance
Comparison of original and decrypted telemetry values
Encrypted computation check
Jayasri presenting the privacy-preserving XR telemetry research poster
Research presentation
Explore how it was built +

I built the notebook pipeline, evaluated identification risk and analytical utility with the research team, and translated the findings into an IEEE VR paper and demonstrations.

  • Python
  • TensorFlow
  • WGAN-GP
  • Differential privacy
  • CKKS
  • Jupyter

Where it could go next

The work shifted my view of generative AI: the same techniques used to imitate people can be redirected to make individuals harder to identify.

More work