---
title: "Privacy and Security"
canonical: "https://help.agiloft.com/space/HELP/43716814/Privacy+and+Security"
format: markdown
---
This article is designed to help answers questions customers may have about privacy/access/permissions when installing Agiloft Contract Assistant for Outlook and the Agiloft Contract Assistant for Word, which will hereby be referred to as Agiloft apps.

# What does the App capabilities section mean?

On the Agiloft Outlook app in [AppSource](https://appsource.microsoft.com/en-us/product/office/wa200003468?tab=overview), near the bottom of the page shows a message from Microsoft that states the following:

> ℹ️ **App capabilities**
> ℹ️ 
> ℹ️ - Can send data over the Internet
> ℹ️ - This app can read or modify the contents of any item in your mailbox, and create new items. It can access personal information information – such as the body, subject, sender, recipients, or attachments – in any message or calendar item. It may send this data to a third-party service.

> Macro (inline-media-image)

  
This warning comes from Microsoft's perspective as a facilitator of app implementation. The reference to third parties will only ever mean your own Agiloft KB.

Consider their mention of this add-in** **simply as an instance of the app that can be installed onto a user's computer. When this message says that the app can read or modify the contents of any item in your mailbox, it is referring to the mailbox of the user running the app. At no point will there ever be running instances of the app code that have access to more than a single user’s mailbox at a time, which must be properly configured before it can be accessed.

Microsoft doesn’t allow Office Apps to expand Windows permissions, and Agiloft backs that up by not allowing users to run API calls they do not have permissions for. Microsoft also heavily vets and audits the apps offered on their store, so our representation in [AppSource](https://appsource.microsoft.com/en-us/product/office/wa200003468?tab=overview) is a verification of proper security compliance.

# What permissions do the apps get?

Using the Outlook or Word apps in no way ever increases a user's permissions, either in the KB or in the Microsoft environment. 

A user can only interact with content they would also be able to interact with in Agiloft. Working in an app does not add any extra level of permissions to the user, it just provides a more convenient user interface to work in.

If you don't have permission to do something without the app, you still won't be able to do that thing with the app. If you attempt something you do not have permission for in Agiloft, both editing or viewing, you will receive an error message.

In Outlook, the app will only get Read & Write permissions to the mailbox of the user who launches the app, and inherits the permissions of that user.

The manifest file used for the Outlook app is hosted at [https://outlookaddin.agiloft.com/manifest.xml](https://outlookaddin.agiloft.com/manifest.xml). The snippet of the manifest file that controls permissions is: 

```
<Permissions>ReadWriteMailbox</Permissions>
```

  
The context that [Microsoft provides](https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/privacy-and-security) for <Permissions> assures that the app only gets Read & Write permission to the mailbox of the user who launches the app, not to all mailboxes within the organization. 

# How do the apps send data?

Both the Outlook app and the Word app use API calls to access mailbox items and contract documents, respectively. It also uses API calls to associate those emails and documents with KB records, as well as make other changes based on user actions that are performed in the apps.

The Outlook app uses MS Outlook APIs to interact with the currently open email. It then uses Agiloft REST APIs to associate those open emails with KB records, and make other KB changes based on user decisions related to the open email.

Similarly, the Word app uses MS Word APIs to interact with the currently open document. It then uses Agiloft REST APIs to associate those open documents with KB records, and make other KB changes based on user decisions related to the open document.

The API calls only send data to the user KB. If admins would like to confirm this, we recommend verifying this with a tool like [Fiddler](https://www.telerik.com/fiddler).

# How do the apps ingest data?

Both the Outlook and Word app contain mechanisms that ensure they only use data relevant to their tasks at hand.

Since the Outlook app requires the ability to send emails to the Agiloft KB, it requires the highest MS Outlook permission level, ReadWriteMailbox. While this technically means that the app has access to the entire mailbox of the individual user only, the app is programmed to only read mailbox items that are opened with the Outlook app specifically.The app will add it’s routing data in the headers or subject line of the appropriate mailbox item, and will check back there for it’s own routing data.

The Word app processes all the data available, such as text and OOXML metadata, in documents that are opened with the app only in order to match annotation data from the KB into that document text. The app doesn’t store data per se, instead, it uses data for local processes like AI extraction. Simply put, the Word app only has access to information in open Word documents, as well as the parts of your Agiloft KB it interacts with via HTTPS REST requests that are required to run relevant Word app-related workflows, such as the Clause Library, Clause Types, and Contracts tables.

Both apps have their code loaded from Agiloft servers. These servers are [wordaddin.agiloft.com](http://wordaddin.agiloft.com) and [outlookaddin.agiloft.com](http://outlookaddin.agiloft.com).

# How do the apps retain data, if any?

Both apps cache KB data securely and locally, but that is the extent of data retention. The Word app does not cache document data, and the Outlook app does not cache mailbox data. KB data is not purged, but can be manually cleared by clearing your local cache.

The Outlook app purges all metadata (subject, body, attachments, headers) of any open mailbox item associated with a Contract record at the end of every session, only retaining relevant KB data to help initiate connection. For example, only server URLs and KB names are cached.

The Word app purges all document data after every session, only retaining relevant KB data to help initiate connection and perform basic workflows. For example, the logical names of the Attachments table and its critical fields are cached.

# How do the apps authenticate?

Both apps use the same login structure, which begins by checking to see if a valid auth token exists. If yes, they use it to reauthenticate with the KB. 

If not, they launch the login dialog:

- If the user chooses username/password as the login, those credentials are encrypted and sent through an HTTPS REST request to the KB’s EWLogin API. A new token is issued upon credential acceptance and the app will use that token for all REST calls in the session.
- If the user chooses SSO in any form, the app redirects to the SSO provider, which is specified in the KB configuration. When SSO is used, the identity provider authenticates the user to Agiloft’s configured endpoint. Agiloft validates this assertion and creates an auth token.

All auth token management occurs in the KB server code; the apps only know how long these tokens are valid for. The Word app will automatically refresh the login auth token every few minutes to prevent unnecessary logouts.

# What infrastructure do the apps use?

For the Outlook app, a mailbox item is processed by the MS Office JavaScript API and sent to the Outlook app, which then uses inbound email to communicate the data to your KB.

For the Word app, an open docx file is processed by the MS Office JavaScript API and sent to the Word app, which then uses Agiloft REST APIs to communicate the data to your KB.

The REST API never makes calls to the app, but it does return KB data in response to HTTPS REST GET requests.

# How do the apps behave when offline?

No daya synchronization occurs when the user is offline. Through their nature as MS Office add-ins, the apps cannot do anything when they are closed; the app code only runs when launched, and all code processes cease when the user closes the app. 

#### Additional Resources

- [Microsoft documentation on mailbox items available to addins](https://support.microsoft.com/en-us/office/use-add-ins-in-outlook-1ee261f9-49bf-4ba6-b3e2-2ba7bcab64c8)
- [Microsoft documentation on Outlook privacy and security](https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/privacy-and-security)
- [Microsoft documentation on end user privacy concerns](https://learn.microsoft.com/en-us/office/dev/add-ins/concepts/privacy-and-security#addressing-end-users-privacy-concerns)