Legal

Privacy Policy

Last updated: November 6, 2026

This policy explains, in plain language, which personal data we process when you use Manaliza and why, who we share it with, how long we keep it, and the rights you have over it.

In short

We only process the data needed to provide the service: your account details, the content you upload and create, and the platform accounts you choose to connect.
We do not sell your data, we do not use it for advertising, and we do not use your content to train our own AI models.
We send content to YouTube or any other platform only when you choose it and ask us to.
You can disconnect your connected accounts at any time and ask us to delete your account and data.
For any question, reach us at info@manaliza.com.

1. Who we are and what this policy covers

Manaliza is a content production platform that offers a live streaming studio, AI-powered short video (Shorts) creation, SEO suggestions for YouTube videos and preparation tools for news teams. This policy applies to the manaliza.pro website, the web app and the Android app. On platforms such as Google, Meta and TikTok our app appears as Manaliza Pro.

In this policy, "Manaliza", "we", "us" and "our" mean Manaliza, which provides the service and is responsible for your personal data. For users in Türkiye, the notice under the Personal Data Protection Law No. 6698 (KVKK) is in our KVKK Notice.

2. What the service does

Reji Live: a live streaming studio that runs in the browser. Your guests join with an invite link, without creating an account. Broadcasts can be sent to YouTube and to other streaming destinations you add, and can be recorded.
Shorts: uses AI to create short clips, subtitles and covers from your videos and broadcast recordings, and, if you want, publishes or schedules them on your connected accounts.
SEO: creates title, description, tag and similar suggestions for your YouTube videos, and watches the channels you follow for new videos and live streams.
Editor's Desk (Editör Masası): rundown boards, a news library, bulletins and news videos, plus a voice room to talk with your team.
Teams: you share the same workspace with your teammates.
Connected accounts: YouTube and Google Calendar, plus Facebook, Instagram, Threads, TikTok and LinkedIn connections, which are being rolled out gradually.

3. What data we process

