Terms of Service

These terms govern your use of Knowl Cloud. They are written to be read, so they use plain language rather than legal idiom. Where a sentence is short and blunt, that is deliberate.

1. Who we are

Knowl Cloud is operated jointly by ĐỖ GIANG THÀNH ĐẠT and TRƯƠNG THÀNH LONG, both individuals resident in Vietnam. In these terms "we", "us" and "our" mean both of us together.

We have not yet incorporated a company. If Knowl Cloud is later transferred to a company we form or control, or to another successor that continues the service, we may transfer our rights and obligations under these terms to it so far as the law allows. We will tell you before that happens, and where the law requires your consent we will ask for it. A transfer will not by itself reduce any right these terms give you.

You can reach us at [email protected] for anything about these terms, your data or security, and at [email protected] for anything about a plan, a charge or a refund. Both are real mailboxes and a person reads them.

2. What Knowl Cloud is

Knowl Cloud is a hosted service that stores knowledge your team and your coding agents deliberately publish to it, and makes that knowledge available across the repositories and people in your workspace.

Customer Content means what you deliberately publish: atoms and the categories, reasoning, evidence, repository references and authorship attached to them, along with anything else you choose to include in a published item.

Knowl Cloud is offered for professional and business use. It is a tool for software teams, and it is not designed, priced or marketed for personal, family or household purposes. Where you nonetheless qualify as a consumer under the law that protects you, §14 applies.

Knowl itself — the command-line tool and engine that run on your own machine — is separate software under a separate licence. It is open source under Apache-2.0 and these terms do not govern what happens locally. These terms govern only the hosted service.

Knowl Cloud does not background-sync your repository, code index, embeddings or agent session history. If you deliberately put source code, logs or anything else inside something you publish, that material is part of what you chose to send us.

3. Accounts and eligibility

You need an account, which you create by signing in with Google or GitHub. You must be at least 16 years old to use Knowl Cloud.

Each account belongs to one person. Do not share a login — a shared login is how an audit record stops meaning anything, and the audit record is much of what Knowl Cloud is for.

You are responsible for activity under your account until you tell us it has been compromised. Workspace owners are responsible for who they invite and what permissions those people get.

If you use Knowl Cloud for an employer, client or other organisation, you confirm you have authority to do so and to accept these terms on its behalf.

4. Your content stays yours

As between you and us, you — and the organisation you use Knowl Cloud for — keep all rights in Customer Content. Publishing transfers ownership of nothing.

You give us only the licence needed to run the service: to receive, store, back up, transmit, index, search, scan for credentials, display to your workspace and export your Customer Content. That licence lasts as long as we hold the content and no longer. You confirm you have the rights and authority to grant it.

We will never use Customer Content to train, fine-tune, evaluate or improve any machine learning model. Not ours, not anyone else's. Not on a paid plan and not on a free one. Not after "anonymising" it. This is not a setting you have to find and switch off — there is nothing to switch off, because we do not do it.

We do not routinely read your Customer Content. A person may look at it only where reasonably necessary: because you asked us for support and gave us permission; to investigate a serious security or abuse problem; to comply with a valid legal obligation; or to protect you, another user or the service. Automated processing needed to run the product — credential scanning, indexing, search — is not human review.

5. What you must not publish

Knowl Cloud is for engineering knowledge — what your team learned, decided and verified. It is not a filing cabinet for personal information, and it is not built to be one.

You must not deliberately publish:

• Sensitive personal data, including data about health, biometrics, genetics, race or ethnic origin, political opinions, religious beliefs, trade union membership, sex life or sexual orientation, criminal records, or financial account details.
• Personal data about people outside your own team or workspace, unless you have a lawful basis and every permission needed to process it.
• Credentials. API keys, passwords, tokens, private keys.
• Anything unlawful, anything that infringes someone else's rights, and anything you do not have authority to publish.

Our server scans every publish and refuses content that looks like a credential. That is a safety net, not a promise to catch everything — the rule is yours to keep.

