Skip to content
Takeida
LegalTerms of Service

Terms of Service

The agreement between you and us. It is short where it can be and specific where it matters, which is mostly the parts about who owns what you write and what happens when you let somebody adapt it.

Effective
13 September 2026
Version
0.1
Status

Draft, pending legal review

What you keep

Copyright in everything you write. We claim none of it.

What we take

Only the licence needed to store and show your work to the people you authorised.

What it costs

Nothing during beta. There are no billing terms here yet.

The short version

A plain reading of the sections below. It is not a substitute for them, and where the two differ the sections govern. It is here because a contract nobody reads protects nobody.

  1. You own what you write.

    Copyright stays with you or your organization. We take only the permission we need to store it, show it to the people you chose, and back it up.

  2. Publishing is not permission to take.

    Making a Concept public lets people read it. It does not let anyone adapt it, and it does not let anyone's Agent work on it. Those are separate decisions.

  3. You name the terms for adapting.

    If you make a Concept adaptable you pick one of four Creative Commons licences. Adapters get a straight answer instead of a guess.

  4. That grant does not reach backwards.

    Switching adaptable off stops future adaptations. The ones already made were made under the licence you named, and they stay made.

  5. You are answerable for your Agent.

    An Agent can propose and can never publish. The audit record names the person whose Agent it is.

  6. You can leave with everything.

    Export runs while your account is live, and for 30 days after it ends. It is a folder of ordinary Markdown, not an archive only we can read.

Who this is between

These terms are an agreement between you and [ENTITY NAME], a company to be incorporated in Nigeria at [REGISTERED ADDRESS]. In this document, "we", "us" and "Takeida" mean that company, and "you" means the person or organization using the service.

The company is not yet incorporated. Those two placeholders are left visibly unfilled rather than guessed at, and they will be completed before anybody is asked to agree to this.

The service is Takeida: a knowledge base where an organization writes, reviews and keeps what it knows, and can publish some of it. A Concept is one such knowledge base. A Draft is where writing happens before it is official. A Proposal is a request that a Draft become part of the record, and the trunk is what has been approved.

Using the service means you accept these terms. If you are agreeing on behalf of an organization, you are confirming that you may bind it.

Your account and your organization

You need an account, and you must be old enough to enter a contract where you live. Every account gets an organization when it signs up, including a one-person one.

  • Give us an address you actually read. It is how we reach you about the account, and it is how you get back in.
  • Keep your credentials to yourself. Anything done with them is treated as done by you until you tell us otherwise, so tell us quickly if that stops being true.
  • Your organization decides who may read, who may write and propose, and who may approve and publish. Those decisions are yours to make and yours to get right.
  • An account is for a person. Agents connect through their own keys, described in section 7, rather than by borrowing a person's sign-in.

Beta, and what that means for you

The service is in beta and free to use. There is no fee owed for current use, and there are no billing, renewal or refund terms in this document, because writing them for a product nobody pays for would be writing them twice.

What being in beta actually means:

  • Features change, including ones you rely on. We will not remove export, and we will not make review optional, because those two are what the product is. Most other things are subject to revision.
  • Availability is not guaranteed. There is no uptime commitment in this document and no service credit, because a free beta cannot honestly offer one.
  • Paid plans may be introduced. If they are, we will give you at least 30 days' notice before your use of the service would start to cost money, and you can export everything and leave in the meantime. We will not convert a free account to a paid one without you saying yes.

Keep your own backups of anything you cannot afford to lose. That is ordinary advice for any service and particularly honest advice for one in beta. Section 9 describes how to take everything with you at any time.

What you write stays yours

You keep copyright in everything you write. We claim no ownership of your content, and nothing in this agreement transfers any of it to us.

To run the service at all we need permission to do specific things with what you write. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, back up, transmit, process, reformat and display your content, strictly for the purpose of providing the service to you and to the people you have authorised. That licence is limited to those purposes and ends when the content is deleted, save for backups that expire on their normal cycle.

The reach of that licence follows your settings rather than our convenience. A private Concept is displayed to the people you gave access to. A public Concept is displayed to anyone with its address. You change that by changing the setting, not by asking us.

Publishing, and what it does not permit

A Concept starts private. You can make it public, and then anyone with its address can read what is on the trunk, without an account and without belonging to your organization.

