How to Revoke Kindroid's Google Calendar Access

1. Open Google's access controls

Expected outcome: you are inspecting linked apps for the Google account that supplied Kindroid's calendar.

Follow the linked-apps link in Google's official connection-management instructions. Check the signed-in email before changing anything. Select Access to your Google Account, then inspect a candidate app using See details.

Do not use the separate sign-in-removal flow as a substitute. If several Google accounts are signed in, inspect them separately without granting any new permissions. Keep account identifiers private.

2. Match the integration and exact Calendar scope

Expected outcome: the app identity, connected account and granted Calendar permission match the integration you intend to revoke.

Kindroid's calendar guide documents a Nylas authorization flow and read-only access. That does not establish the display name in your Google account. Inspect the app identity and exact permission wording actually shown; record a scope identifier if Google displays one, without guessing it from this article.

A familiar name alone is insufficient, especially if you use other calendar integrations. If the grant includes broader access or several services, read what removing the whole grant affects. Stop for clarification if you cannot confidently connect it to Kindroid; do not revoke every Nylas-related or Calendar-enabled entry.

3. Remove only the matching access grant

Expected outcome: Google confirms removal for the connection whose Calendar access you identified.

Within the matching app's access details, choose Remove access, then Confirm, as Google's current instructions specify. Read the confirmation carefully before accepting. Removing that grant can affect other features relying on it; this is not a promise of a Calendar-only permission switch.

Leave unrelated apps and sign-in connections unchanged. Kindroid mentions disconnection through settings, but the checked guide does not give a precise disconnect-button path. This workflow therefore uses Google's documented controls, not an invented Kindroid button.

4. Reopen Google settings and verify

Expected outcome: the matching Calendar access grant is no longer present when you inspect the same Google account again.

Navigate away, return to linked apps, and inspect the same account and candidate connection. Check specifically for the Calendar permission you recorded. An app can have multiple link types, so its name remaining somewhere in the list is not by itself a failed revocation.

If the access still appears, refresh and inspect again; mark the outcome unresolved if it persists. Do not reconnect to test. A chat reply claiming calendar blindness is not permission evidence, and recollection of an old appointment is not proof of fresh access.

Separate withdrawn access from retained information

Revocation addresses the current Google permission, not deletion of information already obtained.

The Kindroid privacy policy's retention section says chat conversations and generated media remain until deletion of the relevant AI or account, with broader retention exceptions for purposes such as legal obligations and disputes. It does not establish a calendar-specific purge deadline after Google revocation.

Treat event details already discussed or incorporated into context as a separate cleanup question. Ask Kindroid what remains in conversation history, memory and integration records, and how deletion requests are handled. Request clarification about Nylas-held records too; these sources do not verify their deletion. No anonymity or complete-erasure guarantee follows from removing access.

Troubleshoot without reopening access

Stop when the connection cannot be identified or the permission state remains contradictory.

Missing entry: check the original Google account and any access filters first. Do not authorize again to make an entry appear. Multiple plausible grants: ask support to help identify the matching integration. Share only redacted app and permission labels, never event contents, passwords or authorization tokens.

If you need scheduling help meanwhile, use Google Calendar directly and keep the integration disconnected. Sharing a generic availability summary manually is an alternative, but anything you type into Kindroid becomes a separate disclosure. Exclude appointments, addresses and other people's details you do not want retained.

Check timeout, privacy and payment separately

Neither inactivity nor a subscription change replaces verification of the Google permission.

Kindroid documents automatic disconnection after 14 days without an AI actively recalling from a nonempty calendar. The guide does not establish that this removes Google's authorization grant. Do not wait for that timeout when you want to withdraw access now.

Do not buy an upgrade to troubleshoot revocation. Treat subscription renewal and cancellation as separate tasks: inspect your existing billing channel if you also want to stop paying. Do not infer cancellation, a refund, or deletion from a permission change.

Completion checklist

Finish with a verified permission result and a separate list of unresolved retention or billing questions.

Privately note the date, account checked, matching grant and reopened verification result, without copying calendar contents. Keep access removal, historical-data cleanup and subscription status as three separate outcomes. Leave any uncertain outcome unresolved rather than treating silence from the AI as success.

Frequently asked questions