What Iris accesses, only after you sign in and approve it. You sign in on Google’s or Microsoft’s own page, so Iris never sees your password. With a Google account, Iris asks for: your name and email address, to identify your account; your Gmail messages and labels, to show your inbox and to let you read, send, reply, archive, trash, star, label, mark read or unread, and snooze; your Google Calendar events, to show your calendar and to let you create, edit, delete and answer invitations, requested only when you open Calendar; and a hidden app folder in your Google Drive (Google calls it “app data”). With a Microsoft account (Outlook.com, Hotmail or Microsoft 365), Iris asks for the equivalent: read, organise and send your mail, your calendar, and Iris’s own app folder in your OneDrive. In either Drive, Iris can see only its own app folder and no other file.
What goes in your Drive app folder. One locked backup of your encryption keys, so a new device of yours can restore them, and the files you keep in Iris Vault. Both are encrypted on your device before they are uploaded, with keys only you hold, so neither Google, Microsoft nor FluidPrism can open them.
What passes through our servers. Iris’s servers sync mail with your provider and relay chat and calls. Mail that Iris end-to-end encrypts is sealed in your browser before it leaves, and stays unreadable to our servers and to Cloudflare, which carries traffic to iris.fluidprism.com. Mail that isn’t end-to-end encrypted, such as mail to people not on Iris, is handled in readable form while it is built and handed to Google or Microsoft, and is not stored. For every message, the sender, recipients, time and subject remain visible to our servers and your provider. The security model sets out the exact conditions.
Chat, calls and files. Chat messages are encrypted on your device before they leave it. Our servers only ever hold them as ciphertext, which we cannot read, to deliver them to your contacts and your other devices. Calls are encrypted end to end between the people in them: one-to-one calls connect directly between devices where possible, and group calls run through a media server that forwards audio and video it cannot decode. If you turn on IP protection, calls go through a relay so the other person doesn’t see your IP address. Files you send are encrypted on your device first; where possible they travel directly between devices, and otherwise pass through the relay as ciphertext until delivered or until the expiry you choose. The key that opens a shared file travels in the part of the link after the # sign, which is never sent to a server.
What Iris stores. Your sign-in tokens, encrypted at rest on our server, so you stay signed in. Your public keys and the addresses they belong to, so the people you write to can encrypt to you and check it’s really you. Small records needed for features: snooze and scheduled-send times, draft identifiers, which accounts and devices are connected, locked key-backup metadata, and anonymous usage counts that contain no message text and no third-party addresses. No message content: your mail is cached in your own browser, and your calendar is shown in your browser without being stored on our servers. Sign-in sessions last at most 30 days and end after 7 days of not using Iris.
On your devices. Iris keeps your mail cache, settings and encryption keys in your browser’s storage on each device, with keys unlocked by your passkey. Linking a new device passes your keys to it encrypted end to end, through the code you scan. The leak check that warns about card numbers and IDs runs entirely on your device and sends nothing anywhere.
People you invite. Invitations are sent from your own mailbox. The people you invite can join Iris free; their data is handled exactly as described here once they sign up.
How we use it. Only to provide the Iris features described above. We do not sell account data, use it for advertising, or transfer it to others except to provide the service, to keep it secure, or when the law requires it. No person at FluidPrism reads your mail unless you ask us to for support, or for security or legal reasons. We do not use Gmail, Outlook or any other account data to train artificial intelligence or machine learning models.
Google API Services User Data Policy. Iris’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Service providers. Google and Microsoft, as your email providers; Cloudflare, which carries and protects traffic to iris.fluidprism.com; and our hosting providers. Each processes data only to deliver the service.
Your choices. Disconnect an account in Iris under Settings, Connected accounts, or remove Iris’s access in your Google Account (Security, Third-party access) or your Microsoft account (Privacy, Apps and services). Delete your Iris data in Settings, Your data, “Delete my Iris data”: it disconnects your accounts, revokes Iris’s access at Google and Microsoft, and deletes your key-backup records, usage records, passkeys, notices and sessions immediately; your mail stays with your provider. Delete the cloud key backup in Settings, Security & keys, and Vault files from Iris Vault. For anything else, email [email protected].