Vibe In One hosted terms

← Start a workspace · En français · Privacy policy

# Vibe In One Hosted Terms 1.2

These are the terms for the **hosted** Vibe In One service — a workspace at
`<name>.<zone>` that we run for you. They are an agreement about a *service*.

They are not the software licence. The `LICENSE` file in the Vibe In One source is
proprietary and grants nobody any right to run the software without a written
agreement with us; it is not the document that decides what you may do with a
workspace we run, and these terms grant you no rights in the software itself.
Running your own copy of Vibe In One needs such an agreement, on separate terms,
which we may or may not offer — it is not part of this service and nothing here
entitles you to it.

Copyright 2026 Lawrence Collier. **We** and **us** below mean Lawrence Collier,
who owns Vibe In One and operates this service from Québec, Canada, and who can
be written to at **admin@vibeinone.ca**. **You** means the organisation whose
workspace it is.

These terms are published in English and in French. The French version is at
`/terms/fr` and is the one offered first to a customer in Québec; see section
16, which says which version governs.

---

## In short

The terms below are what actually count, but they say this:

* **A workspace is free for fourteen days, for up to ten people.** One trial
per organisation, not one per workspace.
* **After that, ten US dollars per person per month, per workspace.** A person
is an account that can sign in and has not been deactivated — the number your
own **Settings → Users** shows, and the only number we invoice from.
* **There is no free tier after the trial**, and no cheaper way to have the
same thing. What you are buying is the workspace, run for you.
* **Two things the software enforces, and only two**: the trial stops at ten
people, and a workspace whose trial has ended or whose invoice is long unpaid
becomes read-only. Read-only, never deleted, and reversible the day you pay.
Everything else about the count is shown and settled between us.
* **Your workspace's contents are yours.** We do not read them, sell them,
train anything on them, or hand them to anybody unless the law makes us.
* **Runners are your machines.** The agent work happens on hardware you own,
under your own AI account and its own bill. We do not supply either.
* **You can cancel at any time**, from your own Settings, and everything you
have already paid for runs out before anything changes. Section 4 says what
we refund and what we do not.
* **Deleting stops the workspace immediately and destroys its data thirty days
later**, for good, with no copy kept.
* **Stripe is the seller on the receipt.** It takes the payment, charges
whatever sales tax applies where you are, and remits it; the service is still
ours and this agreement is still with us. Section 4.

---

## 1. What a workspace is

A **workspace** — a *tenant* in the software and in our own documentation — is
one address under our zone, one database, and one set of accounts. It is the
unit of everything below: of the trial, of the bill, of suspension and of
deletion.

One workspace is one bill. If you want a second workspace it is a second
subscription at the same price, counted separately, and the two do not pool
seats, share accounts or see each other's data — because in the software they
are two entirely separate databases with nothing between them.

## 2. Who you are

**Your organisation** is the legal entity, sole proprietorship or other
organisation the workspace is for, together with every organisation that
controls it, that it controls, or that is under common control with it. It is a
deliberately wide definition, for one reason: a single company should not be
able to be two customers by being described differently on two forms.

It matters in exactly one place — the trial is one per organisation — and
nowhere else. Everything else is per workspace.

## 3. The trial

A new workspace is free for **fourteen days** from the day it is created, for
up to **ten people**.

