summary

buying a product from ashen one buys a licence: the right to use it, on one machine, for as long as you like.

• one purchase, one machine. the licence does not expire.
• every future version of that product is included. there is no upgrade fee.
• where a product has a free edition, it does not run out: it is smaller, not shorter.
• used honestly, none of the terms below come up.

scope

these are the terms every piece of software from ashen one is sold under. they are the same for each of them, and they are written to stay the same for the ones after.

a licence covers the product it was bought for. a second product is a second purchase: nothing here is a bundle, and nothing here is a subscription to everything.

what you bought under, you keep. terms may be reworded for products that come later; they do not reach back and change a licence already sold.

the licence

what you buy is permission to use the software. the file it arrives in is just the file; the licence is the part that is yours.

1. machines   a licence runs on one computer at a time.
2. transfer   expected, and it costs nothing. take the licence off the old machine and it is free to go on the new one. a machine dying, being rebuilt or being replaced is not a reason to buy the software twice.
3. users   the licence is yours. two editors working at once are two licences, whether that is two rooms in a facility or two seats at one desk.
4. term   it does not lapse, and it is not a subscription. a version that works today will still work in ten years on a machine that has not changed.
5. commercial use   included, with nothing to declare. what you cut is yours; the software makes no claim on the sequence, the export or the money.

updates

every version of a product you own is included in the price you paid, for as long as there is a version. there is no upgrade fee, no major-version wall and no maintenance year that runs out.

a new build is the same kind of file as the one you installed, and your licence does not change when the version does.

settings survive an update. what you have set is stored on your machine, and a new build finds it where the last one left it.

the free edition

where a product has one, it is free on any machine, with no purchase and no account, and it does not stop working. it is not a trial period: it is the product with less of it. what it leaves out is a matter of size, and what it carries is finished, not cut down.

it is updated too, as far as it can be: a fix reaches it when it touches something it actually has, and work on the parts it does not carry has nothing to land on.

it is there for finding out whether the software suits you, and for staying, if the smaller edition is genuinely all you need. it is free either way.

host support

a product that lives inside somebody else's application depends on what that application offers. each product names the hosts and the releases it runs in, and it will be kept working in current ones for as long as the platform it is built on exists.

a new host release is followed by a build that runs on it.

the platform is not mine and its future is not mine to promise. if it goes, the last build to run stays yours and keeps working on the release it was made for: a licence is not withdrawn because a host moved on.

this is the one thing on the page you are asked to take as a statement of intent rather than a term: the work will be done for as long as it can be done.

limits

use it honestly. that covers it, and what follows is only the same sentence with names on the parts of it people ask about.

1. the file   do not pass the software or your licence key on: not shared, not posted, not resold. one purchase is one seat, and a key in circulation stops being one.
2. the code   do not take it apart to rebuild it, defeat the licensing, or ship any part of it inside something else.

what you bought stays yours. the licence can only be withdrawn for a breach of the two above.

the sale

the licence is set here; the transaction is not. how the money is taken, and on what terms it can be given back, belongs to whoever processes it.

1. refunds   —

if something is wrong with the key, the install, or a build that will not load, write to me first. it is one person here.

warranty

the software is provided as it is. no software is promised to be free of faults, and this is not either.

if it fails, what can be owed to you is what you paid for it, and nothing beyond that: not a missed delivery, not lost work, not the job. anything it gets wrong is worth reporting and will be fixed if it can be.