Privacy policy
How apoc-google handles Google user data.
Who runs it
apoc-google is developed and operated by Austin Williamson, an individual based in Las Vegas, Nevada. It is a personal tool. Its only user is the developer, acting for his own Google accounts and for client accounts he has been granted access to administer.
What it accesses
The application requests three Google API scopes, and no others.
- Google Ads API adwords
- Campaign, ad group, keyword and spend data, plus account configuration, for Ads accounts the user administers. Read-only in practice: the application issues no write operation against an Ads account.
- Google Analytics Data API analytics.readonly
- Aggregated traffic and conversion reports for GA4 properties the user administers.
- YouTube Data API youtube.upload
- Uploading video files to channels the user manages. Uploads are created as unlisted; the application does not read comments, subscribers or viewing history.
It does not access Gmail, Contacts, Drive, Calendar, Photos or any other Google service.
How the data is used
To build reports about advertising spend, website traffic and lead outcomes for the accounts above, and to deliver video uploads to those channels. Nothing else. The data is not used to advertise to anyone, is not combined with data about other people, and is not used to train or improve any machine-learning or artificial-intelligence model.
Where it is stored
Authorization tokens are kept in a local configuration file on the developer's own computer, outside source control. Report data pulled from Google is cached on that same computer alongside the reports it produces. The application runs no server of its own and has no user accounts or database of visitors.
Sharing
Google user data is not sold, rented or transferred to any third party. Reports derived from it are shared only with the client whose account the data came from.
apoc-google's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and revocation
Access continues until it is revoked. Any account owner can revoke apoc-google at any time from myaccount.google.com/permissions, after which the application can no longer read that account. Cached report data for an account is deleted on request.
Contact
Questions about this policy go through the contact sheet on austinwmson.com.
Changes
If what the application accesses or how it handles data changes, this page changes with it and the date at the top moves.