Privacy
What this website collects, what it does not, and what it does with a visitor's analytics choice.
- Last updated
- Other documents
- Terms · IP & Confidentiality · Cookie policy
Contents
This page describes what the Seimora Group website does with information about the people who visit it.
What this page covers, and what it does not
It covers this website as it is built today. It is not a complete data-protection notice: it does not identify the legal entity acting as controller, give a contact route for a data-subject request, state where data is stored, or name the company that will carry its email, because those are not settled facts. Rather than publish a guess at any of them, they are absent. Nothing described below depends on them.
There is no account, and no contact form other than the quote intake
This site has no login and no newsletter. The only thing you can submit is an enquiry through the quote intake, and everything it collects is described below. Files can also be added to an enquiry already on file, from the private link in its acknowledgement email; that page takes files and nothing else. Every other page is read-only.
What the quote intake collects
Submitting an enquiry sends us the answers you typed: your name, your email address, an optional phone number, your company, and a structured description of the job — where the steel is going, what the scope is, the tonnage band, the governing code, the software, and the dates. It is used to answer your enquiry and to do the work if you instruct us, and for nothing else.
If you upload files, they go directly from your browser to encrypted object storage rather than through this website. They are scanned before anyone here can open them, and every read of an uploaded file is logged — who, when, and which file.
Before any upload is possible you are shown a confidentiality acknowledgement and asked to accept it. Accepting records the time, the network address the request came from, your browser's user-agent string, and the version of the text you were shown. That record is kept with the enquiry, which is the point of it: it is evidence of what was agreed, and when.
The full terms covering your models and drawings are at IP and confidentiality.
How long an enquiry is kept
An enquiry and its uploaded files are retained for 24 months after the project closes, and then permanently deleted.
"Project close" means the enquiry did not convert — it was marked lost, declined, or expired without a response — or the work it led to was delivered and formally closed out. A live enquiry is not deleted on a timer, however old it is; the clock starts when it closes.
Two things are kept beyond that and are named here rather than left implied. The business record that an enquiry existed — its reference number, the company and the date — is retained as an ordinary business record, because a reference number has to keep meaning something. Ordinary web-server request logs are covered separately below.
Analytics, only if you accept it
A consent banner appears on a first visit. Nothing non-essential loads until you answer it, and that is enforced in code rather than promised: the analytics script is requested only when consent has been granted and an analytics provider is configured. Decline, and no analytics script is loaded, no request is made to an analytics provider, and no identifier is created.
The analytics this site is built to use is cookie-less and aggregate — page views, referrers, and coarse device and country information derived from the request itself. It does not set a cookie, does not follow a visitor between sites, and does not build a profile.
What is kept in your own browser
Answering the banner writes a single value — granted or denied — to your
browser's local storage, under the key seimora-consent. It stays on your
device, it is never sent to a server, and clearing site data for this domain
removes it and brings the banner back.
Two further items exist while you are filling in the quote intake, and both are named here because one of them holds your contact details. A part-finished enquiry is saved as you type it — your company, your name, your email address, your phone number if you gave one, and your description of the job — so that an accidental refresh does not lose it. Alongside it, any file you are part-way through uploading is recorded by filename, size and last-modified date against the identifier of the unfinished upload, so that a reload does not restart a large file from zero.
Both live in session storage, which belongs to the single browser tab and is discarded when that tab closes; neither is sent anywhere by being stored, and the draft is deleted once the enquiry is sent.
Four more items contain nothing that identifies you. Two are display preferences, kept in local storage so they last between visits: whether you chose the light or the dark drawing space, and whether you chose SI or imperial units. Two are markers in session storage that last only as long as the tab: one records that the home page has already been loaded, so its opening animation does not replay, and one that its short "Before you go" note has already been shown. None of the four is sent anywhere.
The cookie policy lists all seven keys, what each holds and how each is cleared, and a test in this site's codebase fails the build if a storage key exists that the cookie policy does not name.
Email about your enquiry, and the provider that carries it
Submitting an enquiry produces two messages: an acknowledgement to you, with your reference and a private link for attaching further files, and an internal notification to the estimating mailbox, which carries a summary of your answers and a signed, expiring download link for every file you uploaded.
Sending email means handing those messages to a third-party email provider, which necessarily sees what is in them — your contact details in both, and the download links in the internal one.
That provider has not been chosen, so this page does not name one. The site ships an adapter for one such service and the seam for others, but no sending account exists yet, and until a deployment is configured with one, no message is delivered at all. When the choice is made, the provider will be named here, because a named recipient of your contact details and of links to your drawings is exactly what this page exists to disclose.
Error reports
When a page fails, this site can send a technical error report — the URL, the browser, and a stack trace — to an error-monitoring provider so the failure can be fixed. That reporting is inactive unless a provider is configured, and it is separate from the analytics choice above, because it is about the site working rather than about measuring visits.
Request logs
The service hosting this site records ordinary web-server request logs: IP address, time, the page requested, and the browser's user-agent string. Any site on the public internet produces these; they exist to serve the page and to defend against abuse.
Changes
This page changes when the site does. The date at the top is the last time it was revised.