Refunds

The policy, in one paragraph

Email us within 30 days of paying and we will refund you in full, to the card you paid with. You do not need to explain why. When we issue the refund we also withdraw your certificate, so the public verify page stops showing it as active. That is the only condition, and the reason for it is below.

Why the certificate comes down

The certificate is a statement we are making to a buyer on your behalf. A buyer who follows it to our verify page is trusting that we did the work and that we stand behind it. If the report has been refunded, we are not standing behind it, and leaving the certificate up would mean showing a buyer something we have effectively disowned.

A withdrawal is not a revocation. Revocation is reserved for misconduct, it carries a reason category, and it appears in our public revocation log. A withdrawn certificate simply stops being published. Nothing about a refund is recorded anywhere a buyer can see, and nothing about it reflects on you.

Your report stays in your account either way. You keep what you learned about your code. What you give up is the ability to show a buyer a certificate you have been refunded for.

A low grade is not a reason we say no

It is also not a reason we say sorry. We charge the same fee whatever the result, our sales copy never promises a grade, and a report that told you nothing uncomfortable would not be worth showing a buyer. If your grade is lower than you expected, the remediation list is ranked by how much each fix would move it, and one fix-and-rescan is already included in what you paid.

The free preview exists so that this is never a surprise. You see roughly a third of the findings, drawn from real analysis of your actual repository, before you are asked for any money.

What within reason means

We would rather write this down than leave it to our discretion on the day. We may decline a refund in these cases, and only these:

• The request comes more than 30 days after payment.
• The certificate has already been used to complete a sale of the product, and the buyer relied on it. At that point withdrawing it takes something away from someone who is not party to this refund.
• Repeated refunds across multiple analyses by the same person or for the same product. At $299 an analysis costs us real money to run, and a preview-then-refund loop is not what this policy is for.
• The report was obtained by misrepresenting who owns the repository.

If we decline, we will tell you which of these applies and why. We are not going to invent a fifth reason.

If you paid for someone else's scan

A buyer-funded scan is refunded automatically if it is never claimed. You pay, the seller gets a link, and they have 30 days to redeem it against their repository. If that window passes we put the money back without you having to ask, because you paid for an assessment and no assessment happened.

Once a seller has claimed it, the 30-day policy above applies and it is theirs to invoke, not yours. At that point the report exists and belongs to them. If they claimed it and then did not share it with you, tell us: that is not what claiming it means, and we would rather hear about it than not.

How to ask

Email hello@struckcode.com from the address on your account, and mention the report you want refunded. We will confirm within one business day and issue the refund the same day. Your bank then typically takes 5 to 10 business days to show it, which is their timing rather than ours.

Certificate withdrawal is currently a manual step on our side. We do it within two business days of issuing the refund.