Privacy Policy

Last updated: October 23, 2026

This Privacy Policy explains how Bardiyah collects, uses, stores, and protects personal information when you use our website and content production platform.

Information We Collect

We may collect the following categories of information:

  • Account information such as your name, email address, and encrypted password.
  • Workspace data that you create inside the platform, including projects, scripts, schedules, tags, and content records.
  • Integration data that you choose to connect, such as Meta page/account identifiers and access tokens required to fetch social performance metrics.
  • Technical information such as browser type, IP address, device information, and usage logs.
  • Communication data when you contact us through forms or support channels.

How We Use Your Information

We use collected information to:

  • provide and maintain the platform,
  • authenticate users and secure accounts,
  • save and display your content workspace data,
  • fetch connected platform metrics when you explicitly link external accounts,
  • improve performance, reliability, and product features,
  • respond to support requests and operational issues,
  • comply with legal obligations and prevent abuse.

Legal Basis

Where required by applicable law, we process information based on one or more of the following grounds:

  • your consent,
  • performance of a contract with you,
  • compliance with legal obligations,
  • our legitimate interests in operating and securing the service.

Meta and Social Integrations

If you connect Facebook, Instagram or Threads through Meta, we store the minimum information required to maintain that connection, retrieve the metrics you requested and the comments on your posts, publish the posts you schedule for automatic publishing at their time, and reply to, hide or delete comments when you ask us to. This may include:

  • your Meta user identifier,
  • selected Facebook page identifier,
  • selected Instagram business account identifier,
  • encrypted access tokens,
  • granted scopes and connection timestamps.

We use this information only to support the connected features in your account. You can disconnect the integration from your settings at any time.

Social Platform Connections

Connecting a social platform is optional and always starts with you. Nothing is connected automatically, and the platform is only contacted after you have signed in there and approved the connection.

What we read

For TikTok, we read the connected account’s profile, meaning its username, avatar, and follower count, together with that account’s own videos and the public performance metrics those videos report. When you publish to TikTok from Bardiyah, we also read that account’s posting settings, as described under TikTok below. We read nothing else, and we never read another account’s data.

Meta connections are described in the section above. YouTube works in two ways. Without any connection, you paste a public video URL, and we read that video’s public figures through the YouTube Data API using our own developer credentials; you are not asked to sign in to YouTube, and we hold no access token for your channel. You can also choose to connect your own channel, to read it or, when you turn on publishing to YouTube, to upload the videos you schedule, as described under YouTube below. Because this uses YouTube API Services, Google’s handling of the data it receives is governed by the Google Privacy Policy.

Reading, and publishing only what you schedule

A social platform connection reads the data described here. Bardiyah never posts, uploads, edits, or deletes anything on a connected platform on its own initiative: it publishes only a post you scheduled for automatic publishing, at the time you set, with the text, media and settings you chose. For TikTok and YouTube this is described under TikTok and YouTube below.

How access tokens are stored

Access tokens are encrypted at rest in our database. They are never shared with third parties, never sent to your browser, and never exposed to any client application. They are used only by our servers, only to make the requests described above: reading your data, and publishing the posts you schedule. The one exception is Google Drive's short-lived picker token, described under Google Drive below.

Performance records over time

Platforms report the figures they hold today, not a history. So that you can see how a video performs over time, we record a daily snapshot of the metrics for the content you have linked. These records live in your workspace and are kept for as long as your account is active. They are removed when you delete the record, delete the content it belongs to, or delete your account.

Disconnecting

You can disconnect any platform at any time from the Integrations settings page. Disconnection takes effect immediately: we revoke the access token with the platform where the platform supports it, we delete the stored token, and we stop collecting any further data from that account.

Performance records already collected stay in your workspace, because they are part of your own reporting history. Delete them, the content they belong to, or your account, and they go with it. The exceptions are data read through a connected YouTube channel and through TikTok, which follow the rules under YouTube and TikTok below.

The platforms' own policies

Once you connect an account, that platform’s own privacy policy governs how it handles your data on its side. Please review the policy of any platform you connect.

TikTok

When you connect your TikTok account to Bardiyah, we ask for your permission to access specific data, and we use it only to provide what you asked for:

  • Basic account information: your ID, username, display name and avatar. We use it to show the connected account inside Bardiyah.
  • Account statistics: your follower count. We use it to show how your account is performing.
  • Your videos and their numbers: we use them so you can pick the video you published and follow its numbers in the content calendar.
  • Your posting settings at the time of posting: display name, available viewing options, comment, Duet and Stitch settings, and the maximum video length. We use them to show you the right options before posting.

Publishing from Bardiyah to TikTok

