Español · The Spanish text governs; this English version is a translation.

Privacy Policy

It is also engman's personal-data treatment policy under Ley 1581 de 2012.

Version: 2026-10-27

A new version takes effect on December 18, 2026: read version 2026-12-18.

This is an English translation. The Spanish text is the one that governs (section 21).

1. Data controller

The controller of the personal data this Policy describes is Ruben Amauri Melo Carballo, a natural person domiciled in Cartagena de Indias, Colombia, who acts under the trade name engman. In this Policy we call them "engman".

2. Scope

engman is a web application where tech leaders (CTOs, heads of department and engineering managers) keep the 1:1 meetings, feedback and career plans of the people they lead.

This Policy covers the personal data for which engman is the controller (Responsable): Users' accounts, the waitlist and acceptance evidence (sections 3 to 5). Section 6 explains invitation emails, which engman sends on the Customer's behalf. It also explains how engman handles Google data, artificial intelligence and Connected agents. It is, in addition, the personal-data treatment policy that Ley 1581 de 2012 requires. It is a single document, published in Spanish and English (section 21).

For the Records that Users keep about the Customer's People, the Customer is the controller (Responsable) and engman acts as processor (Encargado), on the Customer's behalf (section 20). That relationship is governed by the Data Processing Agreement (DPA).

In this Policy, these words have this meaning:

3. Databases and purposes: Users' accounts

This database holds Users' accounts. It includes invited managers: their account is theirs, not the Customer's, and each of them gives the authorization to process it.

Data we process:

Purposes:

The Customer's People have no account: the User enters their information (section 20).

4. Databases and purposes: waitlist

The waitlist on engmanapp.com is two Google Forms, one in Spanish and one in English. The answers are saved in a Google Sheets spreadsheet.

They ask, as required, for your email, your role and how many people you manage, directly and indirectly. If you wish, also your country, your name and how you heard about engman (it may come prefilled with the channel you reached the page from).

We use them only to: (i) write to you about engman; (ii) invite you to early access; and (iii) arrange a 20-minute call, only if you tick the separate, optional box that allows it.

Each form shows a notice with these details and two boxes: the authorization, required, and the call, optional. If you write to us at hello@engmanapp.com, we delete your entry.

5. Databases and purposes: acceptance evidence

Each time a User ticks the acceptance box (when creating a Workspace, when accepting an invitation, or for a new version of the Terms), we store an acceptance record with:

Purposes: to prove that the contract was made and that you gave your authorization, and to establish, exercise or defend legal claims. We do not use these records for anything else (section 15).

6. Invitation emails

When a User invites a person to engman, engman sends the invitation to the work email address the Customer recorded for that person. It does so on the Customer's behalf, as processor (Encargado), under the DPA: that email is part of the Customer's data and is kept while the person's record exists in the Workspace. The invitation link expires after 7 days; the User can send a new one.

When the person accepts, engman checks that whoever joins is the person invited, and the email becomes part of their account (section 3).

7. Google user data

engman asks for each Google permission only when you turn on the feature that needs it. You can revoke it at any time in your Google Account.

The use of information received through Google Workspace permissions will comply with Google's User Data Policy, including its Limited Use requirements. The statement Google requires, in its original language:

"The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements."

We do not sell Google user data, do not use it for advertising, and do not use it to train or improve artificial-intelligence models. Google access tokens (OAuth) are stored encrypted.

8. AI processing

engman uses Google's Gemini models on Vertex AI, part of Google Cloud, to extract and summarize the documents you import and to prepare meeting agendas.

engman's artificial intelligence extracts, groups and summarizes the Customer's own Records, with links to their sources, and drafts agendas.

Every artificial-intelligence output and every write by a Connected agent is a Proposal that a person reviews and confirms in the web app before it is saved. Nothing is saved to a person's Records without that confirmation.

engman's artificial intelligence never rates, ranks, scores or compares people, never infers emotion, and never recommends hiring, promoting, disciplining or dismissing anyone.

Google does not use this data to train its models. engman does not train models on its Customers' data either, and uses only artificial-intelligence providers that commit not to do so.

Google's automated abuse monitoring may keep a request it flags for up to 90 days, in the United States, only to review possible misuse.

9. Connected agents

A User can connect an artificial-intelligence assistant (for example, Claude) to engman through MCP or A2A. The Connected agent acts on behalf of that User.

10. Legal basis and authorization

In Colombia. We process your data with your prior, express and informed authorization (Ley 1581 de 2012, art. 9). Colombian law does not allow processing it merely because it is needed for a contract (Ley 1581 de 2012, art. 10), so we ask for that authorization:

If the EU General Data Protection Regulation (GDPR) applies to you. We rely on your consent only for the waitlist's optional call. The bases are:

11. Recipients and processors

We share personal data only with those who need it for their task. Each receives only what that task requires.

12. International transfers and transmissions

engman runs on Google Cloud in the United States: the application and the database are in the us-east4 region, and the Vertex AI models run in the United States. The email provider stores data in the United States.

