Privacy Policy

1. Scope

This policy applies to the Brick Garage website at brick.loopwick.com and its interactive builder, Ramp test, Career progress, guides, and local sharing tools. The current release does not require an account and does not provide cloud synchronization. References to “we,” “us,” or the “operator” mean the operator of Brick Garage through Loopwick.

Links to other websites are governed by their own privacy practices. A link does not cause Brick Garage to send a saved design or local game record to that destination.

2. Information stored in your browser

Brick Garage uses browser storage to make local play possible. Depending on the features you use, locally stored data can include:

• the active build draft, placed part identifiers, positions, rotations, colours, selected layer, and builder settings;
• named saved designs, local design identifiers, timestamps, and versioned content references;
• prepared test snapshots, Ramp settings, recent run history, locally saved best results, and comparison statistics;
• completed Garage Career mission identifiers and locally calculated XP and rank progress;
• local challenge baselines, anonymous build digests, preview preferences, and limited interface state; and
• a non-secret installation identifier and validated cache metadata only where a future optional-content verification flow requires them.

This data is associated with the current browser profile and site origin, not with a Brick Garage account. It is not automatically synchronized across browsers or devices. Clearing site data, uninstalling the browser, using private browsing, or changing devices may remove it.

3. Imports, exports, and sharing

Imported design JSON and BR1 share codes are parsed and validated in the browser. A received remix opens as a read-only preview first and does not replace the active workspace unless you choose to save it locally. Invalid, unsupported, malformed, or oversized data is rejected.

Information leaves your browser when you take an explicit action such as downloading a design file or Ramp image, copying text or a share code, opening a remix link, using the browser's system share feature, or posting content through another service. You control that transfer. Shared build data is limited to the relevant core part identifiers, transforms, colours, selected settings, and any included Ramp summary. It is designed to exclude account data, email, payment state, receipts, unrelated saves, and complete local history.

Do not include personal or confidential information in design names or other text that you plan to export or share. After you send information to another person or service, that recipient's handling is outside the local Brick Garage storage boundary.

4. Analytics and advertising status

Because these scripts are inactive, Brick Garage does not currently use them to create analytics profiles, measure behaviour across sites, personalize advertising, or set advertising cookies. The hosting and network providers that deliver the website may still process ordinary technical request information, such as an IP address, user agent, timestamp, requested path, and security signals, as necessary to transmit and protect the service under their own policies.

If analytics or advertising is introduced later, it must follow a consent-first process where required. Before activation, the public notice and Cookie Policy will be reviewed, required consent controls will be configured, provider identifiers will be validated, and scripts will remain disabled unless the deployment is explicitly marked ready. Advertising, if enabled, is intended for guide content rather than builder controls, navigation, downloads, or modals.

5. Optional content and commerce

Pack sales are disabled in the current public release. Previewing a planned pack does not create an account, purchase request, ownership record, or analytics event. The public game does not store payment-card details, and a checkout redirect or local flag cannot grant optional-content access.

If verified optional-content access is offered in a future release, the browser may temporarily cache an opaque signed receipt and display-only pack identifiers. The design requires server session secrets and payment details to remain outside readable browser storage. Any material change to the personal information used for commerce would require updated public information before launch.

6. Your choices and data retention

You can rename, duplicate, export, or remove saved designs through the game controls. You can clear run history or other feature data where the interface offers that action. You can also remove all Brick Garage local data using your browser's site-data settings. Export important designs first because local deletion may be irreversible.

Local data remains until it is overwritten, removed through the interface, cleared through browser settings, or removed by the browser's own storage policy. Session-only state normally ends when the page or private session closes. Files and text that you export remain wherever you or the receiving service store them.

7. Children and sensitive information

Brick Garage is a creative game and is not designed to collect sensitive personal information. Do not place health, financial, government identifier, precise location, private contact, or other sensitive data in a design name, exported file, or shared message. A parent or guardian should supervise a child's use of browser storage and external sharing tools as appropriate.

8. Security and changes

The project validates imported formats, limits build and payload sizes, blocks unknown fields where the format requires it, and uses a restrictive content security policy. No browser or storage method can be guaranteed completely secure. Keep your browser updated, review files before sharing them, and maintain independent backups of important builds.

We may revise this policy when the game, hosting, storage, analytics, advertising, or commerce behaviour changes. The effective date above will be updated when a revised policy is published. Materially different data use will not be described as active before the related feature and required controls are ready.

9. Contact

For privacy, support, or content-removal enquiries, contact the Brick Garage operator through Loopwick. Do not send sensitive game or payment information unless it is necessary for the request.