Security
Built secure, by default.
Security is not an add-on for us; it is the foundation. This is how we approach everything we build, in plain language and with real examples from our work.
- 01
A personal login for everyone
Every user gets their own account with their own password. It is always clear who did what, and access can be granted or revoked cleanly.
For example
In the construction platform we are building for a contractor, every freelancer gets their own login, in their own language.
- 02
Everyone sees only their own data
The database itself guards, row by row, who may read what. Even if something went wrong in the site, the database simply refuses to hand over someone else's data.
For example
A client in our portal sees only their own invoices, tickets and documents. Never anyone else's.
- 03
The server double-checks everything
Hiding a button is not security. Every action is verified again on the server: is this person really allowed to do this? Only then does anything happen.
For example
Admin actions in our systems check the user's role first. If it does not match, nothing happens.
- 04
Always an encrypted connection
Everything runs over https, the padlock in your browser. Eavesdropping along the way is pointless, and browsers are automatically steered to the secure line.
For example
This is enabled on every site we build. Enforced, not optional.
- 05
Strict rules for the browser
A site can tell the browser exactly what is allowed: which scripts may run and who may embed the site. We set those rules tight.
For example
The website we built for Van de Pol only accepts its own scripts and refuses to be embedded in anyone else's page.
- 06
Keys in the vault, never in the code
Passwords and integration keys do not live in the source code but in a secure vault at the hosting provider. They cannot leak by accident.
For example
Our bookkeeping integration reads its key only on the server, straight from that vault.
- 07
Private documents stay private
Proposals and invoices live behind long, unguessable addresses, and we actively keep search engines away.
For example
Search engines do not know our proposal pages exist. Only people who receive the link can open them.
- 08
Careful with data
We store as little as possible and deliberately choose European services for storage and email. Good for you, and neat under the GDPR.
For example
On the Van de Pol site we even host the fonts ourselves, so no visitor data flows to American servers.
- 09
Backups and updates keep running
Daily backups and maintained updates are a standard part of our care. If something breaks, we restore it.
For example
This is included in every hosting-and-care package we deliver, at no extra charge.
Questions about how we handle your data? We are happy to explain, without jargon.
Ask your question