Your data stays yours.
Privacy notice for the personal WhatWhenWhy application. Updated October 21, 2026.
WhatWhenWhy, operated by Kanan Dume Ventura, is a private productivity workspace. This page explains the current application, including its optional Google Calendar and Google Tasks connections.
What is stored
Optional time logs record the activity, duration or clock interval, timezone, and the business/personal, billing, income, client and rate choices you enter. Calendar plans do not become worked time. Explicit session check-ins can create a linked actual-work record. Corrections update that session identity; potentially overlapping manual logs require your review, and older check-ins are not imported by guesswork. Each time entry keeps its chosen classification when a task or project is reclassified later. Reports contain reported time and clearly labelled current progress, not proof of payment or measured activity. Reviewed report snapshots retain the selected period, filters and source identities. Mutable work records keep private revision history. Subtasks have their own checkboxes and do not automatically complete their parent task.
The freeform Journal stores only entries you save. Images and video are uploaded to an owner-only private Supabase Storage bucket with multi-factor authentication required. Previews load only on request. Media files are private account storage, separate from password-encrypted secret notes. Journal and media data are excluded from the existing voice and ChatGPT connections. You may explicitly select their text and catalog records for a private project review download; the download does not grant a helper access to your account or include original media files. Native browser spelling checks use your browser settings; no spelling service is added by WhatWhenWhy. Archive actions are reversible. Native JSON exports include account records and the media catalog. The complete account ZIP also includes every cataloged original, including archived files, with integrity checks. Ordinary authenticated reads block retained secret-note snapshots. A complete export or recovery that needs those snapshots requires your existing vault password inside WhatWhenWhy; it is never saved in a package or intentionally logged. The exported package can include earlier plaintext after this explicit vault review, so keep the package private. Its reviewed recovery adds missing records in the same account without overwriting current records or reconnecting providers. Secret-note recovery still needs the existing vault and original password. Routine database-only backups do not include original media; an optional verified media package can be included in an encrypted operator backup.
Your account information, tasks, captures, writing, archive entries, preferences, and connected-calendar records are stored in the application's personal Supabase project. Account access requires a password and multi-factor authentication. This is not end-to-end encrypted storage: the application's server and authorized infrastructure operators can process stored data.
Milestones and result reports, notes, confirmation references, supporting links and their explicit task connections are stored as private native records. Calendar source words are saved when connected; original task context and report/link revisions remain in history after corrections, unlinking or a source record leaving the Calendar cache. Reports are self-reported, not independently verified payments or measured activity. Supporting links are not fetched automatically. Recording or correcting a result never completes a task, changes a deadline or edits a Google event; task completion requires its own explicit action. These records are included in private exports and relevant review packets only when you prepare them, not sent to an AI service automatically.
Your Google Calendar connection
Calendar access begins only after you approve Google's consent screen. Read access requests your calendar list and read-only event access. Calendar names, identifiers, and source settings are stored for selection. Event identifiers, titles, start and end times, all-day status, and synchronization metadata are imported only from calendars you enable. Event identity, organizer identifiers and recurring-occurrence identity let verified copies appear as one commitment while keeping each calendar record and link. Differing copies remain visible for review. Newly discovered sources start off. The integration does not request Gmail access or import email bodies.
Writing is a separate, optional connection requesting owned-event and free/busy permissions. Google's owned-event permission technically permits creating, editing, and deleting events on calendars you own. The editor supports eligible guest-free events, including events originally created in Google, with name, description, location, time, all-day, repeating-event and reminder controls where supported. You choose an owned, enabled calendar for each new event. Changing or deleting a repeating occurrence or series uses a separate review and acknowledgment. Guest changes and unsupported special event types are not offered.
Free/busy information is used to check scheduling conflicts. A write requires your preview and confirmation. A parallel plan changes only your event, not the conflicting event. Calendar data and derived availability are used to provide these visible calendar and planning features, not advertising, profiling for marketing, or unrelated AI training.
Your optional Google Tasks connection
Google Tasks access begins only after you approve Google's separate consent screen. It requests the read-only Tasks scope. WhatWhenWhy cannot create, edit, complete, move or delete a Google Task. After connecting, only task-list names are discovered and every list starts disabled. Task titles and source details are read only after you enable a list and press Sync.
Enabled Google Tasks are stored as a read-only projection, separate from native WhatWhenWhy tasks. The projection can preserve the original title, notes, status, hierarchy, source links, assignment provenance, Google version and update information. Google's date is shown as a scheduled day, not treated as a hard deadline or timed appointment. WhatWhenWhy does not turn an imported record into a new commitment automatically.
Credentials and protection
Google refresh credentials are encrypted on the server and are not included in browser-readable records or app exports. Calendar and Tasks credentials remain separate. The server uses them only for the Google connection and sources you enable. Application access controls restrict records to their owner; Google connection and synchronization operations require the existing multi-factor session. No protection eliminates every security risk.
Notes have three owner-chosen privacy levels. Regular notes appear in normal note views and permitted helper reads. Private notes are omitted from default note lists and recent-note requests, but remain available in an explicit private view and can be requested from an authorized helper. Secret-note words are encrypted in the database using a password that is not stored by WhatWhenWhy. The password must be typed into the first-party WWW page and must not be spoken or pasted into ChatGPT. A connected helper can receive secret content only after that WWW password check, through a single-use unlock that expires after five minutes.
Changing an existing note to secret protects its current live copy. An earlier revision, activity-history entry, downloaded export, connected-note snapshot or encrypted provider backup may already contain the earlier plaintext and can remain for its stated retention period. WhatWhenWhy shows this warning before conversion and does not claim retroactive erasure. Losing the secret-note password can make the encrypted current copy unrecoverable.
Optional private helper access
Talk to WWW offers a separate restricted API. A connection starts only after you review and approve it in WWW using your existing multi-factor session. You choose task, Capture-note and Notebook reading, or a narrower requested combination. Reading uses your saved timezone; it is not a new Google connection. Regular notes can be listed without search words. Private notes require an explicit request. Secret notes follow the separate one-time password-unlock rule above. Goals, project history and other unrelated records are not part of this release's read scope.
A helper grant lasts at most 15 minutes, can expire earlier with your signed-in session, and has no automatic refresh. Settings lets you inspect and revoke API access without deleting records or changing Google consent. Exact-word captures are saved as review inbox entries, not automatically turned into tasks, deadlines, completion or Calendar changes. Ordinary capture history and backup retention still apply.
The private helper keeps its short-lived bearer credential in process memory, not in chat, public pages or model inputs. The server stores a hash of that credential and authorization metadata. Requests use fixed API paths; search words and dates stay in request bodies rather than URL query strings. Application code does not log private request content or raw database errors. Narrow database privacy controls reduce routine query diagnostics for these API connections, but provider infrastructure, privileged instrumentation, fatal errors, stored records and backups remain separate risks. This is not a zero-retention or end-to-end-encryption guarantee.
The restricted helper API does not by itself call OpenAI, share ChatGPT conversation history or add background AI monitoring. If you explicitly ask a connected assistant to read WWW, the returned task or Calendar content is provided to that assistant for your request and is subject to that assistant service's own policies. Separate optional connections are described below.
Optional in-app voice, when enabled
Talk to WWW's in-app voice panel is separate from your ChatGPT account and conversation history. It requires your existing WWW sign-in and multi-factor verification, plus explicit consent for a temporary API grant of at most 15 minutes. Voice can read tasks, Today, your saved timezone, enabled cached My Time events, linked goals, projects and outcomes, and a bounded list of recent regular Capture and Notebook notes when you explicitly ask for notes. My Time is a saved WWW projection, not a fresh Google availability check. Private and secret notes and Notebook bodies are not available through voice. You may also approve review-only Capture access for this session, or leave it off. Spoken requests to create or change something may produce a reviewable next-step card, but the model cannot apply that action. Existing WWW task, Calendar, purpose, result and Capture review screens remain the only places where you can separately confirm a change.
Recording starts only when you press Start microphone. Pressing Stop & send, or reaching the 30-second recording limit, submits the bounded clip for automatic transcription. OpenAI receives your audio, transcript, recent panel conversation and the task, cached My Time, linked-plan or regular-note information needed for the answer you requested. Automatic transcription and replies can be inaccurate. Replies use an AI-generated voice. You can type or use keyboard dictation instead of recording, mute spoken replies, or stop a request. Keyboard dictation may be processed by your device or keyboard provider under its own settings.
The panel does not save audio or a conversation automatically. Only words you explicitly confirm with Save these words to Capture are stored as a native Capture, with the existing private history and backup retention described below. If a save is interrupted, retry the same save without changing its words or check Capture first, to avoid duplicates. Its temporary access credential and conversation remain in browser memory. Closing the panel, signing out or hiding the page stops recording, clears the panel and attempts to revoke that panel's API grant; if revocation cannot be confirmed, the grant still expires within 15 minutes and can be reviewed in Settings. Closing cannot undo a save already sent. Requests already sent to a provider cannot be recalled by closing the panel. Application code disables AI SDK telemetry, requests Responses API storage off and does not intentionally log audio, transcripts, record text or authorization headers. This is not a zero-retention guarantee: OpenAI abuse-monitoring logs, hosting metadata, privileged instrumentation and backups are separate risks. See OpenAI's data controls.
Infrastructure providers
Supabase processes account and application data. Google processes Calendar and Tasks requests and consent. Vercel serves the website and may process ordinary request metadata. Encrypted database backups are retained in private GitHub Actions storage for up to 90 days. These providers process information needed to operate the service under their own applicable policies.
WhatWhenWhy does not sell personal or Google data, send it to advertising platforms or data brokers, or use it for personalized advertising. The app contains no analytics trackers. External AI calls occur only through the optional, consented voice feature described above, not background monitoring. This integration does not feed your content to APORIA or SPREAD systems. Data may be accessed by authorized operators when necessary to maintain or secure the application, investigate a problem, or meet legal obligations; it is not a public data feed.
WhatWhenWhy's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Your choices and retention
Use Settings to choose Calendar sources and Google Task lists, remove Calendar write access, or disconnect either read connection. Disconnect removes the corresponding saved credential and connected projection from the live app and attempts Google-side revocation. You can also remove WhatWhenWhy in your Google Account's third-party connections. Google revocation can affect other clients of this same Google project for your account. Disconnecting does not delete events from Google Calendar or tasks from Google Tasks. Information already included in an encrypted backup may remain until that backup expires.
My trail retains a private history of saved task, list, capture, library, task-session link and decision-note changes, including earlier and deleted text. Deleting a working record does not erase that history. History begins with an explicitly labeled current-state baseline, not a reconstruction of earlier behavior. Submitted decisions, observations and saved AI reviews remain distinct from recorded changes. Unsent drafts and keystrokes are not recorded; do not put passwords or credentials into notes. Contact the operator below to request removal of retained history. Information in encrypted backups can remain until those backups expire.
Settings offers a plaintext JSON export of native lists, tasks, captures, writing, revisions and history, plus a task CSV export. My trail can also prepare a private review packet for you to share with an AI service you choose. The application does not send that packet automatically or run scheduled external AI reviews. Downloaded packets can contain sensitive saved words and deleted versions; review and protect them yourself. These exports do not include Google credentials or a Google Calendar event export.
What this is for stores your private goals, projects, task-purpose choices and reviewed activation explanations. Earlier names, reasons and revisions remain in purpose history. New linked task sessions can retain the purpose recorded when they were linked; existing sessions are not assigned invented original reasons. Purpose records and session-purpose snapshots are included in the JSON export and encrypted database backups. They are not copied into Google event descriptions or shared with an AI service automatically. Retiring a purpose or changing an association does not erase its saved history.
Connect the dots stores your explicitly chosen connections between Notebook entries and goals, projects, tasks or individual Calendar sessions/events. The words saved when first connected and the connection/unlink history remain private native records even if a current entry or plan is later removed. Reconnecting keeps that first snapshot; it does not silently replace it with newer words. These connections and snapshots are included in native JSON exports and private review packets. A project packet includes its explicitly connected entries and their saved revisions, including historical connections, but not those entries' unrelated connections. Connections do not activate, schedule, complete or edit a plan, and nothing is copied to Google or sent to an AI service automatically.
Learn what helps stores only feedback you explicitly review and confirm: your response, optional notes, the task and observation names when first saved, and a fingerprint of the supporting evidence. Unchanged observations with saved feedback stay out of the default review; changed supporting facts can bring them back. Show again and corrections add history rather than erasing earlier feedback. Feedback does not complete a task, change a deadline or apply a Calendar adjustment. Original feedback can remain after a working task is removed and is included in encrypted backups, native JSON exports and relevant owner-prepared review packets. Drafts are not recorded. Feedback is not sent to an external AI service or used for background profiling.
Try what works saves only experiments you review and confirm: your exact hypothesis, what would make it useful, a proposed session length, task and feedback identities, a snapshot of the original feedback and recent saved session reports, and your later assessments and notes. Corrections append history. These are intentions and self-reports, not applied preferences, proof of completed work or evidence of causation. They do not change tasks, Calendar events, links or deadlines. History can remain after the working task is removed. Experiments and their retained baseline/history are included in encrypted backups, native JSON exports and relevant owner-prepared review packets. Nothing is sent to external AI or monitored in the background; unsaved drafts are not recorded.
Use what I learn stores only choices you review and confirm: experiment-to-session connections, optional reports of whether you tried an approach, exact notes, and task-specific session-duration defaults. Each connection retains the chosen experiment and session context; each approach report refers to a particular saved check-in, not measured adherence or proof of causation. Unlinking, corrections and clearing defaults append history. Snapshots can remain after a task, session or check-in context changes. Defaults are optional inputs to a future time search, never automatic bookings or changes to estimates, deadlines, rest or capacity. This history is included in encrypted backups, native JSON exports and relevant private review packets you prepare. No external AI, background monitoring or new Google access is introduced.
My Compass stores only your saved purpose, dimensions of freedom, reviewed goal relationships and optional experiential reflections. Purpose and relationship changes retain history; corrections to reflections append a new record. Nothing in Compass activates or schedules work automatically. Find searches owner-scoped records; private notes require an explicit protected scope and secret words remain outside search. Retained task history can be recovered only as a new Inbox action after your review, with an immutable provenance receipt.
For access, correction, removal, or privacy questions, contact kanandumeventura@gmail.com. If the data practices change, this notice will be updated.
About WhatWhenWhy | Open your workspace
Private ChatGPT connection
When you explicitly connect your WWW account after its existing MFA, ChatGPT may read only the record types you select. This release can list recent regular notes and can read explicitly requested private notes. Secret notes require the separate WWW-only one-time unlock. It cannot change tasks, deadlines, Calendar events or account permissions. The connection ends within 24 hours, on WWW sign-out or when you revoke it in Settings. Authorization and token records are encrypted in the private bridge store. Hosting providers may retain limited request metadata under their own policies; application logs do not intentionally include record text, passwords, authorization codes or tokens.