Legal
BusyBird Privacy Policy
Effective date: November 22, 2026
Version: 1.0 (pre-release)
Pre-release edition. BusyBird has not been released and is not on sale. None of the online services described here (accounts, relay, push notifications, call relay, licence service, checkout, update feed) is operating yet. This document describes how they will work and applies from the first public release.
1. Who we are
LedgerNorth LLC ("we", "us"), a Texas limited liability company, makes BusyBird. We decide how the data described here is used (we are the "controller").
Contact for privacy questions and requests: support@ledgernorth.io · LedgerNorth LLC, Austin, Texas, USA.
2. The short version
- BusyBird runs on your computer. Your bots, conversations, files, settings and AI keys stay there.
- Your bots talk directly to the AI providers and other services you set up. We never see your prompts, replies, files or keys.
- Today we run no online service for BusyBird. The only data we receive is what a visit to this website sends and any email you write to us. When our services start, they will handle only what is needed to sell licences, connect your phone to your computer, and deliver updates.
- Phone-to-computer traffic is end-to-end encrypted. Our relay cannot read it.
- We do not sell your data. We do not use it for advertising. We have no analytics or tracking in the apps.
- We do not train AI models on your data.
3. What stays on your computer
This data is stored only on your devices. We do not receive it:
- your bots, conversations, prompts, AI replies, files, memories and settings;
- the logins and API keys for your AI providers and other services;
- your Google sign-in and Gmail or YouTube data, if you use the optional Google tool;
- your licence key and the trial and licence files;
- the keys that encrypt your phone connection.
Your bots send content from your computer straight to the services you choose (for example Anthropic, OpenAI or Google). Those services handle it under their own privacy policies. Read them before you connect them.
Google tool. If you connect Gmail or YouTube, you use your own Google Cloud project and OAuth client. Your Google tokens are stored on your computer in a folder only your user account can read. Google data goes only between Google and your computer, and on to any AI provider your bots use. We never receive, store, read or share it. Because the OAuth client is yours, Google treats you as the developer, and Google's API Services User Data Policy (Limited Use) applies to you.
4. What the phone apps do
The BusyBird apps for iPhone, iPad and Android have no account or sign-in of their own. They pair with your computer by scanning a QR code and talk only to that computer, end-to-end encrypted. We receive nothing from them.
- Camera: used only to scan the pairing QR code. The image is read on the phone and is not stored or sent.
- Microphone and speech recognition: used only when you dictate a message or start a Live call. Dictation uses your phone's own speech recogniser, on the device when the phone supports it.
- Local network: used to find your computer on the same Wi-Fi.
- Stored on the phone: the pairing keys and device token for each computer, a copy of the office artwork, and your app settings. Removing the computer in the app or deleting the app removes them.
- Android pairing scanner: the Android app uses Google's ML Kit to read the QR code. ML Kit sends Google device and app information, a per-installation ID, performance metrics and error codes for diagnostics and usage analytics, under Google's privacy policy. It does not send the image.
- Live calls (optional): if you start a voice call with a bot, your voice, the chat's recent messages and the bot's answers go to OpenAI, using the OpenAI key set up on your computer. The app tells you this and asks before each call starts.
- Spoken replies on iPhone (optional): if you add your own ElevenLabs key on the phone, the text of bot replies is sent to ElevenLabs to be read aloud.
OpenAI and ElevenLabs handle that data under their own privacy policies and your own account with them.
5. What our services will receive
None of the services in sections 5.1 to 5.6 is operating yet. This is what each will receive once it starts.
5.1 Licence and trial
| Data | When | Why |
|---|---|---|
| Licence ID and plan (from your key) | Activation and each check | Confirm the licence is valid |
| A random ID for your computer | Activation and each check | Count computers per licence |
| Your computer's name (its hostname, up to 128 characters) | Activation and each check | Show you which computers use the licence. A computer name can include your name. |
| Operating system and app version | Activation and each check | Support and compatibility |
| Activation and last-seen times | Activation and each check | Licence management |
| Your network (IP) address | Every request | Deliver the response and limit abuse (not stored in our database or logs; see section 7) |
| Trial start date | Only if you sign in to an account | One trial per person |
The desktop app checks the licence about twice a day.
5.2 Buying a licence
You pay on a checkout page run by Stripe. Stripe collects your name, email, billing address and card details.
We receive from Stripe: IDs for the checkout, the Stripe customer, the subscription and the payments, plus the paid period. Stripe also gives us your email once, so we can email your licence key. We do not store your email or your licence key in our licence database. We keep the Stripe IDs so a refund, chargeback or cancellation can end the right licence.
Stripe processes payment data for us and also uses it for its own fraud-prevention and legal purposes, under Stripe's privacy policy.
5.3 Accounts service (only if you sign in)
You need an account only to reach your computer from your phone through our relay, or for push notifications.
| Data | Why |
|---|---|
| Your email address and an account ID | Sign-in and contact about your account |
| Sign-in codes (stored only as a keyed hash; valid 10 minutes) | Sign-in |
| Session and computer credentials (stored only as hashes) | Keep you signed in; let each computer get relay tokens |
| For each computer: the name you or the app gives it, operating system, app version, a random ID, when it was added or removed | Show and manage your computers |
| Rate-limit counters keyed by IP address, email or account (kept for about an hour) | Stop abuse |
5.4 Push notifications (optional)
If you turn on notifications on a phone, your computer registers it with our accounts service. We store the phone's device ID, the push provider (Google or Apple), the push token, the environment, and when it was last updated.
Notification content is sealed (encrypted) on your computer with a key only your phone has. We, Google and Apple cannot read it. iPhone notifications show a fixed generic message until the app decrypts them. Google and Apple see the push token, the time and the size of each notification.
5.5 Phone relay
When your phone cannot reach your computer directly, traffic goes through our relay. The relay sees which computer is online, the network addresses involved, how many phones connect, when, and how many bytes pass. It never sees content. Relay logs name a computer by a short prefix of its ID and contain no client addresses. Per-address limits are held only in memory.
5.6 Call relay (optional)
When a voice call between your phone and your computer cannot connect directly, it may pass through our call relay. The call relay sees network addresses and traffic volume and timing. Call audio is encrypted between your devices. The call relay keeps no log.
5.7 Updates, downloads and the website
When the desktop app checks for updates, or you visit our website or download page, your device sends a normal web request (IP address, browser or app version, operating system, time). Our host, Cloudflare, processes these requests and may keep short-lived logs. The update check does not include any ID of yours.
This website, busybird.ai, sets no cookies, runs no analytics and loads nothing from other sites.
5.8 Email and support
We will send sign-in codes and licence keys by email from noreply@ledgernorth.io, through a mail provider we will name in section 8 before those emails start. If you email support, we keep the messages to answer you.
6. What we do not do
- We do not sell or "share" personal data for advertising, and we do not process it for targeted advertising.
- We do not run analytics, telemetry or tracking in the apps.
- We do not make automated decisions that have legal or similarly significant effects on you.
- We do not knowingly collect sensitive data.
7. How long we keep data
| Data | How long |
|---|---|
| Account email, account ID, computers | Until you delete your account. A computer you remove stays listed as removed until then |
| Sign-in codes | 10 minutes, or until used |
| Session tokens | Up to 30 days |
| Computer credentials | Up to 90 days, then rotated |
| Relay tokens | About 2 hours |
| Push registrations | Until you turn notifications off, remove the phone, or the provider says the token is invalid |
| Rate-limit counters | About 1 hour |
| Licence records (licence ID, Stripe IDs, computer details) | For the life of the licence, then 7 years for tax and accounting records |
| Server logs (no emails, codes, tokens or addresses) | 14 days |
| Database backups | 30 days |
| Support emails | 2 years after the last message, or sooner if you ask |
| Payment records at Stripe | Under Stripe's policy |
8. Who processes data for us
Today only Cloudflare (this website) and our email provider (support email) handle any data for us. The others start with the services they support.
| Provider | What it does | Data it handles |
|---|---|---|
| Stripe | Payments, invoices, subscriptions | Payment and billing details, email |
| A hosting provider, named here before those services start | Runs the accounts service, relay and call relay | Data in sections 5.1 to 5.6 |
| Cloudflare | Website, downloads, update feed and DNS | Web request data (5.7) |
| Google Firebase Cloud Messaging | Android notifications | Push token, Firebase installation ID, sealed content |
| Apple Push Notification service | iPhone notifications | Push token, sealed content |
| A mail provider, named here before those emails start | Sends sign-in codes and licence keys | Email address, message content |
| A backup storage provider, named here before those services start | Encrypted database backups | Data in 5.1 to 5.4 |
We require these providers to protect the data at least as well as this policy does. We may also disclose data if the law requires it, to protect people or our services from harm or fraud, or to a business that takes over BusyBird (we will tell you first).
9. Where data is processed
We are in the United States. Our providers may process data in the United States and other countries.
10. Your rights
Wherever you live, you can ask us to:
- tell you whether we process your personal data, and give you a copy in a portable format;
- correct it;
- delete it;
- (where it applies) restrict or object to how we use it.
We do not sell personal data or use it for targeted advertising or significant profiling, so there is nothing to opt out of. We will not treat you differently for using your rights.
How to ask (any of these):
- Email support@ledgernorth.io from the address on your account, or with your licence ID.
- Follow the steps at https://busybird.ai/delete-account.
When accounts start, you will also be able to delete your account inside the app.
You do not need an account to make a request. We may ask for information to confirm it is you. An authorised agent can act for you with your signed permission.
Our answer. We answer within 45 days (one month for people in the EU/UK), free of charge. If we need more time we tell you why within that period. We can extend once by up to 45 more days (two more months in the EU/UK).
Appeal. If we refuse a request, you can appeal by replying to our answer with "Appeal". We answer an appeal in writing within 60 days. If we deny it, you can complain to the Texas Attorney General at https://consumerprotection.texasattorneygeneral.gov/ or to your local regulator. In the EU/UK you can complain to your data protection authority at any time.
Deleting your account (once accounts exist) removes your email, your computers, their credentials and your push registrations. Each computer stops getting relay tokens at once; a token it already holds expires within about 2 hours. We keep licence and payment records we must keep for tax and accounting, without your email. Backups roll off within 30 days.
11. Legal bases (EU and UK users)
- Contract: to sign you in, run the relay, notifications and calls, and issue and check licences.
- Legitimate interests: to secure the Services, limit abuse and prevent fraud.
- Legal obligation: to keep tax and accounting records.
- Consent: for push notifications, which you can turn off at any time.
You must give your email to use an account, and payment details to buy a licence. Without them those features are not available. The app itself works without an account.
12. Children
BusyBird is not for children. You must be at least 18 to use it. We do not knowingly collect personal data from anyone under 13 (or under 16 in the EU). If you think a child has given us data, email support@ledgernorth.io and we will delete it.
13. Security
We encrypt phone traffic end to end. We store secrets only as hashes. Our servers keep no logs of emails, codes, tokens or credentials. Backups are encrypted. No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.
14. Do Not Track
We do not track you across other websites or services, so browser "Do Not Track" signals change nothing here. We do not let other parties track you through our website or apps.
15. Changes
We will post any change here with a new effective date. If a change is significant, we will tell you in the app or by email before it applies.