User and operator help
These guides explain the product behavior, recovery boundaries, and privacy-safe troubleshooting information support can use.
A standard identity is created on your device. Write down the six recovery words in order and keep them offline. They restore identity access, contacts, and account relationships that have synchronized. They do not recreate messages deleted from every authorized device and backup.
Open New conversation to show an invitation code or QR code. The other person scans or pastes it once. QEYET creates the conversation and stores the contact relationship locally. A contact can be assigned a private local name or note without changing the other person's identity.
Press Enter to send from a desktop browser and use the send control on touch devices. Replies, reactions, edits, deletion, typing state, presence, drafts, folders, and contact notes are available from the conversation interface.
The owner can invite members, transfer ownership, add administrators, approve joins, set slow mode, assign member tags, and temporarily restrict posting. Group messages are encrypted separately for each authorized recipient route.
Attach a file without adding message text. Direct files transfer only while sender and recipient endpoints can connect. The sender shows queued, transferring, received, and completed states, and an interrupted transfer can resume. Offline file bytes are not uploaded to the message-envelope queue.
On the existing device, open Settings, then Link another device. Scan the QR code from the new authorized device. Encrypted state synchronizes as devices reconnect. Device lists and revocation controls remain available from Settings.
Remove a lost device as soon as possible. Revocation blocks future synchronization but cannot erase information already visible on an unlocked device.
Enable notifications in Settings and approve the browser or operating-system prompt. You can independently control messages, calls, files, preview text, sound, and quiet hours. Android native clients provide the strongest locked-screen delivery. iOS browser behavior remains subject to Safari and installed-web-app limitations.
Open a conversation and choose the phone or camera control. The recipient receives an incoming-call prompt when push and network routes are available. Calls prefer direct WebRTC, use TURN for restrictive networks, and use a self-hosted SFU for larger meetings.
Create an @qeyet.com address from the Mail start screen. Native QEYET recipients use encrypted device delivery. Outside addresses use Internet SMTP compatibility. The message route label states which path is active.
Create custom folders from the folder menu. On mobile, swipe a message to archive or reveal move actions. Sent mail returns to the inbox after successful composition unless you explicitly open another folder.
Create an event from the Calendar tab, choose a time zone, add guests, set reminders, and leave the meeting option enabled to include a QEYET room. Google and Outlook can be linked through short-lived OAuth sessions. Yahoo and generic providers can use private iCalendar or standards-based links.
Guests open the personalized URL, enter their display name, verify the invited email when required, and wait for admission. In the meeting, use the top panel controls for participants, chat, and the Meeting Capsule. Camera background blur is selected from device settings.
Shared notes, decisions, actions, chat, and attendance synchronize with the calendar event. Personal notes remain private to the author's authorized devices.
Install the QEYET bridge on the same computer that runs Hermes, then pair the one-time QR code in Settings. After the connection is active, New conversation shows Hermes session controls. Separate folders can hold separate agent sessions and workspace context.
Tenant owners create enrollment codes, assign roles, manage directory visibility, establish Spaces, review privacy-safe operational metadata, and revoke organizational access. Admin authority does not provide conversation keys or decrypt user vaults.
An administrator can reissue organizational access after identity verification. Old message history returns only from an authorized device or encrypted backup that still holds it.
Support can use the QEYET version, browser and operating system, network-route state, opaque packet identifier, queue age, and a screenshot you choose to provide. Never send recovery words, private keys, a decrypted vault, or private message content.
Check service status before reporting a routing or gateway problem.
Delete for me changes only the current device. Delete for everyone sends a signed deletion event to authorized peers and linked devices. The local kill control removes messages, call logs, cached media, and local application storage from the device. Contacts can be preserved when that option is selected.
A linked device that has not yet received a deletion event may retain its prior copy. Release 44 propagates deletion tombstones so the item is removed when that device next synchronizes.