Full disclosure
Last updated August 24, 2026. What we collect, what we claim, and the things most sites bury. If anything here is unclear, ask us and we’ll fix the page.
The short version. We don’t track you. There are no analytics and no ads on this site. The only cookie we set is the one that remembers if you picked light or dark mode, and we only set it if you click the button. The Google map is the one outside thing here. If you use the contact form, we do collect a fair amount of technical detail along with your message. That’s the part worth reading below.
1. What the contact form collects
When you press send, two sets of information go along with your message. Nothing is collected when the page just loads. We think you should know exactly what those are, because most contact forms do this quietly and never say so.
Read from your connection (dependable)
Our host tells us these about the message itself. They can’t be faked from your end, and we never read them out of what you typed:
| What | Why it’s there |
|---|---|
| IP address | Tells us roughly where a message came from, and lets us block a source if we get flooded. |
| City, state, country, ZIP area | Rough guess based on the IP, not your device’s location. Often off by quite a bit. |
| Timezone | So we don’t reply at three in the morning your time. |
| Internet provider | Which provider or company network the message came through. |
| Data center | Which of our host’s data centers handled it. Only useful for fixing problems. |
| Timestamp | When it arrived, in UTC. |
Reported by your browser (take with salt)
Your browser offers these up on its own. You can change or turn off any of them, and nothing here breaks if you do:
| What | Why it’s there |
|---|---|
| Device type, platform, browser | If you tell us something looks broken, this saves a round of “what are you using?” |
| Screen and window size | Same reason. Most “it looks wrong” reports get solved by this one line. |
| Timezone and UTC offset | Cross-checks the one above. |
| Languages | So we reply in one you read. |
| CPU cores, memory, touch support | Context if you’re reporting something slow. |
| Referring page | Tells us how you found us. Blank if you typed the address. |
| User agent string | The long version of the browser line. |
Being straight with you
Put together, that’s a fairly specific picture of your computer. We collect it because it makes answering a technical question much faster, and because it helps us tell a real person from the steady drip of spam. We’re not going to pretend it’s nothing.
It arrives as an email in one inbox. We don’t put it in a database. We don’t build a profile from it. We don’t sell it or share it with anyone. It lasts as long as the email does. Ask us to delete your message and we will, and we’ll tell you when it’s done.
If you’d rather not send any of that, just email us directly instead of using the form. A regular email carries only what your own mail app sends, which is a lot less.
2. Cookies and storage
One, and only if you ask for it:
- Light or dark mode. Click the button and we save your choice in your browser, plus a cookie that lasts a year. Never touch the button and we never save anything. That’s the whole list.
No analytics, no advertising, no tracking pixels, no session recording.
The one thing here that isn’t ours is the Google map. It loads with the page, and Google may set its own cookies when it does. That part is between you and Google. We don’t see any of it.
3. Where we stand on certification
The front page lists ISO/IEC 20000-1, 27001 and 42001 as standards we’re working toward. To be completely clear: we are not certified in any of them yet. We’re doing the groundwork. That’s real work, but it is not the same as a certificate.
You won’t see a certification badge here, and that’s on purpose. ISO doesn’t let anyone use its logo to show certification. The badges you usually see belong to the company that ran the audit, and they’re only allowed while a certificate is active. Showing one before then would break the rules and, worse, mislead you. When we pass, this page and the front page will list the standard, the certificate number, who issued it, and the date.
4. How we use AI
An AI helper wrote most of the first draft of this website. A person reviewed every line. The “How we built this” section on the front page goes through what it got right and what it got wrong, in detail, including the mistakes.
In client work, the rule is the same one we apply to each other:
- What the AI writes is a draft, never a finished answer. A person reads all of it before it goes near your systems.
- We’ll tell you where we used it. If you’d rather we didn’t on your job, say so and we won’t.
- We never paste your passwords, personal data, or customer data into outside AI tools.
5. Things we’ve left out elsewhere
- “Two engineers” means what it says — two people on the work. It doesn’t mean both of us sit there for every hour of it. It means neither of us ships a change the other one hasn’t read.
- The numbers on the front page describe how we work. They are not measured results. “Bus factor: 2” just means two of us are on your job. It isn’t a score, and we haven’t dressed it up as one.
- We’re small. If a job needs ten people, we’ll tell you instead of taking it and hoping. We’d rather point you somewhere better and stay someone you’d call again.
- No customer reviews on the site. When there are, they’ll be from real named customers who said yes. We won’t make any up.
6. Getting in touch about this page
Corrections, deletion requests, or a question about anything above — use the contact form or email us directly. A person will answer.
If we ever change something important here, we’ll update the date at the top and say what changed.