Collect only what the workflow needs
A maintenance intake should ask for information that helps the property team understand, prioritize, access, or repair the issue. Teams should avoid requesting sensitive personal information that does not serve that purpose.
Review access before a pilot
Define who on the property team needs to view resident conversations, who can change status or assignment, and what information an outside contractor should receive. The least-privilege review should reflect the actual pilot workflow.
Document data lifecycle and subprocessors
Before deployment, confirm what data is stored, where it is processed, the current subprocessors, backup and retention behavior, deletion procedures, and how data can be exported at the end of a pilot.
Confirm current controls directly
Security capabilities evolve. Stead will provide the current implementation details during a deployment review rather than make a blanket claim on this page that may not match a specific environment or integration.
Keep emergency operations outside one tool
A property team's emergency policy should not depend on a single software channel. Maintain documented phone, on-call, and escalation procedures and explain them clearly to residents.
Frequently asked questions
What information should we request in a security review?
Ask for the current architecture, data flow, access model, encryption details, subprocessors, retention and deletion process, backup behavior, incident-response process, and integration-specific controls.
Should contractors see the full resident conversation?
Not by default. Share only the information needed to perform the assigned work, subject to the property team's policies and resident access requirements.
Is this page a claim of a specific certification?
No. This page explains review topics and operating principles. Request Stead's current control and certification status for the deployment being evaluated.