# Security FAQ

<details>

<summary>Can I export my data?</summary>

Yes, you can export your data by navigating to **Settings > Login & Security**.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-7618f940092b4f6eeaf434429b4218d030b41c14%2Ffaq-export-your-data-settings.png?alt=media" alt="Export your Missive data settings user interface" width="850"><figcaption></figcaption></figure></div>

Here's what you can expect from each export category:

* **Comments**: This contains all comments from all organization and private conversations that you have access to. Timestamps are included for each comment. It excludes any conversations that have been moved to the trash. Each organization's comments will be provided in a separate **.csv** file.
* **Contacts**: This includes all contacts from every contact book that you have access to. Each contact book's data will be provided in a separate **.csv** file.
* **Conversations**: This includes all data (such as messages (emails, SMS, etc.), comments, assignments, etc.) from all organization and private conversations that you have access to. Timestamps are included for each message. It includes conversations marked as spam, but excludes any conversations that have been moved to the trash. Each organization's conversation data will be provided in a separate **.json** file.
* **Email addresses**: This contains all the 'From', 'To', and 'Cc' fields in all emails you have access to, excluding those in the trash or marked as spam. All this data will be provided in a single **.csv** file.
* **Phone**: This includes all the 'From' and 'To' fields in all SMS messages you have access to, excluding those in the trash or marked as spam. All this data will be provided in a single **.csv** file.
* **Responses**: This contains all responses you have access to. There will be separate exports for each team, the entire organization (for responses shared organization-wide), and personal responses. All these exports will be in **.html** format and will include attachments separately.
* **Rules**: This includes all rules you have access to. There will be a separate **.csv** file for each organization and for your personal rules.

Once your export is ready, Missive will deliver it in a dedicated conversation in your inbox.

</details>

<details>

<summary>Can you read my emails?</summary>

Technically speaking, it would be false to claim we cannot read your emails. Missive imports your emails via IMAP like any email app does and stores them in a database. This includes text content and attachments. Storing this data in our own database is the technical foundation of a collaborative product like Missive. Thus, we naturally have access to the database that contains your emails in order to manage and maintain it in good shape for Missive to operate properly. This is the same situation as with your main email provider (Gmail, Office 365, etc).

That said, only a few of our engineers have access to the database in question. Even for these people, getting to your actual email content is not trivial. We built internal tools that allow our engineers to do their daily job (e.g. see what is going on in the system, the number of emails processed, etc.), but none of these tools display email contents. Needless to say, we are not in the business of scanning, sharing, or selling any of our users’ data. We never access a user’s data unless this user has specifically granted us permission and asked us to investigate a bug with their account, for instance.

