Security
The policy below is the disclose.io core VDP terms, carried word for word rather than rewritten in our own voice — revision 0a19d51, CC0-1.0. We filled in the scope and contact sections the template exists to have filled in, and changed nothing else. Anything Shallot adds beyond the standard is in a separate section at the end, so you can see where the standard stops and we start.
Introduction
Shallot welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.
Systems in Scope
This policy applies to any digital assets owned, operated, or maintained by Shallot.
Named explicitly, because a safe harbour is only as good as its scope:
- shallot.recipes, and its subdomains
- cdn.shallot.recipes
- getshallot.app, which redirects here
- The Shallot iOS app, and its share extension
Out of Scope
- Assets or other equipment not owned by parties participating in this policy.
Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
In our case that means these, named so there is no ambiguity. We cannot authorise access to systems we do not own, and nothing on this page attempts to — however much of Shallot they happen to be running:
- Supabase — our database and authentication provider
- Vercel — hosting for this site
- Cloudflare — our CDN and image storage
- Resend — transactional email
- Apple, including the App Store and TestFlight
Our Commitments
When working with us, according to this policy, you can expect us to:
- Respond to your report promptly, and work with you to understand and validate your report;
- Strive to keep you informed about the progress of a vulnerability as it is processed;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
- Extend Safe Harbor for your vulnerability research that is related to this policy.
Our Expectations
In participating in our vulnerability disclosure program in good faith, we ask that you:
- Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
- Report any vulnerability you’ve discovered promptly;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly;
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- You should only interact with test accounts you own or with explicit permission from the account holder; and
- Do not engage in extortion.
Official Channels
Please report security issues via security@shallot.recipes, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.
Safe Harbor
When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:
- Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
- Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.
Beyond the standard
Everything above is the disclose.io text. Everything below is ours, and adds to it rather than modifying it.
What to include
Whatever you have. You do not need to ask permission first, and you do not need a polished write-up — a rough description is genuinely more useful to us than a delayed one. If you are deciding what is worth writing down, these help most:
- What you did, in enough detail that we can do it again
- What happened, and what you expected to happen instead
- The URL, and roughly when you tried it
- What you think an attacker could do with it
What “promptly” means
The standard commits us to responding promptly without saying how promptly. Shallot is built and run by one person, so these are honest numbers rather than impressive ones:
- Within 3 working days — we acknowledge your report and tell you whether we have reproduced it
- Within 10 working days — we tell you what we plan to do and roughly when
- As it moves — we keep you updated until it is fixed, rather than going quiet
If something is being actively exploited, say so in the subject line and we will drop everything else.
What “a reasonable amount of time” means
Ninety days. The standard asks you to give us reasonable time before disclosing publicly, and left at that, reasonable means whatever we decide later. If we have not shipped a fix by then and you publish, that is the deadline working as intended — it is a deadline on us, not a veto we are holding over you. If a fix needs longer for a reason we can explain, we will ask, and you are free to say no.
Credit, and no bounty
We will credit you by name in the fix announcement if you would like us to, and stay quiet about your involvement if you would prefer that.
There is no bug bounty. Shallot is pre-launch and has no revenue, so we cannot pay for reports, and would rather say that plainly than let you find out after the work is done.
Content and copyright
This page is for security vulnerabilities. Copyright, takedown and content complaints go to legal@shallot.recipes. Shallot publishes nobody’s recipes, and has no plans to — there are no public pages, no shared recipe URLs and no feed, and a public sharing surface was dropped in July 2026 rather than built. The address exists anyway, because a company with nowhere to send a complaint is its own problem.
Machine-readable
This policy is advertised at /.well-known/security.txt per RFC 9116.