Legal
Last updated: October 24, 2026
Cookie Policy
Cookies are small pieces of data a site stores in your browser. dormscape also uses local storage, session storage and temporary in-memory state. This page explains how these support planning, shared rooms and optional voice, and how to manage them. dormscape does not use advertising or retargeting cookies.
On this page8 sections
Sign-in and room progress
These keep the basic site working.
- Sign-in session. If you create an account, your sign-in session is kept in your browser’s local storage so you stay signed in between visits. This isn’t a traditional cookie, but it does the same job. Without it, you’d have to sign in again every time.
- Planner progress. As you move through picking a school, dorm, style, and budget, your in-progress choices are held in session storage under
dormscape-planner. A usable room also has a recovery copy in local storage underdormscape-planner-recovery-v2. That local copy can survive closing the tab or signing out and can be seen by someone using the same browser. It is not a cloud backup. - Workspace recovery. Unsaved workspace edits can be kept in session storage under
dormscape-workspace:…, scoped to your account and room. The recovery entry is removed after the matching edits are saved or you discard it. Session storage normally ends with the tab, although browser session restoration can restore it. Saved rooms and comments are held on our server, not in this recovery entry. - Hall Finder. Your places, days and filters for each school are kept in local storage under
dormscape-hall-finder-v1, with the name of the last schedule file you added and, on Plus or Pro, which saved setup they belong to.dormscape-hall-finder-lastremembers the last school you used. When you sign in from Hall Finder,dormscape-hall-finder-resumeremembers the page to return to for up to 24 hours, and session storage notes that the tab came back from signing in. Schedule files themselves are never kept in browser storage. - 3D drawing drafts.
dormscape-3d-draft-v1:…stores the room builder draft in local storage, scoped to your account. It remains until replaced or removed through site-data clearing or the account-deletion cleanup in that browser.
Preferences and temporary steps
Local storage remembers your cookie choice (dormscape-cookie-consent), motion preference (dormscape-motion-paused), whether you have seen a welcome message, and whether the Hall Finder tip on your plan has been shown or dismissed (dormscape-hf-result-tip). These entries have no automatic expiry in our code. Other short-lived entries support sign-in redirects, pending shopping actions and dismissed prompts. Session entries are cleared when their flow finishes or the browser tab session ends; local entries remain until removed by the relevant flow or cleared in your browser.
Live collaboration and voice
Supabase uses your existing sign-in session to authorize private workspace connections. Current online or away status, active view, selected piece, cursor coordinates and a temporary connection identifier are held in memory and shared with current room members. dormscape does not store a cursor history. Comments and replies are server-side room data, not cookies; clearing browser storage does not delete them.
When you choose to join Room voice, the app requests a short-lived LiveKit join token and keeps the connection state in memory. dormscape does not save this token or call audio in cookies or local storage. LiveKit processes the audio and connection information needed to deliver the call. dormscape does not record or transcribe calls. Leaving the call or workspace page disconnects the voice session.
Microphone permission is managed by your browser separately from cookies. Join with mic off does not enable it. Join and talk or Unmute asks for permission when needed; accepting analytics does not grant microphone access. Rejecting analytics does not disable room voice or comments. Read the Privacy Policy for what is shared and retained.
Analytics
dormscape uses PostHog to see how the site is used: which pages get visited and which buttons get clicked. When configured, PostHog can use cookies and local storage with browser identifiers to connect usage events across visits. These identifiers are not necessarily anonymous. We use the results to improve the product, not for advertising profiles. Session recording is disabled. Events on private workspace, login, account and report pages are filtered out; private comments and voice audio are not sent to PostHog.
dormscape also uses Google Analytics to measure site traffic: which pages get visited, how people find the site and how long they stay. It sets first-party cookies, _ga and _ga_DSRNH55V8B, holding random identifiers that count visits and returning browsers; Google’s default lifetime for them is two years. Google Analytics sends nothing from workspace, login, account or report pages, and once one of those pages is opened it stops sending until the next full page load. Google signals and ad personalization are turned off, so this data is not used for advertising. Read how Google uses information from sites that use its services, or install Google’s Analytics opt-out browser add-on.
Our current analytics setup is opt-out: it may initialize before you answer the banner. Choosing Reject stops Google Analytics from sending further data right away and keeps it from loading on later visits. For PostHog, reload the page to apply that preference to an already-running session; the preference then prevents subsequent PostHog initialization and dormscape analytics calls. Rejecting does not erase data already sent or existing stored entries, including Google Analytics cookies. You can remove stored entries through your browser settings.
Separately, dormscape-session is a random identifier in local storage used to associate our product-click records and optional purchase-survey or feedback submissions. It remains until cleared and currently operates independently of the analytics banner choice. It is not a login credential and does not contain call audio or private comments.
What we don’t use
dormscape does not use advertising or retargeting cookies or sell cookie data. If you follow an Amazon product link, use Google sign-in or visit Stripe checkout, that provider may use its own cookies and storage under its policies. dormscape’s banner does not control those other websites.
Changes to this policy
We may update this policy as dormscape changes. We’ll update the date at the top when we do.
Questions
Questions about cookies? Email info@dormscape.us.
Something unclear? Ask a human.
info@dormscape.us