Content Poster privacy policy

Content Poster is a private publishing tool that posts my own photos and videos to Instagram and YouTube. It does not sell data, show ads or track people.

Colour-tinted photograph from about 1899: the Bosphorus seen from a wooded hill above Kandilli, the green shoreline curving towards Rumeli Hisarı under a pale pink sky.
The Bosphorus at Kandilli, photochrom, about 1899.Credit: "Bosphorus, view of Kandilli and the Rumelian Citadel, Constantinople, Turkey, ca. 1899" by Detroit Publishing Co., under license from Photoglob Zürich, public domain, via Wikimedia Commons

Who runs Content Poster

Content Poster (also called insta-poster) is built and operated by Gönenç Türkekul, an individual based in Istanbul, Türkiye. I am the data controller for the data described here. Contact: gonencturkekul@gmail.com.

Content Poster is not a public service. There is no sign-up, and only I can log in. It publishes content to Instagram and YouTube accounts that I own or manage.

What data the app processes

Content Poster processes only the data it needs to publish posts:

Instagram and Facebook (Meta)
An access token for the connected Instagram professional account and its Facebook Page, plus the account ID and username. After publishing, it stores the media ID, permalink and publishing status that Instagram returns. Permissions used: instagram_basic, instagram_content_publish, pages_show_list and business_management.
YouTube (Google)
When YouTube publishing is turned on, an OAuth token with the youtube.upload scope only. After an upload, it stores the video ID, link and privacy setting. It does not read your channel's viewers, comments or analytics.
Google Drive
Read-only access to the Drive folder that holds the media to post. It stores file IDs, file names and a fingerprint (hash) of each file so the same file is not posted twice.
Post content
Captions, scheduled times, publishing results and error messages for each post.
Telegram
Draft previews and status messages sent to my own Telegram chat through the Telegram Bot API, so I can approve a post before it goes out.
Login and technical data
A session cookie that keeps me logged in (up to 14 days), a cookie that remembers the interface language, and standard server logs (IP address, time, request) used for security and debugging.

What the app does not do

It does not read your direct messages, followers, insights, comments, contacts or the personal data of people who view or interact with published posts.

It uses no advertising, no analytics or tracking tools and no third-party cookies. It does not sell, rent or share data for marketing, and it does not use data from Meta or Google to train AI models.

How the data is used

Data is used only to prepare, schedule and publish posts, to show their status, to avoid duplicate posts and to keep the app secure. Data received through the Meta and Google APIs is used only for these purposes and in line with the Meta Platform Terms and the Google API Services User Data Policy, including its Limited Use requirements.

Some drafts are prepared with AI tools. Caption text and visuals may be drafted with Anthropic's Claude, and voice-overs are made with a speech model that runs locally. Only the media and text I choose to publish are involved, and I review every post before it is published.

Who the data is shared with

Data goes only to the services needed to do the job: Meta (Instagram and Facebook) and Google (YouTube and Drive) to publish and fetch media, Telegram to deliver approval messages, and Anthropic when an AI draft is requested. Each acts under its own terms and privacy policy.

I do not share data with anyone else unless the law requires it.

Where data is stored and how it is protected

Data is stored in a PostgreSQL database on infrastructure I control. Access needs a password login; logins are rate-limited, and the session cookie is HttpOnly. Short-lived media links expire after two hours. No system is perfectly secure, but I limit access to myself and keep stored data to the minimum the app needs.

How long data is kept

Access tokens are kept while an account is connected and deleted when it is disconnected or access is revoked. Post records are kept so I have a history of what was published, and are deleted when they are no longer needed or on request. Server logs are kept only as long as needed for security and debugging.

How to delete your data

To remove Content Poster's access to Instagram or Facebook, open Facebook Settings, then Apps and websites (or Business Integrations), and remove the app. For YouTube or Google Drive, remove the app at myaccount.google.com/permissions. The tokens stop working immediately.

To have all stored data deleted, email gonencturkekul@gmail.com with the subject 'Content Poster data deletion' and the account name. I will delete the tokens, post records and logs linked to that account within 30 days and confirm by email.

Your rights

Depending on where you live, laws such as Türkiye's KVKK (Law No. 6698) or the EU GDPR may give you the right to access, correct, delete or move your data, and to object to or restrict its use. Email gonencturkekul@gmail.com and I will reply within the time the law allows. You can also complain to your data protection authority.

Content Poster is not meant for children and does not knowingly process children's data.

Third-party policies

Content Poster uses YouTube API Services. By using its YouTube features you also agree to the YouTube Terms of Service (youtube.com/t/terms), and the Google Privacy Policy (policies.google.com/privacy) applies. Meta's Privacy Policy (facebook.com/privacy/policy) applies to Instagram and Facebook data.

Changes to this policy

If the app's data use changes, I will update this page before the change takes effect. Last updated 4 November 2026.