This section is about what you deliberately publish. The ordinary metadata Knowl Cloud generates about your own team — who published something, who changed a role, and when — is service and audit data, and our Privacy Policy describes how we handle it.

6. Your responsibility for what you publish

You warrant that you have the right to publish everything you publish and that it complies with §5.

Where Customer Content contains personal data, the person or organisation who decided to put it there decides why it is processed, and is responsible for that decision. We process it to provide Knowl Cloud on their behalf. Where the law calls that role a processor, that is the role we are in for that content. It is a different role from the one we hold over account, security, audit, device and operational data, where we decide the purposes ourselves — §1 of the Privacy Policy sets out both.

If your use of Knowl Cloud needs a notice, a consent, another lawful basis, or a data processing agreement, putting that in place before you publish is yours to do.

We do not monitor what you publish beyond the automated credential scan described in §5, and we are not responsible for its content.

If you use Knowl Cloud for a business or organisation, you indemnify us against third-party claims, regulatory fines and reasonable legal costs arising from your breach of §5 or §6, so far as the law allows. This does not apply where consumer law prevents it, and it does not cover loss caused by our own unlawful conduct.

We may remove content or suspend an account that breaches these terms or the law, and we are not liable for the consequences of doing so. Where it is reasonable and safe, we will tell you first and give you a chance to fix it. Where the breach is serious, urgent or continuing, we may act first and explain afterwards.

7. Acceptable use

Do not resell Knowl Cloud or present it as your own hosted service. Do not work around plan limits, rate limits or workspace boundaries. Do not access a workspace you were not invited to. Do not disrupt or overload the service, use it to attack anyone else, or run intrusive security testing against production without asking us first.

Good-faith security research is welcome. Write to [email protected] before testing anything that could affect other users, availability or data. We will not treat responsible disclosure as abuse because you found something.

8. Plans and payment

Knowl Cloud has a free plan and paid plans. What each one costs and what it includes is on the pricing page. The free plan takes no payment and needs no card.

Paid plans are sold by Polar, who act as our merchant of record. Polar Software, Inc. is the legal seller to you: they take the payment, handle sales tax and VAT in your country, and issue your invoice. Your contract for the purchase itself is with them, under their terms, and we do not hold your card details. We remain responsible for providing the service to you under these terms.

Prices are shown in US dollars and exclude tax. Polar add whatever tax your country requires at checkout, so the amount you pay may be higher than the listed price.

Subscriptions renew automatically for the period you chose — monthly or yearly — until cancelled. Cancelling stops the next renewal and leaves your plan running to the end of the period you already paid for.

How to cancel and when you get your money back is set out in our Refund and Cancellation Policy. In short: cancel at any time, and if you write to us within 14 days of a charge we refund it. That policy is part of these terms.

We say who you are buying from plainly, because it changes who your contract for the purchase is with, and that is not a detail to discover at a checkout.

9. What we commit to

Four promises. Each is already true in the code that runs the service, so none of them is an aspiration.

1. We will never use Customer Content to train a model. As set out in §4, without qualification and on every plan.
2. Export is available on every plan, always. Including the free plan, including while an account is read-only after a failed payment, and including after a workspace is archived. We will never make you pay to get your own knowledge back.
3. Nothing is hard-deleted without a confirmed written request from a billing admin. Not when a payment fails, not when a workspace is archived, and not after any period of inactivity. Knowledge in Knowl is superseded, deprecated or archived — all of which stay readable. This promise is about what the product does on its own; it does not prevent deletion, anonymisation or redaction where a valid privacy right or the law requires it, where content is unlawful, or where it is necessary to protect the service or another person. Where we can satisfy a privacy request by removing a personal attribution while leaving the workspace's technical history intact, we may do that instead.
4. We will give you at least 30 days' notice before discontinuing the service. §11 says how.

