Privacy

We read only what is
already public.

This is the key difference. We don't ask for access to your systems and we don't get it. The access we build knows exactly what your site tells the world - and not a word beyond that.

What we read

  • Visible pages: home, services, about, common questions.
  • The price list, if it is published on the site.
  • Terms, policies and contact details written in the open.
  • In short - everything anyone sees without logging in.

What we never touch

  • The site's code - we don't go into it at all.
  • The database and admin systems - we have no access.
  • Passwords, personal areas, closed dashboards.
  • Data about customers, patients or staff - we don't see it.

Why this isn't just a promise

There is a difference between "we promised not to go in" and "we have no way in". Here it is the second. We reach the site the way any visitor does, from the outside. There is no connection to your systems that could be left on or misconfigured - there simply is no such connection. It is the boundary of how the work is built, not a box someone has to remember to tick.

And about updates and compliance

How it updates without internal access

When the site changes, the access re-reads the public content. Access to systems is not needed to update, because everything required is already public on the site.

Less sensitive data - less exposure

Because we don't collect your customers' personal data, there is no pile of sensitive information sitting with a third party. That keeps the picture simpler against requirements like GDPR too.

Let's start with your site

Leave an address and an email. We'll show you exactly what gets read and what doesn't.