Skip to content
Docs Flowy
Terms of service

The agreement,
written to be read.

These are the terms Docs Flowy is provided on. Where the law needs a particular form of words, it is here; where it does not, it is not. An agreement nobody finishes reading protects nobody.

Last updated

01

Who these terms are with

Docs Flowy is operated by Tulmira Ltd, company number 17497033, registered at 128 City Road, London EC1V 2NX. In these terms, we means Tulmira Ltd and you means the person or the organization using the service.

Creating an account, or using the service under an account somebody else created for you, accepts these terms. If you do not accept them, do not use the service.

Our privacy policy describes how personal data is handled. It forms part of this agreement and is not a separate promise.

02

What the service is

Docs Flowy reads the markdown documentation already in your git repositories and presents it as a navigable, searchable handbook. The folder structure is the navigation, and there is no configuration file to write.

On top of reading, the service records workflow state about a document — review and implementation status, notes and their replies, read receipts — and offers a read surface, plus one narrow write, to agents over MCP.

Access to your repositories is read-only. We do not clone a repository, we do not write to one, and we do not open anything in one on your behalf.

03

Accounts

You must be at least 16 and able to enter into a contract. The details you give us must be accurate, and you must keep them accurate.

A handle is claimed once and cannot be changed afterwards. It is written beside your name on rows that outlive the moment they describe — audit events, notes, statuses — and a rename would leave every one of them saying something that is no longer true.

You are responsible for what happens under your account and for keeping your credentials to yourself. Write to [email protected] if you think somebody has reached an account who should not have.

An account can hold a GitHub identity, a password, or both. Either can be removed. Neither can be removed while it is the last one, because that would leave the account with no way back in.

04

Organizations

Where you accept these terms on behalf of an organization, you confirm that you are entitled to bind it. The organization is then the customer, and these terms apply to everyone it admits.

What a person may do is decided by their role. An Owner administers everything, an Admin administers everything except ownership itself, a Member reads what they have been granted, and a Guest is narrower again. Roles are enforced by the service, not by a button being hidden.

An organization cannot be left with no Owner. The last Owner of an organization other people belong to has to hand it over or delete the organization before leaving it.

Removing somebody from an organization ends their access to it, including grants they held directly and through a team. It does not touch their account, which is theirs and not the organization's.

05

Your content

Your repositories and the documents in them are yours. Nothing here transfers any right in them, and we claim none.

To run the service we need permission to do what the service does, so you grant us a limited, non-exclusive, revocable licence to read, index, render, cache and display your content to the people and credentials you authorize, and for nothing else. We do not use your content to train models and we do not disclose it beyond the recipients named in the privacy policy.

The licence ends when you disconnect a repository or delete your account or your organization, and the copies we hold go with it. Your repository is untouched throughout: disconnecting leaves nothing behind in it, because nothing was ever put there.

You are responsible for being entitled to connect what you connect, and for the content itself being lawful.

06

Acceptable use

Do not use the service for anything unlawful, and do not use it to hold or distribute content you have no right to.

Do not attempt to reach data belonging to another organization, and do not probe for a way to. Reporting a hole you found is welcome and goes to [email protected]; walking through it is not.

Do not work around plan limits, rate limits, or the minimum review state set on an API key. Those are the shape of what was agreed rather than an obstacle inside it.

Do not resell the service or present it to a third party as though it were yours, unless we have agreed that in writing.

Connect only repositories you are entitled to connect. The service asks GitHub as you rather than as an installation for exactly this reason, and getting around that breaches these terms as well as GitHub's.

07

GitHub, GitLab and other sources

Your agreements with GitHub and GitLab are yours, and these terms change nothing in them. What we can do with a source is bounded by the access you grant and by nothing else.

A GitLab connection uses a project or group access token that you paste. We refuse a token carrying a write scope and a token with no expiry, and that refusal has a visible consequence: we cannot create a GitLab webhook for you, so freshness there is a poller rather than a push.

If a source becomes unavailable, changes its API, or withdraws the access you granted, the documents that depend on it stop updating. A third party's decision about its own service is not something we can be responsible for.

08

AI features

AI features are off until an organization turns them on, and only somebody entitled to do so can turn them on. The change is recorded in that organization's audit trail.

Use is metered in credits. A cached answer spends none, and an empty document makes no call at all.

