ContentOSSign in

Privacy policy

ContentOS · Duke 520 LLC
Last updated: September 23, 2026

ContentOS helps authorized people plan, publish, manage conversations and measure content across their brands. Duke 520 LLC operates ContentOS. Contact us about privacy at heymrmom@gmail.com.

Information we handle

We handle your account name and email, workspace and brand membership, access permissions, sign-in sessions, and information you enter into ContentOS. This includes drafts, uploaded media, schedules, approvals, internal notes and publication records.

When you connect a platform account, we receive the account identifiers, authorization tokens and permissions needed for the features you enable. Depending on the platform and your authorization, we may retrieve account profiles, posts, captions, media references, comments and replies, participant identifiers, performance statistics, and private conversations and attachments. Private-message access applies only to supported accounts for which you grant that permission. People who comment on or message a connected brand may have their platform-provided information included in that brand’s inbox.

We also process operational information needed to keep the service working, such as request, synchronization, delivery and error records. Session cookies and browser storage support sign-in, security and interface preferences.

How we use and share information

We use information to provide the features requested by you or authorized brand members: prepare and approve content, carry out approved scheduled publications, synchronize platform content, organize conversations, send human-directed replies, and display reports. Background collection runs for configured accounts. Connecting an account does not by itself authorize every ContentOS user to publish or reply.

Authorized workspace and brand members can access information according to their permissions. Hosting, database, storage and operational service providers process information needed to operate ContentOS. Connected platforms receive the content and requests needed to perform the operations you authorize. When you follow a platform link or load content from another service, that service’s own policies also apply.

Protection and retention

Platform credentials are encrypted in ContentOS’s server-side vault. Access controls separate workspace and brand permissions. No security measure eliminates every risk.

ContentOS retains working content, synchronized observations, reports and delivery history to provide its features. Disconnecting or revoking a credential stops its use in ContentOS but does not by itself erase previously stored information. To request deletion of that information, follow our data-deletion instructions. We review the scope of each request and explain any information that must be retained for a legal obligation or a separate person’s rights. We do not treat this exception as permission to retain provider data contrary to the provider’s requirements.

Platform controls and YouTube

ContentOS uses YouTube API Services. Google’s handling of information is described in the Google Privacy Policy. YouTube use is subject to the YouTube Terms of Service. You can revoke ContentOS’s Google access through Google account permissions. Revocation and deletion of ContentOS’s stored data are separate controls; you may request both.

You may also remove the app’s access using the connected platform’s account or business-integration settings. Contact us if you need help identifying the relevant connection.

Questions and requests

Email heymrmom@gmail.com to ask about your information, request a correction, or request deletion. Do not send passwords, access tokens or refresh tokens. We may request enough information to verify your identity or authority over the affected account.

We will update this page when these practices change and seek additional consent where required before using connected-account data for a new purpose.