Skip to content
Bitfield Creek Labs

Privacy Policy

Last updated September 27, 2026

Overview

Bitfield Creek Labs is a trade name of Halo Softworks LLC. Halo Softworks LLC, 33973 North Shawnee Ave, Grayslake, IL 60030, is the company responsible for the information described in this policy.

Bitfield Creek Labs builds local-first software: Aura Wire AI Command Center, a Windows application with a small local Host program; Aura Terran Knowledge, a Windows application; and the free, open-source Bitfield Ollama Agent command-line tool. Your documents, prompts, chat history, project files, and provider API keys stay on your machine when you use them. We do not operate a cloud corpus for either product, and we do not receive your chat contents or keys.

This policy describes information we collect through bitfieldcreek.com, our support channels, license activation, and the small set of operational requests the products make to us — not data they process locally on your machine. Local handling of prompts, documents, and API keys is covered in Our products below; the exact requests each product makes are listed under Requests our products make.

Our products: prompts, documents, and API keys

Aura Wire AI Command Center and Aura Terran Knowledge are designed so that sensitive work stays on your device. That is a product design choice, not an absolute guarantee against every possible misconfiguration or third-party practice. In particular:

  • Prompts and responses — Aura Wire AI Command Center sends your request to the AI provider you configure and processes the request in memory. Chat history you keep in the extension is stored in your editor’s extension-storage folder on your machine. The Host’s traffic records keep sanitized metadata (provider, model, tokens, latency, cost estimates), not prompt or response bodies; the extension’s Privacy Audit shows you exactly where each file lives. Bitfield Creek Labs does not receive your prompts, responses, or chat history.
  • Documents and corpora — Aura Terran Knowledge indexes folders you choose on your PC and stores the index there. Document contents, file names, paths, and search queries are not uploaded to Bitfield Creek Labs.
  • API keys and credentials — Keys and tokens you enter for OpenAI, Anthropic, Cursor, Copilot, Ollama, Gemini, or other providers are stored locally on your device for those connections. We do not collect or store your provider API keys on our servers.
  • Providers you choose — When you send a request to a third-party AI provider you configure, that provider receives the request content under their terms and privacy policy. Our products do not replace those policies. Optional features that call other services — Aura Terran’s web search, or external MCP servers you add — send your query to that service when you turn them on.
  • Bitfield Ollama Agent — the command-line agent sends no data to Bitfield Creek Labs. Its only network traffic is to the local Ollama server and any MCP servers you configure. It writes session notes and a project index into a .halo-agent folder inside the workspace you run it in.
  • De-identified operational events — the products send a small number of de-identified events (install, still-running, version) as described below. Those events do not include documents, prompts, chat history, keys, or corpus contents.

For how the website and checkout collect information, see the sections that follow.

Information we collect

When you purchase a license

Checkout is processed by Stripe. We receive your email address, payment status, and metadata needed to issue a license (product, tier, seat count). We do not store full payment card numbers on our servers.

When you start a trial or activate a license

Starting the free trial from inside Aura Wire AI Command Center or Aura Terran Knowledge sends the product id, a random device identifier generated by the product, and the product version to our license API so the trial can be issued once per device. Activating a purchased license sends the same fields plus your license key. We use this to enforce seat limits and to help with support. No account is created and no email address is required for a trial.

Requests our products make

Each request below goes to bitfieldcreek.com or to our release CDN, is best-effort, and does not stop the product from working if the network is unavailable. Like any HTTPS request, they carry connection metadata (IP address, user agent) that our hosting provider processes for delivery and security; we do not join that metadata to the event fields for profiling.

Aura Wire AI Command Center (Windows app, optional editor extension, and Host)

  • Host download — on first use the extension downloads the Host program for your operating system from our release CDN and verifies its checksum.
  • Update check — the extension reads our release feed when it starts and about once an hour to learn whether a newer Host is available. Updates install only when you accept them.
  • Installation events — installed, first getting-started view, Host ready, Host download succeeded or failed, update check, and a once-a-day “still active” ping. Each carries a random installation id created by the extension, the extension version, an OS label, whether the run was an update, the install channel, the editor family (VS Code, Cursor, Codespaces, other), and whether the editor was installed locally or running in a browser.

These events do not include usernames, machine names, workspace names, file paths, chat text, or provider keys.

Aura Terran Knowledge (Windows application)

  • Installer events — the setup wizard reports that installation succeeded, with a random per-run installation id, installer version, numeric Windows version, and whether the run was an update.
  • Lifecycle events — session start and session end (with approximate run time), and one notice when you uninstall. Each carries the product id, app version, an OS label, and a random device identifier stored in the app’s data folder.
  • Update check — the app checks our release CDN about every four hours, downloads a newer version in the background when one exists, and installs it the next time you quit the app.
  • Embedding model download — the first time you index documents, the app downloads its on-device embedding model once from huggingface.co (a third-party model host) into the app’s data folder. Hugging Face receives the connection metadata for that download under its privacy policy; none of your documents are involved. Indexing and search then work offline.
  • Configuration of other programs — only when you click the one-click MCP setup, the app adds an entry to Cursor’s or Claude Desktop’s MCP configuration file. It does not read or send the rest of those files.

