Privacy policy
Yaybird is run by Leonyr, LLC. Effective 21 October 2026.
This policy explains what personal data Yaybird collects, why, who else handles it, how long we keep it, and the choices you have. Questions or complaints about it go to support@yaybird.com.
Who we are
Yaybird is a service for planning, approving and publishing posts to social media accounts. AI agents you connect can draft posts, and a person on your team approves them before they go out. Leonyr, LLC, a Wyoming limited liability company that trades as Yaybird, runs it.
For your account, billing and our website, we decide how your data is used (we are the controller). For personal data inside the content your workspace puts into Yaybird, such as people named in a post or the people who comment on your posts, we handle it for you and on your instructions (we are your processor). If you need a data processing agreement, email support@yaybird.com.
What we collect
- Account: your email address and name, the workspaces you belong to and your role in each, and your notification settings. If you sign in with Google, Google tells us your name, email address and profile picture; we keep no Google access token.
- Workspace and brand: brand names, brand rules, time zone, posting times, team invites, and the agents and API keys you connect. API keys are stored hashed.
- Posts and media: the captions, comments, images and videos you or your agents create, who approved what and when, and each platform's answer when a post goes out, such as the post id and link.
- Connected social accounts: the account id, name and picture. For most accounts the access token is held by Zernio, our publishing partner, not by us. For the few accounts connected directly to our own platform app, we hold the token, encrypted.
- Comments for the inbox: comments on posts you published through Yaybird, with the commenter's public name, handle and comment text, and the replies you send.
- Results: the numbers platforms report for your posts, such as views, likes and comments.
- Billing: your plan, subscription status and billing dates. Stripe collects and holds your card details, billing address and tax id. We never see your full card number.
- Waitlist: the email address you leave on our website.
- Security: your IP address and browser type with each sign-in session. Our own rate limits store IP addresses and email addresses as keyed hashes. Two short counters keep them as they are: the sign-in link limit keeps your email address for about 15 minutes, and our sign-in library keeps your IP address for its one-minute rate limit. We delete both within an hour.
- Support: what you send us when you email us.
- Feedback: feedback you send from the app is stored with your workspace and emailed to us so we can reply.
We do not collect data about your followers or audience beyond the comments and results above. We do not sell personal data, and we do not use your data to train AI models. We tell Meta when you arrive from one of our ads, sign up, start your trial and make your first payment, as Our ads on Meta explains, and Google which of its ads led to a sign-up, trial or payment, as Our ads on Google explains. We count how people use our public pages and sign-up, and record how the app is used with your content hidden, as Product analytics explains.
AI agents you connect
Yaybird does not run its own AI model on your content. You choose the AI agent that drafts for you, such as Claude, ChatGPT or another client, and what it may do in your workspace. What that agent reads goes to its provider under your agreement with them, not ours. You can disconnect an agent at any time in the app, and it loses access at once.
Why we use it, and our legal basis
- To run the service you signed up for (performance of our contract): sign-in, your queue and calendar, brand rule checks, approvals, publishing, the inbox, results and notification emails.
- To bill you and keep records (contract and legal obligation): payments, invoices, tax and accounting.
- To keep the service safe (legitimate interests): rate limits, stopping abuse, finding and fixing errors.
- To tell you about Yaybird (legitimate interests, or consent where the law needs it): your waitlist invite and important changes to the service. You can opt out of anything that is not about your account.
Who else handles your data
We use these service providers (subprocessors). Each gets only the data it needs to do its job for us.
- Cloudflare, Inc. (United States): hosting, the database, media storage, sign-in state for agents, logs, our support email forwarding, privacy-friendly visitor counts on our public pages, and the bot check and speech-to-text (Workers AI) behind the free auto captions tool, which receives only the sound of a video and keeps none of it.
- Zernio Software SL (Spain): connects your social accounts, holds their tokens, publishes approved posts, and returns comments and results.
- Stripe, Inc. (United States): checkout, subscriptions, invoices, tax and card payments.
- Google LLC (United States): sign-in with Google, if you choose it.
- Resend (Plus Five Five, Inc., United States): sends sign-in links, invites and notification emails.
- PostHog, Inc. (United States): the product analytics and the recordings of how the app is used described in Product analytics.
The social platforms you publish to (such as Instagram, Facebook, Threads, TikTok, YouTube, LinkedIn, X, Bluesky, Pinterest and Google Business Profile) receive your posts because you tell us to send them there. Their own terms and privacy policies apply to what they do with them.
Meta Platforms, Inc. gets the ad events described in Our ads on Meta and uses them under its own terms. Google LLC gets the ad conversions described in Our ads on Google and uses them under its own terms.
We may also disclose data when the law requires it, to protect our rights or people's safety, or to a buyer if the business is sold, under this policy.
Our ads on Meta
We advertise Yaybird on Facebook and Instagram. When you arrive from one of those ads, and when you sign up, start your trial or make your first payment (whether or not you came from an ad), our server tells Meta so it can count what its ads led to and show them to people likely to use Yaybird. There is no Meta pixel or script on our pages: the events go from our server to Meta's Conversions API.
With each event we send:
- from sign-up on, your email address, hashed with SHA-256 so Meta can only match it to an account that already has that address;
- your country, hashed, and from sign-up on a hashed id for your workspace;
- the IP address and browser type of your visit when you arrive, and the ones you signed up with for the later events;
- the click id from the ad link and a random browser id, kept in the _fbc and _fbp cookies;
- the page, the time, and for a payment its amount and currency.
We send nothing else: no posts, media, brand rules, social accounts or comments. Meta uses these events under its Business Tools Terms and its privacy policy.
We send none of it and set neither cookie if you are in the EU, the EEA, the UK or Switzerland, if your browser sends Global Privacy Control, or if you choose Do not share my info. Choosing that signed out covers this browser only; choose it while signed in to also delete what we kept for later events about the workspaces you own, so none of them are sent.
Our ads on Google
We also advertise Yaybird on Google. When you arrive from one of those ads, the ad link carries a click id. We keep it and the time of the click in the yb_gclick cookie, and with your workspace when you sign up. When you sign up, start your trial or make your first payment, we tell Google Ads so it can count which ad led to it and show our ads to people likely to use Yaybird. There is no Google tag or script on our pages: Google Ads fetches these conversions from our server as a password-protected file, and we may also upload the same file to Google Ads ourselves.
With each one we send the click id Google put in the ad link, whether it was a sign-up, a trial or a first payment, and its time, with a value of zero for a sign-up and the amount and currency for a first payment. We send nothing else: no name, email address, IP address, posts, media, brand rules, social accounts or comments. Google uses them under its own terms and its privacy policy.
We keep the click id for 90 days after the click, as long as Google takes it. We keep and send none of it, and set no cookie, if you are in the EU, the EEA, the UK or Switzerland or we cannot tell which country you are in, if your browser sends Global Privacy Control, or if you choose Do not share my info, which works here as it does for Our ads on Meta.
Product analytics
We use PostHog to learn which pages work and which ones lead people to sign up. On our public pages (never the sign-in pages), a script served from our own site records the pages you view, the links and buttons you click, the site that sent you, your country and your browser, device and screen type. It never records what you type. To tell one visitor from another it sets one first-party cookie, ph_..._posthog, with a random id and the current visit (the page you landed on with its campaign labels, and the site that sent you), and keeps a few entries in session storage that clear when you close the tab. Our server forwards these events to PostHog without your IP address or our other cookies.
On the sign-in pages no analytics script runs. Our server counts, once a day, which steps of signing in a visit reaches (the sign-in page, the code sent, a code that did not work, signed in, account created, checkout opened, trial started) with the ad or link it first came from, and tells PostHog the same with your country and the random id above, if your browser has it. To count a visit once, it uses a value made from the yb_src cookie below, or else from your IP address and browser, with a secret key and the date, so it is different every day. It never keeps or sends the IP address, your browser, email address or name. We keep those counts for 13 months.
From sign-up on, our server also tells PostHog when a workspace signs up, moves through setup, connects its first social account, starts its trial, makes its first payment (its plan, amount and currency) or cancels, with the ad or link it first came from and the page it landed on and the country it signed up from. These events carry the workspace's id, never your name, email address, IP address, posts or media. When you sign up, we tell PostHog that the random id and the workspace's id are the same visitor, so we can see which pages and ads lead to sign-ups.
Inside the app, once you are signed in, we record how the pages are used: your clicks, scrolling and the screens you open, so we can see where the app is hard to use. Before anything leaves your browser, what you type, your posts' text and captions, comments, brand rules, names, handles, email addresses, links to your posts, and our messages that repeat what you entered are hidden as stars. Your images and videos are left out. The parts of a screen that show keys, tokens, agent connection details or billing are recorded as blank boxes. Page addresses are kept without the details some carry after the page name. These recordings carry your workspace's id, never your IP address. They are kept in your browser's session storage only until they are sent, and that storage is cleared when you close the tab.
We send none of it, and set no analytics cookie, if you are in the EU, the EEA, the UK or Switzerland, if your browser sends Global Privacy Control, or if you choose Do not share my info, which works here as it does for Our ads on Meta.
International transfers
We are a US company and most of our providers are in the United States. When personal data from the EU, the UK or Switzerland goes to the US, we rely on the European Commission's Standard Contractual Clauses (with the UK addendum) or the provider's certification under the EU-US Data Privacy Framework and its UK and Swiss extensions.
How long we keep it
- Account, workspace, posts, media, comments and results: while your account is open. When you ask us to delete your account or a workspace, we delete it within 30 days.
- Connected accounts: until you disconnect them or your subscription ends. Then we disconnect them at Zernio and delete the tokens.
- Sign-in sessions: up to 30 days. Sign-in links and codes: 15 minutes, and they work once.
- Waitlist emails: until you join or ask us to remove you.
- Billing records: as long as tax and accounting law requires, usually up to 7 years.
- Ad events for Meta: the IP address from sign-up for 45 days, the rest while your account is open or until you choose Do not share my info.
- Ad clicks for Google: 90 days from the click, or until you choose Do not share my info.
- Product analytics: PostHog keeps the events for as long as our plan with it sets, from 1 year up to 7 years. They hold no IP address, name or email address. Recordings of the app: as long as our plan with PostHog sets, never more than 90 days and often less. Choosing Do not share my info while signed in deletes the recordings of the workspaces you own.
- Logs and database backups: they roll off on their own within 30 days.
Cookies and similar storage
We set the cookies the service needs to work, two for our ads on Meta and one for our ads on Google, only when you arrive from one of those ads and only where Our ads on Meta and Our ads on Google allow, and one for Product analytics where it runs.
- better-auth.session_token: keeps you signed in, up to 30 days.
- ws: which of your workspaces is open, up to a year.
- tz: your time zone while you sign up, 1 hour.
- yb_invite: the team invite you opened, until you accept it.
- yb_src: if you arrive from one of our ads or links, or from another website, where from (the campaign labels, which ad network if any, the page you landed on and the referring site's name), up to 90 days, saved with your workspace when you sign up so we know which ads work. It is our own cookie: no ad network sees it, and it holds nothing about you. Before you sign up, we also use it to count, once a day, that someone came from an ad and whether they opened the sign-in page, with nothing that identifies you. We keep those counts for 13 months.
- _fbc and _fbp: the click id from a Meta ad link and a random browser id, up to 90 days, sent to Meta with the events above. Only our own server reads them.
- yb_gclick: the click id from a Google ad link and when you clicked, up to 90 days, kept with your workspace when you sign up. Only our own server reads it.
- ph_..._posthog: a random id and the current visit for Product analytics on our public pages, up to a year. Not set in the EU, the EEA, the UK or Switzerland, with Global Privacy Control, or after Do not share my info.
- yb_no_share: remembers that you chose Do not share my info, for a year.
- oauth_state, oauth_choice, zernio_state: protect the step where you connect a social account, and are removed when it finishes.
The app also keeps your light or dark theme, and your progress on a post you publish by hand, in your browser's own storage, and, where Product analytics records the app, the recording until it is sent. Our public pages may use Cloudflare Web Analytics, which counts visits without cookies and without following you across sites, and our Product analytics, with the one cookie above and a few session storage entries that clear when the tab closes. There is no ad pixel or ad network script anywhere in Yaybird.
Your rights
Depending on where you live, you can ask to see, correct, delete or export your personal data, to restrict or object to how we use it, and to withdraw consent you gave. Email support@yaybird.com from the address you sign in with. We answer within 30 days and may need to confirm it is you. If your data came to us through a customer's workspace, we pass your request to that customer and help them answer it.
In the EU or UK you can also complain to your data protection authority. We would like the chance to fix it first.
California
We do not sell personal information. Sending the ad events in Our ads on Meta may count as sharing it for cross-context behavioral advertising. You can opt out at Do not share my info, and we treat Global Privacy Control as the same choice. We do not use sensitive personal information to infer anything about you. The categories we collect are identifiers (name, email, IP address), commercial information (your plan and payments), internet activity (sign-in and use of the app) and the content you create, for the purposes above. You can use your rights through an authorized agent, and we will not treat you differently for using them.
Platform notices
YouTube and Google
Publishing to YouTube uses the YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service, and the Google Privacy Policy applies. We use the channel's data only to publish your approved videos and show their comments and results. You can revoke access at any time from your Google security settings. When you do, or you disconnect the channel, we delete the data we got from it within 7 days. Data we keep from YouTube is refreshed or deleted at least every 30 days.
X
If a post or comment we stored from X is deleted or changed on X, we delete or update our copy, within 24 hours of a request from X or from the account owner. We never use X content to train or fine-tune AI models.
Meta, TikTok, LinkedIn and others
For Facebook, Instagram, Threads, TikTok, LinkedIn, Bluesky, Pinterest and Google Business Profile, we use the data we get from the platform only to publish what you approve and to show its comments and results where the platform has them (Google Business Profile posts have neither). You can remove Yaybird at any time in the platform's own settings, and ask us to delete what we hold by following our data deletion steps.
Security
Everything travels over HTTPS. Tokens we hold are encrypted, API keys and sign-in links are stored hashed, and each workspace sees only its own data. No system is perfectly safe. If a breach puts your data at risk, we will tell you without undue delay.
Children
Yaybird is for businesses and people aged 18 or over. We do not knowingly collect data from children.
Changes
If we change this policy in a way that matters, we will email account owners at least 14 days before it takes effect. The date at the top says when it last changed.
Contact
Leonyr, LLC, trading as Yaybird. Email support@yaybird.com.