Privacy Policy

Last updated 25 October 2026 · Türkçe (the Turkish text governs)

In short. livetoahundred publishes research-based health posts, and short explainer videos made from them. Our publishing app posts only to our own accounts. It also reads the statistics of our own accounts and posts: totals such as views, likes and the number of comments, and the breakdown of our followers as a group by country, city, age and gender, as the platform reports it. It does not read comments or messages, and it collects nothing that identifies the people who see, follow or interact with our posts. If you subscribe to the newsletter, we take only your e-mail address. This website uses no cookies. We count its visits with a cookieless counter (GoatCounter) that identifies no one. Questions or requests: info.live2a100@gmail.com.

1. Who we are

livetoahundred is run by one private individual living in Türkiye; it is not a company. It publishes as @livetoahundred on Instagram and on our Facebook, LinkedIn, TikTok and YouTube accounts. That person is the data controller (veri sorumlusu) under Turkish Law No. 6698 on the Protection of Personal Data (KVKK).

Contact: info.live2a100@gmail.com. Anyone who makes a request under section 10, and any competent authority, will be given the controller's full name and postal address on request, without delay.

2. What this policy covers

  • this website;
  • our publishing app, which runs on our own server: the Meta app livetoa100 (its Instagram part is called livetoa100-IG) for our Instagram professional account @livetoahundred and our Facebook Page, and the LinkedIn app livetoa100. It also uses the Zernio posting service for our TikTok and YouTube accounts;
  • the explainer videos we make from our posts and publish as Instagram and Facebook Reels and as TikTok videos (section 4);
  • our newsletter subscription (section 7);
  • e-mails you send us.

It does not cover Instagram, Facebook, LinkedIn, TikTok, YouTube or Telegram themselves. Their own privacy policies apply when you use them.

3. Our publishing app and platform data

The app is a private tool. Only we use it, and it acts only on accounts we own. Nobody else can connect an account to it. It handles:

PlatformData the app keepsWhy
Instagram (Meta)The access token for our account, our account ID and username, and the IDs of the posts it publishesTo publish our posts and check that they went out
Facebook (Meta)The access token for our Page, our Page ID and name, and the IDs of the posts it publishesThe same
LinkedInThe access token for our profile, our LinkedIn member ID and display name, and the IDs of the posts it publishesThe same
TikTok, YouTubeNo token: Zernio holds these connections. We send Zernio the images or video, caption and title of each post, and keep the ID of the post it createsThe same
Statistics (Instagram, Facebook, TikTok)Totals for our accounts and for each post we published: views, reach, likes or reactions, and comment, share and save counts; follower counts; and our followers' breakdown by country, city, age and gender as a percentage or count computed by the platform. For TikTok, also each post's share of views by traffic source and by followers versus non-followers, as TikTok reports it; Zernio supplies the TikTok figures. For our videos (Reels and TikTok videos), also play counts and average and total watch time. No names, user IDs, comment text or anything else that identifies a personTo see how our posts perform and which topics interest our readers

What the app never does. Meta's standard Instagram setup includes permissions to manage comments and messages (instagram_business_manage_comments, instagram_business_manage_messages). Our app does not use them. It uses instagram_business_manage_insights only to read the statistics described above for our own account. To publish to a Facebook Page, Meta requires four more permissions: pages_show_list and business_management, which let the app find our own Page, and pages_manage_posts and pages_read_engagement, which let it post, check that the post went out and read the reaction, comment and share counts of our own posts. read_insights lets it read our own Page's statistics. The app uses them only for our own Page. It does not read, store or answer comments or direct messages, and it does not collect data about individual followers, people who like or comment, or viewers: the statistics it reads are totals and percentages computed by the platform, with no names or user IDs. If we ever want to use the comment or message permissions, we will update this policy before we start.

We do not sell, rent or give away platform data. We do not use it for advertising or profiling, and we do not combine it with other data.

4. Research sources and people named in them

