Privacy Policy
App Permissions

Index

To provide you and your teammates visibility into each others' presence and to provide you with insights and coaching about your working style and habits, Ampll needs access to some of your activity data. You can grant the Ampll app this access via standard permissions on your devices and within your applications.

This page illuminates the minimum set (required) of permissions the Ampll app needs to be functional and the (optional) full set of permissions that enhance its utility. For each permission requested below, you’ll see why Ampll needs the specific permission, exactly what it uses the access for, and of equal importance, what Ampll does not do with these permissions

For a detailed explanation of each requested permission, click its name below.

Required Permissions

Ampll is currently available for people using either Google or Microsoft 365 accounts.  Here are the permissions with these providers Ampll needs to function:

Optional Permissions

In addition to the base set of permissions above, Ampll offers the following optional integrations to maximize the work style insights it can provide to you.

Detailed Explanations

Login (Google, Microsoft, and Slack)

What is being requested

  • Microsoft calls this login permission “Sign you in and read your profile.”
  • Google calls these login permissions “See your personal info, including any personal info you’ve made publicly available” and “See your primary Google Account email address.”
  • Slack calls this login permission “View information about your identity.”

What is being requested

This access is used to create and access your Ampll user account.
Ampll currently supports login services from Google, Microsoft, and Slack. As such, Ampll never stores your passwords. Moreover, by utilizing these providers, you can take advantage of their native password recovery, multi-factor authentication, and security audit features. Both providers also let you revoke access to apps like Ampll at any time.

How your data is used

In addition to logging you in, Ampll  stores your email, full name, and profile image to create your user account.

How your data is not used

Your personal information accessed from creating an account and logging into Ampll will:

  • Never be sold to a third party.
  • Not be used in any other way beyond delivering you the service represented by the Ampll app and its functionality.
  • Not be kept beyond your direction: You can delete your personal information at any time from within the app.

Calendar

*Calendar Access (Google and Microsoft)

What is being requested

  • Microsoft calls these calendar permissions “Have full access to your calendars” and “Read your contacts.”
    Google calls the read-only calendar permission “See and download any calendar you can access using your Google Calendar.”
  • Google calls the calendar write permission “View and edit events on all your calendars.Note: For Google, the ability to write calendar events is separate and optional while Microsoft combines this access into a single permission.

Why is this requested

Ampll requests both read and write access to your calendars. Read access to your calendars allows Ampll to analyze your schedule, provide you with real-time working style insights and coaching based on your preferences. Write access to your calendars is used to reserve specific time on your calendar, such as focus time or well-being time so you can block out your availability for this activity. Note: The schedule reservation feature is currently in testing and will be released in the app soon.

Calendar permissions is highly recommended to use Ampll because your schedule management is central to providing insights and coaching around your working style and work/life integration habits. For instance, your potential for “Zoom fatigue” from remote meetings and ability to find uninterrupted time for focused work are vital to measuring your energy and delivering customized coaching.

How your data is used

In general, Ampll aims to use and store only the metadata about your calendar - the date, time, duration, meeting name, the meeting location, and the meeting participants. To enable detection of remote meetings, Ampll inspects the content of the meeting invitation for fingerprints of conferencing applications, including Zoom, Google Meet, and Microsoft Teams. While Ampll does store metadata about underlying conferences, it does not store the contents of the meeting invitation itself. To parse your recipient list, use of the Microsoft programming interface also entails a permission to read your contacts.

How your data is not used

Your personal information accessed from creating an account and logging into Ampll will:

  • Never be sold to a third party.
  • Not be shared with anyone at your company in an identifiable way, without your express permission
  • Not be used in any other way beyond delivering you the service represented by the Ampll app and its functionality.
  • Not be kept beyond your direction: You can delete your personal information at any time from within the app.

Email

*Email Read-only Access

What is being requested

  • Microsoft calls this email permission “Read your mail.”
  • Google calls this email permission “View your email messages and settings.”

Why is this requested

As an optional capability, Ampll can detect the time you spend reading and writing emails. To perform these functions, Ampll requests email permissions.We recognize that there are many security implications around email privileges and remain vigilant to minimize the data used and stored by Ampll. Still, with the “always on” culture in modern work and the growing incidence of burnout (even as documented by the World Health Organization), we feel that providing objective measurements of time spent reading and composing emails can be both useful and important.

How your data is used

Ampll neither “reads” nor stores the contents of your email. However, the limitations of the providers’ programming interfaces require Ampll to request "read" permissions to obtain the metadata used to measure the time you spend on email.

To determine whether you are reading email, Ampll looks for the marking of messages from “unread” to “read.” It also looks for the deletion or movement of email from the Inbox. To identify the emails you interact with, Ampll stores the mailbox ID, timestamps, and counter of overall message changes (read, moved, deleted). Ampll does not store any content of your emails.

