Detect sensitive content before it reaches the wrong destination.
ClipDove Enterprise
Central clipboard policy.
Clipboard content stays local.
Give people a fast, searchable Mac clipboard while IT and security control how API keys, credentials, payment data, IDs, screenshots and personal information move into apps, websites and AI tools.
Use targeted app, domain and AI rules instead of banning clipboard tools.
Measure protection events and device posture without viewing copied content.
Policy engine
Control what happens, where and when.
Start with a balanced policy, then tune response, scope and exceptions for your organisation.
Sensitive paste actions
Choose the response for detected content.
- Ask, redact, block or allow
- Apply to every destination or AI tools only
- Strict protection at copy time
- Permit controlled original-paste exceptions
- Restore temporarily hidden items
App and website rules
Protect risky destinations without slowing trusted work.
- Blocked and trusted applications
- Blocked and trusted domains
- Ignored apps never enter clipboard history
- Password-manager compatible controls
- Company-specific regex detectors
Detection coverage
Recognise common secrets and personal information locally.
- API keys, tokens and credentials
- Payment cards, IBANs and identity numbers
- Email addresses and phone numbers
- Names and company identifiers
- Text inside screenshots through local OCR
History governance
Set consistent boundaries for clipboard storage.
- Maximum history retention
- Maximum secret lifetime
- Enable or disable image history
- Control Clear History and Quit
- Launch at login and pause-capture policy
Privacy architecture
Visibility without surveillance.
Protection runs on the Mac. The management plane receives policy state, device posture and event outcomes—not the material people copy.
Stays on each MacClipboard textScreenshot pixelsFilenamesWindow titlesSearch queries
Optional management dataApp and policy versionProtection statusEvent countsmacOS and chipOptional device identity
Cloud reporting can be disabled. Hostname and username sharing are optional. Clipboard content is not required for central policy or posture reporting.
Operations
Fits the way Mac fleets are already run.
Deploy and enrol
- MDM-ready
.mobileconfig - Custom Settings
.plist - One-time enrolment tokens
- Manual or fleet-wide deployment
- Automatic application updates
Manage policy live
- Versioned policy on every Mac
- Heartbeat-based policy refresh
- Push selected controls fleet-wide
- Leave unticked settings user-controlled
- Separate portal for each company
Device posture
- Enrolled and active device counts
- Last check-in and installation date
- App version and protection status
- macOS, Apple chip and region
- Optional hostname and username
Audit and integrate
- Blocked, redacted and allowed counts
- Copy-redacted and cancelled outcomes
- Original-paste exception counts
- HTTPS webhook for SIEM ingestion
- Cloud reporting can be disabled
Management-plane safety
- Hashed tenant and device keys
- Encrypted DynamoDB and private S3
- Point-in-time recovery and versioning
- Per-device data erasure API
- Rate-limited regional API
Employee experience
- Fast searchable clipboard history
- Plain-language and type filters
- Keyboard-first quick paste
- Visible protection decisions
- Local search, classification and OCR
Clear answers
Enterprise FAQ
Does ClipDove upload employee clipboard content?
No. Clipboard text, screenshots, filenames, window titles and searches remain on the Mac. Optional reporting covers policy state, device posture and protection-event outcomes.
Can we deploy ClipDove through MDM?
Yes. ClipDove supports a managed .mobileconfig, Custom Settings .plist, enrolment tokens and fleet-wide policy.
Can policy target AI tools?
Yes. Controls can apply to all destinations or only AI applications and websites, with separate blocked and trusted app or domain rules.
Can events feed our SIEM?
Yes. Protection outcomes can be sent through an HTTPS webhook without sending the copied content itself.
What can administrators see?
Depending on configuration: enrolment and activity, policy and app version, protection status, macOS, chip, region, event counts and optional device identity.
Bring your policy
Protect the paste,
not just the perimeter.
Tell us about your Mac fleet, sensitive-data requirements and AI policy.