Privacy Policy

This page explains what personal information Klaudius collects, how we use it, and who we share it with.

Who we are

Klaudius is operated by Cloudbot Limited (“we”, “us”, “our”), a company registered in England and Wales, which is the controller of the personal data described here. For privacy questions, email hello@klaudius.dev.

What we collect

Information you give us

• Email correspondence: when you email us, or write to us from the app’s Help screen, we receive your email address and your message. A message from the app also carries the name and email address on your licence, technical details of the app and your computer, and a reference to any diagnostic reports you have sent.
• Purchase information: you give your payment details to our merchant of record, Lemon Squeezy, not to us. It passes us your name and email address and, for a subscription, its status and dates, the amount and currency of your first payment, and its own reference numbers. It never passes us your card details.
• Emails about your subscription: we email your licence key, and a reminder before an annual plan renews. When you buy or subscribe, we also add you to our product-update emails. You stay on that list after your subscription ends, until you unsubscribe with the link in any of them.
• Free-build requests: when you ask for a free build, we receive your email address, the region or business you give us and which form you used, linked to your visits to klaudius.dev. We email you to confirm; once you do, we send you the build and occasional emails about Klaudius, each with an unsubscribe link.

Information collected automatically

• Server logs: standard web server logs (IP address, time, address requested, browser or app details), kept for 30 days for security and abuse prevention. When the app checks for a new version of itself, it only confirms your licence is active and leaves nothing but these logs.
• Licence checks (the Klaudius app, subscriptions): the app checks your subscription with our servers when it opens and about once an hour while it runs. Each check sends your licence key, an ID the app creates when it’s installed, your computer’s name and operating system, the app version, which AI agent you use, and a security key and signature. For each computer using your licence we keep those details, when it first and last checked in, and a record of any computer you release. We use them to confirm your subscription, to hold your place on up to 2 computers, to spot a licence being shared and to protect our servers. If your licence is in use on 2 computers and you open the app on a third, the app lists the other two by name, operating system and last check-in so you can release one. Our analytics provider, PostHog, receives the outcome of each check with the app version, operating system and AI agent, under a one-way code in place of your licence key and without your computer’s name. All of this happens whether or not usage data is switched on in the app.
• Pipeline downloads (the Klaudius app, subscriptions): when the app downloads or updates its pipeline, or is turned away at the computer limit, we keep a record of the request with the same computer and app details as a licence check, and which pipeline version we sent. We use it to spot a licence being shared. PostHog receives the same details for each download and for any request that looks unusual. This happens whether or not usage data is switched on in the app.
• Pipeline marks: each copy of the pipeline we send is marked, and we keep a list of which mark went to which licence, so a copy found elsewhere can be traced back to it.
• Checkout limits: when you start a checkout, on our website or in the app, we record a one-way code of your network address, to limit how many checkouts one address can start. The free-build form does the same, with the email address you enter.
• Licence checks and pipeline downloads (earlier licences): when Klaudius checks one of these licence keys or downloads the pipeline (at setup and for updates), we keep a record of each computer using it: an ID derived from the computer’s details, its name and operating system, the Klaudius version, and when it first and last checked. PostHog receives the same details, and which AI agent you use, under a one-way code in place of your licence key. We use them to enforce the computer limit and to spot a licence being shared.
• Desktop app usage data and diagnostic reports: see The Klaudius desktop app below.
• The phone app: see The Klaudius phone app below.

klaudius.dev uses PostHog for analytics, which stores a cookie in your browser so it can recognise repeat visits. If you arrive through a partner’s link, Lemon Squeezy’s affiliate script also stores a cookie, so a purchase can be credited to that partner.

How we use it

We use the information we collect to:

• Fulfil your order, run your subscription and provide support
• Check your licence, hold its place on up to 2 computers, and detect sharing, fraud and abuse
• Run the phone app’s relay and send its notifications, if you pair a phone
• Find and fix problems in Klaudius, and improve it
• Decide, from how you use Klaudius, whether to tell you about a feature or check in with you
• Send you a free build, and emails about Klaudius, when you ask for one
• Communicate with you about your purchase, updates and support
• Comply with legal obligations

Why we’re allowed to use it. We use your details to provide your subscription and support you, because that’s our contract with you. We run the licence checks, the computer limit, the pipeline marks and the checkout limits, and send their details to PostHog, because we have a legitimate interest in stopping licences being shared, preventing abuse and keeping Klaudius running. We send product-update emails because we have a legitimate interest in telling customers about Klaudius, and free-build emails because you asked for them; you can stop either at any time. Usage data and reports are covered under “The Klaudius desktop app” below. And we keep the records the law requires.