There is no uptime guarantee. We do not offer a service level agreement, we do not promise a percentage, and we are not going to pretend otherwise while two people run this. We monitor the service from outside itself and we will tell you when something is wrong.

10. Suspension and termination

You can stop using Knowl Cloud whenever you like. Export your knowledge first — §9 guarantees you can.

If a payment fails, Polar will retry it and email you, and we will email the organisation's billing admins as well. A subscription belongs to an organisation, so each step below applies to every workspace in it. What happens then, in order:

1. For 14 days from the first failed payment, nothing changes. The organisation stays on its paid plan and everything keeps working, because most failed payments are an expired card rather than a decision.
2. After 14 days it becomes read-only. Everything stays readable, searchable and exportable; publishing new knowledge pauses. Local Knowl keeps working throughout — it is only sharing to your workspaces that stops.
3. After a further 30 days it is archived. An archived workspace is still readable and still exportable.

Nothing in that path deletes anything, and paying restores the plan at any point along it. §9 promise 3 is what makes that binding rather than a description of current behaviour.

We may suspend or terminate an account for a serious or repeated breach of §5, §6 or §7, for unlawful use, or where keeping it active creates a real security risk. Unless doing so would be unlawful or unsafe, we will give you a reasonable opportunity to export first.

11. If we discontinue the service

If we decide to shut Knowl Cloud down, we will give you at least 30 days' notice before it stops. We will send that notice by email to every workspace owner, and show it in the application and on this website.

Export will work throughout that period. That is the point of the notice: enough time to get your knowledge out and somewhere else, calmly.

We are two people. We would rather promise thirty days and keep it than promise ninety and discover we cannot fund it after the service has stopped earning. Nothing here requires us to keep operating where doing so has become unlawful, technically impossible, or necessary to stop an active security incident.

12. Changes to these terms

These terms carry a version number and an effective date, both shown at the top. Every previous version stays published at its own address, so you can always read what you agreed to.

For a material change — anything that reduces your rights or adds an obligation — we will publish the new version at least 30 days before it takes effect and email every workspace owner.

If you do not agree with a change, you can stop using Knowl Cloud and export your data before it takes effect. Continuing to use the service after the effective date means you accept the new version, where the law allows acceptance to work that way; where it requires something more, we will ask for that instead.

For corrections and clarifications that change nobody's rights, we will publish and record the change without 30 days' notice.

13. Disclaimers and liability

Knowl Cloud is provided as is and as available. We do not warrant that it will be uninterrupted or error-free, and we do not warrant that a retrieval result is correct. Retrieval is a ranking problem — treat what comes back as context for a person or an agent to judge, not as an authority.

To the fullest extent the law allows, we are not liable for Customer Content you or your team publish, for decisions taken on the basis of it, for indirect or consequential loss, for lost profits or revenue, or for loss caused by your own breach of these terms or failure to secure your account.

Where a contractual cap may lawfully apply, our total liability is the greater of: the amount paid for Knowl Cloud in the twelve months before the claim arose — whether paid to us directly or through a merchant of record — and US$100. The US$100 floor applies while the service is free.

Nothing in these terms excludes or limits liability that cannot lawfully be excluded, including mandatory consumer rights, fraud, fraudulent misrepresentation, wilful misconduct, gross negligence, and death or personal injury caused by negligence. If any limitation here is held unenforceable, the rest still stands.

14. Governing law and disputes

These terms are governed by the laws of Vietnam, and the courts of Vietnam have jurisdiction over disputes arising from them.

If you are a consumer, nothing here takes away a protection or remedy that the law of the country where you live says cannot be taken away by contract. Where a mandatory rule conflicts with these terms, the mandatory rule wins. We say so because in much of the world it is true whatever a contract claims, and a clause that pretends otherwise tells you something about the rest of the document.

A dispute about the purchase itself — the charge, the tax, the invoice — is between you and Polar as the seller, and their own terms and dispute process govern it. A dispute about the service is between you and us, and this section governs it. §9 of the Refund and Cancellation Policy says where to start if you are not sure which one you have.