You can read [our Privacy Policy here](https://missiveapp.com/privacy). We take the privacy and security of your data very seriously.

</details>

<details>

<summary>Do you support 2-factor Authentication (2FA)?</summary>

Yes, users connecting to Missive with an email and password can enable 2FA from their **Login & Security** settings.

For users connecting to Missive with Google, here's [how to enable 2FA](https://support.google.com/accounts/answer/185839).

</details>

<details>

<summary>How do I enable two-factor authentication (2FA)?</summary>

Enabling two-factor authentication (2FA) to your Missive account will add an extra layer of protection to your data.

For users connecting via OAuth, please read this tutorial for people who [sign in with Google](https://support.google.com/accounts/answer/185839) or this other for people who [sign in with Apple.](https://support.apple.com/en-ca/HT204915)

To activate 2FA on your regular Missive account, you will need to get an authentication app such as Authy or Google Authenticator.

**Once you have downloaded one of the apps, please follow these steps:**

1. Go to **Settings** > **Login & Security**.
2. Enter your account password
3. Click on Enable two-factor authentication
4. With the previously downloaded authentication app, scan the QR code
5. Enter the 6-code digit in Missive.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-06399e980a3213e4bd51f791a7a769c7dc716aeb%2Ffaq-2fa.png?alt=media" alt="Screenshot of Missive&#x27;s two-factor authentication QR code" width="1036"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Can I enforce 2FA for all users in my organization?</summary>

It's not possible to enforce 2FA on users in the Free, Starter, or Productive plans.

Organizations on the **Business plan** can set up SAML SSO (Single Sign-On), which requires all users to authenticate through your identity provider (Azure, Okta, Google, etc.). While SSO is not the same as 2FA, it achieves a similar goal by centralizing and enforcing authentication policy through your chosen provider.

See [SAML and SSO](https://missiveapp.com/docs/administration/saml-and-sso) for setup instructions.

</details>

<details>

<summary>What does 2FA mean next to my user name in my user's settings?</summary>

The 2FA badge displayed in the user list for organization admins shows who enabled 2-factor authentification.

</details>

<details>

<summary>How can I change my password?</summary>

If you are logged out of the app, click on the "Forget my password" link on the login page, then enter your login email on our password reset page. You will receive an email containing instructions to reset the password for your account.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-1a5272472d9c0aa4db0791fb1716e3f21e25e5e6%2Ffaq-forgot.png?alt=media" alt="Image showing where to reset your password" width="449"><figcaption></figcaption></figure></div>

If you are still logged in, go to **Settings** > **Login & Security** to change your password.

<br>

</details>

<details>

<summary>How to change from Google login to username/password?</summary>

Go to **Settings** > **Login & Security** and click **Set a password**.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-5bda0f9f0ac6f8de5f4a530c2bcf813dc8d80717%2Ffaq-change-google-login.png?alt=media" alt="Change from Google login to username/password"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Why do I need to confirm my password in the settings?</summary>

This is only if you need to update your login credentials such as your email, password or OAuth provider. You can update any other settings without entering your password.

That is meant as a security step to make sure no one but the owner of this account can change the login information.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-b9e76bdc020fe9175153188dd1f274bc134cc2fc%2Ffaq-confirm-password-in-settings.png?alt=media" alt="Image showing password confirmation"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Why I always need to sign in again?</summary>

If you use Missive infrequently on a given device, this is normal. Missive sessions expire after 2 weeks of inactivity and require you to log in again.

This is for security reasons and is not configurable.

</details>

<details>

<summary>Is there a limit on how many active sessions I can have?</summary>

Yes. Each user can have up to **10 concurrent active sessions** across all devices and browsers.

</details>

<details>

<summary>Do you offer a bounty program?</summary>

We do encourage responsible disclosure of security issues related to Missive. Read more about our [bounty program here](https://missiveapp.com/security/bounty).

</details>

<details>

<summary>What is your uptime/downtime track record? (SLA)</summary>

In **2020**, we achieved 99.95% uptime.

In **2021**, we achieved 99.92% uptime.

Here's a breakdown per quarter:

* **2021** Q1 - 100%
* **2021** Q2 - 99.98% (maintenance)
* **2021** Q3 - 100%
* **2021** Q4 - 99.68%

In **2022**, we achieved 99.96% uptime:

* **2022** Q1 - 99.92%
* **2022** Q2 - 99.96%
* **2022** Q3 - 99.95%
* **2022** Q4 - 99.99%

In **2023**, we achieved 99.97% uptime:

* **2023** Q1 - 99.95% (maintenance)
* **2023** Q2 - 99.95%
* **2023** Q3 - 99.99% (maintenance)
* **2023** Q4 - 99.999% (maintenance)
* All maintenances happened during US Eastern nighttime.

As a reference, see here what 99.95% uptime represents on various basis (monthly, quarterly, etc): <https://uptime.is/99.95>

</details>

<details>

<summary>What happens when a user is removed from an organization?</summary>

Removing a user from an organization involves several steps and can have different implications. Here's what you need to know:

**Accesses to shared conversations**

The removed user will **lose access to all shared conversations** (those with the colored organization flag on the left). This is a background process that can take from a few minutes to several hours to complete.

If shared conversations contain emails from the user's personal email account, these emails will be removed from the shared conversations but will remain available to the removed user in new private conversations.

**Before removing**

If the departing user had a personal email, a team inbox, a WhatsApp number, an SMS line, or a social page connected, take action first to avoid data loss. See [Removing a user](https://missiveapp.com/docs/administration/security/removing-a-user).

**Comments/Chat**

Removed user comments are kept in shared conversations for remaining users to see.

**Assigned conversations**

Missive will do everything needed to ensure that the removed user assigned conversations won’t fall into a crack:

* Conversations assigned to the user that are closed will remain closed but the user will be unassigned so that if a newer message comes in, the conversation will be moved back to the team inbox.
* Conversations assigned to the user that are still open will immediately be moved back to the team inbox upon removing the user.

Given that second point, something to consider is if you believe the user in question was not keeping their **Inbox** and **Tasks** view clean, meaning they did not archive / close conversations even when they were done handling it, you don’t want a large influx of their old assigned conversations to fill up your team inbox.

To avoid that, something you can do before removing users (or on a regular basis) is to check your organization **Tasks** view (located in the + Pin to sidebar menu if you never opened it) and close old tasks your coworkers did not close.

</details>

<details>

<summary>Can I get a list of all IP addresses used by Missive's servers?</summary>

The servers Missive uses to connect to IMAP servers are hosted on Amazon Web Services (AWS). There are multiple IP addresses active at once and these may change several times a day.

If you need a list of IP address ranges to whitelist on your server, you can use the following file provided by AWS:

<https://ip-ranges.amazonaws.com/ip-ranges.json>

Although this may change in the future, all our servers currently originate from the US East 1 (N. Virginia) region, so you can filter the file and select only the IP ranges with "region": "us-east-1".

Note that this file may change regularly; you must synchronize the whitelist on your IMAP server accordingly. You can read more on the [expected usage of this file](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html).

</details>

<details>

<summary>Are you having a service outage?</summary>

If we are experiencing issues with the service, we will post a message on our [status](https://status.missiveapp.com/) page.

</details>

<details>

<summary>How to install Missive if you don't have admin permissions on your computer?</summary>

For the auto-update to work for users without admin privilege, Missive needs to be downloaded and moved to the user’s personal Applications folders (eg. `/Users/frodo/Applications`) whereas most apps are normally installed in `/Applications`.

If Missive hasn’t already been installed, jump to step 2.

**1) From the admin account**, completely uninstall Missive and its related files. To do that, we recommend using [AppCleaner](http://freemacsoft.net/appcleaner).

<figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-5a466bdf5cfeda6f22783153cd1b20a0b55cd02e%2Fguides-non-admin-app-cleaner.png?alt=media" alt="Completely uninstall Missive and its related files"><figcaption></figcaption></figure>

**2) From the user account**, [download the latest Missive version](https://missiveapp.com/download) and open the `.dmg` file.

Do not move the app in the Applications shortcut provided. Instead, open another Finder window and go to the user's Home folder (<kbd>⌘</kbd> + <kbd>Shift</kbd> + <kbd>H</kbd>) and drag Missive into the Applications folder. That folder doesn't require admin rights. If you're prompted with an admin/password dialog, you're most likely not dragging the app in the right directory.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-8f91bc97c44fa0acdd6496a434adc0ab54df0cb7%2Fguides-non-admin-drag-missive.png?alt=media" alt="Move Missive to the non-admin user personal Applications"><figcaption></figcaption></figure></div>

**3)** Open Missive from there, pin in to your Dock and you’re ready to collaborate! 😎

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-b23e1e1beb4eda6df78209ae3adffda25d723c79%2Fguides-non-admin-docked-missive.png?alt=media" alt="Pin Missive to your Dock"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>How can a department with sensitive data (e.g. HR) have more privacy in Missive?</summary>

The best setup for a team that handles confidential information is to establish their own separate Missive organization. Conversations in Missive are scoped to the organization they belong to, so members of one organization cannot access conversations from another.

By giving a sensitive department its own organization, you ensure:

* Confidential emails and chat conversations are only visible to members of that organization
* There is no risk of accidentally sharing sensitive conversations with the broader company
* Each organization has its own settings, teams, and access controls

See [Organization settings](https://missiveapp.com/docs/administration/organization-settings) for more on how to configure a new organization.

</details>

<details>

<summary>Why is AVG detecting images as threats?</summary>

AVG routinely flags regular images as threats, even on images hosted by Gmail. You can fill up this [form](https://www.avg.com/en-ca/false-positive-file-form) to help improve their algorithm.

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2Fgit-blob-1253bf4c0ada49b130c8da43b994d2baa5d1491a%2Ffaq-avg.png?alt=media" alt="" width="623"><figcaption></figcaption></figure></div>

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://missiveapp.com/docs/administration/security/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
