How we look after your data
Version 3 · 23 October 2026
The Spanish version prevails; the English version is for information only.
This notice explains which personal data we process on this site and in the An:des service, where it comes from, why, on what legal basis, with whom, for how long and how to exercise your rights under Chilean Law 19.628, as amended by Law 21.719.
Who is responsible
The data controller is Franco Lavín, a natural person who operates AndesLex and Andes Compliance from Santiago, Chile. For any request about your data, write to [email protected].
What data we process and where it comes from
On this site.
- What you type when you request access: name, work email, company, role and the matter you want to solve. You give it to us; we do not obtain it from other sources.
- If you apply as a startup, whether you want one of the places with more time. We do not ask why or ask for a certificate: we do not process data about your health.
- What the server records when it shows you the site: IP address, date and time, page requested and browser type.
- If you talk to Érika on this site: your voice, which is processed in the moment to transcribe it and is not recorded, and the transcript of the conversation. Also whatever you type to her.
In the service.
- Your account: the email, name and picture of the account you sign in with (Google) or the email we send the access code to, and the public part of your passkey. The private key never leaves your device.
- What your organisation puts into An:des: obligations, tasks, plans, findings, analyses, reports, documents, evidence, the proof of each decision (PoD, Proof of Decision) and the audit records of who did what and when.
- Your email, calendar and files, only if you connect them and only what you choose, with your permission and for as long as it lasts.
- If you talk to Érika in the service: the audio of the query, to transcribe it, and the text of the conversation.
- Technical and security data: device, browser, IP address, sessions, access events and error logs.
The people whose data we process are those who visit the site, request access, or use the service on behalf of a customer organisation. This tab’s session storage remembers journey choices and, after a request is submitted, its pending attempt so it can be retried with the same identifier and content. It also keeps a SHA-256 fingerprint and the minimum receipt details to flag a repeat. These data last for this tab’s session. The pending attempt is removed when a new request is started or receipt is confirmed. Persistent storage remembers preferences such as dismissing notices and the language suggestion; request copies stored by earlier versions are removed. The security-key demonstration may use a technical cookie to maintain its illustrative session. Cloudflare may use security cookies, such as __cf_bm or cf_clearance, when applying its protection. Access to the app service uses its session cookies. These mechanisms do not by themselves authorise any further use of the data. Site searches and simulator controls are sent to An:des infrastructure to return the selected result. In the sanitary-authorisation example, its state and any text you edit are also processed there during the query. These queries do not use AI models, write to the database or retain their content on the server. Drafts, conclusions and records from that example remain in this tab’s session; they are not submitted to the health authority.
Why, and on what basis
- To answer your request and arrange your access, including a first look at the rules that may apply to your company, so we arrive prepared. The basis is that you ask us: these are pre-contractual steps taken at your request (art. 13, letter c).
- To provide the service to your organisation: identify the obligations that apply, govern what is missing, prepare decisions and prove each one. There, your organisation is the controller of the data it puts into An:des and sets its legal basis; we process it as processors, on its behalf and under its instructions (art. 15 bis).
- To keep the site and the service secure and to know how many different people visit them, in aggregate figures that identify no one. The basis is our legitimate interest in protecting them and understanding their use, which does not override your rights (art. 13, letter d). Cloudflare counts visits by IP address, without cookies or identifiers in your browser.
- To talk to Érika. On the site, the basis is your consent, which you give when you start (art. 12). We keep the transcript for thirty days as a record of what Érika said, to review her quality and answer for her; that part rests on our legitimate interest (art. 13, letter d). In the service, the basis is set by your organisation, which is the controller.
Only the conversation with Érika on the site rests on your consent. You withdraw it by ending the conversation or not starting it, and that does not affect what was done before.
We do not sell your data or use it for advertising. We do not train artificial-intelligence models with our customers' data.
Artificial intelligence and automated decisions
Érika is an AI. On this site, the consent says so before you start, the screen shows it during the conversation and she says so in her first answer; in the service, every answer states it. She reads, explains and prepares; she does not decide for you or build profiles about you. In the service, every decision is taken by a person with the authority to take it and is signed with their passkey. Érika does not infer emotions from your voice: her style only changes with the music you share, from the public metadata of the track.
For how long
- Form data, while we arrange your access. If no relationship follows, we delete it within six months.
- Server logs, thirty days.
- The transcript of a conversation with Érika on the site, thirty days. The audio is not recorded.
- Service data, for the term of the contract with your organisation and, when it ends, as it instructs: return or deletion, within the period set by the data processing agreement. The proof of each decision is kept for as long as your organisation needs to evidence it.
Who else processes it
Providers that give us infrastructure, email, artificial intelligence, voice, signature and timestamping, as processors, under contract and only for those purposes. Each one receives only what its service needs. We do not transfer your data to third parties. The full list, with what each one receives and does not, lives in the trust center.
- Supabase (United States): database, authentication and files of the service.
- Render (United States): the servers An:des runs on.
- Cloudflare (United States): network, domain names and the visit count.
- OpenAI (United States): in the service, Érika's language model and voice transcription; it receives the query and the document fragments that query needs.
- ElevenLabs (United States): Érika's voice in the service and, on this site, the conversation with Érika, by voice or in writing. On this site, Érika's answers are generated by Claude, Anthropic's language model, through ElevenLabs.
- Google and Microsoft (United States): sign-in and, only if you connect them, your email, calendar and files.
- SendGrid (United States): the notification emails the service sends you.
- The timestamp of each Proof of Decision (PoD): it receives only the SHA-256 hash of the document, never the document.
- Legale and Legaliza (Chile): advanced electronic signature and online notarisation, when your organisation uses them; they receive the document, its attachments and the geolocation of the signer.
Several of these providers process data outside Chile, most of them in the United States. Those transfers are made with the safeguards required by articles 27 and 28 of the law: a data processing agreement with each provider, with confidentiality, security and purpose obligations, and, once the Personal Data Protection Agency recognises adequate levels of protection, in line with that list. Reading, OCR and matching of your documents and of screening run on our own infrastructure (Render and Supabase), without third-party OCR or analysis services. In the service, only the fragments needed to answer a query reach Érika’s model.
Your rights
You can request access, rectification, deletion, objection and portability of your data by writing to [email protected]. We answer within thirty calendar days of your request, a period that may be extended once by another thirty.
When you request rectification, deletion or objection, you may also request, with your reasons, the temporary blocking of your data while we resolve it. We answer that request within two business days and, in the meantime, we do not process that data (art. 11, in relation to art. 8 ter). In the cases of art. 7, you may request blocking instead of deletion.
If your data is in An:des because your organisation put it there, you exercise your rights before it; we help it answer in time. If we refuse your request or do not answer in time, you may turn to the Personal Data Protection Agency.
Security
We protect your data with technical and organisational measures proportional to its risk: encryption in transit and at rest, access separated per organisation, one passkey per act, records of who accesses what and why, and observability without content. If a security breach affects your data, we notify you without delay, and the Agency as the law requires, with what happened, which data it touches and what we did.
Changes
If this notice changes, we publish the new version here with its date. The version in force is the one the app reads.