⚡ NewAI-Enable Programme — redesign a role from S$1,050 with Job Redesign+ funding
Home/Data Use

Connected Services & Data Use

What JobKred can access when you connect a third-party account, who in your workspace can use that connection, and how the data is handled.

1. What connectors are

JobKred lets you connect third-party services — such as Google Drive, Microsoft OneDrive and SharePoint, Dropbox, Box, Notion, and Atlassian Jira and Confluence — so that content from those services can be imported into your projects and used in chats and workflows. Availability of individual connectors varies by deployment and plan.

Connections are read-only: we do not request permission to send, modify or delete anything in the connected service. The only exception is an explicit export action you trigger yourself (for example, exporting a JobKred file to your own Google Drive).

2. Use of Google user data

JobKred's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In concrete terms, for each Google service:

  • Google Drive — we request the drive.file scope only. JobKred can see only the specific files you select in the Google file picker, never your whole Drive.
  • Gmail (where available) — we request read-only access (gmail.readonly). JobKred never sends, modifies or deletes mail.
  • Google Calendar (where available) — we request read-only access to events.

We use Google user data solely to provide the user-facing features described on this page: importing the content you choose into your JobKred project so it can be searched, summarised and used as context in chats and workflows — including, where you have connected the service to a shared project, by the members of that project (see section 4). We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI models (see section 5).

3. What we access from other providers

  • Microsoft OneDrive, SharePoint and Outlook — delegated, read-only Microsoft Graph permissions. JobKred can only ever read what the connecting account itself can read, and many work or school tenants additionally require your Microsoft administrator's consent.
  • Notion — access only to the pages you explicitly share with the JobKred integration during the Notion consent step.
  • Atlassian Jira and Confluence — read-only scopes, pinned to the single Atlassian site you choose at connect time, and always bounded by your own Jira/Confluence permissions.
  • Dropbox and Box — read-only access to files and metadata.
  • Storage credentials (S3-compatible, SFTP) — used only to list and read the files you point JobKred at.

4. Sharing a connection within a project

A connection belongs to one project, and each project holds at most one connection per provider.

  • If you connect a service in a shared project, every member of that project can browse and import through your connection. This is stated in the confirmation dialog at the moment you connect.
  • If you do not want to share an account, connect it in your private (default) project instead — the connect dialog offers to switch you there. Your default project can never have other members.
  • The people who can use a shared connection are always limited to the members of that one project, who are always members of your own organisation.
  • Your login credentials and OAuth tokens never leave our servers and are never shown to other members. Members use the connection through JobKred's backend only; every browse and import is recorded in an audit log together with who did it.
  • Only a project admin (or an organisation admin) can disconnect the connection. If you leave the project or your organisation, the connection is automatically detached or revoked, and revoking a connection permanently deletes its stored credentials.

5. AI processing

Content you import through a connector is processed by JobKred's AI features: it may be parsed, summarised, converted into search embeddings, and supplied as context to a large language model when you (or members of the project it lives in) use chat and workflows.

  • Requests to our AI model providers are configured for zero data retention: prompts and outputs are not stored by the provider or used to improve their services.
  • Connected-service data is never used to train or improve AI models — neither ours nor anyone else's.
  • Enterprise workspaces can additionally run all AI processing on their own model-provider key (bring your own key), so their data is only ever sent to a provider they have a direct contract with.

6. Storage, retention and deletion

  • Connection credentials are encrypted at rest.
  • Content you import becomes a file in your JobKred project. You can delete it at any time like any other file; deleting it also removes its derived summaries and search embeddings.
  • Disconnecting a provider stops all access immediately, and revocation permanently deletes the stored credentials.
  • You can also revoke JobKred's access from the provider's side at any time — for example in your Google Account security settings or your Microsoft account's app permissions.

7. Human access

JobKred staff do not read the content of your connected services or imported files. The only exceptions are: with your explicit permission (for example, during a support session you initiate), where strictly necessary to investigate abuse or a security incident, or where required by law.

8. Questions

This page supplements our Privacy Policy. If you have questions about how connected-service data is handled, contact us.