MerzSoft
Back to the legal center

Legal center

Security and confidentiality

Protection principles applied to the site, communications, and client projects.

Last updated: October 11, 2026

1. Principles

  • Collect and share only the information needed for each purpose.
  • Limit access to personnel and providers who need to be involved.
  • Keep credentials and secrets out of public code and browser interfaces.
  • Review risk according to the scope and sensitivity of each project.

2. Site and communication protection

The site uses encrypted HTTPS connections and infrastructure services that help mitigate abusive traffic. The form validates input, limits attempts, and keeps the email-provider credentials in the server environment.

These measures reduce risk but cannot promise absolute security. We investigate and remediate reasonably verified vulnerabilities according to their impact.

3. Project confidentiality

Client information is used to assess or perform the agreed service. Where needed, the parties may sign a confidentiality agreement and define who can access repositories, designs, data, and environments.

We will not publish a client project, logo, result, or testimonial as a case study without the relevant authorization.

4. Secure development and delivery

  • Access and environment definition according to the project.
  • Review and testing proportional to risk before delivery.
  • Third-party dependencies and services subject to updates and licenses.
  • Transfer or revocation of access when the project closes, as agreed.

Specialist audits, penetration testing, managed backups, high availability, and certifications are not presumed to be included; they must be stated in the proposal.

5. Shared responsibility

Clients must protect their accounts, use appropriate authentication, provide lawful content, communicate access changes, and keep the services they manage up to date. Passwords must not be sent through the public form.

6. Incidents

For a confirmed incident under our control, we will seek to contain it, document it, correct its cause, and notify affected people or clients where required by risk, contract, or applicable law.

Suspected vulnerabilities may be reported through the contact email without exploiting the issue, accessing other people’s data, or disrupting the service.

7. Providers and changes

Providers are selected according to service needs, while each remains responsible for its own infrastructure. This policy may change as safeguards, risks, or providers evolve.

These pages describe the general operation of the site. A signed proposal or contract may establish project-specific conditions and will govern that service.