Now Obvious Publishing

Data practices

Privacy policy

Last updated: October 17, 2026

This policy covers Now Obvious Publishing, private software operated by the owner of @nowobvious on YouTube and @now_obvious on Instagram. It is used for the owner’s channels, not offered as a service to other account holders.

Information used by the local workflow

The current helpers do not retrieve private messages or YouTube Analytics reports. The Google permission youtube.force-ssl supports separate caption uploads and also permits broader account actions, including deletion. The implemented publishing workflows do not delete existing videos or posts.

Purpose, storage and sharing

This information is used to connect the intended accounts, carry out owner-authorized publishing and resolve upload problems. Credentials and sensitive upload journals are kept in owner-only files outside the shared project on the owner’s computer. Nonsecret connection results and release receipts may be retained in the project.

Authorization and publishing data is transmitted over HTTPS to Google or Meta as needed. Those platforms process uploaded content under their own policies, including the Google Privacy Policy.

The owner uses an AI-assisted production workflow. Selected media, scripts, public channel information and nonsecret connection or publishing results may be provided to the owner’s AI tools to create, review or troubleshoot a release. These tools process submitted material under their applicable service settings and policies. Credentials and tokens are not intended to be included in prompts or public files.

The tool does not sell Google or Meta account data, use it for advertising, or use it to train general-purpose AI models. Its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, disconnection and deletion

The owner retains local credentials and operation records while needed to run the workflow and reconcile uploads. There is no automatic timed deletion process. The owner can stop the software, remove authorization and delete its local credential files, journals and project receipts. Copies deliberately submitted to an AI service must also be managed through that service’s controls.

To revoke Google or YouTube access, open Google Account connections, select the publishing app and remove its access. See Google’s connection-management instructions and YouTube’s authorization-revocation guidance. Reauthorization is required before the local tool can access the account again.

Meta access can be removed in the connected account’s app or business-integration settings. Revoking access or deleting local files does not remove videos or posts already sent to a platform; the owner can manage those directly in YouTube or Instagram.

This informational website

This website has no signups, forms, cookies set by its code, advertising, analytics scripts or custom tracking. It does not run OAuth or receive tokens. When publicly hosted, the hosting provider may process ordinary request information, such as IP addresses and requested pages, to deliver and secure the site. Following an external link takes you to that provider’s website.

Questions and updates

Contact @now_obvious on Instagram about these practices. This page will be updated when the workflow’s data use changes.