Last updated: 12 November 2026
This policy explains how WanderHackr Automation handles Google data in its editorial automation. The application is operated for WanderHackr’s owner and authorized editors to research travel topics and prepare content for review.
What the application accesses
When an operator connects Google Search Console, the application can access the Search Console properties available to that Google account and performance information such as page URLs, search queries, dates, clicks, impressions, click-through rates and average positions. The installed connector requests Search Console viewing and management permissions; the current editorial workflow uses property listings and performance queries.
How the data is used
Performance information helps identify editorial opportunities, review existing coverage and prepare internal recommendations. Search Console statistics are analytical inputs, not guarantees of demand, rankings or future traffic. Content is prepared in WordPress for editorial review.
Processing and sharing
Data is processed in the operator-controlled automation infrastructure, including n8n and the editorial service. Selected search queries, page URLs and performance metrics may be sent to the AI processing services used by the editorial workflow, including the OpenAI API, to support topic planning and content analysis. We do not sell Google data or use it for targeted advertising.
Our use and transfer of Google API data is limited to the editorial functions described here and is subject to the Google API Services User Data Policy, including its Limited Use requirements.
Storage and security
Performance snapshots and editorial records are stored in the operator’s automation systems and may be included in backups. Access is controlled through infrastructure and application accounts. OAuth credentials are managed by the automation platform and are not published in articles. Stored records remain until the operator deletes them; backup copies remain until those copies are replaced or deleted.
Disconnecting and deleting data
You can revoke the application’s Google access through your Google Account connections. Revoking access stops subsequent authorized access but does not automatically erase records already stored by the automation. To request deletion of stored Google-derived records, contact wanderhackr@gmail.com. Requests concerning backup copies are handled as part of the operator’s backup process.
Contact and updates
For questions about WanderHackr Automation or this policy, email wanderhackr@gmail.com. Material changes to the application’s Google data practices will be reflected in this policy.