Valeur.This site has one form. Almost all of this notice is about it.
The pages are served as flat files: no cookie is set, nothing is written into your browser, no request goes to a third party. Personal data appears at one point only — when you fill in the pricing form and send it. Below is every field that form carries, what the server adds to it, and where each of those goes.
This notice describes what this site’s own code does, and it was written by reading that code. What the providers this site runs on record on their own side is beyond what this code can see; their part has its own heading below.
Thirteen rows: you fill in ten, two are added on the way, one you never see.
The left-hand column is the same wording the form shows you — this table is copied from the form rather than rewritten. The order is the order the fields are written into the email, so you can read the email and this page side by side. Two fields are required: Business email and Name. Everything else is optional.
- Which side of the contract are you on?
- One of five options. Which side you are on decides where the first conversation starts.
- Which band is the contract sum in?
- One of four bands. The option is the name of a range; what is written into the email is that name, rather than an amount.
- Which heading should be opened first?
- As many of five headings as you like, including none of them. The names of the ones you tick are written into the email as one line.
- Business email
- Required. The address a reply goes to; it is also set as the email’s reply address, so a reply comes straight back to you.
- Country
- Optional, free text. It helps work out which legal tradition the contract will be read in.
- Name
- Required. So that a reply can address a person.
- Company
- Optional. If it is filled in, it also appears in the email’s subject line.
- Title
- Optional. Who is asking changes what the question is.
- Phone
- Optional. For anyone who would rather talk than write; left empty, the reply comes by email alone.
- Project type
- Optional, free text. What is being built changes which contract form the conversation is about.
- Country code (from the connection)
- A two-letter country code. The hosting network derives it from your connection and the server adds it to the email as one line. It is a country: not a location, a city or an address.
- Browser identification line (from the connection)
- The identification line your browser sends with every request. It is added to the email and it does one thing: it tells an obviously automated submission from a person’s. A long one is clipped.
- One field you never see
- The form carries a text box nobody can see; a person leaves it empty and an automated submission that fills every input fills it too. Arriving filled, the submission never becomes an email and what was in the box is written nowhere. The reason this row exists is simple: a list that counts twelve of thirteen fields is a list with a secret in it.
The table was read from the form and the sending code themselves. The heading of ten of the thirteen rows is a copy of the wording the form shows, and their order was checked one by one against the order the fields are written into the email.
One email, one inbox.
Sending the form does one thing: the fields above are written into a plain-text email and it goes to the company’s contact address. No account is opened along the way, no profile is built, no record row is written.
One email
The fields are written into one plain-text email and sent, through a mail provider, to the company’s contact address. The address you gave is set as the email’s reply address, so a reply comes straight back to you rather than anywhere else.
That inbox is the only place it is kept
This site’s own code writes to no database and keeps no copy after delivery. From then on your enquiry lives where an email lives: in the company’s mailbox, for as long as an enquiry is useful. It is deleted when you ask.
Your IP address is never written into the email
To thin out repeated submissions from one connection, the address is put through a one-way digest; only that digest is held, for about a minute, as a key. The address itself is neither written into the email nor stored anywhere.
The consent box is read in three places
The box you tick is read in the page’s own markup, in the script on the page, and once more on the server. A submission that never met this text never becomes an email. That box is also the basis for the processing: your explicit consent.
Withdrawing your consent is the same act as making a request: one line to the address below is enough. Withdrawal changes what happens next rather than what already happened.
Three sentences, all three written after counting.
This is the easiest section of a privacy notice to write, and it usually comes from a template. Each of the three sentences here was measured by scanning the source files before it was written — because a template describing a cookie nobody sets is the kind of sentence this site stops a build over.
No cookie is set
No page here sets a cookie or writes to browser storage. That is why you were never shown a cookie banner: there is nothing to consent to.
The typefaces come from this domain
Every typeface on these pages is served from under this domain. Because no request goes to a font service, no font service sees that you opened this page.
No counter, no tracker
No request leaves this domain from this page: no analytics, no tag manager, no embedded video, no share button. The source does mention schema.org, but that is the name of a vocabulary rather than an address the browser calls: it states which vocabulary the structured data uses. So there is no third party that knows you opened this page.
All three were measured by scanning the page sources and the stylesheets. Read the result together with the next heading: your browser connecting to this site still leaves a trace somewhere.
Four providers keep records of their own.
This site is served through Cloudflare; the form’s email is sent by Resend; the email that arrives sits in the corporate mailbox at Zoho Mail; the domain is registered with GoDaddy. The four do not see the same thing: your connection passes only through the first two, and those keep the kind of records any server keeps — which address connected, what was asked for, and when. Zoho Mail holds the email the form produced for as long as it stays in the mailbox; GoDaddy never sees your visit, what sits there is the domain registration. Those records sit in their systems under their own terms; this site’s code can neither read them nor erase them. That is written here as the place our promise ends rather than as a reassurance.
Resend is in the EU (Ireland) and the Zoho Mail box is in the EU; Cloudflare is a distribution network, so the page is served from a point near you rather than from one country. These four names are stated by the controller; the page itself does not prove them. Each publishes its own privacy terms on its own site.
What you can ask for, and where to write.
You can ask what is held about a form you sent, ask for a copy of it, ask for it to be corrected, or ask for it to be deleted. The request goes to the same place the form goes: one inbox that a person reads.
What is held, and a copy of it
The only thing held is the email you sent, so the copy is that email. Your address is searched for and whatever is found is sent to you.
Correction
If you filled a field in wrongly, sending the right value is enough; the correction sits in the same thread, in the same mailbox.
Deletion
A deletion request means the thread is removed from the mailbox, and no copy is looked for anywhere else, because no copy is made anywhere else.
For requests, and to withdraw consent: info@valeurtechnology.com
Valeur Technologies Ltd (in formation) · Istanbul · info@valeurtechnology.com