Published in English and in Korean, each a full version of the same obligations. If you are a consumer habitually resident in Korea, the Korean version governs; otherwise English is canonical. Where a term is unclear the reading more favourable to you prevails, and mandatory consumer law where you live prevails over both.
1. Who these terms are between, and how you accept them
1.1 We are the individual who operates NMTS under the name needmoretruth — one person, not a company, also shown as NeedMoreTruth Storage. NMTS names this product and its file format; the service is the website and application at nmts.me. You are the person using it, and the NMTS key holds the account.
1.2 These terms and the Privacy Policy are put in front of you in full, in both languages, with their version and date, on the screen where you accept them. You accept by creating an account, or by accepting a new version on that screen, and we record which version you accepted. When you take a one-time pass for an AI agent on nmts.me/ai, you accept there, and that acceptance is recorded for the account the agent makes with the pass; a business connecting an NMTS Platform key under 3.7 names in its request the versions it accepts, and we refuse the request unless they are the current ones. The board has its own terms, accepted separately when you open a board profile. If you are a consumer in the European Union, the European Economic Area or the United Kingdom, you may withdraw from this agreement within 14 days of accepting it, without giving a reason, by deleting your account or writing to nmts@nmts.me; nothing is paid to us, so nothing is refunded.
2. What the service is, and what it is not
2.1 NMTS is a published file format, software that runs in your browser, and a coordination server. Your files are encrypted on your device before any part of them leaves it, and we hold no key to them, so we cannot read a file's contents or its name. The engine's source and the format are published at github.com/needmoretruth/nmts-crypto; the limit of that is that we also write the software your browser runs.
2.2 We are not the storage. On NMTS Standard your encrypted bytes sit on the Walrus network's nodes, which neither we nor you choose, and your storage terms are recorded on the Sui blockchain. On NMTS Heavy each part sits whole with Filecoin storage providers chosen from the network's public registry — two, run by different operators, unless you choose otherwise in the command-line tool — and the storage is recorded on the Filecoin blockchain. We own, run and control none of these and have no contract with any provider. When a storage term ends the data is deleted — by the Walrus network, or on Filecoin by each provider, when it chooses, after a removal request — and neither of us can recover it afterwards.
2.3 We do not hold your money: except on the credit route in section 4, a payment for storage goes from your own wallet to the network, we take no share, and we cannot start, stop or reverse one. Nothing here is for sale — we charge you nothing, and the only money reaching us is a voluntary gift under section 6.
2.4 The version number is below 1.0 and parts of the product are still being built; the product says so where such a feature would be. Do not use the service where a failure would cause serious harm, or as the only copy of anything.
3. Your account and your NMTS key
FACT NOTICE
If you lose your NMTS key, your account and everything in it become unreadable, and this cannot be undone. The wallets come from the same key, so any coins at their addresses are lost too. We hold no copy of the key, and there is no reset path.
3.1 Your NMTS key is a 160-bit secret made in your browser, and every key the account uses comes from it, including the wallets' private keys. Whoever has the key has the account: if someone else obtains it they can read your files and spend from the wallets, and all we can do is sign your other devices out. Changing the key is not a rotation — a new key is a new account.
3.2 Creating an account in the browser has one step you cannot skip: you type the key back in, or you save the recovery file that holds it. An account an AI agent makes with a one-time pass has no such step: the command-line tool keeps the key in its credentials file on that machine. The sign-up screens also explain what the recovery list is — an encrypted index of your files, not a copy of your key. The independent recovery tool at github.com/needmoretruth/nmts-recovery opens your files without us, from your key and a recovery list you saved.
3.3 To create an account you must be at least 14, and old enough where you live to make an agreement like this on your own. We do not ask your name, email address or date of birth, so we cannot check your age.
3.4 To let a program act for you, use an API key rather than your key. It carries only the permissions you pick, always expires, cannot open your files, and is listed and revoked with your NMTS key alone — never with another key.
3.5 You may make AI accounts under your account: up to three, each of which may make up to three of its own, twelve in all; across all of them, nine creations and nine deletions a day. Each is a full account — "AI" is only its name, and you may use one yourself — whose key your browser derives from the key of the account above it and never sends us, so your own NMTS key alone recovers every one of them; what we keep is which account made it, its place among the three, and when. Turning this on the first time asks for a human check and a short computation by your browser. A stop on an AI account for a breach locks the account that made it out of making more, and a second stop stops that account too. You list and delete them from the account that made them. An AI account is for you alone. Making one and handing it to another person, or letting several people use it under your account, is not allowed: AI accounts were not developed for shared use or for handing over, and that use can create risks for you and for others. Your account and the AI accounts under it are counted together for the trial, the human check and the daily limits.
3.6 You can delete your account from inside the product at any time, and the Privacy Policy says what that deletes and what outlives it. There is no condition attached.
3.7 A business may connect an NMTS Platform key to its account by giving us the key's public half. It may then open accounts for the people who use its own product, up to a daily limit we set, and sign for each such account which requests we accept from it, with which permissions and until when — the kinds of permission an API key carries, and one more that opens the account in the first place. These terms apply to the business for the NMTS Platform key it connects and for every account it opens: toward us, the business is the holder of those accounts. A person who reaches NMTS through a business's product has their agreement with that business, not with us. The business answers to us for what it does under its signature and for what its product does in those accounts, and to those people under its own terms. Section 8 is owed to us by the business for those accounts, and the business carries the same rules into its own terms with its users. Before it opens an account for a person, the business shows that person our Privacy Policy and obtains their consent to the transfers abroad listed in its section 5 — including, if the business is established outside the Republic of Korea, the business reading that account's records from there. The business confirms that its product is not directed to children within the meaning of 16 C.F.R. §312.2 and that it opens no account for anyone below the age in 3.3, and tells us at once if either changes. Whether the business or the person holds an account's NMTS key is the business's design. Whoever holds the key can sign in with it at nmts.me — accepting these terms then, as anyone does — delete the account (3.6) and take its files (8.4). If the business holds the key, the business can read those files, we still cannot, and the business does those things for the person when the person asks. What 8.3 and 8.4 have us tell an account holder is told to whoever signs in to the account; where that is the business, it passes it on to the person. A business replaces its NMTS Platform key with a request signed by both the old key and the new, and the old key's signatures stop counting at once.
4. Credits are a free gift, never sold
4.1 Credits are a free gift, lent to you without charge. They are never sold, are not a coin and not on any blockchain, give you no ownership and have no money value, and buy nothing except storage we buy for your file. You may move them between your account and the AI accounts under it, and nowhere else. One credit is one megabyte for 28 days, counted on the size actually stored; NMTS Heavy costs half as many, rounded up. Because credits have no money value, a mistake in how they are counted or priced — a wrong price, a balance that shows the wrong figure, a charge counted more than once — is corrected in credits, not compensated in money. Please report one when you see it.
4.2 While we run the free-trial programme we may offer a limited number of trial credits each week, some weeks none, first-come first-served, at most once per ISO week for you and the AI accounts under your account together. We may change or end the programme. Credits in your balance are taken back only for a reason we state to you: you obtained them by breaking section 8 or by working around the weekly limit, they were issued in error, or a binding legal requirement demands it. Unused credits expire on the date shown when they arrive.
4.3 On this route the term is fixed at 28 days and cannot be extended, and we refuse an upload that would go over the credits one file, or one account in a day, may use. A credit-paid upload to NMTS Standard also holds a deposit you choose when you upload, up to 64 credits — 64 unless you set another figure: those credits leave the balance you can spend, come back when the storage term ends, and pay for the work if you ask us to release that storage early. If the bundle they were held against expires first, they go with it; if the upload does not complete, they come back. If you chose no deposit, that release work is paid from your balance at twice the fee, and when the balance is short we cannot release the storage early.
4.4 Storage bought with credits is paid for and registered by us, so we can destroy it before its term ends — when you ask, when a report under section 8 is made out, or when a binding legal requirement demands it — and you cannot release or extend it yourself.
5. Paying the storage network from your own wallet
5.1 The product includes a wallet derived from your NMTS key, whose private key is made and used inside your browser and which you can export at any time; the command-line tool derives a Filecoin wallet from the same key. Those addresses hold real coins. You can also connect a wallet of your own.
5.2 Storage on Walrus is prepaid for a fixed term you choose, and storage on Filecoin from the command-line tool is paid out of a deposit you fund, for as long as it lasts, in transactions you sign yourself; the payment goes to the storage network and we are not a party to it. Extending a Walrus term is a new payment you sign. Storage payments cannot be reversed or refunded by us, by you or by the network.
5.3 Expiry dates are not exact, because the storage network sets the length of its own units of time; the product says where a date is a floor and marks a single date as an estimate.
5.4 Value leaves your wallet without a confirmation for each transaction only under an auto-approval or under a standing share you set. The storage-only auto-approval is on unless you turn it off; you approve the total of a spending session before it starts and its first payment yourself, and it signs only within that total. An everything auto-approval, which can also move funds out, signs only if you turn it on. The standing share is 0 until you set it (6.2). Every transaction costs gas, and once one is signed and confirmed neither we nor anyone else can reverse it.
6. Gifts, the standing share and the hall of fame
6.1 A gift to the developer, which the product's screens call a donation, buys nothing — no storage, no credits, no features, no priority — is not refundable and cannot be undone. In Korean law it is a 증여 (Civil Act art. 554). Anyone who gives nothing gets the same service.
6.2 Three ways to give lead to the same published address: the donation card, in SUI or WAL; a standing share of each WAL payment for storage, sent straight after that payment; and the command-line tool. The standing share is 0 until you set it. You agree to it once, choose it on a dial up to 10 % or type a higher share up to the whole amount with one more confirmation, and can set it back at any time. A transfer to a wrong address is lost and we cannot recover it.
6.3 The hall of fame is a public page listing the developer first and then the hundred largest senders by cumulative amount, each under a shortened sending address — what the public ledger already shows. If you have given, you can ask to be listed under a display name instead by signing a short message with the sending wallet, and change or remove it the same way. The listing is a courtesy, not consideration, and links no wallet to an NMTS account.
6.4 Where a law you cannot contract out of gives you a claim about a gift, we act on it: we hold the ledger of transfers to that address and will look it up, and we may ask you to sign from the sending address to show the gift was yours.
7. Deleting, and what we can and cannot remove
7.1 Deleting a file destroys the key we hold, not the stored bytes. The file moves to the trash, and after 30 days there — or at once, if you say so — the file record and the wrapped key we hold are deleted, after which the encrypted bytes cannot be turned back into your file. The bytes stay on the storage network until the term runs out, except that for a file on NMTS Heavy paid with credits the deletion also sends a removal request (2.2).
7.2 Removing the data from the storage network is a transaction you sign yourself, and works only for storage registered to your own wallet; for credit-bought storage you ask us on the file's screen, or on NMTS Heavy delete the file, and we destroy the object or send the removal request (4.4).
7.3 A recipient whose device unwrapped a shared key can open the bytes until the term ends, whether or not either side undoes the share, and a backup taken before a deletion can still hold the wrapped key, which still needs your key.
7.4 If a storage object we bought with our own funds for a credit-paid file of yours on NMTS Standard goes missing, a daily check shows you the finding on your own drive and we post it without naming you. We cannot bring it back, and the credits spent on that file are not returned.
7.5 A public link you make to a file lets anyone who holds it download and open that file without an account, until you or we cut it, it reaches the expiry you chose, or the file goes to the trash. The key that opens the file is in the part of the link a browser does not send to us. Cutting a link stops new downloads through NMTS; copies already downloaded stay with whoever has them.
8. What you may not do, and what we may do about it
8.1 Do not use the service to store, share or distribute material that sexually exploits children, material infringing another's rights, or anything whose storage or distribution is a crime where you are. Do not attack the service: no breaking into other people's accounts, no automated flooding, and no bypassing the human check or the rate limits.
8.2 We cannot see what you store unless someone gives us a file's public link (7.5) or a key that opens it, because whoever holds either can open that file. So we do not scan and cannot detect prohibited content, and we act only on reports. Write to nmts@nmts.me, which is also the designated recipient (수령인) for copyright takedown and restoration demands under 저작권법 제103조, saying what you complain about precisely enough to identify it, on what basis, and how to reach you. Anyone can also report a public link from its page, without an account.
8.3 A person reads every report we can identify and decides on it. A report that a public link holds child sexual abuse material or non-consensual intimate images cuts that link at once, before anyone reads the report and without anyone opening the file. Our measures are to cut a public link, to remove the records that let a file be reached through NMTS, to release the storage object where credits paid for it, and to stop serving the account. We tell both sides, where we have a way to reach them, what we did or declined to do, its scope, the facts and the ground we relied on, and how to challenge it: reply to us, go to a court where you live, or use an out-of-court body where there is one. Removing the records, or cutting a link, is reversed if you make out a restoration demand under 저작권법 제103조 제3항, unless the claimant tells us before the restoration date that they have sued.
8.4 If we stop serving your account, we record which of five grounds it was on: a copyright complaint we upheld; a report of unlawful material we upheld; a serious or repeated breach of these terms; a legal order binding on us; or your own request. A stop stays with the NMTS key. The files in a stopped account are still yours to take with your key and recovery list, and deleting the account is still something you do, not something we do to you.
8.5 If an authority orders us to act, we can hand over only what we hold, which the Privacy Policy lists; we cannot produce your files' contents or their names. We check that a demand binds us, and we tell the affected person unless we are forbidden to.
9. Our responsibility to you
9.1 Nothing here excludes or limits any liability that the law where you live does not allow to be excluded or limited, and that law prevails over anything in this document.
9.2 We are responsible to you for harm we cause intentionally or by gross negligence, for death or personal injury caused by our negligence, and for other harm our negligence causes you. We set no monetary cap on what we owe. If we take credits from you in error, we put them back.
9.3 Subject to 9.1 and 9.2, and except where the harm was caused or contributed to by our own breach of these terms or of the law, we are not responsible for:
- loss of access caused by losing your NMTS key;
- the storage network deleting data when a term ends or after a removal request;
- what the storage networks' nodes and providers do, since we do not run them;
- what is written on the public blockchain;
- what someone does with a file you shared;
- transactions correctly executed within a total you approved under the storage-only auto-approval, under an everything auto-approval you turned on, or under a standing share you set, which does not cover our own error in computing or addressing that total or that share.
9.4 If a court finds any part of these terms invalid, the rest continues to apply unless the law where you live says it cannot stand without that part.
10. Changes to these terms and to the service
10.1 Each version has a string in the form YYYY-MM-DD-vN and a date, both shown at the top of this document and in the product. We never edit a published version, and we send any of them on request.
10.2 A new version is posted on the notice board with its date, and applies to you from the moment you accept it on the acceptance screen. Until you accept it, the version you last accepted remains the agreement. Continuing to use the service is not, by itself, how you accept it: until your acceptance is recorded the service refuses only the requests that hand us or take on something new — uploading a file, creating a share or a public link, publishing your sharing identity, making an API key, moving credits between your own accounts, writing on the board — and everything else keeps working, including reading your drive, downloading files and deleting your account. Requests a business signs for an account it opened (3.7) do not pass this gate, because the business's acceptance covers the accounts it opens; connecting an NMTS Platform key requires the current version (1.2).
10.3 Changes do not apply backwards: a dispute already arisen, and storage already paid for, stay under the version then in force.
10.4 We change the service to fix faults and security problems, to follow the storage network's formats, rules or prices, to comply with a law, or to improve it; where a change removes something you can do, the notice board carries it as a dated entry, which is how it reaches you since we hold no address for you.
11. Governing law and disputes
11.1 If you are a consumer, we impose no choice of law or court on you. In the European Union, the United Kingdom and Korea that means the law where you normally live governs this agreement — all of it, not only its mandatory rules — and you can claim in your own courts. Elsewhere your own country's rules decide, and we will not argue that this agreement sent it elsewhere.
11.2 If you are not a consumer — if you use the service for a trade, business or profession — this agreement is governed by the law of the Republic of Korea.
11.3 There is no arbitration clause here and no waiver of your right to take part in a class or group action. Nothing here stops a small-claims case or a complaint to a regulator or consumer body where you live; in Korea you can also apply to the 콘텐츠분쟁조정위원회 or the 한국소비자원.
12. Contact and language
12.1 nmts@nmts.me is our single point of contact, for you and for authorities, read by a person in English or Korean; the support inbox in the product and nmts support in the command-line tool reach the same person. It is also the designated recipient named in 8.2 and the contact for privacy matters.
12.2 These terms exist in English and in Korean, each a full version of the same obligations and equally binding. If you are a consumer habitually resident in Korea, the Korean version governs, otherwise English is canonical; where there is doubt about what a term means and you are a consumer, the reading more favourable to you prevails, and mandatory law where you live prevails over both versions.