Hold every record
to the standard.
Then prove it.

MADDS sets the rules, checks and ownership that keep your data complete, accurate and defensible — quality you can measure, governance you can show an auditor, and one version of every number the business relies on.

  • Profiling
  • Rule design
  • Stewardship
  • Audit trail
  • Compliance mapping
LTL UTL ±0.5% TOL Δ 0.31% WITHIN TOLERANCE SAMPLE · 1,000 RECORDS 12 RULES ACTIVE 1,000,000 RECORDS
How we look at a dataset: sample it, measure it against agreed tolerance, and record the reading — every single day.

Quality dimensions

Six tests your data has to pass.

We profile every core table against six dimensions, agree thresholds with the people who use the numbers, and wire the checks into the pipeline. Failures surface on the day they happen — not in a board meeting six weeks later.

Every row below starts failing and flips to passing as you scroll — that flip is the work MADDS does.

  1. Completeness

    Every required field is actually filled.

    Failing Passing

    12,400 blank phone numbers in the customer table.

    99.6% complete — the remaining blanks are quarantined and owned.

  2. Accuracy

    Values match the real world, not just the schema.

    Failing Passing

    4.1% of addresses fail delivery validation.

    99.1% verified against the source of record before load.

  3. Consistency

    The same fact reads the same way everywhere.

    Failing Passing

    Three spellings of one customer name across CRM, ERP and billing.

    One golden record, matched and propagated to every system.

  4. Timeliness

    Data arrives when the decision needs it.

    Failing Passing

    The sales feed lands 26 hours late, and nobody is told.

    30 days inside SLA — lag under 15 minutes, breaches alerted.

  5. Uniqueness

    One record per real-world thing.

    Failing Passing

    18,400 duplicates sitting quietly in the customer table.

    0 open duplicates — match rules written down, versioned and reviewed.

  6. Validity

    Values follow the agreed rules and ranges.

    Failing Passing

    Dates arrive in four formats; 9% fall outside any valid range.

    99.4% valid — the schema is enforced at the pipeline door.

Stewardship

Unowned data is just rumour.

Governance breaks when everyone assumes somebody else is responsible. MADDS writes four roles into your operating model — with mandates people can actually follow — and records who answers for what in the data catalogue.

Audit trail

Every change leaves a receipt.

Who changed what, when, from where, and under which rule. The trail is written as the work happens — not reconstructed the week before an audit — retained on schedule, and exportable in the format your auditor actually asks for.

  • Reads are logged too

    Access to personal data is recorded, not just edits. If someone looked, the trail says so.

  • Retention on schedule

    Seven years by default, or the period your regulator requires — held in storage that cannot be quietly rewritten.

  • Evidence on demand

    CSV, JSON or a signed evidence pack: one request, one export, no screenshots in a slide deck.

MADDS · DATA AUDIT RECEIPT

asset: customer_master · region: IN · 12 Feb 2026

06:00:02 job · daily refresh started

06:14:47 rule · completeness · pass 99.6%

06:15:11 rule · uniqueness · pass 0 dupes

06:15:40 rule · validity · pass 99.4%

09:32:18 user · r.iyer updated tax_id

09:32:19 note · ticket fin-2291 · owner approved

11:04:55 access · finance-role granted · 30d

14:27:09 export · pii column removed · dpdp-4

16:51:02 rule · timeliness · sla met · lag 11m

18:40:33 seal · day closed · hash 7f3a…c19b

10 events · 0 unexplained · retained 7 years

One asset, one day — printed exactly as the trail records it.

Compliance

Standards we build in, not around.

Controls are mapped to the frameworks your auditors recognise, and the evidence is collected by the pipeline rather than assembled under deadline. When a requirement changes, the rule changes in one place.

Evidence assembles as the work happens — access reviews, data protection impact assessments, records of processing, control tests — so the audit pack is a download, not a project.

Policy in practice

Same data. Different discipline.

One revenue dataset, two organisations. The numbers themselves are identical — what differs is everything around them: the rules, the names, the receipts. Hover a row to see the pair.

