What Chui does with a calendar, what it never does, and how to disconnect one.
A calendar is connected from Settings, over Google or Microsoft. It is read-only — Chui cannot create, move or cancel anything in it, and it does not want to.
What it buys:
What is stored, and for how long. Chui keeps the meetings in your next day and a half on its servers — that is what lets it offer to record one at the moment it begins. For each it holds what the invitation carries that helps Chui record and name the meeting — today that is what it is called, when it begins and ends, how and by what link it is joined, its body or agenda, who was invited, whether you accepted, and which recurring meeting it is an occurrence of. A meeting that has ended is deleted within twenty-four hours; disconnecting the calendar deletes every one of them at once. Nothing older is kept, and nothing about the people on an invitation is looked up, enriched or kept separately. A meeting stored with a recording is part of that recording and lives as long as it does.
How loudly Chui announces a meeting is a setting: nothing, a notification, or an alarm; at the start or one or five minutes before; for every meeting or only for meetings with other people in them.
Ten minutes before a meeting Chui knows something about, the phone gets a Briefing instead of the ordinary reminder: the meeting's name and up to three short lines — what the last recorded occurrence of the same recurring meeting left open, and where things stand with the people on the invite Chui already knows. Tapping it opens the Briefing screen, which has the same lines, one line per person, and the button that starts recording. The same screen opens from the meeting on “Coming up”.
It is built from every meeting you can open — your own, and a colleague's that your team shares with you — and from the people in them; never from mail, never from the web. When the last occurrence was a colleague's recording, the Briefing says whose it was. So when you send somebody to a meeting in your place, your next Briefing already knows what was decided there. A meeting with nobody Chui knows and no earlier recording gets no Briefing and keeps the ordinary reminder, so there is never a Briefing with nothing in it. It follows the reminder setting: “None” turns it off too.
Notes for next time. On a person's page, under “Next time”, you can leave a short note — «ask about the office lease». It goes at the top of the Briefing of the next meeting that person is invited to, so it is also in the push ten minutes before; that push is the reminder. A note reaches a meeting only through the person's email address on the invite, so a person Chui has no address for never gets one. When a meeting with them is recorded, Chui reads its summary and marks the note done if it was raised; otherwise it waits for the next meeting. A meeting Chui had nothing else to say about gets a Briefing when a note is waiting.
Some organisations require an administrator to approve an app before it may read calendars. Chui says so when that happens and offers a link to send to whoever handles it, which approves Chui for the whole company in one click.
Removing a calendar from Settings stops the upcoming meetings appearing and deletes the stored ones. Your recordings stay — they are meetings now, not calendar entries.
An assistant connected to Chui can see what is coming up — list_upcoming() is what answers "what do I have today?" — and can list what is connected with list_calendars(). It reads the same merged day the app draws: all-day entries and meetings you declined are already out of it, and a meeting Chui has recorded is marked as recorded. Every meeting carries an event_id; one Chui has a Briefing for is marked has_briefing, and get_brief() answers with it — "brief me before my next meeting".
It can write the Briefing too. prepare_write_brief() reads back what a meeting's Briefing says now and what it would say, and write_brief() then writes it — to correct one Chui built, or to write one for a meeting Chui knew nothing about. A Briefing written this way is never rebuilt by Chui. And it can leave you a note for the next meeting with somebody with leave_note(), list them with list_notes(), and change or remove one, each in two steps (prepare_update_note() then update_note(), prepare_remove_note() then remove_note()).
It cannot connect one. A calendar permission belongs to your account and outlasts the assistant, so signing the assistant out would not take it back — Chui therefore refuses to start a calendar consent on an assistant's behalf, however the request is made. connect_calendar() answers with directions for you to follow in a browser, which is where consent happens and always will.
It can disconnect one, and that one is split in two so the question always gets asked. prepare_disconnect_calendar() changes nothing and answers with the account by name and a list of exactly what would go; disconnect_calendar() then accepts only a token that first call minted, so it can never act on a calendar it was not handed the details of, and never on a different one.
What goes is worth reading before you say yes. The permission, revoked at Google — Microsoft offers Chui no way to withdraw a consent, so there you remove Chui from your connected apps yourself, and Chui says so rather than claiming it is done. The stored upcoming meetings. And the link between your recordings and the calendar entries they were, which does not come back if you reconnect: reconnecting makes a new connection, so Chui stops marking those meetings as already recorded and stops offering the earlier meetings in the same series. Your recordings, their titles and their guest lists are untouched.
What Chui can and cannot promise there. Chui always produces that list, and your assistant is told to show it to you and wait for a yes. What Chui cannot do is check that it did: an assistant you have set to approve everything automatically can run both steps in a row. If that matters to you, leave this tool needing your approval in your assistant's own settings — that switch is the part that stops it, and Chui would rather say so than let you assume otherwise.
Nothing an assistant can reach writes to your calendar itself. Chui never asked for permission to.
What an assistant sees of a calendar on a RECORDING — the meeting's own name, who was invited, and which other recordings are occurrences of the same recurring meeting — is What happens after you stop.