Start building a more resolutive network
Book a demo and we'll show you the impact with your network's own numbers.
Version 2.11 · In force since November 19, 2026
TERAL website, platforms, applications and integrations
| Item | Information |
|---|---|
| Controller | TERAL S.A.S., Tax ID (NIT) 901.616.741-2 |
| Address | Cra 43F #10-38, Manila, El Poblado, Medellín, Antioquia, Colombia. |
| Privacy channel | Primary: alan@teral.ai. Alternate: teralai@teralmed.co. Contact phone: +57 300 467 8602. |
| Surfaces | teral.ai/es, web platform, mobile applications, administration, support and institutional integrations |
| Version | v2.11, text updated on November 9, 2026 |
TERAL S.A.S., Tax ID (NIT) 901.616.741-2, with its principal domicile in Medellín, Antioquia, Colombia, acts as controller when it determines the purposes and essential means of processing. Address for notices: Cra 43F #10-38, Manila, El Poblado, Medellín, Antioquia, Colombia. For inquiries, complaints and the exercise of rights: Primary: alan@teral.ai. Alternate: teralai@teralmed.co. Contact phone: +57 300 467 8602. The officer responsible for handling data protection requests is David Alberto Calderón Duarte, with intake and coordination through the channels indicated.
Where TERAL processes information on behalf of a healthcare provider, insurer, clinic, hospital, health professional or other client that determines the clinical or institutional purpose, TERAL will act as processor under the terms of the applicable agreement, data transmission agreement or DPA. This classification depends on the actual flow and not on the name the parties give the document.
This Policy applies to the teral.ai/es website, forms, commercial and support channels, user accounts, web and mobile applications, administrative modules, demonstrations, pilots, integrations with information systems, artificial intelligence services, APIs and any other TERAL operation involving personal data.
For processing carried out on behalf of an institutional client, the controller's lawful and documented instructions, the DPA, the security annex and the corresponding agreement will prevail for that flow. This Policy does not replace the data subject's authorization, clinical informed consent, the client's privacy notice or the obligations of the custodian of the medical record.
Including an AI function, provider or data category in the general description of the Platform does not enable it for every client. Each activation will respect the documented instructions, scope and exclusions of the applicable agreement and DPA. Where a signed instrument initially excludes AI processing or requires a Change Order, that condition must be met before activation; it is not modified by publishing this Policy or the Terms of Service.
TERAL will apply the principles of lawfulness, purpose, freedom, truthfulness or quality, transparency, restricted access and circulation, security and confidentiality. It will also apply criteria of minimization, necessity, proportionality, privacy by design and demonstrated accountability according to the sensitivity and risk of each flow.
Data subjects may be health professionals, institutional administrators, patients, client representatives, website visitors, commercial contacts, employees, candidates, contractors, suppliers and other persons connected with TERAL's operation.
TERAL may receive data directly from the data subject, from an authorized client or user, from permitted public sources or through integrations activated and documented for a project. The methods below depend on the contracted service; describing them does not mean that all of them are active, nor does it by itself authorize a connection to clinical systems.
The existence of redaction, pseudonymization or visual masking does not mean that all data are anonymous. Images, documents and screenshots may contain visible or embedded identifiers, metadata or text. The client and TERAL must validate the actual flow, the fields processed, the permissions, the logs and the exact point at which each control operates.
Clinical integrations require prior per-project validation of fields, permissions, authentication, logs, retention, incidents and testing. The detection and removal controls provided for text do not evidence equivalent protection of images, screenshots, metadata or retrieved documents. Before enabling each flow, TERAL and the controller must define and verify the appropriate measures and the review or suspension procedure that applies when those measures prove insufficient. No transmission lacking a legal basis or the necessary security measures is authorized. Using a model or OCR does not by itself evidence anonymization.
The data subject is not required to authorize the processing of sensitive data and will be informed that doing so is optional, except where a legal exception applies. Where TERAL acts as controller and the processing requires authorization, it will obtain prior, express, informed and verifiable authorization, specific to the corresponding purposes and sensitive categories.
Where it must obtain authorization, TERAL will use physical or electronic forms or other verifiable means that evidence the data subject's will; silence does not constitute authorization. It will retain evidence of the text accepted, the identity and the date of acceptance, with restricted access, for as long as the authorized processing and the applicable legal or defense obligations subsist. The data subject may request a copy through the channels in section 1.
Where a client or professional uploads clinical information and TERAL acts as processor, the controller must evidence the authorization or the applicable legal exception, inform the data subject and document its instructions. Acceptance of this Policy or of the Terms of Service does not by itself replace express authorization to process health data or clinical informed consent.
Internal comparative AI testing for TERAL's own purposes will be limited to synthetic or effectively anonymous data. This Policy and the processing mandate do not authorize reusing clinical personal data for TERAL's own research, training, evaluation or improvement purposes. A different use will require a separate assessment, prior information and the applicable legal basis, as well as documented controls.
| Flow | Controller and source of authorization | TERAL's role and evidence |
|---|---|---|
| Website, contact, account, credentials, billing, support and TERAL's own security | TERAL is Controller because it defines these administrative and operational purposes. | It must inform, obtain the applicable acceptance, handle rights requests and document processor providers. |
| Individual sign-up and clinical data uploaded by a professional | Where the professional determines the purpose of the processing, they will be Controller and must obtain and retain the authorization or evidence the applicable exception. Care custody depends on the relationship and the corresponding legal obligations. | TERAL acts as Processor in the operations carried out exclusively on behalf of the professional. Their instructions and scope must be documented through the applicable instrument. |
| Institutional sign-up and administration of the client's users | The institution is Controller of the data of patients, professionals and users it processes within its relationship. TERAL keeps the role of Controller for the purposes of its own that it actually determines —including commercial, account, credential, support or security purposes— and acts as Processor in the operations carried out on the institution's instructions. | TERAL is Processor in the operations carried out exclusively on behalf of and under the instructions of the institution. An agreement, DPA, profiles and a record of additions and removals are required. Its own purposes are governed by the obligations of a Controller. |
| Manual upload of cases, documents and images | The Controller will be whoever determines the purpose of the processing, which may be the institution, the professional or TERAL depending on the operation. The physical act of capturing or uploading does not by itself define that role. | If TERAL acts on behalf of another controller, it will be Processor and must follow its lawful instructions. If it decides a purpose of its own, it will also meet the obligations of a Controller for that purpose. |
| Integration with an electronic health record | The institution that determines the care purpose will be Controller of the corresponding processing. Custody of the medical record is assigned according to the care relationship and the applicable rules; it does not depend solely on ownership of the source system. | TERAL acts as Processor when it carries out the integration exclusively on behalf of and under the instructions of the Controller. Each activation requires a DPA, technical annex, minimum fields, security, logs, testing and production acceptance. If TERAL determines a purpose of its own, it will also meet its obligations as Controller. |
| Teral AI to perform the contracted service | Whoever determines the clinical or institutional purpose will be Controller. The allocation is documented for each service and is not presumed from the engagement of the physician or the technology provider. | TERAL acts as Processor when it performs the service exclusively on behalf of and under the instructions of the Controller; the actual inference providers may act as sub-processors according to their real function. If TERAL determines a purpose of its own, it will meet the obligations of a Controller. Prior controls are defined and verified separately for text, images and metadata, without extending guarantees from one flow to another. |
| RAG and retrieval of documents or historical cases | Whoever determines the retrieval purposes and the authorized sources will be Controller of the corresponding processing. | When acting on behalf of the Controller, TERAL will be Processor. It must apply to the sources and derivatives the applicable access, retention and deletion instructions, and verify compliance. |
| Evaluation, research, training or improvement for a purpose of TERAL's own | TERAL becomes Controller of that own purpose. | Internal comparative testing is limited to synthetic or effectively anonymous data. Reuse of personal data is not authorized; a change of purpose requires separate review. |
Allocation is made by purpose and actual activity. TERAL will be Controller of the purposes it determines and Processor of the operations it carries out exclusively on behalf of and under the instructions of another Controller. TERAL's engagement of a physician or the performance of activities at a clinic does not by itself settle that allocation. Each project must define the information given to the patient, how authorizations are obtained and kept, the recipients and the custody of the medical record. Institutional permission for access or registration and the data subject's authorization serve different functions. Teral Incorporated's involvement in technology procurement must be documented in the chain, without attributing the clinical purpose to it for that reason alone.
TERAL will not sell personal data and will not use clinical information for behavioral advertising. This Policy does not grant TERAL or its providers authorization to train or fine-tune models with personal data from the service. The applicable instructions and agreements must restrict its use to the authorized purposes. Inference to provide the service and internal testing are distinct purposes; the latter are subject to the rule in section 7.
The Platform may offer classification, search, summarization, draft generation, consistency auditing, conversational assistance or information retrieval through artificial intelligence models. These functions support the operation and do not replace clinical judgment, human review or the responsibility of the professional or care entity.
TERAL may classify, organize and cross-check information using rules and criteria defined for each service, and generate observations, alerts or recommendations for human review. These functions may support the review of documentation, billing, procedures or medical prescriptions. Their outputs do not by themselves constitute a finding of fraud or a final decision on care, dispensing, coverage or payment. Recommendations are not binding. The final decision rests with the competent person, who must review the output and may accept or disregard it according to their professional judgment and the applicable rules. The scope, the authorized data, the rules and the responsibilities will be established for each project.
Image analysis functions may produce false positives, false negatives or inconclusive results. The absence of alerts does not prove authenticity, absence of tampering or diagnostic validity. Synthetic demonstrations show the available workflow; they do not certify clinical effectiveness or replace the validation required for the contracted use. If a check could not be run or did not produce a valid conclusion, that status must be distinguished from a verified negative result.
TERAL does not direct its services to minors. If an authorized care flow includes a minor's data, the controller must verify the legal basis, the corresponding representation and respect for the minor's best interests and prevailing rights. Where the processing requires authorization, it must be obtained from the legal representative, first guaranteeing the minor's right to be heard and weighing their opinion according to their maturity, autonomy and capacity to understand. The exceptions and special rules applicable to the care flow will be respected. TERAL will apply restricted access and enhanced security measures.
TERAL may grant access to authorized personnel, clients, professionals, technology providers, advisors and authorities, solely according to purpose, role and need. Where a provider processes data on behalf of TERAL or of a client, it must be bound by obligations of confidentiality, security, instructions, deletion, audit and incidents.
Infrastructure and AI services may include Amazon Web Services —Comprehend and Bedrock with Claude models—, Google Cloud Vertex AI/Gemini and MongoDB Atlas, with processing in United States regions or in the locations of the specific service reported for the project. Teral Incorporated may engage these providers within the service delivery chain, under the applicable instructions and obligations. Optional analytics functions through Google Analytics/Firebase or PostHog require a valid choice under the Cookie Policy and must respect its rejection or withdrawal. Direct connections with other providers, including Anthropic or OpenAI, are not enabled merely because they are technically available. Material changes will be documented and reported in accordance with the applicable law and agreement.
TERAL may carry out international transmissions to infrastructure, database and artificial intelligence providers located in the United States. For each flow, the controller, TERAL S.A.S., Teral Incorporated and each provider or sub-processor must be documented, together with the instructions, DPA, region and applicable measures. If a third party determines its own purposes and receives data as a controller, the flow will be treated as a transfer and the applicable legal mechanism will be verified before sending. Agreements or model clauses do not replace the legal requirements of a transfer.
International scope and additional safeguards. If processing becomes subject to the GDPR because of a relevant establishment, targeted offering or monitoring of the behavior of individuals in the EU/EEA, TERAL will apply to that processing the required information, legal basis, rights, security and transfer rules. Data subjects may exercise, where applicable, access, rectification, erasure, restriction, portability, objection and withdrawal of consent, and may lodge a complaint with the competent authority; GDPR requests will be answered within one month, with the legal extension and a reasoned notice where applicable. A generic acceptance will not be used to authorize solely automated decisions with legal or similarly significant effects. The accessibility of the website or the absence of European sales does not by itself determine the reach of that regime.
TERAL will adopt technical, human, administrative and contractual measures that are reasonable and proportionate to the risk, including identity and access management, encryption where applicable, segmentation, logging, monitoring, backup, testing and vulnerability management. No measure completely eliminates risk, and this Policy does not constitute an unconditional guarantee of security, availability or absence of incidents.
In the event of an actual or suspected incident, TERAL will activate its procedure for analysis, containment, preservation of evidence, remediation and notification. Where it acts as processor, it will inform the controller without undue delay in accordance with the agreement. Notifications to data subjects or authorities will be made by the party under the obligation, within the applicable deadlines and conditions.
TERAL will retain data for as long as necessary for the purposes reported, the controller's lawful instructions and the applicable legal or defense obligations. The term of the agreement does not justify retaining unnecessary data nor does it prevent processing a well-founded deletion request.
Requests may be submitted through the email addresses or the address for notices in section 1. They must identify the data subject or their representative, describe the request and the relevant facts, indicate a channel for a response and attach the documents the requester wishes to rely on. Inquiries will be addressed within a maximum of ten (10) business days from receipt; if this is not possible, the reason and the new date will be communicated, which will not exceed five (5) business days after expiry of the initial term.
Complaints will be addressed within a maximum of fifteen (15) business days from the day following receipt. If the complaint is incomplete, a request to cure will be issued within five (5) days of receipt; if two (2) months elapse from the date of that request without the information being provided, the complaint will be deemed withdrawn. Where it is not possible to resolve within the initial term, the reason and the new date will be communicated, which will not exceed eight (8) business days after expiry of that term.
TERAL will verify the identity and, where applicable, the representation of the requester, requiring only the information necessary to process the request. It will record the request, forward it to the competent area and respond through the channel indicated. Upon receipt of a complete complaint, it will add to the database the annotation «complaint in process» and its reason within the following two (2) business days, maintaining it until resolution. Extensions will be communicated before expiry of the initial term.
If the request concerns data processed exclusively as processor, TERAL will forward it to the competent controller and will cooperate in accordance with the DPA. Where it is not competent to resolve a complaint, it will refer it to the appropriate party within a maximum of two (2) business days and will inform the requester.
The website and the applications use technologies necessary for operation and security. Optional analytics, including Google Analytics/Firebase and PostHog on the relevant surfaces, requires a prior valid choice and can be rejected or withdrawn from "Cookie preferences". It may process browser or account identifiers, session and usage events; it is not presented as exclusively anonymous. Contractual acceptance or access to the service does not by itself authorize that analytics. The inventory distinguishes active and removed technologies and explains their provider, purpose, browser lifetime and controls at https://teral.ai/es/cookies and https://www.chat.teral.ai/cookies. The lifetime of a cookie is not the same as the retention of events on servers.
TERAL will publish the version and effective date of this Policy and will retain evidence of previous versions. It will inform data subjects of substantial changes in a timely manner before applying them and will obtain a new authorization where applicable. This includes material changes in purposes, sensitive categories, providers, regions, roles or AI uses.
Evidence of acceptance or acknowledgment may include the version or hash of the text, the identity or account, the date, time and time zone, the channel and the acceptance event. An IP address or other additional signal will be included only if necessary and proportionate. That evidence does not turn a general acceptance into a valid authorization for sensitive purposes that were not disclosed.
Records of contractual acceptance, acknowledgment of the notice, processing authorization and cookie choice will be kept separately, with the minimum necessary identifier, date and time, channel, purpose, version of the text presented and decision. They will be kept with restricted access and the possibility of later consultation; they will not be reused for marketing, and no additional data unnecessary to evidence the action will be collected.
This edition 2.11, dated November 9, 2026, enters into force upon its effective publication on TERAL's website, the date of which will be shown next to the published text. It supersedes the previous version without retroactive effect and with the information or new authorization required under section 19. The retention of each category is governed by section 14 and the applicable obligations. TERAL will retain evidence of the published versions.
Book a demo and we'll show you the impact with your network's own numbers.