Security
Built for a brokerage's security review.
TruHu handles your clients' plan documents and their employees' contact details. Here is how that data is protected, where it lives, and exactly what the AI does with it, for the team that has to sign off.
Independently audited
SOC 2 Type II compliant
- TruHu
- SOC 2 Type II
- Ensemble platform
- SOC 2 Type II
- Ensemble platform
- ISO 27001
- We never sell your data or use it for advertising
- AI providers never train on your data
- Nothing reaches employees until your team publishes
- Employee pages stay out of search engines
Protected at every layer.
Controls running in production today, from the infrastructure up to the link an employee opens.
Encryption
Personal information is encrypted in transit and, where technically feasible, at rest, on secure servers in the United States.
Tenant isolation
Each organization's documents, conversations and tool data are isolated from every other's. No cross-tenant access, by architecture.
Secrets stay server-side
Credentials are encrypted at rest and managed on the server. They never reach the browser or the AI model.
Session security
Sessions are server-side and opaque, secrets are hashed, and sessions idle out after 60 minutes. Access is re-checked against live membership every 90 seconds, so someone you remove loses access mid-session.
Private by default
Benefit sites and Pages use unique, non-indexed links that never appear in search results, whether shared as a link, a QR code or an embed.
Password and MFA gating
Confidential Pages can be password-protected, with MFA required on top: a check on who sees the page, whoever the link was forwarded to.
What happens to a client's plan documents.
The AI reads, sorts and drafts. Your team decides what ships. Here is the whole path, from upload to the record it leaves behind.
- 1
Upload
Documents go into your organization's own isolated workspace, encrypted and never shared across tenants.
- 2
Read
AI providers process them under zero data retention and are contractually barred from training on them.
- 3
Build
Plan figures are filled from the source documents by rules, never by the model. Only the prose is generated.
- 4
Review
Your team confirms the plans, edits anything and publishes. Nothing reaches a client until they do.
- 5
Record
Every step is traced and every change versioned, so any output can be explained and any version restored.
No training on your data
Our AI providers are contractually prohibited from using your data to train their models.
Zero data retention
AI providers are configured to keep nothing once a request is processed.
Locked content stays locked
Locked pages are protected from AI edits and survive a rebuild. Compliance language is managed centrally, effective-dated and tracked.
Watched in production
Monitoring agents check live conversations for data leakage, PII exposure and claims the documents do not support.
Least privilege, by default.
Everyone sees what their role needs and nothing more, and access ends the moment someone is removed.
Inside the brokerage
TruHu Advisor
- Admin
- Manages teammates, roles and account configuration, and builds guides and sites.
- User
- Builds and edits guides and sites. Cannot manage teammates or configuration.
Teammates sign in with Google, Microsoft or a password. Admins invite, reset and remove users from one screen.
Inside the employer
TruHu Workforce
- Administrator
- Manages employees, Pages, messages and company settings.
- Partial admin
- Scoped to the sections they are assigned. A location manager can message their own team, not the whole company.
- Employee
- Sees what was sent to them. Can request a change to their own contact details, which an admin approves.
Every company's messages come from one recognizable number, and texts go only to the employer's own workforce.
Offboarding without data loss
Mark a departing employee Inactive: their access ends, and their acknowledgments and survey responses stay on record.
Audit trails
Delivery, opens, clicks and acknowledgments are timestamped per employee, and admins can review activity logs for the account.
Version history
The builder auto-saves and keeps a full version history, so any change can be traced and undone.
One employee record
Advisor and Workforce read the same employee table rather than keeping two copies of an employer's roster.
What we collect, and what we never do with it.
The short version of our privacy policy, for the data a broker or employer brings to TruHu.
Privacy and data requests
support@truhu.com- What we collect
- Names, email addresses and mobile numbers provided by the employer, account logins and preferences, and the activity logs behind delivery records and audits.
- Where it lives
- On secure servers in the United States, with regular routine backups.
- What we never do
- Sell personal information, use it for advertising, or share it for cross-context behavioral advertising. The platform sets only essential cookies, and we use no advertising or marketing cookies anywhere.
- Sub-processors
- A short list: cloud hosting, our database provider, email delivery and AI providers. Each processes data only to provide its service to us. The current list is available on request.
- Retention and deletion
- Data is kept only as long as it is needed, then deleted or de-identified. Requests to access, correct or delete data are answered within 30 days.
- Employee choices
- Employees can reply STOP to any text to opt out, and START to rejoin. Messages are service communications only, never marketing.
Independently audited, stated precisely.
What each audit covers, and exactly which regulations apply to TruHu.
TruHu
SOC 2 Type II
AICPA · Security and availability
Our controls are tested by an independent auditor over a period of time, not only on the day of the audit.
Ensemble platform
SOC 2 Type II
Security, availability and confidentiality
Every TruHu AI feature runs on Ensemble, the enterprise agent platform, which holds its own attestation.
Ensemble platform
ISO 27001
Information security management
The international standard for how an organization manages information security risk, certified for the platform.
Where the lines are
- HIPAA
- TruHu is not designed to hold protected health information. Advisor is built from plan documents and Workforce from employee contact details, not claims or medical records, so PHI stays out of uploads and messages.
- TCPA and CAN-SPAM
- Texts are sent on the employer's behalf, to its own workforce, and never for marketing. TruHu supports explicit opt-in and compliant implied consent, with templates and guidance.
- CCPA
- California residents, including employees whose data we process for an employer, can know, correct, delete and port their data. We do not sell or share it for advertising.
Security questions, answered.
The questions that come up in every vendor review. Anything not covered here, bring to the first call.
Report a security concern
support@truhu.comIs TruHu SOC 2 compliant? Can we see the report?
Yes. TruHu is SOC 2 Type II compliant, audited against the AICPA's security and availability criteria, and the Ensemble platform our AI runs on holds SOC 2 Type II and ISO 27001. Ask for the report when you book a call and we will walk your team through what it covers.
Does our data train AI models?
No. The AI providers we use are contractually prohibited from using your data to train their models, and they are configured for zero data retention.
Where is our data stored?
On secure servers in the United States. Personal information is encrypted in transit and, where technically feasible, at rest, and each organization's data is isolated from every other's.
Can the AI change the plan numbers?
No. Plan figures are filled from the source documents by rules, not generated by the model, and every plan table is checked against the plans your team confirms. Locked pages are protected from AI edits altogether.
Is TruHu HIPAA compliant?
No. TruHu is not designed to hold protected health information. Advisor works from plan documents and Workforce from employee contact details, not claims or medical records, so PHI should stay out of uploads and messages.
Are employee benefit sites public or searchable?
No. Sites and Pages use unique, non-indexed links that do not appear in search engines. For confidential content, add a password or require MFA.
What happens when someone leaves?
Remove a teammate and their access ends mid-session, because rights are re-checked every 90 seconds. Mark a departing employee Inactive or Terminated rather than deleting them: their access ends, their acknowledgments and records are kept, and you can still send a one-off COBRA or offboarding message.
How is consent for text messaging handled?
Employers choose explicit opt-in or a compliant implied-consent approach, with templates and guidance from us. Messages are sent by the employer, not TruHu, which is an important distinction for compliance, and every employee can reply STOP to opt out.
How do we request, correct or delete data?
Email support@truhu.com. We answer requests to access, correct or delete personal information within 30 days.
Bring the questionnaire to the first call.
Send your security questionnaire ahead of time. The first call is with someone who can answer it, SOC 2 report included.