How IntoBlocks uses cookies and similar technologies for its Minecraft creator workspace.
2026/09/19
NOT AN OFFICIAL MINECRAFT PRODUCT OR SERVICE. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT.
This Cookie Policy explains how IntoBlocks ("IntoBlocks," "we," "us," or "our") uses cookies, local storage, session storage, pixels, tags, and similar technologies on intoblocks.app and related Services.
IntoBlocks is an independent AI workspace for Minecraft creators. It is not affiliated with, endorsed by, or sponsored by Mojang Studios or Microsoft.
IntoBlocks is operated by CURIOMIND LTD, at 71-75 Shelton Street, Covent Garden, London, United Kingdom. CURIOMIND LTD is responsible for the IntoBlocks Services and related support and purchases. Contact support@intoblocks.app; Mojang and Microsoft do not provide support for IntoBlocks.
Cookies are small files that a website stores through your browser. Local and session storage keep information in the browser, while pixels, tags, and scripts may transmit limited usage or device information to us or a provider. These technologies can keep you signed in, remember preferences, protect accounts, preserve temporary workflow state, measure performance, and attribute visits where permitted.
These technologies are required to provide a feature you request or to protect the Services. They may support authentication, account sessions, security, load balancing, upload and generation state, fraud prevention, and consent records. Disabling them in your browser may prevent sign-in or other core functionality.
These technologies remember choices such as language, theme, sidebar or interface state, selected Minecraft version, palette, and other workflow preferences. Some choices may be stored only on your device.
We use Plausible Analytics for aggregate traffic measurement. Plausible does not use cookies, local storage, or persistent identifiers for this measurement. It processes an IP address and user-agent information to create a daily identifier and does not store the raw IP address. Other analytics technologies, where enabled and legally permitted, help us understand feature use, generation funnels, errors, loading performance, and reliability.
If we run advertising or affiliate campaigns, optional technologies may attribute visits, signups, or future purchases to a campaign or partner. We do not treat an integration that merely exists in the codebase as active. Where consent is required, these technologies should not be enabled until the required choice has been obtained.
The precise names and durations of provider-controlled cookies can change. IntoBlocks may use the following types when the related feature is actually enabled:
| Category | Provider or controller | Purpose | Typical duration |
|---|---|---|---|
| Necessary | IntoBlocks and authentication infrastructure | Account sessions, security, requested workflows | Session or the configured account-session period |
| Necessary | IntoBlocks | Record the cookie choice for the current browser | Until deleted or replaced |
| Functional | IntoBlocks | Language, interface, and local workflow preferences | Session or until deleted |
| Necessary | Storage and security providers | Secure uploads, downloads, abuse prevention, and temporary access | Session or provider-defined security period |
| Cookie-free analytics | Plausible Analytics | Aggregate pageview, referrer, device, and geographic statistics without cookies or persistent identifiers | Aggregated measurement; daily visitor identifier |
| Optional analytics | A provider actually enabled in production | Additional usage, performance, or conversion measurement after acceptance | Provider-defined; disclosed when enabled |
| Payment | Subotiz and its payment partners, when production checkout is enabled and used | Checkout, transaction security, and fraud prevention | Provider-defined |
Production payment activation is pending. Payment technologies are used when the payment feature is enabled and requested; naming a provider here does not mean its checkout is already live. Non-essential payment-related tracking remains subject to applicable consent requirements.
Examples of first-party storage currently configured include:
| Identifier or technology | Purpose | Configured lifetime |
|---|---|---|
intoblocks-cookie-consent (local storage) | Remember acceptance, rejection, or dismissal | Until changed or cleared |
| Better Auth session cookies (names may include a secure prefix) | Maintain the requested signed-in session | Seven-day session, renewable with activity; session cache up to one hour |
sidebar_state cookie | Remember the sidebar layout you choose | Seven days |
intoblocks-language-user-selected (local storage) | Remember an explicit language choice | Until replaced or cleared |
Optional providers vary with the enabled feature and deployment. Before enabling an additional non-essential provider, we will identify its purpose and relevant storage practices and update the consent controls where required. Disabled integrations do not receive information merely because they exist in our software.
Strictly necessary technologies are used to provide the website, a feature you request, or account security and generally cannot be disabled through an IntoBlocks preference control.
Plausible's cookie-free aggregate measurement remains active when you reject optional technologies. Where applicable law requires consent for other analytics, advertising, affiliate, or non-essential technologies, we will request that consent. Rejecting them does not prevent access to core features, although optional measurement or attribution may be unavailable.
You can also delete or block cookies and site storage using your browser settings. Doing so may sign you out, erase preferences or temporary workflow state, interrupt uploads or generation status, or prevent requested features from working. Choices are normally browser- and device-specific.
Use Cookie Settings on this page or in the footer to reopen the consent notice and change your choice. Rejecting optional technologies after acceptance withdraws consent for future optional processing; it does not undo earlier lawful processing or automatically erase provider-held records. The page reloads when withdrawing an existing acceptance so previously loaded optional scripts are no longer running on that page. You can request deletion separately under our Privacy Policy.
Our consent interface records the choice made in that browser. Selecting "Reject Optional" or closing the notice keeps Google Analytics, session-replay, optional product analytics, advertising, affiliate, and marketing technologies disabled. Browser-level cookie and site-storage settings provide an additional control.
Third parties used for authentication, hosting, storage, AI processing, security, analytics, or payments may set their own cookies or receive browser signals when their service is loaded. Their policies govern their independent processing. We will identify material providers in this Policy, our Privacy Policy, or the relevant interface when required.
Following a link to Minecraft, an independent viewer, an import tool, or another website takes you to a separate service with its own cookie practices.
Browser Do Not Track signals are not interpreted consistently across the industry. Where a legally recognized opt-out signal applies to processing we conduct, we will make reasonable efforts to honor it as required by law.
We may update this Policy when our technologies, providers, legal obligations, or Services change. We will update the date above and provide additional notice where required.
Questions about cookies and similar technologies may be sent to support@intoblocks.app.
