English is the canonical text; the Korean version is a full version of the same content. If you are a consumer habitually resident in Korea, the Korean version governs for you.
1. Who is responsible, and how to reach us
1.1 NMTS is operated by one individual under the name needmoretruth, who is the controller of the personal data described here and, being one person, is also the person in charge of personal data protection (개인정보 보호책임자).
1.2 Contact: nmts@nmts.me, or the support inbox in the product. There is no phone line and no postal counter.
2. What we hold, why, for how long, and on what basis
2.1 We do not ask for and do not hold your name, email address, phone number, age, date of birth, postal address or payment details. You need give us nothing outside this table; without an NMTS key there is no account. These categories are all of them.
| Items | Purpose | Period | Basis |
|---|---|---|---|
| Account: an id derived from your NMTS key, sign-in credentials, your public codes with the day each was made and the day you revoked one, a pointer to your encrypted recovery list, the dates it was made and last seen, the document versions you accepted, and, for an AI account, which of your accounts made it and when | Running your account | While the account exists | Agreement |
| Files: per file its stored size, its times, its encrypted key, where it lives on the storage network and, if you paid from your own wallet, that wallet's address; an encrypted list of all your file names and folders; per share the two accounts, the public code each used and the time | Storing, listing, sharing and checking your files | While the file exists; a deleted file 30 days in the trash; a share until either side undoes it | Agreement |
| Public links: per link a random token, the file it opens, the account that made it, values your browser encrypted that we cannot open, whether it shows the file's name, when it was made, when it expires, when it was cut and whether by you, by us or by a report, and a count of the times it was opened, with no time and no reader | Letting anyone who holds the link open the file, and letting you or us cut it | Until the file's record or the account is deleted; a link is cut when its file goes to the trash | Agreement |
| Sessions and program keys: token hashes with their times, an encrypted device label, and per key a handle, a hash of its secret half, its permissions and its use counts | Keeping you signed in and letting a program act for you | A session until you sign out or until it goes unused for the length you chose — 1 hour to 30 days, and 30 days for “until you sign out”; a session of 1 hour to 30 days also ends 30 days after sign-in, even if in use; a key up to 90 days as you chose, and 30 days more once revoked | Agreement |
| Abuse counters: failures at a door that takes a secret, and refused free-trial applications with their week | Keeping automated abuse out | 30 days; refusals 8 ISO weeks | Legitimate interests |
| Credits: grants with their source, week and expiry, the ledger of what each bought, and per credit-paid upload the file, the public storage identifiers, our transaction, the size and the term | Running the free trial and buying storage for your file | While the account exists | Agreement |
| Storage loss: your account identifier, the object the chain no longer knows, and the day we first missed it | Telling you your file is lost | 12 months from that day | Legal obligation |
| Gifts: per transfer to our published gift address, read from the public Sui ledger, the transaction id, sending wallet address, coin, amount and time; and a display name you sign for | Showing the gifts are real, and listing you by name | While the hall of fame is published; a name until you remove it | Legitimate interests; consent for the name |
| Support: your message in readable form with its category, reference code, public code and times; whatever you ticked to attach, which can include file names, paths and sizes; and a command-line run log, redacted on your own machine; a report you make about a shared file or a public link, with the reason you picked, what you wrote and a contact if you give one | Answering you, and acting on reports | 30 days — 120 days for a question about the board or a request for your data or its removal, and 12 months for a question about a storage loss — or at once if you withdraw it; email to nmts@nmts.me 12 months after our last reply | Agreement |
| Board: your nickname and its history, your switches, your posts in readable form, reports with the quoted excerpt and the reporter's explanation and contact details, your notice box, and a bar left by a closed profile | Running the board and keeping its measures effective | While the account exists; a notice or decided report 12 months; an under-14 bar 5 years | Agreement; legitimate interests; consent for the switches |
| Registration: the account identifier being registered from the command-line tool, and a challenge tag with its times; for a one-time pass for an AI agent, a digest of the pass, when it was issued, expires and was used, the document versions accepted with it, and the account it made | Finishing that registration | Until it completes or expires | Agreement |
| Sign-up survey: your answers about how you heard of NMTS, what describes you and what you will keep, with any free text you typed, and the day, stored without an account identifier, a session or an address | Our own interest, and statistics about who arrives and how | Kept as statistics without identifiers | Consent — you may skip it, and skipping changes nothing |
| NMTS Platform: for an account with an NMTS Platform key connected, its public signing key, the name it chose, its status, and the dates it connected and last changed the key; for an account opened through a business, which business opened it and when; per business, how many accounts it opened each day; and for each request a business signs, the time it was signed and a hash of the signature | Letting the business open accounts, checking its signatures and keeping its daily limit | While the account exists; the daily count 30 days, cleared by the next account the business opens after that; the signature hash 10 minutes, cleared by the next signed request after that | Agreement with the business; for a person whose account a business opened, legitimate interests (2.5) |
| Measures and totals: a stop with its ground and day; a one-way fingerprint of each public code its owner revoked; what an operator did through the administrative routes, never an inquiry's text, an NMTS key or any other key; and service-wide totals with no per-account figure | Keeping a measure in force, retracing what we did, publishing use | A stop until we lift it; a revoked code's fingerprint for good; the rest while the service runs | Legitimate interests |
2.2 What we cannot see. The keys that open your files come from your NMTS key, which we do not hold, so we cannot read a file's contents or its name. The exceptions are ones you make yourself: names, paths and sizes you attach to a support message arrive readable, and a file's public link lets whoever holds it open that file, including us if the link reaches us. The limit of that is that we also write the software that encrypts, and your browser runs the version we serve. Please keep health, beliefs, politics and sex life out of a support message: it is the one box we can read, and we hold no separate consent for such data.
2.3 Your IP address is not stored in a form that can be turned back into an address. It exists on our server only while a request is handled; what is stored for rate limits and the counters above is a keyed hash under a key that lives only in memory, is remade at 00:00 UTC daily and is never written to disk.
2.4 The bases. Agreement is GDPR Art. 6(1)(b) and 개인정보 보호법 제15조 제1항 제4호; legitimate interests GDPR Art. 6(1)(f) and 개인정보 보호법 제15조 제1항 제6호, all of which you can object to (6.2); consent GDPR Art. 6(1)(a) and 개인정보 보호법 제15조 제1항 제1호, off until you turn it on; legal obligation GDPR Art. 6(1)(c) and 개인정보 보호법 제15조 제1항 제2호.
2.5 If you reach NMTS through a business's product, that business opened your account and is its holder toward us (Terms 3.7). Your agreement is with the business, and the business is a separate controller, answerable to you, for whatever it collects about you. We are the controller only of what this table lists — your account carries no name here either — including which business opened the account. Because you have no agreement with us, we hold those records for you on legitimate interests (2.4) instead: running the account the business asked us to open, keeping the business's daily limit, and refusing any business's request for an account that is not its own. The business reads your account's records (4.1) within the permissions it signs for itself, for up to 30 days at a time; those permissions never reach the key that opens your files, delete the account or make its credentials. If the business holds your NMTS key, it can also sign in as the account and read your files; we still cannot. We send a business nothing about you beyond what its own requests return. The business shows you this policy, and asks for the consent section 5.6 describes, before it opens the account. Every right in section 6 is yours against us for what this table lists. If you hold the NMTS key, sign in with it at nmts.me and each route in 6.2 is open to you. If the business holds it, ask the business, which the Terms require to act for you in the account, or write to us (1.2): we will confirm with the business that the account is yours, because we hold nothing that identifies you. Section 12 says where you can complain.
2.6 Decisions taken by machine. The free trial is first-come, first-served within the week's quota; a support message identical to one sent in the last 24 hours is refused; a door that takes a secret refuses after repeated failures; a report that a public link holds child sexual abuse material or non-consensual intimate images cuts that link at once. None is final — write to us and a person looks. We do not profile you.
3. How records are destroyed
3.1 When a period above ends, a sweep deletes the rows themselves rather than hiding them, and deleting your account deletes the rows we hold for it. Where a law binding on us requires us to keep something longer, we keep it, record which law it was, and delete it when that duty ends.
3.2 Four things outlive the account: our note that we did something to an account, with your public code taken out; a stop or a board bar, which an account identifier being derived from your NMTS key would otherwise let you clear by making the account again; the fingerprint of each public code you revoked, for the same reason, with which anyone who holds that code can check that it was revoked; and the gift ledger and any display name, which follow the wallet and go when you sign again with it.
3.3 Deletion does not reach a backup taken before it (8.2) or the blockchain, which keep what they already hold. The storage network keeps the ciphertext until its term ends; for a file on NMTS Heavy paid with credits, deleting the file sends a removal request, and each provider deletes the bytes when it chooses.
4. Who receives it
4.1 We provide your personal data to no one as a third party, with one exception. A business that opened your account (2.5) receives what its signed requests for that account return — records from the Files, Credits and Storage loss rows of the table in section 2, and nothing that opens a file (개인정보 보호법 제17조 제1항 제2호). Two companies process it on our behalf under our instructions: Cloudflare, Inc., which serves the site and ends the encrypted connection, so it sees the whole of each request and response, runs the human check and stores our backups; and Proton AG, which runs the mailbox at nmts@nmts.me.
4.2 The gateway, storage and chain services are not ours and are not instructed by us, so each decides for itself what it does with what it receives. Your browser reaches the public networks through a Walrus upload relay and aggregator run by Mysten Labs, Inc., or, on NMTS Heavy, the Filecoin storage providers of 4.5 directly, and reads the Sui chain through Suiscan, a product of Staketab, and PublicNode, run by Allnodes Inc.; they see your IP address, the blob, piece and object identifiers, sizes and times, and, for the chain services, your wallet address and the transactions you sign. The Filecoin chain is read through GLIF, run by GLIF Ltd., by our own server and by the command-line tool when it pays from your own wallet, in which case GLIF sees your IP address, that wallet's address and the transactions it signs. Our own server also reads the Sui chain through Nodeinfra Co., Ltd. and Bware Labs and talks to the storage providers; its calls carry our wallet address, never yours.
4.3 Those are all of them. We use no analytics, advertising, support or marketing vendors and send no email or push notifications. We do not sell your personal information and do not share it for cross-context behavioural advertising.
4.4 When an authority demands data, what can be compelled is what section 2 lists; nobody can produce your files' contents or names, because we hold no key to them. For user-stored data we require a court order or a judge's warrant, we record every disclosure, and we tell you unless a law or the order forbids it.
4.5 Your encrypted files go to the Walrus network or, when you choose NMTS Heavy, the Filecoin network, and your payments to the Sui blockchain or, from your own wallet in the command-line tool, the Filecoin blockchain — public networks we neither own nor run. Nodes and storage providers run by independent operators, with whom we have no contract, hold the ciphertext, its identifier, its size and the time, and serve it to anyone who asks for it by identifier; the Filecoin providers are chosen from the network's public registry. Nobody there receives file names, your account, or anything decrypted. What your wallet signs is public and lasting, and neither we nor you can erase that ledger — consider that before importing a wallet linked to your identity elsewhere, before paying Filecoin from your own wallet, and before sending a gift.
5. Data leaving the country
5.1 OVH Hosting Inc. — our server.
- Items: every record section 2 lists, which our server holds.
- Country and recipient: Canada; OVH Hosting Inc., 1801 McGill College Avenue, Suite 800, Montréal, Quebec H3A 2N4, Canada, rprp@ovh.ca.
- When and how: from 10 October 2026, as each record is written, over encrypted connections, to our server in its data centre in Beauharnois, Quebec.
- Its purpose and period: to run our server; it holds each record for the period this policy gives that record.
- Ground: in Korea, 개인정보 보호법 제28조의8 제1항 제3호 가목, entrusted storage for the performance of your agreement, this policy being the disclosure it requires; in the EU, the European Commission's adequacy decision for Canada, 2002/2/EC, kept in force by GDPR Art. 45(9); in the United Kingdom, the Data Protection Act 2018, Schedule 21, paragraph 5(2)(b).
- How to refuse: this cannot be refused while you hold an account; deleting it removes your records from our server as section 3 describes.
5.2 Cloudflare, Inc. — the edge, the human check and our backups.
- Items: the whole of every request and response, this being the provider that ends the encrypted connection — your IP address, the address you asked for, anything you type into the support inbox or write on the board — and the encrypted copies of our database.
- Country and recipient: the United States and the nearest edge to you; Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, privacyquestions@cloudflare.com.
- When and how: at each request, over encrypted connections; the database copies daily at 03:30 UTC and at five past each hour in which anything changed.
- Its purpose and period: to deliver and protect the site and to check that a request comes from a person; it holds a backup as long as we keep it there.
- Ground: in Korea, 개인정보 보호법 제28조의8 제1항 제3호 가목, entrusted processing and storage for the performance of your agreement, this policy being the disclosure it requires; in the EU and the UK, the European Commission's standard contractual clauses and their United Kingdom counterpart, sent on request.
- How to refuse: for the human check, do not create an account, sign in, apply for a trial or take a one-time pass for an AI agent. The edge cannot be refused while you use the site, and the backup cannot be refused while you hold an account; deleting it keeps you out of every copy written afterwards.
5.3 Proton AG — our mailbox.
- Items: email you send to nmts@nmts.me, and a daily summary of that day's support messages.
- Country and recipient: Switzerland; Proton AG.
- When and how: as each email arrives, and once a day for the summary, over encrypted connections.
- Its purpose and period: to run the mailbox so that we can answer you; both go 12 months after our last reply, sooner if you ask.
- Ground: in Korea, 개인정보 보호법 제28조의8 제1항 제3호 가목, entrusted storage for the performance of your agreement, this policy being the disclosure it requires.
- How to refuse: do not email us; the support inbox reaches us without this transfer.
5.4 The storage networks and the chain services are different. We have no contract with any of them, so no entrustment route is open to us, and what your browser sends leaves your device without us as the exporter. Your ciphertext goes to Walrus nodes or Filecoin providers whose countries we do not fix and cannot verify; there is no adequacy decision and no standard contractual clauses for that, because there is no counterparty to sign them. In the EU and the UK we rely on GDPR Art. 49(1)(b), the transfer being necessary to perform your agreement with us, and a supervisory authority may take a narrower view of that ground. For Korea we cannot point to a ground in 개인정보 보호법 제28조의8 제1항 that we are satisfied covers these flows, and a regulator could conclude that they do not meet the overseas-transfer rules. What protects you is that the data is encrypted on your device before any byte leaves; the one item encryption does not cover is your IP address, which the gateway, node or provider exchanging the bytes with you can see.
5.5 Ask us which countries hold your data, at nmts@nmts.me: we read the storage nodes or providers and the locations they declare on the public ledger and send you what they say, with the time we read it, unverified because we cannot check them.
5.6 A business that opened your account (2.5) may be established outside the Republic of Korea, and then reads that account's records from there.
- Items: what its signed requests for the account return — records from the Files, Credits and Storage loss rows of the table in section 2.
- Country and recipient: the business, in the country it is established in; the business tells you both before it opens the account.
- When and how: each time we answer one of its signed requests, over an encrypted connection.
- Its purpose and period: running its product for you; its own policy says how long it keeps what it reads.
- Ground: your consent, which the business obtains before it opens the account (Terms 3.7) — 개인정보 보호법 제28조의8 제1항 제1호, and GDPR Art. 49(1)(a). For you that consent also covers 5.2 and 5.3, because you have no agreement with us for 개인정보 보호법 제28조의8 제1항 제3호 to rest on.
- How to refuse: tell the business you refuse; it then opens no account for you, and its product works for you only as far as it can without NMTS.
6. Your rights, and how to use them
6.1 Everyone gets the same rights, wherever you live. In Korea, 개인정보 보호법 제35조 access, 제36조 correction and deletion, 제37조 suspension of processing and withdrawal of consent; in the EU and the UK, GDPR Chapter III. Where a law gives you more, it applies on top of this.
6.2 You can ask what we hold and get a copy in a usable form, correct something including a finding of ours about you, delete files, empty the trash, withdraw a support message or delete your whole account from inside the product, ask us to stop using a record but keep it while something is disputed, and withdraw a consent, which does not make what we did on it before the withdrawal unlawful. You can object to anything we do on a weighing of interests, and we stop unless the interest demonstrably prevails for your particular situation (GDPR Art. 21(1)); in Korea the right is wider, because it does not ask what our basis was.
6.3 Use either contact in 1.2, and a person answers by hand. Your NMTS key is the only credential we have and we do not hold it, so a request about an account must come from a signed-in session for it or quote the public code of the message it relates to. We will not accept an identity document instead, because that would mean collecting exactly the data this service avoids. A legal representative can act for you, and what shows the relationship is destroyed at once. If a business opened your account, 2.5 says how you reach us.
6.4 How fast, and at what cost. Without undue delay, and at the latest 10 days in Korea and one month in the EU and the UK, extendable by up to two further months for complex or numerous requests with our reason given inside the first month. There is no charge. If we refuse we say why, and that you can complain to an authority and go to a court where you live.
7. What is collected automatically in your browser
7.1 One cookie records whether you read English or Korean. It is set for that and nothing else, and you can refuse or delete it in your browser settings without the site breaking. Everything else the product keeps on your device stays there, including the private key of any wallet you imported, encrypted under a key derived from your NMTS key and never sent to us; you can clear all of it from your browser settings.
7.2 Do Not Track and Global Privacy Control. We do not collect what you do over time and across other websites, so there is nothing for such a signal to switch off, and as far as we can tell no other party does it through our pages: the only code on our pages from another company is our edge provider's.
8. How we keep it safe
8.1 Your files are encrypted in your browser with keys derived from a secret we do not hold. Your sign-in secret is stored as an argon2id verifier with a per-account salt and sign-in tokens as hashes; a session ends when you sign out, or earlier once it goes unused for the length you chose (30 days for “until you sign out”); a session of 1 hour to 30 days also ends 30 days after sign-in, even if in use; IP addresses are handled as 2.3 describes; operator access runs on credentials the operator alone holds, and what an operator does through the administrative routes is recorded. The text of a support message is encrypted inside the database under a key our server holds, so a copy of the database alone does not open it.
8.2 The backups are the honest exception. We take encrypted copies of the whole database and store them off-site with Cloudflare: a full backup daily at 03:30 UTC and a further backup at five past each hour in which anything changed. A backup taken before you deleted something still contains it, and for the first 7 days the store refuses to let a backup be deleted or altered, which is why an erasure cannot reach a copy inside that window; after that an hourly backup goes 91 days after it was written and a daily backup 364 days after. Because a restore can bring back records deleted after the backup was taken, before the service opens again we compare the restored backup against the newest one we hold and delete again the accounts deleted in between.
8.3 If someone got our server or the account holding our backups, they would have what section 2 lists in readable form and your encrypted blobs — but not your NMTS key, your file keys or your file contents.
9. If personal data is lost, stolen, leaked, forged, altered or damaged
9.1 We will tell you — unless, and only for as long as, a law or a binding order forbids it, or we are still finding out how far it reached and closing the way in. Korean law treats those six events together as 유출등 and requires the notice (개인정보 보호법 제34조 제1항, in force 11 September 2026, reading 유출등 as defined in 제23조 제2항). The GDPR calls it a personal data breach, requires us to tell the supervisory authority within 72 hours of becoming aware unless it is unlikely to risk your rights (Art. 33(1)), and to tell you where the risk to you is high (Art. 34(1)).
9.2 What the notice says: which categories of data were involved; when it happened and how; what you can do to limit the harm, the one step that genuinely protects you here being to create a fresh account and move your files to it; what we have done and how you can be helped; how to reach the person handling it; and what you can claim and where, meaning compensation, statutory damages and dispute mediation (개인정보 보호법 제34조 제1항 제1호부터 제6호까지).
9.3 How and when. We hold no address for you, so Korean law's provision for that case applies: we post what the notice must carry on our own site for at least 30 days instead (개인정보 보호법 제34조 제1항 단서 · 시행령 제39조 제3항). That posting is the notice board, a page in the product and on the website, readable without an account, where every notice carries the date it went up. It goes up within 72 hours of our becoming aware, and what we cannot yet confirm we add as we confirm it (시행령 제39조 제1항·제2항). We report to the Personal Information Protection Commission within 72 hours in the cases the decree names (시행령 제40조 제1항). In the EU and the UK the same posting is the public communication Art. 34(3)(c) allows where individual notice would take disproportionate effort, which it does because we hold no address for you.
9.4 Storage of yours that goes missing is one of these events. Where the daily check finds the chain no longer knows an object that held a file of yours, the finding is shown on your own drive and posted the same day on the notice board, naming nobody. We ask the chain again each day for twelve months and take the notice down if the object is found, and you can have an object checked again at once.
10. Children
10.1 The service is not directed to children. We hold no date of birth and cannot verify anyone's age; the one age record we keep is your own statement on the board that you are 14 or older. If we learn that an account belongs to a child below the minimum age in the Terms, we stop serving it and delete the records we hold for it at once. An account a business opens carries that business's undertaking, under Terms 3.7, that its product is not directed to children and that it opens no account for anyone below that age. If you are a parent or guardian and think your child has an account, write to nmts@nmts.me with anything that lets us find it.
11. Changes to this policy
11.1 Every version carries a version string in the form YYYY-MM-DD-vN and an effective date, both at the top of this page. We do not edit a published version in place: a change means a new version string, we keep every version with the dates it was in force, and we send you any of them if you ask.
11.2 A new version is posted on the notice board with its date, and this policy is kept continuously posted on the website, linked from the foot of every page, in both languages (개인정보 보호법 제30조 제2항 · 시행령 제31조 제2항).
12. Complaints
12.1 Write to us at nmts@nmts.me — but you do not have to come to us first. You can complain to a supervisory authority and bring a claim in court, and in the EU and Korea the law guarantees you can do that where you live.
12.2 In Korea: the Personal Information Protection Commission (개인정보보호위원회) and the 개인정보 분쟁조정위원회. In the European Union: the supervisory authority where you live, work or where the problem happened. In the United Kingdom: the Information Commissioner's Office, and UK law also lets you complain to us directly (Data Protection Act 2018, s. 164A). Anywhere else: your national data-protection or consumer authority.
13. Language
13.1 English is the canonical text of this policy, and the Korean version is a full version of the same content, not a summary.
13.2 Where there is doubt about the meaning, the reading more favourable to you prevails, and the mandatory law of the country where you live prevails over both language versions. If you are a consumer habitually resident in Korea, the Korean version prevails for you. Subject to those rules, if the two genuinely conflict, the English version is the reference text.