Skip to main content

Methodology

Peer Benchmarking Methodology

SyndTrack's anonymized peer benchmarking lets real-estate syndication investors compare their portfolio performance against a community of peers — without exposing individual deal data. This page explains how we collect, aggregate, and protect that data.

Opt-in Consent

Peer benchmarking is strictly opt-in. Your portfolio data is never included in any aggregation unless you explicitly choose to participate. You will be shown a clear explanation of what data is contributed and how it is anonymized before you consent.

You can opt out at any time. Opting out immediately flags your data as excluded; the next aggregation run will not include your portfolio. No historical removal is required because benchmarks are recomputed on each cache refresh.

Consent is versioned. If the scope of data collection changes materially, we will ask for your consent again under the new version.

Privacy Protection: k-Anonymity & Minimum Thresholds

To prevent individual deal leakage, SyndTrack enforces two thresholds before displaying any benchmark segment:

When either threshold is not met, the benchmark statistics for that segment are hidden and replaced with a "Insufficient data" indicator. This ensures no individual portfolio can be reconstructed from the published aggregates.

Aggregation Approach

For each segment, SyndTrack first computes a per-investor summary statistic (e.g. average IRR). Cross-investor percentiles and means are then computed on those per-investor summaries. This two-step approach ensures that investors with large portfolios do not dominate the reported statistics relative to investors with fewer deals.

All aggregated statistics are stored only in the pre-computed cache table. The cache table contains no user IDs, deal IDs, or any other personally-identifiable information.

Benchmark Segments

Portfolio IRR vs. Peer Median (by Vintage Year)

For each vintage year cohort, SyndTrack computes each opted-in investor's average deal IRR, then calculates the 25th percentile, median, and 75th percentile across those per-investor averages. Grouping by vintage year controls for market-cycle effects.

Inputs used

  • Deal IRR (annualized)
  • Vintage year of first investment

Privacy note

IRR is averaged per investor before statistical aggregation, so no individual deal IRR is ever surfaced.

Distribution Yield vs. Peer Median (by Asset Class)

Distribution yield (DPI — distributions paid / called capital) is calculated per investor per asset class. The median and interquartile range across investors is then reported for each asset class (e.g. multifamily, industrial, private credit).

Inputs used

  • Total distributions received
  • Total called / invested capital
  • Asset class of each deal

Privacy note

Yield is aggregated at the investor level before cross-investor statistics are computed.

Sponsor Concentration vs. Recommended Thresholds

For each opted-in investor, SyndTrack computes the fraction of called capital allocated to the single largest sponsor. The peer distribution of this concentration ratio is then reported. The recommended threshold is 25% — allocating more than a quarter of a portfolio to a single operator is generally considered a concentration risk.

Inputs used

  • Called capital per deal
  • Sponsor identifier per deal

Privacy note

Only the top-sponsor ratio (a single scalar per investor) is used in aggregation. No sponsor names are shared.

Asset Class Diversification vs. Peer Average

For each asset class, SyndTrack reports the peer-average allocation share — what fraction of portfolio capital the typical opted-in investor has in that asset class. This lets investors compare their own allocation mix against the peer group.

Inputs used

  • Called capital per deal
  • Asset class per deal

Privacy note

Per-investor allocation percentages are aggregated across investors. No individual allocation breakdown is exposed.

Data Freshness

Benchmark segments are pre-computed and cached for up to 1 hour. The cache timestamp is shown in the UI alongside each benchmark. When a user opts out, the cache is immediately invalidated so the next request triggers a fresh computation that excludes the opted-out user.

What We Never Share

Questions?

If you have questions about how your data is used in peer benchmarking, please contact us at privacy@syndtrack.io.