Security and compliance
An AI that talks to your residents has to be safe for them and defensible for you. This page lists the rules ResidentAnswer follows and the protections we are putting in place.
ResidentAnswer is preparing for its first pilot. Items marked Committed are rules built into how the product works. Items marked Planned are not in place yet, and we will tell you when each one is.
Committed How the product worksPlanned Not in place yet
What the assistant will never do
Some decisions belong to people. These limits hold in every building, on every channel.
- Screen, score or approve applicantsIt answers questions and books tours. Leasing decisions stay with your team.
- Deny an accommodation requestRequests for assistance animals or accessibility changes always go to a person.
- Handle a life-safety emergency aloneIt gives 911 guidance, then phones your on-call chain until a person takes it.
- Create voiceprintsNo speaker identification, now or when phone answering arrives.
- Take card numbers by voice or chatPayments go through your own portal or a payment link. Card numbers a resident says or types are removed from the record.
- Change the phone number on fileThat is how accounts get taken over, so a staff member makes the change.
- Send legal noticesEntry notices, rent increases, lease violations and evictions follow your normal process with your staff.
- Pretend to be a personEvery chat shows that an AI assistant is answering, and anyone can ask for staff to follow up at any time.
Calls and texts
Phone and text answering for residents are not available yet. Phone and text rules carry real penalties, so these rules are planned into those channels before they launch.
Consent before outbound messages Planned
Non-emergency texts and calls go only to residents who opted in, with consent records kept for at least four years.
Opt-outs honored right away Planned
STOP and HELP work on every number, and an opt-out made any other reasonable way is honored too.
Recording announced on every call Planned
Residents call from many states with different recording rules, so every call says it is recorded.
Registered business texting Planned
Each building’s texting is registered with the carriers before launch, so messages are not filtered as spam.
Verified caller ID Planned
Outbound calls carry carrier verification and your business name, so residents see who is calling.
Collections only after legal review Committed
The assistant sends no rent reminders or collection messages, and won’t until your counsel and ours have reviewed them.
Fair housing and accessibility
The assistant gives every prospect and resident the same answers, and keeps the record to show it.
Same answers for every prospect Committed
The assistant answers only from your facts, with no comments on who lives in a neighborhood. Prospect conversations are kept for the building’s retention period.
Resident confidentiality Committed
The assistant never confirms whether someone lives in the building or in a unit, and never shares anything about another resident.
Text for every phone task Planned
Anything residents can do by phone they can also do by text, for deaf and hard of hearing residents and night-shift workers.
Accessible website chat Planned
The chat is built to the WCAG 2.1 AA standard and tested with screen readers before launch.
English and Spanish Committed
Residents are answered in the language they write in.
A person on request Committed
Residents can ask for staff to follow up at any point in the chat, and your team can reply in any conversation from the staff portal.
Checking who is calling
Planned for phone and text, where caller ID can be faked, so private information needs more than a matching number. Today the chat has no access to balances, lease details or access codes, so it has nothing private to check for. Three levels, by what is being asked.
No check
General building questions and common-area maintenance.
Pool hours, trash days, a broken hallway lightCaller ID, name and unit
Enough to open or check a work order for the caller’s own home.
“Is someone coming about my sink?”Text code to the number on file
Needed for balances, lease details, contact changes, and gate or access codes.
“What do I owe this month?”
Your data
Your residents’ information belongs to you. We process it on your behalf and only for running your buildings.
A data processing agreement Committed
We sign one with every client, so our role and limits as your processor are in writing.
A published list of subprocessors Planned
Every vendor that touches resident data is named: the phone carrier used for on-call paging, the AI model provider, hosting, and your property software if connected.
No training on your conversations Planned
We are getting written no-training terms from each AI vendor before launch.
A retention schedule Committed
Conversations are deleted after a retention period set for each building, a year unless you choose otherwise.
Your data stays yours Committed
If you leave, you get an export of your data, with deletion on a set timeline.
Records you can use Committed
Emergency reports, who took them and when, and every conversation are kept for the building’s retention period, and emergency reports for at least a year, for audits and disputes.
Security controls
What property companies expect from a vendor that holds resident data. We will answer your security questionnaire, including SIG Lite or CAIQ, as part of any pilot.
| Control | Status | What it means |
|---|---|---|
| Staff sign-in | Planned | Multi-factor sign-in for everyone, with single sign-on for your team |
| Access by building | Planned | Each staff member sees only the buildings and roles they are given |
| Encryption | Planned | Data encrypted in transit and at rest |
| Action log | Planned | A record of every action the assistant takes and every staff access |
| Permissions in code | Planned | What the assistant may do is enforced by the system, not by its instructions, and tested against prompt injection before launch |
| Outage failover | Planned | If the platform goes down, residents are pointed to your office or a human answering service, with a public status page |
| Incident response | Planned | A written plan with notification timelines |
| Penetration test | Planned | An outside test every year |
| SOC 2 | Planned | Type I in the first year, then Type II |
| Insurance | Planned | Cyber liability and technology errors and omissions coverage |