Report & Data Contribution Policy

This policy explains four distinct data types on Moonora Lab and how each is handled. By submitting a report or contributing Vault data, you also agree to our Terms, Privacy Policy, and Community Guidelines.

• Community reports — user-submitted narrative/payment experiences that may be reviewed and published.
• Private Payment Vault imports — user-private source data; not public merely because uploaded.
• Qualified trusted observations — internally validated derived payment timing; may be automated; not the same as human verification.
• Public company aggregates — company-level statistics without raw invoice identifiers, amounts, filenames, uploader identity, or exact private event dates.

• Describe first-hand business experiences only.
• Prefer objective payment timing facts over speculation.
• One report per invoice or transaction helps accuracy.

I certify that this report reflects my organization's genuine business experience with this company and that, to the best of my knowledge, the information provided is accurate.

• Vault uploads stay private by default.
• Contribution requires a separate unchecked affirmative consent.
• Only selected eligible records are processed.
• Automated validation may qualify clean records or quarantine ambiguous ones.
• Automatic qualification is not an endorsement.
• High-impact or suspicious events may generate internal integrity alerts for Moonora operators.

• Company matching prefers trusted MC/USDOT identity for auto-qualification.
• Fuzzy or weak matches may quarantine.
• Duplicate detection uses protected commitments — not public invoice numbers.
• Contributor influence is capped so one account cannot dominate timing.

We do not publish abuse-detection thresholds that would enable evasion.

• Severely overdue: more than 30 days past a known due date, or at least 60 days from invoice when no due date is available.
• Confirmed unpaid: a separate stronger state requiring the implemented evidence standard — not every severely overdue item.
• Open-not-due observations are not treated as payment failures.

Trusted Payment Pulse unlocks after enough qualifying observations from enough distinct contributing accounts. Confidence labels evidence strength and does not change the numeric score. Aggregates may update after correction, revocation, rematch, or recalculation.

• Community report disputes follow the verified-representative process.
• Trusted signal challenges and evidence correction/removal are separate paths.
• Future-only consent revocation stops new processing; already-qualified evidence needs a separate request.
• Admins may rematch, revoke, restore, or reprocess through the integrity queue.
• Filing a challenge does not automatically remove evidence.

Details: Data Correction & Challenges.

• Personal attacks, hate speech, illegal content, or confidential customer details that should not be public.
• False, retaliatory, or fraudulent statements.
• Fabricated imports, altered dates, multi-account manipulation, or dedupe evasion.
• Moonora may reject, remove, quarantine, or suspend accounts that violate this policy.

legal@moonoralab.com