Kernel
Back to Kernel

Data controls

Disconnecting is not deleting.

These instructions explain the application’s separate controls, how to contact Simon Corcos for help, and which records may remain.

Last updated September 8, 2026

1. Disconnect to stop future imports

Use Kernel’s integration controls to disconnect Google or Slack first. You can also remove Kernel’s authorization through the provider’s account controls. Disconnecting stops the connection; it does not by itself erase information already imported into Kernel. Contact us if you cannot access these controls.

2. Separately delete imported copies

After disconnecting, use the separate delete-imported-data control for the integration, or contact us for help. Deleting imported copies alone does not disconnect an active integration, which can import data again. This cleanup does not promise removal of accepted tasks or events, task/time records, or audit history. Deleting Kernel’s imported copies does not delete the original emails, messages, or calendar events in Google or Slack.

3. Request account removal

Self-service account deletion is disabled. Email Simon Corcos at simoncorcos.ing@gmail.com with the account email and the scope of your request. Do not send passwords, API keys, or message contents. We may need to verify account ownership. The removal process disables access, revokes workspace API tokens, archives public booking links, stops integrations, and schedules provider-credential and imported Gmail/Slack cleanup. It retains the workspace and task/time/audit history; a later invitation to the same email can restore access to that workspace.

What may remain

A Google authorization history can retain the Google account identifier, workspace references, and connection timestamps/counts to manage authorization limits. Cleanup can run asynchronously, and backup expiration is not immediate. Account removal does not automatically expire all retained history. Contact us to discuss those records, backup limitations, the applicable retention arrangements, or a request that goes beyond imported-data cleanup. See the privacy notice for the wider data-handling context.