Privacy Policy

Last Updated: November 4, 2026


1. Who we are

Shape of Dreams Wiki (shapeofdreams.web.app) is an unofficial, fan-made wiki and build planner for the game Shape of Dreams. It is run by Lukstrike, an independent developer, and is not affiliated with Lizard Smoothie, NEOWIZ or Google. This policy explains what data the website collects, how it is used and how you can remove it.

2. Information we collect

  • Google account information: signing in is optional. If you sign in with Google (through Firebase Authentication), we receive your name, email address, profile picture URL and a unique user ID.
  • Builds: the builds you save (traveler, identity memory, memories, essences, déjà vu, stars, description, optional YouTube link), the nickname you choose for them, your user ID as their owner, the dates they were created and last edited, and their view and like counts. Every saved build is public.
  • Likes: when you like a build, we store a record of your user ID and the time of the like under that build, so each account can like a build only once. A like cannot be undone. The record is not shown to other visitors; only the total number of likes is public.
  • Views: opening a build adds one to its public view count, once per browser tab session. This count is not linked to you.
  • Contact messages: the name, email address, subject and message you type in the contact form.
  • Usage data: pseudonymous analytics collected by Google Analytics (see section 5).

3. How we use your Google user data

We use Google Sign-In only with the basic scopes openid, email and profile. We do not access Gmail, Drive, Contacts, YouTube or any other Google service, and we never post or change anything in your Google account.

  • Name: shown only to you in the site menu, and used to pre-fill the nickname field when you create or copy a build. Only the nickname saved with a build is shown publicly (in the community list, on the build page, and in that page's title and link preview); you can change it or leave it empty, and the build then shows as "Anonymous". In builds saved on or before October 19, 2026, an empty nickname field was filled with your Google account name, so such builds may show that name as their nickname; you can change it by editing the build.
  • Name in older builds: builds first saved on or before October 19, 2026, and not edited since, also store the Google account name their author had at the time, in a field called creatorName. The website does not display it, but, like all build data, it is publicly readable through the site's database and is downloaded by visitors' browsers together with the build. Editing and saving one of those builds removes it, and you can also ask us to remove it (see section 7).
  • Profile picture URL: shown only to you, next to your name in the menu. It is not copied to our database.
  • Email address: kept by Firebase Authentication to identify your account. It is not shown on the website, not stored in your builds, and not used for ads or newsletters; we only write to you to answer a request you send us.
  • User ID: a random identifier stored as the owner of every build you save, so only you can edit or delete them, and as the key of your like records. Like all build data it is publicly readable, so anyone can tell which builds were saved by the same account; on its own it does not reveal your name or email address.

We do not sell Google user data, do not use it for advertising, and do not share it with anyone except Google Firebase, which stores it for us, or when required by law. The only Google data that becomes public is the nickname you choose (your Google name, if you keep the pre-filled value) and the Google account name stored in older builds, as described above. Shape of Dreams Wiki's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. Data sharing and third-party services

We do not sell, trade or rent your personal information. The website uses these services to work:

  • Firebase (Google Cloud): sign-in (Firebase Authentication), the build database (Cloud Firestore) and website hosting.
  • Google Analytics: site traffic statistics.
  • Google AdSense: ads that help pay for hosting.
  • EmailJS: delivers the messages you send through the contact form to the site owner's mailbox.
  • YouTube: builds with a video embed it from youtube.com; when such a build is shown, YouTube receives your IP address and may set cookies.
  • jsDelivr and Google (gstatic.com): serve the website's libraries (Bootstrap, the text editor, the Firebase SDK) and receive your IP address and browser details when they are loaded.

Every build you save is public: anyone can see it on the community builds page and on its own page together with its nickname, and build pages can appear in search engines and link previews. All stored build fields, including the owner's user ID and, in older builds, the creatorName field, can be read through the site's public database.

5. Cookies and browser storage

  • Firebase Authentication keeps your sign-in session in your browser's storage (IndexedDB), including your name, email address and profile picture URL, until you log out.
  • The website stores in localStorage your language choice and the IDs and times of the builds you most recently saved, edited, deleted or liked in this browser, so copies of build lists kept in other tabs are refreshed.
  • For the current tab only (sessionStorage) it keeps an unsaved build while you sign in, the IDs of the builds you viewed (so each view is counted once per session), and for up to 10 minutes a copy of the community build list and of the build you opened from a list, so going back doesn't download them again. It also caches site files with a service worker.
  • Google Analytics uses cookies (such as _ga) to count visits and collects pseudonymous data such as pages viewed, device type and approximate location, but not your name or email address.
  • Google AdSense: third-party vendors, including Google, use cookies to serve ads based on your previous visits to this and other websites. Google's use of advertising cookies enables it and its partners to serve ads based on those visits. You can opt out of personalized advertising at Google Ads Settings. See also how Google uses information from sites that use its services.
  • Visitors in the European Economic Area, the United Kingdom and Switzerland (detected by Google from the visitor's IP address) are asked for consent through Google's consent message, a Google-certified consent management platform that follows the IAB Transparency and Consent Framework. Until you answer, Google Analytics and Google AdSense do not store cookies on your device (Google consent mode), and you can accept, refuse or choose purposes and partners one by one. You can change or withdraw your choice at any time with the "Privacy and cookie settings" button shown at the bottom of the page.

6. Data retention and security

Builds are kept in our database until you delete them. Copies of the build database made for maintenance are kept offline by the site owner for at most 90 days and then deleted. Your Firebase Authentication account (name, email address, profile picture URL, user ID and sign-in dates) and your like records are kept until you ask us to delete your account; like records also stay after the liked build is deleted. Sign-in and build data are stored on Google Cloud infrastructure. Contact messages are delivered by EmailJS to the site owner's mailbox and kept only as long as needed to answer them.

7. Your rights and data deletion

  • You can delete your builds at any time on the My Builds page.
  • You can remove the Google account name from an older build yourself by opening it with Edit and saving it.
  • To delete your whole account (sign-in record, builds and likes), or only the Google account name stored in older builds, send a request through our Contact page using your account's email address. We delete the data, including from our backups, within 30 days and confirm by email.
  • You can remove the website's access to your Google account at any time in your Google Account permissions. This stops future sign-ins but does not delete data already stored.

8. Contact

For any question about this Privacy Policy, use the form on our About & Contact page.