How your account, keys and data are protected
Sign-in, passwords shown once, keys that reach one thing, encrypted connections, and what writing help can and cannot see.
Updated 1 min read
Your sign-in
- Accounts are opened only for confirmed email addresses.
- Turn on two-step verification from Settings, Your sign-in.
- The console refuses changes that do not come from the console itself.
Passwords and keys
- Mailbox passwords are generated for you and shown once. We keep no copy; a lost one is replaced.
- API keys start
rmk_and are shown once. A sending key can only send transactional mail; an agent key reaches only its agent's mailbox. - Revoke any key at once from the page where it was made.
- A Cloudflare token for automatic DNS is kept encrypted, used only for its domain, and destroyed when you disconnect.
- Passwords for mail you move in are held only while the copy runs.
Connections
Mail apps connect over TLS on ports 993 and 587, and mailboxes require encrypted connections for mail in and out. Your domain's mail is signed with DKIM keys for your own domain.
Writing help and AI
- Writing help drafts and rewrites; it never sends, approves, schedules or changes settings.
- No contact details are ever sent to it. Your brief, brand and the page or notes you give it are read as material, never as instructions.
- Every proposal is recorded under Versions, with which model wrote it and what became of it. Proposal text is kept for 90 days for comparison.
- Agent drafts and automatic replies are the exception: they send the incoming email to the model to write the answer. They run only if you choose them for an agent.
Who can see what
Roles decide what each person can change, and every change is checked again by Rykon Mail itself, not only by the screen. See Roles and inviting your team.