01Scope
This policy covers cubley.app (Cubley) — a site for discovering, publishing, and following step-by-step guides for Minecraft builds. It describes what we collect from you, why, and what choices you have. It does not cover Minecraft itself, or Google's own handling of your Google Account, which its own privacy policy governs.
02Information we collect
Account information, from Google Sign-In
You can browse and view every public build without signing in. Publishing a build or deleting one you published requires signing in with your Google account. When you do, Google shares your name, email address, and profile picture with us. We never see or store your Google password — Google handles that entirely on its own servers.
Content you publish
If you publish a build, we store the build file's block data, the name and description you give it, the category you choose, and the display name you ask to be credited under (which can be different from your real Google name).
Collected automatically
Your IP address is used briefly to enforce a limit on how often one visitor can publish, to keep the site from being flooded with spam or abuse. It is not stored alongside your account or attached to the builds you publish.
Cookies
We set two cookies, both required for the site to function — never for advertising or tracking:
session— keeps you signed in, for 30 days.oauth_state— exists for a few minutes during Google sign-in only, to confirm the sign-in request actually came from you.
We don't run analytics, advertising, or third-party tracking scripts.
03How we use it
- To sign you in and keep you signed in between visits.
- To show your name and picture next to builds you've published.
- To confirm you actually own a build before letting you delete it.
- To rate-limit publishing and keep the library free of spam.
- To operate, maintain, and improve the site generally.
05What's public
Cubley is a public library by design. Anything you publish — a build's name, its description, the build itself, and the display name you credit it to — is visible to anyone who visits the site, including people who have not signed in. Please don't put personal information you'd rather keep private into a build's name or description.
06Retention
We keep your account information and anything you've published for as long as your account exists, or until you remove it yourself. You can delete any build you've published at any time, from that build's page — it's removed immediately and permanently.
To delete your account and all associated data entirely, contact us at blockguide1.best@gmail.com — we don't yet have a fully automatic self-service option for this.
07Your choices
- Sign out any time from the account menu — this ends your session immediately.
- Delete a build you published, any time, from its page.
- Revoke Cubley's access to your Google account entirely at myaccount.google.com/permissions.
- Request a copy or deletion of your data by contacting us (below).
08Children
Cubley is not directed at children under 13, and we don't knowingly collect personal information from them. If you believe a child has signed in or published a build here, contact us and we'll remove it.
09Security
We never store a password — Google's own security handles that side of your account entirely. Sessions are cryptographically signed so they can't be forged, and the site is served over HTTPS. No system is perfectly secure, but we don't collect more than the site needs to run.
10Changes to this policy
If this policy changes in a meaningful way, we'll update the date at the top of this page. Continuing to use Cubley after a change means you accept the updated policy.
11Contact
Questions, requests, or concerns about your data: blockguide1.best@gmail.com.