AndesLex Legal Center

AndesLex Privacy Policy

Version v1.2 · Last updated 2026-07-10
operational reference pending owner legal review
Descargar esta versión
Esta página reproduce el documento versionado y fechado que se identifica arriba. Su publicación no convierte el texto, por sí solo, en prueba de cumplimiento, seguridad, configuración efectiva ni suficiencia legal.

AndesLex Privacy Policy

Last updated: July 10, 2026 Effective date: April 2, 2026 Website: https://andeslex.cl Operator: AndesLex (Franco Lavin, sole proprietor), Santiago, Chile

This Privacy Policy explains how AndesLex collects, uses, stores, shares, protects, retains, and deletes personal data and other user data processed through the AndesLex service, including identity data obtained through Google Sign-In.

1. Roles and Scope

The legal role applicable to particular data depends on the deployment, the parties, their instructions, and any agreement actually executed. This public reference does not itself determine controller, processor, service-provider, or subprocessor status. Organizational customers remain responsible for their own notices, authority, legal bases, and end-user requests where applicable.

2. Data We Access and Collect

2.1 Google Sign-In Data

When you use Google Sign-In, AndesLex accesses only the Google account data needed to authenticate an existing authorized identity and maintain its session, such as:

  • email address
  • display name
  • profile image URL

For the current authentication flow, AndesLex requests only the Google access needed to sign you in and manage your AndesLex session. No broader Google data integration is represented by this reference.

2.2 Platform and Workspace Data

As part of normal use of AndesLex, we may collect or generate:

  • tenant, account, and workspace administration records;
  • tasks, action plans, assignments, and operational workflow state;
  • compliance findings, legal analysis outputs, and generated reports;
  • evidence references, traceability records, Proof of Decision (PoD) records, and artifact metadata;
  • audit logs, event trails, and system operations metadata;
  • support requests, bug reports, and diagnostic information you choose to submit.

2.3 Technical and Security Data

We may automatically process technical data needed to operate and secure the service, such as:

  • browser and device metadata;
  • IP address and session metadata;
  • access timestamps, login events, and service logs;
  • error, abuse-prevention, and security monitoring records.

3. How We Use Data

3.1 Google User Data

We use Google user data only for the user-facing functionality you requested, including:

  • authentication and access control
  • session management for existing authorized accounts
  • displaying your profile identity inside the platform

We do not use Google user data for:

  • advertising;
  • sale, resale, or licensing to data brokers or other third parties;
  • unrelated marketing purposes;
  • training or improving generalized, shared, foundational, or frontier AI/ML models.

3.2 Platform Data

We use platform and workspace data to:

  • deliver compliance, governance, legal, and operational workflows requested by authorized users;
  • generate findings, reports, and governed outputs;
  • preserve auditability, traceability, and evidence integrity;
  • secure the service, investigate abuse, and troubleshoot incidents;
  • maintain, support, and improve the reliability of the service.

4. How We Share Data

We do not sell personal data or Google user data.

We may share or transfer data only in the following limited cases:

4.1 Infrastructure and Service Providers

We use service providers to operate AndesLex, such as providers for hosting, database, storage, authentication, logging, and support tooling. These providers process data only to help us deliver the service and under applicable contractual or legal safeguards.

4.2 AI and Processing Providers for User-Facing Features

Selected AndesLex workflows may use third-party processing providers to generate or assist with user-facing legal or compliance analysis, including OpenAI-based processing in selected flows where that runtime path is enabled.

When we use such providers:

  • we send only the data reasonably necessary for the requested feature;
  • we try to minimize or pseudonymize data where appropriate to the workflow;
  • we use the provider only to perform the requested processing task for AndesLex;
  • Google Sign-In data is not sent for unrelated model training or improvement.

4.3 Legal and Regulatory Requirements

We may disclose data when required by applicable law, court order, lawful governmental request, or regulatory obligation.

4.4 Corporate Transaction or Protection Scenarios

We may disclose limited data where necessary to investigate abuse, protect the security or integrity of the service, or in connection with a merger, acquisition, financing, or sale of assets, subject to applicable legal requirements.

5. Data Storage and Protection

5.1 Where Data Is Stored

In current AndesLex deployments, platform data is primarily stored using:

  • Supabase-managed PostgreSQL for application and operational records; and
  • Supabase-managed object storage or equivalent storage rails where a deployed workflow actually stores artifacts or files.

5.2 Security Measures

We implement technical and organizational measures designed to protect data, including:

  • encryption in transit using HTTPS/TLS;
  • encryption at rest provided by underlying database and storage infrastructure;
  • application, database, and storage access controls on the paths where they are configured and verified; this policy does not certify complete RLS, grant, policy, effective-role, or tenant-isolation closure;
  • audit logging and event trails in selected instrumented flows;
  • integrity protections, including hashes for selected evidence and artifact flows;
  • session and authentication controls for account access.

5.3 How We Handle Google User Data

Google account profile data used for authentication may be stored as part of authenticated account records and is subject to the controls and limitations described here.

6. Data Retention and Deletion

6.1 Retention

We retain different categories of data for different periods:

  • account and profile data: while needed to operate an active account and afterward only for a documented operational, security, contractual, or legal reason;
  • OAuth and session tokens: only as long as needed to maintain active authentication, until logout, disconnection, revocation, expiry, or other session termination;
  • workspace, analysis, and operational data: for the duration of the service relationship and for any additional period reasonably necessary for support, auditability, contractual enforcement, or legal obligations;
  • audit and traceability records: as required by system retention policies, contractual commitments, and applicable law.

6.2 Deletion Requests

You may request deletion of your personal data by contacting [email protected].

Upon a valid request, AndesLex will, as applicable:

  1. delete or anonymize personal data we control;
  2. revoke or remove locally stored Google-connected session credentials that remain associated with your account, where applicable;
  3. stop further Google Sign-In access tied to the disconnected authorization; and
  4. confirm completion or explain any remaining legal or operational retention basis.

6.3 Retention Exceptions

Some data may be retained despite a deletion request where retention is required or justified by applicable law, contractual obligations, security investigations, fraud prevention, or the need to preserve auditability and evidence integrity.

6.4 Google Account Revocation

You can revoke AndesLex's access to your Google account at any time through your Google Account permissions. After revocation, AndesLex will stop new Google API access tied to that authorization and handle remaining stored tokens or session state according to this policy and our retention rules.

7. Your Rights and Requests

Subject to applicable law, you may have rights to:

  • access your personal data;
  • request correction of inaccurate data;
  • request deletion of personal data;
  • object to or restrict certain processing; and
  • request portability of certain data.

For requests relating to AndesLex-controlled account or support data, contact [email protected].

If AndesLex is processing content on behalf of an organizational customer, we may direct you to that customer where it acts as the primary controller for the relevant data.

8. Google API Services User Data Policy

AndesLex's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

For the current Google Sign-In surface, Google identity data is used only for authentication and session establishment for an existing authorized account, subject to the explicit authorization boundary described above.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will publish the updated version on the applicable legal page and update the "Last updated" date above. Material changes may also be communicated in-product or by another appropriate channel.

10. Contact

For privacy questions, deletion requests, or complaints:

Email: [email protected] Responsible party: Franco Lavin Location: Santiago, Chile

Back to secure access