website analytics
when a Mixpanel project token is configured, the public website records page views, visible time on each page, maximum scroll depth, outbound link clicks, waitlist calls to action, waitlist steps, and whether an application succeeds, fails, or is left unfinished. campaign tags in links, such as utm source, medium, campaign, content, and supported ad click ids, are retained for first-touch and latest-touch attribution.
analytics events do not include your name, email address, organization, job title, or any free-text waitlist answer. optional automatic capture is limited to clicks, dead clicks, rage clicks, and form-submission signals on public marketing pages. it does not capture text, form input, full URLs, or private application pages. waitlist, sign-in, contact, and custom-request forms are always blocked from automatic capture. heatmaps and session replay are disabled. Mixpanel stores an anonymous browser id in local storage so visits can be counted consistently, and the site respects your browser's Do Not Track setting.
after you sign in, dreamscape may connect that browser's anonymous marketing journey to your account using a namespaced internal user id. your email address is not used as the Mixpanel identity or sent as an analytics property. dreamscape resets the analytics identity when you sign out or the authenticated session ends.
email addresses
an email address submitted for a waitlist application, contact request, or account is used by dreamscape for the requested application, reply, or authentication workflow. it remains outside the Mixpanel analytics boundary. do not place an email address in a campaign link or UTM tag, because URLs can appear in browser history, server logs, analytics, and referrer data.
inbox
when you create a playlist, when a new Hugging Face Hub revision of that playlist is published, or when your playlist is deleted, dreamscape writes a notice for the playlist owner only. those rows live in the header inbox. they are not emailed and they are not sent to other users.
web push
the inbox fills for types that are on. a live browser or OS notification is optional. the first authenticated /app visit with no subscription, or a queued prompt after MCP use, shows a dismissible prompt. clicking Allow in the browser is the only way to subscribe; using MCP does not subscribe you. dreamscape then stores a Web Push subscription (endpoint and keys) so it can send a small payload: event type, title, and click URL. no API tokens or Hub grant fields are included.
you can turn OS notifications off, and mute individual types, in Account → Notifications. OS off is sticky and deletes stored subscriptions. turning a type off skips new inbox rows, toasts, and Web Push for that type; existing inbox rows stay. dreamscape does not add a home-screen PWA manifest in this release; iOS OS notifications stay best-effort, with the inbox as the reliable record.