Security
Thoughtful defaults.
Clear limits.
Security is an ongoing engineering responsibility. Here is what this website is designed to protect, and where its scope ends.
Small public surface
The public website is separated from the capture-processing prototype. It exposes no capture upload, global capture listing or shared device credential. It uses HTTPS, restrictive browser content permissions and account responses that are not cached.
Account boundaries
When accounts are activated, the server verifies Firebase credentials and current identity state. It derives account ownership from the verified identity. Profile changes and preview requests require verified email; deletion requires recent authentication. Request origins and input sizes are checked.
Deliberate data handling
The site does not use advertising analytics or session replay. Passwords are handled by the authentication provider. Do not upload or send private scenes in a bug report; inspect diagnostics first. Public cloud scene storage is not part of this launch.
Reporting an issue
Existing testers should report security concerns through their invitation channel, without passwords, access tokens or private captures. A public security contact is pending verification before general release.