Publishing changes who may read, and nothing else.

  • Only the trunk is public. Drafts stay private, because a Draft is somebody's unfinished thinking and publishing a Concept is not agreeing to be read mid-sentence.
  • Nobody outside can publish into it. The most an outside contributor can do is raise a Proposal for one of your people to judge. Review is unchanged by publishing.
  • You can make it private again. What was read while it was public has been read, and we will not pretend otherwise, but the door closes when you close it.

Publishing something to be read is not consent to have it taken.

This is a term of this agreement, not a statement of intent. Marking a Concept public grants a right to read it and grants nothing else. Anyone who takes, republishes or adapts a public Concept that has not been marked adaptable is doing so without a licence from its owner, and copyright applies to it exactly as it would to anything else they had not been given permission to use.

Two further decisions stay off until you make them, and neither is implied by publishing: whether the Concept may be adapted, covered in section 6, and whose Agents may work on it, covered in section 7.

Terms for adapting

Marking a Concept adaptable permits anyone who may read it to make an adaptation: a new Concept of their own, containing what you had published at the moment they took it.

Because that is a grant of rights, it needs to say on what terms. When you make a Concept adaptable you choose one of four licences, and that choice is what an adapter receives. A Concept with no licence named cannot be made adaptable, and that is deliberate: permitting adaptation without naming terms leaves every adapter guessing and every owner unprotected.

  • CC0 1.0

    May do
    Anything, including commercial use.
    Must do
    Nothing.
  • CC BY 4.0

    May do
    Anything, including commercial use.
    Must do
    Credit to the original writers.
  • CC BY-SA 4.0

    May do
    Anything, including commercial use.
    Must do
    Credit, and the adaptation carries these same terms onward.
  • CC BY-NC 4.0

    May do
    Non-commercial use.
    Must do
    Credit to the original writers.
  • No licence named

    May do
    Reading, and nothing else.
    Must do
    Nothing, because nothing is permitted. A Concept cannot be made adaptable in this state.
Creative Commons rather than a software licence, because this is prose. A fixed list rather than a text field, so an adapter gets an answer they can rely on instead of a paragraph somebody pasted without reading.

What the adapter gets, and what they do not

An adaptation contains every document on your trunk as it stood, with its paths, links, tags and properties, plus the Concept's description and its about page. It does not contain anyone else's history: no proposals, no reviews, no audit trail, no contributors, no followers, no ratings.

The adaptation is a new work in the adapter's organization, with its own new address. It starts private and non-adaptable whatever yours was set to. It records the address it was adapted from, so a reader can follow the trail back. Nothing the adapter does reaches your Concept, and nothing you do afterwards reaches theirs.

The original writing stays credited to the original writers. The licence you named governs what the adapter may then do with it.

The grant is irrevocable for adaptations already made

You can turn adaptable off at any time. Doing so prevents further adaptations from that moment. It does not withdraw the licence from anybody who already adapted the Concept, and it does not oblige them to stop using or publishing their work.

Turning adaptable off

Before

Three people adapted it while it was adaptable.

  • k4m2pxq7kept
  • b9wzr3xtkept
  • m7hq2vndkept

After

Nobody else may adapt it. The three already made are unaffected.

The count of adaptations never decreases, because it counts events that happened, and a switch flipped later does not unhappen them. The contract says the same thing the product already does.

Turning adaptable off leaves the licence recorded as it was, rather than clearing it, because adaptations already made were made under it and erasing it would misrepresent what those adapters were granted.

If you later choose a different licence, the new one applies to adaptations made after the change. It does not reapply to earlier ones. Each adapter holds what they were granted when they took it.

Agents

An Agent is a software assistant that connects through its own key rather than through a person's sign-in. Your organization decides whether Agents may work at all, and each Concept decides whose.

You are responsible for what your Agent proposes as if you had written it yourself. That is not a disclaimer we are inventing to avoid something: it is the rule the audit log already follows.

What the Agent does

Writes on a Draft and raises a Proposal, which one of your people still has to approve. It can never publish.

Who is answerable

The member whose Agent it is. The audit record names that person, because a person is what you can hold responsible and an instrument is not.

  • An Agent belonging to somebody outside your organization is capped at writer standing no matter what its owner holds elsewhere. It can propose and it can never publish.
  • Admitting outside Agents to a public Concept is its own setting and starts off. Letting strangers read never lets their machinery work.
  • Narrowing the setting takes effect immediately, including on work already under way, because the policy is checked every time an Agent does anything rather than once when it was set up.
  • Do not give an Agent access you would not give the person who runs it, and do not point one at a Concept whose contents you would not want a machine reading.

Bringing work in

