Security Policy
Version 1.0 — Effective October 7, 2026
If you have found a security flaw in the Software published by OakChet LLC ("OakChet", "we", "us"), or in oakchet.com, we would like to hear about it, and this page says how. Capitalized terms have the meanings given in section 1 of our Software License Agreement.
How to tell us
Email support@oakchet.com. Put "security" in the subject so it is not treated as an ordinary support request.
Tell us which product, what you found, how to reproduce it, and what you think the consequence is. A rough description is better than none — do not wait until you have a polished write-up.
What we will do
- Acknowledge your report. A real person will consider and acknowledge your report.
- Ignore apparent spam. Any report that looks like spam or phishing will be completely ignored.
- Tell you what we think, including if we disagree that it is a problem, and why.
- Keep you informed while we work on it, and tell you when it is fixed.
- Credit you in the release notes if you would like to be named, or not if you would rather not be.
We do not pay bounties. We are not pretending to have a budget we do not have.
What we ask of you
- Give us a reasonable chance to fix it before telling anyone else. What is reasonable depends on the flaw; talk to us and we will agree a date rather than impose one.
- Do not test against anyone else's data or machines. The Software runs on a person's own computer and reads their own files. Use your own.
- Do not do anything destructive — no denial of service, no deleting or altering data, no social engineering of anyone.
- Do not access, copy or keep anyone's personal information. If you come across some while investigating, stop and tell us.
What we promise you in return
If you follow the above and report in good faith, we will not pursue legal action against you, and we will not ask anyone else to. We will treat your report as a contribution, which is what it is.
If you believe you have found something and are unsure whether looking further would cross one of those lines, ask us first.
What is in scope
- The Software, in every form we publish it — installers, portable builds and store packages alike.
- oakchet.com, including the purchase and License delivery endpoints.
What is not
- Anything a user can already do on their own machine. The Software reads the user's own files by design, and runs with that user's own permissions.
- Reports from automated scanners with no demonstrated consequence. Tell us what an attacker could actually achieve.
- Our service providers' own infrastructure — Stripe, Cloudflare, Microsoft and Resend each run their own programs, and a flaw in theirs should go to them. If it is unclear whose it is, send it to us and we will work it out.
- Missing hardening that is not exploitable. We will read it, and we may well fix it, but it is not a vulnerability report.
Where this is published
The machine-readable version of this is at https://oakchet.com/.well-known/security.txt, per RFC 9116.
Contact
OakChet LLC 7345 164th Ave NE, Ste 145-196 Redmond, WA 98052 United States
support@oakchet.com