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-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".
- Address: Carrera 15 # 39-20, Cartagena de Indias, Bolívar, Colombia
- Email: hello@engmanapp.com
- Telephone: +57 318 659 4497
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:
- Customer: the company that holds the Workspace.
- Workspace: the Customer's space in engman.
- Owner: the User who created the Workspace or who holds it now.
- User: a manager with an engman account: the Owner or another manager the Customer invited.
- the Customer's People: the employees (and, where the Customer has decided it is lawful, contractors) about whom Users keep Records. They have no engman account.
- Records: the 1:1s, action items, feedback, career plans, imported documents and private notes that Users keep.
- Proposal: an artificial-intelligence output or a write by a Connected agent that waits for a person to confirm it in the web app.
- Connected agent: an artificial-intelligence assistant a User connects to engman through MCP or A2A.
- Subprocessor: a provider that processes the Customer's personal data for engman.
- the Terms: engman's Terms of Service.
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:
- Your name and email address.
- If you sign in with Google: the name and email Google gives us. We ask only for that basic profile data, and we do not keep your profile picture.
- If you sign in with email and password: the password, which we store only as a cryptographic digest (an Argon2id hash), never in readable form.
- Your second factor: the key of your authenticator app or the public key of your passkey, and your recovery codes. The app key and the codes are stored encrypted.
- Your preferred language.
- For each session: the IP address and the browser and system (user agent) you signed in from.
Purposes:
- Create your account and protect it, including the second factor every User must use.
- Identify you when you sign in and show you only the Workspace and the Records you have access to.
- Send you service emails, such as confirming your email or changing your password, and the ones engman sends on your behalf, such as agendas.
- Show you the app and the emails in your language.
The Customer's People have no account: the User enters their information (section 20).
Preventing repeat trials. To give one trial per organization, engman keeps the email domain of the person who creates the Workspace or, for a personal email, a keyed hash of that email, with the trial's start date, for 24 months. If someone else on the same domain creates a Workspace, engman emails the first Workspace's Owner naming that person's email. Basis: legitimate interests (GDPR art. 6(1)(f)), with the right to object; LGPD art. 7(IX); in California, security and integrity (CCPA); in Colombia, the authorization the Owner gives when creating the Workspace, which names this purpose; in Mexico, the consent the Owner gives when creating the Workspace, which names this purpose.
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:
- the User's identifier and the Workspace's identifier;
- the versions of the Terms and of this Policy that they accepted;
- the kind of acceptance: as Owner when creating the Workspace, as an invited User, or for a material change;
- the date and time;
- the IP address and the browser and system (user agent) they accepted from, and the session identifier;
- the language in which the text was shown to them;
- for the Owner's acceptances, the Customer's legal name or name, its country and its tax identification number, if one was entered. When the Customer is a natural person, that name and number are personal data.
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.
- Google Calendar (optional): engman reads the events on calendars you own to find your upcoming 1:1s, keeps only the identifier and times of the events it links to a 1:1, and writes the meeting agenda into the description of events you organize. It does not read other calendars.
- Google Drive (optional): engman opens only the files you pick in the Google file picker, to import their content. It cannot see your other files.
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.
- What it can read. In this version of engman, only identifiers: names, work emails, teams, who each person reports to, dates, statuses, counts (for example, of open or overdue action items), email language and internal ids. Never free text, such as the content of 1:1s, feedback or private notes. And only what the User who connected it can already see.
- What it can write. 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. A Connected agent never changes a Record directly.
- Where the data goes. What engman returns to the agent reaches that agent's provider (for example, Anthropic for Claude), under the account the User holds with that provider. From then on the data has left engman and that provider's terms apply. That provider is not an engman Subprocessor.
- What we keep. Which agent it is, who connected it and when, and when it was last used, to show on the Connected agents page. Each call the agent makes is also recorded as an audit event (who, when and which action, with identifiers), which is part of the Customer's data (section 20) and is kept while the Workspace exists.
- How long. Proposals nobody confirms are discarded after 30 days. The agent's access lasts until the User disconnects it; if the agent goes unused for 14 days, the User must approve it again.
- How to stop it. In the web app, on the Connected agents page, with the Disconnect button (app.engmanapp.com/agents). The agent is cut off on its next call; what it already proposed stays in the confirmation queue until it is confirmed or discarded. The Owner can also turn off agent access for the whole Workspace on the same page.
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:
- Users: with the acceptance box, shown unticked when creating a Workspace and when accepting an invitation. Before you tick it, we use your account data only so that you can sign in and create or join a Workspace.
- Waitlist: with the form's authorization box, which is required. The 20-minute call is arranged only if you also tick the separate, optional box that allows it.
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:
- for your account, performance of the contract (GDPR art. 6(1)(b));
- for the waitlist, steps prior to a contract that you asked for by signing up (GDPR art. 6(1)(b)) and, to arrange the call, your consent, which you give with the optional box and can withdraw at any time (GDPR art. 6(1)(a));
- for acceptance evidence, our legitimate interest in proving the contract and the authorization, and in establishing, exercising or defending claims (GDPR art. 6(1)(f)).
11. Recipients and processors
We share personal data only with those who need it for their task. Each receives only what that task requires.
- Providers that process data for engman. Google Cloud hosts engman, stores its data and runs the artificial-intelligence models. An email provider sends engman's emails, including those to the waitlist. Google also hosts the waitlist form (Google Forms). The full list of Subprocessors, with each one's name, location and activity, is on the Data Processing Agreement (DPA) page: engmanapp.com/dpa.
- Paddle (Paddle.com Market Ltd), which collects payment for subscriptions as reseller and Merchant of Record and processes billing data as an independent controller, under its own privacy notice: https://www.paddle.com/legal/privacy. It is not an engman Subprocessor and receives no Customer Data.
- Connected agent providers. They receive, outside engman, what the User asks for through the agent (section 9).
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
- Data is encrypted in transit and at rest.
- Private notes are additionally encrypted with a key of their own for each Workspace, protected by a Google Cloud KMS key.
- Every User signs in with a second factor (an authenticator app or a passkey), also when signing in with Google.
- The original files you import are deleted once the import is settled, and at most 30 days after upload.
- Technical logs: for each request your browser or a Connected agent sends to engman, engman logs the method, the address requested without parameters or tokens, the result, the response time and a request identifier. These logs keep neither your IP address nor your browser. To limit sign-in attempts, engman also keeps a counter per IP address for a few minutes. We use them only to keep the service secure and to find and fix faults.
- Cookies: the website engmanapp.com sets none; the app sets only the sign-in session cookie, which is strictly necessary.
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. |
| One trial per organization | 24 months after the trial starts. |
| 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:
- Know, update and correct your personal data.
- Ask for proof of the authorization you gave us.
- Be told, on request, how we have used your data.
- File complaints with the SIC, after making your query or claim to engman (section 18).
- 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).
- 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:
- Disconnect Google Calendar or Google Drive, in engman or in your Google Account.
- Disconnect a Connected agent on the Connected agents page.
- Ask us for a copy of your data, or to delete your account and its data, at hello@engmanapp.com.
- If a User keeps Records about you, see section 20.
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.
- Queries (for example, to know what data we hold about you): we answer within 10 business days of receiving it at most. If we cannot within that time, we tell you why and answer within 5 more business days at most.
- Claims (to correct, update or erase data, revoke the authorization, or report a breach of the rules): we answer within 15 business days at most, counted from the day after we receive it. If we cannot within that time, we tell you why and answer within 8 more business days at most.
- Incomplete claims: within 5 days of receiving it, we ask you for what is missing. If 2 months pass from that request without you sending it, we take it that you have withdrawn the claim.
- Claims that are not ours to resolve: we send them to whoever must resolve them within 2 business days at most, and we tell you.
- Complaint to the SIC: you can file it only after making your query or claim to engman.
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-12-18 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.