steddUse of YouTube API Services
Steddai uses YouTube API Services to connect the channel selected by the signed-in channel owner, retrieve channel, video, statistics, comment, and reply data, and perform owner-requested actions such as publishing replies or updating a video description or owner-authored comment. Steddai requests read-only and write access because these shipped features require both. Steddai never requests or stores a YouTube password and does not scrape YouTube.
Data accessed and stored
Depending on the feature you choose, Steddai may process your YouTube channel ID and title; uploaded-video IDs, titles, descriptions, tags, thumbnails, visibility, dates, duration and statistics; public comments and replies, including author display names and channel IDs; and the results of actions you explicitly authorize. OAuth refresh tokens and user-supplied API keys are encrypted at rest and are never displayed again after connection.
How the data is used
YouTube data is used to show and refresh your creator workspace, organize comments, generate editable reply and content drafts, maintain audience history for the channel owner, and execute YouTube actions that you separately preview or confirm. Authorized data is visible only to the authorizing workspace and service providers acting for Steddai. Steddai does not sell YouTube data, use it for advertising, or allow unrelated third parties to access it.
Refresh and retention
Active data is refreshed or deleted within the periods required by YouTube’s Developer Policies. Non-statistical YouTube API data is refreshed or deleted within 30 calendar days. Stored statistics and authorization are rechecked at least every 30 days. If authorization is revoked or cannot be refreshed, Steddai stops access and deletes the associated authorized YouTube data as soon as possible and within seven calendar days.
Your control and YouTube actions
Steddai identifies the connected channel and clearly labels actions that will change YouTube. Replies, description edits, and owner-comment edits require a user-initiated preview or confirmation. Steddai does not change video visibility unless a user expressly requests a feature that clearly identifies that visibility change.
Disconnect, revoke, and delete
Use Settings → Integrations to disconnect YouTube OAuth. Steddai immediately asks Google to revoke the token and deletes stored authorized YouTube data and associated YouTube-derived workspace records. You may also revoke access in Google’s security settings. Deleting information stored by Steddai does not delete content stored by YouTube; use YouTube itself, or an authorized tool that supports deletion, to delete content from YouTube.
A separate API-key connection reads public data without access to a Google account. Disconnecting that key stops future collection. Public API data is still refreshed or deleted according to YouTube’s required retention periods.
Applicable Google terms
Use of YouTube features is also governed by the YouTube Terms of Service and Google Privacy Policy. Steddai’s use of Google user data complies with the Google API Services User Data Policy, including its Limited Use requirements.