Overview / Privacy
Privacy
What does this website learn about the people who read it?
The words you deliberately type into the demo request form, and nothing else. These pages carry no measurement layer, ask your browser to store nothing, and hand out no identifier that would let one visit be recognised as the same reader as the next.
Is any analytics or tag-management code loaded on these pages?
None is. Read the source of this page: apart from our own domain, the only host it asks your browser to contact is the font service described further down. No tag manager sits behind these pages, no advertising pixel fires on them, no session-replay recorder watches the cursor, and no counter increments when a page opens. The consequence is worth stating plainly, because it is the whole point: the readership of this page is unknown to us. How many people opened it, which link carried them here, which paragraph they stopped at — those facts do not exist on our side of the connection. A vendor writing about measurement restraint while quietly instrumenting its own brochure would be arguing against itself, so the instrumentation was left out. Introducing it later would be a change to the code, and this page would be rewritten in the same change.
Are cookies, local storage or session storage used anywhere here?
Not one of the three. Nothing is written to your browser that outlives a page load, which is why no consent banner interrupts the reading: a banner exists to gather permission, and there is no permission here to gather. Close the tab and your browser holds exactly what it held before you arrived.
Where do the figures typed into the latency budget allocator go?
Each of them stays in the browser tab where it was entered. The allocator on the service baselines page is arithmetic run by a small script already sitting in your browser: it totals the milliseconds you enter, subtracts that total from the target you set, works out each hop's share and draws the bars. No value is written to storage, no value travels to this server or to any other, and every figure you entered dies with the tab you entered it in. Open your browser's network panel and use the allocator with it running: it stays empty, because there is no request to record.
Who processes the demo request form, and what passes through them?
The form posts to FormSubmit, an external form-to-email service. It is the machinery that converts a submission into a message sitting in our mailbox, and it is what redirects you afterwards to the acknowledgement page on this domain. Everything you typed necessarily passes through it in transit, and what that company may do with a message while handling it is governed by the terms and the privacy notice it publishes on its own account. Anyone who would rather keep the exchange between two parties can leave the form alone and write to contact@optier.com; the message reaches the same mailbox and the same readers.
What travels is what the page asks for: your name and work email, then — only where you choose to fill them in — your organisation, your role, the transaction you would want followed, an approximate count of the systems it crosses, the stage you have reached, and the message itself. The markup holds one more field that is hidden from view. A person completing the form never sees it and never fills it in; automated submitters generally do, which is how those submissions are recognised, and whatever they put there is thrown away unread.
What is done with a request once it arrives?
- One of the engineers building OpTier reads it, and the reply comes back from that person.
- Correspondence remains filed where it landed, which is what keeps a question asked in one season intelligible to whoever reopens the exchange two seasons afterwards.
- Your address joins no mailing list, for the straightforward reason that this company operates none.
- Nothing you wrote is put up for sale, rented out, bartered, or handed to some other business to use for ends of its own.
- Say that you want the thread erased and erasing it is the next thing that happens, with a short note back to confirm it has gone.
What sits in the web server's own logs?
The machine serving these files keeps the access log that any web server keeps: the network address the request came from, the file that was asked for, the time it was asked for, the response code returned and the browser's own description of itself. Those lines exist so the server can be run and defended, and they get read when something breaks or when the traffic pattern turns hostile. They are not joined to form submissions, not assembled into a profile of a reader, and not handed to anybody outside the people operating the server.
Why does a page here fetch a typeface from another company?
The display face and the body face are both delivered by Google Fonts. One request therefore leaves your browser for that service whenever a page here loads, and it carries your network address with it. The design does not depend on the download succeeding: a content blocker, a corporate proxy that refuses the domain, or an outage all leave the page rendering in a fallback face that reads perfectly well, and no layout on this site breaks when the fetch is blocked.
Could our production data reach OpTier through this website?
There is no route by which it could. OpTier is monitoring software that a customer installs and runs on infrastructure they control themselves. The traces it records, the baselines it builds and the alerts it raises all stay inside that organisation. We are not an operations business and do not administer, repair or watch anybody's systems on their behalf, so no channel exists that would carry your transaction data to this marketing site or to the people who write it. A security reviewer assessing what is in front of them is assessing static pages and one email form.
Is any of this aimed at children?
The subject is enterprise monitoring software and the readers it is written for are the engineers, operators and reviewers who evaluate that kind of product. No page here is directed at a child, and nothing is knowingly gathered from one.
Who answers a question about this notice?
Write to contact@optier.com and a person replies. Procurement questionnaires and security reviews covering this website are answered from that same address, in writing.
Last reviewed 15 August 2026.