01
Scope
This Privacy Policy covers the Warpeer website and Warpeer application releases published by Warpeer contributors. It does not cover Warp, remote hosts, command-line tools, plugins, websites, or other services that you choose to use through Warpeer.
Warpeer is an independent pure-terminal fork of Warp and is not sponsored, endorsed, or published by Warp.
02
Privacy summary
Warpeer does not require an account. This website has no contact form, payment flow, behavioral analytics, advertising, marketing pixels, or fingerprinting. Warpeer does not sell personal information or share it for cross-context behavioral advertising.
Warpeer does not operate a backend for terminal content and does not send product telemetry, crash reports, or automatic update data. Terminal content stays on your Mac unless you choose a command, connection, plugin, link, or third-party service that sends it elsewhere.
03
Website data
The site stores a theme preference named warpeer-theme in your browser's local storage so your light or dark choice persists. Application code does not set a tracking cookie.
The static hosting and network delivery providers may process request metadata such as your IP address, requested URL, user agent, timestamp, and security signals to deliver the site, maintain reliability, prevent abuse, and investigate security incidents. Warpeer does not use that metadata to build advertising profiles.
04
Data on your device
Warpeer processes terminal output, commands, settings, layouts, session references, local logs, and related application state on your Mac. Warpeer does not upload this data to a Warpeer-operated service.
Private-tab passwords and optional recovery answers are represented by salted local verification records rather than being sent to Warpeer. Touch ID decisions are handled by macOS; Warpeer does not receive or store your biometric template. Private-tab locking reduces casual exposure inside Warpeer but does not replace macOS account security, FileVault, or careful credential handling.
05
Warpeer for iPhone
Warpeer for iPhone stores saved hosts, credentials, snippets, known-host fingerprints, connection logs and settings on your device. Passwords and private keys are kept in the iOS Keychain. Warpeer does not run an account service and the app contains no analytics, advertising or crash-reporting SDK.
When you connect to a server, Warpeer uploads a small helper to ~/.warpeer/remote in your home directory on that server over the same SSH connection. The helper lists tmux and Herdr sessions, detects coding agents, reads git status and reports resource metrics for the connection you opened, and returns that data to your iPhone. It is not sent to Warpeer.
Device permissions are requested only when you use the feature that needs them, and you can change them at any time in iOS Settings. The camera scans a device transfer code or captures an image you attach to terminal input. Photos you pick and images you attach are uploaded only to the server you are connected to, over that SSH connection. Dictation uses the microphone and Apple’s speech recognition, which may process audio on Apple’s servers under Apple’s privacy policy; the recognized text is placed in the terminal input for you to review before sending. Face ID unlock is handled by iOS, and Warpeer never receives biometric data. Local network access is used only to discover SSH services on your network.
Notifications are optional. If you enable them, your device push token and notification subscriptions are sent to the relay address you configure, and that relay delivers alerts through Apple Push Notification service. Device transfer moves your vault between your own devices after you scan a QR code on the new device.
Every feature is free during Early Access and the app does not contact a purchase service. If paid plans are introduced, purchases will be processed by Apple, and subscription status by RevenueCat, under their own privacy policies; this policy will be updated before that happens.
06
Network activity you initiate
A terminal is a network-capable tool. Commands, SSH sessions, package managers, command-line applications, local plugins, opened links, and remote services can transmit terminal content, credentials, files, device information, or other data at your direction.
Those destinations process data under their own terms and privacy policies. Review commands and destination policies before sending sensitive information. Warpeer contributors do not control a remote service merely because it can be reached from the terminal.
08
Retention and deletion
The browser theme preference remains until you clear site data or change it. Warpeer application settings, logs, credentials, and state remain on your device until you reset, remove, or delete them. Removing the application may not automatically remove every configuration or log file.
Infrastructure providers may retain request and security logs according to their own operational schedules and legal duties. Warpeer contributors do not maintain account profiles or a centralized terminal-history database.
09
Security
Warpeer keeps its own terminal data on your Mac, but no software or storage method is perfectly secure. Protect your macOS account, enable disk encryption, keep system software current, review plugins, and avoid placing secrets in screenshots, logs, feedback, or untrusted commands.
If you believe a Warpeer-controlled surface has a privacy or security issue, contact [email protected] without including live credentials or unnecessary private terminal output.
10
Your choices and rights
You can clear the website theme preference through your browser, remove local Warpeer data from your Mac, avoid optional plugins and remote services, and stop using the website or application.
Depending on where you live, you may have rights to know, access, correct, delete, restrict, or obtain a copy of personal information, object to certain processing, or complain to a data protection authority. Because Warpeer has no accounts or centralized user profile, the project may have no data that can be linked back to you. Requests can be sent to [email protected] and may require reasonable identity verification. You will not be discriminated against for exercising an applicable privacy right.
11
Children
Warpeer is a developer tool and is not directed to children. The project does not knowingly collect personal information from children through an account, advertising, or analytics system. If you believe a child has provided personal information to a Warpeer-controlled channel, contact [email protected].
12
International delivery
Static hosting and network providers may process request metadata in countries where they operate. Privacy protections can differ by location. Warpeer limits its own website processing and does not operate a centralized terminal-content service.
13
Changes to this policy
This policy may change when Warpeer features, hosting, distribution, or legal obligations change. Material revisions will be published with a new last-updated date. If Warpeer later adds accounts, hosted services, telemetry, crash reporting, payments, or behavioral analytics, this policy will be updated before those features are introduced.
14
Contact
Privacy questions and requests can be sent to [email protected]. Include only the information needed to understand the request, and do not send passwords, private keys, access tokens, or full terminal transcripts.