Trust modelPrivate by design.
Crawlspace records are not public listings. Access is permissioned, logged, and limited to the purpose of the request. The owner controls the record — not the contractor, and not the platform.
Six controls. One owner.
The registry stores property records — so the trust model has to be visible, not buried. Every control here exists because someone outside the homeowner relationship will, eventually, want access.
The owner controls access.
Unless another legal owner or authorized property manager is designated, the homeowner alone decides who sees the record and what they can do with it.
Contractors see only what they're given.
Members access specific records for specific purposes — not a directory of everyone in their service area. Permissions are scoped, time-bounded, and revocable.
Every entry is signed and dated.
Every record identifies who added it, when, and what type of evidence supports it. The registry preserves the chain — it does not let one contributor bury another.
Old records are preserved, not overwritten.
The registry tracks change — moisture readings over years, condition photos before and after correction, drainage and RH upgrades. The trend is the story.
Every view is logged.
Viewers, dates, purposes, permission type, exports — visible to the owner. If someone has the record, the owner knows.
The record moves with the property.
Ownership transfer requires explicit authorization and a clean chain of custody. The next owner inherits the history — with privacy preserved.
Four roles. Four scopes.
Every relationship to the record fits one of four roles. Each carries a defined scope of what the holder can see, add, or export.
Owner
Full control. Invite contributors, grant viewer access, export the transfer packet, revoke any prior permission. Default for the property owner.
Contributor
Read access plus permission to add correction records and maintenance events. Scoped to specific zones or the whole record. Revocable.
Viewer
Read-only access. Time-bounded by default (14 days), or single-export. Cannot add records. Used for inspectors, agents, and buyers.
No access
The default for everyone else. Including Crawl-Space Connect staff outside support workflows, and including contractors who are not invited to the record.
Transfer protocolA record that can change hands cleanly.
When the property sells, the record can travel with it — preserving the chain of evidence while resetting access. Both parties have to opt in. Neither party can erase prior history. About the transfer packet →
What we hold, and why.
The registry holds property documentation. Everything else is the minimum we need to operate the account — and nothing is sold.
Documentation, by design.
Property profile fields, Crawlspace Blueprints™, conditions, corrections, events, documents, and access logs. This is the record — held as long as the owner keeps the account active.
Minimum viable identity.
Name, email, phone (optional), authentication credentials. Used to operate the account. Not sold, not used for advertising.
Operational only.
Aggregate, anonymized signals for platform reliability — page errors, performance, uptime. No behavioral tracking, no third-party ad pixels.
At rest and in transit.
TLS in transit. AES-256 at rest. Per-record access scoping enforced server-side — not in the client.
Owner-controlled.
Records are held while the account is active. Owners can export the full record at any time, and request account deletion — which redacts PII and severs the property's link to the prior owner.
Operating, disclosedYour record. Your call.
Records are private until you share them. Shared records remain logged. Transferred records leave a clean chain. That's the whole model.