Skip to content

Security

Version 2 · Last updated 7 October 2026

If you think you’ve found a security problem in Milkcrate, we want to hear about it. This page explains how to report it and what you can expect from us.

How to report a problem

Email security@milkcrate.site. Tell us what you found, where (the address or the part of Milkcrate), the steps that reproduce it, and what someone could do with it. Screenshots or a short proof of concept help.

Please don’t report security problems through the report form, an enquiry form on a Milkcrate page, or social media, and don’t share the details with anyone else while we fix it.

What’s in scope

trymilkcrate.com, app.milkcrate.site (the Milkcrate dashboard), api.milkcrate.site (the API behind it) and the Milkcrate pages at <name>.milkcrate.site.

The services we use, such as our payment, hosting and email providers, have their own disclosure programmes: report problems in their systems to them. If you aren’t sure whether something is in scope, email us and ask.

Testing in good faith

Test only with accounts you own or have permission to use. Don’t access, change or delete anyone else’s information. If you come across someone else’s information by accident, stop, don’t keep or share it, and tell us in your report.

Don’t try denial of service or load testing, don’t run automated scans that slow Milkcrate down for other people, and don’t send spam through our forms. No phishing or social engineering of our team or our users, and no physical attempts.

Give us a reasonable time to fix the problem before you tell anyone else about it. We’ll agree a date with you, usually within 90 days of your report.

What we do

We aim to reply within 5 business days to confirm we have your report, and we keep you updated while we investigate and fix it.

If you follow this policy in good faith, we treat your research as authorised: we won’t take legal action against you over it or ask law enforcement to investigate you.

We don’t run a paid bug bounty. If you’d like, we’ll thank you by name once the problem is fixed.

What we usually don’t treat as a vulnerability

Reports from automated scanners with no demonstrated impact, missing security headers or cookie flags on their own, version numbers in responses, clickjacking on pages with no sensitive action, self-XSS, and rate limits on requests that don’t touch anyone’s account or data. If you can show real harm, report it anyway.

Changes to this policy

When this policy changes, we update the date at the top of this page.