Privacy

What stays in your browser

Cozy Cube saves your house automatically in this browser. The saved data can include room names and layouts, furniture and its placement, room finishes, doors, and the camera view. Named save points, recovery data, and game preferences are also stored locally. These are tied to this browser and site, not to an account, and are not automatically available on another device.

Gameplay analytics is on by default for new preferences when you enter the game. Your preference and a random anonymous browser identifier are stored locally; an existing off choice is preserved. A small local marker remembers the first analytics notice so it is not shown again. A separate random browser key supports repeated publishing of the same room. You can remove locally stored game data by clearing this site’s browser storage; doing so can also remove your rooms and save points. Clearing browser storage does not remove a published share.

When you share a room

Publishing a short share link sends the selected room data to Cozy Cube’s share service so it can store and serve that room. You may also choose to send a display handle, a link to a parent share, and details for a Tucked Away hunt. A random browser key helps recognize repeat publications; the service stores a hash of that key. If the share flow uploads a generated preview card, that PNG is stored for the link. The service uses Cloudflare storage and may process the request’s network address for rate limiting and, when configured, abuse checks.

Anyone with a published link can open the shared room and may remix it. A link created without the share service instead contains the room data in its URL fragment. Treat either kind of link as public: people or services you send it to can view or copy it. Avoid putting private information in room names, handles, or designs.

For Tucked Away hunts, Cozy Cube keeps a total found count for the published share. The browser also stores a small marker so it does not report the same share as found more than once from that browser.

Free currently has no in-game control to remove a published share, and Cozy Cube does not publish a fixed retention period for share records. Do not publish a room unless you are comfortable with it remaining accessible through its link.

Website analytics

On the production landing page, Cozy Cube automatically sends limited website events to PostHog: a page view, visible page sections, button clicks, room demo interactions, and launch signup attempts and results. This respects your browser’s Do Not Track signal. It uses a random identifier held only in memory for that page lifetime, without saving analytics cookies or a website analytics identifier in browser storage. Reloading the page creates a new identifier.

Website events include only a broad entry-source category: organic search, paid search, social, email, referral, direct, or other campaign. This is determined in the browser from the referring site or a recognized campaign medium and stays in memory for that page lifetime. Raw referring addresses, campaign values, visited URLs, query strings, fragments, email addresses, confirmation tokens, and room contents are not sent. The page view uses only the fixed public homepage URL. Website analytics is separate from the optional gameplay analytics preference in Settings. A signup result awaiting email confirmation does not mean the subscription is confirmed.

Optional product analytics

Gameplay analytics is on by default when you enter the game with no saved analytics preference. Existing off choices are kept, and you can turn it off anytime in Menu → Privacy. A compact first-menu notice explains this and closes when you enter the room or dismiss it. This setting controls the main game, not website analytics on the landing page. Gameplay analytics is also suppressed when your browser signals Do Not Track or the required local storage is unavailable. When enabled, Cozy Cube sends allowlisted gameplay events to PostHog using a random anonymous identifier and a temporary session identifier. Events can describe entering ready play, placing or editing furniture, styling, named saving, successful sharing, undo and redo, tutorial progress, panel openings, changed-room recovery, and image or GIF download requests. Download requests do not confirm that a file was saved to your device. Limited feature-use events cover catalog discovery, experience controls, music commands, and accepted pet interactions at most once per feature in an analytics-enabled page session. Events may include room and item counts, the Free edition, the current desktop or mobile viewport layout, and fixed action categories. Session IDs, usage budgets, and tutorial ordinals stay in memory and are not added to saved rooms.

Product analytics is not designed to send room contents, room names, furniture coordinates, save files, instance or save identifiers, share identifiers or URLs, search terms, favorite lists, selected music track identifiers, referrers, or arbitrary personal details. Cozy Cube does not use PostHog session replay, DOM autocapture, or advertising profiles. Turning analytics off stops future collection and discards unsent events; it does not delete events already received by PostHog.

Error diagnostics and service operation

Error diagnostics are separate from product analytics. In production, Cozy Cube can send error reports to Sentry even when product analytics is off. The reports may include error messages, stack traces, a source label, a sanitized page path, and a short trail of recent gameplay event names with limited context such as room and item counts or the panel used. Automatic collection of user details, cookies, request headers and bodies, URL query strings, and stack-frame variables is disabled. Sentry may still infer approximate location from the network connection unless its project settings scrub IP addresses. Error text and stack traces can still contain information associated with the error, so avoid entering private information into the game.

Cozy Cube uses Cloudflare to serve the game and operate its share service. Cloudflare and the analytics and diagnostics providers process technical request data to deliver their services under their own terms and settings. Cozy Cube’s public app materials do not specify provider-side retention periods for analytics, diagnostics, or operational logs.

Launch news emails

If you sign up for launch news on the Cozy Cube website, we use your email address only to tell you about the Cozy Cube Full Game launch. We first send one email asking you to confirm. If you don’t confirm within 48 hours, your address is removed from our signup records the next time our weekly cleanup runs, and we won’t email you again unless you sign up again.

We store your address, when you signed up and when you confirmed. Signup records are kept in Cozy Cube’s Cloudflare database. Once you confirm, your address and subscription status are kept with Resend, our email provider, and our own record keeps only hashes of your address and confirmation link, plus the related times. We also use your network address briefly to limit repeated signups.

Resend keeps your address until you ask us to delete it. Unsubscribing stops our launch emails, and Resend keeps your address marked as unsubscribed so they don’t reach you. If your address is entered in our signup form after that, we send an email asking you to confirm, at most once every 24 hours, and you stay unsubscribed unless you click its link. If it isn’t clicked within 48 hours, our record of your address is removed the next time our weekly cleanup runs. We delete the confirmation link hash in the first weekly cleanup at least 30 days after you confirm. Otherwise, the address hash and times stay in our record until you ask us to delete them.

Every launch email has an unsubscribe link. To unsubscribe or ask us to delete your address, email support@jcstudio.org.

Questions

For questions about this notice or Cozy Cube’s privacy practices, contact J&C Studio at support@jcstudio.org.