Do I Need to Own a File to Decode It?

Yes. Emphatically, unambiguously yes. You must own the file or have explicit written permission from the owner before recovering its source. This is not a soft guideline you can talk your way around, and it is not a box to click through without reading. It is the single condition the entire service is built on. If you do not have rights to the software, this service is not for you, and no amount of framing changes that.

Because this question comes up constantly and the answer genuinely matters, this article explains why ownership is required, what the attestation at upload actually means, what does and does not count as authorization, and how to handle the gray areas responsibly.

Why Ownership Is Non-Negotiable

Source recovery exists for legitimate, common reasons. You wrote software and lost your own source. You inherited or purchased a codebase you now own. You are authorized to maintain an application and the original files are gone. In every one of those cases, recovery helps you get back something that is rightfully yours to have.

Using recovery on code you have no rights to is a different thing entirely, and it is prohibited. It also defeats the entire purpose of the service. The tool is a way to get your property back — not a way to take someone else's work, bypass a license, or obtain source you were never entitled to. The ownership requirement is what keeps the service on the right side of that line, and it is enforced as a matter of principle, not convenience.

This applies without exception regardless of how the file was protected. Whether you would route it through the ionCube decoder or the SourceGuardian decoder, the rule is identical.

The Ownership Attestation at Upload

Every upload requires you to attest that you own the file or are authorized to recover it. This is a deliberate checkpoint placed at the exact moment it matters. By submitting, you are formally declaring that you hold the rights. That declaration is your responsibility, and it is on you to be truthful about it.

Think of the attestation like a signed statement rather than a cookie banner. It exists to put the authorization question squarely where it belongs: with the person requesting recovery, who is the only one in a position to know whether they actually have the rights. The attestation does not create rights you do not have — it records the claim you are making. That distinction is important, and it is why an honest answer at this step is not optional.

What Counts as Ownership or Permission

Some clear cases where you are on solid ground:

• You wrote it. You built the software, lost the source, but still have the encoded build. That code is yours.
• You bought the business or the codebase. You acquired the rights to the software as part of a purchase, and those rights include the source.
• You commissioned it and own the result. You paid for custom development under terms that gave you ownership, and you simply lost the original files.
• You have written authorization. The copyright holder gave you explicit, written permission to recover and maintain the code.

In each of these, you can honestly complete the attestation and proceed.

What Does Not Count

Equally important is recognizing the situations where you should stop:

• A usage license. Software you merely use under a license that does not grant source rights is not yours to recover. This is the most common misunderstanding, and it is covered in more depth below.
• Files shared without authority. Something a colleague, forum, or third party gave you without the right to do so does not become yours to recover just because you now possess it.
• Anything you cannot honestly attest to. If you are not sure you own it or have permission, that uncertainty is your answer. Do not proceed until it is resolved.

Handling the Gray Areas

Real situations are not always tidy. Maybe you bought a product years ago and are not sure what the terms said. Maybe you are maintaining a client's system and are not certain your engagement covers source recovery. In these cases, the responsible move is to resolve the ambiguity before uploading, not after. Re-read your purchase or license terms. Ask the original author or vendor for written permission — a short written grant removes all doubt. When you cannot get clarity, the safe and correct choice is not to proceed. It is far better to spend a day getting permission in writing than to act on a guess.

Why This Protects You Too

The ownership requirement is not only about the rights of others; it protects you. A clear record that you attested to ownership, backed by genuine rights and ideally by written permission you have kept, means you are acting responsibly and can demonstrate it. The requirement keeps the whole service legitimate, which is in the interest of every honest user. A tool that ignored ownership would be a tool for the wrong purpose, and it would not be worth trusting with your own code either.

FAQ

A license to use the software — is that enough? Generally no. A usage license is not the same as owning the source or having permission to recover it. When in doubt, get written permission from the owner first.

What if I only have written permission, not ownership? Written permission from the rightful owner is acceptable. Keep a record of it in case you ever need to show your authorization.

Does the attestation protect me legally? It records your declaration of rights. It does not create rights you do not have, so make sure your claim is genuine before you make it.

I wrote the code but a client paid for it — who owns it? That depends on your agreement. Ownership of commissioned work varies, so check the contract terms before assuming the source is yours to recover.

The vendor is out of business — can I just recover it now? The vendor being gone does not automatically transfer rights to you. You still need genuine ownership or permission; their absence removes one path to the source, not the ownership requirement.

What if I'm honestly unsure whether I'm allowed? Then do not proceed until you have resolved it. Re-read your terms, seek written permission, and only upload once you can truthfully attest.

Recover What's Rightfully Yours

If you own the software or are authorized to recover it, you are exactly who this service is for, and the ownership requirement is nothing to worry about — it simply describes your situation. Learn more on the FAQ or review pricing, then start a free trial or create an account to begin. Just make sure, every time, that the file is genuinely yours to recover before you attest and upload.