We do not sell your personal data.

Who we share it with

We share personal information only with these providers, and only as needed to run Klaudius. Lemon Squeezy and Google are data controllers in their own right; the others process data on our behalf:

• Lemon Squeezy is our merchant of record, under its own privacy policy. It sells you the licence or subscription, takes your payments, including renewals and retries, handles tax and receipts, and runs the page where you manage your subscription. You give it your email, billing address and payment details at checkout; it never shares your card details with us.
• Resend: sends our automated emails, such as licence keys, subscription emails and product updates, and delivers messages from the app to us.
• Hosting and email providers: host klaudius.dev, our database, the phone app’s relay and diagnostic reports from the app, and run our email.
• Expo: sends the phone app’s notifications, through Apple’s or Google’s notification service, and delivers the phone app’s updates. It receives your phone’s notification token, each notification and, for updates, a random ID for that install of the app, as described under The Klaudius phone app.
• Google Fonts: klaudius.dev loads its fonts from Google, so your browser sends Google your IP address when you visit.
• PostHog: our analytics, hosted in its EU region. It records page views, clicks and session recordings on klaudius.dev, with what you type into forms masked, and receives the app’s usage data and the licence-check and download details described above.

Where your data goes. Some of these providers, including Lemon Squeezy, Resend and Expo, process data in the United States, and the phone app’s relay is hosted there. Where they do, we rely on each provider’s data transfer terms.

How long we keep it

• Licence keys for earlier licences: for the lifetime of your licence
• Licence and subscription records, and the list of pipeline marks: while your subscription is active and for 6 years after it ends, for refunds, disputes, our legal obligations and tracing a copy found later
• The list of computers using your licence, and their public keys: while your subscription is active and for 90 days after it ends
• Support emails: 24 months from the last interaction
• Free-build requests: until you ask us to delete them
• Server logs: 30 days
• Counts we keep to limit abuse (licence checks, checkouts, the free-build form and messages from the app): 2 days
• Pipeline download records: 180 days
• Diagnostic reports: 90 days
• Website analytics and app usage data, including the download details sent to PostHog: one year
• Phone app messages: until your phone or computer reads them, and at most 7 days
• Phone pairing records: while the pairing lasts, and 30 days after it ends
• Phone notification log: 1 day
• Counts we keep to limit how many messages a phone pairing sends: 1 hour
• Phone app connection records on the relay: 7 days, except each login’s current session, kept until the pairing ends

Data you process when running Klaudius

Klaudius runs on your own computer. When you run it, it gathers information about businesses you choose to target, such as their public contact details and photos, and uses it to build websites and send outreach. We don’t receive that data, except where it appears in a message or diagnostic report you send us, or an error message, as described below. If you pair the phone app, some of it passes between your phone and your computer through our relay and in notifications, end-to-end encrypted, so we hold it only in a form we can’t read, and only until your phone or computer collects it (at most 7 days). Your credentials stay on your computer and are used directly with each provider.

For that data, you are the data controller. We are not your processor, except that when you use the phone app, our relay stores it for you, encrypted and unreadable to us, until your phone or computer collects it, and we pass on its notification previews the same way; for that, we act as your processor, on your instructions, under section 6 of our terms. If someone you contact exercises their data-protection rights, such as access, correction, deletion or objection, those requests are for you to handle, not us.

The Klaudius desktop app

Your conversations with your AI agent, your clients’ details, your credentials and the websites Klaudius builds stay on your computer or go straight to the services you’ve connected, except what a diagnostic report includes and, if you pair the phone app, what passes to your phone end-to-end encrypted (see The Klaudius phone app). The app sends us two kinds of information, below. On a subscription it also checks your licence and downloads its pipeline, as described under “What we collect”.

Usage data

By default, the app sends us usage events about what it’s doing: for example, a run or setup step starting, finishing or failing and how long it took, which screens you open (their names, never what’s on them), which Klaudius skills a conversation uses (their names, never what you asked), updates, errors and crashes, and counts such as how many leads a search found. Once a day it also sends how Klaudius is set up: which features are connected, such as your AI receptionist or GoHighLevel, the options you’ve picked, such as your outreach channels and hosting, your plan, the country and language you work in, how many mailboxes you use, and your computer’s type, memory and free disk space. That’s yes or no, a count or the option you picked, never the key, address, price or number behind it. Each event includes the app version and your operating system. Error events include a short error message, with details that could identify you, your clients or your accounts, such as file paths, web addresses, email addresses and phone numbers, removed before it leaves your computer. A name inside an error message, such as a business name, can still get through. Usage events never include your prompts, your messages, what Klaudius writes, your clients’ details or your credentials.

