Product and policies
Cookie Policy
Effective July 15, 2026
This policy explains the browser-storage technologies used by Brick Garage. The current release relies on essential local storage for game data. Analytics and advertising technologies are disabled.
1. What this policy covers
“Cookies” is often used as a broad label for browser technologies that remember information. A cookie is a small value that a website can send with later network requests. Local storage and session storage keep values in the browser without automatically attaching them to every request. Brick Garage currently uses local browser storage more than traditional cookies, but this policy describes all three categories in one place.
The categories below are based on purpose: essential local game operation, analytics, and advertising. A technology may not be active merely because the software contains a future-ready integration. The current deployment status determines whether it is loaded.
2. Essential local storage
Purpose
Essential local storage supports the game features you ask Brick Garage to perform. It can remember the active build draft, placed parts and transforms, colour and layer selections, named saved designs, prepared snapshots, Ramp settings and history, locally saved best results, Career mission progress, challenge baselines, and limited interface preferences.
This information stays in the current browser profile and site origin. It is not a Brick Garage account and does not synchronize itself to another device. The data makes it possible to return to a draft, update a named design, compare a current Ramp build with a local best, and keep Career progress between sessions.
Other necessary values
The application may keep a non-secret installation identifier or validated cache metadata for a future optional-content verification boundary. Such a value cannot prove a purchase by itself. Pack sales and the production verification service are disabled in the current public release, so previewing planned content does not create a session, purchase, or ownership record.
Essential storage does not require advertising consent because it is used for the local feature you requested. You can still block or clear it through browser settings, but doing so may prevent saves from working or erase local progress. Export important designs before clearing site data.
3. Analytics storage and scripts
Analytics are disabled in the current release. Brick Garage does not currently load an analytics script, set an analytics cookie, create a visitor analytics profile, or record in-game events through an analytics provider. Injected browser analytics are blocked by the site's current security policy.
Ordinary hosting and network delivery may still involve technical request records used to serve and protect the site, such as a timestamp, requested path, IP address, user agent, response status, and security signals. Those operational records are different from an in-page behavioural analytics integration and are handled by the relevant infrastructure providers under their policies.
If a product analytics tool is introduced later, this policy will be reviewed before activation. Where consent is required, non-essential analytics will stay off until the visitor has made the required choice. The notice will identify the active provider, purpose, duration, and available controls rather than treating a future possibility as current collection.
4. Advertising storage and scripts
Advertising is disabled by default and is disabled in this release through VITE_ADSENSE_ENABLED=false. Brick Garage therefore does not currently load the advertising provider script, request an ad placement, or set advertising cookies through that integration.
The code requires an explicit enabled flag, valid public placement identifiers, and a consent-readiness flag before the advertising integration can become active. If advertising is enabled in a future deployment, the public notice and consent controls must be reviewed first. Ads are intended for guide content, not for builder controls, navigation, downloads, or modal actions.
An active advertising provider may use cookies or device information according to the visitor's consent choice and the provider's policies. That is a future conditional description, not the current Brick Garage behaviour. The site will not describe advertising cookies as active while the advertising script remains disabled.
5. Imports, sharing, and external sites
Opening a local file or pasting a BR1 code does not require an analytics or advertising cookie. Supported data is validated in the browser and shown as a preview or imported only after the relevant user action. Copying a share code, downloading a file, saving a PNG, or opening a remix link may create data outside Brick Garage at the location you choose.
External links, system share tools, social composition pages, and recipient websites may use their own cookies or storage. Their policies and controls apply after you choose to visit or share with them. Brick Garage does not control storage created by another service.
6. Browser controls
Most browsers allow you to inspect, block, or delete cookies and site storage. The exact controls vary, but they are commonly found under privacy, security, cookies, permissions, or site-data settings. You may be able to:
- delete all data stored for brick.loopwick.com;
- block cookies or storage for one site or for all sites;
- clear data automatically when the browser closes; or
- use a private session that removes local state when the session ends.
Blocking essential storage can cause drafts, named designs, Ramp history, Career progress, and preferences to disappear or remain session-only. Clearing storage cannot be undone by Brick Garage because the current release has no account or cloud backup. Export design JSON before deletion when you want to keep a build.
7. Changes and contact
This policy may change if Brick Garage activates a new storage category, analytics system, advertising provider, consent tool, account feature, or commerce service. The effective date will be updated when revisions are published. A future integration will not be listed as active until its deployment requirements are actually met.
For questions about browser storage or this policy, contact the Brick Garage operator through Loopwick.