* It is **one trial per organisation**, not one per workspace and not one per
person. A second workspace created by the same organisation is not a second
trial, whatever it is called and whoever signs up for it.
* **The trial stops at ten.** Creating an eleventh account is refused while a
workspace is on the trial, and so is reactivating a deactivated one, with a
message saying so. Deactivating somebody frees their seat immediately, so ten
is ten people at a time and not ten people ever. The cap is on the trial and
on nothing else: a workspace that is being paid for has no limit at all.
* **On the fifteenth day, without a subscription, the workspace becomes
read-only.** Everybody can still sign in, read everything, and take their
data out; nothing accepts changes. It is not suspended, nothing is deleted,
and starting a subscription puts it back. See
[What the software enforces](#12-what-the-software-enforces) and section 9
for what happens to a workspace much later.
* We can end or refuse a trial — for a second trial by an organisation that has
had one, or for use we would refuse under section 11 — and we will say so in
writing to the address the workspace gave us.

## 4. What it costs

**Ten US dollars per person per month, per workspace**, once the trial is over.

* The count is taken **on the day each invoice is raised**, and it is the count
described in section 5. Somebody who joins the day after an invoice is not
charged for that month; somebody deactivated the day after one is not
refunded for it. There is no proration in either direction, and the symmetry
is the point.
* Invoices are monthly and due within **thirty days**. Fourteen days after that
the workspace becomes read-only under section 12; it is never deleted for
non-payment without the written notice section 9 describes.
* Prices may change under section 13, and never inside a month you have already
been invoiced for.
* Tax, where it applies, is on top, and is added by the seller named below at
the moment you pay rather than billed by us afterwards.

There is no minimum, no seat block to buy in advance, and no charge for a
workspace that has one person in it beyond that one person.

**Who takes the money, and whose name is on the receipt.** Payment is taken
through **Stripe**, which sells you the subscription as *merchant of record*.
Stripe is therefore the seller for that transaction: it charges you, works out
and collects whatever sales tax, GST, QST or VAT applies where you are, and
remits it to that government. Stripe transacts through **Link**, so the receipt
and the invoice come from Link, the purchase is labelled *Sold through Link*,
and your card statement reads `LINK.COM*` rather than our name. Nothing else
moves: the service is ours, this agreement is with us, and everything in this
document — the price, the count, the notice periods, what we store, what we do
not do — is unaffected by who processes the payment. Ask us if you ever need a
copy of an invoice or cannot tell a charge apart.

**Cancelling.** Cancel whenever you like, from **Settings → Billing** in your
own workspace or by writing to us. There is no notice period and no
cancellation fee. Cancelling ends the subscription at the end of the period you
have already paid for, and the workspace works normally until then — and for
the fourteen days after it that section 12 gives every workspace whose
subscription has ended. Then it becomes read-only rather than stopping or being
deleted. Nothing of yours is deleted because you cancelled: deletion only ever
happens under section 9, which is a thing you ask for.

**Refunds.** The month you are in is not refunded pro rata, in either
direction: the count is taken on the day the invoice is raised, somebody who
joins the next day is not charged and somebody deactivated the next day is not
refunded, and that symmetry is the whole of the arrangement. Two exceptions,
because they are the ones we would want in your place:

* **A month the service was substantially unusable in** — an outage or a
defect of ours that cost you a material part of it — is refunded, if you tell
us within thirty days of that month ending.
* **A charge raised after you cancelled**, or a duplicate one, is refunded in
full, and we do not need to be argued with about it.

Ask by writing to us. Where Stripe is the seller, we ask Stripe and the money
goes back to the card that paid it. None of this takes away a right you have
under consumer protection law where you live — in Québec, the *Consumer
Protection Act*, which applies to a consumer and not usually to a business
buying a business tool.

## 5. Counting people

A **person** is an account in that workspace that can sign in and has not been
deactivated.

* The accounts the software creates for itself — the AI assignee, the GitHub
importer, the author of items filed by an integration — are not people and
are never counted. They are marked as bots in the database and the count
excludes them.
* A **deactivated** account is not counted, and counts again the day it is
reactivated. Handing back a seat really does hand it back, the same day, with
no notice period and nothing to ask us for.
* Accounts are never *deleted* in Vibe In One — the schema will not orphan somebody
else's work — so deactivating is how a seat is returned, and it is a switch
your own administrator controls.

**It is the number on your own screen.** Settings → Users shows an active
count; the fleet page we invoice from runs the same query inside your own
workspace's database and gets the same number, by construction. There is
deliberately no second count that only we can see.

## 6. This is a service, not a copy of the software

A hosted workspace is Vibe In One with the machine rented from us. You do not
receive a copy of the software, and you do not run an installation. We do — on
our own hardware, under our own copyright.

So **the software's own licence decides nothing about a hosted workspace**, in
either direction:

* Nothing in that licence caps who may be in here, and nothing about the people
in here is counted under it. What decides who may be in a workspace is
section 4, and that is a price rather than a limit.
* A hosted workspace with thirty people in it is therefore not in breach of
anything. It is a workspace with a thirty-person bill.
* If you separately run a copy of Vibe In One under an agreement with us, that
agreement covers that copy and this one does not. The people in it are not
counted toward what you are invoiced for here, and the people here are not
counted toward it.

**These terms grant you no rights in the software.** They are not a licence to
it, they do not become one once you have paid, and taking your data out at the
end (section 9) is not the same as taking the software with you. Running
Vibe In One yourself is a separate arrangement on its own terms, offered at our
discretion — it is not the cheaper version of this one, and it is not something
this agreement gives you.

## 7. What we store, and where

Everything your workspace holds, and nothing else:

* **Your workspace's database**, in a storage object dedicated to that one
workspace: cards, boards, pages, canvases, chat, comments, activity, user
accounts (with passwords stored only as bcrypt hashes), sessions, settings
and the metadata for every attachment.
* **Your files**, in object storage under a key prefix that is your workspace's
name: attachments, screenshots and the recordings a runner uploads. Each file
is encrypted with AES-256-GCM before it is stored, under a key derived for
that one file of that one workspace, and is decrypted only when a member of
your workspace opens it. **Be clear about what that protects, too:** somebody
who can read the storage — through Cloudflare's dashboard, its support, or
credentials to the bucket — sees ciphertext. It does not put your files beyond
our reach: the key is held by the deployment, which is us, because the
service has to be able to decrypt a file to show it to you. The names, sizes
and dates of the stored files are not encrypted.
* **Secrets you put in Settings** — AI provider keys, a GitHub token, SMTP
credentials — encrypted at rest with AES-256-GCM, as rows in your own
workspace's database. **Be clear about what that protects:** the key is held
by the deployment, which is us, so this protects the values if the storage
behind them were ever disclosed. It does not put them beyond our reach, and
no encryption scheme that lets the software use a key can. If a credential
must never be reachable by anybody but the person who issued it, do not put
it in a hosted workspace — scope it down, or keep it on your own runner,
where an agent CLI's own login already lives. (Two things are not in that
category and are stronger: passwords and runner tokens are stored only as
hashes, so nobody here can read one back — including us, and including when
you have lost it.)
* **One row about the workspace itself**, in our fleet's own small table: its
name, whether it is being served, when it was created, which plan it is on,
what our billing provider last said about it, when it is due to be purged if
it is, an administrator's email address if you gave us one, and a free-text
note an operator may have written. That row is the only customer data that
lives outside your workspace, and the email address is there for the reason
it is needed: every reason to write to you — an unpaid invoice, a workspace
about to be purged, a workspace that will not start — is a reason we cannot
get *into* the workspace to look it up.
* **Ordinary operational logs** at the edge: hostnames, paths, status codes,
timings and errors. They are what makes an outage diagnosable. They are not
a copy of your content and are not kept as one.

