WhatWhenWhy Terms
Effective October 15, 2026. Terms for the private WhatWhenWhy workspace.
WhatWhenWhy is operated by Kanan Dume Ventura. It brings captures, tasks, time, writing, and an archive into one personal workspace. Access is limited to accounts the operator authorizes.
Your account
Use only an account you are authorized to use. Keep your password, authenticator, and recovery methods private. Do not try to bypass access controls or view another person's private information.
Your content stays yours
You retain ownership of your content. The application and its service providers process it to provide the features you choose, maintain the service, and protect its security, as described in the Privacy notice. WhatWhenWhy does not sell your personal or Google data or use it for advertising, data brokerage, or unrelated AI training.
Connecting Google Calendar is your choice
Calendar access requires your approval on Google's consent screen. Read access and write access are separate. Newly discovered calendars start disabled; you choose which sources to read. Approving a connection does not itself create or move an event.
The current writing feature creates or moves one eligible, guest-free, non-recurring timed event created through WhatWhenWhy on one selected calendar you own. It requires a preview and confirmation. Event-name and description editing, deletion, guests, all-day changes, and recurring-series editing are not offered in this version.
Connecting Google Tasks is your choice
The Google Tasks connection is separate and read-only. You choose which task lists WhatWhenWhy may display. Imported records remain Google Tasks and are not automatically converted into native tasks, deadlines or Calendar events. WhatWhenWhy cannot create, edit, complete, move or delete Google Tasks through this connection.
A Google scheduled date is displayed as a scheduled day, not treated as proof of a hard deadline or an exact time. Review imported information before relying on it for a critical commitment.
Check each calendar change
Review the calendar, date, time zone, start, end, and overlap information before confirming. Daily Framework is visual time, not reserved availability. A deliberately confirmed parallel plan keeps the conflicting event unchanged. If availability cannot be checked, the application does not treat that as permission to write anyway.
Synchronization and provider responses may be delayed or unavailable. If a save result is uncertain, use the application's calendar-check step or check Google Calendar before repeating the change.
Disconnecting and keeping a copy
You can remove a saved Google connection in Settings or revoke WhatWhenWhy in your Google Account. Revocation can affect other clients in the same Google project for that account. Disconnecting does not delete events from Google Calendar or tasks from Google Tasks. Retention and backup limits are described in the Privacy notice.
Keep independent copies of important information. The application's native JSON and task CSV exports are plain text. They do not export Google credentials or provide a Google Calendar event backup. Protect any downloaded copies yourself.
Availability and changes
WhatWhenWhy depends on Google, Supabase, Vercel, and other infrastructure described in the Privacy notice. Features and availability can change. It is not an emergency service, and it should not be your only record of a critical commitment. Material changes to these terms or the application's data practices will be identified in updated notices before the revised terms are used.
Questions or removal requests
For access, correction, removal, or questions, contact kanandumeventura@gmail.com.