1. Who operates tasksGPT?
The app and this informational site are published by Ours Agile (France, SIREN 911 724 169). For privacy inquiries, contact contact@ours-agile.com.
This policy describes the Ours Agile-operated instance and this public website. People hosting their own copy are responsible for their own data practices and privacy notices.
2. What Google data is accessed?
With the account holder's authorization, tasksGPT accesses basic Google identity information: account identifier, email address and display name. It also requests the Google Tasks OAuth scope https://www.googleapis.com/auth/tasks, which permits reading and changing Google Tasks data.
Requested task information may include list names and identifiers, titles, notes, due dates, status, positions, and parent–subtask relationships. The connector does not request access to Gmail, Google Drive, Google Calendar or Contacts. Visitors to this informational website do not sign in to Google.
3. Why is the data used?
Identity data verifies that the connecting Google account is authorized. Google Tasks information is used to perform requested task features, including reading lists and tasks, creating or editing tasks, creating subtasks, moving and reordering items, and completing or reopening tasks.
Changes are sent to Google Tasks only when a user requests the corresponding action. Safeguards check identities, task hierarchies and possible duplicates, but cannot guarantee that every action will be free of errors. Google user data is not used for advertising, profiling or sale.
4. Where is information stored?
OAuth credentials and account identity are handled by the Cloudflare-hosted Worker and its OAuth provider using Cloudflare-managed storage, including access and refresh tokens needed for authorized access. Short-lived OAuth flow state is stored in Cloudflare KV. Google Tasks records are fetched when tools are called; the current implementation does not maintain a separate long-term database of copied task lists.
Authorization records may remain in the deployed instance until the connection is revoked or the relevant records are deleted. Revoking a grant blocks future use of that authorization but does not automatically erase data already processed by other providers or captured in diagnostic logs.
Cloudflare may process technical logs under the deployment's settings. Error diagnostics may contain service-response details and should be handled as potentially sensitive. This informational website has no custom analytics scripts, advertising trackers, forms or tracking cookies; web hosts may still collect routine access logs.
5. Which other services are involved?
- Google authenticates the user and hosts their tasks.
- Cloudflare runs the MCP Worker and provides authorization-related storage.
- ChatGPT / OpenAI, when connected by the user, may receive the instructions sent to the connector and task data returned by its tools, subject to that platform's own terms and privacy practices.
- GitLab hosts the publicly available source code and may host this informational website.
Google user data is processed only to provide the requested features and related security operations, not sold or shared for targeted advertising. Independent deployments may use different service providers.
6. How can access be revoked or data deleted?
Only authorize a self-hosted connector that you trust. You can revoke a Google grant through Google Account third-party connections. You can also disconnect tasksGPT from ChatGPT or delete an instance that you operate.
For access, correction or deletion requests about the Ours Agile-operated instance, email contact@ours-agile.com. We can assess and process requests about data held by this instance. Data independently held by Google, Cloudflare or OpenAI may need to be managed using those providers' controls. Revoking OAuth access does not delete the original tasks in Google Tasks.
7. How is the instance secured?
The Ours Agile-operated instance restricts logins to a configured Google account email. Its public endpoints use HTTPS and its OAuth client secrets are stored in Cloudflare secrets rather than the public code repository. No online service is entirely risk-free; only authorize instances you control or trust.
8. Policy changes
We may update this policy when the software's capabilities, providers or handling of data change. The date above reflects the most recent version. Material changes to the use of Google user data require appropriate notice before new processing.