Social Publisher Privacy Policy
Social Publisher Privacy Policy
Updated October 23, 2026. This policy covers Cary Decker’s private MiniMe Social Publisher application. It does not replace the store’s separate customer privacy policy.
Information used
The application processes media provided by its owner, filenames, transcripts, captions, thumbnails, product references, selected social accounts, approval records, schedules, publication identifiers and URLs, and available platform statistics. Authorized Google connections provide the relevant YouTube channel information and video status. Optional Google Drive and Sheets access supports reading, uploading, naming and organizing media and recording publication information in the owner’s chosen spreadsheet.
Purpose and control
Information is used to prepare content, carry out the owner’s reviewed publishing instructions, maintain archives, verify results and diagnose operational failures. Authorization tokens are stored in restricted application credential files for the background worker. Other application records and media are stored on the publisher host and in owner-selected cloud archives. The private publisher is accessed through the owner’s private network.
Service providers and sharing
Approved publication sends the selected media and captions to the chosen platform. The application uses Google/YouTube, connected social platforms, Buffer where configured, the Oracle publisher host, and the owner-approved media host when needed to deliver videos. Google Drive archives and Sheets records are stored in the owner’s selected destinations. Hosting a video for delivery can create an externally accessible delivery URL; this is distinct from making the application public. Third-party providers process information under their own policies.
The application does not sell Google user data, use it for advertising, or use it to train generalized artificial-intelligence or machine-learning models. Local caption drafting processes content for the owner’s requested task; it is not model training. Google data is used only for the described owner-authorized features, consistent with the Google API Services User Data Policy, including its Limited Use requirements.
Retention and deletion
Cloud archives and publishing records are retained for the owner’s ongoing use until the owner deletes them or requests removal. App-managed local media can become eligible for cleanup after all approved destinations are published and cloud/archive checks pass, under the configured retention policy. This does not automatically delete cloud archives, published posts or general device Trash. Revoking access does not remove copies already posted to a platform or stored in an archive; those copies must be deleted in their respective services.
Revoking access and contacting the operator
Google access can be revoked at Google Account connections. The owner can also disable application connections and request deletion of application data by contacting Cary Decker at cary@innowerks.com.