Privacy, security, and data safety notes

What data we collect

Required permissions for Shared Email Templates for Outlook

Your use of our products does not give us access to any sensitive personal data stored in your Microsoft account such as physical address or credit card details.

Depending on the Shared Email Templates feature you're going to use for the first time, you'll get the corresponding permissions request like the one in the screenshot below:

We use each of the permissions granted by you for a specific purpose. Please see detailed descriptions of required permissions in Privacy Policy (https://www.ablebits.com/docs/shared-templates-privacy-policy/#annex-two).

Required permissions for Shared Email Templates for Gmail

Your use of our products does not give us access to any sensitive personal data stored in your Google account such as physical address or credit card details.

Depending on the Shared Email Templates feature you're going to use for the first time, you'll get the corresponding permissions request like the one in the screenshot below:

We use each of the permissions granted by you for a specific purpose. Please see detailed descriptions of required permissions in Privacy Policy (https://www.ablebits.com/docs/shared-templates-privacy-policy/#annex-three).

Where we store the collected data

All your templates are stored in an encrypted cloud-based database hosted by Amazon Web Services. This is a protected storage inside an isolated private network. All data can only be accessed through the template sharing service, the core back-end service of Shared Email Templates.

When you create an encrypted team, you add one more layer of encryption. In this case, all templates are encrypted with the AES symmetric-key algorithm before being saved to the cloud database. Please note, you are the only person who knows the Team Password and passes the password to your teammates in a safe way.

Also, SET stores local copies of your templates (the local templates cache) in the following locations on your devices:

• web browser local storage in case of the Shared Email Templates web app or the Shared Email Templates add-in running in Outlook on the web (Outlook Online)
• Outlook cache in case of the Shared Email Templates add-in running in your desktop Outlook.
• in your web browser local storage in case of the Shared Email Templates web app or the Shared Email Templates extension running from Chrome Web Store.

The local templates cache is isolated and not accessible by other browser extensions or Outlook add-ins. We store the local templates cache unencrypted because of the performance reasons. Otherwise we would have to decrypt templates each time you start Shared Email Templates, which would dramatically increase its startup time.

The local templates cache is refreshed with each change in templates, e.g. if your teammate creates a new template, the new template goes to the cache.

How it works

Shared Email Templates is designed and built taking care of your privacy and security; it is architected and developed following the zero-trust and privacy-by-design principles. The diagram below explains how Shared Email Templates works for the main use case — inserting a template into the email message you are writing. Your mail, attachments, images, and other Outlook or cloud-based data stay on your device and on your cloud storage. No data is sent to Shared Email Templates services or any 3rd-party service, and all actions and transformations are done locally, in your Outlook.

It works the exact same way when you use the extension from your Gmail:

1. A user starts the Shared Email Templates add-in or Chrome extension.
2. From the Shared Email Templates services, the add-in/extension loads and decrypts the user's and a team's templates, as well as profile and team properties.
3. The user inserts the selected template into the currently opened email message.
4. The add-in/extension parses the template and its macros.
5. From Outlook or Gmail, the add-in/extension reads the current email message if macros referring to the message content are found.
6. From Azure Active Directory, the add-in/extension reads the user's properties if macros referring to AD properties are found.
7. The add-in/extension asks Outlook or Gmail to attach files or insert pictures if the Attach or InsertPicture macro is found.
8. The add-in/extension changes email message fields if corresponding macros are found.
9. The add-in/extension inserts the processed template into the current cursor position.
10. The add-in/extension replaces the current signature (if there's any) with the signature embedded into the template.

What data others collect, but we don't

We do not collect any payment information, such as bank account details, credit card information, and check information.

You might find that Microsoft Office telemetry is run together with the Shared Email Templates app and add-in. This is because we use Microsoft's office.js framework.

Who can access your personal data at our office

We develop and test our products on specially created testing configurations, so access to your personal data is very limited and only a few people at our office have permissions.

However, no one has permissions to access your templates and passwords, including your personal password and Team Passwords.

Read-only access (provided on request only) is given to a few of our core engineers and only in case they need to figure out some complex technical thing.

Read-only access is provided to our senior system administrator to perform online monitoring and periodic maintenance of our servers and services.

Read-only access to your data is also given to our customer support service and sales specialists. They need your personal data to assist you when you contact us with related questions.

How we control access to your data at our office

We make a lot of effort to keep your data safe. Firstly, we restrict physical access to our office and to our computers with door locking, access control systems, alarm system, and surveillance facilities. Secondly, we restrict access to our systems by using central management of system access, no guest accounts policy, password and authentication policies.

Also, we control access to data with the help of differentiated access rights, access rights defined according to duties, measures to prevent the use of automated data-processing systems by unauthorized persons.

To prevent unauthorized access, data alteration and disclosure, all our communication channels are encrypted using virtual private networks for remote access, transport and communication of data. All our sub-networks are joined into a wholly-owned private network. Finally, all our computers are protected with antivirus software and firewall systems.

You can find detailed information on our technical and organizational security measures in our Data Processing Agreement at https://www.ablebits.com/docs/shared-templates-dpa/#annex-two.

How to erase your data

To remove your data, simply delete all the teams where you are the administrator, and then delete your account in the Profile section. To have all your communications with us removed from our systems, please contact our customer support service.

How you can make sure that everything above is true

You can see all the information that is sent to our services and storages with your own eyes with the help of the Fiddler tool or your browser console. Also, you can inspect our client-side source code directly in your web browser.

Data access using Microsoft Graph

Sign in/Sign up with Microsoft

General Shared Email Templates functionality

Mail Merge functionality

Data access using Google APIs