Before · weak governance

revenue_report_march.xlsx

  1. The number

    Three “final” revenue figures in circulation: ₹1.24, ₹1.41 and ₹1.18 crore.

  2. The owner

    Nobody admits to owning the field, so the fix waits for a volunteer.

  3. The definitions

    Each team counts “revenue” its own way — and all three ways ship in reports.

  4. The freshness

    Last refresh: unknown. The workbook is a copy of a copy.

  5. The history

    Who changed the total? No log, no answer, no recourse.

Verdict — three meetings to agree one number.

After · strong governance

revenue_report_march · certified

  1. The number

    One certified figure: ₹1.41 crore — versioned, signed, traceable to source.

  2. The owner

    A named owner and steward in the catalogue, with a response SLA.

  3. The definitions

    One published definition of “revenue”, change-controlled and versioned.

  4. The freshness

    Refreshed at 06:00 daily against a 15-minute SLA, monitored and alerted.

  5. The history

    A full audit receipt for every change, retained for seven years.

Verdict — one number, agreed by default.

The raw data was identical in both organisations. The only difference is what surrounds it — and that is the part MADDS builds.

Put your data on the record.

A two-week quality and governance review: we profile the core datasets, agree the rules and thresholds, name the owners, and leave you with a scorecard, a rule register and a plan your auditors will recognise.

MADDS Legal & policies

Privacy Policy

Updated Draft for review

Your information, handled with purpose. This draft explains the information collected through the MADDS website, why it is requested, and how to contact us about it.

Information you choose to share

When you send an enquiry or project brief, we collect the details you enter: your name, email address and message, together with any company, phone, country, industry, service interests, budget or timeline you choose to provide. Newsletter sign-ups collect your email address and subscription status.

Please do not include passwords, payment-card details, identity documents or sensitive personal information in general enquiry forms. Only share information about another person when you are authorised to do so.

How that information is used

  • Enquiries and proposals: to understand your request, reply to you and discuss a potential project.
  • Project communication: to coordinate agreed work and maintain relevant business records.
  • Optional updates: to manage a newsletter subscription you request. You can ask to stop these messages at any time.
  • Site operation: to maintain forms, investigate technical problems and protect the website against misuse.

Submitting an enquiry is not, by itself, an instruction to subscribe you to marketing messages. Any permission needed for an additional purpose should be requested separately.

Website technology and service providers

Security cookies help the site's forms work correctly. The website also loads fonts and interface libraries from external services, including Google Fonts, Cloudflare's cdnjs and jsDelivr. When your browser requests those files, the provider receives connection information such as your IP address and browser details.

Hosting, email and technical-support providers may process information needed to operate the service. The live provider list, hosting locations and any international transfers must be confirmed before this draft becomes a final notice. Read the Cookie Policy for more detail about website storage.

Retention and security

The proposed approach is to keep enquiry and project records for as long as needed for the relevant conversation, agreed services, record-keeping duties and dispute resolution. Subscription information should be reviewed when someone unsubscribes. Specific retention periods and deletion processes still need to be confirmed by MADDS.

No website or transmission method can be guaranteed completely secure. Access controls, hosting safeguards and backup arrangements should be reviewed against the information being handled.

Your choices and requests

You may contact us to ask about information you supplied, request a correction or deletion, or withdraw a newsletter request. Rights and exceptions depend on the applicable law and the circumstances. We may need reasonable information to verify that a request relates to you before releasing or changing records.

For a privacy question or concern, email info@madds.io with the subject “Privacy request”. This contact route does not limit any right you may have to approach the relevant authority.

Children and changes to this notice

The website presents business services and is not intended to collect information from children. Contact us if you believe a child has submitted personal information. When this notice changes, the revision date will be updated so you can identify the latest version.

Draft for review. The legal entity, processing grounds, providers, retention schedule and applicable rights must be confirmed before publication as a final policy.

Questions about this policy?
info@madds.io