How we handle your data

For operators deciding whether to contribute data, and for counsel reviewing us as a vendor. This page summarises our Anonymisation and Aggregation Methodology in plain words.

Three tiers

Raw data — contract terms, payment flows, status events — lands in a logically isolated tenant per company. It is never exposed or queryable through the portal.

Standardised contract histories are rebuilt from the raw data against one set of definitions, so books from different systems become comparable. They stay inside the company's isolated boundary, visible only to users that company has authorised.

Only cohort-level aggregates cross into any shared view. The step from contract level to cohort level is one-way: the shared layer contains no keys, identifiers or record-level data that could rebuild the tiers below it.

No personal data

We ingest contract-level financial data only. We do not request names, telephone numbers, national identification numbers, addresses or GPS coordinates. If such fields arrive in a file anyway, they are dropped on ingestion and never stored. Contract identifiers are kept only to match payments to contracts, and are stripped entirely before aggregation.

Anonymisation rules

Shared analytics are aggregated by origination month and product category. No individual contract appears in any shared view. Any displayed cell draws on data from at least three companies; smaller cells are suppressed or merged, and the rule holds across every filter and drill-down. Where one company would dominate a cell, that cell is suppressed too. In benchmarks you see your own company named; every peer is anonymous.

Deletion

Raw and standardised data are deleted within 30 days of a request or the end of the agreement, with backup copies purged within 90 days. Anonymised aggregates contain nothing attributable to any company.

The full versioned Anonymisation and Aggregation Methodology and our Data Contribution and Licence Agreement are available on request at info@maf-lab.com.