What it does

When you ask the panel to look, we read the period of your diary that you choose. By default this is tomorrow. You can choose up to three months. We show the meetings that include somebody from outside your own organisation.

Press Brief me on a meeting. The questionnaire opens with that meeting already filled in. This includes who it is with, their organisation, when it is and how long it runs. It also includes who else is invited and what the invitation says about the agenda. You can edit or empty every box before you submit anything.

The permissions we ask for

For Google, we ask for one calendar scope: https://www.googleapis.com/auth/calendar.events. It covers events and nothing else about your calendar. It does not reach your calendar’s settings or its sharing rules. We also ask for openid and email. These tell the panel which account is connected, so you can see it and disconnect it.

For Microsoft, we ask for Calendars.Read. It is read-only, and the Outlook side only reads today.

Why the Google one can write, and what it writes. We can put the briefing into your own diary 15 minutes before the meeting, so it is on your phone as you walk in. We do this only when you press the button for it. Google does offer one narrower permission, calendar.events.owned, which covers only calendars you own; we do not use it yet. The scope that writes only to a calendar we create would put the briefing on a calendar nobody has switched on.

Instead, we follow one rule, and it is part of how the feature is built. A briefing always goes into a separate entry of your own, private, with no guests on it. We never write into the meeting itself. Everybody invited to a meeting can see its description. So if we added the briefing there, the person you are meeting would see your notes on them. Nothing we do changes an entry anybody else can see.

We do not ask for your mail, your contacts or your files. None of the permissions here would let us read them.

What we read, and what we do not read

From each meeting in the period you chose, we read its title, time, length, the addresses of the people invited and the invitation’s description. The description is usually the agenda, and it saves you retyping.

We do not read a meeting’s location or anything attached to the invitation. We tell Google and Microsoft not to send them. Before the description reaches your screen, we remove every joining link, meeting ID, passcode and dial-in number.

We never store the events themselves. We read them, use them to fill in the form in front of you, and then discard them. We keep what you submit: your answers, so you can reopen and rebuild the briefing later. You can delete the briefing at any time, which deletes the answers with it.

We use nothing from your diary to train a model or to advertise. We use it only to produce the briefing you asked for. We do not sell it or share it with anyone for their own purposes. Our use of information received from Google APIs follows Google’s API Services User Data Policy, including its Limited Use requirements.

If you would rather not connect anything

You do not have to. You can type the meeting in or paste the invitation. Or you can drop the .ics file your calendar exports onto the page. We read that file inside your own browser and never upload it. The briefing is the same either way.

Turning it off

You disconnect on the same panel you used to connect. For a Google calendar, we delete our own copy of the token and tell Google to revoke it. So the permission is gone at both ends. The privacy notice gives full detail of what we hold and for how long.

Privacy notice · Terms · Fair use policy · [email protected]