01 Scope and controller
This notice describes how OrderFlow Metrics Editorial Desk, an independent editorial unit, handles information in connection with the static documentation site published at orderflow-metrics.org. The desk is the point of contact for every question raised on this page. Its postal address, electronic mail address and telephone number appear in the final section.
The site is a fixed collection of hand-authored HTML and CSS documents about configuring the ATAS (Advanced Time And Sales) analytical platform. Because those documents are static, there is no application layer behind them, no visitor database, no session state, and no facility for a reader to create, edit or remove records on the server. Pages are prepared in advance and served as files.
02 What the hosting layer records
Like nearly every web host, the server writes a short technical line each time a file is requested, so operators can keep the site reachable and trace faults. A typical line contains the requested file name, the date and time of the request, the response status code, the number of bytes returned, and a truncated network address. No line is joined to a name, a profile or a cross-site identifier.
| Field | Purpose | Kept |
|---|---|---|
| File name | Availability monitoring | 30 days |
| Date and time | Fault tracing | 30 days |
| Status code | Error detection | 30 days |
| Bytes returned | Capacity planning | 30 days |
| Truncated address | Abuse mitigation | 30 days |
Log lines are retained for a rolling window of thirty days and are then discarded automatically by the host. They are used only for availability monitoring and abuse mitigation. They are never sorted into behavioural insight, never scored, and never enriched with information obtained elsewhere.
03 Forms and messages
Some pages display a form layout so that readers can see the intended arrangement of labels, fields and buttons. Those demonstrations transmit nothing. There is no handler on the server to receive a submission, no mailbox that is filled by the form, and no database table where entered text is written.
Note A page styled as a form is a visual example. Typing into it and pressing the button does not send or save anything, because no receiving code exists on the host.
Where a reader wishes to contact the desk, the route is electronic mail or postal mail. Correspondence sent that way arrives in an ordinary mailbox and is handled under the practices described in section four. It is not copied into any web-facing system.
04 Reader rights and how to exercise them
A reader may ask what information about them, if any, is held. In practice a static site holds none that is tied to an identity, but the request is still honoured. Four rights are offered without charge.
- Access
- Confirmation of whether any record connected to the requester exists.
- Correction
- Fixing an inaccuracy in correspondence the desk has kept.
- Deletion
- Removal of correspondence that the desk no longer needs to keep.
- Objection
- A request to stop using correspondence for any purpose beyond answering it.
Requests may be sent to [email protected] or by post to 1840 Wexford Avenue, Suite 12, Portland, OR 97205, United States. A reply is sent within thirty days. No fee is asked and no identity proof beyond a workable return address is demanded.
05 Children
The documentation is written for technical adults who configure charting software. It is not addressed to children, and the desk does not knowingly keep information about anyone under thirteen. If a parent or guardian believes a child has corresponded with the desk, a message to the address above will lead to prompt deletion.
06 Tracking, advertising and third parties
The site runs no analytics package, no advertising network, no social plug-in and no tag manager. No element on any page sets a number of its own in the reader's browser, and no page asks a remote service to load a resource. Fonts, images and style sheets are served from the same host as the pages themselves.
The desk does not share, rent or exchange correspondence with anyone. The only circumstances in which a record would be handed over are a lawful request from a competent authority or a necessity to protect the safety of a person, and any such event would be logged and reported in the correction log kept on the editorial policy page.
Questions about this notice, and requests to amend or expand it, may be raised through the contact page or by electronic mail. Last reviewed: 12 October 2026.