Security & readiness
Claims that match the controls.
Each control is labeled by where it stands. In the code today means it runs in this application and the demo, with tests. In build means it is being built for the pilot. Planned means not built. The marketing site and the public demo contain no customer data.
| Area | Control | Status |
|---|---|---|
| Confirmation enforcement | Rules in application code block confirming or sending by anyone but the file's agent (or a confirmer the team added), by the assistant, on expired or edited drafts, to opted-out recipients, and in non-operational states. Sending states are one-way and ordered. Covered by automated tests and exercised by the demo. | In the code today |
| State eligibility | Availability is a data record with status, enabled workflows, who confirms, and a last-verified date. Unknown states resolve to unavailable. Enforced in code, not only in banners. | In the code today |
| Sensitive data rules | The assistant does not accept government IDs, account numbers, or payment details by text and never delivers earnest-money or wire instructions. A product rule applied in the demo; enforced in the pilot build. | In build for the pilot |
| Audit log | Log of requests, drafts, versions, confirmations, discards, expirations, sends, deliveries, and replies, exportable per file. The demo derives each message's record from its fields; the persistent log is being built. | In build for the pilot |
| Authentication | Production sign-in for pilot agents with session rotation and device revocation. This site exposes no sign-in and holds no customer data. | In build for the pilot |
| Data isolation | Every file, message, and confirmation scoped to one agent or team, with cross-account reads rejected at the data layer. | Planned |
| Roles and permissions | Agent, team confirmer, and admin roles with least-privilege defaults. Assistant actions recorded as a distinct system actor. | Planned |
| Document storage | Documents encrypted at rest, served through short-lived signed links, never attached to outbound SMS as public URLs. | Planned |
| Retention and deletion | Retention follows your policy and state record-keeping rules; deletion requests honored after the retention window. | Planned |
| MLS credentials | No MLS integration exists today. If built: per board, per user, no shared passwords, no scraping, no training on listing data. | Planned |
Messaging registration
Before the first production text.
- Register the brand and the campaign use case with the carrier registry before any production sending.
- Publish the opt-in language, sample messages, and STOP/HELP handling exactly as used in the product.
- Record consent per recipient with source and timestamp; suppress after STOP; honor START to resubscribe.
- Identify the sender as the agent (and their brokerage affiliation) in every message and include the AI disclosure.
- Keep a per-agent sending identity; never pool numbers across accounts.
Insurance
Only bound coverage gets published.
Errors-and-omissions and cyber coverage figures are shared with brokerages on request once bound. No coverage claim appears on this site before that.
Questions about a specific control: use the contact page and mention security in the message.