When you schedule a post for automatic publishing to TikTok, Bardiyah publishes it to your account on your behalf, using the publishing permission you granted when you connected the account. In detail:

  • What we send to TikTok: the video or photos you chose for the post, with their content exactly as it is; only a photo in a format TikTok does not accept has its format converted to JPEG. With them we send the text you wrote for TikTok and the settings you chose yourself: who can watch, whether comments, Duet and Stitch are allowed, the commercial content disclosure, and the AI generated content label.
  • When we send it: only at the time you set, or immediately if you press "Publish now". Until then the post stays in Bardiyah and nothing from it reaches TikTok.
  • Only with your consent: we send no post before you review its settings and agree to TikTok's Music Usage Confirmation, and to TikTok's Branded Content Policy when you disclose branded content. If you edit the post's settings, text or media after consenting, we ask for your consent again before publishing.
  • One hour before the time: we ask TikTok for your account's status and its available posting options, to make sure the post will be published as you chose. No content is sent at this step.
  • How the file travels: we upload the video from our storage to TikTok's servers through TikTok's official posting API. For photos, we place a temporary copy of each photo at an unlisted link on Bardiyah's domain for TikTok to fetch, and delete those copies when publishing ends. We do not share your content with anyone other than TikTok.
  • What we keep after publishing: the publishing status, the post's TikTok ID and link, your settings and the time of your consent, the posting details we read from your account at the time of posting, and a log of what happened and when, so we can show you the result and track the post's numbers in your content calendar.
  • If publishing fails: we tell you why straight away. If your account reached TikTok's daily posting limit, we try again every hour until the post goes out or you stop it, up to 24 attempts.
  • What we never do: we never publish anything you did not schedule, never change the viewing option you chose, never add a logo, watermark or link to your content, and never edit or delete any post already on your TikTok account.
  • How to stop publishing: at any time before the post's time you can turn it into a reminder you publish yourself, or pause automatic publishing for the whole project. You can disconnect your account from the "Integration settings" page so Bardiyah stops publishing to it for good, or remove Bardiyah's access from the TikTok app's settings.

Keeping your data safe: your account access tokens are stored encrypted. We do not sell your TikTok data, share it with anyone else, or use it for advertising.

Disconnecting and deleting your data: you can disconnect your account at any time from the "Integration settings" page in Bardiyah. When you disconnect, we delete your access tokens immediately, along with the TikTok account data and the video numbers we stored; only the link to each video you linked stays on your calendar, without its numbers. You can also remove Bardiyah's access from the TikTok app, in its security and permissions settings. To ask us to delete any other data, email info@bardiyah.net.

To learn how TikTok handles your data, see TikTok's Terms of Service and TikTok's Privacy Policy.

Google Drive

Connecting Google Drive is optional. It lets you choose images and videos for your posts from your own Drive, using Google's file picker.

What we access

We ask Google for a single permission: access to the files you choose in Google's picker. We cannot see, list or open any other file in your Drive. For each file you choose, we read its name, type, size, dimensions, duration, a small thumbnail and its link, so the file can appear in your post. We also read the e-mail address of the Google account you connect, to show you which account is connected.

Why we access it

Only to attach the files you chose to your posts in Bardiyah and to show them back to you there. We do not sell information from your Google Drive, use it for advertising, or use it to train AI models.

Copying a file into Bardiyah

A file you choose stays in your Drive, and Bardiyah keeps only a link to it. Only when you choose "Copy to Bardiyah" on a file do we download that one file and store it with your post, so it stays available even if it is later removed from your Drive. We never copy a file unless you ask.

Tokens and disconnecting

Your Google Drive tokens are encrypted at rest. When you open Google's picker, your browser receives a short-lived access token so the picker can show your files; the long-lived token never leaves our servers. You can disconnect Google Drive at any time from the Integrations settings page: we revoke the access with Google and delete the stored tokens. Files you copied into Bardiyah stay with your posts, and Drive links stop showing until you connect again. You can also remove Bardiyah's access from your Google account settings at any time.

Google API Services User Data Policy

Bardiyah's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

YouTube

Connecting a YouTube channel is optional. It lets you pick a video from your own channel when you mark a scheduled post as published, instead of pasting its link, and follow that video's figures in Bardiyah. When you turn on publishing to YouTube, it also lets Bardiyah upload to your channel the videos you schedule. Bardiyah uses YouTube API Services to do this. By connecting a channel you agree to be bound by the YouTube Terms of Service.

What we access