Events carry two linked pseudonymous IDs: one made from your licence key (a random one stands in before you enter it), and one for your installation, so we can match an error to a support request. They’re stored with PostHog in its EU region, which also sees the IP address they’re sent from. We rely on our legitimate interest in keeping the app working, improving it, and deciding whether to tell you about a feature or check in with you. You can turn usage data off in Settings; that doesn’t stop the licence checks or download records, which the app needs to run.

If you switch on “Share pipeline totals” in Settings (off by default), the app also sends daily counts, such as how many businesses you’re tracking, how many sites are live and how many customers you’ve won: numbers only, never names. We use them to see what operators achieve with Klaudius, and a change in them, such as a new customer won, may prompt us to email you to ask how it’s going.

Diagnostic reports

There are four kinds:

• Automatic run reports are on by default. The app tells you about them the first time you use it, with a button to turn them off, and you can change this any time with “Send run reports automatically” in Settings. After each run, the report lists which tools ran (for a command, only the program’s name), whether they worked and how long they took, the AI model, effort setting and agent version, and error messages and log lines from around the run, cleaned the same way as usage data. It never includes your prompts, your messages or what Klaudius writes.
• Automatic crash reports use the same switch and are not shown to you first. They hold the app’s log lines from around the crash, cleaned the same way, what stopped and why, the name of the command that was running (never what it was working on) and how long the app had been open. They never include a conversation.
• Problem reports you send yourself, including the one the app offers after a failed run, are shown to you in full first. They include what you write, recent log lines and the log lines from the end of the run, and can include the conversation from the run. The app replaces names, keys and contact details it recognises with placeholders, and the preview shows where.
• Problem reports you send from the phone app (Settings, then “Send a report”) go through the Klaudius app on your computer. They include what you write, the phone app’s recent log lines (connection changes and error messages, cleaned the same way as usage data) and your computer’s recent log lines, cleaned as for crash reports. They aren’t shown to you first and never include a conversation.

Every report includes the app version and your operating system, with your computer’s user folder name removed. Reports are stored with our hosting provider at an unlisted web address, filed under a one-way code made from your licence key. Only we read them, to find and fix problems, and we delete them after 90 days. When you send a report yourself, we also get an email with what you wrote, the error your run ended on and a link to the report, and we keep that email like other support emails.

For automatic reports, we rely on our legitimate interest in fixing faults; you can object by turning them off. For reports you send, we rely on your consent, given by pressing Send. Email hello@klaudius.dev to have any report you’ve sent deleted.

The Klaudius phone app

The Klaudius phone app lets you answer Klaudius, approve follow-ups and start or stop work from your phone, while the Klaudius app on your computer does the work. Your phone and your computer pass messages to each other through a relay we run. Those messages are end-to-end encrypted, along with everything in them: your clients’ details, the replies businesses send you, follow-up messages, what Klaudius asks you, your conversation with Klaudius and the names of your phone and your computer. They’re locked with a key your computer makes and gives your phone only inside the code you scan, so only your phone and your computer can read them. The key never reaches us, and we can’t read the messages.

What we can see

• Pairing: the app on your computer sends us your licence key when you pair a phone, and from time to time to ask whether the phone app is available for your licence. We use it only to check your licence, and pairing a phone doesn’t count towards your computer limit. For each pairing we keep which licence it belongs to (not the key), whether the phone is an iPhone or an Android phone, when it was paired, when your phone and your computer last connected, when we last checked your licence and whether it was active and, if you allow notifications, your phone’s notification token.
• Messages: for each message, when it was sent, its size, whether it’s going to your phone or your computer, and a label saying what kind of message it is, such as an approval, follow-ups, a reply, a run or a chat message. Never what it says.
• Logins: the relay gives your phone and your computer a login each, made for that pairing alone and not linked to your email address.
• Connections: like any web service, when your phone or your computer connects to the relay or to klaudius.dev, its IP address and the technical details it sends (its “user agent”, which can show the app and system version) are recorded, for security and to stop abuse. To limit how often one network address can ask whether the phone app is available, we also record a one-way code of it.

We use these to run the relay, check your licence, limit abuse and count how many phones are paired.

Notifications

