VaarioEspañol

Legal

Confidentiality, Security and Document Lifecycle Policy

Version 1.0 · Last updated: 18 November 2026

Not yet in force. Reviewed by counsel; it takes effect on the date Vaario OÜ publishes it, once the company's registry details are filled in. The English text is a translation of the Spanish one, pending counsel's approval.

Confidentiality commitment and contractual effect

Effective date: [public launch date]. Official URL: https://vaario.app/legal/security

At Vaario OÜ ("Vaario", "we" or the "Company") we understand that the documents you analyse on https://vaario.app (the "Platform") — whether contracts, financial reports, technical manuals, commercial proposals or corporate policies — contain sensitive and strategic information for your work.

This Policy describes openly our security architecture, the technical and organisational controls that protect the confidentiality of your files, and the full lifecycle of each document from upload to final deletion. This document forms an integral part of our Terms and Conditions of Use, our Privacy Policy and our Data Processing Agreement — DPA, whose content prevails in the event of a difference in interpretation.

1. Core Principles of Confidentiality

  • Exclusive ownership by the User: you (or your Organisation) keep at all times one hundred per cent (100%) of the ownership of and rights in the documents you upload and the results obtained. Vaario claims no ownership or commercial exploitation rights over your information.
  • Absolute "zero AI training" guarantee: no uploaded document, extracted text, request (prompt), annotation or generated output is used to train, fine-tune, distil or improve our own or third-party providers' artificial intelligence models (including Amazon Web Services — AWS Bedrock).
  • Strict logical isolation (multi-tenant isolation): each account's documents and workspaces are logically isolated at database and storage level, ensuring that no other customer can view, query or cross-reference your files.
  • Minimisation and automatic deletion: we keep your documents only for as long as needed to provide the service, purging them automatically once they have gone unused for the period you choose in your account (thirty (30) days by default).

2. Map of the Document Content Lifecycle

To give full technical visibility of how your files travel and are protected in our hybrid architecture (deterministic algorithms and artificial intelligence), we set out each stage of the content lifecycle:

Lifecycle stageWhat happensInfrastructure and locationSecurity and protection controls
1. UploadThe user selects and uploads a file from their web browser to the Platform.Frontend on Vercel (functions in the EU, Dublin) and API on Railway (Amsterdam, EU).Encrypted transmission over HTTPS / TLS 1.2 or higher and perimeter attack mitigation through Cloudflare.
2. Extraction and deterministic processingThe system reads the document, extracts the text and runs literal or structural comparisons based on algorithmic rules (no AI involved).Backend API on Railway (Amsterdam, EU).Isolated in-memory processing in secure containers in the European Union, with no document content in the logs (scrubbed logs).
3. Active storageThe original file, the extracted text, metadata and annotations are stored so they can be consulted and managed in the workspace.Database and object storage on Supabase (Ireland, eu-west-1, EU).Encrypted at rest by the provider (AES-256); the extracted text is also encrypted by the application before it is stored (AES-256-GCM, authenticated encryption); access restricted by Row Level Security (RLS) policies and signed URLs that expire within one hour at most.
4. AI analysis and inferenceWhen the user asks for a summary, semantic extraction or a question in the AI chat, the necessary context is sent to the language model.AWS Bedrock (EU regions only: Ireland, Germany, Sweden, France, Italy and Spain).Encrypted channel (TLS 1.2+); transient in-memory (RAM) processing during inference; no retention and a contractual prohibition on use for training under the AWS GDPR DPA.
5. Collaboration and notificationsIf the user invites a Guest Collaborator or shares comments, the system sends access links or email notifications.Supabase (EU) and Resend (US entity, with SCCs).Per-document permission control; dedicated invitation links; encrypted SMTP transmission (TLS) and minimal extracts in emails.
6. Export and downloadThe user downloads their original documents, comparison reports or generated summaries to their own device.From Supabase / Railway (EU) to the user's device.Generated on demand through authenticated sessions and encrypted transfer (HTTPS/TLS). Once downloaded, custody of the local file rests with the user.
7. Deletion and backupsAutomatic purge once the chosen period passes without use (30 days by default), with notice 7 days before; or immediate deletion when the file or the account is deleted.Supabase (Ireland, EU).Final deletion from the active production environment and automatic overwriting of encrypted backups within at most ninety (90) calendar days.

