The short version: Cubby stores clipboard history locally on your Windows PC. The desktop app does not include analytics, advertising, cloud sync, or network-backed AI features. This website collects limited, privacy-preserving visit counts.
What Cubby stores
To provide clipboard history, Cubby records supported content you copy while it is running. That currently includes plain text, HTML, RTF, images, and file lists, along with useful context such as the source application, content type, timestamps, and whether an item is pinned.
History is stored in Cubby’s local application-data directory. Clipboard payloads are kept in a local SQLite database, and image data is kept in local application files.
What Cubby does not collect
- No Cubby account or sign-in is required.
- No clipboard content is sent to Cubby or SouthForge AI servers.
- The Cubby desktop app sends no product analytics or usage telemetry.
- No advertising identifiers are created.
- No AI service receives or processes your clipboard content.
- No cloud clipboard sync is included.
Network access
The desktop app uses network access to check GitHub periodically for signed updates and to open links you request. Update checks do not include clipboard content or product-usage events.
Website analytics
This website records page views and clicks on download and GitHub links so we can understand whether the site is useful. It does not load a third-party analytics script or set an analytics cookie. A first-party Cloudflare Worker hashes the request IP address, browser user agent, a private salt, and a 30-day rotation period before sending the event to PostHog. Raw IP addresses, browser user agents, and clipboard content are not included in the event sent to PostHog.
Sensitive information
Clipboard history can contain passwords, access tokens, personal messages, customer information, and other sensitive content. Cubby provides ignored-application controls so selected apps can be excluded from capture, but no exclusion system should be treated as a substitute for careful handling of secrets.
Local encryption: Cubby encrypts stored clipboard payloads and image data with AES-256-GCM. Its encryption key is protected by Windows for the current user. This protects copied content in Cubby’s application-data files at rest, but it cannot protect content from software running as you while Cubby is able to unlock your history.
Your controls
You can delete individual clips, clear unpinned history while preserving pinned clips, or use the confirmed clear-everything action. Uninstalling Cubby may not automatically remove every application-data file; those files can be removed manually if you want to erase all remaining local history.
Third-party services
The Cubby website is served by Cloudflare, uses PostHog for the limited aggregate website metrics described above, and links to GitHub for source code, releases, and support. Those services process requests under their own privacy terms. The Cubby desktop app does not send clipboard content to any of them.
Changes to this policy
This policy will evolve as Cubby approaches a general release. Material changes will be reflected here and in the open-source repository.
Questions
For a privacy question or concern, open an issue on GitHub. Avoid including private clipboard content in a public issue.