What daydream does with your data.

This page is a plain description of how the software behaves, checked against the source code. It is not yet a legal privacy policy. A reviewed policy will replace this notice before daydream is promoted publicly.

The short version

daydream runs in your browser. Your projects are written to that browser's local storage and stay there. There are no cookies, no analytics, and no tracking scripts of any kind. Fonts are served from daydream itself, so opening the site does not call out to a font host.

Three things can leave your device, and each one is listed below with what triggers it.

What is stored on your device

Everything you type into a project: the board, the script, the storyboard, the shot list, the schedule, the blocking setups, the call sheet and the slate takes. That includes anything you enter about other people, such as crew names, roles, phone numbers and email addresses, and location addresses.

Also stored: your theme choice, whether you have seen the welcome screen, whether the sidebar is collapsed, and a local profile with the name and email you enter at sign-in. A sample project is written on first load so the app has something to show.

Clearing your browser's site data erases all of it. Deleting a project from the home screen erases that project and every module's copy of it.

What leaves your device

A shoot location, when a call sheet needs weather or the nearest hospitalOpenStreetMap · Open-Meteo

The location text you typed is sent to Nominatim (OpenStreetMap) to turn it into coordinates and to find the nearest hospital, then those coordinates go to Open-Meteo for the forecast and sun times. As with any request from a browser, your IP address is visible to them. The result is cached on your device for thirty days. Neither receives anything else.

A share link's contents, when you copy onethe recipient, and daydream's server if you are signed in

A share link carries a frozen copy of that document. For a call sheet that includes crew names and call times, and any phone numbers, emails, location and hospital details you have entered. Signed in, the copy is stored on the server behind a random token and expires; you can see and revoke those links on the project's overview page. Signed out, the copy is encoded inside the link itself, which means it never expires and cannot be taken back once sent.

Your projects, when you sign indaydream's account storage

Signing in creates an account and backs up your projects to it, including everything described above, so they are available on your other devices. Uploaded storyboard frames are stored as images. This only happens on this deployment if cloud accounts are switched on.

Your email address

If cloud accounts are on, signing in sends your email address so a sign-in code can be emailed to you, and stores it with your account. If they are off, the name and email you enter stay on your device and are never transmitted.

Payments

If you subscribe, the payment is handled by Stripe on Stripe's own pages. daydream never sees or stores your card details. What comes back is which plan you are on and when the period ends.

Deleting things

A single project: delete it from the home screen. That removes it and every module's copy of it from this browser.

A share link: open the project's overview and revoke it. It stops working for everyone immediately. Links copied while signed out cannot be revoked, because the document travels inside the link rather than on a server.

There is no account to delete on this deployment: nothing is synced anywhere. Clearing your browser's site data removes everything daydream has stored.

Who to ask

A contact route for questions and data requests will be published alongside the reviewed policy.

Last checked against the source on 7 September 2026.