Privacy

Privacy policy

Plain answers about the two kinds of data Cobaltian touches: the near-nothing this website collects, and the drawing packages clients send us to review.

Last updated: 2026-08-03

Read this first: this is a plain-language policy written by a one-person business, and it has not been reviewed by an attorney. It describes what Cobaltian actually does, but it should get real legal review before anyone relies on it as a legal instrument — especially where client files contain sensitive engineering or critical-infrastructure design information. If your engagement needs signed confidentiality terms, put them in place before sending anything; signed terms govern over this page.

The short version

  • This website collects almost nothing — no cookies we set, no analytics, no trackers. There's one form (contact), spam-checked by Cloudflare Turnstile. Hosting (Cloudflare) and fonts (Google) see the standard request data any site's infrastructure sees.
  • Files sent for an engagement are used for that engagement only. They are never shared without consent, and never used to train any AI model.
  • One person sees your data: Dustin, doing the work himself.
  • Want anything deleted, or want to ask something? Email hello@cobaltian-engineering.com.

What this website collects

There are no accounts, no comment boxes, and this page sets no cookies and runs no analytics scripts, tracking pixels, or ad tech. There is one form — the contact page — and email links elsewhere that open your own mail app instead.

Three pieces of infrastructure see data as a normal part of doing their job:

  • Hosting — Cloudflare. The site is served from Cloudflare's edge network. Like any host, Cloudflare processes your IP address and request logs to deliver and secure the page, and provides us aggregate traffic statistics — counts, not identities. We set no cookies ourselves; Cloudflare's infrastructure may set its own operational ones to do this job, covered by Cloudflare's own privacy policy, not something we added.
  • Fonts — Google Fonts. The page loads its typefaces (IBM Plex Sans and Mono) from fonts.googleapis.com and fonts.gstatic.com. Your browser requests those files directly from Google, which — like any web request — exposes your IP address and browser metadata to Google, under Google's privacy policy.
  • Spam protection on the contact form — Cloudflare Turnstile. The contact page runs a Turnstile challenge before a submission goes through. It runs in your browser, checks whether the visitor looks human, and reports a pass/fail token — it isn't used to track you across sites. Cloudflare's privacy policy covers what it processes to do that.

Submitting the contact form sends what you typed — name, email, company if you gave one, and your message — to us as an email. From there it's handled exactly like any other message, per "When you email us" below.

When you email us

hello@cobaltian-engineering.com is a forwarding alias: Cloudflare Email Routing receives mail sent to it and passes it along to our working inbox. When you write to us, we hold what any correspondence holds — your address, your name if you signed it, and whatever you wrote — and we use it to reply and to scope the work.

Correspondence is kept as ordinary business records. There is no mailing list to be added to; emailing us gets you a reply, not a drip campaign.

The packages clients send us

This is the part that actually matters. An engagement means sending Cobaltian real drawing packages — CAD files, PDFs, cable and panel schedules, drawing registers, transmittal records. That material is your (or your client's) proprietary engineering data, and for substation and utility work it can include sensitive critical-infrastructure design information. Here is what happens to it:

  • Used for your engagement, nothing else. Files are inputs to the review or automation work you hired us for. They are not mined for marketing, benchmarked across clients, or reused in anyone else's work.
  • Never shared without consent. No third party gets your files for their own use unless you have agreed to it first or the law compels it. There are no subcontractors — the one person who sees your package is Dustin, doing the work himself. (This doesn't count the ordinary infrastructure that stores or transmits anything sent electronically — your email provider, ours, the storage underneath it — the same way sending someone a PDF always involves the systems carrying it; none of them see it as anything but data in transit or storage, and none of them get to use it for anything.)
  • No AI pipeline runs on your files today. There's no automated checking system built yet for client files to pass through — reviews are done directly. If that changes, the plan is to run it on locally hosted models rather than a third-party cloud AI service, specifically so files don't have to leave operator-controlled infrastructure — and either way, client files are never used to train, fine-tune, or otherwise improve any AI model, ours or a third party's. This page will say exactly what's live before it changes.
  • Kept confidential, described honestly. Files are handled as confidential client material and live in standard, reputable business email and file storage. This is a one-person operation, and we won't dress that up: there is no SOC 2 report or ISO 27001 certificate here, and we would rather say so plainly than imply otherwise. If a package needs specific handling — a particular transfer method, a storage constraint, a deletion schedule — raise it before sending and we will agree to it in writing.
  • Flag regulated material before sending. If a package includes information your client or a regulator treats as restricted — CEII-designated material, for example — say so up front so handling can be agreed first.
  • Retention. Files are deleted within 90 days of an engagement closing, unless you ask for it sooner — either way, deletion is confirmed when it's done. What remains afterward is the work product we delivered to you and ordinary business records, like correspondence and invoices.

What we don't do

  • Sell personal information — visitor data, client data, or contact lists. There is nothing here built to.
  • Run ads or ad networks, or share anything with data brokers.
  • Profile visitors, or build marketing audiences out of correspondence.

Questions and deletion requests

Email hello@cobaltian-engineering.com to ask what we hold from your correspondence or engagement, to have emails or files deleted, or to question anything on this page. There is no portal and no ticket queue — a person reads it and answers, and deletion requests are confirmed once they are done.

Where this applies

Cobaltian is a Texas-based business serving other businesses — mostly electrical and MEP engineering firms, substation P&C teams, and EPC electrical teams in Texas and the wider Gulf South, with remote engagements elsewhere in the US considered. This site is not directed at consumers or at audiences outside the US.

We aim to honor the plain intent of US state privacy laws — the Texas Data Privacy and Security Act and the California Consumer Privacy Act are the kind of thing we mean — whether or not a given statute technically applies to an operation this size: clear disclosure, no sale of personal information, and deletion requests that get honored.

Changes to this policy

Cobaltian is a small operation, and this page describes its practices at today's size. As the business grows — new tooling, more people, new ways of taking in work — this policy will be updated to match, with the date at the top changed. If the way engagement files are handled ever changes materially, active clients hear about it from us directly, not by diffing this page.