Security
Last updated November 15, 2026
Property managers trust Rentology with their owners' payouts, their guests' stays, their tenants' leases and the codes to their doors. This page explains, in plain terms, how we protect that data and what you can ask us for.
At a glance
- Encrypted on the way in and at rest, including backups
- Every company's data fenced off at the database, checked before every release
- Two-step sign-in required for company owners and admins
- Card numbers never reach our servers
- One set of rules for the website and all five Rentology apps
1. One platform, every app
Everything on this page applies to every place Rentology runs:
- Rentology on the web (app.rentology.ai and your own company address)
- Rentology, the team app
- Rentology Clean, for cleaners
- Rentology Pro, for contractors and vendors
- Rentology Owner, for property owners
- Rentology Home, for tenants and guests
All of them read the same database through the same access rules. Each app shows a person only what their role needs: a cleaner sees the jobs assigned to them, an owner sees their own homes and statements, a tenant sees their own lease and requests.
2. Encryption
Every connection to Rentology uses HTTPS with TLS 1.2 or newer, and our addresses tell browsers never to connect without it (HSTS). Data stored in our database, file storage and backups is encrypted at rest with AES-256.
Logins and keys you give us for connected systems, such as your booking software or pricing tool, are stored in a separately encrypted store and are never shown back in full, not even to your own admins.
3. Keeping each company separate
Rentology serves many property management companies from one platform. Every record carries the company it belongs to, and a rule inside the database checks that company on every read and every write, so one customer can never see another's data, even if the app made a mistake.
An automatic check runs before every release and blocks any new table that is missing this rule. We also test with people who belong to two companies, because that is where a fence that looks fine for everyone else can fail.
4. Sign-in and access
- Passwords are never stored in readable form; they are hashed with bcrypt.
- Company owners and admins must use two-step sign-in with an authenticator app.
- Risky actions, such as changing a teammate's password or making someone an admin, ask for the code again.
- Roles and per-menu permissions decide who sees owners, money and door codes. Removing a team member ends their access on every device.
- The phone apps keep your sign-in in the phone's own secure keychain, not in plain storage.
5. Payments and bank accounts
Card and bank payments are entered on our payment processor's secure page, which is certified to PCI DSS Level 1. Full card numbers never reach Rentology's servers. Bank accounts for payouts are linked and verified through a dedicated bank-linking provider; we never see the bank login.
Owner and vendor payouts go out only after an approver you name approves them, within per-transfer and daily limits you set, and you can require a second approver.
6. Door codes, AI and recorded calls
Smart-lock codes are created through the lock provider and shown only to the roles you allow. Contractors do not receive lockbox codes.
AI features send only the details needed for the task to our AI provider, which does not use that data to train its models. An AI assistant never denies being automated when asked. Calls to Rentology lines play a recording notice before they connect.
7. How we build and run the service
- We run on US cloud providers that hold their own SOC 2 Type II and ISO 27001 certifications.
- Every code change is scanned for hidden malicious code when it is saved, before it is shared, and again before it is built. A failed scan stops the build.
- Passwords and keys the service needs live in a managed secret store, never in the code, and an automatic check blocks any change that contains one.
- Changes reach a test site first. The test site uses a scrubbed copy of data: emails replaced, phone numbers, door codes and bank details removed.
- Browsers are told not to let other sites frame Rentology pages, which blocks click-jacking.
8. Backups, monitoring and incidents
The database is backed up automatically every day and backups are kept for seven days. Automatic checks watch sign-in, the pages customers load, phone lines and payment jobs around the clock and alert our team when one fails.
If we confirm a security incident that affects your data, we tell you without undue delay and within 72 hours, with what we know, what we are doing and what you should do. Our Data Processing Addendum makes this a contractual promise.
9. Our people
Only a small number of named staff can reach production systems, each behind two-step sign-in, and everyone with access to customer data is bound by confidentiality. We look at your data only to provide the service, to answer a support request, or when you ask us to.
10. Your controls
You decide who is on your team and what each role can see. Company admins can export the company's data and ask for it to be deleted. People using the Rentology apps can delete their own account inside the app. You can turn AI assistants on or off at any time.
11. Compliance
Rentology does not hold a SOC 2 report yet. We use the SOC 2 Trust Services Criteria as our checklist, and the providers we host on, take payments with and send messages through hold their own SOC 2 or PCI DSS certifications. For privacy law (GDPR, UK GDPR, CCPA) see our Privacy Policy, the Data Processing Addendum and the subprocessor page. Texting follows US carrier registration (A2P 10DLC) and STOP requests, and payouts follow the NACHA Operating Rules.
Need a security questionnaire filled in for your company? Email support@rentology.ai and we will answer it.
12. Report a vulnerability
If you believe you have found a security problem in Rentology, email support@rentology.ai with the subject “Security”. We confirm receipt within three business days and keep you updated until it is fixed.
We will not take legal action against research done in good faith that stays within these limits: use only your own accounts, never access, change or keep another customer's data, do not disrupt the service or send bulk traffic, do not trick our staff or customers, and give us reasonable time to fix the problem before you share it.