Preread
01

Sign in with Google.

Preread works entirely off your Google account: the calendar that has your meetings and the inbox that has the context. There is no separate password.

Continue with Google

Signing in only tells us who you are. Preread is in private access: if you haven't been invited, you'll land on a waiting page and can request access. Once approved, the permissions below are asked for on step 02.

Calendar — read, and edit events

To know which meetings are coming, who is attending, and when. Editing is used for one thing: adding the brief's link to the invite when you approve it.

required
WHAT WE READ
Title, time, guests, description and links for events in the next 7 days, and your past events with the same people.
WHAT WE WRITE
Two lines at the end of an event's description, only when you approve a brief. Never before.

Gmail — read only

To find the thread that led to each meeting: the intro, the deck, the "Thursday works."

required
WHAT WE READ
Recent threads with the guests of an upcoming meeting. Kept encrypted while the brief is drafted, then purged on the schedule you set.
WHAT WE DON'T
Anything else in your inbox. We never index it or train on it.

Gmail — send

Only for the fallback when you are not the organiser and the invite can't be updated: you can email guests the link from your own address, on your click.

required
WHAT WE SEND
Nothing, unless you press Send on a message you have read.

Drive — read only

So a deck someone shared shows up in the brief instead of "there was an attachment."

required
WHAT WE READ
Files shared with or by the guests of an upcoming meeting, and files whose name matches the meeting.
WHAT WE DON'T
Your Drive as a whole.

You can revoke any of these at myaccount.google.com/permissions. Published briefs are unaffected.