The Vetrya profile describes a Code of Ethics that sets out the principles of conduct guiding every activity of the group. Five principles are named: legality, fairness, respect for people, confidentiality of information and protection of the environment. Everyone who works with the group, from employees to suppliers, is asked to share them. The profile explains the purpose in one sentence: these principles strengthen mutual trust and the quality of relationships.
A code of ethics is easy to publish and harder to live by. Its value depends on whether people can translate each principle into concrete behavior on an ordinary working day. This article takes the five principles one at a time, explains what they commonly mean for a technology group and shows how a client or a supplier can see them at work.
Why a technology group needs a code
A group that builds cloud platforms, apps, payment services and data-driven solutions handles things that other people depend on. Customers trust it with their information. Clients trust it with their operations. Employees trust it with their careers. Suppliers trust it to pay fairly and to treat them with respect. A written code gives all these relationships a common reference point.
The code also helps with situations that rules do not cover. Laws and contracts describe the minimum. Many everyday decisions fall in a gray area where no rule applies and judgment is required. A set of shared principles guides that judgment, so people in different countries and different roles reach similar answers to similar questions. For a group with companies in the United States, Southeast Asia, Latin America and Iberia, this shared guidance is especially useful.
Legality
The first principle is legality. At its simplest, it means obeying the law in every place where the group operates. That sounds obvious, but in a technology business it has many practical consequences.
- Data protection rules differ from country to country, and a service that handles personal data must respect the rules that apply to each user.
- Contract law, consumer protection rules and financial regulations affect how services are sold and how payments are handled.
- Rules on intellectual property determine how software, content and trademarks may be used.
- Rules on competition and on fair dealing govern relationships with clients and rivals.
Legality in practice means that people ask the right questions before launching something new. Which rules apply? Who checks them? What evidence will show that the rules were followed? Because the group operates in several regions, legality also means keeping track of differences and not assuming that what is allowed in one country is allowed in another.
Fairness
Fairness covers how the group treats everyone it deals with. It includes honest dealing with clients, fair selection of suppliers, equal opportunities for employees and balanced treatment of partners.
For a client, fairness appears in clear proposals, realistic promises and transparent pricing. A fair supplier explains what is included, what is not and what could change the cost. It avoids pressure tactics and does not hide limitations. When a project runs into problems, a fair partner reports them early and works with the client on a solution, instead of waiting until the problem becomes unavoidable.
Fairness also applies to the technology itself. When services use artificial intelligence or automated decisions, fairness means checking that the system does not treat groups of people unequally without good reason. This is an active task. It needs testing, review and a willingness to correct a system that produces unfair results.
Respect for people
The third principle is respect for people. It applies inside the group and outside it. The profile’s broader values support the principle: the vision rests on the conviction that technology becomes truly useful when it serves people and businesses, and the design approach keeps the people who will use a product at the heart of the work.
Inside the organization, respect means safe and fair working conditions, space for different views and attention to the well-being of colleagues. Teams that span cultures and time zones need particular care. A comment that sounds normal in one place may sound rude in another, and a meeting scheduled at a convenient hour for one office may be an imposition on another.
Outside the organization, respect shows in how products are designed. A service that is easy to understand, accessible to people with different abilities and clear about what it does with personal information shows respect for its users. The principle of putting user experience before visual appearance can be read as respect in practice, since it means that people’s needs come before decoration.
Confidentiality of information
Confidentiality of information is central for a group whose work revolves around data. Clients share business plans, customer lists and technical details. End users share personal information and payment details. All of this must be protected from unauthorized access and use.
The principle has several layers.
- Employees and suppliers must not disclose confidential information to people who are not entitled to it.
- Access to systems and data should be limited to those who need it for their work.
- Information must be protected when it is stored and when it moves across networks.
- Incidents that could expose information must be reported and handled quickly.
The security approach described in the profile gives these commitments a technical form. The group protects data, applications and infrastructure with dedicated processes, tools and skills, and it develops Security Operations services that monitor and manage risk continuously. Confidentiality is the ethical goal, and security is the discipline that pursues it every day.
Protection of the environment
The fifth principle is protection of the environment. A technology group may seem far from heavy industry, but its activities have an environmental footprint. Data centers use electricity and water. Devices are manufactured, transported and eventually discarded. Large computing workloads consume energy.
Cloud platforms offer a way to reduce part of that footprint. Shared infrastructure can be used more efficiently than many separate machines, because capacity is allocated according to demand and not left idle. Efficient design, such as avoiding unnecessary processing and storing data sensibly, reduces energy use further.
The profile’s Social Report also refers to sustainability goals, which indicates that environmental concern is part of the way the group measures its impact. A client who cares about their own environmental performance can ask a partner how its services affect energy use and what choices are available to reduce it.
Everyone who works with the group
The profile says that everyone who works with the group is asked to share the principles, and it names employees and suppliers explicitly. Including suppliers is significant. A company’s conduct is judged not only by what it does directly but also by the behavior of those it chooses to work with. A supplier chain that ignores labor rules or environmental standards can damage the reputation of the buyer.
Asking suppliers to share the principles often involves practical steps, such as including ethical commitments in contracts, requesting information about their practices and discussing problems openly when they arise. For suppliers, the benefit is clarity. They know what is expected and can plan accordingly.
Clients can apply the same logic to themselves. A client who works with the group might share its own values and check that they match. When both sides share principles, disagreements about how to behave are rarer and easier to resolve.
Mutual trust and the quality of relationships
The profile closes its description by saying that the principles strengthen mutual trust and the quality of relationships. Trust is not a soft extra in a technology project. It has a direct effect on results. When a client trusts a supplier, information flows more freely, problems are reported earlier and decisions are made faster. When a supplier trusts a client, it can be honest about risks without fear that candor will be punished.
Trust is built through repeated experience. A promise is kept, a mistake is admitted, a confidential matter stays confidential. The code provides the framework, and daily behavior fills it with substance.
Putting the code to the test
A reader who wants to judge whether a code of ethics is real can ask a few simple questions.
- Is the code written clearly, in language that people can understand and apply?
- Does it apply to everyone, including leaders and suppliers?
- Is there a way to raise concerns and a commitment to treat them seriously?
- Do the company’s actions in difficult situations match the code?
A code that passes these questions is more than a decoration. It becomes part of how the organization decides what to do when pressure is high.
Turning principles into habits
A principle becomes real when it changes what people do on a normal Tuesday. A few simple routines can carry the five principles into daily work.
- A short check before each new project asks which laws apply, who is affected and which data is involved.
- Proposals to clients are reviewed for clarity, so that promises are realistic and limits are stated.
- Meetings include everyone who is affected, with time for every voice.
- Access to data is granted for a specific purpose and reviewed regularly.
- Choices about equipment and computing resources consider energy use alongside cost.
None of these routines is complicated. Their strength comes from repetition, since habits shape the culture of an organization more than speeches do. Leaders have a special role because people watch what they do under pressure. When a leader follows the code at a difficult moment, the code gains credibility. When a leader ignores it, no document can repair the damage.
