This guide supplements the Jackdaw Privacy Policy. A connection is optional, and the authorization screen or device permission prompt controls the access you grant. Jackdaw does not access a provider listed here unless you enable that connection.
Communication, calendars, and people
- Gmail: message and thread bodies, headers, metadata, labels, and attachments, used for email display and search, summaries, source-backed context, and user-confirmed sending. Jackdaw does not change Gmail labels or delete messages.
- Google Calendar: subscribed calendar identifiers and properties plus event titles, times, descriptions, locations, attendees, and conferencing details, used for schedule display and search, meeting context, and user-confirmed creation or changes to events on calendars the user owns.
- Google Contacts: saved contact names and available email addresses, phone numbers, organizations, and profile photos, used for contact search and relationship context. Jackdaw does not request Google's separate “Other Contacts” permission and does not modify contacts.
- Google Drive and Docs: shared-drive names, membership and permissions, file metadata, and the text of native Google Docs in the shared drives a Jackdaw workspace administrator selects, used for search, summaries, and source-backed work context. Google Sheets, Google Slides, PDF, and Word files in those drives are copied as read-only originals so members can open them in Jackdaw; they are not used for search or summaries. Jackdaw does not modify files or sharing permissions.
Google Workspace administrator connection
A Google Workspace super administrator may install Jackdaw once for a domain. That installation authorizes reading the organization directory, shared-drive content, and members' Gmail, Calendar, and saved Contacts. It also permits a matched member to send email or create or change an event on a calendar they own after confirming that specific action in Jackdaw. Installation alone does not import those content sources: a Jackdaw workspace administrator separately selects each shared drive or member source, and every source is off by default. Directory data is used to map people and enforce source permissions. Shared-drive content follows the drive's mapped membership; a member's Gmail, Calendar, and Contacts content is visible in Jackdaw only to that matching member. Turning off a selected organization source or disconnecting the organization connection removes its imported Jackdaw projection and stops future access. Google Workspace administrators can also uninstall the app in the Google Admin console.
Microsoft
Outlook email and attachments, calendars and events, contacts, and tasks covered by the permissions you approve. Jackdaw uses this information for connected inbox, schedule, contact, task, search, summary, and source-backed context features and for actions you direct.
Apple
Contacts, calendars, reminders, and health or activity records covered by the device permissions you enable. Jackdaw uses these categories for their corresponding people, schedule, task, and personal activity features.
Slack and Discord
Messages, direct messages, channels or servers, mentions, participants, and related metadata available to the connected account or authorized app. Jackdaw uses this information for search, source-backed context, summaries, and relationship context.
Files, notes, projects, and tasks
Microsoft OneDrive
Files, folders, document content, and related metadata covered by the permissions you approve, used for file discovery, search, and source-backed context.
Notion
Pages, databases, notes, properties, and related workspace metadata shared with the integration, used for search and source-backed work context.
GitHub and GitLab
Repositories, issues, pull or merge requests, comments, and activity available to the connected account, used for project search, summaries, and development context.
Linear and Todoist
Issues or tasks, projects, cycles, labels, comments, assignments, and related metadata available to the connected account, used for task and project context and the actions presented in Jackdaw.
Health and activity
Apple Health
Workouts and activity records and, where you grant permission, sleep, readiness, and recovery information. Jackdaw uses this information for personal activity history and context.
Other connections
X
Public posts, replies, profiles, search results, and related metadata available through the API token you supply, used for reply discovery and context. Jackdaw stores the supplied credential so it can make the requests you initiate or configure.
Rules shared by every connection
The Privacy Policy's connected-services rules govern authorization, use, storage, processor access, human access, retention, disconnection, and deletion for every provider in this guide. Available integrations and provider capabilities can change; if a change materially expands how Jackdaw uses connected data, we will update the policy and request consent where required before using the data in that new way.