Privacy Policy
How Mahdi Crypto Automation accesses, uses, and protects information associated with its personal Google Tasks workflow.
Effective date: October 14, 2026
1. Project and contact
Mahdi Crypto Automation (“the project”) is a privately operated cryptocurrency monitoring and decision-support system, intended for use by its owner. The data contact is [email protected].
2. Information accessed
When the Google account owner grants permission, the project uses the Google Tasks API to access task lists and relevant tasks. Depending on the workflow, data may include task titles, notes, task identifiers, timestamps, completion status, and list identifiers. It also receives OAuth authentication credentials needed to maintain that authorized connection.
The project does not request access to Gmail messages, Google Drive files, or Google Contacts.
3. Why this information is used
Google Tasks information is used solely to coordinate the project’s automated workflows: publish structured inputs, retrieve AI-assisted decisions, validate their freshness and format, prevent duplicate processing, and mark successfully handled tasks as complete. Selected workflow data and processing outcomes may be recorded in the project’s database for reliability, auditing, and error diagnosis.
Google Tasks information is not used for advertising or sold to data brokers.
4. Storage and security
OAuth tokens are stored on the project’s restricted server outside public website directories, using operating-system file permissions that limit access to the project service account. Operational records may be stored in a PostgreSQL database, and relevant failures may be recorded in service logs. Access to these systems is restricted to the project operator.
No internet-connected system is completely risk-free, and no absolute security guarantee is made.
5. Service providers and disclosure
Google provides Tasks and OAuth services. Google’s Gemini features may participate in creating workflow decisions. Cloudflare hosts these public informational pages and may process standard web request data. Telegram is used to deliver selected operational notifications to the project owner. The project does not sell Google Tasks information or provide it to advertisers.
Operational messages sent through Telegram are limited to the information required for project reporting. Service providers may process data under their own applicable terms and privacy practices.
6. Retention and deletion
Information is kept as needed to run the workflow, maintain operational records, and investigate errors. The project does not promise a fixed automatic deletion period. The account owner may request deletion of stored workflow records or revocation of project access by contacting [email protected]. Removal of information from third-party services may also require using those services’ own controls.
7. Control of Google account access
The Google account owner can revoke OAuth access at any time using their Google Account connections settings. Revocation prevents further authorized Tasks API access until permission is granted again. Tasks already created in Google Tasks are managed through Google Tasks itself.
8. Cookies and site analytics
These informational pages do not intentionally set application tracking cookies or run advertising analytics. The hosting provider may process necessary network and security information when a page is visited.
9. Changes to this policy
This policy may be updated if the project’s data practices change. Any updated version will be posted at this URL with a revised effective date.
10. Questions
For privacy questions, access requests, or deletion requests: [email protected].