These events do not include document names, paths, contents, search queries, or provider keys.

Voluntary crash reports

If Aura Terran Knowledge hits an unhandled error, it may show an error report screen. A report is sent to us only if you choose Send. Reports include sanitized error text and stack frames (user paths redacted), product and version, an OS label, and the same random device identifier — not your documents, queries, or prompts.

Information we collect on the website

When you contact us

Support tickets and email include the address and message you provide, plus optional product selection. If Turnstile is enabled on the contact form, Cloudflare may process a bot-check token.

When you download software

We may log anonymous download events (product, asset type, version label, and referring URL when the browser sends one) for release analytics. Installers, the Host program, and extension packages are served from our CDN or edge storage; we do not receive your local file system contents.

When you email yourself a download link

On phones and tablets, you can ask us to email a product download page link for opening on a Windows PC. We store the email address you provide, the product, and an opaque link token so we can send that message and (if you have not downloaded or installed yet) one reminder about 36 hours later. This is not a marketing list. We clear the email after the reminder is sent, or after 30 days, whichever comes first. A short-lived first-party cookie (halo_dl_lead) may remember the link token on the PC so we can stop reminders once you download.

Site usage (first-party analytics)

When you allow analytics cookies, we record first-party page-view events on this site (path and referring URL when available) and clicks on download and purchase buttons (which button, product, and page) to understand aggregate traffic and conversion. These events are stored in our own database and are not sold to third parties. We do not use them to build advertising profiles for resale.

We may also store a first-party attribution cookie (halo_attribution) with campaign parameters and landing path so we can attribute checkouts to marketing campaigns.

We use Ahrefs Web Analytics on all pages for aggregate traffic and search-referral reporting. It is cookieless and does not store an identifier on your device or build an advertising profile; Ahrefs receives connection metadata such as IP address, browser type, and the page viewed. See Ahrefs’ Privacy Policy.

Advertising measurement

When advertising integrations are enabled:

  • Google Ads (gtag.js) — loads on all pages with Google Consent Mode defaults denied (no ad cookies). After you allow marketing cookies, storage is granted so Google can measure ad-driven visits and conversions. When configured, we may also upload selected conversion events (for example extension install or trial) to Google Ads with a stored click id. See Google’s Privacy Policy .
  • OpenAI Ads measurement pixel — measures ad-driven visits and purchases. See OpenAI’s Privacy Policy .
  • Reddit Ads pixel & Conversions API — measures ad-driven visits, download intent (Lead via pixel on installer / VS Code .zip CTAs, and via Conversions API when the download is Reddit-attributed), completed installs (SignUp via server-side Conversions API when attributable), and purchases. See Reddit’s Privacy Policy .
  • LinkedIn Insight Tag — measures ad-driven visits and purchases. See LinkedIn’s Privacy Policy .

OpenAI, Reddit, and LinkedIn load only after you allow marketing cookies. These partners may receive connection metadata such as IP address and browser type, and may set or read cookies. Details and controls are in our Cookie Policy.

Like most websites, our hosting provider (Cloudflare) processes connection metadata such as IP address, user agent, and requested URLs for security and delivery.

How we use information

  • Issue, deliver, and support software licenses
  • Respond to support requests and product feedback
  • Send transactional email (license delivery, ticket confirmations, download links and one optional install reminder)
  • Prevent abuse (rate limits, optional bot checks)
  • Improve releases and understand aggregate download demand and site traffic
  • Measure advertising performance when you allow marketing cookies

We do not sell your personal information.

Cookies and similar technologies

We use essential cookies, optional first-party analytics, and optional marketing pixels as described in our Cookie Policy. You can change your choice anytime via .

Retention

License records are retained while your license is valid and as needed for accounting, disputes, and legal obligations. Support tickets are retained to provide continuity if you contact us again. Emails collected only to send a mobile download link are cleared after the reminder is sent or after 30 days; product and timing fields may remain for aggregate analytics. Analytics events are retained for operational reporting and may be aggregated or deleted over time.

Third-party services

Our products connect to the third-party AI providers you configure (OpenAI, Anthropic, Ollama, and others), and Aura Terran Knowledge downloads its embedding model once from Hugging Face. Those connections are governed by your settings and the provider’s policies, not this website policy.

Your choices

You may request access, correction, or deletion of account-related data we hold by emailing contact@bitfieldcreek.com. Refund and license revocation are handled under our Refund Policy. Software use is governed by our End User License Agreement.

Contact

Questions about privacy: contact@bitfieldcreek.com or open a support ticket.

Halo Softworks LLC (Bitfield Creek Labs)
33973 North Shawnee Ave, Grayslake, IL 60030

Agree to continue

Checkout opens Stripe for a one-time purchase. Please confirm the legal terms first.

Enlarged image