Who this applies to
John Assist is a private AI assistant for one person (John) and the small church work he does. It is operated by Mike Pinch (the "operator"), contact Mike@dandlpress.com. It is not open to the public. The operator creates and manages everything it runs on: the computer, the assistant's Google account cosbyassistant@gmail.com, the AI service account and its key, and the web access. John uses the assistant; he does not hold those accounts or credentials.
This policy describes how the assistant handles information, including information it receives from Google. See the home page for what the assistant does.
What Google data the assistant can reach, and what limits we add
The assistant asks Google for a small set of permissions. The table shows two different things for each: what Google allows the permission to reach (the real extent of the access), and the extra limits that our own software applies. Our limits are not enforced by Google; they are rules built into the assistant's tools.
| Permission | What Google lets it reach | Limits our tools add |
|---|---|---|
| Calendar - view events (events.readonly) | View events on every calendar the assistant's Google account can access: its own, and any calendar John chooses to share with it. | The tools read only the calendars on a list the operator sets (the assistant's own, and John's if he shares it). |
| Calendar - manage events on calendars it owns (events.owned) | See, create, change and delete events only on calendars owned by the assistant's account. It cannot change John's own calendar, even if John shares it. | Writes only go to the allowed calendar. Sending invitations and deleting events each need John's clear approval first. |
| Calendar - free/busy | See when calendars the account can access are busy, without event details. | Only the allowed calendars are checked. |
| Drive - files the app creates (drive.file) | Only the files the assistant itself creates or opens, including the Google Docs and Sheets it makes and can edit. | It creates, organises and trashes files only inside a folder named "John Assist". Trashing needs John's approval and is recoverable in Drive's trash for 30 days. |
| Drive - read-only (drive.readonly) | See and download every file the assistant's Google account can access: everything in its own Drive and everything shared with it, including shared drives it belongs to. Google treats this as a "restricted" permission. | The tools search and read Google Docs, Sheets and plain-text files when John asks, and never read PDFs, images or other file types. They cannot change, share or delete anything outside "John Assist"; to edit a shared document the assistant makes a copy inside "John Assist" and edits the copy. |
The assistant's Google account holds only what John shares with it and what the assistant creates, which keeps the real reach of the read-only permission small in practice. That is a practice, not a technical limit.
Not requested: permission to edit other people's Docs or Sheets, full Drive access, Gmail through Google's APIs, Contacts, or any permission to share files or manage who can see them. The assistant has no tool that shares files or sends email through Google.
The data accessed can include event titles, times, locations, descriptions and attendee names, and the names and text of files that John shares with the account.
John can also write to the assistant by email at cosbyassistant@gmail.com. This mailbox is read over ordinary Gmail mail protocols (IMAP and SMTP) using an app password issued by Google for that mailbox, not through the Google APIs above. Only messages from addresses the operator has approved are processed; everything else is ignored. Replies go only to the person who wrote. The assistant does not send email on its own initiative. Email content is handled like conversation content in the sections below.
How the data is used
- Only to provide the features John asks for: answering questions, checking availability, preparing and editing events, documents and spreadsheets, and recording unfinished work in his project notes.
- Google user data is not sold, not used for advertising, and not used to develop, improve or train AI or machine-learning models.
- Google user data is passed to other services only as listed under "Who receives what", only to provide these features, and only with John's agreement: before the Google features are used, John is shown this policy and asked to confirm that he agrees to those transfers.
- The assistant will not send invitations, share files, delete material or make commitments to other people without John's clear approval of that specific action.
Accounts and credentials
The operator manages all accounts and enters all credentials. John does not hold them. Each credential is used with its own provider only:
| Credential | Issued by and managed by | Used with |
|---|---|---|
| Google sign-in approval for the assistant (a refresh token) and the app's client secret | Google; created by the operator when he signs the assistant's account in | Google's APIs (Calendar and Drive), by the assistant's Google tools |
| Gmail app password | Google, for the mailbox cosbyassistant@gmail.com; entered by the operator | Gmail's mail servers only, by the email connector |
| Anthropic API key | Anthropic, from an account the operator manages and pays for (a workspace set up for John Assist); entered by the operator | Anthropic's API only, to get the AI's answers |
| Cloudflare tunnel token and Cloudflare Access sign-in | Cloudflare; managed by the operator. Access lets only approved people sign in with their Google account. | Cloudflare only |
What keeps credentials out of the AI's prompts, out of what John sees, and away from unrelated services:
- The credentials are stored in restricted files on the computer that only the assistant's own service account and the computer's administrators can read; they are not included in the assistant's instructions or in the text sent to the AI.
- The AI has no tool that reads files, runs commands or browses the computer. It can only call a fixed set of functions (records, Scripture, documents, calendar, files), and those functions return results, never credentials. The Google functions were tested to confirm that their results and error messages contain no token or secret.
- Each credential is attached only to requests to its own provider. Web searches, Bible lookups and page reads are made without any credential.
- The operator searched the conversation records, project records, session database, supervisor logs, the files his maintenance tool can read, and the assistant's logs since they were last cleared, for the actual credential values, and found none. No system can guarantee this forever; if a credential is ever exposed it will be revoked and replaced.
Who receives what
| Service and its role | What it receives |
|---|---|
| Anthropic - the AI that writes the assistant's answers (via the API account the operator manages) | What John types or emails; text of files and attachments the assistant reads for a request; photos John attaches (a reduced copy); results the assistant gets back from Google for a request (for example event details, availability, or document text); and the assistant's standing instructions. |
| Google - the assistant's Calendar, Drive, Docs, Sheets and mailbox | The requests the assistant makes and the content it creates there. |
| Cloudflare - reaches the chat page securely and limits it to approved people | The chat page traffic (messages and replies) passes through Cloudflare's network, and Cloudflare Access sees the Google account used to sign in. |
| Web search and page-reading services - public information | Search words the assistant writes, addresses of pages it opens, and the computer's network address. The assistant is instructed to use general words only and never to put private Google or email content into a search; this is an instruction to the AI, not a technical block. |
| Bible text services - exact Scripture quotations | The passage reference and translation requested, and the computer's network address. |
| The operator's maintenance tool and its providers - see "Maintenance" below | File names, sizes, checksums, technical logs and status information, which can include conversation titles and short log snippets. |
Anthropic receives conversation and Google content in order to answer John; the other services receive only the limited items shown. Nothing is sent to advertisers or data brokers. Under Anthropic's commercial terms, inputs and outputs are not used to train its models by default (see Anthropic's explanation), and Anthropic keeps data for a limited period under its own policies (see its retention page). The operator cannot delete data held by Anthropic, Cloudflare or other providers directly; their own policies apply.
Where data is stored
The assistant runs on a computer managed by the operator in Arizona, USA. On that computer:
- Credentials: in restricted files, as described above.
- Conversations, project notes and uploads: John's chat conversations, the project records the assistant keeps for him (including filed copies of uploads), and uploaded files are stored in the assistant's data folder. The assistant software also keeps its own session history of each conversation so it can remember earlier turns. If a conversation includes information the assistant read from Google, that information may appear in the conversation record, the session history and project notes it saves for John.
- Technical logs: the assistant software keeps rolling log files with technical events and short snippets (for example the first words of a message, the name of a tool used, and project titles). Logs roll over only when they reach a size limit, which can take weeks, and they are not edited item by item.
- Backup copies: before maintenance or changes, the operator takes manual copies of the settings and sometimes of the stored data (conversations, project records, uploads, and the session database) in a restricted folder on the same computer. These are not scheduled and are not deleted automatically. Some copies of settings contain credentials. As currently arranged, the computer's general encrypted backup to an external drive does not include the assistant's data folder. This is the present setup, not a promise; if it changes, this policy will be updated first.
- Documents, spreadsheets and events the assistant creates remain in the assistant's Google account, protected by Google.
Data is protected in transit by HTTPS and at rest by access restrictions on the computer. No system is perfectly secure.
Who can see it, and when
- John can see his own conversations, project records, uploads and files.
- The operator and the computer's administrators can technically read stored conversation records, project notes, uploads, session history, backup copies and logs because they manage the computer.
- Human access to Google user data follows Google's rules. A person reads John's Google data (calendar details, file contents, or conversation text that contains them) only: (1) after John has agreed to the person viewing specific items; (2) when necessary for security, meaning an actual abuse, attack or compromise (routine troubleshooting is not a security purpose and needs John's agreement to the specific items first); (3) when required by law; or (4) in aggregated, anonymised form for internal operations (none is done today). There is no general maintenance exception.
- Everyone else can see Google content only if John shares it with them in Google himself.
Maintenance
The operator maintains the assistant with an AI-assisted administration tool that runs on his own computer account. This tool is itself an AI service. It uses Anthropic's AI through the operator's own Anthropic sign-in (not the API key the assistant uses, and possibly under different privacy settings and terms), may use other AI providers for software-coding tasks (it has not been given John's content for these), keeps its own history and notes on the operator's computer (which the operator's general encrypted backup includes), and posts its reports to a private Discord server the operator owns. Whatever it reads is therefore processed by those services under their own terms.
Routine work (updates, backups, restarts, health checks, cleanup) is done using file names, sizes, counts, checksums, status information and technical logs. The tool is instructed not to open the content of John's conversations, documents or Google data, and it labels test content as a test. So far it has seen only: those technical items; conversation titles (which are the first words of a conversation); short log snippets; and the clearly labelled test items it created. If a title or log snippet happens to contain Google information, that snippet may be seen. Troubleshooting that needs the content of John's conversations, documents or Google data is done only after John agrees to the specific items; it is not covered by any general maintenance exception.
Your control, deletion and backup copies
- Stop access at any time: remove the assistant's access in the Google account's third-party access settings (myaccount.google.com/permissions for cosbyassistant@gmail.com), or stop sharing his calendar and files with the account at any time. John can also ask Mike (Mike@dandlpress.com) to disconnect the assistant's Google authorization; the operator then deletes the stored Google credentials.
- How to ask for deletion: email Mike@dandlpress.com from the address you use with the assistant and say what to delete: specific conversations, project records, uploads or files, or everything.
- What the operator then does (a documented procedure that has been tested on dummy records):
- Removes the requested conversations, project records (including the copies of uploads filed in them), uploads and generated files from the assistant's data folder.
- Deletes the assistant software's session history for those conversations and the stored copies of the AI's replies for them. To make sure deleted text does not stay readable inside the session database file, the operator briefly stops the assistant at a time arranged with John and compacts that database.
- Deletes the copies of those items inside the older backup folders. Whole-file copies of the session database in old backups cannot be edited item by item, so they are deleted entirely, and a fresh backup is made if one is needed.
- Records the deletion in a ledger that holds item IDs and project short names, not content. If a backup is ever restored, the operator re-applies the ledger so deleted items do not come back.
- Searches the assistant's folders for text from the deleted items and tells you what, if anything, remains.
- If you ask for everything to be deleted, or ask for logs to be cleared, the rolling logs are cleared as well, and the stored Google credentials are removed. Otherwise logs are not edited: they can hold short snippets (such as the first words of a message or a project title) until they roll over, which can take weeks.
- Google and providers: items in Google (events, files, documents) are deleted in Google by John, or by the operator at John's request, and Google's own trash and retention apply. Copies held by Anthropic, Cloudflare, Discord and other providers follow their own policies and cannot be deleted by the operator directly.
- Stored conversations and notes are otherwise kept until John or the operator deletes them. Google credentials are deleted when access is revoked or the service ends.
Children
John Assist is not directed to children and is not open to the public.
Changes and contact
If this policy changes, the new version will be posted on this page with a new date, and John will be told of material changes and asked to confirm again before Google data is used in a new way. Contact: Mike Pinch, Mike@dandlpress.com.
John Assist's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.