3. Technical and Organisational Security Controls

Vaario applies a security and privacy by design and by default approach, backed by the following measures:

3.1. Cryptography and infrastructure security.

  • Encryption in transit: all external and internal traffic between the user's browser, the frontend, the backend services, the database and the AI inference APIs is protected by TLS 1.2 or higher.
  • Encryption at rest: all uploaded files, databases and backups are stored encrypted by the provider using the AES-256 standard; the text extracted from each document is also encrypted by the application (AES-256-GCM) with a key known only to Vaario's server.
  • Perimeter security: continuous protection against denial-of-service (DDoS) attacks, malicious injections and unauthorised automated traffic through a web application firewall (WAF) on Cloudflare.

3.2. Access control and internal governance.

  • Authentication and session isolation: identity management with expiring cryptographic tokens in Supabase Auth, with support for multi-factor authentication (MFA) and strict data isolation by account and Organisation through Row Level Security (RLS).
  • Principle of least privilege: no member of the Vaario team routinely accesses the content of users' documents. Administrative access to the production infrastructure is restricted to the technical staff essential for maintenance or critical support, protected by mandatory MFA, encrypted connections and audit logs.
  • Control of remote access: since part of the technical team works from outside the European Economic Area (specifically from Ecuador), all remote administrative access is governed by binding confidentiality agreements, the European Union's Standard Contractual Clauses (SCCs), a strict ban on unauthorised local downloads of customer data and technical security controls.

3.3. Resilience, continuity and backups.

  • Isolated backups: the database takes automated, encrypted backups, logically isolated from the production environment, to ensure continuity in case of technical failure.
  • Retention and destruction cycle: under our retention policy, unused documents are purged when the period chosen in the account runs out (30 days by default), with an automated notice sent at least 7 calendar days before, and they are destroyed immediately in production when an account is deleted. Encrypted backups rotate and are permanently overwritten within at most ninety (90) calendar days.

4. Important Clarification on Professional Secrecy and Non-Disclosure Agreements (NDAs)

Vaario provides a technical environment designed to protect the commercial confidentiality of your documents. However, in keeping with our duties of contractual transparency:

  • Scope of legal privilege: hosting or processing information in Vaario does not in itself confer or guarantee the status of professional secrecy, lawyer-client privilege or immunity from judicial or administrative orders, whose recognition depends exclusively on the laws that apply in your country of residence or practice.
  • Responsibility to check first: before uploading files subject to confidentiality agreements with third parties (NDAs), critical trade secrets or statutory duties of professional confidentiality, the User or their Organisation is responsible for checking that their contractual commitments or sector rules allow the use of cloud document analysis tools, and for anonymising any sensitive or identifying data beforehand where necessary.

5. Incident, Vulnerability and Audit Management

  • Incident and security breach response: Vaario maintains internal procedures to detect, contain and remedy incidents. If a confirmed security breach affects customers' personal data or documents, we will notify the affected users and the competent authorities within the time limits set in our DPA.
  • Responsible vulnerability disclosure: we work actively with security researchers under our Responsible Vulnerability Disclosure Policy. If you find any possible technical flaw, write to us at once at security@vaario.app.
  • Due diligence for corporate customers (B2B): organisations considering Vaario can request further security documentation or standard compliance questionnaires by writing to privacy@vaario.app.

6. Updates to this Policy

Vaario may update this Confidentiality and Security Policy with immediate effect on publication at https://vaario.app/legal/security to reflect improvements in our technical controls, infrastructure updates or new regulatory standards. Where a change substantially reduces the security guarantees in force, it will be notified at least fifteen (15) calendar days before it takes effect.