Privacy policy.

The person responsible — the data controller, in the language of the GDPR — is:

[FULL LEGAL NAME], trading as NoRunDev
[STREET ADDRESS, POSTCODE, CITY, COUNTRY]
[VAT NUMBER, if you have one — otherwise delete this line]
support@norundev.com
WhatsApp: +39 334 870 4214

There is no data protection officer, because this operation is not the kind that needs one. Write to the address above for anything on this page and you reach the person who wrote the program and runs the server.

Four things are worth knowing before the detail.

Opening a dump sends it. The whole 2 MB image goes to this project's server, because Validation, Repair and Regenerate run there and not on your machine. It is a condition of use in the Terms of Service too, and it is the single most important fact on this page.

A NOR dump is personal data. It carries the console's serial, board id, SoC id and MAC addresses. Those identify a specific machine, and through it, usually, a specific person. It is treated as personal data here, not as an anonymous blob.

Nothing is sold, and there is no advertising, analytics or profiling. Three suppliers are involved in running the service, and they are named below. Nobody else receives anything.

Contribute is the exception to all of this, and it only runs when you choose it. It is covered in its own section.

The dump you open. The whole image on first open; after that, only your changes, until they grow large enough that the whole edited file is sent again and becomes the copy the server works on. Why: to run Validation, Repair and Regenerate, which is the thing you bought. Legal basis: performance of the contract, Art. 6(1)(b) GDPR. Without this the paid features cannot work at all — the program still opens a dump and runs ten structural checks locally, but nothing more.

Identity fields you type by hand. Travel with your changes, same as above, same basis.

Your licence key and a fingerprint of your computer. Sent with every request to this project's server, and separately to the licensing service for the check at launch. Why: to confirm the licence is valid, to hold it to one computer, and to detect sharing. Legal basis: performance of the contract for the check itself, Art. 6(1)(b); legitimate interest in protecting the licence against abuse, Art. 6(1)(f), for the anti-abuse side. You can object to the second one — see Your rights — though the licence check itself cannot be switched off without the program ceasing to work.

Your email address and order details. Collected when you buy. Why: to send you the key, to handle transfers, refunds and support, and to keep the accounting records the law requires. Legal basis: performance of the contract, Art. 6(1)(b), and legal obligation for the tax records, Art. 6(1)(c).

What you write to support. Why: to answer you and to keep a record of what was agreed, particularly where a ban or a refund is involved. Legal basis: performance of the contract and legitimate interest in being able to show what was said, Art. 6(1)(b) and (f).

A dump you donate through Contribute. Separate section below, separate legal basis: your consent.

The dump on the server. [CHOOSE ONE AND DELETE THE OTHER TWO — this sentence must describe what the code actually does, so pick the one that is true, or change the code to match the one you want to promise. (a) "Your image is deleted within 24 hours of the last operation performed on it." (b) "Your image is deleted when the program closes, and in any case within 24 hours if the program does not close cleanly." (c) "Your image is kept only while there is space to keep it and is overwritten as newer images arrive; in practice this means it is normally gone within days, but no fixed period can be promised."] While you are working, the copy on the server is replaced by a fresh one whenever your edits grow too large to send as a change list.

Licence and order records. For the length of your term, and then for the period the tax law requires of accounting records — [10 years in Italy; adjust if you are established elsewhere].

Support correspondence. [24 months] from the last message, or longer where a dispute, a chargeback or a ban is still open.

Donated dumps. Until you ask for the donation to be removed. Read the Contribute section before relying on that, because part of what is learned from a donation cannot be called back.

Contribute adds a dump to the reference pool. Nothing is donated by opening a file — only by using that feature, deliberately, when the program asks you and you say yes. Legal basis: your consent, Art. 6(1)(a) GDPR, and you can withdraw it at any time by writing to support.

A donated dump is filed under a fingerprint of your computer, which appears as a folder name on the server next to the dump itself. A note you attach — whether the console worked, a southbridge revision, a comment — is recorded as your claim and is not checked against the chip.

Two things happen to a donated dump, and you should be clear on both before agreeing. What is learned from it feeds the derived maps and templates the service uses: some ship with the program, others stay on the server. And once it has been sanitised — identity fields and logs removed — the dump can serve as a reference dump for Regenerate, which means partitions of your console, other than the ones that identify it, can be written into another customer's console.

Withdrawing consent stops the future, not the past. This is the part that matters and that most notices skip. If you ask for a donation to be removed, the file and the folder holding it are deleted, and it is no longer used as a reference. What cannot be undone is what has already left: the information that has already been folded into the derived maps, and the partitions already written into consoles that were repaired before you asked. Those cannot be identified, recalled or reversed. If that is not acceptable to you, the answer is not to use Contribute — everything else in the program works without it.

One further honest note. Sanitising removes the fields that identify the console. It does not make the file mathematically anonymous: unk holds calibration specific to each console, and a determined comparison against a known dump could in principle link a sanitised file back to the machine it came from. For that reason donated dumps are treated here as pseudonymised personal data, not as anonymous data, and they keep the full protection of this notice.

Three suppliers are involved in running the service. Each of them acts on instructions, under a written agreement, and none of them is allowed to use anything for its own purposes. Nothing is sold, rented or passed to anyone else, and no authority receives anything unless a valid order requires it.

Keygen LLC (api.keygen.sh) — the licensing service, and the only supplier that data leaves the European Union to reach. It receives your licence key, the fingerprint of your computer and two identifiers. It receives no dump data at all: licence checks run on a separate channel by design, and that separation is deliberate.