**Where.** The workspace lives on Cloudflare's network, in the location nearest
whoever first used it, and moves only if Cloudflare moves it. We do not offer a
region guarantee today and will not pretend to: if where your data physically
sits is a requirement you have to satisfy, raise it **before** you sign up
rather than after. It is a conversation, and it is one the answer may be no to.

**Who else touches it.** Cloudflare, as the platform the service runs on, and
**Stripe**, which takes the payment and is the seller of record for it (section
4) and therefore holds your billing details rather than us — we never see a
card number. Nobody else. The AI provider, GitHub account, SMTP server and runner
machines your workspace talks to are yours, chosen by you in your own Settings,
and are not our sub-processors.

**Personal information.** Some of what is above is personal information about
real people — the accounts in a workspace, an administrator's email address,
what a log records. What we do with it, why, for how long, where it goes and
what you and the people in your workspace can demand of us is set out in the
**privacy policy at `/privacy`**, which names the person responsible for the
protection of personal information here and how to reach them. It is written to
Québec's *Act respecting the protection of personal information in the private
sector* and to Canada's *PIPEDA*, and it says the same things this section does
in the language those laws use. Where you are the one deciding what personal
information goes into a workspace — your colleagues' accounts, the people named
on a card — you are responsible for having the right to put it there, and we
handle it for you and for no purpose of our own.