Generated output can be wrong, incomplete, or confidently both. It is provided with no warranty of any kind, and a person has to check it before anything is relied on. Nothing the service generates is professional advice.

An agent may state that feedback has been addressed. It cannot close a note — that stays with a person, and there is no setting that changes it.

09

Plans, billing and credits

Reading is unlimited on every plan and so is the number of people in an organization. What a plan sells is a monthly pool of AI credits and the number of repositories you may connect.

Seats are billed on the period's high-water mark: everybody who held a seat at any point during the period, counted once. Growing a team is charged when it happens, and shrinking one does not refund the part of the period those people were there for.

Payment is taken through Stripe. Amounts exclude tax unless stated otherwise, and tax is added where it applies. If we change a price, an existing subscription keeps its amount until we move it, and the new amount appears on the next invoice rather than as a charge or a refund on the day.

If a payment fails we may restrict the parts of the service the plan pays for until the invoice is settled. We also notify the people who hold billing rights in the organization rather than only whoever happened to hit the wall, because they are usually not the same person.

You can cancel at any time. Cancellation takes effect at the end of the period you have already paid for, and the plan runs until then. We do not refund the unused part of a period beyond what the law requires.

10

Availability and change

We work to keep the service up, and we promise no service level except one written into a separate agreement. Free carries none at all.

Maintenance happens, sometimes without notice when it is a security fix. Features change: we add them, and occasionally we remove one. Where a removal materially reduces what a paid plan provides, we tell paying customers before it takes effect.

The things the product refuses to do — write to your repository, ask a model a question you typed yourself, let an agent close somebody's note — are part of what you are buying rather than limitations we are working to remove.

11

Suspension and termination

You can stop using the service whenever you like: disconnect every repository, and delete your account or your organization from inside the product.

We may suspend or end access where these terms are breached, where an invoice stays unpaid, or where the law requires it. Where the situation allows, we tell you first and give you a chance to put it right.

After termination we remove data on the schedule the privacy policy sets out. Your repositories are untouched either way — they were never ours, and we never wrote to them.

The sections on your content having reverted, liability, indemnity and governing law survive the end of this agreement.

12

Warranties and liability

The service is provided as it stands. To the extent the law allows, we exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement, and we do not warrant that the service will be uninterrupted or free of error.

To the extent the law allows, we are not liable for indirect or consequential loss, for lost profit, revenue or goodwill, or for loss of data you could have avoided by keeping your own copy — your documents live in your git repositories, and that is the copy.

Where we are liable, our total liability for all claims arising in any twelve-month period is limited to the amount you paid us in the twelve months before the claim arose. Where you paid us nothing, it is limited to one hundred euros.

None of this excludes or limits liability that cannot lawfully be excluded, including liability for death or personal injury caused by negligence, for fraud, and for anything else the law puts beyond exclusion.

If you are a consumer in the European Union, your statutory rights are unaffected by this section or by anything else in these terms, and nothing here overrides the mandatory consumer protection of the country you live in.

13

Indemnity

This section applies where you use the service for business purposes. It does not apply where you use it as a consumer.

You will indemnify us against claims, losses and reasonable costs arising from content you connected without being entitled to, from use of the service in breach of these terms, and from your breach of a law that applies to you. We will tell you about any such claim promptly, let you conduct the defence where you want to, and not settle it without your agreement.

14

Changes to these terms

We may change these terms. Where a change is material we give at least 30 days' notice, by email or in the product, before it takes effect, and continuing to use the service after that date accepts the change.

If a material change is unacceptable to you, end your subscription before it takes effect. Where you have paid for a period running past that date, we refund the unused part.

This version takes effect on 2026-09-19 and replaces any earlier one.

15

Governing law and courts

These terms are governed by [GOVERNING LAW], and the courts of [COURTS] have jurisdiction over any dispute arising out of them.

If you are a consumer, that does not deprive you of the protection of the mandatory rules of the country you live in, and you may bring proceedings in your own courts where the law gives you that right.

The European Commission's online dispute resolution platform is open to consumers in the EU. We would rather hear it directly first, at [email protected].

16

Contact

Tulmira Ltd, company number 17497033, 128 City Road, London EC1V 2NX. Questions about these terms go to [email protected]. Security reports go to [email protected], which is read by the people who wrote the code.