Terms of use

What you declare

By uploading a program, you declare that you own it, or that you are entitled to analyse its code. VBReFormer does not verify this declaration and cannot verify it: it binds you.

Where the analysis happens

On our servers, in both editions. The desktop application embeds no analysis engine: the installed package contains no decompiler assembly, only the interface and what it needs to talk to the service. Disassembly and decompilation alike are sent to vb.decompiler.tools and run there. Your binary therefore leaves your machine, whether you go through the browser or the installed application, and a connection is required.

What becomes of your file

• It is sent to our servers, where it is written to a temporary file under a randomly drawn name, for the duration of your session. That file is erased when the session ends: when you close the tab, when the connection drops, or after twenty minutes without activity.
• Nothing is kept: neither the uploaded binary nor the reconstructed project. Closing the session erases both, and there is nothing to recover afterwards.
• The service does, however, keep a record of which programs were analysed, in the form of a fingerprint of their content — a number that identifies a file without making it possible to reconstitute it, or to learn its name. It serves support, pay-per-use billing and abuse detection. For an identified account this list is attached to the account; for an anonymous visit it is attached to no one. These records are kept for one year from the last use, then erased.
• The service keeps an operations log recording the time, the operation requested, sizes and durations — to size the hosting. It contains neither your file's name, nor its content, nor the reconstructed code.

The limits of the service

An uploaded binary may not exceed 64 MiB. A session opens one document at a time; the service accepts six in parallel; a session without activity expires after twenty minutes.

What the service does not promise

Decompilation reconstructs an equivalent source, not the original one: local variable names, comments and layout are not in the executable and cannot be drawn from it. Where a value cannot be restored with certainty, VBReFormer writes a marker rather than a plausible value.