Connected Integrations
Last updated:
This appendix forms part of our Privacy Policy, and the Privacy Policy's definitions apply to it. The Privacy Policy describes the data we read from connected apps in general (Section 2.4), how people in that data are pseudonymised and revealed, and how long data is kept (Section 6). This appendix adds, for each integration whose handling goes beyond that general description, the access we request, what we keep and any period of its own. Integrations not listed here are covered by the general description alone.
1. Google Workspace
Our use of information received from Google APIs is also subject to Section 4 of the Privacy Policy, including our commitment to the Google API Services User Data Policy and its Limited Use requirements.
1.1 Access we request
When a Google Workspace administrator connects Google Workspace to Trefur, we ask Google for the following read-only access. Google shows the exact list on its consent screen before access is granted.
| Access (Google scope) | What Trefur reads | Why |
|---|---|---|
admin.directory.user.readonly | The list of users in your Workspace domain | To count how many people use each AI app or integration, and to recognise activity by your users |
admin.reports.audit.readonly | Admin audit reports, such as app authorisation events, app API activity, Drive file access by third-party apps, Gemini activity and admin setting changes. Gemini activity can include prompt and response text where Google reports it; that text is handled under your workspace privacy setting. IP addresses of the people involved are discarded | To detect AI apps and AI activity in your Workspace and show it to your administrators |
If an administrator also connects Google from the discovery page to extend discovery, we additionally request read-only access to Google Chat spaces and memberships (chat.spaces.readonly, chat.memberships.readonly) and Apps Script process activity (script.processes), and access to the third-party apps each user has granted access to (admin.directory.user.security). Google describes that last permission as able to manage those grants; Trefur uses it only to list them and never changes or revokes anything. We use this data to find AI tools and other third-party apps connected to the workspace, and to show what each one can access.
Where Trefur offers it, an administrator may also connect Google so that your own agents can use Google Drive, Docs, Sheets, Gmail, Calendar or Contacts as tools. Google then shows the additional scopes on its consent screen. Trefur uses that access only to carry out the actions your agents request, on your instruction.
If you sign in to Trefur with Google, we receive only your basic profile and email address (openid email profile) to sign you in.
1.2 What we keep
- Apps and their access. Each third-party app found, the permissions it was granted and when it was first and last seen, with the people who granted it stored as pseudonymous references (Privacy Policy Section 2.4).
- Directory. The people involved and their departments, as described in Section 2.4 of the Privacy Policy.
- App activity (Pro plans and above, where enabled for your workspace). Which Google services (such as Gmail, Drive or Calendar) each connected app called on users’ behalf, kept as counts per app by the hour (by the day after 14 days) and not per person.
- Drive files opened by third-party apps (Pro plans and above, where enabled for your workspace). For each file a third-party app opened on a user’s behalf: its name, encrypted with a key specific to your workspace; its file type; whether it is shared outside your organisation or by public link; and whether its owner is outside your organisation. We do not keep the file’s contents, its Google identifier (only a keyed fingerprint, so the same file is counted once) or who owns it. Names are shown as counts until a workspace owner or admin reveals the names of the files one app opened, giving a reason; every reveal is recorded in the workspace audit log.
1.3 How long we keep it
- App activity and audit events follow your plan's retention period (Privacy Policy Section 6). The list of apps found is kept while your workspace exists.
- Drive file names are kept for a period set by your plan, measured from the last time the app was seen opening the file: Pro 30 days; Team and Mid-Market 90 days; Enterprise and custom contracts 90 days unless a workspace owner or admin sets a period between 30 and 365 days. The period is never longer than your plan's retention period, and if we cannot confirm your plan we apply 30 days. A hold for investigation keeps one app's file names until the hold is released (Privacy Policy Section 6).