For fund compliance teams
Data licensing and compliance pack
Every dataset in the investor feed is traced to a public source with a named licence. This page is the answer sheet for an alternative-data due-diligence questionnaire: where each source comes from, whether it can be resold, what attribution it needs, and how personal data is handled.
Sources marked pending are used in the free map and research, but stay out of paid tiers until commercial reuse is confirmed in writing.
Sources and resale status
Loading the source register…
Due-diligence answers
| Material non-public information | None. Every input is published openly by a public body, a charity or a public API. No data is obtained from company insiders, paid expert networks or private communications. |
|---|---|
| Collection method | Official bulk files and documented public APIs, called at low volume on a schedule. No logins are bypassed and no terms-of-use restrictions are circumvented. No website scraping. |
| Personal data (UK GDPR) | Not distributed. Address-level and name-level fields are discarded at ingest or aggregated before storage. Planning applicant names are kept only when they match a company in the ticker map. |
| Point-in-time history | Every value carries first_seen_at (when our pipeline first recorded it) and source_version. Revisions are appended as new rows and never overwrite history, so as_of queries reproduce exactly what was known on a past date. |
| Backfilled history | Where history is rebuilt from a later file (for example Price Paid years before the pipeline started), the rows are stamped with the backfill run date and flagged source_version = backfill:…. Treat them as restated history, not as-first-published values. |
| Lineage and retention | Raw pulls are archived by source and date (Cloudflare R2 when configured). Aggregates are versioned in git, so every published number can be traced to the run and source file that produced it. |
| Entity mapping | Company links use data/ticker-map.json: name aliases, ticker, validity dates (to handle mergers) and a published match confidence. It is reviewed by hand every quarter. |
| Known biases | Planning coverage depends on what councils publish. FixMyStreet reflects who reports, not where problems are, so it is never used to rank areas. PV_Live and flood data are regional estimates, not site readings. |
| Contact | Privacy and legal: landmanagementviewer@outlook.com · Privacy Policy. Source-specific licence confirmations are tracked below. |
Permission requests
These are the drafted requests for sources whose commercial reuse is not yet confirmed. The status on this page changes once a written reply is received.
Loading…