Sending data to these providers so that they process it for us is an international transmission. The United States is on the list of countries with an adequate level of data protection published by the Superintendencia de Industria y Comercio (SIC), Colombia's data-protection authority. Each transmission is covered by a data processing contract with the provider (Decreto 1377 de 2013, art. 25).

For data subjects in the European Union: Colombia has no adequacy decision from the European Commission. So when a Customer established in the European Union transfers personal data to engman, the transfer is covered by the European Union's standard contractual clauses, annexed to the DPA.

13. Security

14. Retention

We keep each piece of data only for these periods:

Database Period
Users' accounts While the account exists. We delete it when you ask, when the Owner deletes the Workspace, or together with the person's profile when the Customer archives them and 24 months have passed since their leaving date (sooner, if the Owner deletes it).
Waitlist Up to 24 months after you sign up, or until you ask us to delete it, if you ask sooner.
Acceptance evidence The period in section 15.
Connected agents Until the User disconnects the agent; if it goes unused for 14 days, the User must approve it again. Proposals nobody confirms, 30 days.
Imported files Until the import is settled, and at most 30 days after upload.
Technical logs 30 days.

When we delete data from engman's database, it disappears at once from the live database and, within 7 days at most, from the backups. After that, Google purges those copies from its systems within 180 days at most, and no one can recover or restore them.

15. Retention: acceptance rows after deletion

The acceptance records in section 5 are kept even after the User's account or the Workspace is deleted. We keep the identifiers (including the session's), the versions accepted, the kind of acceptance, the language in which the text was shown, the date and time, the IP address, the user agent and, for the Owner's acceptances, the Customer's identification (section 5). The IP address is personal data, and so are the name and tax identification number of a Customer who is a natural person.

We keep the IP address and the user agent for 2 years from the end of the contract they relate to, and the rest of the record for 10 years from that same date, to prove the contract and the authorization, and to establish, exercise or defend claims (Decreto 1377 de 2013, arts. 9 and 11; GDPR art. 17(3)(e)). While that period runs we cannot erase these records even if you ask, because there is a legal and contractual duty to keep them. We consult them only for legal purposes, such as proving an acceptance or handling a claim; never for the product or for analytics. When each period ends, we delete that data.

16. Data subjects' rights

Under Ley 1581 de 2012, art. 8, you have the right to:

  1. Know, update and correct your personal data.
  2. Ask for proof of the authorization you gave us.
  3. Be told, on request, how we have used your data.
  4. File complaints with the SIC, after making your query or claim to engman (section 18).
  5. Revoke the authorization or ask us to erase your data, except where there is a legal or contractual duty to keep it (as in section 15).
  6. Consult your personal data free of charge, at least once every calendar month (Decreto 1377 de 2013, art. 21).

If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction of processing and portability of your data (GDPR arts. 15 to 20), and the right to lodge a complaint with a data-protection authority.

Right to object (GDPR art. 21). Where we process your data for a legitimate interest (acceptance evidence), you can object at any time, on grounds relating to your particular situation. We will stop processing it, unless we need it to establish, exercise or defend claims.

What you can do yourself:

17. Person or area responsible for requests

engman's Personal Data Protection Area (Área de Protección de Datos Personales) handles queries, claims and other requests about personal data (Decreto 1377 de 2013, arts. 13.4 and 23). You can write to hello@engmanapp.com, send a letter to Carrera 15 # 39-20, Cartagena de Indias, Bolívar, Colombia or call +57 318 659 4497.

18. Procedure and time limits

To make a query or a claim, write to us at hello@engmanapp.com or use the other channels in section 17. Give your name, how to contact you and what you are asking for. If it is a claim, describe the facts and attach the documents you want to rely on. We may ask you to confirm your identity before we answer.

19. Minors

engman is a tool for business leaders and is not directed at minors. The Terms also say that engman is not designed to keep Records about minors.

20. engman as processor

The Records that Users keep about the Customer's People belong to the Customer. For that data, the controller (Responsable) is the Customer, and engman processes it only on the Customer's behalf and under its instructions, as the DPA says. This includes the Records that a User's own manager keeps about that User.

If a User keeps Records about you, send your request to your employer, which is the Customer. You can also write to us at hello@engmanapp.com: within 2 business days at most we will send your request to the Customer and let you know that we did.

21. Language

This Policy is published in Spanish and English. The Spanish text is the one that governs; the English version is a translation.

22. Changes

Each version of this Policy is identified by its effective date and stays published at its own address, with that date (for example, engmanapp.com/privacy/2026-10-27). engmanapp.com/privacy always shows the version in force.

If we make a substantial change, such as a change in the identity of the controller (for example, if engman becomes a company) or in the purposes of processing, we will tell you by email before it takes effect. If the change adds a new purpose, we will ask you for a new authorization; Users will give it on the acceptance page shown after signing in.

23. Effective period

This Policy is in force from 2026-10-27 until a new version replaces it. The databases in sections 3 to 5 will remain in force while engman provides its service; within them, each piece of data is kept only for the periods in sections 14 and 15.