Property management software vendors: what records you can license

Who owns the data in property management software?#

Property management software data ownership usually splits three ways. The landlord or management company owns the operating records of its portfolio, tenants have privacy rights in their personal data, and the vendor owns the records it creates running its own business. Hosting all three in one database does not merge them.

Most proptech customer agreements say this in some form: the customer owns customer data, and the vendor receives a license to use it to provide the service, sometimes with rights to aggregated or de-identified data. Older agreements rarely mention AI, so the question of training or licensing use is often unanswered rather than prohibited.

Ownership also moves over time. When a management company loses a property, the owner may take the records with it, and when a customer churns, the termination clause decides whether the vendor may keep any copy. Keep those events in mind during an inventory, because a dataset that includes departed customers' records may rest on rights that have already ended.

Vendor records, landlord data and tenant personal data#

The three-column view below is the fastest way to brief a leadership team. Each column has a different owner, a different approval path and a different licensing outlook.

What your customer agreements decide#

The customer agreement decides what a vendor may do with landlord data, so read every template version still in force, not just the current one. Look for the data ownership clause, the license granted to the vendor, any aggregated or de-identified data right, confidentiality obligations and what happens to data at termination.

An aggregated data clause is not automatic permission to license. Many were written to allow benchmarks inside the product, and they may not extend to delivering records to a third party or training models for others. Negotiated agreements with large management companies often narrow these rights further.

• 1Which template versions are in force, and for which customers?
• 2Does the vendor's license cover only providing the service, or also improvement and development?
• 3Is there an aggregated or de-identified data right, and what exactly does it permit?
• 4Do confidentiality terms treat rent rolls and owner financials as confidential information?
• 5What must be deleted or returned when a customer leaves?

Tenant personal data: why it usually stays out#

Tenant personal data usually stays out of a licensing package because the rules around it are demanding and the vendor rarely has a direct relationship with tenants. Screening reports may fall under the Fair Credit Reporting Act, rental decisions under fair housing laws, and tenant records under state privacy laws where they apply.

Maintenance notes deserve particular care. A routine work order can mention a disability accommodation, a medical device, a pet, a door code or when a unit is empty, and those details survive casual redaction. If any tenant-derived text is considered, California's definition of deidentified information is a useful benchmark: it requires reasonable measures against re-association, a public commitment not to re-identify and contractual obligations on recipients.

Tenant details also hide inside records that look like vendor-owned material. The table shows where they usually surface and the preparation step that handles each.

Pooled rent and occupancy data: the antitrust line#

Pooled rent and occupancy data from competing landlords raises a separate question from privacy: whether sharing it, or a model trained on it, could help competitors align prices. The RealPage case brought that issue to the front of many proptech roadmaps.

For licensing, the practical rule is to keep current, granular pricing and occupancy data from competing customers out of any package unless antitrust counsel has reviewed it. Support and engineering records rarely raise the issue, which is another reason they make a cleaner starting point.

Records AI developers value from proptech vendors#

AI developers value proptech vendor records that show how property operations problems get diagnosed and resolved. Those records come from the vendor's own systems and teach models the work, not the tenants.

• 1Support threads resolving accounting questions such as bank reconciliations, owner distributions and late fee setups.
• 2Integration engineering histories for payment processors, bank feeds, listing sites and accounting exports.
• 3Data migration records showing how portfolios moved from other systems and what broke along the way.
• 4Product decision records explaining why workflows such as lease renewals or move-outs were designed as they were.
• 5Code reviews and incident notes from the platform's own engineering team.

Illustrative: a property accounting platform scopes its first package#

Illustrative: a fictional property accounting and leasing platform serves small residential management companies. An AI developer building agents for back-office accounting asks what records the vendor could license.

The CEO and general counsel sort records into the three columns. Rent rolls, ledgers and tenant files are excluded. A proposed set of rent benchmarks is dropped after counsel flags the pooled pricing issue. The package that proceeds holds support threads about reconciliations and owner statements, linked to the engineering issues and code changes that fixed them, with manager names, property addresses and tenant details removed.

Customers are told in advance that the vendor is licensing its own support and engineering records with their details removed, which answers the question before anyone asks it.

How SourceX approaches proptech vendor records#

SourceX starts with a metadata-only fit check, so a proptech vendor can describe its systems and record families without sharing files. In the SourceX five-step transaction, the Rights step applies the three-column split, Preparation removes landlord, property and tenant details, and Approval stays with the vendor.

Each package that proceeds carries a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Data is licensed, not sold outright, so the vendor keeps ownership of its records.