Recoverable workflows
Long-running imports and document jobs expose progress and terminal states. Retry and idempotency controls are applied where a repeated request could otherwise create duplicate work.
This page explains how MatchAudit approaches recoverability, incidents and service dependencies. It does not turn internal objectives into a contractual SLA. Binding commitments are stated in the agreement signed for the relevant product and plan.
Operating design
These are implementation patterns and operating practices, not a claim that outages or processing delays cannot occur.
Long-running imports and document jobs expose progress and terminal states. Retry and idempotency controls are applied where a repeated request could otherwise create duplicate work.
If a sanctions source refresh fails, screening continues against the most recent successful managed snapshot. Source timestamps and dataset state remain visible for review.
A document that requires malware inspection is not released for analysis when the configured scanner is unavailable or returns a non-clean verdict.
File sizes, row counts, request bodies and provider responses are bounded. Higher-volume and contract-specific limits are agreed for the applicable plan and workflow.
Incident handling
An outage, degraded workflow and personal-data breach are not interchangeable. Classification and notification depend on the actual event and applicable obligations.
Confirm scope, affected service and customer impact before publishing a conclusion.
Restrict the affected path, preserve relevant evidence and prevent avoidable further impact.
Restore safe operation and validate the affected workflow before normal processing resumes.
Notify affected customers as required by the applicable contract, DPA and law.
Record follow-up actions and track remediation appropriate to the incident.
The Data Processing Addendum governs personal-data breach notification for processor activities. The Privacy Notice explains MatchAudit's controller-side processing.
Contract boundary
A trustworthy reliability page makes the source of each promise clear. Ask for contract language when your risk assessment requires a measurable target.
Procurement evidence
Tell us the workflow, criticality, data volume, required support window and recovery expectations. We will identify what can be evidenced and what would need contract-specific terms.