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.
TRUST
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.
→
Source rights
Every public source enters through a registry that records where the data comes from, what the source permits, and how each field may be displayed. Records without reviewed rights do not ship to customers.
Source registry →
→
QA before anything ships
A market goes live only after county-by-county checks pass on source availability, field quality, and display rights. Source review covers where each record came from, what each field means, and how confident the memo should be.
Source review method →
→
Display rules
Owner identities below the confidence floor are withheld, not guessed. Rows that cannot be tied to a recorded instrument are flagged inferred — never silently blended. Every packet section names its public source.
Methodology →
→
Security posture
Acren uses scoped access, route protections, no-store headers on private surfaces, and row-level security as the backstop for customer data. Security questions go to security@acren.ai.
Security contact →
→
Responsible use
Acren ranks research priority, not seller intent, and is not a consumer-reporting product: it must not be used for tenant screening, employment screening, credit, insurance, or lending eligibility decisions.
Responsible use →
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 complete-coverage claim
Coverage varies by state, county, asset class, source availability, and display rights. Acren licenses coverage state by state and activates customer-facing 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 opportunity memo names its public source — county recorder, property appraiser, state corporate registry. Where the record stops, the packet says so with a named verification gap.
Data handling
How Acren treats data.
Acren separates public marketing content, public samples, customer workflow data, source-restricted evidence, and operational telemetry. Public examples stay illustrative.
Customer and account data
Approved-user identity, workspace access, request details, and workflow records are used to operate the product and respond to reviewed-access requests. They are not published on public pages.
Source and vendor data
Raw source payloads and restricted evidence stay out of public pages. Customer-visible fields depend on source rights, display rights, QA status, and entitlement.
Analytics
Public-site analytics are used to understand aggregate page, CTA, and tool usage. Analytics payloads should not include email, phone, free-form notes, property addresses, owner names, or customer data.
Retention
Retention follows source rights, customer agreements, operational audit needs, and approved-deployment scope. Binding retention terms are reviewed during onboarding.
Security controls
Security posture buyers can inspect.
No public page should expose customer data, raw vendor payloads, app routes, admin routes, or private records. These controls are enforced in code and checked in audits.
| Control | Posture |
|---|---|
| Private routes | App, dashboard, admin, auth, and API routes carry no-store and noindex headers where appropriate. |
| Data access | Customer-facing data is gated by authentication, entitlement, source-rights review, display posture, and QA state. |
| Database backstop | Server-side access controls protect customer data. Public pages never rely on hidden UI alone. |
| Headers | The deployed site uses CSP, HSTS, frame-ancestors, content-type protection, referrer policy, and permissions policy headers. |
| Incident posture | Security reports should avoid sensitive payloads in the first message and go to security@acren.ai. |
Service providers
Subprocessor posture.
Acren uses service providers to host, authenticate, store, analyze, and send product communications. Binding subprocessor terms are handled during customer onboarding.
Vercel
Hosting, deployment, CDN, and serverless runtime.
Data platform
Authentication and server-side database policies control where product data is stored.
Google Analytics
Public-site analytics where enabled by configuration and consent posture.
Email provider
Transactional access-request and workflow email where configured.
Responsible use
Responsible boundary
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.
Responsible use
Source trail required
Every recommendation must carry source trails, field-level rights status, and open questions.
Responsible use
Review before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-facing, summarized, internal-only, and withheld fields stay visible as product controls.
Verify it
The detail pages.
Source registry
Where every record class comes from, with rights posture.
Open →
Source review
Field quality, source trails, and confidence methods.
Open →
Responsible use
The boundaries Acren enforces, in full.
Open →
Privacy posture
Data treatment, retention, and service-provider posture.
Open →
Security contact
Report security questions without sensitive payloads.
Open →
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.
Next step
Start with your market and buy box.
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.