Privacy policy
Effective: 25 October 2026 · Applies to the private Usertea Personal Automation integration
Usertea Personal Automation ("the application") is a private, self-hosted automation operated for a single authorized Google account. It connects Gmail to an n8n workflow and, if enabled by the owner, sends selected reports to configured Telegram chats or topics. This public website explains that processing; it is not a Google sign-in page.
1. Who operates the application
The private owner of the Usertea automation operates the application and controls its configuration. For privacy, access, or deletion requests, contact oauth@usertea.com. The website itself does not provide public account registration.
2. Google data the application accesses
With the account owner's OAuth authorization, the application accesses Gmail messages matching configured queries (for example, owner-generated GPT-TG reports and selected task notifications). Depending on each matching message, processed data can include subject, sender and recipient addresses, message ID, labels, timestamps, plain-text report body, and relevant message links. Google OAuth credential material is managed within the self-hosted n8n installation and is not collected by this public website.
3. How Gmail data is used
- Identify configured notification and report emails.
- Extract summaries or full report text based on owner-selected delivery settings.
- Route eligible reports to the owner's designated Telegram chat or topic.
- Record identifiers of successfully delivered messages or message parts to avoid duplicate notifications.
- Diagnose failed deliveries and operate or secure the integration.
The Gmail-to-Telegram workflow is not intended to modify, archive, delete or send Gmail messages. Gmail data is not used for targeted advertising, profiling, or sale.
4. Sharing with other services
When Telegram delivery is enabled, the selected message text and necessary routing identifiers are sent to Telegram so they can appear in the configured chat or topic. Google provides the Gmail and OAuth services. The public information website may be served by its hosting provider, which can process standard technical request information such as IP address and browser headers. Other providers may receive data only as needed for the services described here or as legally required.
5. Storage and retention
The self-hosted n8n environment stores workflow configurations, encrypted OAuth credentials, report delivery identifiers, and configured Telegram routes. Execution logs or operational metadata may also exist subject to the installation's settings. Stored records remain until removed through maintenance, deletion or account revocation processes; no automatic fixed deletion interval is promised. Telegram messages remain subject to Telegram's own settings and retention controls. The public website does not set analytics or advertising cookies.
6. Security and access
The automation runs in a private n8n installation. Access to workflow configuration and stored credentials is restricted to authorized operators; Gmail OAuth tokens are managed by n8n. Network connections use HTTPS where supported. No security measure can guarantee absolute protection.
7. Your choices and deletion
The Google account owner can revoke the application's access at Google Account connections. This stops future authorized Gmail API access; it does not by itself remove already forwarded Telegram messages or previously retained delivery records. To request deletion of stored application data, contact the operator using the address above. Telegram message removal may also require deletion in Telegram.
8. Google API user data policy
The application's use and transfer of information received from Google APIs is intended to adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google account information is used only for the functions disclosed here.
9. Changes to this policy
This policy may be updated if data processing, storage or sharing practices change. The effective date above will be revised when changes are published.