Privacy Policy

Last updated 4 October 2026

Kadenza helps you run your content and leads across LinkedIn, Instagram and YouTube. This policy explains what we collect, why, who we share it with, how long we keep it and how you get it deleted, and we keep it specific to what the app actually does. The controller of your account data is Kadenza.ai. For anything about your data, email support@kadenza.ai.

What we collect

Only what the app needs to work:

• Your account: your email address and name, and the API keys you create for our API and MCP. We store only a one-way hash of each key, never the key itself.
• Connected accounts: when you connect LinkedIn, Instagram or YouTube, we store the account's id, its display name and the access it granted us, with any access token kept encrypted. We never see or store your social-account password.
• Your content: your drafts, the posts you publish and schedule through Kadenza, your brand voice and research answers, and the files you upload to your storage.
• Research: the competitors you choose to track and their public posts and numbers, copies of those posts' pictures (every slide of a carousel) saved in your account's storage, transcripts of videos you ask us to transcribe, and the comments you fetch on a post with the Comment Fetcher. Kadenza doesn't collect competitors' comments on its own.
• Messages: the LinkedIn and Instagram conversations on your own connected accounts that you sync into your inbox, and the messages you send from Kadenza.
• People you add: the prospects you add yourself and the public activity of theirs we save on your posts, and the leads who give their details to one of your lead magnets.
• Public-form safety data: on our public lead forms we process a CAPTCHA result and keep short-lived, one-way fingerprints made from a visitor's IP address plus request counts. We use these only to stop spam and repeat counting. They cannot be turned back into an IP address and expire after 48 hours.
• How you use the app, like the pages you open and the buttons you press, so we can make it easier to use. We never record what you type.
• Technical records like error logs that we need to keep the app running and secure.

Signing in with Google

If you sign in with Google, Google shares your name, your email address and your profile picture with us. We use them only to create your account and keep it secure: your email and name go on your profile, and your picture is shown in your account menu straight from Google's own link, so we don't keep a copy of it. Signing in with Google doesn't connect your YouTube channel. That's a separate step, described below, and only if you choose it.

LinkedIn

When you connect LinkedIn, Kadenza acts on that account only for the things you or your own AI ask for: publishing and scheduling your posts, reading your inbox and sending the messages and replies you ask for, sending invitations and follow-up messages to the prospects you added yourself, and the engagement you turn on, like viewing profiles, reacting and commenting. Kadenza doesn't go looking for prospects for you. We save whether the invitations you sent were accepted, so you know who's connected, and the comments on your own posts that relate to your lead magnets, so you can follow up with the people who took part.

Instagram

When you connect an Instagram business or creator account, Kadenza uses it to publish and schedule your posts, show your own account's results, and handle the replies and private messages for the lead magnets you set up. For that we process the username of the person who got in touch, their comment or message, and the conversation's id. A person only ever hears from you after they reached out first. If they share their email, it becomes one of your leads and goes on to the email tool you connected, like any other lead. If you turn on Instagram engagement, Kadenza also does the actions you approve on your account, like liking a post or replying to a comment.

For competitor research on Instagram we use only public information: public profiles, posts, their numbers and pictures. We don't use anything from a private account.

YouTube and Google data

Connecting your YouTube channel is optional, and everything below only applies if you do it. When you connect, you are also agreeing to the YouTube Terms of Service, and Google's own handling of your data is covered by the Google Privacy Policy. We use the Google and YouTube APIs for this.

We ask Google for three permissions, and here's exactly what each one is for:

• Upload videos (youtube.upload) so a video you choose goes out on your own channel, straight away or at the time you picked in Kadenza. We upload only videos you chose, with the title, description and privacy you set.
• View your YouTube account (youtube.readonly) so we can show which channel is connected and read your own videos and their numbers for your results.
• View your YouTube Analytics reports (yt-analytics.readonly) so the results you see, like views, watch time and subscribers gained and lost, are your real figures rather than an estimate.

