Hand-coded
At the highest level, with no site builder and no content management system. The few changes that come up later, I make myself. Every extension that isn’t there is one door fewer.
One company. No open doors. One standard.
Most people come to me when the website is 20 years old, the office PC crashes every day, and nobody remembers who has the passwords. I walk you through it and rebuild things one piece at a time.
I rebuild websites, move your mail to where it is safe, harden and monitor servers, sort out the computers in your office, and set up artificial intelligence so that you are allowed to use it. Since 1998, for companies, government agencies, and self-employed professionals.
There is very little I can’t program, repair, or solve. And you deal with one person for it, not with an agency, a web host, a mail provider, and an IT shop. I don’t have the capacity for 1,000 clients. I’d rather take on 20 who grow with me.
Doctors, lawyers, tax advisors: if German law binds you to professional secrecy, you need more from your IT provider than a data processing agreement.
A lot of medical and law offices believe a data processing agreement under Art. 28 GDPR and a mailbox at a mass-market host settle the matter. They don’t. Section 203 of the German Criminal Code requires that everyone who helps with your work is bound to secrecy and has been told that a breach is a crime. With clients under professional secrecy I sign both: the data processing agreement and the agreement under section 203.
Very few people see what that means day to day. In an ordinary mailbox your mail sits unencrypted on the provider’s server. Anyone with admin rights there, or anyone who gets hold of them, can read it: an employee as easily as an intruder. For patient files and client correspondence that is not acceptable.
The same goes for the contact form on your website. Your IT provider holds every key. If he makes one mistake, whatever your patients type into that form can be read.
When I look at a medical office from the outside for the first time, I nearly always find the same things. Patient mail sits in plain text at a mass-market host. The login codes for the hosting account go to a device that belongs to an IT contractor who stopped working for the office long ago. The sender address can be forged, because DKIM is missing and DMARC enforces nothing. DNSSEC is switched off.
Don’t wait until you have to write to every patient or client that their data is in someone else’s hands. That is the worst case for any medical or law office. I’m not a lawyer and I don’t give legal advice. I make sure the technology matches what your professional rules demand of you.
Send me your domain. I’ll tell you what I can see from the outside
I pull the content out of your old site, rewrite it, and hand-code the result. What does not exist at runtime can’t be exploited.
At the highest level, with no site builder and no content management system. The few changes that come up later, I make myself. Every extension that isn’t there is one door fewer.
The page is already built when someone asks for it, and it runs on hardened servers in the EU, not on infrastructure nobody has touched in years.
The home market has almost stopped growing. If you want customers outside Germany, you need a site they can read.
Prepared for search engines and for the language models your customers now ask before they ask a search engine.
A full set of security headers, current transport encryption, and forms nobody else can read.
Many privacy policies describe a site that no longer exists in that form. After the rebuild, yours says what the site really does.
Many of these sites are not just old. They were hacked a long time ago and nobody noticed. You get the full source code of the new site.
I rebuild every WordPress site as a static site, hand-coded. The few changes that come up afterward, I make myself.
I no longer think it makes sense to take a risk of this kind today. Every plugin can become a risk. An installation with 30 extensions from 30 developers is a bet that every one of them closes every hole in time. You place that bet again with each plugin. Roughly 4 in 10 websites worldwide run on WordPress. Which is exactly why automating attacks against it pays: find one hole and you’ve found millions of targets at once. It’s nothing personal.
How fast that happens was put on record in July 2026 by the German Federal Office for Information Security (BSI). Cybersecurity warning, criticality level 3 of 4: 2 chained vulnerabilities, together known as wp2shell, let an attacker run code without logging in. The numbers, for the record: CVE-2026-60137 and CVE-2026-63030. Publication and the first attacks were one weekend apart.
And when it happens, you don’t see it. The site loads, the contact form goes through, the dashboard reports nothing. In the background it serves malware to your visitors, hosts a phishing page in a folder you never open, or sends spam in your name. You hear about it from Google, from your host, or from a customer.
So I made a decision: I don’t maintain WordPress, I replace it. I take the text, the images, and the structure out of your existing site and rebuild it as a static site, page by page, by hand. After that your website sits on the server, finished. It is no longer assembled from a database and PHP on every request. There is no database, no login, no plugins, and nothing that needs an update at night.
If your site has already been hacked, I repair it by hand-coding it. I don’t patch the old installation. Whoever got in once has usually settled in more than 1 place, and afterward nobody can tell you for certain that everything was found. I secure the evidence and your content, check what is clean, and build the site new. The old installation goes offline, and the back doors inside it go with it.
You need to be able to change text yourself? Write and tell me what should change, and I change it. For most sites that is a few changes a year: new opening hours, a new employee, a new service. That doesn’t take a content management system with a login that sits on the internet 365 days a year. After that it is your own code, not a theme 200,000 other people bought too. You get the full source code. It belongs to you. Send me the address of your site. I look at it and tell you in writing what the rebuild involves.
I run my own name servers. I register domains, move them, and set up DNSSEC, SPF, DKIM, and DMARC. After that I monitor the mail systems.
A lot of IT providers are overloaded, and these are the records that get left undone. Without them anyone can write in your name, and the person on the other end has no way to spot the forgery.
Which mailbox is the right one depends on what is in your mail.
For clients under professional secrecy I move all mail to Proton in Switzerland. Proton works on the zero-knowledge principle: your mail is stored encrypted in a way that not even Proton can read.
Where mail does not have to be stored encrypted, I use my own mail server in the EU. I look at it every day.
Most break-ins start with a password that was already used somewhere else. 2 things help against that, and both are free.
Long, random, and used nowhere else. If one service gets hacked, only that one login is affected, and not your mailbox, your bank, and your domain along with it.
Two-factor sign-in takes 2 minutes to set up. Someone who knows your password is still standing in front of a locked door.
Your mailbox is the master key. Nearly every service sends its password reset link there. That is why I start there.
My password generator makes you a strong password you can remember, and it takes seconds. It runs on your device, and nothing is transmitted.
Most people who come to me new don’t. Their office IT is so outdated that the daily blue screen counts as normal.
On an external drive, separate from the computer it backs up.
On a drive that is not kept at the company. In the managing director’s safe, for example.
Every layer encrypted, so a lost drive is not a data leak.
I get the workstations in order and replace what can’t be saved. If programs are outdated or interfaces need extending, I do that.
The 39-euro antivirus from the electronics store catches what it already knows. I use CrowdStrike. It judges behavior on the machine and catches attacks nobody has seen before.
I train your staff online: how ransomware gets in, how to tell a forged email, and how to communicate safely with customers and with each other.
Including the accounts people rarely think about: Instagram and your company’s other social media.
That is how long my USB stick lay on a client’s cafeteria table before somebody plugged it into a company computer.
The label on the stick said "Pics 2024." The client had agreed to it, and nobody else knew. I put it on a table in the cafeteria at lunchtime and left. 17 minutes later I got the email the stick sends as soon as somebody opens it. Nobody asked whose it was. Nobody handed it in. They just wanted a quick look at the pictures.
It works nearly every time, and the reason is older than any firewall: Homo sapiens is curious. There is no update for that. The only thing that helps is for everybody in the building to see once, for themselves, how fast it happens.
I’ll gladly leave that stick on your cafeteria table too.
I show your staff how to tell a forged message, even when the sender, the signature, and the tone are right. After that I test regularly: I send emails that could be dangerous, and you see how your people react.
I explain what can happen on a visit to the wrong site: what loads in the background, what settles in, and why the computer shows no sign of it afterward.
A stick from the street or the office hallway does not go into any port. Never. Not for a second. Not even if it says "Salaries." Least of all then.
I train everybody who touches a computer, from the front desk to management: how to act day to day, online, with examples anyone can follow.
More and more often I see people open ChatGPT and paste everything in. For a doctor or a lawyer that is a disaster.
I’ll walk you into the age of artificial intelligence. And legally.
I install the programs on your employees' computers and build the structure behind them, connected to the tools you already use.
Through their APIs I connect whatever fits your job: OpenAI, Claude, or other large models such as GLM and DeepSeek. Which model may see which data is something I settle with you first.
Loading files into a US model, the way nearly everyone does, is not legal for you. With me your AI runs on German servers, contractually secured under section 203 down to the lowest level.
Then, as a lawyer, you load whole court files into your AI, have it analyze them, and have it draft your letters. As a doctor, you use artificial intelligence without giving away a secret.
And I teach you how to use AI with a clear aim, within data protection law, and safely: what to do with the answers, and how to have several agents work for you in a single session. It isn’t witchcraft. It’s structure.
One company, one standard, one point of contact.
Hardening, monitoring, early warning, and if you want it, the whole operation in EU data centers under my control. My system for this is called IPServerSec.
Your WordPress site, rebuilt as a static site and hand-coded. The few changes afterward, I make myself.
Apps for iOS and macOS, server systems, web applications, and the interfaces in between. Underneath, the infrastructure: my own name servers, my own mail server, every domain you need.
Systems, voice agents, and chatbots, wired into the tools you already use. Plus databases and vector databases, so your own material becomes searchable and not just your folder structure.
Once it’s happened: what happened, how the other guy got in, what he did while he was inside, and how you prove it afterward. Because we got hacked is not documentation. It’s a feeling.
Phone, laptop, the devices that carry half a life. The open door is rarely the server. Usually it’s the phone in your pocket.
A start that costs nothing: a separate password for every account, made with the password generator.
My everyday tool: IP Beacon shows your IP address at a glance, along with country, provider, and whether a VPN is behind it. Checked on my own server, no third parties, free and open source.
And when something has to stay confidential: encryptor.app encrypts text and files right in your browser with AES-256, and nothing is uploaded. Free, no account, also open source.
For 25 years, forensics was my work as a court-appointed expert witness.
Who’d bother attacking me, of all people?
It’s the question I hear most, and it’s fair. You have 14 employees, you sell dentures or ductwork, and nothing about your company screams intelligence service. So let’s do the math. Not by feel. By addresses.
The internet has 4,294,967,296 addresses. That’s not an estimate. That’s 2 to the 32nd. The number has been fixed since the thing was built. Your company is one of them.
In 2013, 3 researchers at the University of Michigan released a tool called ZMap. It scans all 4.29 billion addresses. From a single machine, over an ordinary gigabit line, in under 45 minutes. That was 2013.
45 minutes. That’s 32 complete passes a day from one machine. Through the entire internet. Every day. And that’s one machine.
It isn’t one machine.
Your router in Starnberg, a NASA server, and the security camera at a gas station outside Rosenheim sit on the same list and get counted off in the same second. The scanner doesn’t know what NASA is. It knows that port 22 answered.
That answers your question, just not the way you asked it. Nobody picked you. Your number came up.
Calculated from the daily average of 46,000 serious attacks: one every 1.9 seconds. The number keeps running while this page is open.
I keep count. Across my whole server fleet, an average of 46,000 serious attacks land every 24 hours. Serious means the background noise is already subtracted out. No harmless scans, no search engines, no misconfigured printers in Ohio. 46,000 attempts by somebody who wants something.
That’s one every 1.9 seconds. In the time it took you to read this section, there were 32.
You’re not attacked because you’re interesting. You’re attacked because you’re reachable. That’s not a verdict on your company. That’s a loop.
What in that flood affects your systems today is in the Threat Log. Checked daily and assessed.
Server protection I wrote myself.
IPServerSec is my hardening and early-warning system for Linux servers. Not a plugin I bought, not a subscription. It grew over years out of real attacks on real servers. It runs on my entire fleet and on my clients’ systems. It gets tested on me, and the 46,000 from further up is the log of those tests.
It blocks, it detects, it alerts, and it logs. That last one is what everybody underestimates. When it counts, nobody asks whether you had a protection system. They ask whether you can prove it. The gap between those questions is roughly one insurance payout.
They get sorted. Some get a few hours of blocking and are gone again. The second group is the interesting one: the same networks, over and over, for weeks, the same signature, often the same time of day. Mostly they belong to big providers overseas that rent out servers by the tens of thousands and never get around to checking what’s running on them.
When the same attack comes out of one of those networks for the 3rd time, I don’t block the address. I block the network. For 10 years.
If my abuse reports go unanswered and an operator is unaware of his responsibility, I decide for him.
That’s the whole point: a rule set somebody writes for your server. Not a default a vendor wrote once for everyone.
So nothing comes off the rack. Every server gets its own rule set, built from your real traffic, because a mail server needs different rules than a store, and a database server needs different ones than a VPN gateway.
There is no such thing as absolute security. Anyone selling it to you is selling you something else.
My servers are monitored and attacked by artificial intelligence. Around the clock, all of them.
I call the guards Sentries. 3 of them work around the clock. Several times a day they test each server for a way in and compare the installed software with the newly published vulnerabilities. When a vulnerability appears, the Sentries respond together with IPServerSec and patch the systems. If there is a problem, I get a text message, on a weekend at 10 p.m. too.
Ask an ordinary ChatGPT or Claude to test a system inside and out, and the answer is: I won’t do that. As a security company I have access to the largest language models under a clearance that permits exactly this work.
With a written contract in place, I use them to test your company, your website, and your code too. At full force. Hardly any IT provider can offer you that.
I attack other people’s systems only under a written contract with the party entitled to order it.
For the details, see how the AI checks with IPServerSec work.
The best forgery I’ve ever seen came from a managing director who never wrote it.
A few days ago, an employee at a client of mine got an email. Sender: her managing director. Name correct, cell number in the signature correct, the layout an exact copy, down to the font size. It addressed her personally, by name. It asked for the current account balance.
It wasn’t the managing director. It was someone who had first pieced together who talks to whom inside that company, how people there write, and who answers whom without asking twice. In 25 years I’ve seen hundreds of forged messages. This one was the best.
Your spam filter would have let it through too, because technically there was nothing wrong with it. No attachment, no poisoned link, no crooked sender address. Just one sentence meant to get somebody to do something. Anything that only looks for malware never finds this.
A free mailbox isn’t a service somebody runs for you. It’s a shelf your mail gets put on. Nobody there knows your name, nobody checks, and when it matters, what you reach is a web form with nobody behind it.
I don’t send confidential data to a free mailbox. Not to anyone. It would be like sawing off the branch I’m sitting on. A medical office, a law firm, a business with personnel files behind an address like @cheap.xxx shows me where to start before I’ve read the first line. Health data is a special category under Art. 9 GDPR, professional confidentiality carries criminal liability in Germany under section 203 of the Criminal Code, and Art. 32 GDPR requires appropriate technical measures in so many words. That goes for physicians, law firms, tax advisors, psychotherapists, and anyone with personnel files sitting in a mailbox.
The question of who actually runs your mailbox, and who looks inside it, is one you will be asked when something goes wrong. Not by me, but by a supervisory authority.
Try something. Open your mailbox and scroll all the way down, to the oldest message. For most people the year down there still starts with 201. 10 years, 15, for some of you more.
What piled up in that time has never been looked at all at once. Invoices and contracts. Bank statements somebody sent you because it was quicker that way. Job applications with a résumé and a date of birth. Sick notes from employees. Customer lists attached as a spreadsheet. The correspondence with your lawyer, your tax advisor, your bank. And somewhere in there, login details in plain text, because one time it had to be fast.
Most of it isn’t yours. It’s other people’s data, sent to you because they trust you.
Then there’s the part almost nobody accounts for: your mailbox is the master key to everything else. Almost every service lets you reset the password, and the link for it arrives by email. Online banking, the tax portal, your ERP system, cloud storage, domain management, social security. Whoever has your mailbox doesn’t need your other passwords. He has them sent to him.
And here is how it actually plays out. The attacker takes nothing and deletes nothing, because that would get noticed. He reads along. For weeks. He learns how you write, who answers you without asking twice, which invoice is outstanding and who it goes to. Then he writes once, in the right thread, in the middle of a live conversation, in the right tone. That’s where the forgeries nobody catches come from: real messages that somebody had been reading first.
What tips you off is something small. A client replies to something you never wrote. A payment goes to an account you don’t recognize. By then it has usually been going on for weeks.
From that moment it stops being an IT problem and becomes a matter with deadlines. Unauthorized access to a mailbox that holds personal data has to be reported to the supervisory authority within 72 hours (Art. 33 GDPR). Where the risk is high, you also have to notify every affected person yourself (Art. 34 GDPR). In plain terms: you write to your own clients, your applicants, your staff, and tell them their data is in someone else’s hands. That one message is what people will remember about how carefully you ran things, and it travels through your industry faster than any advertising you ever paid for.
And then the question that decides everything: what exactly had you done to prevent it? A free mailbox, a host for 2 euros a month, a password you also use at an online store, and no second factor, even though it costs nothing and takes 2 minutes to set up. Under section 43 of the German Limited Liability Companies Act, management owes the care of a prudent businessperson, and appropriate IT safeguards are part of that. This is exactly the setup where gross negligence gets argued, and that can mean an insurer declines to pay and liability becomes personal.
The order of things is almost always the same: first the sentence that this can’t be possible, then the question of how long it has been going on, and then the silence when somebody works out how many people have to be told.
So I run my own mail server, in the EU, under my control. For clients under professional secrecy it stays with Proton, as described above. vipmail is for everyone whose mail does not have to be stored encrypted. Every incoming message goes through several checks that are independent of one another.
It starts with the question of whether the sender is even allowed to be who he claims to be. SPF, DKIM, and DMARC are set up here for every domain and every account. No exceptions. That’s what makes your own mail arrive at the other end, and what makes forgeries in your name fall apart.
On top of that: public blocklists, for senders and for the addresses a message links to. Filtering software that scores the content. And a stage of my own, where a language model reads the message and judges whether it’s an attempt at fraud. That stage is what catches an attack like the one above, because it doesn’t look at the sender address, it looks at the intent in the text.
The language model never sees personal data. Names, addresses, phone numbers, account numbers, and file references are stripped out first. What gets judged is the structure and intent of a message, never the people in it. If that redaction fails even partly, the check is skipped entirely. I would rather let a message through unchecked than let content leave this house.
Underneath all of that sits the protection of the server itself. 8 separate guard posts watch who tries to log in, at which service, how often, and how fast. 3 wrong tries and you’re out, automatically, in seconds. Above them sits IPServerSec, which blocks not just single addresses but entire network ranges belonging to providers that attacks keep coming from. Right now that’s 3,765 networks holding more than 306 million addresses that can no longer reach this mail server. The list grows daily.
Your data is backed up to 3 separate systems, hourly instead of daily. If something does happen, worst case you lose an hour, not a working day.
And then the part no software replaces: I read the logs by hand, every day. What got through, what got held, what should have been held, where a rule was too sharp. That’s how the system gets a little better every day. Here, somebody looks every day, and he knows your name.
I follow the rules that govern mail on the internet, strictly, and I enforce them. A server with no SPF, no DKIM, no DMARC, and no matching reverse DNS record doesn’t get in. Those gaps are exactly the opening forgeries come through: someone who can’t prove he’s allowed to send is indistinguishable from an attacker.
Nobody is left in the dark about it. The sender gets a reply in plain language stating what his server is missing and what his administrator has to fix. Anyone who fixes it can deliver again, not just to me but to Google and Microsoft, who have been asking for the same thing for years. I’m not strict. I’m just early.
There is no such thing as complete security. I’ve set the bar very high, and it ends with you. A call to the number in your own address book, not the one in the signature, has already stopped a great many five-figure transfers.
Every mailbox here comes with two-factor sign-in. It costs nothing, it takes 2 minutes, and after everything above it is the cheapest thing you can do for your business today. Add a password you use nowhere else. A strong password you can actually remember takes seconds to create with the password generator.
I handle the move: MX records, DNS, exporting the old mailboxes, setting up your devices. Best case you notice none of it, except that from day one somebody is watching.
The most expensive code is the code that was easy to write.
A language model will write you a login form in 20 seconds. In the same 20 seconds it writes the hole in too. It doesn’t tell you, because it doesn’t know. Ask it afterward whether the code is secure. It’ll say yes. It always says yes.
It feels productive. It looks like it works. And almost every time, something comes out of it that none of the people involved can see.
One hole in an application like that is rarely the end of it. Whoever gets in doesn’t stop at the one page. He works his way sideways, through every application and all the data on the same server. If that server also hangs off the company network, this stops being a website problem. Now it’s a company problem.
Somewhere in the 3rd hour in front of a hacked machine, I understand how the other guy was thinking. Some of these attacks are lean, nested, with one move that only occurs to someone who understood the system better than the people who built it. Then I look up who it was. And he’s 16.
I use the same models as the people who built your application. The difference is 42 years of seeing where those models get it wrong. And a review before anything goes live.
You’ve been hacked. Or you want to know whether you have.
I secure servers before anyone gets in, and I reconstruct the case when someone does. I also build the software that runs on them. Since 1998, for companies, government agencies, and self-employed professionals, anywhere in the world.
Most people who come to me after a break-in didn’t notice it themselves. They heard it from Google, from their hosting company, or from a customer who asked why the company website is now selling erectile dysfunction pills.
If it’s already happened, order matters. Secure the evidence first, then close the hole, then clean up. Whoever cleans up first deletes exactly the thing that was supposed to prove, 2 weeks later, that he wasn’t negligent.
If it hasn’t happened yet, you’re in the better position, and the considerably cheaper one. Prevention doesn’t mean installing a product and hoping. It means hardening and watching systems closely enough that an attack shows up while it’s running, instead of when the host pulls the plug.
Write and tell me what’s going on.
If the affected site runs on WordPress, I repair it by hand-coding it. How that works is under I move you away from WordPress.
Companies, law offices, and medical offices face a task that has never come at this speed. Whoever takes it on now has it behind them before it turns into a problem.
The situation has gotten a good deal worse. Your website, the way you communicate with customers, and the way your employees communicate with each other are what I set up again with you, with a clear structure, one piece at a time.
Don’t think this costs nothing. I’d be lying if I told you that. But compared with what an outage or a data leak costs, these costs are small. I walk you through it, at a fair price.
And afterward you can show that you did what was possible. When something happens, that is exactly what your insurer asks.
A lot of medical and law offices believe a data processing agreement under Art. 28 GDPR settles the matter. It doesn’t. Section 203 of the German Criminal Code requires that everyone who helps with your work is bound to secrecy and has been told that a breach is a crime. With clients under professional secrecy I sign both: the data processing agreement and the agreement under section 203. I’m not a lawyer and I don’t give legal advice.
In an ordinary mailbox, mail sits unencrypted on the provider’s server. Anyone with admin rights there, or anyone who gets hold of them, can read it. For clients under professional secrecy I move all mail to Proton in Switzerland. Proton works on the zero-knowledge principle: the mail is stored encrypted in a way that not even Proton can read. Where mail does not have to be stored encrypted, I use my own mail server in the EU.
Without these records anyone can write in your name, and the person on the other end has no way to spot the forgery. I run my own name servers, register domains, move them, and set up DNSSEC, SPF, DKIM, and DMARC. After that I monitor the mail systems.
Loading files into a US model, the way nearly everyone does, is not legal for anyone bound by professional secrecy. With me, the AI for clients under professional secrecy runs on German servers, contractually secured under section 203 down to the lowest level. Which model may see which data is something I settle with you first. I’m not a lawyer and I don’t give legal advice.
I pull the content out of your old site, rewrite it, and hand-code the result, with no site builder and no content management system. The few changes that come up later, I make myself. What does not exist at runtime can’t be exploited. Every extension that isn’t there is one door fewer. The site runs on hardened servers in the EU, in German and English, prepared for search engines and language models. You get the full source code of the new site.
I repair it by hand-coding it. First I secure the evidence and your content, because whoever cleans up first deletes exactly what was supposed to show later what happened. If the site is doing damage right now, have it taken offline, for example by your host. Then I build the site new: static, by hand, with no database, no login, and no plugins. I don’t patch the old installation.
You don’t have to. You write and tell me what should change, and I change it. For most sites that is a few changes a year, and that doesn’t justify a content management system with a login that sits on the internet around the clock. You still get the full source code. It belongs to you, and it keeps you independent of me.
In 4 steps: you write to me, I look at it, you get a written quote, I do the work. The first message commits you to nothing, and you are billed only for what you commissioned in writing beforehand.
You write and tell me what things look like on your end. The first message commits you to nothing.
I look at what is there and tell you in writing what is needed and what isn’t.
You get a written quote. You know what it costs before it starts.
I do the work. You are billed only for what you commissioned in writing beforehand.
I’m interested in partnerships that last for years. I grow with my clients, and my clients grow with me.
Write to me. I’ll walk you through it
CrowdStrike, Proton, ChatGPT, OpenAI, Claude, GLM, DeepSeek, and WordPress are trademarks of their respective owners. I do not claim a partnership with any of them.
My clients call me George.
I’m George A. Rauscher, founder and managing director of intelligent piXel GmbH in Starnberg, Germany.
The one door that’s supposed to be open.
You write to me, and the person who reads it is the person who fixes it. There is no phone number. After that it goes in order and in writing: I look at it, you get a quote, I do the work.
The fastest way to ask a first question with no obligation is Telegram. Telegram is operated by a provider in the United Arab Emirates. There is no adequacy decision for it under Art. 45 GDPR. For confidential or personal information, use the contact form or email.
Anonymous first inquiries are welcome, on Telegram or by email. To answer by email I need an email address, and it doesn’t have to say anything about you. The form asks for your name and does not accept messages sent over a VPN.
Telegram: @intelligentpixel
Email: my@intelligent-pixel.com
Based in Starnberg near Munich. I work for clients in Upper Bavaria, across Germany, and internationally.