Privacy Policy

Who we are

plan.video is the trade name of a Dutch eenmanszaak owned by Cihan Kat. The KVK number is 42183157 and the business address is Salland 1, 1948 RE Beverwijk, the Netherlands. Cihan Kat is responsible for the personal data this product handles. This policy covers the site, the dashboard and editor, the social accounts you connect, and AI agents you connect at plan.video/mcp. Questions go to hello@plan.video.

YouTube API Services

plan.video uses YouTube API Services. When you connect a YouTube channel, you agree to be bound by the YouTube Terms of Service, and Google handles your information under the Google Privacy Policy (http://www.google.com/policies/privacy).

What plan.video accesses: your channel’s identifier, name, and picture; a login that lets it upload to the channel and read its Analytics; and, when you open Analytics, the channel’s daily views, likes, and comments and the titles, upload times, and numbers of its most watched videos. It sends YouTube the video, title, description, privacy status, made for kids setting, and tags you choose.

How plan.video uses and processes it: the channel’s name and picture show which channel a post goes to. The login is used only to upload the videos you confirm or schedule and to read the numbers you ask to see; it is kept encrypted on plan.video’s server and never given to your browser. Analytics numbers are read from YouTube each time you open Analytics and are not stored, except in an assistant chat that used them. plan.video keeps the link to each video it posted so you can open it from your calendar.

How long plan.video keeps it: every day, plan.video checks with YouTube that you still allow its access and that each video it posted still exists, and it reads your channel’s name and picture again. If you have revoked access, plan.video deletes the login and the links to your videos; if a video was deleted on YouTube, plan.video deletes its link. An assistant chat that holds your YouTube numbers or video titles is deleted 30 days after its last message. Everything else is deleted when you disconnect the channel or delete your account, as described under How long it is kept.

With whom it is shared. Inside plan.video, only its owner runs the servers, and no one reads your YouTube data unless you ask for help with your account and agree to it, it is needed for security or abuse, or the law requires it. People you invite to a workspace that includes the channel see its name, its posts, and its Analytics. Outside plan.video, it goes only to: Google, which receives the video and its settings, since that is YouTube itself; Supabase, which stores your account; Hetzner, which hosts plan.video’s server; Anthropic, which receives your channel’s numbers and video titles only when you ask the plan.video assistant about them; an AI agent you connect yourself, only when it asks the Analytics tool; and authorities when the law requires it. Each is described under Google user data. plan.video does not sell YouTube data or use it for advertising.

How to remove access: disconnect the channel in plan.video’s Connections, which deletes the stored login and ends plan.video’s access at Google, or revoke plan.video’s access at any time on Google’s security settings page (https://security.google.com/settings/security/permissions). Deleting data plan.video stored does not delete anything from YouTube itself.

Questions or complaints about plan.video’s use of YouTube data go to hello@plan.video, or by post to plan.video, Salland 1, 1948 RE Beverwijk, the Netherlands.

Information we collect

Account details: your name, email address, and the profile information returned by Google when you sign in that way. An email link sign-in uses the address you enter. If you joined the waitlist or subscribed to the newsletter, the email address you gave.

Posts and media: the posts you plan, with their captions, titles, times, and settings, the videos, images, and audio you add, your media library, and your editor projects. They are saved on your account, so every browser you sign in to sees them, and a copy is kept in your browser so the dashboard opens quickly. If you use Auto-Captions, the video’s sound is sent to be transcribed. The caption tools that add emoji, pick keywords, or translate send the caption’s text.

Social connections: when you connect TikTok, Instagram, Facebook, Threads, YouTube, X, LinkedIn, Pinterest, or Bluesky, plan.video receives the account identifier, the display name, the picture, and a login for that network. Logins are kept on plan.video’s server, encrypted, and are never part of the account data your browser syncs. While you connect, the login passes through your browser once on its way to the server. For some networks your browser is later given a short-lived access token, held in memory for at most 30 minutes, so it can read posting options and numbers; it never gets the login that lasts. The media, caption, and settings of a post are sent to that network only after you confirm the post, or at the time you, a team member, or an AI agent you connected scheduled it.

YouTube: plan.video also receives the channel identifier, name, and picture, and sends the video, title, description, and privacy setting you confirm. plan.video’s server exchanges Google’s sign-in code itself and keeps the YouTube login encrypted there; the login is never given to your browser. While you connect, your browser holds a sealed copy of it that only plan.video’s server can open, and that copy stops working after 30 days. To fill in Analytics, plan.video’s server reads the channel’s daily views, likes, and comments, and the titles, upload times, and the same numbers for its most watched videos. Those numbers are fetched each time you open Analytics and are not stored, except in an assistant chat that used them, as described below. plan.video keeps the link to each video it posts. Disconnecting the channel in plan.video also ends plan.video’s access at Google. This use of YouTube data is covered by the Google Privacy Policy. You can revoke plan.video’s access on Google’s security settings page. When that access is revoked, plan.video deletes the YouTube data it stored for the connection. plan.video’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.

Instagram, Facebook, and Threads: you connect an Instagram professional account with Instagram’s own login, a Facebook Page with Facebook Login for Business, and a Threads profile with Threads’ login, and choose what plan.video may do. plan.video receives the account’s identifier, name, and picture, and a login for it, which is kept encrypted on plan.video’s server and never given to your browser in a form it can use. For Facebook, plan.video lists the Pages you manage, including those of the business portfolios you choose, so you can pick which to connect; it does not read or change anything else in those portfolios. When a post goes out, plan.video’s server sends its caption and the pictures and videos you confirmed, passing the files to Meta through links that stop working after a day. To fill in Analytics, plan.video’s server reads the account’s follower count and its recent posts with their captions, pictures, links, and their views, likes, and comment or reply counts. It reads only those counts, not the text of comments or who wrote them. Those numbers are fetched each time you open Analytics and are not stored, except in an assistant chat that used them, as described below. plan.video keeps the link to each post it publishes. Instagram and Threads logins last 60 days and are renewed while you use plan.video. plan.video does not sell this data, share it beyond the parties listed under “Who receives it”, or use it for advertising. Meta has no way for an app to end its own access to one account, so when you remove the account in Connections, plan.video deletes its login, and you can also remove plan.video in the network’s own settings, as the data deletion page describes.

Bluesky: you sign in with Bluesky and approve plan.video on your Bluesky server, or use your handle and an app password you make in Bluesky’s settings. An app password goes from your browser straight to your Bluesky server and is never stored. Either way, plan.video keeps the login Bluesky returns, encrypted on its server, and ends it when you disconnect the account. Your browser looks up handles and public profiles on Bluesky’s servers. Posts are sent to your Bluesky server only after you confirm or schedule them.

LinkedIn: plan.video receives your LinkedIn member identifier, name, and picture, and the permission to post on your behalf. It does not ask for your email address. A post, with its video or picture, goes to your own LinkedIn profile only after you confirm or schedule it; the file passes through plan.video’s server on its way and is not kept there. LinkedIn’s login lasts about 60 days, after which you reconnect the account. When you disconnect your profile, plan.video ends its access at LinkedIn. You can also remove it in LinkedIn’s settings, under Data privacy.

If you connect a LinkedIn company Page, plan.video also receives the Pages you manage, your role on them and each Page’s name, and the permission to post and comment as the Page and to read its posts and numbers. Posts and follow-up comments go to the Page only after you confirm or schedule them. When you open Analytics, plan.video reads the Page’s newest posts, the totals LinkedIn keeps for them (impressions, likes and comments), and its follower count. Those numbers are fetched each time you open Analytics and are not stored, except in an assistant chat that used them, as described below. plan.video doesn’t read the words of comments, who reacted or commented, or other members’ profiles. Removing a Page deletes its login from plan.video but doesn’t end the access at LinkedIn, because the same login covers your other Pages. You can end it in LinkedIn’s settings, under Data privacy.

TikTok: to fill in Analytics, plan.video reads your newest public videos’ titles, post times, and their views, likes, and comments so far. Those numbers are shown to you and are not stored.

Publishing records: for each post plan.video sends, whether it went out, the link to it on the network, and the error if it failed. If a post fails or a login is about to expire, plan.video can email you a notice with the post’s title or first line, the network, and what went wrong.

Support messages: when you use the support form, the email address you give, your message, whether it is a bug, a feature request, or a question, your browser, the page you came from, and, if you are signed in, your account. It is emailed to plan.video so it can be answered.

Billing: a Stripe customer id and the status of your plan. Card numbers are entered on Stripe’s pages and are not stored by plan.video.

Product mail: whether you have asked to receive product updates or announcements. Basic usage events, such as a page view, may be recorded to understand how the product is used. Google Analytics does that with a cookie, and only after you accept. Until then the tag does not run.

The assistant and AI agents

The plan.video Assistant, on the dashboard’s Assistant page and in the panel that opens from the corner of the dashboard, sends your messages, the accounts and media you pick, and the results of the tools it runs to Anthropic, which writes the answer. When you ask it about your numbers, those results include your Analytics, YouTube included. The chat, with those results, is saved on your account so you can open it again. plan.video keeps your 100 newest chats, and you can delete any of them.

You can also connect an AI agent of your own, such as Claude, ChatGPT, or Cursor, at plan.video/mcp. It gets access only after you sign in and allow it on plan.video’s consent page, and it works only while plan.video is open in your browser. It can then see your connected accounts, media library, and calendar, schedule, change, and delete posts, publish them when you ask, and read your Analytics. For each connected account, YouTube channels included, the Analytics tool returns the account’s handle, its views, likes, and comments for the period you ask about and the one before, how many posts it made, which weekdays and hours did best, and the titles, post times, and numbers of up to eight of its top posts.

plan.video sends this to an agent only when an agent you allowed asks for it. The request and the answer pass through plan.video’s server to your open plan.video tab and back, and the server does not log or keep them. An agent never receives your network logins. What it receives is then handled by the company that runs the agent, under its own privacy policy and your agreement with it, not under this policy. You can disconnect an agent at any time under MCP & CLI, Connected apps, in the dashboard, or in the agent’s own settings; it loses access within about a minute.

How it is used

The information is used to run your account, store your posts and projects, publish a post you confirm or send it at the time it was scheduled, show you Analytics, transcribe or rewrite captions when you ask, answer the assistant and the AI agents you connect, email you about a failed post or an expiring login, send the newsletter if you subscribed, apply your plan’s limits, take payment, keep the service secure, find and fix errors, and reply if you write to us. plan.video does not sell personal information.

Who receives it

  • Supabase runs the database and sign-in.
  • Cloudflare stores the files you upload, in its EU region. When you sign in with your email, Cloudflare Turnstile also checks that you’re a person, using your IP address and details of your browser.
  • Hetzner hosts plan.video’s servers, which keep the network logins and send scheduled posts.
  • Stripe processes payments, and Link, Stripe’s payment service, sells the paid plans. They receive your email address, your plan, and what you enter at checkout.
  • Resend delivers plan.video’s emails, such as sign-in links, team invitations, failed post notices, and messages sent with the support form, and receives the address and the email’s contents.
  • Anthropic runs the plan.video assistant and the caption tools that add emoji, pick keywords, or translate. It receives what you ask, what it needs to answer, and the caption’s text.
  • ElevenLabs transcribes the sound of a video when you use Auto-Captions and sends back the words and their timing.
  • An AI agent you connect at plan.video/mcp receives what its tools return, as described above.
  • Sentry, hosted in the EU, receives a report when plan.video runs into an error: what went wrong, the page it happened on, and your browser and system. It keeps no IP address, sets no cookies and is used only to find and fix errors, so it runs whatever you choose for analytics. Sentry’s policy is at sentry.io/privacy.
  • When you accept analytics, Google receives the page you are on and the pages you open afterwards. Google’s policy is at policies.google.com/privacy. PostHog, hosted in the EU, receives those pages and actions you take in the app, such as signing in or saving a post, linked to your account id. PostHog’s policy is at posthog.com/privacy.
  • Removing a background downloads a model from Hugging Face; the picture stays on your device. Caption previews load fonts from Google Fonts. These services see your IP address.
  • A social network receives a post when it is sent, and what you connect it with.
  • People you invite to a workspace see that workspace’s posts, connected accounts, and their Analytics, in the role you give them. People you send a preview link to see that post, and the name they enter with a comment is shown to you.
  • Authorities, if the law requires it, or to protect the security of the service or its users.

These providers may process data outside your country. Where that happens, plan.video relies on the provider’s contractual protections for the transfer.

Google user data

Google user data means the name, email address, and picture Google returns when you sign in with Google, and the YouTube data described above: the channel’s identifier, name, and picture, its login, the links to videos plan.video posted, and the views, likes, comments, titles, and upload times read for Analytics.

plan.video shares, transfers, or discloses Google user data only with these parties, and only to provide the features you use:

  • Supabase stores your Google sign-in details, your connected YouTube channel’s identifier, name, and picture, its login encrypted with a key Supabase does not have, the links to videos plan.video posted, and any assistant chat that read your Analytics, so they work in every browser signed in to your account.
  • Hetzner hosts the server that exchanges the YouTube login with Google, holds the key that opens it, reads Analytics from YouTube for you, and passes your video to YouTube when it is sent. The video is not kept there.
  • Anthropic receives your YouTube channel’s numbers and the titles of its most watched videos only when you ask the plan.video assistant about them. Anthropic uses them to answer that request and does not use them to train its models.
  • An AI agent you connect at plan.video/mcp, such as Claude, ChatGPT, or Cursor, receives your channel’s handle, its numbers, and the titles, upload times, and numbers of its top videos only when it asks the Analytics tool for them, after you allowed it on plan.video’s consent page and while plan.video is open in your browser. It never receives the YouTube login. The company that runs the agent handles that data under its own policy and your agreement with it.
  • People you invite to a workspace that includes the channel see its name, its posts, and its Analytics.
  • Google receives the video, title, description, and privacy setting you confirm, since that is YouTube itself.
  • Authorities, if the law requires it, or to protect the security of the service or its users.

plan.video does not sell Google user data, does not use it for advertising, and does not use it to train or improve AI or machine learning models. No one at plan.video reads it, unless you ask for help with your account and agree to it, it is needed for security or abuse, or the law requires it.

How it is protected

All traffic between your browser, plan.video’s servers, and the providers above is encrypted with HTTPS (TLS). Supabase and Cloudflare encrypt stored data at rest.

Each account’s rows in the database can only be read by that signed-in account, enforced by row-level security. plan.video’s servers check your sign-in before they act for you.

Network logins are encrypted with AES-256-GCM using a key that only plan.video’s publishing server holds. Each one is tied to its own account, so it cannot be opened for anyone else, and they sit in a table no browser can read. Logins are renewed only on the server. A YouTube login never leaves it.

The YouTube login uses OAuth with PKCE. The client secret stays on plan.video’s server and is never sent to the browser. plan.video asks only for the YouTube permissions it needs to post and to show Analytics.

An AI agent’s access works only at plan.video/mcp. It cannot read the database directly, sign in to your account, or change your email address or password.

Access to production systems and secrets is limited to the owner of plan.video. Secrets are kept in files only the services that use them can read. Disconnecting YouTube revokes plan.video’s access at Google and deletes the stored YouTube login.

How long it is kept

  • Your account, posts, media library, projects, connected accounts, and publishing records: while your account is open. You can delete any of them yourself.
  • Uploaded files: until you delete them, the post they belong to, or your account. Files of a post that went out are kept so you can post it again.
  • Network logins: until you disconnect the account or delete your account. plan.video also ends its access at the network where the network allows it. Meta and LinkedIn company Pages don’t let an app do that, so plan.video deletes the login and you can remove plan.video in that network’s own settings. The sealed YouTube copy your browser holds while connecting stops working after 30 days.
  • YouTube data: checked with YouTube every day, as described under YouTube API Services. The login and video links of a channel whose access you revoked, and the link of a video deleted on YouTube, are deleted at that check.
  • Analytics numbers: not stored. They are fetched again each time, except in assistant chats.
  • Assistant chats: until you delete them, and only your 100 newest. A chat holding YouTube numbers or video titles is deleted 30 days after its last message.
  • Safety copies of account data that was changed or deleted, kept so a mistake can be undone: 30 days.
  • Failed post and expiring login notices: 30 days.
  • Counts of each day’s uploads, used for plan limits: 2 days.
  • Team invitations: until they are accepted or removed.
  • Support messages: as long as needed to answer them, and at most 2 years.
  • Server logs: 30 days.
  • Error reports in Sentry: at most 90 days.
  • Usage events in Google Analytics and PostHog: at most 14 months.
  • The waitlist email address: until you ask for it to be removed.
  • The newsletter email address: until you unsubscribe or ask for it to be removed.
  • Billing records: 7 years, as Dutch tax law requires.

Deleting your account from the product deletes it at once: plan.video ends any paid plan, erases your files, ends its access at each connected network that allows it, and deletes the account and everything stored with it, and the browser you delete it from forgets its copy. A safety copy of your data, described in the list above, goes within 30 days. Comments you left on someone else’s preview link stay with their post. The copy of your posts kept in another browser stays until you clear that browser’s data for plan.video. A post that has already gone out to a social network stays there under that network’s own rules.

Your choices

You can disconnect a social account or an AI agent, delete assistant chats, turn off product mail, and delete your account from the product. The steps are on the data deletion page. You can ask for a copy of your account information, a correction, or deletion by emailing hello@plan.video. If you are in the EEA or the UK, you can also object to certain processing and lodge a complaint with your data protection authority. Analytics stay off until you accept the notice on the site, and this browser remembers that choice. Change your analytics choice.

Children

plan.video is not for anyone under 16. A social network you connect may require a higher age. Do not connect an account you are not allowed to use.

Changes

This policy can be updated by posting a new version on this page. The date above changes when that happens. The terms of service cover use of the product.

Contact

For questions, requests, or complaints about your data or this policy, email hello@plan.video or write to plan.video (Cihan Kat), Salland 1, 1948 RE Beverwijk, the Netherlands.