**Backups** are two things, and they are worth telling apart. The platform
keeps **point-in-time recovery** for your workspace's storage, which can roll it
back to an earlier moment within its retention window. And every night your
workspace takes a **snapshot of its own database**, seals it with a key derived
for that workspace and nothing else, and puts it in a bucket only that workspace
can read from; the last seven days of them are kept and older ones are deleted.
They are listed, downloaded and restored from in your own **Settings →
Backups**, and they are as much yours as the rest of it. Nothing else copies
your database anywhere: not to another account, not to a laptop, and not
anywhere an operator can read it — a snapshot in anybody's hands is ciphertext.
Deleting a workspace destroys its snapshots in the same call that destroys its
files and its database, which is why a purge under section 9 really is final.

## 8. What we do not do

* We do not read your workspace's contents, and nothing automated reads them
either. There is no analytics pipeline, no phone-home and no usage telemetry
in Vibe In One — hosted or not.
* We do not train any model on anything of yours, and we do not let anybody
else.
* We do not sell, rent or share your data.
* We do not put advertising in the product.
* We will not hand your data to anybody except where the law requires it, and
where we are permitted to tell you that it happened, we will.

An operator can, unavoidably, reach the storage the service runs on — that is
true of every hosted service and it would be dishonest to imply otherwise. What
we do about it is a rule rather than a mechanism: we look inside a workspace
only when you ask us to, in writing, for a problem you have reported, and only
as far as that problem needs.

## 9. Deleting a workspace

You can ask us to delete a workspace at any time, in writing, from an
administrator of that workspace. Deletion happens in two steps and neither of
them is a surprise:

1. **It stops.** The workspace is taken off the air immediately. The grace
period protects the *data*, not the availability — a workspace that kept
working while it was being deleted is one people keep putting work into.
2. **Thirty days later the data is destroyed**: the database, every file under
that workspace's prefix, and every sealed snapshot of it. There is no undo,
no second copy and nothing left for us to restore from. Point-in-time recovery rolls a workspace back to
an earlier moment; it does not bring back storage that has been destroyed.

Inside those thirty days, one message from you calls it off and the workspace
comes back exactly as it was. We can lengthen the thirty days for you on
request, and we will never shorten it without asking you first.

We delete a workspace ourselves only after a suspension that has not been
resolved: an unpaid invoice, an unfinished trial, or use we have refused under
section 11. In every one of those cases you get **written notice to the address
on the account, at least thirty days before anything is destroyed**, and the
workspace stays restorable for the whole of that time.

**Getting your data out is your right and you do not need our help to do it.**
Everything in a workspace is reachable through its own API with an
administrator's token — that is the same API the software itself uses, and it
is not restricted on the hosted product. A single-button "export the whole
workspace" is not built yet; until it is, ask before the grace period runs out
and we will take a copy out for you at no charge.

## 10. Your runner, your machine, your AI account

Vibe In One runs a board's agent work on **your** machine. That is a design
decision rather than a limitation of the hosted product, and it has
consequences worth writing into an agreement:

* **We supply no compute for agent work and no AI subscription.** You install
the runner on hardware you control, you log its agent CLI in to your own
account, and the model bills you directly under your agreement with that
vendor. Nothing about a hosted workspace includes a model, credits or a
machine to run them on.
* **What happens on that machine is yours.** The runner clones your
repositories, runs your build and your tests, and lets an agent CLI edit a
working copy unattended. It runs as the user you install it as, with that
user's access. Choose that machine and that user accordingly.
* **Your code goes to your runner and to your AI provider, not to us.** The
hosted service holds what the workspace holds — the card, the brief, the
diff, the log the runner sends back — and never a checkout of your
repository.
* **The runner token and any provider key you configure are credentials that
matter.** Anyone holding a runner token can reach every repository a board on
that workspace can, and a provider key adds a billing channel of yours. They
are issued and revoked in your own Settings, and keeping them is your side of
this.
* **An agent is not a warranty.** Work an AI agent does on your machine, and
anything it commits, pushes or publishes, is yours — review it as you would a
colleague's. Nothing here makes us responsible for what a model wrote.

## 11. Using the service

Use it for anything lawful. We will suspend a workspace, with notice wherever
notice is possible, for: activity that is illegal where we or you are; using it
to attack, spam or defraud other people; deliberately trying to reach another
workspace's data or the platform underneath; or a workload whose only purpose
is to consume our capacity rather than to do your work.

