Back to Kernel

Beta terms

A shared understanding.

These terms describe the private Kernel beta, operated by Simon Corcos. Access is limited to invited users.

Last updated September 8, 2026

Using Kernel

Kernel helps organize tasks, time, calendars, and connected inbox information. Application access is by invitation and uses a private workspace. Keep your sign-in account and API credentials secure. Only connect accounts and provide information you are authorized to use, including where an employer or other organization controls an account.

Responsible use

Do not use Kernel to access another person’s workspace without permission, bypass access restrictions, distribute harmful content, or interfere with the service or its providers. You remain responsible for the information you submit and the actions you authorize. Use must respect applicable law, other people’s rights, and the terms of connected services.

Connections and AI suggestions

Optional connections grant the permissions shown during authorization. Calendar features can change provider events; Gmail access is read-only. AI suggestions may be incomplete or wrong. Review suggestions, schedules, recipients, and actions before relying on them. Connected services have their own terms and availability. The privacy notice explains data handling, including AI processing and updates to linked tasks.

Beta availability

A beta can change, experience interruptions, or contain errors. Features and access may be limited, changed, or suspended for maintenance, security, abuse prevention, or service changes. Do not rely on Kernel as the only record of critical information or as a guarantee that an external action completed.

Leaving the beta and getting help

You can stop using Kernel and disconnect integrations. Account removal is operator-assisted; it is distinct from disconnecting a service or deleting imported copies. Some history may remain as explained in the deletion instructions. Questions about access, these terms, or a requested account removal can be sent to Simon Corcos at simoncorcos.ing@gmail.com.