Security and data boundary

Mater LTD designs Mater so that raw business data stays local by default. Customer-specific records, documents, messages, invoices, screenshots, and identifiers stay inside the customer-controlled environment. The central Mater layer receives only leakage-scanned, non-raw operational signals.

Data boundary

• Local-first processing for raw business data
• Metadata-only admin visibility
• Leakage-scanned collective learning
• Approval boundaries for new access and connectors
• External effects gated by consent, plan, and security policy

What central learning uses

Central improvement uses only safe, non-raw signals such as receipts, error classes, connector patterns, capability gaps, and aggregate improvement metadata. Customer raw records are never centralized to make Mater better.

Website and request form

The public request form is served over HTTPS, validated server-side, rate limited, and protected against spam and injection. We collect only the lead data needed to review company fit, log limited privacy-conscious metadata, and never expose internal contact addresses in the page.

To report a security issue, see our responsible disclosure page.