Skip to content
CODEBRICK.

Privacy Policy

Effective January 1, 2027 · Version 2026-11-05

This policy explains what Codebrick LLC ("we", "us") collects when you use CODEBRICK, the BRICKBOT assistant and BRICKBOT for Revit (its Revit add-in), how we use it, who we share it with and the choices you have. It is written for California residents and applies to everyone who uses the service.

Information we collect

We collect the following categories of personal information:

  • Identifiers: your name, email address, account ID and, if you connect Revit, a device sign-in for the add-in.
  • Account and commercial information: workspace membership, role, plan, credit balance and purchase history. Card details go straight to Stripe; we keep only a Stripe customer reference.
  • Content you provide: project profiles and addresses, uploaded files such as drawings and PDFs, chat messages with BRICKBOT and images attached to them, flagged answers and library notes, office standards, and anything BRICKBOT sends from a Revit model on your instruction.
  • Records of what you accepted: which version of these terms, this policy and the in-app notices you accepted, and when.
  • Usage and device information: pages visited, actions taken, credits used, timestamps, IP address, browser and operating system, kept in our own database and server logs.
  • Professional information: your firm and role, and your statement that you are, or work under, a licensed design professional.

We do not collect sensitive personal information such as government IDs, precise geolocation from your device, or health or biometric data, unless you put it in a file or message yourself. Please do not upload more personal information about other people than your project needs.

How we use it

  • to run the service: sign you in, keep your projects, answer BRICKBOT questions, drive the Revit add-in, meter credits and bill you;
  • to research your project site and applicable codes when you ask;
  • to understand how the service is used, with first-party usage records kept in our own database (no third-party analytics, ad pixels or session replay);
  • to keep the service secure, prevent abuse and debug problems;
  • to send service messages such as confirmations, password resets, invitations and billing notices;
  • to comply with the law and enforce our Terms of Service.

Product improvement is off unless your workspace turns it on. A workspace admin can turn on "Help improve CODEBRICK" in Settings. Only then may we use de-identified project content, chats and edits from that workspace, for product improvement only. We never sell your data. We share de-identified data with partners only if your office admin turns that on. Files marked "Do not use for training" (on by default for every file), chats in which BRICKBOT used such a file, projects marked confidential in their project settings, and your code books (with the chats that quote them) are always excluded. We record who turned the setting on or off and when; turning it off stops new use and marks the workspace's data for removal from anything not yet used.

A chat you share to a project Library can add its code answers to our shared library of code answers, with the project’s name, number, address and owner removed, kept as unverified until a platform admin checks them. Private chats, and chats that used a "Do not use for training" file, never do.

AI processing

BRICKBOT's answers are generated by Anthropic's Claude models. When you send a chat message, upload a file used in a chat, or ask for research or a Revit action, we send Anthropic the content needed to answer: your message, the relevant project profile, excerpts of active project files and code data. You see a notice about this before your first chat message or upload. Anthropic's Commercial Terms of Service state: "Anthropic may not train models on Customer Content from Services."

Where your data is stored

Our website's servers run in Vercel's Washington, D.C. region in the United States. Your data is stored with Supabase (database and files); the storage region will be stated here once confirmed.

Who we share it with

We share personal information only with service providers that process it for us:

  • Supabase: database, authentication and file storage;
  • Vercel: hosting of the website and its servers;
  • Anthropic: the AI model that answers BRICKBOT requests, as described above;
  • Stripe: payments and billing;
  • Cloudflare: Turnstile, which checks that a sign-up or password reset comes from a person;
  • Google Workspace: our email, for service messages and messages you send us.

Site research also looks up your project's address with public government data services (for example county assessor and city zoning maps); we send the address or parcel, not your identity.

The coverage map (the public Is my city covered? page, which anyone can open without an account, and Admin › Jurisdictions) loads its map tiles from OpenStreetMap, so your IP address is sent to OpenStreetMap. An address you look up on that page is sent to the US Census Bureau geocoder to find its city. We don't save the address.

Within your workspace, members and admins can see the projects and content that belong to it. We may also disclose information when the law requires it, to protect our rights or safety, or as part of a merger or sale of the business.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We have not done so in the preceding twelve months.

Sharing with partners is off unless your workspace turns it on. We never sell your data. We share de-identified data with partners only if your office admin turns that on. That setting, "Allow sharing de-identified data with partners" in Settings, is off by default and separate from "Help improve CODEBRICK". Only when it is on may we share de-identified data from that workspace with partners: project content, chats and edits with names, email addresses, street addresses, project names and numbers, and other details that identify a person, a client or a project removed. Files marked "Do not use for training", chats in which BRICKBOT used such a file, projects marked confidential, and your code books (with the chats that quote them) are always excluded. We record who turned the setting on or off and when; turning it off stops future sharing, but data already shared cannot be recalled. Today no data is shared with any partner.

Cookies

We use only the cookies and browser storage needed to run the service. See the Cookie notice for the full list.

Retention

  • Account, workspace and project content: while your workspace is active, until you delete it or ask us to;
  • Deleted files and projects: removed from the service at once; copies in routine backups age out within our backup cycle (we keep the most recent ten backups);
  • Billing records: as long as tax and accounting law requires;
  • Records of what you accepted, and security and audit logs: as long as needed to show what was agreed and to protect the service.

Export and deletion

You can download your project files from the app at any time and delete files, projects or your account. To get a copy of your data or have it deleted, email legal@codebrick.ai from the address on your account. We keep only what the law or the retention list above requires.

Security

Data is encrypted in transit and at rest with our hosting provider, access to every record is restricted by workspace and role at the database level, and secrets are kept on the server. No system is perfectly secure; tell us at legal@codebrick.ai if you believe your account has been compromised.

Your California privacy rights

If you live in California, the California Consumer Privacy Act (as amended by the California Privacy Rights Act) gives you the right to:

  • Know what personal information we collect, use and disclose about you, and receive a copy;
  • Delete personal information we hold about you, subject to legal exceptions;
  • Correct inaccurate personal information;
  • Opt out of the sale or sharing of your personal information. We do not sell or share it, so there is nothing to opt out of;
  • Limit the use of sensitive personal information. We do not use it beyond what is needed to provide the service;
  • Not be discriminated against for exercising any of these rights.

To exercise a right, email legal@codebrick.ai from the address on your account, or mail Codebrick LLC, 113 W 9th St Suite 313, Los Angeles, CA 90015. We will confirm the request within 10 business days and respond within 45 days, which we may extend once by another 45 days with notice. We verify requests by matching them to your account and may ask for more detail. You can use an authorized agent; we will ask for proof that you gave them permission.

We do not respond to browser "Do Not Track" signals, as there is no common standard. We honor Global Privacy Control signals as an opt-out of sale or sharing, which does not change anything because we do neither.

Children

The service is for working professionals and is not directed at anyone under 18. We do not knowingly collect personal information from children.

Changes to this policy

We may update this policy. If a change is material we will tell you in the app or by email before it takes effect. The version at the top shows the current one.

Contact

Privacy questions and requests: legal@codebrick.ai. Help with the service: helpme@codebrick.ai. Mail: Codebrick LLC, 113 W 9th St Suite 313, Los Angeles, CA 90015.

Codebrick LLC · Effective January 1, 2027