Privacy Policy

Neutral Media Tools · Effective

Who operates Publisher

Amr Abdelraouf operates Neutral Media Tools, a private Windows application used by its operator to manage and publish content. For privacy questions or requests, email neutralmedia.support@gmail.com.

What Publisher processes

Publisher processes connected account and Page identifiers, selected media and publishing text, release times, publication status, links, and approval records. On Facebook, it can check relevant comments to avoid duplicates and post a Page comment after the owner has authorized it and Meta has confirmed that the Reel is public. For these checks it may read comment text, identifiers, and author information.

When the owner requests an Insights check, Publisher retrieves available Facebook Reel performance metrics from Meta and displays the results. The current Insights check does not save metric values or historical performance snapshots.

pages_show_list
Identifies Pages the owner manages.
pages_read_engagement
Verifies the connected Page and reads publication information.
pages_manage_posts
Publishes or schedules approved Facebook content and handles its attachments.
pages_read_user_content
Reads relevant Page comments when checking for duplicates.
pages_manage_engagement
Posts owner-authorized Page comments.
read_insights
Reads available Facebook Page and Reel performance metrics, including views, reach, watch time, and engagement, for content performance analysis.

Google OAuth and YouTube

Publisher uses YouTube API Services. The operator signs in and grants access on Google’s authorization page. Publisher does not collect the Google password. It requests the https://www.googleapis.com/auth/youtube.force-ssl permission to verify the connected channel and carry out authorized YouTube publishing actions.

Publisher reads channel identifiers and names, video identifiers, and video, processing, publication, and subtitle status needed for the publishing workflow. It sends selected video files and metadata to YouTube, including titles, descriptions, tags, categories, language, audience and disclosure settings, visibility, and the scheduled release time where applicable. It sends selected thumbnails and subtitle files when supported. Publisher uses this data to prepare, submit, and verify authorized publishing operations.

Google issues an access token for API requests and a refresh token to renew access without asking the operator to sign in for every operation. Publisher stores the saved YouTube OAuth credentials, including those tokens, locally in Windows Credential Manager. Local publishing records can contain channel and video identifiers, links, selected publishing settings, and status or verification timestamps. The account health display also stores non-secret channel and verification information locally. These credentials and records are separate from this website.

Publisher uses Google user data for the YouTube functions described here in accordance with the Google API Services User Data Policy, including its Limited Use requirements. See the Google Privacy Policy for how Google handles data it receives.

Storage and sharing

The saved Facebook Page access token is stored in Windows Credential Manager. A local SQLite database holds publishing plans, approvals, job status, and comment jobs. Project folders may also contain upload records with links and timestamps. Windows account and file permissions restrict local access.

Publisher sends the selected data needed for an authorized operation to the relevant platform, such as Facebook, Instagram, YouTube, or TikTok when connected. That can include a video, description, cover, subtitles, release time, or comment, depending on the operation. Each platform handles the data it receives under its own privacy policy. Publisher does not sell personal data or share it for advertising.

Retention and your choices

Publisher retains credentials as needed for an authorized connection. Publishing and approval records are kept for operating the workflow, resolving issues, and preventing duplicate actions. There is no fixed automatic deletion schedule for these records.

You can contact the operator to ask about personal data held by Publisher or request access, correction, or deletion. The operator verifies requests and accounts for relevant local records and backups, subject to applicable retention obligations. Revoking Meta access stops future use of that authorization. Existing local records and content already on Facebook are handled separately.

To revoke Publisher’s YouTube access, remove the publishing application you authorized from your Google Account’s third-party access settings. To request deletion of saved Google credentials or YouTube API data held locally by Publisher, email neutralmedia.support@gmail.com and identify the relevant channel or video. Revocation blocks future use of that authorization. Local deletion does not delete videos, scheduled releases, or other data held by YouTube. Manage those separately in YouTube Studio.