Privacy Policy

This policy applies to Bricklayer Editor (the desktop app, however you installed it, including from the Microsoft Store), the Bricklayer website, its documentation, downloads, update service, and the optional “Brick” documentation chat (together, the “Services”). Bricklayer is an independent project.

It does not cover services operated by other companies, including Roblox, GitHub, AI providers you choose in Bricklayer Editor, or sites you visit through a link from Bricklayer. Their policies apply to their services.

We keep the site deliberately light on data collection. Depending on how you use it, the Services process:

• Anonymous site analytics. In production, Vercel Web Analytics records aggregate usage data such as pages viewed, referrer, approximate location, device type, operating system, and browser. It does not use cookies or keep a cross-site identifier.
• Functional preference cookies. If you give Bricklayer a heart, the site stores bricklayer-hearted for up to one year so it can remember that choice and avoid counting it twice. The associated counter is stored without an account profile. A previous Terminal beta request may also have left a bricklayer-terminal-beta-requested cookie, which expires within one year of the request.
• Support-chat messages. When you use Brick, the message and the recent conversation context you provide are sent to our server and then to Inception Labs (or Groq, as a backup) to generate an answer. Do not include passwords, API keys, private game files, or other sensitive information.
• Bricklayer accounts. When you create an account we store your email address, a scrypt hash of your password (never the password itself), your display name, and any profile photo you upload. If you sign in with Discord, we store your Discord user ID, username, avatar, and email address if Discord has verified it. Signing in sets a bricklayer-session cookie for up to 30 days; only a one-way hash of it is stored. Account data is kept in a Postgres database hosted by Neon. We email you through Resend only for your account: a link to confirm your address, a link to reset your password when you ask for one, and a note when your download is approved. Those links work once and expire, and only a one-way hash of each is stored.
• Download requests. The region, computer, optional Discord username, and note you enter are saved on your account and emailed to the developer through Resend, so your request can be reviewed and your download made available on your account page. They are not shared or used for marketing.
• Help-forum posts. Threads and replies you post are public and show your display name and profile photo. Your posts are sent to Inception Labs (or Groq, as a backup) so Brick can reply, and when a thread is escalated, its recent messages are emailed to the developer through Resend. You can delete your own messages, or ask to have a thread or your account removed through the contact form. Do not post passwords, API keys, or private files.
• Technical and security information. Our hosting and security systems may process IP address, request headers, timestamps, and error or rate-limit information to deliver the Services, prevent abuse, and troubleshoot failures. The chat rate-limit record is kept in server memory for about one minute.
• Update checks. Bricklayer Editor may contact the update service with its platform, release channel, and installed build identifier to determine whether an update is available.

Bricklayer Editor runs on your computer. It has no telemetry: it does not send usage data, crash reports, your projects, or your prompts to Bricklayer. What it does send, and to whom, depends on what you ask it to do:

• AI providers you choose. When you chat with an agent or ask it to work on your game, your messages and the project content the agent needs to answer — such as scripts, instance trees, and properties read from Roblox Studio — are sent to the provider or agent you selected (for example OpenRouter, OpenAI, a coding agent you installed such as Claude Code or Codex, or a local model through Ollama, which stays on your computer). That provider processes it under its own terms and privacy policy. Bricklayer does not receive a copy.
• API keys. Keys you enter are stored on your computer in a file in your user profile, readable only by your Windows or macOS account, and are sent only to the provider they belong to.
• Roblox Studio. The Editor talks to Studio through a connection on your own computer (localhost). It may call Roblox’s public web APIs to look up the name and details of a game you open.
• Updates and extensions. A copy installed from the Microsoft Store is updated by the Store. Other copies check the update service described above. If you browse or install editor extensions, those requests go to the Open VSX registry.

Uninstalling the Editor removes the app. Your projects, settings, and stored keys stay in your user profile until you delete them; you can sign out of a provider in the Editor at any time to delete its stored key.

• Operate, secure, maintain, and improve the Services.
• Remember your heart and Terminal beta-request choices, and display their aggregate counts.
• Answer a support question you choose to send through Brick or post in the help forum.
• Measure aggregate site traffic and make the site work across devices.
• Comply with legal obligations and protect Bricklayer, its users, and the public.

We do not sell personal information or use it for targeted advertising. We share information only as needed to run the Services:

• Vercel hosts the site and provides aggregate web analytics.
• Inception Labs processes messages submitted to Brick so it can generate a response, with Groq as a backup when Inception is unavailable.
• Neon hosts the Postgres database that stores accounts, download requests, help-forum threads, and anonymous article-feedback counts.
• Upstash stores aggregate heart and Terminal beta-request counters.
• Discord verifies your identity if you choose to sign in with Discord.
• Resend delivers contact-form messages and help-forum escalation emails to the developer.
• GitHub hosts release downloads and the public update manifests.
• We may also disclose information when required by law or to protect rights, safety, and security.

These providers process information under their own terms and privacy notices. In particular, review Vercel’s Privacy Policy, Inception’s Privacy Policy, and Groq’s policies and notices before using their services.

We retain information only for as long as reasonably needed for the purpose described above. Functional preference cookies last up to one year unless you clear them. The site does not create a Bricklayer user account or add Brick chat messages to a Bricklayer database. Our providers may retain operational information under their own policies.

You can clear the functional preference cookies in your browser settings, avoid using the support chat, and choose not to download the Editor. Depending on where you live, you may have rights to request access, correction, deletion, or other controls for personal information we hold. We will honor applicable rights requests after verifying them where appropriate.

The Services are not designed to collect personal information from children. If you are a minor, ask a parent or guardian to help you decide whether to send information through Brick. If you believe a child provided us personal information, contact us and we will review the request.

Bricklayer and its service providers may process information in countries other than yours. Where required, applicable service-provider transfer safeguards are described in their own privacy notices.

We may update this policy as Bricklayer changes. The revised version will appear here with a new “Last updated” date. For privacy questions or requests, open an issue through the Bricklayer issue tracker. Please do not put sensitive information in a public issue; ask for a private contact method instead.

See also the Terms of Service.