Privacy
This site is a set of static files and one form. It sets no cookies, runs no analytics, loads nothing from another domain, and has no account to sign into. The only personal data it ever handles is what you type into the trial request form, and that becomes one email to us.
This page describes all of it. If something here is not specific enough to act on, that is a defect — say so in the trial form and we will fix the wording.
What the trial form collects
- Name
- So a reply is addressed to a person rather than an inbox.
- Organisation
- So we know whose drawings and whose standard we are working to.
- The only channel we use, and only to answer this request.
- Which of these is closest to you
- So the reply answers the question you actually have — an owner writing a specification and a bureau sizing throughput need different answers.
- Drawing source
- To tell you before the trial whether your input is in scope at this release.
- Approximate sheet count
- To size the trial against the per-conversion caps.
- Anything else we should know
- Optional. Whatever you choose to tell us.
The endpoint validates the request and relays it over SMTP to one mailbox we operate. There is no database, no queue, no customer record and no marketing platform behind the form: if the mailbox is empty, the request no longer exists anywhere.
Replying to you, and running the trial conversion you asked for. Not a mailing list, not a newsletter, not a follow-up sequence, and never passed to anyone else.
What the pages themselves do
None. The site sets no cookie of any kind — not for tracking, not for preferences, not for a session. There is nothing to consent to, which is why there is no consent banner.
None. No page-view counter, no heatmap, no session recorder, no tag manager, no pixel. We do not know which pages you read.
None. Fonts are self-hosted and served from this domain — no font CDN request carries your address to anyone. No embedded video, no chat widget, no CAPTCHA vendor, no social buttons.
The sample model, IFC file, schedules and assumptions register are static files on this domain. Downloading one tells us nothing beyond what the server log of any web request would record.
The site stores nothing in your browser. The trial form keeps your answers only in the page you are typing into; close the tab and they are gone.
The host that serves these files keeps its own standard request logs — address, URL, timestamp, user agent — for delivery and abuse handling. We add nothing to them and build no profile from them.
Spam defence, and the address in it
The form is defended by a field a person never sees and a check on how long the form was open before it was sent. Both live in our own code. We use them instead of a CAPTCHA precisely because a CAPTCHA would put a third-party runtime — and your address, and a cookie — on a page that otherwise has none.
The endpoint also counts recent requests per network address, in memory, for one hour, so that one client cannot flood the mailbox. That count is never written to disk and is gone when the function instance stops. Your address is included in the email itself so we can recognise abuse; it is not used for anything else.
Your request lives in one mailbox for as long as the conversation is useful, and we delete it on request. Reply to the email you receive from us and ask — that thread is the fastest route, because it identifies the request without you sending us anything further.
If you never receive a reply, nothing reached us: send the form again rather than assuming we hold a copy.
How you will know
If measurement is ever added it will be cookieless, it will not identify a visitor, and it will be described on this page before it is switched on (roadmap, no date). There is none today.
The footer names the product release this site describes, currently v0.6.0 . This statement is republished with the site, so the page you are reading is the one in force.