This page explains how Rightlight6 handles room uploads, temporary storage, and audit session data in plain language.
This page explains what happens to uploads, how long they may be kept, and what you should know before sending room media.
Privacy priority
Because the audit depends on room images and short walkthrough videos, this page explains retention, deletion timing, and any third-party model handling as clearly as possible.
Upload scope
Room images and short room videos used to generate the audit output.
Retention
Uploads are kept only for the minimum period needed to render results and debug failures.
Expectation
You should be able to see what is temporary, what is saved, and what is sent to model providers.
What matters here
Rightlight6 only works when the system can read room images or short room videos closely enough to describe daylight reach, glare, layering, and visible comfort overlap. That makes upload handling a core part of the service, not a side note.
The privacy goal is simple: keep only the data needed to run the audit, show the result, and inspect failures when something clearly breaks.
You should not have to guess whether uploads are temporary, whether results pages stay live, or whether third-party model providers ever see your data. Those boundaries should be visible here and consistent with the actual service flow.