Platform compliance

Minimum scopes, clear use, and no hidden posting.

Vayiq's platform integrations are designed for approved, user-authorized content workflows. We request access only for features the user enables and keep publishing approval explicit.

Last updated: July 3, 2026

YouTube

  • Use official YouTube APIs for authorized channel data and allowed publishing/thumbnail workflows.
  • Separate read-only analysis from write/publish capabilities so users can grant only what they need.
  • Respect YouTube API Services Terms, branding requirements, quota limits, and user-data policies.
  • Use a verified OAuth consent screen and document requested scopes before any quota or compliance audit submission.

Instagram / Meta

  • Use approved Meta/Instagram APIs for authorized business or creator account workflows.
  • Request only reviewed permissions needed for the feature, such as account insights or publishing when approved.
  • Provide public Privacy Policy, Terms, Data Deletion, and clear product demonstrations for App Review.
  • Show account eligibility and professional-account requirements clearly before a user attempts publishing features.

TikTok

  • Use TikTok developer APIs only after the required app review, scopes, and posting audit requirements are satisfied.
  • Treat draft/direct posting as an explicit user-approved action, never an invisible background publish.
  • Respect platform quotas, refresh-token rules, and content policy requirements.
  • Show the connected creator identity and any platform-required privacy choices before a post is approved.

What Vayiq does not do

  • No sale of raw platform data.
  • No hidden auto-posting without user approval.
  • No private-data scraping.
  • No bot-wall evasion, credential sharing, or unofficial access paths against social platforms.
  • No fake competitor metrics; unavailable metrics are labeled as estimates or omitted.

Reviewer flow

  • Reviewers can use the public API Review Center to understand the product purpose before testing.
  • Demo videos should show the user signing in, connecting a platform through OAuth, seeing the requested scopes, returning to Vayiq, generating or reviewing an asset, and approving or rejecting the action.
  • Every submitted permission should be demonstrated. If a feature is not live and reviewable, the matching permission should not be requested yet.

Reviewer references

  • Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
  • YouTube API Services Terms: https://developers.google.com/youtube/terms/api-services-terms-of-service
  • Meta Platform Terms: https://developers.facebook.com/terms/
  • TikTok Developer Terms: https://developers.tiktok.com/terms/

Need help or deletion?

Email privacy@vayiq.com. For API and platform review questions, use platforms@vayiq.com.