Privacy policy
Effective
The showcase
The demo uses fictional drafts. Replacement text and sample edits stay in browser memory. The showcase code adds no cookies or analytics. Vercel hosts the site and may process request information such as IP address and browser details. Vercel privacy notice
If you connect Buffer
The separate Patchwork app requests account:read, posts:read and posts:write through Buffer OAuth. The app reads account, organization, channel and eligible draft details so you can select drafts and review edits. It sends approved draft edits to Buffer when you apply them. Buffer privacy policy
The app uses an HTTP-only session cookie and stores the Buffer access token encrypted on the server. A connected session lasts up to one hour. The database holds draft copies, linked phrases, reviews and receipts. A campaign expires seven days after its last saved change. The app clears expired records as workspaces are opened.
The public Buffer workbench uses Vercel for hosting and Neon PostgreSQL for database storage. Vercel logs may include request metadata such as the browser and request URL, including the one-use authorization code returned by Buffer. Deleted records can remain in database restore history until that history expires. Local installations use SQLite. Vercel privacy notice · Neon data storage
Remove campaign data
Use Clear campaign to remove draft copies, links, reviews and receipts from Patchwork. Disconnect ends the session and deletes its stored token. You can revoke Patchwork’s access in Buffer. If a write has an unknown outcome, Patchwork retains the organization, post and operation identifiers to prevent a duplicate edit. Those identifiers have no automatic expiry.
Questions
For questions that contain no private information, use the public issue tracker. Arrange a verified private channel with the maintainer before sharing credentials, draft text or other private details. Security reporting guidance