Privacy
A one-page site collects little. Here is all of it.
This site is a static page: no accounts, no sign-up, no server of ours watching you read it. Two things can carry data away from your browser — the contact form, when you press Send, and Google Analytics, only after you accept it in the banner. Two more stay on your device: the language you picked and your answer to that banner.
This page lists each of them, where it goes and for how long. It is written in plain terms because the list is short enough to be.
What goes where
One table instead of a policy
Everything that leaves your browser is in this table. Nothing on the page loads from a third party except the analytics tag, and that one waits for your answer.
| What | Where it goes | When |
|---|---|---|
| The contact form — your name, company, work email, the message and the engagement model you picked | To one row of a spreadsheet on our Google account, and by email to our mailbox. An engineer reads it. | When you press Send, and only then. Nothing is sent as you type. |
| The project brief — company, name, work email, and your answers about the system, its load, stack, budget and timing | The same spreadsheet, on its own sheet, and the same mailbox. The same engineer reads it. | When you press Send the brief, and only then. While you fill it in, the draft is kept in this browser’s local storage; nothing leaves your device until you send. |
| Analytics — the page you opened, your browser and device class, your country from an anonymised address | To Google Analytics, on our account | Only after you accept in the banner. Declined or unanswered, the tag sends nothing and sets nothing. |
| The language you chose | A cookie on this device, read by this site alone | When you pick a language in the menu, or the site opens in the one your browser asks for. |
| Your answer to the analytics banner | This device’s local storage | When you answer. It is why the banner does not ask twice. |
| Fonts, images, scripts, styles | Nowhere — they come from our own server. The one exception is below. | Always. No content network, no font service, no tracking pixel. |
| reCAPTCHA — a signal about how your browser behaves on the form, computed by Google | To Google, which tells our receiver whether the sender looks like a person | Only once you start filling in a form, and only while the site has a reCAPTCHA key; a page you read without touching a form makes no request to Google. |
The addresses of the mailbox and the analytics account are ours. No data on this page is sold, rented or handed to an advertiser.
The contact form
What we ask for, and what we do with it
The form exists so that an engineer can answer you in writing. It asks for what that needs and nothing more.
Name, company, work email, the message
Name and email so we know who is writing and where to reply; the company and the engagement model so the right engineer reads it. The message is yours to word — a sentence is enough.
The project brief, the same way
The brief at /brief asks more — the system, its load, stack, budget and dates — and goes to the same place: a row of the spreadsheet and an email to the same mailbox, read by the same engineer. Everything on this page about the form applies to it. Its draft is saved in your browser as you type, so you can come back to it; it is removed from there the moment you send it, or when you press “Send another brief”. Only the questions marked are required, and a blank is an answer too.
Read by a person
An engineer reads it and answers within three business days. The only software in between is a spam check — a hidden field, a minimum fill time, Google’s reCAPTCHA score — that drops obvious bots; there is no scoring of you, no automated sequence, no follow-up campaign. You get one written reply, then a conversation if you want one.
Kept as long as the conversation
Your message — the row in the spreadsheet and the email — stays with us while we are in touch. If nothing comes of it, both are deleted within twelve months of the last exchange. If it turns into an engagement, the contract says what is kept and for how long.
Stays in the EU
The mailbox that receives your message is hosted in the European Union, and we do not move it elsewhere. The spreadsheet lives in our Google Workspace account, where Google processes it on our behalf under its data-processing terms; nobody outside the company can open it.
NDA on request
If what you need to describe is confidential, ask for a non-disclosure agreement first and send the detail after it is signed. The form is fine for the outline.
The form is not the only way
Everything above applies equally to an email you send yourself. Write to [email protected] and the same engineer answers.
Analytics
Off until you say otherwise
We count visits to know which sections people read. Google Analytics 4 does that; it does not run until you accept.
Denied by default
The tag loads with consent set to denied — no analytics cookie, no advertising signals, nothing stored — and stays that way until you press Accept. Decline and the page remembers that instead.
What Google receives
Which page you opened, roughly when, your browser and device class, and your country, derived from an address that is anonymised before it is stored. No name, no email, no form contents — the form is not measured.
Change your mind here
The switch below shows your current answer and lets you reverse it at any time. Withdrawing consent stops the tag on this device from that moment; it does not reach back into what Google already counted.
Google’s own terms
Google processes the data on our behalf under its Google Analytics terms and data-processing agreement. We do not share the account with anyone else, and advertising features stay switched off.
Your analytics answer on this device
What we don’t have
A shorter list than usual
Most privacy pages are long because the site does a lot. This one does not.
Accounts
There is nothing to sign up for, so there is no password, no profile and no account to delete.
Advertising and tracking pixels
No ad networks, no retargeting, no social-media buttons that report back. Google Analytics waits for your consent; reCAPTCHA loads when you start a form and tells us only whether the sender looks like a bot.
Third-party assets
Fonts, images and code are served from our own host. Two things come from Google and nothing else does: the analytics tag, which waits for your consent, and reCAPTCHA, which loads only when you start filling in a form.
Cookies beyond one
The language cookie is the only one we set. Your banner answer sits in local storage — as does a brief you have started and not yet sent — and the analytics cookie exists only if you accepted.
Data for sale
Nothing on this page is sold, rented, exchanged or used to build a profile of you.
Your rights
Ask, and an engineer answers
The same address as the form. No ticket system, no identity theatre — a reply from a person.
See what we hold
Write to [email protected] and we tell you what we have — usually the messages you sent us and nothing else.
Correct or delete it
Ask and it is done: a wrong email fixed, a conversation erased. Deleting is not a process; it is a message.
Object or withdraw
Analytics consent is withdrawn with the switch on this page. Anything else — say so in the same email and we stop.
Complain
If you are in the EU and believe we have handled your data wrongly, you may take it to the data-protection authority of your country. We would rather hear it from you first.
Who is behind this site
One company runs it, one address for questions
The site is run by ALTESSA SOLUTIONS INC., 1021 E Lincolnway Suite #6920, Cheyenne, Wyoming 82001, USA — the company in the copyright line, and the one that answers for everything described on this page. The engineers who read your message work at its Serbian company, ALTESSA SOLUTIONS SER doo, Trg Nikole Pašića 5, 11000 Belgrade, Serbia, named beside it in the footer. Questions about this page go to [email protected]. If the page changes, the date below changes with it.
Questions
The short answers
One of ours: the language you chose, so the site opens in it next time. The analytics cookie exists only after you accept the banner, your banner answer is kept in local storage, and reCAPTCHA may set Google’s own cookie once you start filling in a form.
To one row of a spreadsheet on our Google account and to our mailbox, hosted in the EU, when you press Send. A spam check turns away obvious bots — a hidden field only a bot fills, a form sent within seconds, a message that is mostly links — and that is all any software does with it: an engineer reads it, nobody scores you or adds you to a list. The project brief goes the same way, on its own sheet.
Yes — email [email protected]. Everything on this page applies the same way.
With the switch on this page. It reverses your answer on this device immediately.
No. It goes to the engineer who answers it and stays inside the company. If an engagement follows, the contract governs from there.
Last changed: 20 September 2026