Legal & Liability

Data protection, scope, and usage boundaries

We provide end-to-end protection of the material you submit, for as long as an engagement is active, conditioned on you (our client / partner) agreeing with us, in writing, on:

• the exact scope of what may be examined,
• the methods we are authorized to use on it (static analysis, secret scanning, dependency checks, or manual review), and
• your acceptance of how we will use and store the material for the purpose of that engagement.

This agreement is the engagement document described on our Services page. We do not examine, use, or store material outside the scope and boundaries that document sets out.

While an engagement is active

Submitted material is kept in an isolated, access-restricted workspace created specifically for that engagement, and is never shared with any third party.

Retention and deletion

We do not store your submitted code, or the findings/report content generated from it, after the engagement's liability/retention period ends. Concretely:

• Each engagement has a defined retention period (30 days from activation, by default, stated in the engagement agreement).
• When that period ends, the submitted code and the content of the generated report (findings, descriptions, evidence) are both deleted. What remains is a bare record that the engagement took place (an ID and dates), kept only for billing and dispute history.
• Either party may withdraw the engagement at any time before that, which deletes the submitted code and the report content immediately, on request.
• We keep operational logs of actions taken (e.g. "an engagement was activated on this date"), because that is necessary for our own accountability and audit trail — but these logs do not contain your code, your findings, or any project-specific content.

Limitation of liability

Mathcore's review is advisory. We identify issues we find within the agreed scope and methods; we do not guarantee that a review will find every issue, and a review should not be treated as a complete guarantee of the security or correctness of your code.

To the fullest extent permitted by applicable law, Mathcore and its operator disclaim all liability for any loss, damage, cost, or expense — direct, indirect, incidental, or consequential — arising from or related to your use of, or reliance on, our review, findings, recommendations, or any software engagement we deliver, including losses arising from testing, deploying, or otherwise experimenting with the results. This includes, without limitation, lost profits, lost data, business interruption, and losses arising from issues we did not identify.

This limitation does not apply to, and nothing on this page excludes or limits, liability that cannot lawfully be excluded or limited under the law that applies to a given client — for example, liability for fraud, or for death or personal injury caused by negligence, where such limitations are not permitted. Where a limitation would otherwise be unenforceable in your jurisdiction, only that limitation is removed; the rest of this page still applies.

Your responsibilities

You confirm, as part of every engagement, that you own the submitted material or are authorized by its owner to submit it. You are responsible for testing any recommended change in your own environment before relying on it in production, and for maintaining your own backups before making changes based on our findings.

Mailing list

If you sign up for occasional updates, we only use your email to send you those updates, we never sell or share the list with a third party, and every email includes an unsubscribe link that takes effect immediately with no login required. We do not currently support a confirmation email upon signup (see FAQ); if you did not sign up yourself, use the unsubscribe link or email us.