The service, the app, and these pages
Privacy.
Effective September 23, 2026
Message contents are end-to-end encrypted. Delivery still needs account and routing information. Here is what that means in ISYEET.
Your text stays between devices.
The app and command-line client encrypt messages using Signal’s official libsignal before sending them. The relay receives encrypted envelopes, not your text or your private messaging keys. Private keys, verified contacts, encryption sessions and recent message history are held on your device. Groups use a separate encrypted copy for each recipient.
ISYEET accepts printable ASCII messages only. ASCII faces are ordinary text. There are no attachments, link previews, media uploads or formatted messages.
What the service processes.
- Account and sign-in
- Your canonical email address, a Google account identifier, account creation information and public encryption keys remain with your account until you delete it. Google verifies your sign-in; ISYEET does not receive your Google password or request access to Gmail messages, files or your Google contacts. Session tokens authorize the app; the relay stores token hashes with an expiry of up to seven days.
- Message delivery
- Encrypted envelopes, message identifiers, sender and recipient account identifiers, ciphertext hashes, and delivery and expiry timestamps. The service can observe who sends to whom and when. It also stores the contacts you permit to send to you. Group content and the group roster are inside encrypted messages; delivery patterns can still reveal relationships.
- Optional notifications
- An Apple push token and a small pending notification record. Notifications contain a generic “New message” alert, not message text or a sender’s name. Apple processes push delivery information. Push delivery depends on device settings and service availability.
- Traffic preferences
- Your notification or cover-mode preference. Cover mode and remote alerts are mutually exclusive. Equal-size envelopes and optional cover packets reduce some traffic clues; they do not hide all timing, network addresses or relationships. The iOS sending schedule runs only while the app is active.
- Network and support information
- Network addresses, request timing and security-related rate limits are processed to operate and protect the service. If you contact support, we receive the information you choose to send. Ordinary support email is separate from ISYEET’s encrypted messaging and does not automatically expire after seven days. You can request deletion of that correspondence through support.
Seven days, with clear limits.
Each message has a fixed expiry seven days after the sending client encrypts it. Reading or retrying a message does not extend that deadline. The relay stops offering expired messages and clears encrypted bodies after recipient acknowledgment or expiry, whichever happens first. Delivery and duplicate-prevention metadata can remain until the same deadline. Maintenance removes expired live database rows in batches.
The app keeps at most 200 unexpired history entries. It removes expired history before displaying it again. An app that is closed, or a device whose protected storage is locked, cannot erase data at an exact moment. A stopped command-line client cleans up when it next runs. Small local duplicate-prevention records can remain for seven days after first receipt without message text.
Recipients can keep independent copies or screenshots. Device backups, filesystem snapshots and information already copied outside the app are not erased by a message timer or by deleting your account.
Delete your account or replace a lost device.
In an app version with account controls, open Settings and choose Delete account. Confirm the warning and sign in to Google again. After the service confirms deletion, the app clears its saved account, private keys and local messages. The relay removes your live account identity, public keys, sessions, contact permissions, queued messages to or from you, notification registration and traffic preferences. A small, hashed operation receipt expires after 24 hours and is removed by maintenance, so a connection failure can be retried safely without deleting a new registration. Provider recovery history remains subject to the limit above.
Deleting your account does not delete your Google account, erase a recipient’s device or remotely wipe a lost device. If you later sign up again, you create new messaging keys.
For a lost device, secure your Google account, then sign in on a new phone and explicitly re-enroll. This replaces your messaging identity and revokes existing service sessions; it does not recover old messages or private keys. Someone who still controls your Google account can sign in again and request another re-enrollment. Contacts must remove the old contact, add you again and independently verify the new fingerprint. A key-change warning is a reason to verify your identity through another trusted channel.
For help with account access or a privacy request, use the contact on our support page.
Providers and public websites.
Cloudflare hosts the relay and the primary website. GitHub hosts the alternate website at isyeet.github.io. Google processes sign-in, and Apple provides app distribution and optional push delivery. These providers process information under their own terms and privacy policies and may process it in different countries.
Provider privacy information: Cloudflare, GitHub, Google, and Apple.
We do not add advertising, analytics scripts, tracking cookies or contact forms to these static websites. The sites do not sign you in to the messaging service. Hosting providers still process ordinary connection and request information. The relay deployment disables application request logging; that does not remove the providers’ own operational records.
Questions and changes.
You can ask about the personal information associated with your account, request correction or deletion, and raise a privacy concern through support. We may need to verify account ownership. Your applicable privacy rights depend on where you live.
ISYEET is in development. We will update this page when its data practices change and show the effective date here. We will bring material changes to users’ attention before they take effect where required.