workflow
workflow connects Simon Lee’s own Google account to his private journal and planning assistant. It is built for one person’s personal use. It is not offered to the public, and nobody else can sign up or connect an account.
Personal use only. Only one Google account, the owner’s, can be connected. The sign-in page is protected by a secret that only the owner holds, and there is no registration, sharing or public access.
What workflow does
Simon records thoughts, ideas and tasks by sending messages to a private Telegram bot. workflow brings in context from his Google account so that this journal can:
- Prepare a morning briefing with the day’s calendar events, open tasks and starred emails awaiting follow-up.
- Link journal entries to the people, events, tasks and emails they mention.
- Turn notes into tasks. Simon can add tasks to Google Tasks from the chat. When a journal entry contains an action item, workflow suggests a task and adds it only if he confirms.
- Help the family plan. In a private family group chat, approved family members can ask the bot about family-related emails, events and tasks, and add tasks to the family task lists. Only items classified as family-related are used there.
Google data it uses, and why
- Google Tasks (read and write): shows open tasks in the briefing, and creates the tasks added from the chat.
- Google Calendar (read-only): reads events from 30 days back to 30 days ahead, with their titles, times, locations and attendees, for the briefing and to link journal entries to events.
- Google Contacts (read-only): reads names, email addresses, phone numbers and notes, to recognize the people a journal entry mentions.
- Gmail (read-only): reads emails Simon sent in the last 30 days, starred emails, and family-related emails from the last 30 days. It uses the subject, sender, recipients, labels and plain-text body for follow-up reminders, for linking to journal entries, and for answering family questions. It never sends, deletes or changes email.
How the data is handled
- Google data is stored in a private database that only the owner can reach.
- To write the briefing and answer questions, relevant excerpts are sent to AI model providers (Anthropic and OpenAI) through their APIs. Their terms don’t let them train their models on this data.
- The data is never sold, never used for advertising, and never used to train AI models.
- workflow’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Details are in Section 3 of the Privacy Statement.
Disconnecting
Access can be removed at any time at myaccount.google.com/permissions. workflow then stops reading the account. Stored Google data is deleted on request.
Policies and contact
workflow is covered by the Unsubject Privacy Statement and Terms of Service. For questions, write to webmaster@unsubject.com.