Scope
This policy covers general.dev, its contact experiences, and the private General Dev Content Studio. General Development is based in Miami, Florida. Content Studio is currently an internal publishing tool operated by Will McLellarn, not a public multi-user service.
Information we handle
Depending on how you use the site or Content Studio, we may handle:
- Contact details and messages you choose to submit.
- Basic, privacy-conscious website analytics such as pages viewed, device category, and referring site.
- Connected-channel identity, granted permissions, account or channel identifiers, and encrypted OAuth access and refresh tokens.
- Videos, titles, descriptions, captions, schedules, provider post identifiers, delivery status, and operational error logs supplied or generated through Content Studio.
We do not ask for or store your social-platform password.
How we use information
We use this information to operate the requested website or publishing workflow; identify the intended destination account; upload, schedule, verify, and reconcile posts; prevent duplicate publication; secure and maintain the service; diagnose failures; and respond to requests. We do not sell personal information or use connected-account data for advertising or audience profiling.
YouTube API Services
Content Studio uses YouTube API Services. Its use is also governed by the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.
When you connect YouTube, Content Studio requests permission to identify the authorized channel, upload operator-selected videos, and read upload processing, visibility, and audience or made-for-kids status. It does not read analytics, comments, private messages, subscriptions, or viewing history.
You can disconnect YouTube inside Content Studio or revoke access from your Google account permissions. Disconnecting first disables local YouTube access and removes the locally stored credentials, channel identifiers, upload-session state, provider video or post references, publishing jobs, and attempt logs. Content Studio then asks Google to revoke authorization. If Google cannot confirm the request, Content Studio tells you to finish revocation from your Google account permissions. A disconnect does not delete videos already published on YouTube.
Other publishing platforms
Content Studio may connect to LinkedIn, X, and Instagram when the operator explicitly authorizes each account. We send only the operator-approved media, text, settings, and API requests needed to publish and verify posts. Those services process information under their own terms and privacy policies.
Storage, sharing, and security
We use service providers for application hosting, database storage, video storage, and operational analytics. They receive only the information needed to provide those services. OAuth credentials are encrypted at rest, administrative access is gated, and publishing callbacks are validated.
No internet service can promise absolute security. We limit access and use reasonable technical and organizational safeguards appropriate to this private workflow.
Retention and deletion
Connected-account credentials are retained until the account is disconnected, access expires, or deletion is requested. Publishing plans, uploaded media, provider post references, and delivery logs are retained while needed to operate and verify the workflow, then deleted or de-identified when no longer reasonably necessary.
To remove a connection or request deletion, follow the steps on our data deletion page or email hello@general.dev.
Changes and contact
We may update this policy as Content Studio or applicable platform requirements change. The date above identifies the current version. Questions or privacy requests can be sent to hello@general.dev.