Privacy policy

Data and purpose

The studio processes your uploaded media, briefs, text, Brand Memory, drafts, approvals and local history to prepare content. Local AI analyzes your own inputs; it does not use YouTube API or Meta data to train AI or create advertising profiles.

The application uses YouTube API Services. With your Google authorization it reads the selected channel identity and the information necessary to verify a specific upload: video identifier, metadata, processing status, visibility and resource version. It stores OAuth tokens and resumable upload session references only in the local macOS Keychain. It does not request your Google password or download videos from YouTube.

When a Facebook Page or professional Instagram account is connected independently, the application processes the selected account or Page identity, granted permissions, Page tasks and access validity with the user's authorization. For a particular approved operation it retains transfer and post identifiers, necessary metadata, processing status and verification results. Access tokens, Meta app secrets and Cloudflare R2 storage access keys are stored in the local macOS Keychain. Connection, publication-operation and temporary-delivery records are kept in separate private storage apart from code and original media. SMM does not request your Facebook or Instagram password.

Sharing

Only content you explicitly approve for transfer is sent to the selected provider. YouTube receives the approved video, title, description, audience declarations and technical upload requests. Upload permission and a later change to public or unlisted visibility are separate decisions. Account linking, editorial approval and a local calendar entry do not publish content.

Source photos and videos, working drafts and Brand Memory remain in SMM's private storage on the owner's Mac. For Facebook publication, SMM sends the exact approved export bytes directly to Meta. For Instagram publication, it sends only the explicitly approved final export and necessary file information to separate private Cloudflare R2 storage with EU jurisdiction, from which Meta retrieves it. Originals, working media, unapproved drafts and Brand Memory are not transferred to R2. EU export storage does not determine where Meta subsequently processes or retains its received copy.

Meta receives the approved content, accompanying text and information needed for the requested operation. It can retrieve an R2 export through a signed download link valid for no more than one hour. Anyone who obtains that link can repeatedly download that export while the link is valid, without signing in to SMM; it is neither a single-use link nor access bound to a particular person. SMM passes the link only to Meta and does not display it in the ordinary interface or store it in routine records. Link expiry alone does not delete the stored object or a copy already downloaded.

The studio, its API and source media remain private. The private remote connection uses Tailscale and application authentication. Storage setup, a connection check, account linking and editorial approval do not start media transfers or publish anything. No advertising, third-party tracking or analytics widgets are embedded in the studio. Use of Cloudflare and Meta services and opening external links are also subject to the respective providers' policies.

Information website

The separate public information website contains these documents only. It does not provide access to the studio, source media, account records or OAuth credentials. Hosting providers process necessary connection and security information to deliver and protect the website. The site does not include advertising, tracking widgets or a contact form. The operator receives messages only when you choose to contact the published email address.

Retention and deletion

Original user media and editorial history are kept for the owner's work until separately deleted by the owner. Google authorization and YouTube-derived data are handled separately. Requests to revoke access or erase provider data must be completed as soon as possible and within seven calendar days, including controlled backup copies. Stale API metadata must be refreshed or removed within thirty calendar days. A pending cleanup must not be represented as completed.

A temporary R2 export is used only to deliver approved content. Once Meta confirms completed retrieval and processing, or the attempt has definitively ended, SMM promptly requests deletion of the object and verifies the result. Transfers and deletion attempts are durably recorded; failure, uncertainty or unavailable access remain marked as pending and require further verification, a deletion retry or operator action. For an uncertain attempt, SMM does not treat elapsed time or a missing response as confirmation of deletion.

As a fallback, an R2 lifecycle rule is set to remove objects and abort incomplete uploads after one day. This is when they become eligible for automatic removal; the provider may carry out removal later. It is not a guarantee of deletion within exactly 24 hours. Current SMM delivery uses a single complete file upload and does not itself create multipart uploads.

The studio's revocation and deletion control applies to YouTube connections. Send requests concerning Facebook, Instagram or R2 delivery data to the operator at the contact below. The operator verifies the requester, prepares the requested deletion scope and arranges removal of the relevant credentials, provider records, temporary exports and controlled copies. SMM does not yet provide combined automatic erasure of all Meta data; local account disconnection does not replace that request.

Deleting an R2 export or expiring its link does not remove a copy already retrieved by Meta. Revocation and local deletion do not delete published content on Instagram, Facebook or YouTube; manage that content separately with the respective platform, using YouTube Studio for YouTube. The owner must also remove separately made backups outside controlled storage; the application cannot access those files.

Sessions

The studio uses a Secure HttpOnly session cookie for private HTTPS login, and browser local storage for interface preferences and resumable file-selection bookkeeping. Each device has its own revocable session. No advertising cookies are used.

Purpose and your rights

Data is processed to provide the private studio functions you request, protect the service and handle your support or deletion request. Optional Google or Meta access is based on your authorization; it can be withdrawn without authorizing publication. Where data-protection law applies, you may request access, correction, erasure, restriction or portability of your personal data and object to processing when the applicable conditions are met. You may also complain to your competent data-protection authority. The operator does not use this studio to make decisions about individuals with legal or similarly significant effects.

Your controls

You can revoke Google's authorization directly in Google account permissions. Google's handling of data is described in the Google Privacy Policy. Contact the operator for access, correction, deletion or privacy complaints. Before the reviewed integration is activated, the owner must accept the current privacy policy and terms.

You can disconnect Facebook or Instagram in the studio; this removes locally stored access, not authorization at Meta or already published posts. You can also revoke the app's authorization directly in the relevant Meta account settings. To erase retained connection and publication-operation data as well, follow the separate data-deletion instructions and contact the operator. An R2 access key can be revoked directly at Cloudflare. First resolve recorded temporary objects or arrange their deletion at the provider; removing a local key does not confirm object deletion.