Trust, stated plainly.

Client software runs in the client’s own environment or in a dedicated tenant agreed for that deployment, inside the EU. Where the client hosts, terminal credentials, data feeds and records stay in the client’s tenant; MYG operates them during the build and hands them over.

After handover MYG holds no client data and no client credentials. Access for warranty work is granted by the client for the duration of the work and withdrawn afterwards.

Every deployment keeps a point-in-time record: each fact is stored with the date it became known, every automated decision is logged with what it read and what it did, and the log is hash-chained so it cannot be edited afterwards without leaving a trace.

That record is the client’s. It is what an auditor, a supervisor or the client’s own IT provider can read a year later.

A data-processing agreement is available before any client data is touched. It names the processing purposes, the retention period, the sub-processors for that deployment and the contact for data-subject requests. Processing stays within the EU unless the client instructs otherwise in writing.

This website itself uses Vercel for hosting, Resend for transactional email, and, only with consent, Google Analytics. Cookie choices can be changed at any time from the banner.

Our engineers work with agents that draft, test and benchmark alongside them. A person decides what gets built and reads every change; nothing reaches a client until the automated tests pass and the record shows where each change came from.

Public documents may go to a language model under contract; licensed data and client records do not leave the client’s environment. When a client asks which parts of a deployment were assisted, we tell them.

Security reports go to contact@myg-media.com, in English or German. The machine-readable policy is at /.well-known/security.txt. We acknowledge reports within two working days and do not pursue researchers who report in good faith.