When something needs you, the app on your computer asks us to notify your phone. Each notification carries a short line we write, such as “Klaudius needs your answer.” or “A business replied.”, and usually a preview of what was said, such as who replied and how their message starts, or what Klaudius is asking you. Your computer locks the preview so that only your phone can open it, and your phone shows it in place of our line when it can. We, Expo, and Apple or Google pass the preview on but can’t read it: we can see only its length, in steps of 128 bytes, and we don’t keep it. We send notifications through Expo, which passes them to Apple’s or Google’s notification service. When you allow notifications, your phone gets its notification token from Expo, and each notification carries that token, our line, its kind and the locked preview. We log the kind and time of each notification for a day, to limit how many we send. You can turn notifications off in your phone’s settings, which also decide whether a preview shows on your lock screen.

Usage data

Once your phone is paired, the phone app sends crash reports and usage events only if usage data is switched on in the Klaudius app on your computer. They go to PostHog in its EU region under the same pseudonymous ID as your computer’s usage data. They record when the app is opened, which screen is shown (its name, never what’s on it), when a notification is opened and what kind it was, and the kind of each action you take, such as answering an approval, approving follow-ups (how many, never which), starting a run or sending a chat message, never what it says. Crash and error reports include a short error message, cleaned the same way as on your computer, and where in the app it happened. Each event includes the phone app’s version, your phone’s model and its operating system version, and PostHog sees the IP address it’s sent from. If usage data is switched on in the app on your computer, its own usage events also record when a phone is paired or unpaired, and from which end, and the kind of each action your phone sends.

Before your phone is paired, there’s no computer to follow, so the phone app sends only crash and error reports and whether pairing started, worked or failed (and a short reason, such as an expired code). These carry a random ID made for that session, which the app doesn’t keep.

You can turn all of this off on your phone, crash reports included, before or after pairing: with “Share crash reports and usage data” in the phone app’s Settings, or from Privacy on its first screen. Off there means off, whatever your computer’s setting says. On your computer, “Share usage data” in Settings turns it off for your paired phone too.

We rely on our legitimate interest in keeping the app working and improving it. If you let your phone share crash reports with app developers, Apple or Google may also pass us a report when the phone app crashes.

Updates

Once paired, the phone app asks Expo once each time it opens whether there’s a newer version of its own code. The check sends a random ID for that install of the app, the app’s version and your phone’s platform, and nothing about you or your work.

How long we keep it

• Messages: deleted as soon as your phone or your computer has read them, and after 7 days if they haven’t been
• When a pairing ends, its waiting messages, its notification token and both its logins are deleted straight away, and its record 30 days later. A pairing ends when you unpair it from either end, when your licence ends, or when neither your phone nor your computer has connected for 30 days
• Notification log: 1 day
• Counts we keep to limit abuse: 1 hour for messages, and 2 days for asks about whether the phone app is available
• Connection records: 30 days on klaudius.dev, and 7 days on the relay, except that the details of each login’s current session are kept until the pairing ends

Why we’re allowed to use it

We run the relay and send its notifications because you asked for them by pairing a phone; that’s part of our contract with you. We keep connection records because we have a legitimate interest in keeping the service secure. For what your messages say about other people, such as your clients, we act as your processor, under section 6 of our terms.

Unpairing and deleting

Unpair from your phone (Settings → Unpair this phone) or from the app on your computer (Settings → Klaudius on your phone → Unpair). Either one ends the pairing on both and deletes its messages and logins as above. Unpairing on your phone removes the key from it; unpairing on your computer does the same the next time your phone connects. Deleting the phone app doesn’t unpair it, so unpair it on your computer too. To ask us to delete anything else, email hello@klaudius.dev.

Your rights

Under UK and EU data protection law, you have the right to:

• Request a copy of the personal data we hold about you
• Correct inaccurate data
• Request deletion of your data (subject to legal retention obligations)
• Object to or restrict our processing of your data
• Receive your data in a portable format
• Withdraw any consent you’ve given, at any time
• Complain to us about how we handle your data

To exercise any of these rights, email us at hello@klaudius.dev.

Changes to this policy

We may update this policy. The date at the top shows the latest change, and we’ll email active customers about substantial ones.

Complaints

If you’re unhappy with how we handle your data, tell us first at hello@klaudius.dev. We’ll acknowledge your complaint within 30 days and tell you what we’ve done about it. You can also complain to the UK’s data protection regulator, the Information Commission (formerly the Information Commissioner’s Office), at ico.org.uk, or to the data protection authority where you live.