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 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.
| Who | How they get in | What Hue may use | Never | Status |
|---|---|---|---|---|
| Visitors | Not signed in | Your 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 account | Live |
| Customers | A 6-digit code sent to their email, as a contact of one account | That account’s own records, each cited | Another account, internal notes, the pipeline, Slack, staff-only fields | Early access |
| Partners | A 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 partnership | An account’s other records, anything internal | Planned |
| Your team | A 6-digit code, as a person in your company’s directory | Everything their role allows, across the systems you connect | Anything beyond their role | Early 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.
- 1Someone asks Your site or channel
On your website or another channel. Not signed in, Hue uses your public facts only.
- 2Hue works out who is asking HQ · Toronto
A signed-in person is matched to your directory as staff, a customer or a partner.
- 3It 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.
- 4The answer is phrased Anthropic API
That turn’s records go to Anthropic’s API to put the answer in words. Not used for training.
- 5It 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.
- 6A 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.
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.
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.
Every action that writes, sends or spends waits for a named person, and every action and approval is logged with who and when.
Encrypted connections everywhere, encrypted volumes for our systems, and the tokens that connect your systems stored encrypted.
Continuous backups and daily snapshots of our systems. Next: a documented, tested restore.
A public subprocessors list, and 30 days’ notice to clients under contract before a new one.
We commit to telling you without undue delay if an incident affects your data. Next: a written, rehearsed response plan.
Information security, access, data retention and vendor policies, written down and reviewed every year.
No third-party penetration test report to share yet.
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.