Found a security problem? Write to security@buttershot.app. Please do not post it publicly or in a problem report first. We will acknowledge your message, aim to do so within three business days, and keep you informed.
1. How ButterShot™ is protected
- Your screenshots stay on your Mac. The app does not upload them. The less we hold, the less there is to lose.
- Signed and notarized. Every release is signed with SnackSafe Inc.'s Apple Developer ID and notarized by Apple, so macOS can check that it came from us and has not been altered.
- Verified updates. Updates are downloaded over an encrypted connection and carry a digital signature that the app verifies before it installs anything. Each download on the releases page lists its SHA-256 checksum.
- One official source. ButterShot™ is distributed only from buttershot.app. A copy from anywhere else is not ours.
- Private storage, least access. Problem reports go into private storage that the public cannot read, and each part of our systems can reach only what it needs.
- Encryption in transit. The website, the update service, the report service and the contact service are served over TLS.
- No third-party code on the website. The site loads nothing from other companies.
No software or service is perfectly secure, and nothing on this page is a warranty. The Terms of Service govern.
2. What we ask of you
- Keep macOS and ButterShot™ up to date.
- Download ButterShot™ only from buttershot.app.
- Check a screenshot for secrets before you share it. Redaction reduces what a viewer can see; it is not a guarantee.
- Secure your Mac: your captures are as safe as the account they are stored in.
3. Reporting a vulnerability
Email security@buttershot.app with:
- what you found and where (the app version and build, or the address);
- the steps to reproduce it, and a proof of concept if you have one;
- what you think an attacker could do with it;
- how you would like to be credited, if at all.
Please do not include other people's personal information or secrets in your report. If you need to send something sensitive, say so and we will arrange a way.
3.1 What you can expect from us
- An acknowledgement, which we aim to send within three business days.
- An honest assessment, and updates as we investigate and fix.
- Credit in the release notes if you want it, once a fix is out.
- We do not currently run a paid bug-bounty programme, and reporting a vulnerability does not entitle you to payment.
3.2 Coordinated disclosure
Please give us a reasonable time to fix a problem before you tell anyone else about it: 90 days from your report, or until a fix is released, whichever comes first, unless we agree otherwise.
4. Good-faith research
We will not bring a legal claim against you, or ask law enforcement to investigate you, for security research on ButterShot™ that you carry out in good faith and that stays within all of the following:
- you test only the ButterShot™ app on your own Mac, and the services at buttershot.app;
- you access only your own data, and stop and report at once if you come across anyone else's;
- you do not degrade, interrupt or damage any service, and do not destroy, alter or retain any data;
- you do not use social engineering, phishing, physical intrusion, or attacks on our staff, our providers or other users;
- you do not use a finding for anything other than reporting it to us, and you keep it confidential as the coordinated-disclosure section asks;
- you comply with the law.
This is a statement of our own intentions. We cannot authorize research on systems that belong to others (for example our hosting provider or Apple), and we cannot bind any third party or any authority. If you are unsure whether something is within scope, ask first.
4.1 Out of scope
- Denial-of-service, flooding and volume-based testing.
- Automated scanning that generates significant traffic, and reports that are scanner output without a demonstrated impact.
- Spam, and abuse of the contact or report services.
- Issues that need physical access to an unlocked Mac, a compromised macOS account, or malware already running with the user's privileges.
- Missing security headers or best-practice settings without a demonstrated, exploitable impact.
- The behaviour of third-party apps and services that screenshots are pasted into.
5. Reporting abuse or a privacy concern
For content on our servers that should not be there, see the Acceptable Use Policy. For privacy questions, see the Privacy Policy.