HaloHalo
HaloHALOCHAT / TECHNICALS

The boring stuff, explained plainly.

What happens when you press send on HaloChat.

No hand-waving. This is the request path, with boundaries at every step — and why a genuinely private AI service costs more and can feel less instant than the free alternatives.

The request path

Five ordinary steps. A lot of backend magic underneath.

01

You press send

Your message travels to HaloChat over TLS 1.3, required with no fallback on the connection to Halo. Outbound legs from Halo to third-party model providers prefer TLS 1.3 and permit TLS 1.2 only with a modern, forward-secret cipher suite. No hybrid post-quantum key exchange runs on this TLS connection today.

02

Your account is validated

The email address you supply (personal or otherwise) is simply an access credential: it authenticates your access, helps measure your usage, and supports service delivery. HaloChat does not need a personal profile or your personal details to answer your question.

03

The request is prepared

Your request is checked and sent through the service’s protected processing path. Your message and recent turns of the conversation (from your device) are sent so the model can answer.

04

The message is briefly decrypted

No AI model can read an encrypted message. Thus, your message needs to be decrypted briefly inside the processing boundary so the request can be understood and an answer can be produced.

05

Your tailored answer comes back over an encrypted connection.

The response travels back over an encrypted connection. Halo does not keep an ordinary, persistent server-side archive of your prompts or answers.

Where browser storage is supported on your device, history remains encrypted there; otherwise, it lasts only for the session. Anyone with access to your unlocked device or browser can read it, and signing out does not clear it.

The privacy boundary

Your prompts and answers are yours to control.

Halo does not train on your conversations. Requests to third-party model providers are sent with a zero-data-retention request setting (we ask; we have not verified each provider’s handling), and what a provider keeps is governed by its own terms; search queries go to a search provider under its own terms.

  • Requests pass automated safety screening. It can miss harmful content and can refuse safe content.
  • Requests flagged by automated screening are refused; screening is not complete. No safety system can guarantee that misuse never occurs.
  • Your request is processed only briefly so the model can produce an answer.

No Halo training collection

Halo does not build a training collection from ordinary customer conversations.

No persistent content archive

Halo does not keep an ordinary, persistent server-side archive of your prompts or answers. Where browser storage is supported, history stays encrypted on your device; otherwise, it lasts only for the session. Anyone with access to your unlocked device or browser can read it, and signing out does not clear it.

Email for the service

The email address you supply (personal or otherwise) is simply an access credential: it authenticates your access, helps measure your usage, and supports service delivery. You are the customer, not the product.

The honest caveat

Encryption protects your message while it travels.

No AI model can read an encrypted message. It must be decrypted briefly for processing, then the answer is encrypted again on its way back.

“Not stored by Halo” is not the same as “never processed.” Ask any AI service how it handles processing, retention, and training before sending sensitive material.

Some frontier providers say they “cannot rule out that de-identified data derived from usage of our products helped improve our models.” That is not an admission that anyone read a particular user’s work. It is a reminder that de-identified does not mean commercially irrelevant.

Removing your name or account details does not remove the value of your code, research, strategy, or business knowledge. It may still be retained, reviewed, or used to improve a model, depending on the provider’s settings and terms.

Why privacy is not cheap

The shortcut is to collect your queries, train models on them, and make you the product.

Privacy means paying for the less convenient choices: encrypted transmission, protected processing, device-held history, limited account information, and a service that does not keep your conversations around to make the next answer easier to generate.

That can affect turnaround time and memory. If HaloChat does not keep a server-side conversation archive, a thread may need to be sent again from your encrypted device history. Preparing and securely processing that context can take longer, and longer conversations can require more work.

Common provider patterns and the HaloChat approach
Privacy questionCommon provider patternHaloChat approach
Model improvementSome services offer an opt-out for new chats, subject to their terms and exceptions.Halo does not build a training collection from ordinary customer conversations.
De-identificationNames or account details may be removed before retained data is reviewed or used for model improvement.Halo’s promise is more direct: ordinary customer conversations are not used to build a Halo training collection.
Chat historyTraining controls may be separate from account history, temporary retention, or review processes.No persistent Halo server-side archive; history stays encrypted on your device when supported, or is session-only otherwise.
SettingsControls vary by product, account type, region, and settings path.HaloChat’s privacy boundary does not depend on finding and enabling a customer-side training toggle.
ProcessingEncrypted messages still need to be decrypted briefly for a model to produce an answer.Same technical reality: requests are processed briefly, then the answer is encrypted on its way back.

Read the exact provider policy before sending sensitive material. “Paid” alone is not a privacy guarantee.

HaloChat is not designed to be the cheapest or fastest option for every request, and it does not pretend to be.

encrypted in transitdevice-held historynot always cheapestnot always fastest

Two products, two boundaries

HaloChat is a service. HaloBusiness is an environment.

HaloChat is designed for consumer questions and personal work. The minimum context needed for a live request may be sent to an eligible AI model or search provider, and the request is processed briefly.

HaloBusiness is a planned, separate product for companies. It is not yet available.

See the HaloBusiness boundary

The short version

What Halo promises — and what it doesn’t.

We do promise

No Halo training collection built from customer conversations. No persistent Halo prompt/completion archive. Your email is used for account authentication and service delivery. You are the customer, not the inventory.

We do not promise

That a request is never decrypted for processing, that privacy is free (or easy), or that device-held history gives you instant server-side memory. Privacy can mean more deliberate processing and more turnaround time.

Still have questions?

Reach out to us — we are friendly!

Ask our limited service guide about HaloChat’s privacy boundary, processing, and availability.

Talk to Halo