Skip to content

HOME SECURITY AND DATA

WHERE DOES YOUR DATA SIT, AND WHO REACHES IT?

These questions come up on vendor forms in enterprise procurement; the answers should be in writing rather than in a call. We do not list certifications we do not hold — what follows are practices, not badges.

FIG. 13 — SECURITY

Security and data

  1. Your data can stay on your server

    Where it matters we install the whole system on your own server; we have built deployments that run without opening a single outbound connection. If cloud is used, which data sits where is written down up front.

  2. Access is granted at the minimum

    A developer's access to production is as much as the job requires and is closed when the job ends. Production data is not copied into development; where needed we generate masked sample data instead.

  3. Secrets never live in code

    API keys and passwords are not written into the repository; they come from environment variables or a secret manager. The same rule applies to this site's own form endpoint.

  4. Backups are part of deployment

    Going live includes the backup setup: how often, where it is stored, and how it is restored. A backup whose restore has never been tested does not count as a backup.

  5. An NDA is standard

    It can be signed before the first conversation. If you have your own template we work from it. We never use a client's name on the site or as a reference without permission.

  6. Handover is always possible

    Source code, servers and accounts stay in your name, and setup steps are documented. If you want to move to another team, we leave no technical obstacle in your way.

For the notice on processing of personal data: Privacy Notice

CONTACT

ANYTHING ELSE? ASK.

If you have a vendor questionnaire, send it; we also answer what is not written here.

Start a project