What we collect

This page explains, in plain terms, the two kinds of information our products may send over the network — and, just as important, what they never send. Delta1 Labs is a trade name of COREBRIDGE SOFTWARE LLC; references to “we” or “us” mean COREBRIDGE SOFTWARE LLC. For the formal statement, see our Privacy Policy.

There are only two things a Delta1 Labs product talks to the network about. They are completely separate, and we keep them that way on purpose:

1. Licensing & activation calls (functional — always happen)

When you activate or validate a license, the product contacts the licensing service. This is a functional part of how a licensed product works — without it, a paid license can’t be activated, checked, or kept valid. It happens whether or not you’ve turned off usage telemetry, because it isn’t usage telemetry.

What a licensing call involves:

• Your license key — so the service knows which license is being used.
• A machine fingerprint — a value derived from the computer, used to bind the license to the seats you’ve activated and to enforce how many seats are in use. It identifies a seat, not a person.

This is not usage tracking. These calls exist only to issue, activate, validate, and renew your license. They do not report what you do with the product — not the code you protect, not the assemblies you open, not the features you use.

If you need a deployment with no licensing calls at all, an offline signed license file removes them entirely — see the product’s licensing documentation. Air-gapped machines make no outbound calls of any kind.

2. Anonymous usage telemetry (optional — evaluation / free use only)

Separately, our products can send a small amount of anonymous usage telemetry that helps us understand what’s actually used and decide what to build next. It is optional, it is limited to evaluation and free use, and it is designed so that it can never identify you.

It is only ever eval / free — and it stops when you license

Usage telemetry is sent only during evaluation or free use. The moment a paid license is applied — Nebula Pro, or a paid Keyright self-hosted deployment — it latches off and stays off. A paying customer’s product does not send usage telemetry at all.

What it is — and what it is never

What it is: a handful of coarse, aggregate usage signals — things like how often the product ran and which broad features were exercised — tied to a random install identifier generated on the machine. That identifier is random: it carries no account, no machine identity, and no user identity, and can’t be traced back to you.

What it never includes:

• Your source code or the assemblies you protect, decompile, or open.
• File names or paths, project names, or anything about your work.
• License keys or activation details.
• Any customer data or personal information.

How to turn it off

It’s opt-out, and turning it off is simple:

• Glass.NET — a checkbox in Settings.
• Keyright (self-hosted) — an instance setting you control on your own deployment.
• Nebula.NET (free edition) — set the environment variable NEBULA_NO_TELEMETRY=1, which disables the analytics call completely. (Paid editions don’t send it in the first place.)

Air-gapped and offline instances send nothing at all. With no network available there is no outbound call to make — not for telemetry, and not for anything else.

Questions?

If anything here is unclear, email support@delta1labs.com and we’ll be glad to explain exactly what a given product does.