Privacy Policy

Effective September 24, 2026

BuilderCo, Inc. ("BuilderCo," "we," or "us") describes here how we handle information when you visit builderco.inc or use the limited BuilderCo Gold Agent pilot in Microsoft Teams. The Teams pilot is currently restricted to one allowlisted BuilderCo account and is not a public service.

Information from the website

Connection and security logs. When your browser requests a page or asset, our web host can receive the IP address, requested URL, date and time, browser and device details, and referring page. The site host may record this information in ordinary server logs to deliver the site, diagnose errors, and protect it.
Fonts. The site requests typefaces from Google Fonts. Google may receive your IP address, browser details, and the requested font as it delivers those files. The site does not use Google Analytics or advertising trackers.
Email you choose to send. The contact link opens your email application. If you email us, we receive the address and message you send and use them to respond and handle the business inquiry.

The public site is a static information page. It has no account registration, contact form, advertising cookies, or analytics code. The short identity video is served as a site asset.

Information in the Teams pilot

The pilot processes messages that the allowlisted user sends directly to the bot, together with the Teams tenant and user identifiers, conversation identifiers, timestamps, and technical message metadata needed to authenticate and respond. It does not read mailboxes, OneDrive, SharePoint, Teams channels, or other Microsoft 365 content. File attachments are disabled, and the pilot has no Planner task creation or scheduled intake.

Messages pass through Microsoft Teams and the Microsoft Bot Framework service, then through a temporary Microsoft Dev Tunnel to the Eve runtime on Jared's Mac. The agent is configured to send message content to a local oMLX model on that Mac, with no cloud-model fallback. Eve's default local workflow store keeps session state under the project’s .eve/.workflow-data directory for continuity. No automatic expiration period is configured for that local store.

The Eve command-line tool also sends limited product telemetry to Vercel: Eve version, operating system and CPU architecture, the CLI command and outcome, whether the agent connection is local or remote, and random session, installation, and project identifiers. Eve's telemetry documentation says it excludes prompts, agent files, URLs, request headers, environment variables, file paths, and file contents. See Vercel's Privacy Notice.

The Teams pilot is for internal evaluation. Do not send credentials, payment-card data, health information, personnel or HR information, ongoing legal material, or confidential information about other people.

Service providers

We use service providers to operate the site and pilot, including the VPS web host, Google Fonts, Microsoft Teams and Bot Framework, Microsoft Dev Tunnels, Vercel for Eve CLI telemetry, and email providers used when messages are sent to or received from us. These providers handle information under their own privacy terms and as needed to provide their services.

Use, sharing, and retention

We use information to operate and secure the website and pilot, answer inquiries, troubleshoot problems, and meet legal obligations. We do not sell personal information or use it for targeted advertising. We share information with the service providers above and when required to protect rights, safety, or comply with law.

Website logs are kept as needed for operations and security; a fixed public retention period has not been set. Teams conversation state is stored locally on the pilot Mac and is not configured to expire automatically. Email correspondence is retained as needed to respond and maintain business records. You can email us to request access, correction, or deletion; we will review and respond to the request.

Security and changes

We use reasonable technical and organizational measures for this limited service, including HTTPS for the public site and authentication and a single-user allowlist for the bot. No internet service can be guaranteed completely secure. We may update this policy as the site or pilot changes; the effective date above identifies the latest version.

Contact

Questions or privacy requests: info@builderco.inc.