Is your data safe? Website and automation security, without the jargon

Short answer: yes. Your site runs on Vercel and your data lives in Supabase. Both are independently audited to SOC 2 Type 2, encrypt everything while it travels and while it sits at rest, and keep your accounts in your own name. This site also never tracks you, so it never has to ask you to accept cookies. Below is the version without the jargon.

Where your data actually lives

I don’t keep your information on my laptop or on some server only I can see. Your website is hosted on Vercel, and if your project needs a database, it lives in Supabase. Both run on top of Amazon’s data centres (AWS), the same infrastructure a large share of the internet sits on.

Two plain facts about both: they’re independently audited to SOC 2 Type 2 and ISO 27001 (outside experts check their security every year and publish the result), and every piece of your data is scrambled both while it travels and while it’s stored (AES-256 encryption, the same kind banks use).

And the part that matters most for you: the accounts are in your name. You own them. If we ever stop working together, you keep the keys and I walk away with nothing of yours.

Why this website is hard to break into

The pages you’re reading were built with Astro, and they’re “static.” In plain terms, every page is printed ahead of time into a plain file, like a brochure, instead of being assembled live from a database each time someone visits. There’s no always-on database sitting behind the public site for someone to pry open. There’s simply nothing there to break.

The few interactive parts, like the chat with Kyn or the audit form, run on small locked-down functions that wake up only when needed, not a server that’s exposed around the clock. Every connection goes over HTTPS (the little padlock in your browser), and I set the security headers that tell browsers to refuse the common tricks attackers try.

What’s the deal with cookies, and why this site never asks

You’ve seen the box on nearly every site you visit: “Accept cookies?” Cookies are small files a website saves in your browser. A few are harmless, like remembering your language. But most of those pop-ups exist for one reason: the site is using cookies to follow what you do and hand it to advertisers, and the law says it has to ask your permission first.

This site doesn’t do any of that. No tracking pixels, no ad networks, nobody buying a profile of your behaviour. That’s why you never saw a pop-up here, and why the footer carries a small “no-cookies website” badge. There’s no consent box because there’s nothing to consent to. I’d rather earn your trust than harvest your clicks.

When I automate something, who sees your data?

This is the question that should come up the moment you hand any tool access to your accounts. When I build you an automation, your information moves between your own apps using your own logins. I’m not a middleman keeping a copy in the middle.

That’s a big reason I build on n8n. With n8n the engine and the data can sit inside your own accounts, not a third party’s, so a customer’s phone number or an invoice never has to pass through anything that belongs to me. If you’re weighing tools, I wrote the longer version in n8n vs Zapier.

What I can promise, and what I can’t

No one honest will tell you a system can never be broken, and if someone does, that’s the first thing that should worry you. So here’s the honest line between the two.

What I can’t promise: that no website or account anywhere is ever at risk. Nobody can.

What I can promise, and mean: I build on platforms whose full-time job is security, audited by people who will always be better at this than I am. I don’t collect data I don’t need. I turn on encryption and the right protections by default, not as an upsell. And if something ever did go wrong, you’d hear it from me first, fast, in plain words, not buried in a notice three weeks later.

That’s the part a certificate can’t give you, and it’s the part I actually control.

Quick answers

Do I have to accept cookies on this site? No. There’s no cookie pop-up because the site doesn’t track you. Nothing is following your visit or building a profile to sell, so there’s no permission to ask for.

Where is my data stored? On Vercel (your site) and, if your project needs one, Supabase (your database), both running on Amazon’s data centres under accounts in your name.

Is it safe to give an automation access to my accounts? Yes, when it’s built so your data stays in your own apps and logins, which is how I build on n8n. Ask exactly what each connection can touch; a straight answer is a good sign.

Can you guarantee my site will never be hacked? No, and don’t trust anyone who says yes. What I can do is build on audited platforms, collect as little as possible, and be the first to tell you straight if anything is ever off.

Still want to ask in person?

Trusting a small studio with your site, or with your customers’ data, is a fair thing to want answered out loud. Tell me what you’re worried about and I’ll give you the real answer. The first twenty-minute call is free, or ask Kyn right here. And if you’re still mapping what to hand off first, start with agent, automation, or chatbot?.