Privacy policy
Review draft.
Prepared 22 October 2026 · Based on the supplied publishing implementation and documentation.
1. Operator & scope
ANMedia Studio is operated by Agile Nimbus to stage, review, approve, schedule and publish content for its own brands. This draft covers the internal application’s publishing functions, including its use of YouTube API Services.
For privacy questions or data-deletion requests, contact admin@agile-nimbus.com. This address is provisional: the operator must verify that it receives mail before adopting this policy.
This public information website does not connect to Google accounts or collect OAuth tokens. It contains no analytics scripts, embedded videos or application cookies. Hosting infrastructure may process request information; the operator must confirm its hosting log practices.
2. Data accessed and why
The inspected YouTube adapter retrieves channel identifiers, channel names, handles and the uploads-playlist identifier to identify the authorised publishing destination. It reads recent uploads, including private items, and video information to verify uploads and reconcile uncertain publishing outcomes.
Video information includes identifiers, titles, channel IDs, privacy and upload status, scheduled publication times and failure information. Where requested, it reads file size, duration and processing status to check an upload. The studio sends approved video files, captions and publication metadata such as titles, descriptions, tags, language and audience declarations to YouTube.
The credential record holds access and refresh tokens, expiry and acquisition times, plus the connected account’s identifier, name and handle. These authorise API operations without storing the Google account password.
youtube.upload
Requested to upload videos to the authorised YouTube channel.
youtube.force-ssl
Requested for caption uploads, video publication and scheduling updates, and channel/video reads used for checks and reconciliation. Google grants broader capability under this scope, including viewing, editing and deleting videos, ratings, comments and captions. The inspected adapter does not implement comment/rating operations or video deletion. The scope is not simply an encryption setting.
The current scope configuration does not request Gmail, Google Drive or a general Google profile/email scope. Confirm the deployed OAuth configuration matches the inspected code before adopting this description.
3. Storage and security
The current credential store writes OAuth client configuration and token records to local JSON files in an operator-controlled secrets directory, separate from project source and staging. The inspected store does not encrypt those JSON files at application level. Files remain accessible to the operating-system user; actual filesystem permissions, disk encryption and backup protection require operator confirmation.
The credential module is designed to keep tokens out of manifests, normal workflow state and dashboard responses. This is not a guarantee that every operational log or error path has been audited for secret leakage.
Staged release files and local workflow records contain media, publishing metadata, validation results, approvals, reviewer comments, remote identifiers, schedules and operation/error history. Publishing audit events are recorded in a hash-chained log; this makes changes detectable when checked, but does not make the log tamper-proof.
The local dashboard uses sign-in sessions with an HttpOnly, SameSite=Strict cookie, per-session CSRF protection and a loopback-only listener. Reviewer passwords are stored as scrypt hashes. These are features observed in the code, not a security certification or confirmation of the deployed environment.
5. Retention
The inspected implementation keeps local token files, staged releases, workflow histories, publishing records and audit logs. No complete automatic expiry or retention schedule for those records was established by this review.
Confirmation required: define how long each category is kept, what is removed on revocation or request, how backups and derived records are handled, and who carries out removal. This draft does not promise a retention period or claim indefinite retention is acceptable.
6. Revoke access or request deletion
You can revoke the studio’s Google access through Google account permissions. Select the application entry and remove access. Revocation prevents further authorised access; it does not itself prove that local studio copies have been erased.
To request removal of stored data, email admin@agile-nimbus.com with the relevant channel or account identifier and the scope of your request. Do not send passwords, tokens or other credentials. The contact address must be verified before this becomes the published request route.
The credential store contains a token-file removal operation, but this review did not establish a complete user-facing erasure process covering staging, state, audit logs, published records and backups. Nor did it establish automatic deletion following Google revocation. Those procedures must be implemented or confirmed before the policy is final.
Removing local data does not delete already-uploaded videos from YouTube. Manage those separately in YouTube Studio. Do not rely on this draft as a commitment to a deletion timeframe.
7. Google and YouTube policies
Use of Google user data is subject to the Google API Services User Data Policy, including its applicable Limited Use requirements. YouTube integration is also governed by the YouTube API Services Terms of Service and YouTube API Services Developer Policies.
The final policy and actual operation must align with those requirements, including required data handling and deletion. Linking these documents does not establish compliance. See also the YouTube Terms of Service and Google’s scope documentation.
8. Required operator confirmations
- Confirm the operator’s identity, monitored contact address and actual deployment configuration.
- Confirm the inspected source matches the running ANMedia Studio application and OAuth scope configuration.
- Set and implement category-specific retention and complete deletion/revocation procedures, including backup handling.
- Confirm filesystem access, device protection, backup locations and people with access.
- List actual processors, transfers, hosting logs, cookies and any secondary uses of Google data.
- Confirm applicable Limited Use practices, including whether any data reaches model-training or other AI services.
- Ensure the internal application presents the final policy and required terms to users, with appropriate agreement before use.
Replace this draft with the reviewed policy, record its effective date and update users when material data practices change.