Security
Safe by design: only you can open what's sent to you
Inlook is built around one rule: a message is visible only to the people it was sent to, and only after Microsoft confirms they own that address. Here's how that works.
Your Microsoft sign-in is the only key
Inlook never sees or stores your password. Microsoft signs you in, then tells Inlook who you are.
Inlook recognises you by the permanent IDs Microsoft gives your organisation and your account. A changed display name or edited profile field can't impersonate you.
Addresses are verified, not claimed
For a work or school account, an address counts only if its domain is verified by the same organisation you signed in to. Someone can't use their own company account to claim an address at yours.
For a personal Microsoft account, Inlook accepts Microsoft's own consumer addresses (such as outlook.com), and addresses at domains no organisation has claimed. A personal account can't claim a company address.
If Inlook can't confirm an address, it's shown to you as unverified and unlocks nothing.
Each message opens only for its recipients
Who can see a message is decided message by message: the sender, and the people in its To, Cc and Bcc.
Adding someone to a thread later doesn't reveal earlier messages that weren't sent to them.
Bcc stays private
Only the sender sees the full Bcc list. A Bcc'd person sees the message and that they were Bcc'd, and no other Bcc recipients.
Reply all goes to the sender, To and Cc, never to Bcc recipients.
Held messages are locked until the owner arrives
When you write to someone who hasn't joined, the message is held against their address. Nobody can read it until the verified owner of that address signs in.
Minimal permissions
Signing in asks Microsoft only for your name and email address (the standard openid, profile and email permissions).
Inlook doesn't read your mailbox, contacts or calendar. The optional copy-back-to-Outlook feature will ask for mailbox permission separately, only when you switch it on.
Encrypted in transit and at rest
All traffic uses HTTPS, and messages are stored in an encrypted Postgres database. Sessions are signed and encrypted cookies.
Inlook is not end-to-end encrypted: its servers process message content to deliver it.
Under your organisation's control
Inlook is a standard multi-tenant Microsoft Entra application. Your IT admin can approve it for everyone, limit who can use it, or block it, from the Entra admin center.
Found a security issue? Email security@getinlook.com.