Pastry collects nothing, sends nothing, and has no servers.
That is the whole policy. The rest of this page only explains what that means in practice, because "we collect nothing" is a claim worth being specific about.
What stays on your Mac
Pastry stores the text you copy so it can give it back to you. That history lives in a file on your Mac, in a directory only your user account can read. It is never transmitted anywhere, because Pastry has no network code of any kind — no analytics, no crash reporting, no update check, no account, no sync.
Clippings that an application marks as concealed — password fields, mostly — are skipped and never written down.
The contents of your clipboard never reach the system log. Pastry logs only sizes, source application names, and outcomes.
What Pastry asks macOS for
- AccessibilityTo paste into the application you were typing in, Pastry synthesises a ⌘V keystroke, which macOS gates behind Accessibility permission. You grant it once, and you can revoke it in System Settings at any time. Without it Pastry still works: the clipping goes onto your clipboard and you paste it yourself.
- Launch at loginRegistered through macOS's own login-item service, which you can turn off in System Settings or in Pastry's settings.
Deleting your data
Clear All in the menu empties the history and removes it from disk immediately. Deleting the app removes everything it kept. There is nothing held anywhere else, because there is nowhere else.
Changes and contact
If this ever changes, it changes in public: the policy lives in the repository with the rest of the source, and its history is the commit log. Questions go to GitHub issues.
Last updated 11 November 2026.