Before filing a claim, either of us may contact the other and try to sort it out directly. That does not remove anyone's right to go to a court or an authority where the law allows it.

15. General

If part of these terms is held invalid, the rest continues to apply. Not enforcing something once does not waive our right to enforce it later.

These terms, together with the Privacy Policy, the Refund and Cancellation Policy, and any separate agreement that expressly covers your workspace, are the whole agreement for your use of Knowl Cloud. Where a signed agreement conflicts with these terms, the signed agreement wins for what it covers.

16. Contact

Write to [email protected] — for questions about these terms, to exercise a right under our Privacy Policy, to request deletion, or to report a security problem.

Write to [email protected] — for anything about a plan, a charge, a cancellation or a refund.

Both are read by both of us.

These terms govern your use of Knowl Cloud. They are written to be read, so they use plain language rather than legal idiom. Where a sentence is short and blunt, that is deliberate.

1. Who we are

Knowl Cloud is operated jointly by ĐỖ GIANG THÀNH ĐẠT and TRƯƠNG THÀNH LONG, both individuals resident in Vietnam. In these terms "we", "us" and "our" mean both of us together.

We have not yet incorporated a company. If Knowl Cloud is later transferred to a company we form or control, or to another successor that continues the service, we may transfer our rights and obligations under these terms to it so far as the law allows. We will tell you before that happens, and where the law requires your consent we will ask for it. A transfer will not by itself reduce any right these terms give you.

You can reach us at [email protected]. It is a real mailbox and a person reads it.

2. What Knowl Cloud is

Knowl Cloud is a hosted service that stores knowledge your team and your coding agents deliberately publish to it, and makes that knowledge available across the repositories and people in your workspace.

Customer Content means what you deliberately publish: atoms and the categories, reasoning, evidence, repository references and authorship attached to them, along with anything else you choose to include in a published item.

Knowl Cloud is offered for professional and business use. It is a tool for software teams, and it is not designed, priced or marketed for personal, family or household purposes. Where you nonetheless qualify as a consumer under the law that protects you, §14 applies.

Knowl itself — the command-line tool and engine that run on your own machine — is separate software under a separate licence. It is open source under Apache-2.0 and these terms do not govern what happens locally. These terms govern only the hosted service.

Knowl Cloud does not background-sync your repository, code index, embeddings or agent session history. If you deliberately put source code, logs or anything else inside something you publish, that material is part of what you chose to send us.

3. Accounts and eligibility

You need an account, which you create by signing in with Google or GitHub. You must be at least 16 years old to use Knowl Cloud.

Each account belongs to one person. Do not share a login — a shared login is how an audit record stops meaning anything, and the audit record is much of what Knowl Cloud is for.

You are responsible for activity under your account until you tell us it has been compromised. Workspace owners are responsible for who they invite and what permissions those people get.

If you use Knowl Cloud for an employer, client or other organisation, you confirm you have authority to do so and to accept these terms on its behalf.

4. Your content stays yours

As between you and us, you — and the organisation you use Knowl Cloud for — keep all rights in Customer Content. Publishing transfers ownership of nothing.

You give us only the licence needed to run the service: to receive, store, back up, transmit, index, search, scan for credentials, display to your workspace and export your Customer Content. That licence lasts as long as we hold the content and no longer. You confirm you have the rights and authority to grant it.

We will never use Customer Content to train, fine-tune, evaluate or improve any machine learning model. Not ours, not anyone else's. Not on a paid plan and not on a free one. Not after "anonymising" it. This is not a setting you have to find and switch off — there is nothing to switch off, because we do not do it.

We do not routinely read your Customer Content. A person may look at it only where reasonably necessary: because you asked us for support and gave us permission; to investigate a serious security or abuse problem; to comply with a valid legal obligation; or to protect you, another user or the service. Automated processing needed to run the product — credential scanning, indexing, search — is not human review.

5. What you must not publish