When you connect YouTube, Kadenza keeps a secure key that lets it post and read your numbers for you, and it saves your channel's name, picture and ID. If you let Kadenza see your channel's numbers, we save them day by day, like views and subscribers, along with the numbers for each video you post through Kadenza. We don't read or store comments on your channel.

While your account is active, we read your channel's numbers again from YouTube regularly, and we check each video again once twenty days have passed since we last read it. While your account is active, if we haven't read your channel's name and picture for twenty days, for example because you didn't let Kadenza see your numbers, we read them and your channel's ID again. We keep checking that you still let Kadenza use your YouTube account. If your account is active and we can't confirm that for twenty-five days, we remove your channel's saved name and picture and delete the numbers we couldn't confirm, and YouTube stays connected. If your account is locked, for example because your plan has ended, and we can't confirm it for twenty-five days, we disconnect YouTube the same way you would, and you can connect it again once your account is active. If a video is deleted from YouTube, we delete its numbers as soon as one of those checks shows it's gone.

We do not sell any of it, we do not use it for advertising, and we do not hand it to anyone except the providers who help us run the app. Your Claude or ChatGPT only ever sees it if you connect one yourself and ask for it. We keep the public YouTube data we hold for competitor research, like a channel's name, picture, description and numbers, for no more than thirty days, then we either refresh it or delete it. We keep a channel's link and ID while it's on your list, so we know which channel to refresh, and after you turn it down, so we don't suggest it again.

You can take our access away at any time. Disconnect YouTube in the Configure tab, which also asks Google to cancel our access, or remove Kadenza from your Google account at security.google.com/settings/security/permissions or myaccount.google.com/permissions. If you disconnect YouTube, we ask Google to end our access, delete your key and your channel's saved name and picture right away, and delete your YouTube numbers within seven days; after that, your channel ID is kept only in the record of videos you posted through Kadenza. If you remove Kadenza's access in your Google account instead, we notice the next time we use it, which is within about twenty days while your account is active, and a locked account is disconnected after twenty-five days anyway; then your key, your channel's saved name, picture and ID, and your YouTube numbers are gone within thirty days. We keep a record of the videos you post through Kadenza: the title and description you wrote and each video's link; for a video that was scheduled on YouTube itself, the record also keeps your channel ID and the publish time and privacy setting YouTube reported. Deleting your YouTube data from Kadenza does not change anything on YouTube itself: to remove a video from YouTube you need to do that in YouTube.

Kadenza's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

How we use it, and why we're allowed to

• To run the features you ask for: research, drafting, publishing and scheduling, your lead magnets and funnels, your inbox, outreach to people you added, and your results. We need this to provide the service you signed up for.
• To sign you in and send service messages, like a new-lead notice, a safety alert if a platform flags your account, or a warning that a connection needs attention. Same reason: the service can't work without it.
• To keep Kadenza safe: stopping spam and abuse, protecting accounts, and making sure one person can't take a second free trial. This is our legitimate interest in running a secure service.
• To understand how people find and use Kadenza, through Google Analytics, so we can improve it. This happens only if you accept analytics cookies, and you can take that back any time from Cookie settings.
• To meet legal duties, like keeping records the law requires.

We don't sell your data, we don't use it for advertising, and we don't use it to train AI models.

Who we share it with

We use a small set of service providers to run Kadenza. Each gets only what it needs for its job and is bound by its own terms:

• Hosting and computing: the servers that run the app and its background work.
• Database, sign-in and file storage: where your account and data live.
• Email delivery: sends sign-in and service emails.
• Social-platform connections: the services that connect your LinkedIn and Instagram accounts and carry the posts, messages and reads you ask for, plus a public-data service for Instagram research.
• Google and YouTube: sign-in with Google, your YouTube channel if you connect it, and public YouTube data for research.
• Spam protection: a CAPTCHA check on public lead forms, which receives the technical request data it needs.
• Analytics: if you accept analytics cookies, Google Analytics measures visits to our site and app. Google then receives standard analytics data (rough location, device, pages viewed) and sets its own cookies.
• Payments, once paid plans open: a payment processor handles your card details, and we never see or store them.