Our posts summarise published studies and news articles. To write a post, our tool downloads the study or article. That includes the author list and any contact details printed in it. The tool sends the text to an AI language model provider (currently OpenAI) to draft the post. A post may name authors, journals or people in the news, and it credits its source. We use this public information only to report on the work. KVKK Art. 28(1)(c) exempts processing for scientific purposes or within freedom of expression, provided it does not violate privacy or personal rights, and we keep within that limit.

Explainer videos. For some posts we also make a short video that explains the post. Anthropic (Claude) writes the script from the post and its source text. OpenAI draws the illustrations. ElevenLabs reads the narration with a synthetic voice. We put the video together on our own server: the illustrations stay still, and any charts are drawn there from the post's numbers. The videos show drawn characters, not real people. No personal data of readers or followers goes into them.

The full texts saved with each post are deleted from our server after 30 days. The title and abstract of every study the tool has considered, and up to 12,000 characters of the text of every news article it has considered, stay in our database as a record of what it has already seen. If you are named in a post and something is wrong, write to us and we will correct it.

5. Our private review chat on Telegram

Before a post is published, it goes to a private Telegram group that only people we invite can join. There it is approved, rejected or corrected. Instructions typed in that group are stored in our database for as long as we run the account, and they may be sent to the AI model provider to carry out the request. We do not store the names or Telegram user IDs of group members. Telegram keeps the chat history under its own policy.

6. Where data is kept and for how long

  • Access tokens and account IDs. They are stored on our own server in files that only our own server account can read. We keep them until they are replaced. We delete them when we remove the app's access to an account or stop using a platform, or when you ask (see Data deletion).
  • Publishing records (which post went to which platform, its post ID and its status). These stay in our database for as long as we run the account.
  • Working files for each post (images, video, captions and source text). These are deleted from the server after 30 days. For explainer videos, the working files (script drafts, narration, illustrations and clips) are deleted 30 days after the video is made; the finished video and its script are kept with the post. We also keep one archive of post files from 3 to 7 September 2026 (images, video and captions, without source texts) on the same server, with no set deletion date. A published post stays on the platform until we delete it there.
  • Statistics (see section 3). They are recorded once a day for our accounts and several times a day for recent posts, and stay in our database for as long as we run the account.
  • Database backups. These are kept on the same server for 14 days.
  • Newsletter subscribers. E-mail addresses and subscription records (confirmation date and IP address) are kept at Brevo until you unsubscribe. After that, the address stays only on a do-not-send list, so that you are not e-mailed again. Write to us if you want it removed completely.
  • Media for TikTok and YouTube. This is uploaded to Zernio and kept under Zernio's own terms. For Instagram, post images may be placed at a public web address so that Instagram can fetch them. Videos for Instagram and TikTok are uploaded to Zernio, which keeps them at a temporary public web address for 7 days so that the platforms can fetch them.

7. This website

This website sets no cookies and stores nothing in your browser. Visit counting. We use GoatCounter (goatcounter.com, outside Türkiye) to count visits. When you open a page, a small script loaded from this website itself sends GoatCounter the page's address and title, the address of the site you came from (if any) and your screen width. GoatCounter also sees your IP address and your browser's User-Agent line, and derives only your country, browser and operating system from them. Your IP address is not stored: to avoid counting the same visit twice, a one-way hash of the IP address, the browser details and a random number is kept in memory only, for at most 8 hours. The records hold no name, no IP address and no identifier that points to you; we see only totals: how many visits, which pages, which referring sites, which countries and device types. No age, gender or interest data is collected; the counts are not used for advertising and are kept for as long as the site runs. Apart from this, the website loads no third-party scripts or fonts. It is hosted on GitHub Pages by GitHub, Inc. (USA). GitHub logs every visitor's IP address for security purposes, whether or not the visitor is signed in to GitHub. We do not receive those logs. See GitHub's privacy statement.

