Back

What this system sees

This is the complete list. The software that connects to your tools asks for exactly these permissions and nothing else, and this page is generated from that same list.

The short version

It reads, it never writes.

Every connection to your tools is read-only. It cannot send an email, post a message on your behalf, create a calendar event, or change anything in your accounts.

The one thing it sends is your own brief, to you.

The delivery connection can message one direct-message channel: yours. That destination is fixed when you connect it and no job can change it.

You never type a password here.

Google and Slack show you their own permission screens. Granola gives you a token you can revoke in Granola.

You can take it all back.

Disconnect revokes the permission at the provider first, then deletes the stored key with no recovery window. You can also revoke from your Google account’s security page at any time.

Connection by connection

Google Calendar

Your meetings, so the morning brief knows what your day looks like.

What it reads
  • The titles, times, attendees and descriptions of events on your calendars. It cannot create, change or delete events. https://www.googleapis.com/auth/calendar.readonly
What it never reads
  • Your email. Gmail is not requested in this phase, and when it is, it will be read-only: nothing in this system can send, edit or delete mail.
  • Your Drive files.
  • Your password. Google shows you its own consent screen; this system only receives a token you can revoke at any time.

Revocation: confirmed by the provider when you disconnect. Key rotation reminder after 180 days.

Granola

Your meeting transcripts, stored verbatim so nothing is lost to a summary.

What it reads
  • Transcripts and notes of meetings recorded in your Granola account. granola:read
What it never reads
  • Meetings you did not record.
  • Anything outside your own Granola account.

Revocation: manual, in Granola › Settings › API tokens › Revoke. We tell you this when you disconnect. Key rotation reminder after 90 days.

Slack (delivery)

Where your briefs arrive: a direct message from your second brain to you, and only you.

What it can do
  • Nothing. This lets the system send a message to the one direct-message channel chosen at connect time. chat:write
  • Nothing. This lets the system open that one direct-message channel with you. im:write
What it never reads
  • Any channel, group or direct message. This connection has no read scope at all.
  • It can never message anyone but you. The destination is fixed when you connect and cannot be changed by a job.

Revocation: confirmed by the provider when you disconnect. Key rotation reminder after 180 days.

Gmail (read-only)

Overnight mail and threads awaiting your reply.

Not yet available
What it reads
  • Messages and labels. It cannot send, draft, edit, archive or delete anything. https://www.googleapis.com/auth/gmail.readonly
What it never reads
  • It cannot send mail. Drafts the system proposes are written to your vault, never to Gmail.

Revocation: confirmed by the provider when you disconnect. Key rotation reminder after 180 days.

Slack (reading)

Mentions and threads in channels you are in.

Not yet available
What it reads
  • Messages in public channels you are a member of. channels:history
  • Messages in private channels you are a member of. groups:history
  • Your direct messages. im:history
  • Names of people in the workspace, to label who said what. users:read
What it never reads
  • Channels excluded in your deployment's classification file. Those are dropped before the model sees them.

Revocation: confirmed by the provider when you disconnect. Key rotation reminder after 180 days.

Linear

Open issues assigned to you.

Not yet available
What it reads
  • Issues, projects and comments you can see in Linear. Nothing can be created or changed. read
What it never reads
  • Anything you cannot already see in Linear.

Revocation: confirmed by the provider when you disconnect. Key rotation reminder after 180 days.

Where it is stored, and for how long

Your permission keys

Live in AWS Secrets Manager in Pipeline’s AWS account, encrypted, readable only by this application. They are deleted immediately when you disconnect. They are never in a database, a file, a log, or a browser.

What your second brain reads

Meeting titles and transcripts are written to your own private vault repository, which belongs to your deployment alone. Nothing from one person’s vault is ever read by another’s.

The activity log

Records when a job used a connection, which job, what kind of thing it read and how many. Never the content. It cannot be edited or deleted, by anyone, including the operator.

Who can see it

You

See your connections and your activity log on these pages.

The operator

The person who runs this system sees that connections exist, their status and the activity log. Never your keys or your content.

Scheduled jobs

Yours, and only yours, receive short-lived access tokens to do their reading. They never receive the long-lived key.