Knowl Cloud is for engineering knowledge — what your team learned, decided and verified. It is not a filing cabinet for personal information, and it is not built to be one.

You must not deliberately publish:

• Sensitive personal data, including data about health, biometrics, genetics, race or ethnic origin, political opinions, religious beliefs, trade union membership, sex life or sexual orientation, criminal records, or financial account details.
• Personal data about people outside your own team or workspace, unless you have a lawful basis and every permission needed to process it.
• Credentials. API keys, passwords, tokens, private keys.
• Anything unlawful, anything that infringes someone else's rights, and anything you do not have authority to publish.

Our server scans every publish and refuses content that looks like a credential. That is a safety net, not a promise to catch everything — the rule is yours to keep.

This section is about what you deliberately publish. The ordinary metadata Knowl Cloud generates about your own team — who published something, who changed a role, and when — is service and audit data, and our Privacy Policy describes how we handle it.

6. Your responsibility for what you publish

You warrant that you have the right to publish everything you publish and that it complies with §5.

Where Customer Content contains personal data, the person or organisation who decided to put it there decides why it is processed, and is responsible for that decision. We process it to provide Knowl Cloud on their behalf. Where the law calls that role a processor, that is the role we are in for that content. It is a different role from the one we hold over account, security, audit, device and operational data, where we decide the purposes ourselves — §1 of the Privacy Policy sets out both.

If your use of Knowl Cloud needs a notice, a consent, another lawful basis, or a data processing agreement, putting that in place before you publish is yours to do.

We do not monitor what you publish beyond the automated credential scan described in §5, and we are not responsible for its content.

If you use Knowl Cloud for a business or organisation, you indemnify us against third-party claims, regulatory fines and reasonable legal costs arising from your breach of §5 or §6, so far as the law allows. This does not apply where consumer law prevents it, and it does not cover loss caused by our own unlawful conduct.

We may remove content or suspend an account that breaches these terms or the law, and we are not liable for the consequences of doing so. Where it is reasonable and safe, we will tell you first and give you a chance to fix it. Where the breach is serious, urgent or continuing, we may act first and explain afterwards.

7. Acceptable use

Do not resell Knowl Cloud or present it as your own hosted service. Do not work around plan limits, rate limits or workspace boundaries. Do not access a workspace you were not invited to. Do not disrupt or overload the service, use it to attack anyone else, or run intrusive security testing against production without asking us first.

Good-faith security research is welcome. Write to [email protected] before testing anything that could affect other users, availability or data. We will not treat responsible disclosure as abuse because you found something.

8. Plans and payment

Knowl Cloud is currently free and we do not take payment. There is no charge, no card on file with us, and nothing to cancel.

When we introduce paid plans, we expect to sell them through a merchant of record — a third party who is the legal seller to you, takes the payment, handles tax in your country, and issues your invoice. Price, tax, refunds, chargebacks and cancellation will be governed by that company's terms with you, not by these. We will not hold your full card details, and we will publish a new version of these terms naming them before any of it starts.

We say this now rather than later because it changes who you are buying from, and that is not a detail to discover at a checkout.

9. What we commit to

Four promises. Each is already true in the code that runs the service, so none of them is an aspiration.

1. We will never use Customer Content to train a model. As set out in §4, without qualification and on every plan.
2. Export is available on every plan, always. Including the free plan, including while an account is read-only after a failed payment, and including after a workspace is archived. We will never make you pay to get your own knowledge back.
3. Nothing is hard-deleted without a confirmed written request from a billing admin. Not when a payment fails, not when a workspace is archived, and not after any period of inactivity. Knowledge in Knowl is superseded, deprecated or archived — all of which stay readable. This promise is about what the product does on its own; it does not prevent deletion, anonymisation or redaction where a valid privacy right or the law requires it, where content is unlawful, or where it is necessary to protect the service or another person. Where we can satisfy a privacy request by removing a personal attribution while leaving the workspace's technical history intact, we may do that instead.
4. We will give you at least 30 days' notice before discontinuing the service. §11 says how.