We don't use advertising pixels and nothing about you is shared with ad networks. The email tools you connect as lead destinations get the leads you send them, because you asked for that. We can give you a list of our providers by name if you email support@kadenza.ai.

Cookies

The cookies that keep you signed in and your session secure are essential. They're always on, because the app can't work without them, so they don't need your permission. One more small cookie remembers the choice you make on our cookie banner, for twelve months.

Google Analytics is the only thing that asks. It loads, and sets its own cookies, only after you press Accept or turn Analytics on in Cookie settings. If you leave it off, or don't choose, it stays off. You can change your mind any time with Cookie settings here, or with the same link at the bottom of our website and the login page.

About AI

When you ask for a transcript, we turn the saved video into text with a speech-to-text model we run ourselves, and we use that media only for that. Kadenza doesn't use that model, or any other, to write your content or to read your pictures. You can separately choose to connect your own AI, such as Claude or ChatGPT, using your API key and our MCP. If you do, that AI reads the Kadenza data you ask for under its provider's terms and privacy policy. That connection is yours to make and remove by revoking the key in the API & MCP tab.

Other people's data (your leads and prospects)

When you capture leads or add prospects, you are responsible for having a lawful reason to contact those people and for honoring their requests. Kadenza only stores and processes that data on your behalf. Anyone whose data you hold can email us at support@kadenza.ai to have it removed.

How we keep it safe

Your files sit in a private storage bucket and are only ever served through short-lived signed links, never a public URL. API keys are stored hashed, so even we can't read them back, and access tokens for your connected accounts are encrypted. Data is encrypted in transit, and database access is locked down so one account can never see another's data.

How long we keep it

• Your account and your own content: while your account is open. You can delete files, drafts, leads and keys yourself at any time.
• Competitor posts, their numbers and saved pictures, and inbox messages: up to one year, then they're deleted.
• YouTube data: as described in the YouTube section above.
• Magnet reading records (how far people read a gated guide): up to one year.
• Public-form safety fingerprints: 48 hours.
• Backups: we keep about a week of rolling database backups to recover from a failure, and a backup copy of each account's files and records that's removed the night after the account is deleted.
• After you stop paying: your work stays in place for at least thirty days, so it's all there if you come back, apart from your YouTube connection and numbers, which follow the YouTube section above. You can delete it yourself any time.

To delete your whole account and everything in it, follow the steps on our data deletion page, or email support@kadenza.ai.

Two things outlive your account on purpose. The first is a short record that your account was deleted: its internal ids, the dates, and technical notes on how the deletion went. We don't put your name or email in it. It's there so a late sign-in, a delayed job or our backup copy can't bring the account back, so we keep it for as long as Kadenza runs. The second only applies if you ever started a free trial: a scrambled one-way code made from your email address, with the date. We keep it so nobody can take a second free trial by deleting their account and signing up again, which is a legitimate interest in stopping our own offer being abused. It is not your email, it cannot be turned back into your email, and nothing else is attached to it. We delete it after two years.

Where your data is processed

Our providers run servers in more than one country, so your data may be processed outside the country you live in. Where your data leaves the UK or EEA, we rely on Standard Contractual Clauses or an adequacy decision. Email us for a copy.

Your rights

You can ask us what data we hold about you, and ask us to correct it, export it, delete it, restrict how we use it, or object to our use of it. Email support@kadenza.ai and we'll take care of it. You can also export your whole workspace yourself through the API. If you're not happy with how we handled your data, you can complain to the data protection authority where you live.

Children

Kadenza is for adults running a business or brand. It's not for anyone under 18.

Changes

If we change this policy we'll update the date at the top, and for anything significant we'll let you know by email. If we ever want to use your Google data in a new way, we'll ask you first.