Private by architecture.
The Vamp product website is a static, open-source project site. It does not provide user accounts, advertising profiles, a hosted remote-access relay, or a project-operated analytics dashboard. The site may be delivered by its hosting and network providers, which can process ordinary request information such as IP address, user agent, requested path, and time for security, reliability, and delivery. Visiting links to GitHub, Google Fonts, Tailscale, or other third-party resources makes a separate request governed by that provider’s privacy terms. This page stores a theme preference and a language preference in the browser’s localStorage (`vamp-theme`, `vamp-lang`). Effective date: 23 October 2026.
Vamp applications
Vamp applications are designed for direct connections over a trusted local network or a private Tailscale network. Pairing identities, trusted-peer records, session metadata, and terminal workspace state remain on the user’s machines. The project does not operate a central account database or relay that receives remote screen, input, clipboard, file, audio, or terminal content. Raw terminal bytes are not persisted to disk by the host’s session journal; only bounded in-memory reattachment data and semantic session events are used to support reconnects.
Permissions and user control
Vamp Sync uses Screen Recording only after the user grants permission in macOS System Settings. The Mac App Store edition is sandboxed and View Only: it does not request Accessibility permission, inject remote input, remotely unlock the Mac, launch or close other apps, resize windows, or run terminal commands. The separate website edition offers keyboard and pointer control, window resizing, and optional Remote Unlock after explicit Accessibility approval. New peers require visible approval after comparing their complete fingerprints, and trusted peers can be revoked later. Users choose which private network carries the connection, which devices are approved, and when sharing stops.
Reports and changes
Support messages and security reports contain the information the sender chooses to provide and are processed only to investigate and respond. Do not include credentials, pairing secrets, private keys, or unrelated personal information. Material privacy changes will be published in the public repository and reflected on this page. Questions about this notice can be sent through the project’s contact routes.
Retention and deletion
Vamp Control and Vamp Sync retain local preferences, saved hosts, pairing identities, and trusted-peer records across launches so that you can reconnect. Forgetting or revoking a peer prevents further trusted connections; a revoked record may remain in local app storage. Revoking trust does not erase the device’s own identity. The connection history displayed inside Control is bounded in memory and disappears when that app process ends. Separate macOS diagnostic and unified-log records may remain under the operating system’s own retention and diagnostic-sharing settings; a saved export is not removed by quitting the app. A diagnostic export, received file, or screenshot that you save remains wherever you chose to save it until you delete it. Compatible hosts may retain bounded semantic session metadata and journals for reconnects; raw terminal output is not written to those journals.
To stop sharing, disconnect and stop the host. To withdraw a device’s access, revoke or forget it on each relevant Mac. To remove local configuration, quit the app and remove its own data from your Mac’s Application Support directory or sandbox container using Finder. This also removes saved host and session records in that location. Identity data or compatibility credentials stored in Keychain may survive app removal and must be removed separately in Keychain Access if you want to reset them. Removing an identity requires pairing again. Do not remove other applications’ files or Keychain items. Contact the project if you need help identifying Vamp’s data. Files or records on another device, in a backup, or exported by you must be deleted at that location separately.
Voluntarily submitted support and security reports have no automatic expiry. Reports remain until you remove them where the service permits or a deletion request is processed, except for information that must be retained to meet a legal obligation or document a security fix. GitHub issues and comments may be public and remain visible after an issue is closed; use GitHub’s editing and deletion controls or ask the repository maintainer to remove identifying content. For private correspondence, request deletion through the same contact route you used to send it. The project does not receive your local screen, input, clipboard, file, audio, or terminal content unless you deliberately include it in a report, and cannot delete copies held independently by other people or service providers.