Depending on what you turn on, we ask Google for one of two permissions to your YouTube account:

  • Read only (youtube.readonly), when you connect a channel to pick your videos and follow their figures.
  • Manage your YouTube account (youtube.force-ssl), when you turn on publishing to YouTube. This permission includes everything the read only permission allows, and lets Bardiyah upload the videos you schedule.

With either permission we read:

  • your channel's title, handle and picture, and its subscriber and video counts;
  • the list of videos you uploaded, including unlisted and private ones, with each video's title, thumbnail, privacy status, publish or scheduled time, duration and view count;
  • for the videos you link to a script or publish from Bardiyah: their views, likes and comments.

With the publishing permission we also read:

  • whether your channel can upload videos longer than 15 minutes;
  • your playlists' titles, so you can choose one for a video, and YouTube's lists of video categories and languages;
  • the status of the videos Bardiyah uploads for you.

Publishing from Bardiyah to YouTube

When you schedule a post for automatic publishing on YouTube, Bardiyah uploads it to your channel on your behalf, with the publishing permission you gave it. This is exactly what happens:

  • What we send: the video you chose for the post, unchanged, and the details you set for YouTube in Bardiyah: title, description, tags, thumbnail, visibility, whether it is made for kids, category, language, playlist, whether it contains altered or synthetic content, and whether to notify your subscribers. We never add a logo, watermark, intro, link or promotional text.
  • When we send it: only after you press «Schedule post» or «Publish now», or «Upload again» after you deleted the video in YouTube Studio. If Bardiyah's daily upload limit on YouTube is reached, the upload is tried again automatically when the limit renews. A video you schedule as public for more than 30 minutes ahead is uploaded right away as private, with your publish time set inside YouTube, so you can see it in YouTube Studio straight away, and YouTube itself publishes it at that time. A video you schedule as unlisted or private, or that is due sooner, is uploaded right away as private, and at your time Bardiyah changes only its visibility to the one you chose.
  • After it is uploaded, the video is yours on YouTube. You edit or delete it in YouTube Studio. Bardiyah never edits, replaces or deletes a video on your channel. If you delete it in YouTube Studio, you can ask Bardiyah to upload it again.
  • What we read back: the video's ID, its upload, processing and privacy status, any reason YouTube gives for refusing it, its title, thumbnail and publish time, so we can show you its status and link it to your post. We read it when you open the post, an hour before the publish time, and at that time, to check that the video is still there.
  • What we keep: the video's ID and link, its upload and publishing status, the details you set for it, and a log of what happened and when, so we can show you the result and follow its figures in your content calendar. For each channel we also remember the last audience, category and language you chose, so your next post starts with them. Details we read from YouTube are refreshed while the post is active and deleted when they have not been refreshed for 30 days.

Bardiyah never deletes anything on your channel, never comments, likes or subscribes on your behalf, and never uploads anything you did not schedule yourself.

How Bardiyah uses each YouTube permission

  • Read only (youtube.readonly): we call channels.list to show the channel you connected, and playlistItems.list and videos.list to list your own videos and show their public figures (views, likes and comments) in your content calendar, and to let you link a post to a video you already published.

  • Manage your YouTube account (youtube.force-ssl): used only to publish the posts you schedule, and only after you press «Schedule post» or «Publish now». With it we:

    • upload the video with videos.insert, with the details you set;
    • set the thumbnail you chose with thumbnails.set;
    • add the video to the playlist you chose with playlistItems.insert;
    • read your playlists and YouTube's lists of categories and languages (playlists.list, videoCategories.list, i18nLanguages.list) to show you the choices;
    • read your channel's status (channels.list) to know whether it can upload videos longer than 15 minutes;
    • read the video's status (videos.list) to show you whether it uploaded and finished processing;
    • read your channel's newest uploads (playlistItems.list and videos.list) when an upload is interrupted, so the same video is never uploaded twice;
    • at your post's time, change only the video's visibility with videos.update to the visibility you chose (for example «Unlisted»), when YouTube cannot apply it in advance.

    This permission also covers everything the read only permission allows, so we ask you for only one of the two.

  • Nothing else: we do not use either permission to delete anything, edit any other detail of your videos, comment, like or subscribe, act on any channel other than the one you connected, or for advertising. Bardiyah's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Why we access it

Only to let you pick a video in scheduling, to show your connected channel on the Integrations settings page, to show each linked video's figures in your scripts' performance reports, and, when you turn on publishing, to upload the posts you schedule and show you their status.

Where it is stored, and who sees it

What we keep is stored in Bardiyah's database on our own servers, inside your account. It is never sold, never shared with third parties, never used for advertising, and never used to train AI models.

