Русский 
English Last updated: 1 September 2026
1. Scope and contact
WPG n8n is an internal application operated by the WPG team for content preparation, review and publication. It is used by the project owner and authorised WPG team members.
This policy describes the application’s current content workflows and the intended data practices for its planned Google Search Console integration. Search Console processing will begin only after the integration has been implemented and the Google account owner has authorised access.
For questions or requests about your data, contact white.ads.bot@gmail.com
2. Data the application accesses
Google Sheets and Google Drive
Within the permissions granted by the Google account owner, WPG n8n accesses:
– Content in spreadsheets selected by the WPG team: topics, descriptions, draft posts, image prompts, editorial comments, versions, statuses and dates.
– Spreadsheet names and identifiers, sheet and column names, and row numbers. Google Drive metadata may be used to locate and select spreadsheets during setup.
– OAuth access and refresh tokens needed to make authorised Google API requests. The application does not receive your Google account password.
Google Search Console – planned integration
Once the integration is implemented and authorised, WPG n8n will use read-only access to Search Console properties selected for WPG’s internal SEO reporting. Depending on the report, the data retrieved may include:
– Property identifiers, website URLs and the connected account’s property permission levels.
– Search queries, page URLs, reporting dates, countries, device categories and search appearance categories.
– Search performance metrics, including clicks, impressions, click-through rate and average position.
The integration will retrieve data for internal analysis. It will not add or remove Search Console properties, submit or delete sitemaps, or otherwise modify Search Console settings.
Telegram and operational data
For content workflows, the application processes bot commands, suggested topics, replies, editorial feedback, user and chat identifiers, message identifiers and image file identifiers. These data connect a team member’s action to the relevant topic or post version.
The n8n server may also store API responses, workflow results and error details in execution history. This history may contain Google spreadsheet data, Telegram messages and, when the Search Console integration is enabled, data used for SEO reports.
3. How data are used
Google Sheets data are used to maintain the content plan, generate and revise materials, manage reviews, store versions, record selected publication dates and publish approved content.
Google Search Console data will be used only to prepare internal SEO reports and monitor the organic search performance of websites managed by WPG. They will not be used as input for AI content generation or sent to Telegram.
Operational data are used to run the application, investigate errors and protect the service. Google data are used only for the functions disclosed on the [application page](https://wpgads.com/n8n/) and in this policy.
4. Where data are processed and shared
Google: Google Sheets stores the team’s content records and, if report storage is enabled, designated internal SEO reports. Google Drive provides necessary file metadata. Google Search Console will provide the authorised search performance data when that integration is enabled.
OpenAI API: The content workflow sends the topics, draft text, editorial comments and image prompts needed to generate or revise materials. These requests may contain content read from the selected Google Sheets. Google OAuth credentials are not included in model prompts. Google Search Console data and SEO reports are not sent to OpenAI or other AI providers.
Telegram: Content topics, drafts, images and service notifications are sent to the team’s review group and can be read by its members. Approved text and images may be published to the selected public channel and become accessible to its readers. Google Search Console data and SEO reports are not sent to Telegram or published by the bot.
WPG’s n8n server: The server processes API requests and workflow results, stores connection credentials and may retain execution history. Authorised WPG team members can access internal SEO reports through the reporting locations configured for that purpose, such as designated Google Sheets.
Access to specific spreadsheets, reports and review materials is provided to team members with the data owner’s permission. Additional access may be necessary to investigate security issues or comply with applicable law. Connected service providers process the data they receive under their applicable terms and privacy policies.
5. Google data and Limited Use
WPG n8n commits to complying with the Google API Services User Data Policy, including its Limited Use requirements, in its use and transfer of information received from Google APIs.
The WPG team does not sell Google user data, use it for personalised advertising or transfer it for training general-purpose AI models. Transfers to the OpenAI API in the content workflow are for fulfilling the specific content request. Search Console data remain within the internal SEO reporting workflow described above.
The application requests the permissions needed for implemented functions. Planned integrations will not request additional Google permissions before they are ready to use. New purposes or transfers require updated disclosures and any necessary consent before processing begins.
6. Storage, retention and protection
Content plans, post versions and any enabled report records are stored in the designated Google Sheets. Connection credentials and retained execution history are stored on the n8n server. Messages and images sent to Telegram are also stored by Telegram.
Data are retained for as long as needed to maintain the content plan, work with versions, produce internal SEO reports and diagnose operational issues. The contents and retention period of execution history depend on the n8n server’s settings. Authorised team members can remove working records, and requests to delete data controlled by WPG can be sent to the contact address above.
Access to application settings, credentials and internal records is limited to authorised team members. Requests to Google APIs, the OpenAI API and the Telegram Bot API use HTTPS. Connection tokens are kept in n8n credentials and are not intended for inclusion in published content.
Internal SEO reports are kept separate from the data inputs used for AI generation and Telegram content delivery.
7. Revoking access and requesting changes or deletion
The Google account owner can revoke WPG n8n’s access through Google Account connections. Revocation stops further authorised access to the affected Google services.
Revoking access does not automatically delete data already stored in spreadsheets, execution history, Telegram messages or published posts. To request access to, correction of or deletion of data controlled by WPG, contact white.ads.bot@gmail.com. We may ask you to verify that you are entitled to make the request.
Deletion within third-party services is subject to the available controls and the services’ applicable policies. Previously published content may remain in copies held by readers, including forwarded messages.
8. Changes to this policy
The current policy is published on this page. If Google data use or sharing practices change, the WPG team will notify affected users and obtain any required consent before using their data for the new purpose.