Privacy Policy
Last updated: October 22, 2026
Hwip is run by Hyungtak Jin ("I", "me"). This policy says what the Hwip apps, the hwip CLI and the Hwip server collect, why, and what you can do about it. Contact: support@hwip.app.
The short version
- The contents of your notifications, questions, answers, diffs, terminal output and session history are encrypted on your devices before they are sent, and the server stores and forwards ciphertext. Some messages are not encrypted, among them channel posts and the status notifications the server writes itself, and the encryption does not fully protect you from a server that actively lies about your device list. What the server sees lists exactly what is and isn't covered.
- I collect what is needed to run the service: your account, your devices, and routing data about your sessions.
- There is no advertising, no analytics SDK and no sale of data.
What is collected
Account. When you sign in with Google or Apple, the server receives and stores your name, your email address and, if you set one, a profile picture. With Apple you can choose to hide your email, in which case the server stores no email for you.
Devices. For each phone or computer you connect: an id derived from a hash of a hardware identifier, the device type and model, the nickname you give it, the app version, its push notification token, its public encryption key, whether it is online and when it was last seen, and, for transfers over your local network, its private network address.
Sessions. For each agent session your computer reports: the session name, the name of the project directory (not its path), its label and title, the agent's session id, its state and when it was last active. Aliases and folders you assign in the app are stored too.
Content. Notifications, questions, answers, files, question context, session history and live session data are stored or relayed as ciphertext that only your devices can open. Two kinds of content are not encrypted: posts to a channel, and the short status notifications the server writes from your session list (they contain project and session names).
Usage counters. How many pushes and questions your account has sent in the current day and month, to enforce the limits of your plan.
Purchases. Hwip has no paid plan yet, so the server stores no purchase data. If one is added, this policy will say what it stores before anyone can subscribe.
IP address. Your IP address is not stored on your account or devices. It is used as a short-lived counter key to rate-limit sign-in requests, and it can appear in a log line when a request is rejected by that limit.
What is not collected. No contacts, no location, no advertising identifier, no analytics events, no crash reports. The server never receives your private keys, the full path of your project directories, or the arguments and output of the tools your agent runs.
How it is used
To deliver your messages to your devices, show you your sessions, enforce plan limits, prevent abuse and keep the service running. Nothing is used for advertising or profiling, and nothing is sold.
Who else receives data
| Who | What | Why |
|---|---|---|
| Amazon Web Services (Seoul region) | Everything the server stores | Hosting: database, file storage, relay, sign-in |
| Google (Firebase Cloud Messaging) | Push token and the notification payload | Delivering notifications, on iPhone and Android |
| Apple (Apple Push Notification service) | Push token and the notification payload | Delivering notifications on Apple devices |
| Google or Apple, as your sign-in provider | That you signed in to Hwip | Sign-in |
| A webhook URL you configure | What you set the webhook to send | Only if you set one up |
For an encrypted push, the notification payload holds a fixed title and body, the push id, its type and a hash that names your account. For the two unencrypted kinds it holds the text.
Your data is stored in South Korea. If you are elsewhere, using Hwip means your data is transferred there.
I would disclose data if the law required it. Because of the encryption, what could be disclosed is what this policy lists as collected, not the contents of your messages.
How long it is kept
| What | Kept for |
|---|---|
| Pushes, questions, channel posts | 30 days |
| Files and attachments | 30 days |
| Session history (encrypted) | 365 days |
| Server logs | 1 month |
| A device you no longer use | Removed after 30 days unseen, the next time you register a device |
| Account, devices and session list | Until you delete your account |
Expiry is handled by the database and can run some hours late. The production database keeps point-in-time recovery data for 35 days.
Your choices
- Delete your account in the app: Settings → Profile → Delete account. This deletes your files, sessions, session history, devices, the channels you own and your sign-in record. Copies of channel posts already delivered to other subscribers remain until they expire (30 days), and logs and database recovery data age out on the schedule above.
- Turn off session history upload:
hwip listener --no-turn-history, or"turnHistory": falsein~/.hwip/config.json. - Turn off question context (the diff and terminal lines attached to a question):
hwip ask-context offin a project, orhwip ask-context off --global. - Remove a device in the app.
- Ask for a copy of your data, or a correction: email me. There is no self-service export. Most of what is stored is ciphertext that only your own devices can open.
Depending on where you live you may have further rights over your personal data, such as access, correction, deletion and objection. Email me to exercise them.
Children
Hwip is a developer tool and is not directed at children. Do not use it if you are under 14.
Changes
If this policy changes in a way that matters, the date above changes and the change is announced on this page before it takes effect.
Contact
Hyungtak Jin · support@hwip.app