How long we keep it

  • The list of your channel's videos is read when you open the picker and is not stored; it is held in memory for at most 10 minutes so the picker opens quickly.
  • Your channel's details (title, handle, picture and counts) are refreshed every day while you are connected. Any detail that has not been refreshed for 30 days is deleted.
  • A video's figures (views, likes, comments) are refreshed every day while the video is linked to a script. Figures that have not been refreshed for 30 days are deleted.
  • When you pick a video, we keep only what we would keep for a pasted link: the video's ID and its URL. These are your own publishing record and stay with your schedule.

Tokens and disconnecting

Your YouTube tokens are stored encrypted and never leave our servers. You can disconnect YouTube at any time with the Disconnect button on the Integrations settings page: we revoke the access with Google, delete the stored tokens straight away, and delete all data we stored through the connection within 7 days (in practice the same day). The same happens if Google tells us the access was revoked, and when you delete your Bardiyah account. Your scripts and schedule stay as they are; their video links go back to working like pasted links.

Disconnecting stops any upload that has not started. Videos already uploaded stay on your channel, and YouTube still publishes scheduled ones at their time unless you delete them or change their time in YouTube Studio.

You can also remove Bardiyah's access at any time from your Google account's permissions page at https://myaccount.google.com/permissions, or from Google's security settings at https://security.google.com/settings/security/permissions.

Google's privacy policy

Google's handling of your data is described in the Google Privacy Policy.

Google API Services User Data Policy

Bardiyah's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

MCP and AI Assistant Integrations

What an MCP connection is

MCP, the Model Context Protocol, is an open standard that lets an AI assistant work with an external service on your behalf. Connecting Bardiyah over MCP means an assistant such as ChatGPT or Claude can read and write your ideas, projects, and scripts while you talk to it, instead of you moving between two applications. In plain terms, it is a door between that assistant and your Bardiyah account, and you decide whether it is open.

You open the connection, not us

Every MCP connection is started and authorized by you. We never create one on your behalf. No assistant reaches your account until you have signed in to Bardiyah and approved the connection on our consent screen, where the requested permissions are listed before you agree to them.

What moves, and what we do with it

When a user connects Bardiyah to ChatGPT, Claude, or any other MCP client, the requests and the data needed to carry out those commands may be sent to Bardiyah.

We process that data for operating the service, providing the features the user requests, maintaining them, and improving their operational functionality, without using user content to train AI models except with explicit consent. Bardiyah does not use user content to train its own AI models unless explicitly stated and consented to.

What a connected client can reach

A connected client can reach only your own content, and only within the permissions you granted when you approved the connection. It cannot reach another user’s workspace, and it cannot exceed the permissions you granted. Narrower permissions mean a narrower door.

The assistant’s policy governs its own handling

Once data reaches ChatGPT, Claude, or any other client, that client’s privacy policy governs how it is stored, processed, and used from that point on. We cannot control, audit, or undo how a third-party assistant handles data after it leaves our systems, and we cannot delete it there on your behalf. Please read the privacy policy of any assistant before you connect it.

Disconnecting

You can disconnect any MCP connection at any time from the MCP server page in your settings. Disconnection takes effect immediately: the client’s access token is revoked, and that client can make no further requests to your account.

Retention after disconnection

Disconnecting deletes the stored authorization for that client. Your own workspace content is unaffected and stays exactly as you left it, because the connection was a way in, not a copy.

Anything the assistant already received sits with that assistant, under its own policy and its own retention rules. Removing it there is done through that service, not through Bardiyah.

Data Retention

We retain your information for as long as your account remains active or as needed to provide the service, resolve disputes, enforce agreements, and comply with legal obligations.

When you remove integrations or delete content, related records may be removed or anonymized according to operational and legal requirements.

Sharing of Information

We do not sell your personal information. We may share information only in the following cases:

  • with service providers who help operate the platform,
  • when required by law or valid legal process,
  • to protect the rights, security, and integrity of the platform and its users,
  • in connection with a merger, acquisition, or asset transfer.

Security

We apply reasonable technical and organizational safeguards to protect data, including encryption for sensitive stored credentials where applicable. However, no method of transmission or storage is completely secure.

Your Rights

Depending on your location, you may have rights to:

  • access your personal information,
  • correct inaccurate data,
  • request deletion of your data,
  • object to or restrict certain processing,
  • withdraw consent where processing is based on consent.

You may contact us to exercise these rights.

Third-Party Services

Our service may link to or integrate with third-party platforms such as Meta, YouTube, TikTok, and others. Their privacy practices are governed by their own policies, and you should review those separately.

Contact

If you have questions about this Privacy Policy or your personal data, please contact us through the website contact form or the support channel made available by the service.