That is the whole list, and it is meant to be. A tool for tracking work that
reserved the right to decide which work is acceptable would be a bad tool.

## 12. What the software enforces

Two things, and this section is the whole list.

**The trial stops at ten people.** An eleventh account is refused while a
workspace is on the trial, and the message says why. Deactivating somebody
hands their seat back the same day, so this is a limit on how many of you are
here at once.

**A workspace nobody is paying for becomes read-only.** That happens on the
fifteenth day of a trial with no subscription behind it, and it happens
fourteen days after an invoice goes unpaid or a subscription is cancelled — not
before. Read-only means everybody can still sign in, everything is still there,
everything is still readable, and every way of getting your data out under
section 9 still works. Only changes are refused.

**Nothing else is.** There is no licence key, no phone-home, and no check on
anything but those two. In particular, being read-only is not being suspended
and never turns into deletion on its own: a workspace is only ever suspended or
deleted by a person, under sections 9 and 11, and with the notice those
sections promise.

Read-only is meant to be an inconvenience you can end in an afternoon, and it
undoes itself the moment the subscription is right — there is nothing to ask us
for and no reactivation fee. If it has caught you at a bad moment, say so; we
would rather move the date than have you lose a sprint to an expired card.

## 13. Changing these terms

We can change these terms and the price, and we will tell you in writing at the
address on the account **at least thirty days before** either takes effect. A
change never applies retroactively to a month already invoiced.

If you do not want the change, tell us before it takes effect and the answer is
the same one it always is here: your data comes out, the workspace is deleted
under section 9, and you owe nothing beyond the months already used. Terms that
can be changed unilaterally are only fair if leaving is genuinely easy, so
leaving is genuinely easy.

The current version is always the one at `/terms` on the address you signed up
at, and it carries a version number at the top of it. We keep every earlier
version and will send you any of them on request — including the one your
workspace agreed to, which is the version that was current on the day it was
created, plus any change you have since been notified of under this section.

## 14. Availability, warranty and liability

**Availability.** We run this carefully and we do not promise an uptime figure.
There is no SLA today, and offering one we have not measured would be a number
rather than a commitment. If that is a requirement you have, say so — it is a
conversation, and until it is agreed in writing it is not part of these terms.

**Warranty.** ***As far as the law allows, the service is provided as is,
without any warranty or condition of any kind.***

**Liability.** ***As far as the law allows, our total liability to you under or
in connection with these terms, for all claims taken together, is limited to
what you paid us for the workspace in question in the twelve months before the
claim arose. We are not liable for lost profits, lost data, lost business or
any indirect or consequential loss.*** Nothing here limits liability that
cannot be limited by law — including liability for death or personal injury
caused by negligence, or for fraud.

Section 10 is the reason the paragraph above is not only boilerplate: the agent
work runs on your machines, under your accounts, against your repositories, and
we are not in a position to be liable for what it does there.

## 15. Your content is yours

You own everything you put into a workspace and everything the people in it
create there. You grant us the one permission running the service requires —
to store, copy and transmit that content for the purpose of operating the
workspace for you — and that permission ends when the workspace is deleted.

We own Vibe In One itself, and these terms grant no rights in the software. See
section 6.

## 16. Getting in touch, and the law

**Write to admin@vibeinone.ca.** Anything these terms call for "in writing"
means that address, or a reply from us to an administrator's email address on
the account. The same address is on the signup page and in the footer of our
home page, and it reaches a person rather than a queue.

**The law.** These terms are governed by the laws of the Province of Québec and
the laws of Canada applicable there, and the courts of the Province of Québec
have exclusive jurisdiction — except that nothing in this sentence takes away a
consumer-law right you have where you live, or the right of a consumer to sue
where they live.

**Language.** These terms exist in English and in French, and neither version
is a summary of the other. The French version is published at `/terms/fr` and
is the version offered first to a customer in Québec. If the two ever differ,
tell us: for a customer in Québec the French version governs, and elsewhere the
English does. *Les parties reconnaissent avoir eu l'occasion de prendre
connaissance de la version française des présentes conditions.*

If any part of these terms is unenforceable, the rest still stands.