Effective date: 30 October 2026
Who operates this integration
KOR.AI KEM Personal Email is operated by Lyndon Selby for personal use within the private KOR.AI environment. This policy covers the Gmail integration, not other KOR.AI services or the website's contact form.
Contact: lyndon.selby@gmail.com
Google data accessed and why
With your Google authorization, KEM can access email content and mailbox information through Gmail's read-only and compose permissions. Depending on the task, this includes message bodies, sender and recipient addresses, subjects, dates, headers, threads, labels, attachments, and drafts. The permissions are broader than access to messages individually selected in Gmail.
KEM uses this information to search and read email, review threads, summarize retrieved messages, and create and review drafts. Retrieved raw messages can include attachments; local tools also support attachment handling. Drafts can contain text, recipients and attachments supplied for the task. Approved draft uploads store an unsent draft in Gmail.
The compose permission permits sending at Google's level. KEM currently keeps sending disabled through its application controls and does not automatically reply. The current Gmail integration does not apply labels, archive, move or delete messages.
Processing, storage and credentials
KEM's email tools run on the founder's Mac, and its assistant is configured to use a local model. Data returned by those tools can enter the assistant conversation. Fetched raw messages and metadata, local drafts, follow-up records, operation receipts and conversation history may persist locally. This is not a promise that all data remains only on the Mac.
The active Google OAuth credentials, including renewable tokens, are stored in macOS Keychain. KEM uses OAuth rather than asking for your Gmail password. Keychain protects credentials; it does not establish that all saved email files or conversations have the same protection.
Discord and other exposure
The approved remote email interface is the founder's private one-to-one Discord DM with KEM. Message excerpts, retrieved content, summaries, draft content and related conversation information included in that DM are sent to Discord and are subject to Discord's storage, access and deletion practices. Discord is a separate service, not local-only storage.
The email tools restrict this interface to the approved founder DM and exclude shared server and group channels. Those application restrictions do not eliminate risks from access to the Mac, the Discord account, or copies subsequently made by the user. This website is an information page, not a Gmail login or mailbox upload service.
Retention and removal
There is no fixed automatic deletion period established for local email files, drafts, receipts or assistant conversation history. They can remain until the operator removes them. Gmail drafts remain in Gmail until deleted there. Discord messages and any copies or backups follow the relevant service and device retention practices; deleting one copy does not guarantee deletion of every copy.
To request removal of retained integration data, contact lyndon.selby@gmail.com and identify the relevant records without sending unnecessary email content. Removal must cover local saved files and conversation records separately from Gmail drafts and Discord messages. Revoking Google access does not erase data already retrieved.
Your control
You can stop requesting email operations, ask the operator to disable the KEM account connection, and remove the application's access through your Google Account's third-party connections settings at Google Account connections. Revocation stops future authorized access; it does not retract existing local or Discord copies. You can separately delete Gmail drafts in Gmail and manage your Discord messages and account settings in Discord.
Google user-data requirements and changes
Google API Services User Data Policy, including its Limited Use requirements, governs the integration's use of Google data: Google API Services User Data Policy. This policy describes the current personal email workflow; it is not a claim of Google verification or certification. Any new use, recipient or processing arrangement requires an updated disclosure and any necessary consent before it begins.