The short answer
Review access, sensitive-document handling, integrations and recovery procedures. Evaluate specific controls and published policies rather than relying on a broad claim that a platform is secure.
On this page
Know what information you are storing
Create a short inventory: contact details, leases, screening reports, payment records and maintenance photos. Identify which records contain sensitive personal information and which staff need them for a legitimate task.
A contractor may need an address, repair description and agreed contact method. That does not mean they need the tenant's screening report or a folder containing every lease. Minimize what you share and review access when a job or employment relationship ends.
Protect the sign-in and recovery path
Use a unique password and the strongest sign-in protection the service offers for your account. Keep recovery details current and protect the email account that receives resets. Confirm any unexpected account-change request through a known channel.
Do not send passwords, verification codes or full payment credentials to support. A screenshot can often be redacted to show the error and masked account details without exposing unrelated tenant information.
Inspect sharing and integrations
Before linking a service, read which data and actions it requests. Prefer the access needed for the task and know how to revoke it. Check whether a shared link requires authentication and whether its recipients can forward or download the material.
Worked example: when sharing a repair record, inspect the photo for visible mail or documents. Remove irrelevant personal information before sending it. Then confirm the recipient and the actual delivery result; a private note and a tenant message are different records.
Ask for specific evidence
Read the current privacy and security pages. Ask about access controls, retention, incident reporting and export options that matter to your operation. Verify any certification or audit claim against a current document with the relevant scope and dates.
This article does not assert an independent security certification, a particular encryption implementation or an uptime guarantee. Those claims require evidence beyond the presence of a login screen or an AI feature.
Prepare for staff changes and mistakes
Keep a list of administrators and connected services. Review it when someone joins, leaves or changes role. If a document reaches the wrong recipient, preserve the facts and contact the appropriate support and privacy advisers promptly.
For Rentari, start with the published Security page and Privacy Policy, then use Contact Support for a specific question. State which control you need confirmed rather than sending sensitive records as proof of the concern.
Written and maintained by the Rentari team. Examples explain a decision; they are not customer results. Found an error or an unclear step? Send a correction with this page's address and the detail to review.
Your next step
Find the current product workflow