# Welvets privacy policy

Last updated: 15 November 2026

Your data is yours. This policy explains what personal data we collect when you use Welvets, why we collect it, who else handles it, how long we keep it, and what rights you have. We collect the data we need for the purposes in section 3.

In this policy:

- "Betalgo", "we" and "us" mean Betalgo Up Ltd, the company named in section 1.
- "Welvets" or "the service" means the website at welvets.com, the app at app.welvets.com, the API, and the Queen program that runs on a customer's computer.
- "Onelink" means Sold through Link, LLC, Stripe's affiliate that sells Welvets plans and top-ups to customers as the merchant of record.
- A "customer" is the business or person that uses Welvets under our [terms of service](https://welvets.com/terms.md). "You" means anyone whose personal data this policy covers: website visitors, people on our early-access list, members of our community, customers and the people who use Welvets for them.

## 1. Who we are

Welvets is run by Betalgo Up Ltd, a private limited company registered in England and Wales, company number 11843965, registered office 565 Green Lanes, London, England, N8 0RL.

We are the controller (the organisation that decides how and why personal data is used) for:

- account and sign-in data,
- data from our website, including the early-access form,
- billing data we receive from Onelink and the plan records we keep,
- the computer, usage and security data we need to run the service,
- personal data inside customers' events and run logs, when we use it for our own purposes, such as analytics or training AI models (section 4),
- emails between you and us, and
- what you post in our community on Discord.

When we provide Welvets to a customer, we act for that customer for the personal data inside their events and run logs. Section 4 explains both roles.

**Who is responsible for data protection.** Tolga Kayhan, our director. You can reach him at contact@welvets.com.

**Contact us** about anything in this policy at contact@welvets.com, or by post to Betalgo Up Ltd, 565 Green Lanes, London, England, N8 0RL.

**If you're in the EU.** Our contact for people in the EU is Tolga Kayhan, our director, at contact@welvets.com.

Sign-in happens at auth.welvets.com, a sign-in service that Betalgo runs for its products. Our emails come from mail.welvets.com.

## 2. What we collect

### When you sign in and use your account

You can sign in with Google, GitHub, or an email address and password. Sign-in goes through our own sign-in service, which runs on Keycloak (an open-source sign-in system). We store:

- your user ID, email address, display name and first name,
- your default workspace, your roles and when you joined,
- your workspace's name, and
- the Stripe customer ID that links your workspace to its billing.

If you sign in with Google or GitHub, we get your email address and name from them. The Welvets app itself doesn't store passwords.

### Your workspace

A workspace is where a customer sets up Welvets. It holds your role in it, the tools you connect, and, for GitHub, the repositories you choose. The access tokens that connect Welvets to your tools are stored encrypted on our servers.

A workspace owner can also give us an AI provider's API key, such as an OpenAI key, where their agent needs one. We store it encrypted, like the other tokens, and use it to run that workspace's agents: we pass it to the Queen on the workspace's computers.

### Events from tools you connect

When you connect GitHub, Linear or a similar tool, it sends us events, such as a new issue or a comment on a pull request. We store:

- the full event exactly as the tool sends it. It can include other people's names and email addresses, and the content of repositories and issues,
- who sent the event and who received it, and
- for GitHub, the repositories you chose.

### Runs and their logs

When an event wakes your agent, the Queen on your computer sends us the run's progress, logs and results, so you can follow them in the app. Before sending, the Queen masks secrets in the formats it knows. It can't recognise every possible secret, so avoid making your agent print secrets of your own.

Today, your agent runs on your computer with your own AI tool, and that tool's provider handles what your agent sends it, under its own terms. From your runs, we receive what the Queen sends us.

### Details of your computer

When you connect a computer, the Queen tells us its hostname (the computer's name, which may include yours), operating system, processor type and Queen version, when it registered and when we last heard from it.

### IP addresses

We use IP addresses in hashed form (turned into a scrambled code) to apply rate limits, which stop anyone sending too many requests. We keep them in memory for about a minute, and never write them to storage.

### Usage counters

Each day we count, for each workspace, the events received, the run time, and the amount of data stored. We use these counts to work out credits, and for the other purposes in section 3.

### Billing data from Onelink

Onelink sells Welvets plans and top-ups to you on our behalf, as the merchant of record. It charges your card, issues receipts and invoices, and collects tax. Stripe holds your card, subscription and tax details; we don't store your card details.

Onelink passes us order data: your name, email address, billing address, tax ID and order details. Once we have it, this policy covers it. We also keep:

- your plan, its state and your billing period,
- the amount of any invoice that failed to pay,
- how long you've been with us, which sets your loyalty credits, and
- your referral code and a list of your referrals with their dates. We don't show you the names of the people you refer.

How Onelink and Stripe handle your data is covered by their own terms and privacy policy, which you see at checkout. Onelink's customer terms are at https://stripe.com/gb/legal/consumer#sold-through-onelink-terms.

### Emails

We send you:

- account emails from our sign-in service, such as checking your email address or resetting your password, and
- billing warnings: when you've used 80% of your credits, when you reach zero, when a payment fails, and when new runs stop. We send these through Cloudflare's email service. They are plain emails with no tracking.

Onelink sends your receipts and invoices.

When you email us, your message reaches us through Google Workspace. We keep it so we can answer you and refer back to it later.

### Our community on Discord

Our community, the [Betalgo Developers Community](https://discord.gg/YQySmNrT2T), is a server on Discord. If you join it:

- Discord's own terms and privacy policy apply to your use of Discord.
- What you post there can be seen by other members and by us.
- We may use what you post to answer questions and to improve Welvets, for the purposes and on the lawful bases in section 3.

### The early-access form

Welvets isn't open to the public yet. If you join the early-access list on our website, we store your email address and the time you signed up. When you submit the form, Cloudflare Turnstile checks that a person, not a bot, is sending it.

### Cookies and browser storage

We use no analytics or advertising cookies, in the app or on the website. The app sets only cookies it needs to sign you in and connect your tools. The website sets none. On the early-access form, Cloudflare Turnstile checks that you are a person.

| What | Where | What it does | How long it lasts |
|---|---|---|---|
| Session cookie (`welvet_browser_session`) | App | Keeps you signed in | Up to 30 days, or until you sign out |
| Sign-in cookies (`welvet_oauth_state`, `welvet_oauth_pkce`) | App | Complete a sign-in safely | 10 minutes |
| Connection cookies (`__Host-welvet_provider_…`, `__Host-welvet_agent_…`) | App | Complete connecting a tool, such as GitHub, safely | 10 to 15 minutes |
| Cloudflare Turnstile check | Website, early-access form only | Tells people from bots | Runs only when you submit the form |

The app also keeps a few things in your browser's own storage. None of it is sent to us. You can clear it at any time in your browser settings.

| What | What it does | How long it lasts |
|---|---|---|
| Referral code | Remembers the code from a referral link until your workspace can claim it | Until the code is claimed or refused |
| Last-visit time and a "seen" flag for your first successful run | Show a welcome-back note and a first-run message only once | Until you clear your browser storage |
| Interface settings, such as the dashboard period and which runs the activity list shows | Remember your choices | One hour for the dashboard period. The rest last until you close the tab. |
| Drafts and return pages, such as a half-filled form, an invite you opened while signed out, and the page to return to after signing in | Save your place so you don't lose work | Until you close the tab, or until used |

## 3. Why we use your data, and our lawful basis

The law lets us use personal data only for a lawful reason. We rely on these:

- **Contract:** we need the data to provide the service a customer has signed up for.
- **Legitimate interests:** we need it for a reasonable purpose of our own, which we name below, and that purpose isn't outweighed by your rights.
- **Legal obligation:** the law requires it.
- **Consent:** you have agreed. We use this only for the early-access list.

| What we do | Data we use | Lawful basis |
|---|---|---|
| Create your account, sign you in and run your workspace | Sign-in and account data, workspace | Contract |
| Run the service: receive events, wake your agent, show runs, logs and results, and keep track of your computers | Events, runs and logs, computer details | Contract. For other people's data inside events and logs, we act for the customer (section 4). |
| Work out credits, apply your plan, referral and loyalty credits, and stop new runs when credits run out | Usage counters, billing data | Contract |
| Send account emails and billing warnings | Email address, plan state | Contract |
| Keep Welvets secure: rate limits, bot checks, system logs | Hashed IP addresses, the Turnstile check, system logs | Legitimate interests: protecting Welvets, our customers and the tools they connect from attacks, spam and misuse |
| Find and fix faults, and restore data after a failure | System logs, backups | Legitimate interests: keeping the service working and able to recover |
| Analyse how Welvets is used | Account data, events, runs and logs, usage counters, system logs | Legitimate interests: developing and improving our products |
| Debug and test Welvets | Account data, events, runs and logs, usage counters, system logs | Legitimate interests: developing and improving our products |
| Improve Welvets and develop new products and features | Account data, events, runs and logs, usage counters, system logs, posts in our community | Legitimate interests: developing and improving our products |
| Train, fine-tune, test and evaluate machine-learning and AI models, including our own | Account data, events, runs and logs, usage counters, system logs | Legitimate interests: developing and improving our products |
| Answer your emails, and your questions in our community | Your email address or community name, and what you tell us | Legitimate interests: replying to people who contact us. Contract, where you're a customer asking about your plan. |
| Tell you when registration opens | Early-access email address | Consent. You can withdraw it at any time. |
| Meet legal duties, such as a valid order from a court or authority | Only what the order covers | Legal obligation |
| Make, defend or settle legal claims | The records that matter to the claim | Legitimate interests: protecting our legal rights |

For analysing, debugging and testing, developing products and training AI models, the data can include other people's personal data inside customers' events and logs. For those purposes we're its controller (section 4). You can object to any of these uses (section 8).

If you use Welvets as a member of a customer's team, rather than as the customer, our contract is with the customer. For your account data we then rely on our legitimate interest in providing the service the customer has signed up for.

## 4. Our two roles for data in customers' events

Events and run logs can contain other people's personal data, such as the name and email address of someone who opened an issue. We handle that data in two roles:

- **When we provide Welvets to a customer,** the customer decides what Welvets handles, by choosing which tools to connect and what their agent does. For that, the customer is the controller and we're their processor: we handle the data for them, on their instructions.
- **When we use it for our own purposes,** such as analysing, debugging and testing, developing products, and training and evaluating AI models (section 3), we're its controller. Our [terms of service](https://welvets.com/terms.md) (section 6) give us these rights, and customers agree to them.

Our terms ask customers not to send especially sensitive data through Welvets, such as health data or government ID numbers.

**Customers:** a data processing agreement is available on request at contact@welvets.com.

**If your data is in a customer's events** (for example, you contributed to a customer's GitHub repository): for how the customer uses Welvets, please contact that customer. If you contact us about that, we'll pass your request on to them and help them answer it. For our own uses described above, you can contact us directly, including to object (section 8).

## 5. Who we share your data with

We share personal data with the providers below, so they can help us run and develop Welvets, and with the tools you choose to connect.

| Provider | What they do for us | Where |
|---|---|---|
| Cloudflare | Hosting, databases, file storage, sending email, and the bot check on the early-access form | Data stored in Cloudflare's EU jurisdiction. Requests may be processed in Cloudflare locations worldwide. |
| Microsoft Azure | Sign-in data | Germany |
| Neon, on Amazon Web Services | Sign-in data | Frankfurt, Germany |
| Stripe and Onelink | Checkout, payments, tax, receipts and invoices, and payment and subscription questions | The United States, and other countries where Stripe and its service providers operate, such as India |
| Google Workspace | Receiving emails you send us | Countries where Google and its subprocessors have facilities, including the United States |
| AI model providers we use to train or run models, under contract | Training, fine-tuning, testing, evaluating and running machine-learning and AI models for us | Depends on the provider (section 6) |
| Discord, if you use our community server | Runs the server for our community | Discord's own locations, including the US |
| GitHub | Only if you connect it: sends us events from the repositories you choose | The United States, and other countries where GitHub and its providers operate |
| Linear | Only if you connect it: sends us events | Mainly the United States, and other countries where Linear's providers operate |

GitHub, Linear and Discord are services you choose to use. We exchange data with them because you connect them or join our community there, and their own terms and privacy policies apply to what they hold.

We update this list before we start using a new provider.

We also share personal data when the law requires it, such as a valid court order. We share only what the order covers.

If Betalgo is ever sold or merges with another company, we'll tell you before your personal data moves or falls under a different privacy policy.

## 6. Sending data outside the UK and EU

We store the data inside Welvets in the EU: Cloudflare keeps it in its EU jurisdiction, and our sign-in data is in Germany. We are a UK company. UK law treats EU countries as protecting personal data adequately, and the EU has an adequacy decision for the UK, so data can move between the UK and the EU.

Some data is handled outside the UK and EU:

- Cloudflare may process requests in its locations worldwide, even though it stores the data in the EU.
- Stripe and Onelink, Google Workspace, the AI model providers we use, Discord if you join our community, and GitHub and Linear if you connect them, may handle data in other countries, including the US.

When personal data goes to a country without an adequacy decision, we rely on one of these safeguards: the UK-US data bridge or the EU-US Data Privacy Framework, where the provider is certified under them, or standard contractual clauses approved by the UK and the EU. Email contact@welvets.com for a copy of the safeguards that apply.

Which safeguard applies depends on the provider:

- **Cloudflare:** its data processing terms are part of its standard customer agreement. For UK personal data they use the EU standard contractual clauses with the UK International Data Transfer Addendum, and Cloudflare also relies on the Data Privacy Framework where it is certified.
- **Stripe and Onelink:** Stripe's data processing terms are part of its services agreement. They use the EU standard contractual clauses with the UK Addendum. Stripe, LLC also says it follows the UK Extension to the EU-US Data Privacy Framework.
- **Google Workspace:** Google says it relies on UK adequacy regulations, the UK Extension to the EU-US Data Privacy Framework, and standard contractual clauses.
- **Microsoft Azure and Neon:** they store our sign-in data in the EU. If anyone outside the UK and EU reaches it, the safeguards in their own data processing terms apply.
- **Discord, GitHub and Linear:** these are services you choose to use, and their own terms apply. Discord and GitHub say they follow the UK Extension to the EU-US Data Privacy Framework. Linear's data processing terms use the EU standard contractual clauses with the UK Addendum.

## 7. How long we keep your data

| Data | How long we keep it |
|---|---|
| Event and run history shown in the app | About 30 days |
| System logs | 7 days |
| Backups | 30 days |
| Archive of events | While your plan is active. We delete it with the rest of your workspace data, 90 days after your plan ends. |
| Account and workspace data, including connections, computer details and billing records | While your plan is active, and for 90 days after it ends, so you can come back. Then we delete it. |
| Usage counters | While your workspace exists. When we delete the workspace, we delete its counters too, or keep only totals that can't be linked to anyone. |
| Hashed IP addresses used for rate limits | About one minute. We keep them in memory only, to count requests, and never write them to storage. |
| Early-access email addresses | Until registration opens, or until you ask us to delete yours |
| Emails you send us | Two years after your last message |
| Posts in our community on Discord | Until you delete them or we remove them. Discord's own rules also apply. |

**Deleting your account.** There's no delete button yet. To delete your account, email contact@welvets.com from the email address on your account. We'll delete it and confirm within one month. Copies in our backups disappear within 30 days after that.

**Data already used to train models.** Deleting data removes it from our stores and then from our backups, as this section describes. But if we've already used it to train an AI model, the model may keep what it learned from it, and we can't take that back out. Data we've already de-identified or combined, so that it no longer identifies anyone, may also remain.

We keep data longer than shown only when the law requires it, or to deal with a dispute or legal claim, and only for as long as that lasts.

## 8. Your rights

You have these rights over your personal data:

- **Access:** ask for a copy of your data and how we use it.
- **Correction:** ask us to fix data that's wrong or incomplete.
- **Deletion:** ask us to delete your data. We may keep what the law requires us to keep. Section 7 explains what deletion can't undo.
- **Restriction:** ask us to limit what we do with your data, for example while we check whether it's accurate.
- **Portability:** get the data you gave us in a common, machine-readable format, or ask us to send it to another provider.
- **Withdrawing consent:** where we rely on your consent (the early-access list), you can withdraw it at any time. This doesn't affect what we did before.

We don't make decisions about people by automated means that have legal or similarly serious effects on them. The service does stop new runs automatically when a workspace runs out of credits, as our terms of service explain; that's how the plan works, not a decision about you.

### Your right to object

Where we rely on legitimate interests (see section 3), including analysing how Welvets is used, debugging and testing, developing products and training AI models, you can object at any time, for reasons to do with your situation. We will then stop, unless we have compelling reasons that outweigh your interests, or we need the data to make or defend a legal claim. We don't send marketing emails. If we ever do, you can object at any time and we will stop.

### How to use your rights

Email contact@welvets.com. We may ask you to confirm who you are, for example by writing from the email address on your account. It's free. We'll reply within one month. If a request is complex, or you send us several, we may take up to two more months; if so, we'll tell you why within the first month.

If your data is in a customer's events or logs, we act for that customer when we provide Welvets to them (section 4). For that, please ask the customer first; we'll help them answer. For our own uses of that data, ask us.

## 9. Complaints

If you're unhappy with how we've handled your personal data, tell us at contact@welvets.com. We'll acknowledge your complaint within 30 days of receiving it, look into it without undue delay, and tell you the outcome.

You can also complain to the Information Commissioner's Office (ICO), the UK's data protection regulator, at https://ico.org.uk. If you're in the EU, you can complain to the data protection authority where you live or work, and you can contact Tolga Kayhan, our director, at contact@welvets.com.

## 10. How we protect your data

- You sign in through our own Keycloak sign-in service. The Welvets app holds no passwords.
- Access tokens are stored encrypted on our servers.
- The Queen masks secrets in known formats before it sends us logs.
- We use IP addresses in hashed form, for rate limits.
- Our billing emails carry no tracking.

If a security breach puts your personal data at risk, we will tell you and the ICO as the law requires.

## 11. Children

You must be 18 or over to use Welvets. It isn't meant for children, and we don't knowingly collect children's personal data. If you think a child has given us personal data, email contact@welvets.com and we'll delete it.

## 12. Changes to this policy

We'll update this policy when the service or the law changes, and change the date at the top. If a change matters to you, such as a new kind of data, a new purpose or a new provider, we'll tell account owners by email or in the app before it takes effect.

Questions about this policy or your data? Email contact@welvets.com.
