Task Manager Privacy Policy

Last updated: September 11, 2026

Task Manager is a personal task and calendar application. Its optional Gmail capture integration uses read-only Gmail access to detect messages delivered to a dedicated capture alias and selected by a dedicated Gmail label. Eligible messages create private Task Manager tasks automatically. It does not modify, move, delete, send, mark as read, or add or remove labels from Gmail messages.

Google data accessed

The integration accesses the authorized Gmail account address; Gmail label identifiers and names; mailbox history and watch state; and, for messages carrying the configured capture label, Gmail message and thread identifiers, history identifier, internal date, size, selected email headers, snippet, bounded MIME content, and attachment metadata. The selected headers may include From, To, Cc, Reply-To, Subject, Date, Message-ID, and Delivered-To. It may download attachment-backed plain text and supported PNG, JPEG, or WebP image attachments for private task creation. Other attachment types are not imported.

How the data is used

Google data is used only to identify newly received capture messages, recover messages missed by push delivery, prevent duplicate processing, and create the authorized user's private Task Manager task. The message subject becomes the task title. Plain-text message content, or the Gmail snippet when plain text is unavailable, becomes task notes. Gmail HTML is not rendered or copied into task notes. Supported images within the 5 MiB and 8-million-pixel hosted source-image limits are validated, normalized, integrity-checked, and stored through Task Manager's private attachment system. Images declared above the byte limit are rejected before download; downloaded image headers are checked against the pixel limit before normalization. A source exceeding either limit is not registered. Other failed attachments are not registered, and any transient staged object is removed through scheduled cleanup. The task is still created with a filename-only notice. Gmail notifications are treated as mailbox-change signals rather than email content, and Gmail remains the source and audit copy.

Server-side processing and storage

Gmail watch notifications pass through Google Cloud Pub/Sub to a private Supabase backend. Gmail API calls, intake processing, task conversion, and image normalization occur on that backend, not in the browser or static PWA. Raw Gmail intake records, Gmail provenance, conversion state, and OAuth credentials are not made available to the browser. Created tasks and successfully imported attachments synchronize to the authorized user's Task Manager clients as ordinary private task data.

The Google OAuth refresh token is encrypted with AES-256-GCM before database storage. The encryption key is held separately as a server-side secret. Short-lived access tokens are used in server memory. Access to Gmail integration tables is restricted from anonymous and normal authenticated clients, and authenticated Pub/Sub requests are validated before processing.

Retention

Validated intake records, server-only delivery-to-task associations, created tasks, imported private attachments, and encrypted Gmail connection state are retained until the integration owner requests their deletion or the associated Task Manager account data is deleted, subject to the application's normal task deletion and backup behavior. Temporary staged attachment objects are reused during bounded retries or removed through server-side cleanup. Short-lived OAuth authorization-session records are marked consumed and expired records are removed during a later authorization bootstrap. Revoking Google access stops future authorized Gmail API access but does not automatically delete records or tasks already stored by Task Manager.

Sharing and sale

Google user data is not sold, rented, used for advertising, or shared with other Task Manager users. It is processed only through the infrastructure providers needed to operate the integration: Google APIs and Google Cloud Pub/Sub for Gmail notifications, and Supabase for private backend processing and storage. The public Cloudflare Pages application does not receive Gmail OAuth tokens.

Your choices and deletion

You can stop future access by revoking Task Manager under your Google Account's third-party connections and by disabling the dedicated Gmail filter or label workflow. To request deletion of the stored Gmail connection, intake records, delivery associations, generated tasks, and imported attachments, email tyler.ktm373@gmail.com from the authorized account and identify the Task Manager Gmail integration. Deleting stored Task Manager data does not delete the original messages in Gmail.

Security and changes

Task Manager uses scoped OAuth authorization, encrypted refresh-token storage, authenticated push delivery, server-only secrets, database access restrictions, bounded processing, and idempotent records to reduce risk. No internet service can promise absolute security. This policy will be updated if the integration's data practices materially change.

Google API Services User Data Policy

Task Manager's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions or requests concerning this policy can be sent to tyler.ktm373@gmail.com.