[EMAIL]
What to send
A wrong number. The page, the value, and what you think it should be. If you have a source, send it; if not, send it anyway. Every value on this site names where it came from precisely so that this message is possible to write, and a correction is worth more to us than a compliment.
An audit result. If you ran the checklist against Materiascope and got a different score than we published at /trace/self-assessment, that is a bug in our document. Send it, including if it is better than ours.
A disagreement with the framework. The evidence ladder is a position, not a fact. If a rule gets a real case wrong, that is the most useful thing anyone can send — and the right place is an issue at github.com/materiascope/trace, where the argument is public.
A material we do not cover. Coverage is uneven and we say where. Knowing what people are actually blocked on shapes what gets connected next.
What to expect
Response time: usually a day or two, occasionally longer. If something is time-critical, say so in the subject line.
On enterprise and on-premise: we do not have it. If your data cannot leave your network, this product is not currently for you, and we would rather tell you that in an email than after an invoice. Tell us anyway — the queue is shaped by who is asking.
On pricing and refunds: first month refunded, no argument. The failure mode we care about is somebody paying for coverage we do not have. See pricing.
What this page does not offer
- Phone support. There is no phone.
- Guaranteed response times. No SLA exists, so claiming one would be a lie.
- Engineering advice. We cannot tell you which material to use. We do not know your application, we are not carrying your professional responsibility, and a vendor doing either by email is a vendor to be careful with.