Terms

Signing in means accepting what is on this page. If you would rather not, don’t sign in.

“The operator” below means the person running this particular deploy.

A private library of the commands, prompts, paths and URLs you look up over and over. It is built for one person at a time: your library is yours, nobody else is in it, and there is nothing to administer.

Nothing is charged for it today. That is a fact about now rather than a promise about later — this is a small product run by one operator, and it may become paid. If it does, you will be told before it happens rather than after, and an account that does not want to pay keeps what the rest of this page gives it: Export, self-serve and immediate, and the option of simply stopping. Nothing you file is held hostage to a decision made after you filed it.

There is no payment detail on file because there is nowhere on this deploy to put one, and nothing in this document asks you for money.

You sign in through an identity provider — with Google, or with an address and a password you set there. The account is yours, and it is created the first time you sign in with an address the provider has verified. The operator can suspend an account, or remove it on request; being able to authenticate is not by itself a promise of continued access.

Keep the account to yourself: anything done with it is treated as done by you. If somebody else wants a library, they can make their own account rather than borrowing yours.

Your commands, notes, prompts and paths are yours. The operator claims no ownership of them and takes no licence beyond what running the thing requires: storing them, indexing them so search works, and showing them back to you.

They are not used to train anything, not analysed for any purpose of the operator’s, and not shown to anybody else. That does not change if the deploy ever starts charging — what you file is not part of what would be sold. What is stored and who can see it is set out in the Privacy policy.

This is the clause that matters, so it is not buried at the bottom.

BashNotes stores text and copies it to your clipboard. It never runs anything, and it does not check that what it hands you is safe to run. A command that was correct when it was filed may be wrong for the machine you are sitting at, wrong for the environment you have picked, or simply out of date.

It does mark commands it recognises as destructive, and it asks before copying one that is aimed at production. That marking comes from a hand-written list of commands, which means it will miss things — the absence of a warning is not a statement that a command is safe.

• Don’t store credentials — see the standing rule in the Privacy policy. Store the pointer to the secret, not the secret.
• Don’t put anything here you are not entitled to hold, including other people’s confidential material.
• Don’t try to reach anybody else’s library, work around the sign-in, or probe the deploy for weaknesses without asking the operator first. Ask, and the answer will probably be yes.
• Don’t use it to break the law or to store anything unlawful.
• Don’t hammer it. Sign-in attempts, new accounts and the size of what one account can store are all limited, and the limits are sized for people rather than scripts — hitting one is a sign to stop, not a puzzle to solve.

It may be slow. It may be down. It may be moved, rebuilt or switched off, with notice if that is possible and without if it is not. There is no service level here and no support commitment: this is one person running a small application.

Which is exactly why Export is self-serve and immediate. It lives on the Account settings page, which is in the nav on every screen, and it hands the whole library straight back — no request, no approval, nothing to wait for. Take your own copy: nobody has to agree to it, and it is the backup that does not depend on this deploy still existing.

BashNotes is provided as-is and as-available, without warranty of any kind — no promise that it is fit for your purpose, that it will keep working, or that what it stores is correct.

To the fullest extent the law allows, the operator is not liable for any loss or damage arising from your use of it — including lost or corrupted data, and including anything destroyed by a command you copied from it.

Nothing in this document excludes any liability that cannot lawfully be excluded.

You can stop using it whenever you like, and you can delete the account outright from the Account settings page — immediately, without asking anybody, and permanently. Export first: an export you did not take is not a backup you have, and after the deletion there is nothing left to take one from.

The operator can withdraw your access at any time. Withdrawing it takes effect on your very next request rather than when your cookie happens to expire. That ends your access; it does not by itself delete what you filed, which is the separate act above and is covered in the Privacy policy.

The date at the top says when this last changed, and the full history is in the project’s git log. Carrying on using the deploy after a change means accepting the changed version; if you would rather not, export and stop.

One change is deliberately outside that. Starting to charge is not something you agree to by carrying on. It needs telling you in advance and a decision from you — silence is not consent to a bill, and an account that makes no decision keeps its data and its Export rather than losing either.

Every clause left out was left out on purpose, and it is more useful to say so than to let the gaps look like oversights.

• No price, no billing terms, no refund position. Because nothing is charged for. Writing them now would mean inventing a plan nobody is on, and a term about money that does not move any is the kind of clause a reader learns to skip.
• No governing law and no chosen court. Nothing is charged for, there is no company and there is no money in dispute, so naming a jurisdiction would be ceremony rather than a decision.
• No arbitration clause, no class-action waiver. Same reason.
• No service level and no support hours. Promising either would be a lie, and a term nobody intends to keep devalues the ones above it. This one does not change if the deploy starts charging — it is one operator either way, and paying for something does not conjure a second person to answer the phone.

The first three are a set, and they come back together or not at all: the day anything here is billed, they have to be written before the first payment rather than after it. Naming them is the point of this section — a gap you have been told about is a scheduled piece of work, and one you have not is something discovered by whoever is owed money.