Account details: your email address, your account type and plan, and preferences such as language and theme. If you sign in with Google (currently in our Android app), we use only your verified email address from Google.
Sign-in and session data: the 6-digit sign-in codes we email you (we store only a hash of the code, never the code itself, and a code is valid for 10 minutes) and your device sessions, together with your IP address and browser information.
Team data: team name, members and their roles (owner, editor, viewer), and the email addresses of the people you invite.
Your content: the video, audio, image, logo and PDF files you upload; your broadcast recordings; your notes, boards, cards, broadcast plans and bulletins; the video and channel links you give us to analyze; and the clips, subtitles, covers and title, description and tag suggestions we create for you.
Live broadcast data: the camera video and microphone audio of you and your guests during broadcasts and preparation, the name and title your guests enter, the live chat messages your broadcast receives (the viewer's name and message) and poll votes.
Connected account data: the ID, name, username and profile picture of the platform account you connect, the permissions you grant and access tokens. Details are in sections 5, 6 and 7.
Payment data: payments are taken by Stripe. We never see or store your card number. We store your Stripe customer ID, your plan, subscription status, billing period dates and a record of payment events.
Usage records: your credit transactions, Shorts and SEO jobs, broadcast durations and a usage log of AI features (which feature, how much).
Technical logs: IP address, browser and device information, language, referring page, the cookies your browser sends, the action you took and error logs. We keep these for security, abuse prevention and troubleshooting.
Correspondence: emails and support requests you send us.
Stored in your browser: your session keys and preferences are stored in your browser. Details are in our Cookie Policy.

4. How we use your data

To create your account, recognize you and let you sign in.
To run the features you ask for: live streaming, recording, clip creation, SEO analysis, publishing, scheduling, calendar and notifications.
To make teamwork possible: members of the same workspace see and edit content as far as their roles allow.
To manage plans, credits and payments.
To send service emails: sign-in codes, team invitations, broadcast reminders, and notifications when a channel you follow goes live, when your analysis or content is ready, and when you run out of credits.
To keep the service secure, prevent abuse, and find and fix errors.
To meet our legal obligations.

We do not sell or rent your personal data and we do not use it for ad targeting. We do not use your content or data to train our own AI models.

5. Google user data (YouTube and Google Calendar)

5.1 YouTube API Services

Manaliza uses YouTube API Services. By connecting your YouTube channel to Manaliza you agree to the YouTube Terms of Service. How Google handles your data is described in the Google Privacy Policy.

5.2 Permissions we request and why

We request these permissions only when you start a connection:

Permission	What we use it for
Sign in with Google `openid` `email` `profile`	To let you sign in to your account in the Android app. Of the information Google provides, we use only your verified email address.
Upload videos to YouTube `youtube.upload`	To upload the Shorts and videos that you or your team choose to publish to the channel you connected.
Manage your YouTube account `youtube.force-ssl`	To show the name, ID and picture of the connected channel; to create the live broadcasts you start from Manaliza, bind them to a stream, start, end and, when needed, delete them; to update the title, description, privacy status and thumbnail of videos uploaded with Manaliza; to show your broadcast's live chat messages in the studio and post the results of polls you run to the chat.
Google Calendar events `calendar.events` `userinfo.email`	To add your broadcast plans, with reminders, to your Google Calendar and keep them up to date. We only create, change or delete events that Manaliza created. The email permission is used to show which Google account is connected.

5.3 Public YouTube data

For SEO analysis, Shorts creation and Channel Tracking, we read the public information of the video and channel links you give us (title, description, tags, statistics such as views, duration, live status, captions and transcript) through YouTube API Services. When you start a Shorts or SEO job for a video, we also process the video's audio and picture.

5.4 What we store

The ID, name and picture of the connected channel.
OAuth access and refresh tokens. YouTube tokens are stored encrypted in our database.
The IDs and status of videos, live broadcasts and calendar events created through Manaliza.
Live chat messages and poll votes from your broadcasts; these are deleted automatically after 30 days.
Information about the videos you analyze and the SEO suggestions we create.

5.5 Who we share it with

We do not sell Google user data, we do not use it for advertising, and we do not use it to develop, improve or train generalized artificial intelligence or machine learning models. We share this data only as far as needed to run the features we provide to you:

with your teammates in the same workspace;
with AI service providers, so they can create the output you asked for on your behalf (for example a video's title and transcript);
with our hosting and storage providers;
with competent authorities when security requires it or the law obliges us.

A member of our team looks at this data only with your permission (for example in a support request), for security reasons or when the law requires it.

5.6 Limited Use disclosure

Manaliza Pro'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.

5.7 How to revoke access

In Manaliza: go to Settings → Integrations and press "Disconnect" next to your YouTube channel or Google Calendar. When you disconnect YouTube, we revoke our access at Google and delete the stored tokens; when you disconnect Google Calendar, we also delete the tokens.
In your Google Account: you can remove Manaliza Pro's access at any time on the Google Account permissions page.

5.8 Retention and deletion

We keep data received from YouTube API Services only for as long as needed to provide the service, and we refresh or delete it within the periods required by the YouTube API Services Developer Policies. When you disconnect, the access tokens are deleted immediately. When you ask us to delete your account, we delete this data as well; see Data Deletion for how.

6. Meta data (Facebook, Instagram, Threads)

If you connect your Facebook Page, Instagram professional account or Threads profile, we request the permissions below from Meta. We use them only to publish the content that you or your team choose on that account, to show its publishing status, and to let you see and reply to comments on posts published through Manaliza.

Permission	What we use it for
`pages_show_list`	To list the Facebook Pages you manage. Only the Pages you select are connected.
`pages_read_engagement`	To read your Page's basic information, such as its name and picture, and post engagement.
`pages_manage_posts`	To publish the content you choose on your Page.
`pages_read_user_content`	To read comments on posts on your Page.
`pages_manage_engagement`	To reply to and manage those comments.
`instagram_business_basic`	To show your Instagram account's ID, username and profile picture.
`instagram_business_content_publish`	To publish the videos and posts you choose on your Instagram account.
`instagram_business_manage_comments`	To see and reply to comments on those posts.
`threads_basic`	To show your Threads profile's ID, username and picture.
`threads_content_publish`	To publish the posts you choose on Threads.
`threads_read_replies` `threads_manage_replies`	To see and manage replies to your posts.

What we store: the ID, name, username and profile picture of your account or Page, the list of permissions you granted, encrypted access tokens, and the IDs and status of posts made through Manaliza. We do not request or see your friend list, private messages or ad accounts.

Removing access and deletion: you can disconnect in Manaliza under Settings → Integrations, or remove Manaliza Pro in the "Apps and websites" settings on Facebook and the "Website permissions" (or similar) settings on Instagram and Threads. When Meta sends us a data deletion request, we automatically delete the connection data for that account and give you a confirmation code; you can check the code's status on the Data Deletion page.

These platform connections are being rolled out gradually. If a platform's connection does not yet appear in your account, or you have not connected that account, we receive no data from that platform.

7. TikTok and LinkedIn

TikTok (user.info.basic, video.publish): to show your account's ID, display name and profile picture and to send the Shorts clip you choose to your TikTok account. In line with TikTok's rules, the sharing screen shows your account name, privacy options and sharing settings; nothing is sent to TikTok until you press "Share". We read the post's status (such as processing or published) from TikTok.
LinkedIn (openid, profile, email, w_member_social): to recognize your account (name, profile picture, email) and to share the posts you choose on your behalf.

The access tokens for these accounts are also stored encrypted; you can remove a connection at any time under Settings → Integrations or in the platform's own app settings.

8. Other streaming destinations

If you add a streaming address (RTMP) and stream key to send your live broadcast to another platform, we store them only to send your broadcast to that address. Your stream key is secret; do not share it, and renew it on the platform if you think it has leaked.

9. Artificial intelligence

To create Shorts clips, subtitles, cover images, title, description and tag suggestions, news texts and similar output, your content (for example a video's audio, transcript, title, description, frames or broadcast moments) is sent to AI service providers. These providers process the content on our behalf and only to produce the output you asked for. We do not use your content to train our own AI models.

If you turn on the optional voice director suggestions in the studio, the host's audio is processed by a speech recognition service to understand commands and suggestions. This feature is off by default.

When we suggest images and videos for clips, we send only search terms to image search and stock media services. AI output can be wrong; check it before you publish.

Your teammates: members of the same workspace see content according to their roles.
Your guests and viewers: the video and audio that goes on air may be public on the platform you broadcast to.
Platforms you connect: the content we send at your request and the information needed for it (for example a title and description).
Our service providers: working on our behalf and under our instructions: cloud hosting, database and file storage (for example Microsoft Azure and Cloudflare), live video and audio infrastructure, email delivery, payments (Stripe), and AI and image search services.
BültenHub: the news library and news videos in the Editor's Desk work with the BültenHub news service. When you use these features, your email address is shared to match your account, and the related news content is shared for the news videos you request.
Competent authorities: when the law requires it, or when needed to protect our rights and our users.

We never sell your personal data.

11. International transfers

Because our service providers also have servers outside Türkiye, your data may be transferred abroad. We make these transfers in line with applicable law. Details are in our KVKK Notice.

12. How long we keep data

Data	Retention
Account details and your content	While your account is open, or until you delete it.
Sign-in code	Valid for 10 minutes; only a hash is kept.
Device session	Expires after 30 days without use, and in any case after 90 days at the latest.
Media uploaded for a broadcast	Removed from your list when the broadcast ends and permanently deleted about an hour later. Files in your brand library and files attached to Editor's Desk cards are kept.
Polls of ended broadcasts	Deleted when the broadcast ends.
Live chat messages and poll votes	30 days.
Broadcast recordings	While your account is open. Deleting a broadcast removes it from your list; if you also want the recording file deleted from our servers, write to us.
Shorts clip files	Deleted 7 days after they are created; information such as titles and text remains. Download or publish the clips you want to keep.
Deleted Shorts videos	Kept for 7 days in "Deleted videos", then permanently deleted.
Connected account access tokens	Until you disconnect; deleted immediately when you do.
Payment and invoice records	For the periods required by law.
Technical and security logs	For as long as needed for security and troubleshooting.

Copies of deleted data in security backups are deleted in the normal backup cycle.

13. Your rights and deleting your data

You can ask to access, correct or delete your data, and you can object to its processing. To do so, write to info@manaliza.com from the email address registered to your account.

Delete your account and data, disconnect connected accounts: Data Deletion.
Your rights under KVKK and how to apply: KVKK Notice.

14. Security

Connections are encrypted (HTTPS). Access tokens for YouTube and other connected platform accounts are stored encrypted in our database; sign-in codes and session keys are kept only as hashes; sign-in attempts are rate-limited; and access within a team is granted by role. No system is completely secure; if a data breach occurs, we will inform you and the relevant authorities as required by law.

15. Children

Manaliza is not designed for children under 16 and we do not knowingly collect their data. If you notice such a case, write to us and we will delete the data.

16. Cookies and browser storage

We keep small records in your browser to keep you signed in and remember your preferences. We do not use advertising or analytics cookies. Details are in our Cookie Policy.

17. Changes

We may update this policy. The latest date is shown at the top of the page; we announce significant changes in the service.

18. Contact

For any privacy question or request: info@manaliza.com. Other ways to reach us are on the Contact page.