Daydream privacy notice
Private personal installation · September 13, 2026
What Daydream does
Daydream turns Oura daily sleep, readiness and activity summaries into a landscape. This notice describes the current private, single-user installation, not a public hosted service.
Data used
With your authorization, The dedicated Daydream setup requests all categories enabled for its Oura registration. You review the actual permissions on Oura’s consent screen. The daily scene uses your calendar date, sleep score, readiness score, active calories and daily target calories. Additional authorized data can include profile/email, recorded heart rates, workouts, tags, sessions, sleep oxygen summaries, ring configuration/battery, stress/resilience, cardiovascular age and VO2 max. These are optional details; availability depends on what Oura provides for your account. The returned daily summary records may also contain an activity score and steps. Missing values stay missing. Oura handles account sign-in; Daydream does not ask for or store your Oura password.
Your place photos
You can upload a home or city photo as your scene. The browser resizes it before upload; the server validates and re-encodes it, removing embedded location and other metadata. The photo, place name and scene positioning are saved privately on your Pi and included in downloaded backups. Switching to the default landscape does not erase earlier photo assets needed by retained snapshots. The app does not automatically send photos to an AI service. If you separately ask an assistant to prepare a sky cutout, that approved processing can use an image-generation provider; the resulting mask is then stored on the Pi and reused locally.
Where data is stored
Daily records, retained snapshots, rendering inputs and preferences are saved on your Raspberry Pi. The private website is hosted on Vercel and forwards authenticated requests through Cloudflare to the Pi. A browser-local copy of latest records supports recovery when the server is unavailable. OAuth tokens are kept in an encrypted, HttpOnly browser cookie; application credentials are stored privately on the server. Downloaded backups contain personal Oura data and should be kept private.
Sharing and generated art
This version has no advertising or analytics integration and does not automatically send your measurements or photos to an image-generation provider. Its landscape assets are pre-created; daily rendering uses your scores locally in the browser. Oura receives the API requests required to retrieve your summaries and manage authorization. The hosted website requires your private access key; the Pi API separately requires a server-only gateway credential.
Retention and control
Snapshots are retained until the installation owner removes them. Disconnect clears this browser’s Oura session but preserves saved artwork data and does not revoke access at Oura. You can manage third-party access through your Oura account. Download backup exports retained snapshots, latest records, settings and uploaded scene photos. To remove all stored copies, the owner must remove server archives, browser site data and any backups; the current interface does not offer one button that erases every copy.
Access and contact
The person running this private installation controls its files and access. If someone shared the installation with you, contact that person about your data before using it. No public support or hosted service is offered by this local build. Public distribution would require a named operator, contact details and an updated notice.