Typewell

Terms & Conditions

Last updated 5 August 2026

Typewell is free, open source and provided as is. Your notes are yours — we neither hold them nor claim any rights over them. In exchange, there is no warranty and no guarantee the site stays online, so keep your own backups of anything you would hate to lose.

1. Agreement

By using Typewell at typewell.net, or any copy of it you host yourself, you agree to these terms. If you do not agree with them, please do not use it. Typewell is free of charge, so the simplest remedy for any dissatisfaction is always to stop using it.

2. What Typewell is

Typewell is a notes application that runs entirely in your browser as a single static HTML file. There is no account, no subscription and no server holding your work. The software is released under the MIT licence, which permits you to use, copy, modify and redistribute it, including commercially, subject to that licence's terms. Where the MIT licence and these terms differ regarding the software itself, the MIT licence governs.

3. Your notes are yours

You retain all rights to everything you write. The maintainers claim no ownership, licence or interest in your content, and have no technical means of accessing it: notes are held in your own browser, and any backup goes to a Google Drive or GitHub account belonging to you.

You are solely responsible for what you write and for keeping your own copies of it.

4. No warranty

Typewell is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. The maintainers do not warrant that the app will be available, uninterrupted, error-free, or that it will preserve your data.

Please take this one literally. Notes live in browser storage, which a browser may clear without warning — when you clear site data, in private-browsing sessions, or under storage pressure. Turn on a backup, or export your notes regularly. Data lost this way cannot be recovered by anyone, including us.

5. Acceptable use

Typewell runs on your own device, so there is little for us to police, but you agree not to use it to break the law, to infringe anyone's rights, or to attack, overload or interfere with the services it connects to. You are responsible for complying with the terms of any third-party service you connect, including Google and GitHub.

6. Third-party services

The optional Google Drive and GitHub Gist backups are provided by those companies, not by us. Their terms and privacy policies apply to your use of them, we have no control over them, and we are not responsible for their availability, behaviour or handling of your data. The Privacy Policy sets out exactly which third parties are contacted and when.

7. Limitation of liability

To the fullest extent permitted by law, the maintainers and contributors shall not be liable for any claim, damages or other liability — whether in contract, tort or otherwise — arising from or in connection with Typewell or its use, including any loss of data, loss of profits, or business interruption, even if advised of the possibility of such damage.

Some jurisdictions do not allow certain exclusions of warranty or liability. Where that is the case, the exclusions above apply only to the extent permitted, and nothing in these terms limits liability that cannot lawfully be limited.

8. Availability and changes

Typewell is maintained by volunteers on a best-effort basis. We may change, suspend or discontinue the hosted site at any time, without notice or liability. Because the software is MIT licensed and is a single file, you can always keep a copy: download index.html and it will keep working offline from your own disk, independently of this site.

9. Changes to these terms

These terms may be revised. The date at the top will change with them, and every revision is recorded in the project's public commit history. Continuing to use Typewell after a change means you accept the revised terms.

10. Contact

Questions about these terms are best raised as an issue on the project's issue tracker.