Privacy Policy
Last updated: July 26, 2026 · Version: privacy-notice-en-2026-07-26 · Effective: July 26, 2026
1. Who processes data and in what role
NuvaMed SpA ("NuvaMed"), RUT 78.385.718-9, with its publicly stated location in Las Condes, Santiago, is the controller for processing it determines directly, including professional accounts, contracting and billing, support, security, abuse prevention, and authorized commercial communications. If public-site analytics is enabled later, NuvaMed will be the controller for that processing and must respect the visitor's informed preference.
For clinical records and other patient data processed to deliver healthcare, the healthcare provider —the professional or institution— determines the care purpose and retains the custody and responsibilities assigned by healthcare law. For those activities, NuvaMed provides technology as a processor acting on the provider's documented instructions, without prejudice to NuvaMed's own legal obligations.
Before clinical production processing is enabled, the provider and NuvaMed must execute the applicable data processing agreement. Publishing this policy or a contract template does not replace execution and verification of that agreement.
The responsible party and rights channel therefore depend on the purpose. Requests about a clinical record are coordinated with the provider treating the patient; NuvaMed receives or routes the request where appropriate.
Contact: contacto@nuvamed.cl
2. Legal framework
This policy describes processing in light of current Chilean law and obligations applicable to healthcare providers, including:
- Ley 19.628 — Protection of Private Life
- Ley 20.584 — Patient Rights (confidentiality of clinical records)
- Ley 21.331 — Recognition and Protection of the Rights of Persons in Mental Health Care
- DS 41/2012 — Regulation on clinical records
Ley 21.719 was published, and its principal amendments enter into force on December 1, 2026. NuvaMed is adapting its contracts, controls, and procedures for that date; this reference does not mean that a future obligation is already in force or replace an assessment of each processing activity.
3. Data we collect
3.1 Healthcare professional data
- Name, email, phone, RUT
- Specialty and registration number (SIS/Superintendencia)
- Billing information
- Video-call integration credentials (Zoom and/or Google — encrypted OAuth tokens), if the professional chooses to connect them
3.2 Patient data
- Full name, RUT, date of birth, contact information
- Health insurance (FONASA, ISAPRE, PRAIS)
- Clinical data: diagnoses, medications, clinical notes, risk assessments
- Wellness portal data (mood self-reports, medication adherence)
- Appointment, telemedicine, consent, representative, and care-related communication data
- When the AI assistant is enabled or used: session audio or transcript, encrypted recovery copies, encrypted text segments and partial facts, and resulting drafts or notes
3.3 Technical data
- Audit logs (clinical record access, modifications)
- IP address, browser user agent, session identifiers, authentication, and security events
- On the public site, while non-essential analytics remains disabled: only technical data needed to deliver and secure the page and respond to expressly requested actions
- Support messages, communication-delivery data, and technical error diagnostics
4. Purpose of data processing
- Provision of electronic clinical record services
- Support for the provider's regulatory workflows (for example, GES/AUGE or Ley 21.331), without executing or certifying the required acts
- Preparation of editable drafts of prescriptions, epicrisis, certificates, and transfer forms; professional review, signature, and issuance are required
- Communication between healthcare professionals (CareLink network)
- Telemedicine videoconferencing (integration with Zoom and/or Google Meet, at the professional's choice)
- Appointment reminders and confirmations by email, with a calendar invite (.ics) and a video-call link
- Billing and electronic tax documents (SII DTE)
- Authentication, account administration, support, and operational continuity
- Prevention, detection, and investigation of fraud, abuse, and security incidents
- Clinical assistance with AI when the feature is enabled and the applicable authorization or other basis exists; the result remains subject to professional review
- Measurement of public-site use and service improvement, according to applicable preferences
5. Legal basis
The applicable basis depends on the actor, purpose, and type of data. Delivery of this notice provides information about processing and is not, by itself, consent for every purpose.
- Healthcare and provider duties: the provider determines the basis that permits creation, maintenance, and use of the clinical record, including retention duties and any authorization or consent that applies. NuvaMed processes the data on the provider's instructions
- Express authorization under Ley 19.628 in force through November 30, 2026: where no special law authorizes processing, NuvaMed separately requests informed written authorization for professional-account, security, contracting, and billing data that is necessary for the service. Acceptance of the Terms and acknowledgment of this notice do not replace that authorization
- Contractual relationship: defines the purposes needed to administer the account and provide and bill for the service, without replacing an authorization required by the currently effective Ley 19.628
- Legal obligations: retention of clinical records, tax documentation, handling rights requests, and other applicable requirements
- Specific authorization or consent: where the law or optional nature of a feature requires it, for example certain recordings, AI uses, marketing, or non-essential analytics. Declining an optional feature does not prevent care through applicable alternatives
- Security and abuse prevention: under the powers, duties, and conditions recognized by applicable law and contracts. From December 1, 2026, legitimate interest will be invoked only where Ley 21.719's requirements are met
5.1 Express authorization for necessary account data
Under article 4 of Ley 19.628 in force through November 30, 2026, registration or re-acceptance presents a separate action with this scope: “I expressly authorize NuvaMed SpA to process the personal data strictly necessary to administer and authenticate my account, provide and protect the service, handle support, prevent and investigate fraud, abuse, and security incidents, and manage the plan, billing, tax documents, and necessary transactional communications.”
The authorization covers name, RUT, contact details, profession, professional registration, institution or practice, account and session identifiers, authentication and security events, support requests, subscribed plan, billing details, and payment metadata NuvaMed receives from its payment provider. NuvaMed does not request or store complete card details under this authorization.
These data will not be disclosed to the public. They may be disclosed only to processors and providers needed for the stated purposes, to the extent described in this notice and subject to applicable contracts and controls.
This authorization is necessary to create and operate a professional account. If it is not granted, NuvaMed cannot open or maintain that account. It does not authorize marketing, non-essential analytics, recordings, AI features, or the processing of patient clinical data; those purposes require their applicable basis and, where required, a separate optional choice or specific consent. Declining an optional purpose does not prevent use of functions that do not require it.
The authorization may be revoked in writing for future processing by emailing contacto@nuvamed.cl. Revocation is not retroactive and may require account closure or restriction where processing is indispensable to provide or protect the service, without affecting legal retention duties.
6. Third-party integrations
6.1 Zoom Video Communications
NuvaMed integrates with Zoom for telemedicine sessions. When a professional connects their Zoom account:
- We store encrypted OAuth2 tokens (Fernet, AES-128-CBC) with a unique derived key per professional
- We create Zoom meetings on behalf of the professional for scheduled appointments
- If the professional has cloud recording and transcription enabled in Zoom, we download the VTT transcript to generate a draft clinical note using AI. The original recording remains subject to the professional's Zoom account configuration and retention
- The raw VTT file is not intentionally stored as a separate clinical document. Drafts, notes, and encrypted transcript fragments or extracted facts may remain where needed for the active clinical, continuity, recovery, or audit purpose
- On disconnection, we delete the active credential from active systems and attempt to revoke the token with Zoom; external revocation may depend on the provider's response
- Zoom webhook communications are validated via HMAC-SHA256 signature with replay protection
- When the app is deauthorized from the Zoom Marketplace, the active credential is deleted from active systems. Restricted copies may remain until the backup-deletion cycle completes
For more information, see Zoom's Privacy Policy.
6.2 Google — Sign-In
We offer Google Sign-In. When a user chooses this option, we access only their name, email address, and profile picture from the Google account, for the sole purpose of creating or authenticating their NuvaMed account. We do not access any other Google account data through sign-in.
6.3 Google Calendar and Google Meet (telemedicine)
If a healthcare professional chooses to connect their Google account to generate Google Meet video-call links, NuvaMed requests the https://www.googleapis.com/auth/calendar.events scope of the Google Calendar API. With this permission:
- What we do: when a telemedicine appointment is scheduled, we create a single event in the professional's calendar with an automatically generated Google Meet link. We update that event if the appointment is rescheduled and delete it if the appointment is canceled.
- What we do NOT do: we do not read, list, or access the professional's existing events in Google Calendar. We only manage the events that NuvaMed creates for telemedicine appointments. We do not use Google Calendar data for profiling, advertising, or any purpose other than the one described.
- What we store: only the encrypted Google OAuth2 tokens (Fernet, AES-128-CBC with a unique derived key per professional), the email address of the connected Google account, and the calendar event identifier and Meet link associated with each appointment. We do not store the contents of the professional's calendar or any other Google account data.
- Revocation: the professional can disconnect the integration in the application. We delete the active credential from active systems and attempt revocation with Google; restricted copies may remain until the backup cycle completes. They can also revoke access directly from their Google account permissions page.
Limited Use: NuvaMed's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data obtained through Google APIs is used exclusively to provide or improve user-facing features within NuvaMed; it is not transferred to third parties except as necessary to provide those features, for security purposes, to comply with applicable laws, or in connection with a merger or acquisition; and it is not used or sold for advertising purposes.
6.4 Google Gemini (AI)
NuvaMed uses Google Gemini or Vertex AI, depending on the active configuration, for clinical-assistance functions: summaries, analysis and pre-session briefings, and —when the professional uses AI Scribe— transcription and structuring of draft clinical notes from session audio or a transcript.
Audio or text is transmitted encrypted in transit to the AI service. Minimization and pseudonymization controls are applied before or after transmission depending on the technical route; audio necessarily contains the original conversation during transcription and cannot be considered anonymous. For large recordings, the application uses Google's Files API and attempts to delete the file immediately after processing. If deletion fails or expires, Google may retain the file until its automatic expiry, currently up to 48 hours.
To support recovery after an interruption, certain AI Scribe routes may store an encrypted audio copy in NuvaMed infrastructure for a configurable technical period from 1 to 90 days. Encrypted text segments and partial facts may also be retained for continuity and traceability, in addition to the draft or clinical note reviewed and signed by the professional. Applicable retention is described in section 8 and must match the information shown to the patient before the feature is activated.
NuvaMed does not use clinical content for advertising or to train its own models. Google's use and retention terms depend on the active service and contract. Processing may occur outside Chile where a route without regional residency is used; production configuration, contractual terms, and transfer safeguards must therefore be verified for the enabled feature.
6.5 Infrastructure, payments, communications, and monitoring
- Google Cloud Platform: application hosting, databases, storage, keys, queues, and backups
- Flow.cl and Bsale: payments, billing identity, amounts, and electronic tax documents
- Email providers: transactional messages to professionals and patients; content depends on the requested communication
- Twilio/WhatsApp: messaging where an institution enables a compatible function
- Sentry: error monitoring and technical diagnostics with filters intended to reduce personal data
These providers receive only the categories needed for the relevant function. Their effective region may differ from the application's primary region and depends on provider and configuration.
6.6 Public-site analytics
Non-essential analytics is disabled on the public site while no preference mechanism is available to support an informed choice before loading it. Local events prepared by a page are not transmitted to Google Tag Manager. If analytics is enabled later, this notice and the provider register must identify the tags, data categories, recipients, retention, and applicable transfers; clinical-record data must never be sent to those tools.
7. Security
- Encryption in transit using TLS and encryption at rest managed by Google Cloud for configured services
- Additional application-level encryption for selected sensitive fields, including integration tokens and selected clinical content; this does not mean that every field uses the same additional layer
- Primary application infrastructure on Google Cloud Platform, region southamerica-west1 (Santiago, Chile); integrations and some AI routes may process data in other regions
- Authentication with JWT + httpOnly cookies, role-based access control
- Institution-isolation controls and audit records for sensitive actions covered by the platform
- Editing and addendum controls intended to preserve clinical-note traceability
No security measure eliminates all risk. NuvaMed reviews its controls and handles vulnerabilities and incidents according to their severity.
8. Data retention
- Clinical records: the healthcare provider must retain them for the applicable legal minimum, currently at least 15 years. Account deactivation does not end that duty
- Account, contract, billing, support, and security data: for the relationship and afterward as necessary for contractual, tax, security, claims-defense, and operational-closure duties
- Audit records: for the period required for traceability, security, and provider duties; deletion is restricted where they must remain evidence
- Integration credentials: while connected; active credentials are deleted or revoked on disconnection, subject to restricted backup-deletion cycles
- AI Scribe recovery audio: a configurable technical period from 1 to 90 days; the current code default is 30 days. It may be deleted sooner when the workflow permits. Retention requires the applicable optional consent scope
- Large files sent to Gemini: immediate deletion is attempted; after a deletion failure, the provider may retain the file until its automatic expiry of up to 48 hours
- Transcripts and AI results: the raw Zoom VTT file is not deliberately stored as a separate document. Drafts, clinical notes, and encrypted transcript fragments or extracted facts may be retained for the applicable clinical, continuity, recovery, or audit purpose
- Backups: copies removed from active systems may remain until the restricted backup and recovery cycle completes
9. Rights and requests
Personal data subjects may exercise their rights to:
- Access: request a copy of the personal data being processed
- Rectification: correct inaccurate or incomplete data
- Deletion, cancellation, or blocking: request cessation or restriction of processing where applicable, subject to legal retention obligations
- Opposition: object to data processing under certain circumstances
- Portability or structured delivery: where applicable law recognizes that right, including delivery of the clinical record in the cases provided by Ley 20.584
- Withdrawal of authorization: withdraw consent for future uses where consent is the basis, without affecting prior processing or retention obligations
Requests may be made through the in-app privacy portal or by writing to contacto@nuvamed.cl. Where a request concerns a clinical record, the requester may be asked to identify the responsible healthcare provider so NuvaMed can route or coordinate it. NuvaMed will acknowledge and respond within the applicable legal period, including any permitted extension and reason.
10. Breach notification
When an incident affects personal data, NuvaMed assesses its scope, contains and documents the incident, informs the responsible healthcare provider where appropriate, and makes communications required by applicable law and contracts without undue delay. The recipient and timing depend on the incident's nature, risk, and the rules in force; this policy does not state a universal 72-hour deadline.
11. International transfers
Primary application infrastructure is hosted on Google Cloud Platform in Santiago, Chile. Some integrations, messaging, monitoring, and AI routes may process data outside Chile. NuvaMed must identify the active service and region, limit transfer to what is necessary, and apply the contract, authorization, or other safeguard required for the relevant processing. A non-regional AI route must not be described as processing exclusively in Chile.
12. Modifications
We may update this policy to reflect legal, operational, or provider changes. We will publish the date and version, retain history, and notify material changes before they take effect. Where a new purpose requires consent, NuvaMed will request a specific choice; continued use does not replace that consent.
13. Contact
For privacy and data protection inquiries:
NuvaMed SpA
RUT: 78.385.718-9
Publicly stated location: Las Condes, Santiago, Chile
Email: contacto@nuvamed.cl
Website: nuvamed.cl