Import brings a folder of Markdown you wrote elsewhere into a Concept. It always lands in a Draft, never on the trunk, and there is no setting that changes this.

When you import, you confirm three things:

  1. The content is yours to bring, or you hold permission from whoever does own it, sufficient for it to be stored and shown here.
  2. Bringing it in does not breach an obligation you owe somebody else, including a confidentiality obligation or a licence that forbids this use.
  3. Where it contains personal data about other people, you have a lawful basis for putting it here.

Import is the fastest way to move a very large amount of text into an organization at once, which makes it the most likely route for material that was never anyone's to bring. The Acceptable Use Policy deals with that directly. Importing something because it was published and readable is exactly the mistake the sentence in section 5 is about.

Taking work out

You can take everything you have written with you, whenever you want, as a folder of ordinary Markdown that opens correctly somewhere else.

  • Export is available for as long as your account is live, at no charge, with no cap on how often you run it.
  • After an account or organization is closed, export stays available for 30 days. After that the content is deleted on the schedule in the Privacy Policy, and we cannot get it back for you.
  • What travels is the trunk: the approved record, with attachments written alongside the documents and references rewritten to point at the files as they were saved. Work still on a Draft stays where it is.
  • Export of a Concept is governed by the same permission as adaptation, because taking a Concept onto a laptop and taking it into another organization are the same act from the owner's side.

If we ever discontinue the service we will give at least 60 days' notice and keep export working throughout. An export you cannot run is a promise we did not keep.

Acceptable use and suspension

The Acceptable Use Policy is part of this agreement and sets out what may not be published, how to report something, and how an appeal works. Read it: it is short, and it is the document most often cited at somebody.

We may restrict, unpublish, suspend or terminate access where that policy has been broken. We act proportionately and we tell you what happened and why, except where telling you would itself be unlawful. The ladder of what we do, and what skips straight to the end of it, is set out in that policy.

Ending this agreement

You can close your account at any time, from the settings, without asking us.

We may end this agreement by giving you 30 days' notice, or immediately where you have materially broken it, where continuing would expose us or another user to legal risk, or where we are required to. Immediate termination does not remove the 30 day export window in section 9, except where the content itself is unlawful to retain.

Sections 4, 6, 13, 14 and 15 survive termination, together with any licence already granted to an adapter under section 6.

Changes to these terms

We will change these terms. When we do, we will post the new version here with a new version number and effective date, and keep the previous one reachable so you can see what changed.

For a change that materially reduces your rights or increases your obligations, we will give at least 30 days' notice by email to the address on your account before it takes effect. Continuing to use the service after that date means you accept the new version. If you do not, close the account and export your work, and we will not charge you for the privilege.

What we do not promise

The service is provided as it is. To the extent the law allows, we make no warranty that it will be uninterrupted, that it will be free of faults, or that it will fit a particular purpose you have in mind. This is a beta, and section 3 says plainly what that means.

Some of what the service does depends on other people's software and infrastructure, named in the Privacy Policy. We choose them carefully and we do not control them.

Nothing here excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud.

Liability

Neither of us is liable to the other for indirect or consequential loss, loss of profit, loss of business, or loss of anticipated savings.

Our total liability to you under this agreement, for all claims taken together, is limited to the greater of the amount you paid us in the 12 months before the claim arose, or USD 100. During the beta, the first of those figures is zero, which we would rather state than leave you to work out.

You are responsible for content you publish and for content you import, and you will cover us against a third party claim that arises from either, where the claim is a result of you breaking section 5, 8 or the Acceptable Use Policy.

Governing law

This agreement is governed by the laws of the Federal Republic of Nigeria, and the courts of Nigeria have jurisdiction over any dispute arising from it.

We state that plainly rather than burying it, because a reader in London or Lagos or Chicago should not have to guess which country's courts apply. The business is Nigerian and the law that binds it is Nigerian, including the Nigeria Data Protection Act 2023.

Where you are a consumer, this does not take away rights you have under the mandatory law of the country you live in, and it does not stop you bringing a claim there if that law says you may.

The Privacy Policy explains how we handle the same question for privacy rights: one standard for everybody, set at the highest of the regimes, extended as a contractual commitment rather than claimed as a jurisdiction.

Contact

Questions about these terms go to legal@takeida.com. A person reads it. Anything else, including support and security reports, is on the contact page.

If a court finds part of this agreement unenforceable, the rest of it still stands. Our not enforcing something once does not mean we have given it up.