Market, MLS, Compliance & Privacy
A comprehensive overview of PropChain's market opportunity, regulatory framework, and data governance approach across predictive analytics, transaction workflows, and data-as-a-service revenue lines.
Market Research & TAM/SAM/SOM Summary
Three Primary Revenue Lines
PropChain's market sizing framework encompasses predictive analytics through Terra Engine and PropPredict, transaction workflows via Visual Transaction Pipeline, and Data-as-a-Service through Terra Net APIs and reports.
This framework aligns long-term market opportunities with conservative Seed capital planning, positioning very large revenue scenarios as long-term upside rather than 24-month FP&A targets.
Predictive Analytics
Terra Engine core decisioning
Transaction Workflows
VTP & smart contracts
DaaS & APIs
Terra Net data feeds
Market Definitions & Product Segmentation
1
TAM – Total Addressable Market
The global annual revenue opportunity for a given product category, assuming 100% penetration of all relevant customers across all geographies and segments.
2
SAM – Serviceable Available Market
The subset of TAM that PropChain realistically targets in the medium term, constrained by ORI-2 states, U.S. focus, digitally active segments, and regulatory boundaries.
3
SOM – Serviceable Obtainable Market
The realistic share of SAM PropChain could capture within the initial 3-7 year horizon, assuming successful execution and reasonable competition in the marketplace.
Predictive Analytics Market Opportunity
Terra Engine & PropPredict TAM/SAM/SOM
$67.7B
Global TAM
Annual predictive analytics and decisioning opportunity across 600M global property units
$1.4B
U.S. SAM (Low)
ORI-2 top-15 states, digitally engaged residential and light-CRE segments
$3.2B
U.S. SAM (High)
Expanded addressable market with premium upsell potential
The global TAM reflects approximately 600M property units with 5% adopting advanced digital decision tools at roughly $225/year in AI-driven analytics spend. PropChain's U.S.-focused SAM represents the practical playing field for Seed and post-Seed phases, targeting digitally active homeowners, investors, and professionals in top-15 ORI-2 states including CA, NY, FL, TX, WA, NJ, MD, VA, CO, GA, NC, OR, MA, AZ, and NV.
Conservative Seed-Stage Revenue Targets
24-Month ARR Scenarios
Low: $100k ARR
Conservative baseline across all revenue lines
Base: $250k ARR
Expected case with modest traction
High: $400k+ ARR
Strong execution scenario
Long-Term SOM Positioning
The $33.8M–$67.7M SOM for predictive analytics represents a multi-year post-Seed goal (5-7+ years), not a 24-month target. This corresponds to approximately 1-2% of SAM with 135k+ highly engaged users at roughly $250/year net ARPU.
Seed FP&A deliberately constrains near-term expectations, with end-of-runway ARR representing well under 0.1% of SAM to provide early validation without overpromising.
Transaction Workflows & VTP Market
End-to-End Transaction Coordination Layer
PropChain's Visual Transaction Pipeline orchestrates the complete transaction timeline from offers through inspections, financing, and close. The platform embeds smart contracts and escrow hooks over time while supporting ad-supported placements and service referrals for inspectors, title agents, and contractors inside the workflow.
Offers & Negotiation
Digital coordination and timeline tracking
Inspections & Due Diligence
Service referrals and status updates
Financing & Close
Smart contract hooks and escrow integration
This line captures a narrow slice of coordination and workflow value rather than replacing brokers or core transaction parties, targeting approximately 30% of the broader platform TAM for an indicative global transaction workflow TAM of approximately $20B.
Transaction Workflows Market Sizing
$20B
Global TAM
Transaction workflow digitization opportunity
$1.5B
U.S. SAM (Mid)
ORI-2 workflow coordination spend
Conservative Seed-Period Approach
The monetization roadmap sketches early transaction workflow revenue at approximately $200k ARR from VTP and smart contracts by Q1 2026, contributing to a $1M total ARR goal by Q4 2026 when combined with subscriptions and data marketplace revenue.
However, the Seed Capital Plan compresses these targets into conservative scenarios where VTP and transaction fees provide only tens of thousands of ARR at most as features come online late in Seed. Long-term SOM scenarios show transaction workflows contributing meaningfully to nine-figure revenue stacks alongside subscriptions and DaaS/API, but these are explicitly treated as 10+ year, post-Series B outcomes.
Data-as-a-Service & API Market
Terra Net & Terra Engine Data Monetization
Hedge Funds & Asset Managers
Asset-level forecasting and portfolio analytics for institutional investors seeking predictive property insights and market intelligence.
Urban Planners & Municipalities
Zoning and development risk analysis, infrastructure planning, and neighborhood evolution tracking for public sector decision-making.
Insurers & Lenders
Fraud detection, pricing models, and risk assessment tools leveraging curb-level data and predictive analytics for underwriting.
PropTech & FinTech Platforms
API integrations and bundled analytics for platforms seeking to enhance their offerings with Terra Engine outputs and data feeds.
DaaS & API Market Opportunity
Market Sizing
$12.5B
Global TAM (Mid)
Built-environment data and analytics
$500M
SAM (Mid)
Early institutional and B2B segments
$100k
2026 Target
DaaS subscriptions and reports
Revenue Trajectory
The DaaS/API roadmap targets approximately $100k ARR from data subscriptions and reports by 2026 as one component of the path to $1M total ARR. This represents a 15-25% slice of the broader AI and analytics platform TAM addressable via data feeds, APIs, and analytics subscriptions.
Near-term targets are folded into the 24-month ARR scenarios conservatively, while longer-term projections show DaaS/API as 30%+ of the $1M ARR blend by Q4 2026 (approximately $300k ARR in aggressive scenarios) with a plausible path to $10M-$20M+ ARR over a multi-year horizon as Terra Net coverage and CurbScan data expand.
Combined Platform Market View
Cross-Line TAM/SAM/SOM Summary
Platform TAM
$67.7B+ annually across analytics, workflows, and data globally
Combined SAM
$2.7B–$5.9B U.S. ORI-2 focus plus early B2B segments
Seed SOM
$100k–$400k ARR conservative 24-month targets across all lines
The combined SAM band encompasses approximately $1.4B-$3.2B for predictive analytics, $1.0B-$2.0B for transaction workflows, and $0.3B-$0.7B for DaaS/API. Under this framing, even a $272M+ blended ARR scenario in the distant future would represent approximately 5% or less of combined SAM and under 1% of TAM, which is reasonable for a scaled but not monopolistic player.
Key Insight: PropChain's actual Seed-period revenue targets correspond to a tiny share of SAM (order-of-magnitude 0.01%-0.1%), with large figures like $33.8M-$67.7M SOM and $272M+ total revenue stacks explicitly positioned as long-term upside for valuation and strategic mapping, not baked into 24-month FP&A or runway planning.
Methodology & Limitations
Internal-First Approach
This summary relies primarily on PropChain's internal TAM/SAM/SOM wiki, monetization strategy, and valuation roadmap, reconciled with the Seed Capital Plan and FP&A for consistency.
Hybrid Modeling
TAM is framed top-down using global property units and indicative ARPU. SAM is constrained by geography, digital adoption, and buyer segments. SOM is modeled as modest Seed-period ARR plus directional multi-year upside bands.
Deliberate Conservatism
Whenever historical TAM/SAM/SOM assumptions implied more aggressive near-term ARR than the Seed plan, this memo explicitly defaults to the Capital Plan and pushes higher numbers into post-Seed horizons.
Red Flags & Reviewer Notes
Critical Considerations for Diligence
Potential Confusion on SOM Timing
Earlier internal TAM/SOM work (e.g., $33.8M-$67.7M SOM for predictive analytics) can be misread as a near-term 2026 target. In this Seed data room, it should be clearly labeled as long-term upside, with 24-month ARR scenarios capped at approximately $400k.
Precision of Out-Year Figures
Some valuation materials reference very specific large revenue figures (e.g., approximately $272M+ ARR). These should be communicated as illustrative stacked scenarios, not forecasts, and always tied back to detailed GTM and runway assumptions.
Heuristic Allocation Across Lines
The allocations of platform TAM into predictive vs workflows vs DaaS/API (e.g., 30% to workflows, 15-25% to DaaS/API) are heuristic and based on internal strategic reasoning. Consider refreshing with third-party market research before external marketing.
Regulatory Constraints
While TAM/SAM are framed based on economic potential, MLS, IDX/VOW, and data-licensing constraints may further limit exploitable SAM for certain use cases, especially training models on MLS data. Cross-check with the Regulatory & Licensing Memo.
MLS & IDX Regulatory Framework
Data Access, Compliance & Licensing Strategy
PropChain's regulatory and licensing posture encompasses MLS aggregation strategy through ListHub, CoreLogic Trestle, and MLS Grid, RESO 1.6+ compliance for Terra Net and Terra Engine, treatment of IDX/VOW display versus internal analytics use cases, data retention windows, and handling of training and analytics on MLS-derived data.
Key Regulatory Regimes
- MLS Organizations (OneKey, NJMLS, GSMLS)
- Data Aggregators (ListHub, Trestle, MLS Grid)
- RESO 1.6+ Standards
- Broker/Participant-Direct Agreements
Product Use Cases
- Internal Analytics & Pilot Sandboxes
- Minimal Compliant Consumer Display
- Future Production UX (MLS-backed search)
MLS Aggregation Strategy
1
Phase 1: 0-3 Months
Execute Participant-Direct sandbox agreements with OneKey and at least one NJ MLS. Implement sandbox ingestion into Terra Net with RESO 1.6+ mapping and ≤90-day retention.
2
Phase 2: 3-9 Months
Add either Trestle or MLS Grid for multi-MLS expansion if internal-analytics-only programs exist. If ListHub is used, ship minimal compliant consumer details page with 60-90 day checkpoint.
3
Phase 3: 9-24 Months
Expand MLS coverage in ORI-2 priority markets under mix of direct and aggregator arrangements. Adjust aggregator usage based on cost versus data coverage within FP&A envelope.
Over the Seed horizon, PropChain aims to obtain sandbox, read-only RESO Web API access to IDX-public fields for target MLSs while keeping all pilots under internal-use, no public IDX/VOW, no write-backs, with ≤90-day retention and auditable deletion. Aggregators provide faster, standardized access while honoring their consumer-display orientation and compliance requirements.
Participant-Direct Authorization
Internal-Use Pilot Framework
Environment
Sandbox-first, then tightly scoped production pilots
Security
OAuth2 client-credentials, IP allow-lists, TLS, audit logs
Retention
≤90 days with deletion certificate within 10 business days
Scope & Permissions
Internal-use only with no public IDX/VOW and no write-backs into the MLS. Scopes include readOnlyListings, media, officeBrokerage, and optionally openHouses if permitted.
Setup plus 4 weeks live term that auto-expires unless extended or renewed. This route is expected to be the primary mechanism for early MLS pilots where aggregators do not support internal-analytics-only products.
Compliance Controls
- Strict separation of internal analytics from public display
- Logged deletion certificates after pilot termination
- Auditable access controls and data lineage
- Per-MLS consent and pricing documentation
Aggregator Route Comparison
Trestle, MLS Grid & ListHub Options
1
CoreLogic Trestle
Role: Common hub for OneKey/NJMLS with RESO Web API and normalized schema
Key Questions: Developer/eval access for internal analytics? Broker opt-in requirements? Pricing per MLS?
2
MLS Grid
Role: Normalized multi-MLS access with OAuth2, good for scale
Key Questions: Is OneKey on Grid? Are NJMLS/GSMLS reachable? Per-MLS pricing and broker opt-in requirements?
3
ListHub (Move, Inc.)
Role: Wide coverage with strong compliance framework, display-focused
Key Questions: Can they support sandbox/eval feeds for internal analytics? Required display obligations and retention rules?
Cost Reconciliation: The Seed Capital Plan assumes a blended "S2 Moderate Grow" MLS/data cost of approximately $1,670/month or approximately $40k over 24 months. ListHub Regional pricing ($2.5k setup + $3k/month) is treated as a scenario funded by baseline data budget and contingency, or scoped to shorter evaluation periods.
ListHub Compliance Requirements
Commercial Terms
$2.5k
Setup Fee
One-time regional tier activation
$3k
Monthly Fee
Up to 5 MLSs coverage
Launch Logistics
- Initial deposit due with agreement
- Thursday launch notice to each MLS
- Approximately 5 business days for review
- Metrics and ListHub-labeled links installed before announcement
Compliance & Reporting
Must track at least SEARCH_DISPLAY and DETAIL_PAGE_VIEWED events, with lead events if a form is added. Mobile apps must use the Query-String API rather than JavaScript snippets.
Data Hygiene
- Pull fresh data every 12 hours
- Purge removals on same cadence
- No redistribution of ListHub data
- Maintain required display fields and attribution
RESO 1.6+ Compliance & Field Mapping
Data Dictionary Alignment for Terra Net
PropChain's Terra Net ingestion layer is designed around RESO Data Dictionary 1.6+ semantics, normalizing core entities to RESO-standard fields for consistent processing across all MLS and aggregator feeds.
Listing Fields
ListingKey, ListingId, StandardStatus, ListingContractDate, CloseDate, ListPrice, ClosePrice, PropertyType, PropertySubType, BedsTotal, BathsFull, BathsHalf, LivingArea, LotSizeArea, YearBuilt
Location Fields
UnparsedAddress, City, StateOrProvince, PostalCode, CountyOrParish, Latitude, Longitude
Media & Participants
MediaURL, MediaModificationTimestamp, MediaCategory, ListAgentMlsId, ListOfficeMlsId, BuyerAgentMlsId, BuyerOfficeMlsId
PropChain maintains per-MLS mapping configs that translate local field names and enumerations into RESO-standard values. For early pilots, ingestion scope is limited to IDX-public fields only as specified by each MLS or aggregator, with no off-MLS private fields ingested.
IDX/VOW Display vs Internal Analytics
Internal Analytics & Sandbox
MLS-derived data used exclusively inside PropChain tools for internal staff, pilot stakeholders, and credentialed MLS Participants under NDA/pilot agreements. No public IDX or VOW display unless explicitly permitted.
Minimal Compliant Display
Simple web "Search & View" page surfacing required display fields with ListHub metrics implementation. Mobile apps call metrics via Query-String API to comply with publisher guide.
Future Production UX
Each MLS will have a display profile specifying logo placement, attribution text, field visibility restrictions, required disclaimers, and map provider constraints.
PropChain's default pilot posture is internal-use only with no write-backs to MLS systems, ≤90-day retention for raw listing records, and logged deletion certificates within 10 business days after pilot termination.
Data Retention & Model Training Rules
Retention Policies
01
Raw MLS Records
Maximum 90 days from ingestion
02
Cache Behavior
On-device or offline cache treated as part of 90-day window
03
Deletion Workflow
Jobs purge records and media older than 90 days
04
Certification
Deletion certificate issued within 10 business days
Model Training Approach
Because MLS licenses vary in their treatment of training AI/ML models on listing data, PropChain's default posture is conservative and opt-in based.
Training Guidelines
- Only train Terra Engine models on data from MLSs/aggregators whose contracts explicitly permit analytics/model training
- Where licenses are silent or restrictive, use MLS data only for deterministic analytics (search, filters, basic scoring)
- Training datasets consist primarily of derived features (numeric encodings, aggregated statistics, curb/telemetry signals)
- Street-level telemetry captured independently of MLS licensing may be used more flexibly
- No external model training: PropChain data will not be used to train any external third-party foundation models
Licensing Matrix Structure
Per-MLS & Aggregator Tracking Framework
PropChain maintains living licensing matrices as artifacts in the data room, updated with concrete values as contracts are executed. These matrices track access paths, feed types, scopes, use cases, retention limits, training permissions, pricing, and status for each MLS and aggregator relationship.
Per-MLS Direct Licensing
Tracks MLS name, region/coverage, access path (direct/participant), sponsor, feed type (IDX/BBO/PDAP), RESO scopes, use case (internal/display), retention limit, training permissions, pilot pricing, status, ETA/term, and notes.
Aggregator Licensing
Tracks aggregator, MLSs included, feed scope, use case, retention limit, display obligations, training permissions, pricing (setup/monthly), status, and notes for ListHub, Trestle, and MLS Grid relationships.
Example entries include OneKey (NY metro, Participant-Direct, IDX/BBO read-only, internal analytics only, ≤90 days retention, planned status) and NJMLS (Northern NJ, Participant-Direct/Aggregator, IDX sandbox + prod, internal analytics only, ≤90 days retention, planned status).
Governance & Operational Controls
Data Use Registry
Centralized catalog of all MLS feeds and aggregators with allowed uses and retention rules
Access Control
Least-privilege access with data engineers and specific product services only
Logging & Audit
Audit trail of ingestion, refresh, purge jobs, and model-training pipeline access
Compliance Reviews
Quarterly reviews confirming adherence to retention, display, and training constraints
Incident Response
Data use incident workflow for suspected MLS or IDX policy breaches
MLS Regulatory Red Flags
Critical Considerations for Investors & Counsel
Aggregator Pricing vs FP&A Envelope
ListHub's current quoted pricing (Regional: $2.5k setup + $3k/month) is higher than the S2 Moderate baseline used in FP&A (approximately $1,670/month). Resolution: FP&A budgets $40k over 24 months; any higher run-rate will use shorter evaluation periods, cover fewer MLSs, or be funded from contingency.
Training Rights Not Uniform
Some MLSs may disallow or restrict training of ML models on their listings. Resolution: PropChain will default to no training unless an MLS/aggregator agreement explicitly permits it; per-MLS training flags tracked in licensing matrix.
Internal vs Public Display Line
Many valuable features (predictive scoring, what-if scenarios) are internal or quasi-internal in pilots. Accidental exposure of internal-only views in consumer UX could violate IDX rules. Resolution: Clear environment separation, feature flags, and periodic internal audits.
GSMLS & Similar MLSs
Current guidance: "Defer until official API; do not CSV listings." Resolution: PropChain will avoid any non-API screen-scraping or CSV ingestion and will wait for official RESO or aggregator access.
NAICS Classification Framework
Business Activity Statement for Seed Stage
PropChain's primary and secondary NAICS classifications define the company as a software and data analytics business building real estate predictive tools, not a licensed broker, lender, or investment adviser at this stage.
Primary NAICS
511210
Software Publishers
Rationale for Primary Classification
- PropChain's principal activity is the design, development, and publishing of proprietary software delivering predictive real estate analytics, dashboards, and decision-support tools
- Platform offered as hosted SaaS product with recurring subscription revenue and software-enabled workflows
- Terra Net, Terra Engine, PropPredict, and related algorithms are core IP embedded in software product, not sold as stand-alone consulting or bespoke projects
Secondary NAICS Classifications
1
541511 – Custom Computer Programming Services
Role: Supporting classification for limited custom integrations, pilots, and proof-of-concept work for MLSs, brokers, and other B2B partners. PropChain may occasionally design or extend APIs and analytics features specifically for partners, but these activities remain secondary to the main product.
2
518210 – Data Processing, Hosting & Related Services
Role: Supporting classification for Terra Net/Terra Engine data processing and hosting, including CurbScan telemetry, MLS feeds, and analytics workloads. While integral to the software product, some jurisdictions or RFPs may classify this work as hosting/data-processing.
3
531390 – Other Activities Related to Real Estate
Role: Supporting/contextual classification for describing PropChain's domain focus in real estate analytics, not as a licensed broker or agent. Can be used in contexts where broader real estate focus is requested, provided filings do not imply licensed brokerage activities.
Core Business Activities (Seed Stage)
01
Software Development & Publishing
Building and maintaining PropChain mobile and web applications, including user-facing predictive property search, curb-appeal tools, and market analytics. Packaging capabilities into freemium and paid subscription tiers plus B2B offerings.
02
Predictive Analytics & Data Platform
Ingesting multi-source data into Terra Net and running predictive models (PropPredict, ArchiSpect, CurbValue, CurbCraft) in Terra Engine to generate property-level and curb-level scores and forecasts.
03
SaaS, API & Data Licensing
Monetizing through SaaS subscriptions for individuals and professionals. Offering selected APIs and data products for MLSs, brokerages, and institutions under DaaS/API license agreements.
04
B2B Transaction Workflow Software
Designing software workflows to visualize and orchestrate steps in the real estate transaction process as a digital transaction management pipeline. At Seed, this remains in pilot/design and prototype phases.
05
CurbScan Data Collection
Operating 1-3 scanning rigs over time to collect curb-level imagery and telemetry to enhance Terra Net datasets and improve predictive models. Treated as data acquisition and R&D.
Activities Explicitly NOT Conducted at Seed
Regulatory Boundary Clarification
Real Estate Brokerage or Agency
PropChain does not act as a listing broker, buyer's agent, or representative of any party in a real estate transaction. Does not earn commission-based brokerage fees or hold itself out as a licensed real estate brokerage.
Escrow or Funds Custody
PropChain does not hold client funds, conduct escrow services, or operate trust accounts relating to transactions.
Mortgage Lending or Loan Brokerage
PropChain does not originate loans, underwrite credit, act as a mortgage broker, or arrange financing as a regulated activity.
Securities Brokerage or Investment Advisory
PropChain does not provide investment advice, manage portfolios, or act as a broker-dealer or crowdfunding portal. Any future crowdfunding/investment marketplace concept is strictly post-Seed.
Property Management or Construction
PropChain does not manage properties, collect rents, or provide construction or contracting services. Role is limited to software and analytics that inform such decisions by third parties.
NAICS Regulatory Implications
Core Regulatory Posture
PropChain should primarily be treated as a software and data analytics company, subject to general corporate and contract law, MLS/IDX/VOW/RESO compliance obligations, and general privacy/data protection regimes.
Real Estate & Financial Services Boundary
Because the platform relates to real estate, some states may scrutinize features to ensure PropChain is not performing activities requiring a brokerage license. Maintaining clear product boundaries (software & analytics only; no commissions, no representation, no escrow) is important to preserve classification under software/data NAICS codes.
Future Marketplace Features
Once PropChain contemplates activating crowdfunding, marketplace transaction rails, or tech-enabled brokerage beyond prototypes, it will need to:
- Revisit its NAICS mix
- Obtain specific regulatory advice
- Possibly form subsidiaries or affiliates with different NAICS codes and regulatory regimes
Practical Use
Use this NAICS & Business Activity Statement as the canonical reference when filling out IRS EIN applications, state business registration forms, investor questionnaires, and MLS data agreements.
NAICS Red Flags & Watchpoints
Scope Creep into Regulated Activities
As transaction workflow tools evolve, there is risk that some jurisdictions may view the platform as performing de facto brokerage, escrow, or lending functions. Any move toward facilitating or closing transactions should trigger a licensing and NAICS review.
Future Crowdfunding Features
The Business Plan describes future investment, crowdfunding, and crowd-lending capabilities. These may require entirely different regulatory frameworks and possibly different NAICS codes, and must not be considered active business lines until properly authorized.
State-by-State Variations
NAICS codes are federal, but state real estate commissions and financial regulators may interpret activities differently. Before entering new states, confirm that software offerings do not inadvertently trigger local licensing requirements.
Need for Periodic Update
As revenue composition shifts or new business lines activate, PropChain should reassess and update this statement and associated NAICS codes.
Privacy & Data Protection Framework
Regulatory Summary & Governance Approach
PropChain's privacy and data protection approach emphasizes applicable privacy laws and industry standards, user data rights handling, data retention and deletion, anonymization and aggregation for model training, and Data Processing Agreements with vendor controls.
GDPR (EU/EEA & UK)
Applies where PropChain processes personal data of EU/EEA/UK residents. Core principles: lawfulness, fairness, transparency, purpose limitation, data minimization, accuracy, storage limitation, integrity, confidentiality, and accountability.
CCPA/CPRA (California)
Applies when PropChain meets thresholds for "businesses" under California law. Focus: notice at collection, opt-out of selling/sharing, access/deletion/correction rights, restrictions on sensitive personal information.
RESO & MLS Standards
RESO Data Dictionary and Web API govern field-level and payload consistency for MLS data. MLS/IDX/VOW rules impose field-level display and retention constraints.
Regional & Sectoral Frameworks
Anticipates alignment with PIPEDA (Canada), LGPD (Brazil), emerging EU AI Act for higher-risk AI use cases, and HUD/FHA guidance for public/affordable housing datasets.
Data Categories & Processing Activities
User Account & Profile Data
Email, name/alias, basic profile settings, property preferences, saved searches, watchlists, and optional professional attributes (broker, investor, contractor).
Behavioral & Usage Telemetry
In-app behavior (page views, feature usage, search patterns), event-based telemetry for funnel analysis, device and approximate location metadata for security and UX.
MLS & Listing Data
Standardized RESO 1.6+ fields (address, list price, beds, baths, days on market) and MLS-specific fields, with strict segmentation between internal analytics/model training and permitted display.
CurbScan Telemetry
Street-level video/images from vehicles, GPS coordinates, timestamps, derived geospatial attributes, and extracted curb features aggregated into curb-level rows for Terra Engine.
Derived Analytics
Terra Engine scores, valuations, recommendations, heatmaps, risk scores, curb appeal metrics, aggregated statistics, and benchmarks.
All processing is tied to defined purposes: provide predictive search and property intelligence, support MLS/broker partners with analytics, improve models and ranking algorithms, support fraud detection and security monitoring, and measure performance of GTM and product experiments.
Legal Bases & Transparency
GDPR Legal Bases
01
Contract Necessity
Create and maintain user accounts, deliver subscription features, fulfill B2B pilot obligations
02
Legitimate Interests
Internal analytics, product improvement, security monitoring, non-invasive telemetry
03
Consent
Optional marketing communications, cross-context advertising, high-sensitivity processing
CCPA/CPRA Obligations
PropChain operates primarily as a "business" and in some pilots as a "service provider" to B2B partners.
Key Commitments
- Provide required notices including categories of personal information collected, sources, purposes, and third-party disclosures
- Maintain "Do Not Sell or Share" mechanism if engaging in any selling or sharing of data for cross-context advertising
- Treat certain B2B/MLS data as service-provider processing with contractual use limitations
Users receive clear privacy notices at or before point of collection, including layered explanations and links to full Privacy Policy. Governance materials describe a "My Data" dashboard and granular consent management for each data category.
User Rights Handling
GDPR, CCPA/CPRA & Analogous Frameworks
Access
Provide copy of personal data including basic profile and key derived fields where feasible
Correction/Rectification
Allow users to correct inaccurate personal data
Deletion/Erasure
Delete personal data subject to legal holds and contractual retention obligations
Portability
Provide user-submitted data in machine-readable formats on request
Restriction/Objection
Respect opt-outs for certain analytics, direct marketing, and cross-context ads
Rights requests handled via self-service in "My Data" dashboard where possible, with support channels for complex requests. Governance materials emphasize automation of deletion processes under "Right to be Forgotten" and user-triggered deletion events. All rights requests and outcomes are logged for auditability and regulatory inquiries.
Data Lifecycle Management
Retention, Deletion & Anonymization Framework
Ingestion
Confirmed, documented sources (MLS aggregators, curb-scan rigs, user inputs) with schema mapping and PII redaction where feasible before broader analytic use.
Storage
Encrypted at rest (AES-256) with strict RBAC and segregation of environments. NAS + Azure Data Lake hybrid with tiered storage for hot/warm/cold data.
Processing
Pseudonymization where identifiers not needed. Anonymization and aggregation before broad analytics and model training. Extensive logging of transformations.
Deletion
Automated workflows for user-triggered deletion and contract/policy-driven retention limits. Virtual Data Governance Group sets retention rules.
Category-Specific Retention Policies
User Accounts & Profiles
Retained while account is active and for limited period post-closure (12-24 months) for fraud prevention, dispute resolution, and legal compliance, then anonymized/aggregated.
MLS Data
Retention and use strictly governed by individual MLS/aggregator contracts (ListHub/Trestle/MLS Grid), RESO standards, IDX/VOW rules, and restrictions on training models beyond internal analytics where required.
CurbScan Telemetry
Raw video/images used primarily for feature extraction in near-real-time or batch pipelines, then downsampled and/or deleted subject to defined retention horizons and local privacy guidance around public-space imagery.
Security Logs
Security and access logs kept for security-appropriate period (often 12-24 months, longer if needed for incident investigation).
Security Controls & Privacy-by-Design
Technical Controls
Encryption
AES-256 at rest for databases, object storage, backups. TLS in transit for APIs, web, internal services.
Access Control
RBAC enforced in application and infra layers. Principle of least privilege and environment segregation.
Monitoring & Logging
Centralized logging for access, admin actions, data pipeline operations. Immutable logs for compliance-critical activities.
Vulnerability Management
Regular dependency scanning, patching, and security testing.
Privacy-by-Design Features
- Data Minimization: Avoid collecting fields that do not materially support product goals
- Granular User Control: Built-in consent prompts and opt-outs for higher-risk data types
- PII Separation: Separation of PII from behavioral/telemetry datasets where feasible
- AI Governance: Bias checks, explanation tooling, and guardrails around sensitive attributes
Subprocessors & Cross-Border Transfers
DPAs or data protection schedules executed with cloud providers, collaboration tools, and MLS aggregators. Cross-border transfers rely on Standard Contractual Clauses and applicable adequacy decisions.
AI & Model Governance
Responsible AI Framework
PropChain's AI governance framework references the EU AI Act and places emphasis on responsible AI, data minimization, and bias checks. The framework classifies Terra Engine use cases by risk level and implements safeguards against discriminatory outcomes.
01
Risk Classification
Classify Terra Engine use cases by risk level (low/medium vs any "high-risk" categories) and apply appropriate governance controls.
02
Feature Design
Avoid using sensitive personal data (race, religion, health) as direct features. Design models to rely on environmental and property attributes rather than individual-level identifiers.
03
Documentation & Review
Governance reviews for new AI features. Documentation of training sets, feature importance, and evaluation metrics.
04
Bias Detection
Implement safeguards against discriminatory outcomes including bias detection in scoring for neighborhoods or demographics.
Governance & Accountability Structure
Founder/CEO
Overall accountability for legal compliance and policy sign-off
Product & Engineering Leads
Operationalize privacy-by-design in code, infra, and UX
Legal/Regulatory Advisors
Guide interpretations of GDPR/CCPA/MLS constraints
Virtual Data Governance Group
Stewards policies on data classification, retention, and ethical use
Roadmap Items
- Formalize internal Data Protection Lead role (DPO-equivalent if EU thresholds are met)
- Develop DPIAs (Data Protection Impact Assessments) for high-risk processing such as curb-level telemetry and predictive risk scoring
- Maintain Records of Processing Activities (ROPAs) to satisfy GDPR and similar frameworks
- Conduct periodic privacy audits and pursue certification paths (e.g., SOC 2 alignment)
Documentation Maturity
Core governance concepts are in place (data lifecycle, consent management, auditability), with continued evolution of DPAs, data maps, and internal SOPs expected as the company approaches SOC 2 and privacy certification pathways.
Privacy Red Flags & Open Items
Areas for Review & Future Work
Formal DPO / Data Protection Lead
PropChain is still early-stage; a designated DPO or DPO-equivalent will be formalized as EU user volumes, curb-scan telemetry, and MLS data scale.
MLS Contracts vs Model Training
Each MLS/aggregator may treat model training differently. Investors and counsel should confirm whether PropChain can use MLS data to train models beyond internal analytics and any restrictions on retention, redistribution, or derivative data reuse.
CurbScan Telemetry Risk Profile
Street-level imagery and precise location data can be sensitive if mismanaged. DPIAs, retention limits, and robust anonymization of incidental personal data (faces, plates) need to be clearly documented and implemented.
Cross-Border Data Transfers
As PropChain acquires EU/UK users or partners, SCCs and transfer risk assessments must be actively maintained and kept current with regulatory changes.
Third-Party Tracking & Advertising
If PropChain later introduces retargeting or third-party tracking beyond basic analytics, it will need updated cookie banners, consent flows, and robust "Do Not Sell/Share" and GPC handling.
Compliance Summary & Next Steps
Integrated Market, Regulatory & Privacy Framework
PropChain's comprehensive market, MLS, compliance, and privacy framework positions the company as a software and data analytics platform with conservative Seed-stage revenue targets representing a tiny fraction of a very large, multi-stream market opportunity.
Market Opportunity
- $67.7B+ global platform TAM across analytics, workflows, and data
- $2.7B-$5.9B combined U.S. SAM in ORI-2 priority markets
- $100k-$400k conservative Seed-period ARR targets
- $33.8M-$67.7M long-term SOM as multi-year upside
Regulatory Posture
- Primary NAICS 511210 (Software Publishers)
- MLS aggregation via ListHub, Trestle, MLS Grid
- RESO 1.6+ compliance with ≤90-day retention
- GDPR, CCPA/CPRA, and sectoral framework alignment
The framework emphasizes deliberate conservatism in FP&A, clear separation of internal analytics from public display, robust data lifecycle management, and privacy-by-design principles. All large revenue scenarios are explicitly positioned as long-term upside rather than near-term targets, with realistic room for out-year growth without relying on aggressive or opaque assumptions.