Skip to main content

What Aivara Social does

Aivara Social is a social scheduling and publishing interface operated by Aivara Solutions LLC. Authorized users can connect their own YouTube channels, create a post, choose the exact connected destination, provide video metadata, and request publishing from the same dashboard used for other supported social platforms.

Aivara Social uses the YouTube Data API v3. Aivara Solutions is not endorsed, sponsored, certified, or operated by YouTube or Google.

How authorization works

  1. The user selects Connect YouTube in Aivara Social.
  2. The user is redirected to Google OAuth and chooses a Google account.
  3. Google displays the permissions requested by Aivara Social.
  4. The user explicitly authorizes access and returns to Aivara Social.
  5. Aivara resolves and displays the authorized YouTube channel.
  6. The connection can later be disconnected or reconnected by the user.

Permissions we request

https://www.googleapis.com/auth/youtube.readonly

Used to identify and display the exact YouTube channel authorized by the user.

https://www.googleapis.com/auth/youtube.upload

Used only when an authorized user explicitly requests a video upload or publishing action.

Exact channel selection

Separately authorized YouTube channels may coexist. For each post, the user selects the exact connected YouTube destination. Aivara does not arbitrarily route a post to another channel.

Video publishing

The publishing interface supports a video, title, description, tags, category, privacy setting, and Made for Kids selection. Aivara sends content only after the user submits a publish-now or scheduled action.

Privacy and data handling

  • OAuth credentials are stored by the encrypted server-side credential system.
  • Connected-account data is separated by the authorized account or tenant.
  • YouTube and Google data is used only for requested connection and publishing features.
  • Aivara does not sell Google user data or OAuth credentials.
  • Provider video IDs and status may be retained to display publishing history and results.
  • No credentials, access tokens, refresh tokens, or service keys are exposed on this page.

Disconnecting YouTube from Aivara

  1. Log in to Aivara Social.
  2. Open Social Scheduler, then Settings.
  3. Locate the connected YouTube channel.
  4. Select Disconnect.
  5. The connection is disabled for future publishing requests.

Users can also revoke access at the Google account level through Google Account → Security or third-party connections → Aivara Social → Remove access. Disconnecting does not delete videos already uploaded to YouTube. Account-associated deletion requests may also be sent to kevin@aivarasolutions.com.

YouTube API Compliance Evidence

Operator
Aivara Solutions LLC
API client
Aivara Social
Google Cloud project
Aivara Social
Project ID
aivara-social
Project number
827330762812
Primary access URL
https://portal.aivarasolutions.com

Documented production test

A private production test upload was reported as successfully reaching the explicitly selected RICH AF YouTube channel. This evidence statement does not disclose credentials, tokens, private video URLs, or account secrets.

Publishing flow

Create Post → Select YouTube → Select exact channel → Upload video → Enter YouTube metadata → Publish now or schedule → Track provider status → View the resulting provider URL when available.

High-level architecture

User → Aivara Social Portal → Google OAuth → Encrypted Social Connection Storage → Aivara Social Publishing Service → YouTube Data API v3 → User-selected YouTube Channel.

Reviewer access requirements

A reviewer account should be created manually and assigned access to the Social Scheduler with non-sensitive sample data. The reviewer role should be able to open Settings, view a connected YouTube destination, exercise Connect, Reconnect, and Disconnect controls, create a draft, select YouTube and an exact channel, upload a test video, enter YouTube metadata, choose privacy and Made for Kids settings, submit a private test publish, and view publishing history and provider status.

Credentials must be delivered through the audit form or another approved private channel. They must not be hard-coded into the website or included in this public document.

Policies and external resources