What Hue reads, who sees it,
and what we have not done yet.

The facts behind Hue: where it runs, how an answer is made, who may sign in and see what, the terms we sign, and where we stand on SOC 2.

In short

Where Hue runs
Hue’s chat, sign-in, transcripts, widget and channels run on Humonix HQ, hosted on Fly.io in Toronto, Canada (region yyz). HQ does not keep a copy of your systems: it reads the records a person may see when they ask, and keeps the conversation.
How an answer is written
Hue reads the records first, then sends that turn’s records to Anthropic’s API (Claude) to phrase the answer. Your records are never used to train a model.
Read-only by default
Hue never changes a record on its own. Anything that would write, send, spend or publish becomes a proposal that a named person approves, and the approval is logged.
Every answer cites its record
The system and the reference behind each answer, one tap away, so anyone can check it.
Proofs you can re-check
In proof mode Hue answers yes or no without showing the values. Each answer carries an attested hash commitment: a salted SHA-256 fingerprint of exactly the records it read, which your team can re-check later. It is selective disclosure, not a zero-knowledge proof.
It says it is an AI
On every channel, and it offers a person when someone asks.

Where your records live

Your records stay in your own systems and, once connected, in your Allometry workspace, which holds the rules of who may see what and logs every read. Hosting for workspaces is being set up, so we do not state a region for it yet; this page will say where once it is live. Until a workspace is connected, your Hue answers from your public pages only.

Who can sign in, and what they see

The same Hue answers everyone. What it may use depends on who is asking, and it is checked on every answer, not only at sign-in.

WhoHow they get inWhat Hue may useNeverStatus
VisitorsNot signed inYour public pages, public files and public price list. It can take a lead, book a call or hand off to a person.Anything about any accountLive
CustomersA 6-digit code sent to their email, as a contact of one accountThat account’s own records, each citedAnother account, internal notes, the pipeline, Slack, staff-only fieldsEarly access
PartnersA 6-digit code, as a contact of one of your partners (supplier, distributor, referral partner)Public facts, plus exactly the records you shared with that partnershipAn account’s other records, anything internalPlanned
Your teamA 6-digit code, as a person in your company’s directoryEverything their role allows, across the systems you connectAnything beyond their roleEarly access

Codes are stored only as a keyed hash, expire after 10 minutes and allow 5 tries; 10 failed tries in 24 hours lock the address. A session lasts 8 hours, and only a hash of it is kept. The chat on humonix.com is always in public mode: signed-in answers run in your own Hue widget, which only loads on the domains you list.

How your data moves

One question, from the moment it is asked to the answer, and where each step happens.

  1. 1
    Someone asks Your site or channel

    On your website or another channel. Not signed in, Hue uses your public facts only.

  2. 2
    Hue works out who is asking HQ · Toronto

    A signed-in person is matched to your directory as staff, a customer or a partner.

  3. 3
    It reads only what they may see Your systems

    Your workspace applies the rules of who sees what and logs the read. Nothing else is fetched.

  4. 4
    The answer is phrased Anthropic API

    That turn’s records go to Anthropic’s API to put the answer in words. Not used for training.

  5. 5
    It answers with the source Your site or channel

    Each answer cites its record; in proof mode, a yes or no with a commitment you can re-check.

  6. 6
    A person approves any change Your team

    A write, a send or a payment becomes a proposal for a named person. Every approval is logged.

Data processing terms

Hue is covered by the same data processing terms as every Humonix service. You control your data and decide why it is processed; we process it only to run Hue for you, on your instructions. The signed agreement governs.

Subprocessors
Fly.io hosts Hue and Anthropic phrases its answers. Texts and calls add Twilio, the voice agent adds ElevenLabs, and email notifications use Resend. The full list is public, and clients under contract get 30 days’ notice before a new one that handles their data, and can object.
Data leaving Québec or Canada
Some providers, including the AI model provider, may process data outside Canada. We tell you which ones touch your data and support the privacy impact assessment Québec’s Law 25 requires before such a transfer.
Requests and incidents
We help you answer access, correction and deletion requests from your customers and staff, and tell you without undue delay if an incident affects your data.
When you leave
Your facts, transcripts and settings export in open formats. We delete them from our systems within 30 days, except what the law requires us to keep, and confirm it in writing.

SOC 2: not certified, and here is where we are

Hue is not SOC 2 certified, and there is no SOC 2 report to share yet. This is our readiness list against the SOC 2 control areas, marked honestly. Ask us for the current status.

Access controlIn progress

Sign-in by emailed code, codes and sessions stored only as hashes, lockout after repeated failures, least-privilege access per module. Next: written access reviews.

Change approval and audit logIn progress

Every action that writes, sends or spends waits for a named person, and every action and approval is logged with who and when.

EncryptionIn progress

Encrypted connections everywhere, encrypted volumes for our systems, and the tokens that connect your systems stored encrypted.

Backups and recoveryIn progress

Continuous backups and daily snapshots of our systems. Next: a documented, tested restore.

Vendor managementIn progress

A public subprocessors list, and 30 days’ notice to clients under contract before a new one.

Incident responseIn progress

We commit to telling you without undue delay if an incident affects your data. Next: a written, rehearsed response plan.

Written security policiesPlanned

Information security, access, data retention and vendor policies, written down and reviewed every year.

Independent penetration testPlanned

No third-party penetration test report to share yet.

SOC 2 auditPlanned

An audit by an independent firm, once the controls above have run long enough to be tested. No date set.

Questions, a questionnaire, or a problem to report

Tell us through the contact form. We answer security questionnaires on reasonable request, and typically reply within one business day.

Last updated: October 27, 2026. Summary only; the signed agreement governs.