Content OS is a private content-production workspace operated by Redefined by AI. The account owner uses it to plan projects, store project files, research public videos, schedule and publish their own content, and configure replies to comments on their Instagram posts.
This policy explains how connected Google, YouTube, Drive and social-account data is accessed, used, stored and deleted. Connections and publishing actions are controlled by the signed-in workspace user.
Google sign-in provides the account identity, including name, email address and profile information, to identify the workspace user. When Drive is connected, access and refresh tokens are stored server-side so the application can continue working while the user is away. Content OS does not receive the user's Google password.
The Drive permission is drive.file: access is limited to files created by or selected for use with this app. The app creates project folders and documents, uploads project files, lists and reads accessible files, and moves or deletes files when the user requests those actions. Project media can be copied temporarily or synced to operator-controlled storage for the user's production workflow.
Connecting YouTube stores the channel ID, title, handle, thumbnail URL, granted permissions, access and refresh tokens, and token expiry. Read-only access identifies the connected channel and retrieves channel totals, uploads, video titles, descriptions, dates, thumbnails and public view, like and comment counts. YouTube Scan also uses available public video and channel data to find and rank research references and saves scan history, video details and user-collected transcripts in the private workspace.
The upload permission sends the video specified on a variant or, for project publishing, the first eligible video in filename order from the project's output folder, using the applicable variant or project title and description. Uploads run when the user publishes or at the scheduled time. The current publishing workflow requests public visibility. Publishing results, video URLs and activity records are saved with the project. Content OS uses YouTube API Services; see the YouTube Terms of Service and Google Privacy Policy.
Google account and API data is used to provide the sign-in, file-management, publishing, insights and research functions described above. The Google API Services User Data Policy, including its Limited Use requirements, governs the use and transfer of information received from Google APIs. Content OS does not provide an advertising or data-sale service and has no model-training pipeline. Optional AI tools process user-submitted content to produce the requested output; they do not receive Google OAuth credentials.
Files and project content are sent to the destinations the user chooses for their workflow, including YouTube, Instagram or LinkedIn when publishing. If a linked Notion page is configured, publishing links may be written back to it. Optional AI and audio tools process content submitted to the provider configured by the workspace owner, such as OpenAI, Google Gemini, OpenRouter or ElevenLabs. Those optional submissions are separate from Google authorization; Google OAuth credentials are not included in those tool submissions.
The operator's hosting and database services process stored workspace data to run the application. Access to Google data is limited to providing these features, user-authorized actions, and necessary support, security or legal obligations. It is not made available to unrelated advertisers or data brokers.
Connection credentials are retained while the connection is maintained. YouTube can be disconnected under Settings → Integrations: the app attempts to revoke the Google authorization and removes the stored channel connection. Access can also be revoked through Google Account permissions. Revoking access stops future authorized requests; it does not automatically delete videos already uploaded to YouTube or files already stored in Drive.
Project records, publishing links, activity and saved research are retained separately for the user's workflow. Removing a project from the workspace can archive it rather than immediately erase its database record; Drive-folder deletion is a separate user-controlled action. Disconnecting a channel does not itself remove those records or copies previously sent to another service.
To request deletion of stored Google account data, credentials, research or project records, email redefinedbyai@gmail.com from the connected account and identify the data to remove. The operator reviews and verifies deletion requests; contact the support address for confirmation and status. Disconnecting a service alone does not constitute a request to erase the entire workspace. You can manage or delete uploaded videos and Drive files directly in the relevant Google service.
Credentials are stored server-side, and user-facing connections use HTTPS. Account and workspace access controls restrict the application to authenticated users and authorized operations.
When an Instagram professional account is connected to Content OS, we store:
When someone comments on one of the connected account's posts, and only if that comment matches a keyword the owner configured, we store:
We do not collect commenters' email addresses, phone numbers, follower lists, private messages they did not initiate, or any data from accounts other than the connected one.
We do not sell this data, share it with advertisers, use it for advertising or profiling, or use it to train machine-learning models.
The account owner can disconnect Instagram at any time from Settings → Integrations in the application, which deletes the stored token and all associated automation data.
If you commented on a post and want the record of that comment removed, email redefinedbyai@gmail.com with the Instagram username you commented from. We will delete it within 30 days and confirm by reply.
Data is stored in a private PostgreSQL database on infrastructure controlled by Redefined by AI, not exposed to the public internet. Access is restricted to the account owner. Traffic between Instagram and the application is served over HTTPS, and incoming requests from Meta are verified using a cryptographic signature so that forged requests are rejected.
The application communicates with Meta's Instagram Graph API in order to receive comment notifications and send replies. It does not send Instagram data to any other third party.
If this policy changes materially, the updated date at the top of this page will change. Continued use of the application after that constitutes acceptance of the revised policy.
Questions or deletion requests: redefinedbyai@gmail.com