Legal
Who you are dealing with, the proprietary licence, the terms you agreed to, what we hold, and who to write to.
Who we are
beafk and beafk cloud are made and operated by CyberFruit Lab - FZCO, a free
zone company in Dubai, United Arab Emirates, trading as beafk. That company
holds the copyright in both halves, it is the party you are agreeing with, and
everything below is under the law of the Dubai International Financial
Centre, with the DIFC Courts as the place a dispute is settled.
The four documents, and none of them is longer than it needs to be:
| |
|---|
| Terms of service | the agreement between you and us |
| Privacy | what we hold, who else touches it, and how to make us stop |
| The licence | what may be done with the software itself, in full |
| This page | the map of the other three |
The licence
beafk is proprietary, both halves — this service and the program on your
machine — and it is not open source. The whole text is
one page, published rather than left in a repository nobody
outside this company can open: the terms make it part of the agreement, and a
document you are bound by should be a document you can read. That page is the
copy the terms name, and the one that governs.
Third-party dependencies keep their own licences.
The terms
The terms of service are the agreement itself. They are written to be
read: every clause is a sentence about something the system actually does, and
each one can be checked against this documentation.
What we hold about you
Set out in full on the privacy page, and in the same words for
somebody deciding whether to install in what beafk can
see. The short version: your account, your workspace
and its people, a row per machine with its addresses encrypted, who opened what,
and your subscription. Not your code, not your chats, not your agents'
keys, and no way into your machines.
The services underneath — identity, payments, analytics, the network in front of
us — are named on the privacy page, and a new one is named there before it
starts.
Your data, when you leave
Your machines and everything on them are yours and are never touched by
anything here. Ending a subscription closes the panel's door and deletes
nothing — see
when a subscription lapses.
Deleting your account is immediate and is described exactly, including what it
does not remove, in
deleting your account.
The agents' accounts are yours
beafk is not a reseller of anybody's models. We do not provide, lend, share,
sell or resell accounts, subscriptions, API keys, tokens, credits or model
capacity, in any form. You bring your own account with Anthropic, OpenAI,
xAI or Moonshot AI, you sign it in on your own machine, and they bill
you directly for what it does.
Their terms are what govern that use, and following them is yours: acceptable
use, rate limits, rules about sharing or automating an account, and which
countries they serve. Their credentials never reach us — they live in each CLI's
own file on your machine.
A seat here buys the machine's door, the panel and the plumbing around the
agents. It buys no tokens. See what the plans include.
Other people's names and logos
beafk runs coding agents other people make and names them on screen so you can
tell which is which. Claude Code, Codex, Grok Build and Kimi
Code — and their icons — belong to Anthropic, OpenAI, xAI and Moonshot AI
respectively; Tailscale, GitHub and the services under the cabinet
belong to theirs.
Showing a mark says which product is meant and nothing more: no affiliation, no
sponsorship, no endorsement, and none of those companies is a party to what you
buy here. What you agreed with the maker of an agent stays between you and them.
beafk and its own marks are ours. You may say truthfully that you use beafk;
anything further needs our written say-so.
Payments
Handled by a payment processor. We never hold your card number.
Who to write to
One address, for all of it — a machine, a bill, an enterprise contract, a
licensing question, or a sentence on one of these pages you think is untrue:
hi@beafk.app.
Teams customers get priority support.