To answer this question simply, we receive access tokens for your account when you authorise Fetch and add an integration. We request permissions which are just sufficient for us to serve you well. This means the following for specific integrations, after you integrate them.

• Github: Read and write access to your public and private repositories (doesn't support read-only access)
• Slack: View information on the user's identity and email address. Search the workspace’s content
• Trello: Read access on all boards and teams
• Asana: Access your name, email address, tasks, projects and workspaces. Asana doesn't allow granular permissions giving us access to create and modify tasks, projects and comments on your behalf. We don't ever use write permissions.
• Box: We have the ability to read all files stored on Box in addition to your email address.
• Google: Access to your basic profile info and the ability to read and download all your files. We won't ever download your files.
• Gitlab: We get basic user information and the ability to read code, issues, projects.
• Atlassian: In addition to basic profile information, we get read access to your Jira and Confluence content.
• One Drive: We get your basic information and read access to your sharepoint online and one drive files.
• BitBucket: We get your basic information and read permissions for your repositories, issues, pull requests, team members and wikis.

You can go to the integrations page and disconnect any application with just a single click.
This would remove access tokens stored at our end for that particular integration. If you want to revoke access at the respective platforms as well, you can use the following guide:

• Github: Settings ⟶ Authorized applications ⟶ Fetch ⟶ Revoke
• Slack: Open Workspace ⟶ More ⟶ Apps ⟶ Fetch ⟶ Settings ⟶ Remove Configuration
• Trello: Settings ⟶ Applications ⟶ Fetch ⟶ Revoke
• Asana: Settings ⟶ Apps ⟶ Fetch ⟶ Deauthorize
• Box: Account Settings ⟶ Security ⟶ Fetch ⟶ Forget App
• Google: Permissions ⟶ Fetch ⟶ Remove Access
• Gitlab: Settings ⟶ Applications ⟶ Fetch ⟶ Revoke
• Atlassian: Profile And Visibility ⟶ Connected Apps ⟶ Fetch ⟶ Remove Access
• One Drive: Please follow these steps by Microsoft
• Bitbucket: App Authorizations ⟶ Fetch ⟶ Revoke

Unfortunately slack doesn't allow any app that uses the search:read scope to be published. More from slack here. This means that we can't publish the Fetch for slack app and your workspace Admin will have to approve it. If you or your workspace admin have more queries, reach out to us at support@getfetch.io.

Unfortunately, slack's authorisation infrastructure doesn't allow for us to request multiple scopes at once. This means that we have to get an initial authorisation for your identity information, which includes your name, email address and some other fields and a second authorisation for getting search access for your workspace's content.

These integrations are an alpha feature for our early adopters and they have not been published or verified by the integration app yet.