# Terms of service

URL: https://briq.cloud/legal/terms

> The agreement between you and briq: what we provide, what you are responsible for, and what happens when something goes wrong.

Last updated: 8 October 2026.

## 1. Who you contract with

Uplab SAS, RCS Lyon 823 752 175, VAT FR50823752175, 254 rue Vendôme, 69003 Lyon, France ("briq",
"we"). By creating an
account or using an API key, you accept these terms. If you accept for a company, you confirm you
may bind it.

## 2. The service

briq runs container images as isolated microVMs on your instruction, or on the instruction of an
agent holding your API key or connected by you, and provides an API, an MCP server and a dashboard
to drive them. What runs, and what it does, is your choice. briq is early software: features
change, and we give notice before breaking a documented API.

## 3. Your account and keys

You need accurate contact details and the capacity to contract.

**An API key is a bearer credential.** Anything done with your key, or by an agent you connected,
within the policy you set, is done on your behalf. Keep keys secret, give each agent the narrowest
policy that works, and revoke a key you suspect has leaked. We cannot recover a key: we only store
its hash.

Policies, spend caps and TTLs are enforced before every machine is created, but they are safety
features, not a financial guarantee: metering is reconciled against provider usage, so a cap can be
crossed by a small margin.

## 4. Acceptable use

No crypto mining, unsolicited mail, network scanning or attacks, content illegal in the EU, or
attempts to break tenant isolation. The [security page](https://briq.cloud/docs/security#abuse-policy) sets out the
abuse policy. You are responsible for having the right to run your images, and for what your briqs
process or serve. If you use briq as a business, you indemnify us against third-party claims arising
from what you run on it in breach of these terms.

## 5. Your data

What you put in a briq stays yours. We do not claim rights over it, train anything on it, or look at
it, except at your request for support or where abuse or the law requires. For personal data in
it, you are the controller and we are the processor; the [data processing agreement](https://briq.cloud/legal/dpa) is
part of these terms. Your account data is covered by the [privacy notice](https://briq.cloud/legal/privacy).

## 6. Price and payment

Usage is billed per second while a briq runs, at the published size rates, in euro, excluding VAT
where applicable. Amounts may be displayed in another currency at the current conversion rate; the
euro amount is what is billed. Payments are taken by our payment provider; every payment comes
with an invoice.

**Credits.** Usage is paid first from the team's credits, bought in advance or offered. A new
account receives 10 euro of free credits on its personal team once its email address is confirmed.
We may change or end the free-credit offer at any time; credits already granted stay. Credits are
not transferable, and refundable only where the law requires.

**Plans.** Hobby is free. Pro and Team are monthly subscriptions, paid in advance and
renewed each month until cancelled. What a subscription invoice charges for the plan is credited to
the team as usage credits for the period it pays for, used before any other credits; what is left of
them at the end of that period expires and is not refunded. An upgrade applies at once, and the
difference for the rest of the month is charged then and credited the same way. A downgrade or a
cancellation takes effect at the end of the month already paid for; a month started is not
refunded.

**Pay as you go.** With a card on file (the subscription's card on a paid plan, or a card added on
Hobby), a team whose credits run out keeps running: the usage past its credits is charged to that
card automatically, at least once a month. By subscribing or adding a card, you authorise us to
charge it for these amounts. If a charge is refused, the team goes back to credits until it is
paid. You may remove the card at any time; usage already incurred stays due.

**Without a card**, when a team's balance reaches zero, its running services are stopped and
nothing new starts until it is topped up. We give at least 30 days' notice by email before raising
prices.

## 7. Availability

There is no service level agreement. Briqs are ephemeral: a briq stops at its TTL, a briq whose
creation failed is destroyed 7 days later, and a destroyed briq and its volume are gone. Keep your
own backups.

## 8. Suspension and termination

You may close your account at any time; running briqs are destroyed. We may suspend an account or a
key immediately for abuse, a security risk to other tenants, non-payment, or a legal requirement,
warning you first where possible and always telling you why.

## 9. Liability

briq is provided as is; to the extent the law allows, implied warranties are excluded. Our total
liability for any claim is limited to the greater of what you paid us in the three months before
the claim or 100 euro, and excludes indirect loss, lost profit and lost data. Nothing limits
liability for death or personal injury caused by negligence, for fraud, or where French law forbids
it. Consumers keep their statutory rights.

## 10. Changes

We email account holders at least 30 days before a material change takes effect. Continuing to use
briq means you accept it; if you do not, close your account and we refund unused credits.

## 11. Law and disputes

French law applies, and the courts of Lyon have jurisdiction, without prejudice to a consumer's
right to sue at home. Please write to us first: [hello@briq.cloud](mailto:hello@briq.cloud).