Newsletter subscription. The only form on this website is the newsletter signup. When you submit it, your e-mail address goes straight to our e-mail service provider, Brevo (Sendinblue SAS, France), which also records your IP address and the time. You then get a confirmation e-mail; you are not subscribed unless you click its link. We use your address only to send the newsletter; we do not share it or use it for advertising. We do not track opens or clicks in our newsletters. Every issue has a one-click unsubscribe link.

8. E-mails you send us

If you write to us, we receive your address and your message through Gmail (Google). We use them only to answer you, and we delete them within 12 months of the conversation ending. The exception is a request under section 10: we keep it, with our answer, for as long as a complaint about it could still be made. Please do not send us your health information. If you do, we do not use it in our reply, and we delete it after replying.

9. Who receives data, and on what legal basis

RecipientWhat, and why
Meta Platforms (Instagram, Facebook)Our posts and Reels, and publishing requests, to publish them; requests for our own statistics
LinkedInOur posts, to publish them
Zernio, which forwards to TikTok and Google (YouTube)Images, videos, captions and titles, to publish them; requests for our own TikTok statistics
OpenAISource texts and review-chat instructions, to draft posts; scene descriptions, to draw video illustrations
AnthropicOur post texts and their source texts, to write video scripts
ElevenLabsVideo narration text, to produce the voice-over
TelegramDraft posts and review messages, for review
GitHubVisitors' IP addresses, for hosting and security
Brevo (Sendinblue SAS, France)Subscribers' e-mail addresses and subscription records, to send the newsletter
GoatCounter (goatcounter.com)The page opened, the referring site, browser, screen width and country, to count visits; no IP address is stored
Google (Gmail)E-mails you send us, to answer them
Public authoritiesOnly when the law requires it

These providers are based outside Türkiye, mostly in the USA and the EU, and data reaches them when we use their services. The data we send for videos is our own published content and published study texts, not information about readers or followers.

Legal bases under KVKK Art. 5(2):

  • Website logs, visit counts, e-mails, instructions typed in the review group and the statistics in section 3 rest on our legitimate interest in keeping the site secure, seeing which pages are read, answering you, and preparing and planning our posts (f). The logs, visit counts and group instructions are collected automatically, and e-mails partly automatically.
  • Requests under section 10 rest on our legal obligation to answer them (ç).
  • The newsletter subscription rests on your explicit consent under art. 5/1. You can withdraw it at any time with the link at the bottom of every issue or by writing to us.
  • Information made public by the people concerned rests on the fact that they made it public (d). Processing for research and news also falls under the Art. 28(1)(c) exemption (see section 4).

We make no automated decisions about you.

10. Your rights

Under KVKK Art. 11 you may ask us:

  • whether we process your personal data, and for information about it;
  • for what purpose we process it, and whether it is used for that purpose;
  • which third parties in Türkiye or abroad receive it;
  • to correct it if it is incomplete or wrong, and to delete or destroy it;
  • to tell the recipients about those corrections and deletions;
  • to object to a result against you that comes solely from automated analysis;
  • for compensation if unlawful processing causes you damage.

Readers in the EU also have the GDPR rights to restriction, portability and objection.

How to apply. E-mail info.live2a100@gmail.com in Turkish or English. Give your name and say what you are asking for. We accept requests by e-mail. We may ask for information to confirm that the request is yours. We answer free of charge within 30 days.

Complaints. You may complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) at sikayet.kvkk.gov.tr if we reject your request, answer it inadequately or do not answer in time. The deadline is 30 days after our answer, and no later than 60 days after your request. Readers in the EU may also complain to their local data protection authority.

11. Deleting data and removing the app

See Data deletion instructions: how to remove the app's access yourself, and how to ask us to delete data.

12. Changes

We update this page before any new kind of processing starts, and we change the date at the top. Every earlier version is public on GitHub. This policy is also available in Turkish. If the two versions differ, the Turkish one applies.