To determine whether you are composing emails, Ampll uses two different methods. If your email client writes to the Drafts folder, Ampll looks for the writes to the Drafts folder and changes to underlying word counts to measure the actual time you spent writing emails. If your email client does not write to the Drafts folder, Ampll simply stores a word count for the sent email to estimate the time you spent writing them. Similarly, to analyze email messages you sent prior to setting up your Ampll account, Ampll uses this sent email word count method. To identify individual emails you compose, Ampll also stores their unique IDs (mailbox ID, message ID, thread ID), timestamps, message sent status, the from name and email address, and recipients’ names and email addresses. The recipient information is used to show you the time you spent on specific emails in the Ampll app user interface. Ampll does not store any content of the emails you compose.

How your data is not used

Your personal information accessed from creating an account and logging into Ampll will:

  • Not store your email data beyond what is listed above.
  • Never be sold to a third party.
  • Not be shared with anyone at your company in an identifiable way, without your express permission
  • Not be used in any other way beyond delivering you the service represented by the Ampll app and its functionality.
  • Not be kept beyond your direction: You can delete your personal information at any time from within the app.

Cloud File System Metadata

What is being requested

  • Microsoft calls this file sharing permission “Read all the files you have access to.”
  • Google calls this file sharing permission “See information about your Google Drive files.”

Why is this requested

As an optional capability, Ampll can measure the time you spend in your files accessed via cloud systems, including those written to Google Drive by Google Docs, Google Sheets, Google Slides or those written to Microsoft OneDrive by Microsoft 365 applications. The aim is to help you measure your uninterrupted “deep work.”

Providing objective measurements of “focus time” was a top concern in the market research that informed functionality for the Ampll app. This file metadata permission for cloud systems provides a good balance of measurement ability with minimal privileges. In addition, with the growing use of real-time document sharing during meetings, the Ampll can begin to help you track and measure the efficacy of modern business habits.

How your data is used

With its requested permissions to read shared file metadata, Ampll can view information about your activity on files. To measure time spent in files, Ampll stores the file's unique ID, file name, file content type, revision ID, timestamp, and the name and email address of the user making the revision for each activity. Ampll does not read or modify your file contents.

How your data is not used

Your personal information accessed from creating an account and logging into Ampll will:

  • Not store your file data beyond what is listed above.
  • Never be sold to a third party.
  • Not be shared with anyone at your company in an identifiable way, without your express permission
  • Not be used in any other way beyond delivering you the service represented by the Ampll app and its functionality.
  • Not be kept beyond your direction: You can delete your personal information at any time from within the app.

Slack

What is being requested

  • The permissions the Ampll app uses to connect to your Ampll workspace and map your Ampll team members to Slack users include “Can view information about a user’s identity, View the name, email domain, and icon for the workspaces you’re connected to,” “View people in your workspace,” and “View email addresses of people in your workspace.”
  • The permissions Ampll uses to detect your public channel access include “View messages and other content in your public channels” and “View messages about public channels in your workspace.”
  • The permissions Ampll uses to set your status are called "View profile details about people in a workspace" and "Edit a user’s profile information and status."

Why is this requested

As an optional capability, Ampll can automatically update your Slack status with your presence and detect your usage of Slack public channels when away from your desktop computer. The interpretation of time you spend on Slack using this method augments the Slack application usage detected by the Ampll app on your Mac or Windows PC for a better picture of your time.

How your data is used

Information about your Slack identity and your Slack workspace are used for display purposes in the Ampll Preferences screen to provide further information about connections. The ability to view the people and email addresses in your workspace will be used to assist in inviting your teammates to share their availability in Ampll.

Information about your Slack usage is limited to information about messages written or Slack calls in public channels. Ampll does not store the content of your messages or listen to the content of your calls. In addition, Ampll does not see information from your private DMs, your private group DMs, and your private channels at all.

To read information about your activity in public channels, Ampll requests access to view information about your public channels. Information collected from your Slack messages include the message ID, timestamp, word count, public channel ID, public channel name, workspace ID, and the internal ID of the message author. Ampll does not store the content of the Slack messages. To help make the collected data readable in the Ampll application, Ampll collects some information about the workspace itself and the users to convert machine-generated IDs into human-readable names.

Information collected from your Slack calls include the call ID, timestamp, public channel ID, public channel name, workspace ID, and the internal ID of the call originator. Ampll does not have the permissions to listen to your calls.

How your data is not used

Your personal information accessed from creating an account and logging into Ampll will:

  • Not store your Slack beyond what is listed above.
  • Never be sold to a third party.
  • Not be shared with anyone at your company in an identifiable way, without your express permission
  • Not be used in any other way beyond delivering you the service represented by the Ampll app and its functionality.
  • Not be kept beyond your direction: You can delete your personal information at any time from within the app.