Keygen is established in the United States and stores this data on Amazon Web Services infrastructure in Virginia. The transfer takes place under the Standard Contractual Clauses adopted by the European Commission, which form part of Keygen's own terms and which it applies to all of its customers. Keygen states that it keeps this data for up to 30 days, and that a deletion request is carried out within 30 days. It uses its own suppliers in turn — among them Amazon Web Services, Cloudflare and SendGrid — which it lists in its privacy notice.

One consequence worth stating plainly: because the record of activations lives there rather than here, Keygen is where the information behind a licence-sharing finding comes from. It is also the only place any data about you exists outside the EU. If you would rather it did not, there is no way to use the program without it — the licence check is what the program does before anything else.

Ko-fi — the shop through which plans are sold. Receives what a payment needs: your email address, the order, and the payment details you give it. Those payment details never reach this project; only the order and your email do.

OVHcloud — the hosting provider that runs the machine the server sits on, in its datacentre in Warsaw, Poland. OVHcloud provides the infrastructure and acts strictly on instructions, under the data processing agreement that forms part of its service contract. It does not access the images, and it does not use anything held on the machine for any purpose of its own. Like any hosting provider it keeps its own short-lived infrastructure logs, which it describes in its own documentation.

The server that Validation, Repair, Regenerate and Contribute run on is a virtual private server hosted by OVHcloud in its Warsaw datacentre, in Poland — inside the European Union. Your dump never leaves the European Union. The only data that does is the licence check described above, which carries no dump data at all and goes to the United States.

The server keeps no access logs. No IP addresses, no request history, no record of which files you opened or when. This is unusual and it is a deliberate choice, but it has a consequence worth stating plainly: if something goes wrong, there is very little to reconstruct it from.

This website sets no cookies, runs no analytics and embeds no third-party scripts or fonts. [Confirm this is still true of every page before publishing. If you ever add a visitor counter, an embedded video or a web font served from someone else's domain, this sentence stops being true and a cookie notice becomes necessary.]

The program stores your licence key and the cached result of the last successful licence check. That cache is what keeps the program working for 24 hours without a network, and it is also where a suspension or cancellation is written, so that a refusal holds even with the network unplugged.

Nothing else is kept: no usage statistics, no crash reports, no telemetry of any kind, and no record of the files you have opened. Your dumps stay where you put them. Deleting the program removes the key and the cache with it.

This section is for repair shops and technicians, and it exists because the person whose data is actually in the dump is usually not the person using the program.

When you send a dump from a console you are servicing, you are sending data that identifies your customer's machine. For that customer, NoRunDev is a data controller in its own right — because it decides how the image is stored, how long it stays, and how what is learned from it is used — and you are one too, for your own reasons for holding it. That means two things follow.

Your customer has to be told. Before you send the dump, they should know that the image will be transmitted to and briefly held by a third party in the EU for the repair to be carried out. A written agreement covering this is available on request — write to support and ask for it — along with a short text you can hand to your customer. Both are free.

Contribute is a decision you cannot make for them. Donating a customer's dump puts partitions of their console into the reference pool. Do not use it on a machine that is not yours without their explicit agreement.

Your customer can exercise every right listed below directly against this project, by writing to the support address, even though they never bought anything here.

Under the GDPR you can ask for the following, and asking costs nothing.

Access — a copy of what is held about you, and confirmation of what is being done with it. Rectification — correction of anything wrong. Erasure — deletion, subject to the accounting records that the tax law requires be kept. Restriction — a freeze on processing while something is disputed. Portability — the data you provided, in a machine-readable form. Objection — to anything done on the basis of legitimate interest, which here means the anti-abuse side of the licence checks. Withdrawal of consent — at any time, for Contribute, with the limits described in that section.

Write to support@norundev.com or on WhatsApp at +39 334 870 4214. You get an answer within one month. If the request is complicated the law allows that to be extended by two more months, and you will be told if that happens and why. You will not be asked to justify a request, and a request will never be treated as a reason to look at your account differently.

One practical limit, stated in advance: because the server keeps no logs and donated dumps are filed under a machine fingerprint rather than a name, an access request may need the licence key or the fingerprint to find anything at all. If you have neither, there may be nothing that can be located.

If you think your data has been handled badly, you can complain to a supervisory authority — in Italy, the Garante per la protezione dei dati personali (Piazza Venezia 11, 00187 Roma, garanteprivacy.it), or to the authority of the country where you live. You do not have to write here first, although it is usually faster.

The measures in place are [DESCRIBE WHAT IS ACTUALLY TRUE — e.g. "encryption in transit over TLS for every request; access to the server restricted to key-based authentication from a single administrator account; the disk holding uploaded images encrypted at rest; no copies taken off the server". Do not list anything you have not implemented: an overstated security claim is easier to be caught on than a modest one.]

No system is beyond failure, and this one is run by one person. If a breach occurs that is likely to put you at risk, the supervisory authority will be notified within 72 hours as the law requires, and you will be told directly, in writing, with what is known at the time — including the limits on what can be reconstructed, given that no access logs are kept.

This is run by one person, and that is stated openly in the Terms of Service, which also say what you keep of the program if it stops — see If the service shuts down. If the service ends, everything held on the server — dumps still in process, donated dumps, the reference pool — is deleted. Nothing is sold on, transferred to another operator or handed to anyone as an asset. Licence and accounting records are kept for as long as the tax law requires and then deleted too.

This page changes when the program changes — a new server-side feature, a new supplier, a different retention period — and the effective date at the top moves when it does. Earlier versions are kept and can be requested from support.

If a change materially affects what happens to your data, you will be told by email, at least 15 days in advance, at the address you bought with. Where a change relies on your consent, the change does not take effect for you until you give it.

Anything on this page — a request, a complaint, a question, a donation you want removed — goes to support@norundev.com, or on WhatsApp to +39 334 870 4214.