Privacy Policy
Last updated: November 18, 2026
Auto MMO Publisher ("the Service", "we", "us") is a workspace that lets an authorized operator plan, review, schedule, and publish original content to social media accounts the operator owns or is otherwise authorized to manage, including Facebook Pages, Instagram professional accounts, TikTok, and YouTube channels. This Privacy Policy explains what information we collect, why we collect it, how it is used and stored, and the choices available to you.
We collect and store only the information needed to operate the publishing workflow:
- Account information: your login email and workspace settings.
- Connected platform data: platform account IDs, display names, and profile metadata returned by the platform after you explicitly authorize a connection (for example, via TikTok Login Kit or Facebook Login).
- Access tokens: OAuth access and refresh tokens issued by the connected platform, used solely to make authorized API calls on your behalf.
- Content data: captions, media references (such as uploaded file URLs), scheduling times, and privacy settings you configure for each post.
- Operational logs: publish job status, API responses, timestamps, and retry history, used for debugging and auditing.
We do not collect content from accounts you have not explicitly connected, and we do not scrape or collect data from third parties who have not authorized the Service.
Information is used exclusively to operate the Service:
- Authenticating and maintaining your workspace session.
- Establishing and refreshing connections to platforms you authorize.
- Preparing, scheduling, and dispatching publish requests you create.
- Recording the outcome of each publish request for your own audit trail.
- Diagnosing errors and improving reliability of the publishing pipeline.
We do not sell personal data, and we do not use your data for advertising or for training third-party models.
OAuth access and refresh tokens are stored encrypted at rest and are only ever transmitted to the platform that issued them (for example, sending a TikTok access token only to TikTok's API). Tokens are never displayed in full in the interface, never emailed, and never shared with any third party outside of the platform that issued them. You can revoke a platform connection at any time from the workspace settings, or directly from the connected platform's own app permissions page (for example, TikTok Settings > Manage Account > Apps and websites logged in with TikTok). Revoking access deletes the corresponding stored token.
We retain account, connection, and publish-job data for as long as your workspace remains active, so that you can view your publishing history. If you disconnect a platform, its access tokens are deleted immediately. If you delete your account, all associated personal data, tokens, and content references are deleted within 30 days, except where we are required to retain limited records for legal or security purposes.
The Service integrates with third-party platforms (Facebook, Instagram, TikTok, and YouTube) and infrastructure providers (hosting, database, and file storage). These providers process data only as needed to deliver the Service and are bound by their own privacy policies:
Auto MMO Publisher uses the YouTube API Services. By connecting a YouTube channel, you agree to be bound by the YouTube Terms of Service and acknowledge the Google Privacy Policy.
Limited Use. Auto MMO Publisher's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Data we access. With the permissions you explicitly grant on Google's consent screen (the youtube.upload and youtube.force-ssl scopes), the Service accesses: your YouTube channel ID and channel title; the titles and IDs of the playlists on your channel (only to find the playlist you name for a video); and, for each video you publish through the Service, the video ID and the result of each step returned by YouTube (video link, thumbnail, subtitles, playlist). The Service also stores the OAuth access and refresh tokens Google issues to it. The Service does not read your watch history, subscriptions, comments, analytics, or any other channel's data.
How we use it. This data is used only to perform the actions you request in the Service: uploading the video file you select with the title, description, tags, language, privacy status and scheduled publish time you set; setting the thumbnail you upload; uploading the caption (subtitle) file you attach; adding the video to the playlist you name; showing which channel is connected; and showing you the result of each action. We do not use YouTube data for advertising or profiling, and we do not use it to train machine-learning or AI models. We do not allow humans to read your YouTube data except where you ask us for support, it is needed to investigate abuse or a security problem, or the law requires it.
Who we share it with. We do not sell or transfer YouTube data to any third party. Data is sent only to Google/YouTube to make the API calls you request, and is processed by the infrastructure providers that host the Service (application hosting, database, and file storage), solely to run the Service and under their own security and privacy terms.
How we protect it. All traffic uses HTTPS/TLS. OAuth tokens are stored server-side in our Google Cloud Firestore database, which Google encrypts at rest by default; the Service adds no extra application-level encryption. Tokens are never shown in the interface and are sent only to Google. Access to the database is restricted to the Service and its operator.
Retention and deletion. Tokens are deleted immediately when you press "Disconnect YouTube" in the Service's settings, and the Service also asks Google to revoke them. If you revoke access in your Google Account permissions, the Service can no longer access your channel and deletes the stored tokens and channel details when it next detects the revocation (when it next uses them, and at the latest in a daily check). A daily job refreshes the stored channel name and ID, and deletes the per-video result details (video ID, link, thumbnail, subtitles and playlist status) of finished YouTube publishes 30 days after they were published, in line with the YouTube API Services Developer Policies. You can ask us to delete all of your data at any time by emailing the contact address below; we complete deletion within 30 days.
You may at any time: request a copy of the personal data we hold about you, request correction of inaccurate data, request deletion of your account and associated data, or withdraw consent by disconnecting a platform. To exercise any of these rights, contact us using the details below.
The Service is intended for business and creator use and is not directed at children. We do not knowingly collect personal information from anyone under the age of 16. If you believe a child has provided us with personal information, contact us and we will delete it.
We use industry-standard safeguards, including encryption in transit (HTTPS/TLS), encryption at rest provided by our database host for stored credentials, access controls limiting who can view stored data, and audit logging of publish actions. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above. Continued use of the Service after a change constitutes acceptance of the updated policy.
For privacy questions, data access, or deletion requests, contact us at iduncarewattheysay@gmail.com.
See also our Terms of Service.