Privacy policy
How W2 Analytics handles Google user data.
This policy explains how W2 Analytics, operated by W2 Kitchen, accesses, uses, stores, shares, protects, retains and deletes Google user data obtained through Google and YouTube APIs.
1. Scope of this policy
W2 Analytics is a private, read-only analytics application used by W2 Kitchen to analyse and improve its own YouTube channel and video-production process. It is not offered as a public analytics service.
This policy applies to Google user data accessed after an authorised Google Account grants W2 Analytics permission to access the W2 Kitchen YouTube channel and its analytics.
2. Google user data W2 Analytics accesses
With the channel owner's authorisation, W2 Analytics may access:
- Read-only YouTube account, channel and video information, including the identity of the authorised channel, the owner's video inventory, video identifiers, titles, publication information and status information needed to resolve videos correctly.
- Non-monetary YouTube Analytics information, including performance metrics such as views, watch time, average view duration or percentage viewed, subscriber changes, engagement information and audience-retention data.
- OAuth authorisation credentials required to maintain authorised read-only access. W2 Analytics does not request or store the Google Account password.
W2 Analytics requests read-only access. It does not use these permissions to create, edit or delete YouTube videos, comments, playlists, captions or channel settings.
W2 Analytics does not request monetary YouTube Analytics access under the current production configuration.
3. How Google user data is used
We use Google user data only to provide and improve W2 Analytics for the authorised W2 Kitchen channel. Uses include:
- identifying the authorised channel and its videos;
- maintaining accurate mappings between YouTube videos and W2 production records;
- measuring and comparing channel and video performance;
- analysing audience-retention and other non-monetary performance patterns;
- maintaining historical analytical records so performance can be compared over time;
- identifying videos or patterns that warrant further investigation; and
- supporting internal editorial, research, production and optimisation decisions for W2 Kitchen.
We do not use Google user data for targeted advertising, retargeting, credit decisions, sale to data brokers, information-resale services or the training of generalised artificial-intelligence or machine-learning models.
4. Storage and data protection
W2 Analytics may store authorised Google user data in W2-controlled Google Cloud services, including BigQuery and Cloud Storage, where necessary for historical analysis, validation, provenance and reproducibility.
We protect Google user data using technical and organisational controls appropriate to this private application. These include:
- Encryption in transit: encrypted HTTPS/TLS connections are used when communicating with Google APIs and Google Cloud services.
- Encryption at rest: stored customer content is protected by Google Cloud encryption at rest.
- Least-privilege access controls: production data is restricted to authorised identities and services that require access to operate W2 Analytics.
- Credential separation: OAuth credentials are kept separate from analytical data.
- Secret management: durable OAuth credentials are stored in Google Cloud Secret Manager rather than in source code or the analytics database.
- Source-control protections: OAuth tokens, credentials and raw sensitive production data are not permitted to be committed to the source-code repository.
- Bounded read-only interfaces: W2 Analytics does not expose arbitrary database access or YouTube write operations through its user-facing analytical interfaces.
No security measure can guarantee absolute security, but W2 Analytics is designed to minimise the data and permissions it exposes and to fail closed when expected identity, scope or source conditions are not met.
5. Sharing and disclosure
We do not sell Google user data or share it with advertisers, data brokers or information resellers.
Google user data may be processed by service providers or infrastructure providers only where necessary to operate W2 Analytics and only for the purpose of providing the application's functionality. Access is limited to authorised operators and services with a need to process the data for those purposes.
W2 Kitchen may also disclose data where necessary to protect the security of the service, comply with applicable law, or as otherwise permitted by Google API policies and applicable law.
If W2 Analytics later introduces a new transfer or processing use that materially changes these practices, this policy and the relevant Google authorisation or consent process will be updated before that use is activated.
6. Google API Services User Data Policy and Limited Use
W2 Analytics' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
W2 Analytics also uses YouTube API Services in accordance with the applicable YouTube API Services Terms of Service and developer policies.
7. Data retention and deletion
W2 Analytics retains historical analytics for as long as reasonably necessary to provide the longitudinal analysis, comparison, provenance and production-intelligence purposes described in this policy, or until that data is no longer needed for those purposes.
OAuth credentials are retained only while the channel authorisation remains active and the credentials are required to operate the service. They will be revoked, replaced or deleted when they are no longer required or when authorisation is terminated, as appropriate.
When Google user data is no longer required for the purposes described in this policy, W2 Kitchen will delete or securely dispose of it in accordance with its operational retention practices and applicable legal or security obligations.
8. Revoking access and requesting deletion
The W2 Kitchen channel owner may revoke W2 Analytics' Google Account access through Google's account permissions or third-party connections settings. Revocation stops future access to Google APIs but does not by itself necessarily delete historical analytical records already stored by W2 Analytics.
The channel owner may request deletion of Google user data held by W2 Analytics by emailing ey@w2kitchen.com. On a valid deletion request, W2 Analytics will delete data that is no longer required to be retained for legal, security or legitimate audit obligations and will stop using deleted data for the application's analytical purposes.
9. Human access
Access to Google user data is limited to authorised W2 personnel and approved services where access is necessary to operate, secure, troubleshoot or provide the W2 Analytics functionality described in this policy, or where disclosure is required by law.
10. Changes to this policy
W2 Kitchen may update this policy when W2 Analytics functionality or data practices change. Material changes affecting the use of Google user data will be reflected in this published policy before the data is used for a materially different purpose. The “Last updated” date above will be revised when this policy changes.
11. Contact
Questions, privacy requests or deletion requests relating to W2 Analytics may be sent to ey@w2kitchen.com.
Return to the W2 Analytics homepage.