Privacy Policy

ClipB is built around these privacy principles:

• Clipboard history is stored locally on your device.
• ClipB does not require an account.
• ClipB does not upload your clipboard history to a server.
• ClipB does not sell, rent, or share clipboard data.
• ClipB does not include cloud sync by default.
• ClipB does not include advertising.
• Users can delete clips, clear history, and export their own data.

This policy covers:

• The ClipB desktop application
• The ClipB landing page or project website
• User-controlled exports such as JSON backups and .clipb archives

The desktop app is local-first. The landing page may be hosted by a third-party hosting provider, and external links such as GitHub Releases may be handled by those platforms under their own privacy policies.

ClipB may store the following data locally on your device:

• Copied text
• Copied links
• Copied code snippets
• Copied image data and screenshots
• Copied image files
• Copied file paths
• Optional local backups of copied files
• Clip metadata, such as creation time and update time
• Pinned status
• Favorite status
• Notes added by the user
• Tags added by the user
• Clip category information
• App settings
• Ignored app names
• Privacy and filtering preferences

ClipB stores this data in a local SQLite database. Images and backed-up files may be stored as local asset files inside the app data folder on your device.

The ClipB desktop app does not collect or transmit:

• Account information
• Payment information
• Location data
• Advertising identifiers
• Browsing history
• Usage analytics
• Crash reports
• Telemetry
• Clipboard history on a remote server

ClipB does not sell, rent, or share clipboard data with advertisers, analytics providers, or data brokers.

When clipboard watching is enabled, ClipB watches the system clipboard for supported copied content.

Supported content may include:

• Text
• Links
• Code snippets
• Images
• Screenshots
• Copied image files
• Copied file paths
• Optional backed-up file clips

You can pause clipboard watching, enable private mode, delete individual clips, clear all clips, and configure automatic retention settings.

ClipB supports rich clipboard content. Images and screenshots may be stored as local asset files. Copied file paths may be stored as path-only clips. If copied file backup is enabled, ClipB may copy supported files into its local assets folder.

Path-only file clips do not include a copy of the original file. If the original file is moved or deleted, the path-only clip may no longer point to an existing file.

Backed-up file clips store a local copy of the file inside ClipB’s app data folder. Folders are saved as paths only.

ClipB supports user-controlled export and import.

ClipB may export data as:

• JSON backup files for simple text history
• .clipb archive files for rich clipboard history, including metadata, tags, image assets, and backed-up file assets

Exported files are created only when the user chooses to export them. Once exported, the user is responsible for where those files are stored, backed up, or shared.

Imported .clipb archives are processed locally.

ClipB includes local privacy filters that can help reduce accidental saving of sensitive clipboard content.

These may include:

• Ignoring likely passwords
• Ignoring likely API keys and tokens
• Ignoring sensitive-looking clips
• Blocking clips copied from ignored apps
• Minimum clip length settings
• Maximum clip length settings
• Private mode
• Temporary pause timer

These filters run locally on your device before supported clipboard content is saved.

Privacy filters are helpful, but they are not a guarantee that all sensitive content will be detected. Users should still be careful when copying passwords, private keys, bank details, confidential files, or other sensitive information.

ClipB can store a user-defined list of ignored apps. When active app detection is available, ClipB can avoid saving clips copied from apps in the ignored apps list.

This feature is intended to help users avoid saving sensitive data from password managers, private work tools, browsers, or other apps they choose.

Ignored app names are stored locally.

The ClipB landing page is used to provide information, screenshots, documentation, and download links.

The website itself does not need an account and should not request clipboard data.

If the website is hosted on a third-party platform, that platform may process basic technical information such as IP address, browser type, device information, request logs, or security logs as part of normal hosting operations.

If users download ClipB from GitHub Releases or visit external links, those platforms may process data under their own privacy policies.

ClipB uses locally stored data only to provide clipboard manager features, such as:

• Showing clipboard history
• Searching clips
• Filtering clips
• Restoring copied content to the clipboard
• Displaying image and file previews
• Managing tags, notes, favorites, and pinned clips
• Exporting and importing user-controlled backups
• Applying local privacy settings

ClipB does not use clipboard data for advertising, profiling, or third-party analytics.

The ClipB desktop app does not send clipboard data to the developer or to third-party services.

ClipB does not share clipboard history with advertisers, analytics providers, or data brokers.

If a user manually exports a JSON or .clipb backup and shares that file elsewhere, that action is controlled by the user.

Users can delete data in several ways:

• Delete individual clips
• Clear all clips from settings
• Configure automatic deletion after a selected period
• Protect pinned clips from automatic deletion
• Delete exported backup files manually from their device
• Uninstall the app and remove its local app data folder

When clips with local asset files are deleted, ClipB attempts to remove the associated local asset files as well.

ClipB stores clipboard history locally on the user’s device. Users should be aware that clipboard history can contain sensitive information.

ClipB provides privacy controls to reduce accidental saving of sensitive content, but users should still be careful with passwords, private keys, API tokens, bank details, confidential files, and other sensitive information.

Device-level security remains important. Users should protect their device with operating system passwords, disk encryption, and appropriate access controls.

ClipB does not currently include cloud sync.

If cloud sync, accounts, payments, hosted backups, or other online services are added in the future, this Privacy Policy should be updated before those features are released.

The ClipB desktop app does not use third-party analytics, advertising networks, or cloud storage by default.

The project may use third-party platforms for hosting, downloads, source code, or documentation. For example, GitHub may be used for source code, releases, issues, and downloads. Those services are governed by their own privacy policies.

ClipB is a general-purpose desktop utility. It is not specifically directed to children.

ClipB is open-source software. Users can inspect the source code to understand how clipboard data is handled.

This Privacy Policy may be updated as ClipB changes. Important privacy-related changes should be documented clearly in release notes or project documentation.

For questions about ClipB privacy, open an issue on the project repository or contact the project maintainer.

GitHub: https://github.com/farukumarx64/clipb

Email: f.umaridris.mail@gmail.com