The rules behind every packet.

Acren is built so a skeptical reviewer can check the work: reviewed source rights, QA gates before any market goes live, display rules that withhold what the record cannot support, a published security posture, and explicit responsible-use boundaries. This page summarizes those rules and links to the detail behind each one.

Five commitments

What trust means here.

Each commitment below is enforced in the product, not just stated on this page. The linked pages carry the detail — registries, gates, and boundaries you can verify.

What Acren does not claim

Boundaries, stated plainly.

Conservative claims are part of the product. These are the things Acren deliberately does not say.

No seller-intent prediction

Acren does not infer, predict, or indicate seller intent. The queue ranks research priority from what the public record supports — the ranking reason is always stated in evidence terms.

No complete-coverage claim

Coverage varies by state, county, asset class, source availability, and display rights. Acren licenses coverage state by state and activates customer-visible records only after source, display, and QA review.

No consumer-reporting use

Acren is not a consumer-reporting product and must not be used for tenant screening, employment screening, or consumer eligibility decisions of any kind. Research use only.

No unattributed claims

Every section of an evidence packet names its public source — county recorder, property appraiser, state corporate registry. Where the record stops, the packet says so with a named verification gap.

Responsible use

Research priority, not seller intent

Acren ranks commercial property research priority. It does not infer disposition, hardship, or willingness to transact.

Responsible use

Source evidence required

Every recommendation must carry supporting records, field-level rights status, and verification gaps.

Responsible use

Verification before action

Customers are responsible for verifying records before outreach, capital, or workflow decisions.

Responsible use

Display rules built in

Customer-visible, generalized, internal-only, and suppressed fields stay visible as product controls.

Verify it

The detail pages.

Next

Check the work yourself.

The public sample report shows the per-section citations and the named gaps. If the rules hold up, request access.

Continue
See how each opportunity keeps the source trail attached.