This page confirms that the message form on the contact page reached its confirmation step. It records nothing, sends nothing and stores nothing.
01 What has just happened
The form navigated here. Because the form uses a plain navigation rather than a transmission step, the values you typed were moved into the address of this page in your own browser and no copy exists anywhere else. If you closed the browser without copying the text, the message content is gone; there is no server record to recover it from.
| Location | Content |
|---|---|
| This page address | Form values, visible to you in the browser |
| Desk mailbox | Nothing |
| Server storage | Nothing |
| Third parties | Nothing |
The page address, rather than a stored record, is what carries the text. That is why the confirmation is instant and unconditional: there is no queue to join, no acknowledgement to wait for and no failure mode in which a message is half-recorded. It also means the confirmation is not a receipt. Nothing has been received, and a reader who treats this page as proof of delivery will be disappointed when no reply arrives.
02 To reach the desk, use one of two routes
- Email — send the text to contact@volume-profile-lab.org from your own mail client. This is the fastest route for corrections.
- Post — write to 1201 Orange Street, Suite 600, Wilmington, DE 19801, United States. Use this route for correspondence that must be traceable.
If the message concerned a specific page, include the page name and the configuration it describes; the desk triages by page record, so that detail decides the response order.
03 What happens to a correction
A correction is logged against the page it names, checked against a reproducible configuration, and then either published as a rewrite or returned with an explanation of why the observed behaviour differs. The revision tag in the site header changes when a section is rewritten; small typographical repairs are made without moving the tag. Nothing is published as a correction unless the reporting configuration is stated.
The checking step is the slow part. Reproducing a reported configuration means rebuilding the panel from the instrument, the bar rule and the session template, then replaying a session over the same window. If the result matches the report, the page is rewritten that week. If it does not, the reply describes what was observed instead, because a difference in behaviour is itself useful information about a parameter.
04 While you are here
The three configuration pages are the most-read part of this reference: footprint chart configuration, cluster chart and TPO and Smart DOM depth settings. The comparison of order-flow architectures is on the architecture comparison page, and the open question-and-answer page collects the configuration questions most often sent to the desk.
05 A note on what this site is not
This is a documentation reference. It does not hold any reader profile, it has no mailing list, it publishes no commentary on instruments, and it offers nothing for sale. Because no data is collected by the form, there is nothing to delete on request — but the privacy policy still describes the server logs kept by the hosting operator, which is the only record that exists in connection with a visit.
That absence is deliberate rather than incidental. A reference that collects readers has to justify the collection, publish a retention schedule and answer requests about it; a reference that collects nothing can spend its maintenance budget on documenting parameters instead. The cookie policy sets out the storage position in detail, and the disclaimer states the independence position that makes the whole arrangement possible.