There is no uptime guarantee. We do not offer a service level agreement, we do not promise a percentage, and we are not going to pretend otherwise while two people run this. We monitor the service from outside itself and we will tell you when something is wrong.

10. Suspension and termination

You can stop using Knowl Cloud whenever you like. Export your knowledge first — §9 guarantees you can.

When paid plans exist and a payment fails, our intended path is read-only and then archive, not deletion. The exact steps will be set out in the version of these terms in force when paid plans launch.

We may suspend or terminate an account for a serious or repeated breach of §5, §6 or §7, for unlawful use, or where keeping it active creates a real security risk. Unless doing so would be unlawful or unsafe, we will give you a reasonable opportunity to export first.

11. If we discontinue the service

If we decide to shut Knowl Cloud down, we will give you at least 30 days' notice before it stops. We will send that notice by email to every workspace owner, and show it in the application and on this website.

Export will work throughout that period. That is the point of the notice: enough time to get your knowledge out and somewhere else, calmly.

We are two people. We would rather promise thirty days and keep it than promise ninety and discover we cannot fund it after the service has stopped earning. Nothing here requires us to keep operating where doing so has become unlawful, technically impossible, or necessary to stop an active security incident.

12. Changes to these terms

These terms carry a version number and an effective date, both shown at the top. Every previous version stays published at its own address, so you can always read what you agreed to.

For a material change — anything that reduces your rights or adds an obligation — we will publish the new version at least 30 days before it takes effect and email every workspace owner.

If you do not agree with a change, you can stop using Knowl Cloud and export your data before it takes effect. Continuing to use the service after the effective date means you accept the new version, where the law allows acceptance to work that way; where it requires something more, we will ask for that instead.

For corrections and clarifications that change nobody's rights, we will publish and record the change without 30 days' notice.

13. Disclaimers and liability

Knowl Cloud is provided as is and as available. We do not warrant that it will be uninterrupted or error-free, and we do not warrant that a retrieval result is correct. Retrieval is a ranking problem — treat what comes back as context for a person or an agent to judge, not as an authority.

To the fullest extent the law allows, we are not liable for Customer Content you or your team publish, for decisions taken on the basis of it, for indirect or consequential loss, for lost profits or revenue, or for loss caused by your own breach of these terms or failure to secure your account.

Where a contractual cap may lawfully apply, our total liability is the greater of: the amount paid for Knowl Cloud in the twelve months before the claim arose — whether paid to us directly or through a merchant of record — and US$100. The US$100 floor applies while the service is free.

Nothing in these terms excludes or limits liability that cannot lawfully be excluded, including mandatory consumer rights, fraud, fraudulent misrepresentation, wilful misconduct, gross negligence, and death or personal injury caused by negligence. If any limitation here is held unenforceable, the rest still stands.

14. Governing law and disputes

These terms are governed by the laws of Vietnam, and the courts of Vietnam have jurisdiction over disputes arising from them.

If you are a consumer, nothing here takes away a protection or remedy that the law of the country where you live says cannot be taken away by contract. Where a mandatory rule conflicts with these terms, the mandatory rule wins. We say so because in much of the world it is true whatever a contract claims, and a clause that pretends otherwise tells you something about the rest of the document.

Before filing a claim, either of us may contact the other and try to sort it out directly. That does not remove anyone's right to go to a court or an authority where the law allows it.

15. General

If part of these terms is held invalid, the rest continues to apply. Not enforcing something once does not waive our right to enforce it later.

These terms, together with the Privacy Policy and any separate agreement that expressly covers your workspace, are the whole agreement for your use of Knowl Cloud. Where a signed agreement conflicts with these terms, the signed agreement wins for what it covers.

16. Contact

Write to [email protected] — for questions about these terms, to exercise a right under our Privacy Policy, to request deletion, or to report a security problem.

One address, read by both of us.