Skip to content
An:des

Trust center

Decisions backed by evidence

See what supports a decision, what An:des retains and how it can be checked. You can also find the controls, security information and terms of use here.

  1. ISO/IEC 27001The database, the servers and the network, certified by their suppliers, with SOC 2 where they publish it.
  2. 1 passkey per actWhen the app asks you to confirm a decision, your passkey confirms the content presented in that session. When you sign in to the app, that does not by itself confirm the decision. The five-minute window, for one case, only opens if you choose it.
  3. 8 controlsIts own, each with its path in the code and the live proof it requires.
  4. 0 contentIn the traces, only metadata from a closed list: no content.

Proof of Decision

The history of the same appointment

The Proof of Decision links the background, the criterion, the authority, the act and its effects: version, grounds, authority, limits, term, instructions, responses and changes.

  1. The law of that dayThe framework and the sources relevant to the decision.
  2. The reason for departingThe criterion and the justification, preserved.
  3. The risk with its ownerWho knows, decides and answers for what falls to them.
  4. What is missing, with a dateOutstanding items and follow-up, clearly visible.

What went wrong can always be found. With An:des, your response is on record too.

Your organization keeps control of who decides, who acts and what each participant shares.

What its Proof of Decision looks like An illustrative example, not an executed case. The real verification is below.

  1. VersionThe minutes and the power of attorney, in the version that was signed.
  2. GroundsThe articles and the board resolution that appoints the manager.
  3. AuthorityWho could make the appointment and who signed.
  4. Limits and termUp to what amount and until when the new manager acts.
  5. InstructionsWhat the bank and the enabled systems received.
  6. ResponsesThe bank’s confirmation and what is still pending.
  7. ChangesThe previous power, revoked; the work that depended on it, reviewed.
Andes Compliance
AN:DES
Demostración
COMPROBANTE
Nombramiento
CONTENIDO
Ejemplo ilustrativo
SHA-256 DEL CONTENIDO
513b1e6d163d…f5fd
QR · Nombramiento

andescompliance.com

Demonstration content in Spanish.

On iPhone, add it to Wallet. Safari on Mac can add it to your own devices through iCloud.

Verifiable content

SHA-256 · content

513b1e6d163d7b139e64bb417a56b4158606654c40db1241bf98273c6085f5fd

SHA-256 · Wallet file

1510edf0d2cdbad7527ac3587d68de02b62b1f696fd057641f18e9400ae015ffJSON ↗Open the full verifier ↗
Andes Compliance
AN:DES
Demostración
COMPROBANTE
Mi primer encuentro con An:des
CONTENIDO
Una visita. Una huella. Un recuerdo.
SHA-256 DEL CONTENIDO
7b2e61c884d3…71b6
QR · Mi primer encuentro con An:des

andescompliance.com

Demonstration content in Spanish.

On iPhone, add it to Wallet. Safari on Mac can add it to your own devices through iCloud.

Verifiable content

SHA-256 · content

7b2e61c884d3e14ff0741aecf36b368a6888b9c1c3840c8e8e68d5218bb371b6

SHA-256 · Wallet file

959362dab8f829c4406f0f7699ff4a5a4aca3e60063832641bcaf66e0d784d52JSON ↗Open the full verifier ↗

A real sample

The sealing record of the CASE-001 test package, dated 2 November 2025: the package’s SHA-256 fingerprint matches the one in the record and the GPG signatures of the person responsible verify.

Decision

Close and seal the CASE-001 test package

Verified · fingerprint and signatures, Oct 24, 2026

Closed on 2 November 2025

Andes Compliance
AN:DES
Referencia
COMPROBANTE
CASE-001
CONTENIDO
Cerrar y sellar el paquete de prueba
SHA-256 DEL CONTENIDO
84d30a0bf32d…ed80
QR · CASE-001

andescompliance.com

Demonstration content in Spanish.

On iPhone, add it to Wallet. Safari on Mac can add it to your own devices through iCloud.

Verifiable content

SHA-256 · content

84d30a0bf32dff0c486821496980ad8afbd35a01a5015cbeedd2ae3b71e4ed80

SHA-256 · Wallet file

e44a075dbe4e88dafaed3a6f0674d9c40775ab7b8747ba615c25f11725abea41JSON ↗Open the full verifier ↗
What it proves and what it does not

Proves

  • That the package is the same one that was closed: its SHA-256 fingerprint matches the one in the record.
  • Who signed: the GPG signatures on the record and on the report verify with the key of the person responsible.

Does not prove

  • The time before a third party: it dates from November 2025, before the RFC 3161 (FreeTSA) timestamp that An:des puts on a PoD when a person with authority requests it.
  • An advanced electronic signature: the signature is GPG.

See how we check it

Share the record with a link that expires

For an auditor or a regulator: the link shows the record until the date you set, counts every visit and you revoke it whenever you want. It stays in the case history.

An email that arrives, with its acknowledgement

You forward to An:des the official letter you received. An acknowledgement comes back with the SHA-256 fingerprint of the full email and its RFC 3161 timestamp. The decision window opens with the deadline the email sets.

An example, with a synthetic email · Chile

From
Fiscalización (ejemplo) <[email protected]>
To
Encargado de prevención (ejemplo) <[email protected]>
Subject
Requerimiento de información (correo de demostración)
Date
Mon, 19 Oct 2026 09:14:00 -0300
Correo de demostración del sitio de An:des. No lo envió ninguna autoridad y no se refiere a una organización real.

En el marco de una fiscalización de la cadena de frío, se solicita remitir:

1. El registro de temperatura de las cargas refrigeradas de septiembre de 2026.
2. La respuesta del transportista al desvío de temperatura del 18 de septiembre de 2026, con su evidencia.

Plazo: a más tardar el 3 de noviembre de 2026.

Fiscalización (ejemplo)

Download the example email

Andes Compliance
AN:DES
Demostración
COMPROBANTE
Acuse de ejemplo
CONTENIDO
Requerimiento de información
SHA-256 DEL CONTENIDO
e67b8f1fcca2…3cf1
QR · Acuse de ejemplo

andescompliance.com

Demonstration content in Spanish.

On iPhone, add it to Wallet. Safari on Mac can add it to your own devices through iCloud.

Verifiable content

SHA-256 · content

e67b8f1fcca2f1cc216c6d40f6268116db7a67f39ad26127d28b06280b0a3cf1

SHA-256 · Wallet file

5bd0c3cb07469b0a1d0526de3bc01c85e06eebedfab4e7ea3ec33d214dda0316JSON ↗Open the full verifier ↗

Your browser calculates the fingerprint over the example file. The app requests the RFC 3161 timestamp when it receives the email.

The sample email is in Spanish.

Back to the appointment

Infrastructure

Certified by its suppliers

Your data lives on infrastructure with ISO/IEC 27001:2022 and SOC 2 Type II: the database and the servers; the network, with ISO 27001, 27018 and 27701. The models behind Érika and your AI are certified too. Every line carries its source and its reading date.

What comes from a supplier is stated as theirs, with its source and its date.

See the certifications (6)
SupplierCertifiesSourceRead on
SupabaseISO/IEC 27001:2022 (April 2026) and SOC 2supabase.com/blog/supabase-is-now-iso-27001-certified · supabase.com/docs/guides/security/soc-2-compliance2026-10-09
RenderISO/IEC 27001:2022 (December 2024) and a SOC 2 Type II report from the Organization tierrender.com/blog/render-iso-27001-and-document-center2026-10-09
CloudflareISO 27001:2022, ISO 27018:2019 and ISO 27701:2019cloudflare.com/trust-hub/compliance-resources/iso-certifications2026-10-09
OpenAI (API)SOC 2 Type 2, ISO/IEC 27001:2022, 27017, 27018 and 27701 for the API, and ISO/IEC 42001:2023trust.openai.com2026-10-09
AnthropicISO/IEC 42001:2023, ISO 27001:2022 and SOC 2 Type I and IIsupport.claude.com, article 100158702026-10-09
ElevenLabsTrust center on request; zero-retention mode on enterprise planselevenlabs.io/enterprise · compliance.elevenlabs.io2026-10-09

Controls

Eight controls that put your information under your control

Every control, with what it does and how it is checked.

  1. One passkey per actConfirm with your passkey the decision in front of you. The confirmation stays linked to your account and to the content presented.
    How it is checked

    On andeslex.cl: a decision not confirmed with your passkey stays blocked; once confirmed, it is linked to your account, your session and the content presented, and its authority and its effect are checked separately; with the window open, a decision on another case asks for the passkey again.

  2. The proof of a decision, with fingerprint and sealSHA-256 fingerprint and RFC 3161 seal (FreeTSA) when an authorized person asks.
    How it is checked

    On andeslex.cl: export a PoD and verify the timestamp with openssl outside An:des.

  3. The record of rights requestsA record of rights requests with receipt, deadline, answer and evidence fingerprint.
    How it is checked

    On andeslex.cl: see a recorded rights request, with its receipt, deadline and answer.

  4. Delegation to your AI with permissions and validityOAuth with per-case delegation, actions, end date and revocation.
    How it is checked

    On andeslex.cl: connect Claude via MCP, revoke the permission and check that the next call fails.

  5. Observability without contentTraces to Langfuse with a closed list of metadata.
    How it is checked

    On andeslex.cl: review a live trace and confirm it has no content or identifiers.

  6. Érika identifies herself as an AIEvery chat reply shows “Érika is AI” (EU AI Act, Article 50).
    How it is checked

    On andeslex.cl: a live Érika answer with the identification present.

  7. Érika does not infer emotions from your voiceHer style changes with the mode, your words and the music you share (EU AI Act, Article 5). lib/personality_router · lib/erika/vibeProfileV1.server · vibeTrackAdapters.server · Spotify or SoundCloud oEmbed
    How it is checked

    On andeslex.cl: say the same message to her in two tones of voice and check that her style does not change; share a track and check that only its URL travels.

  8. Human oversight by designTexts with an external effect wait for approval by someone in a responsible legal role (EU AI Act, Article 14).
    How it is checked

    On andeslex.cl: an external effect prepared by Érika stays blocked until the signed decision.

Subprocessors

Who receives what

Each supplier receives only what its service needs, with name, country and data. Reading, OCR and cross-checking are done by An:des’ own code, hosted on Render and Supabase, without third-party OCR or analysis services; only the fragments a query needs go to Érika’s model.

Eleven suppliers, each with what it receives and what it does not.

See the subprocessors (11)
EntityCountryServiceWhat it receivesWhat it does not receive
· Supabase, Inc.United StatesDatabase, authentication and files, in São Paulo (Brazil)The service data, separated by organizationYour private keys or your third-party passwords
Render · Render Services, Inc.United StatesThe servers for the app and its own services, in Oregon (United States)What the app processes while it runsCopies of your documents outside the service
Cloudflare · Cloudflare, Inc.United StatesNetwork, domain names, tunnel and visit countTraffic in transit and network metadataCookies or identifiers in your browser
OpenAI · OpenAI, L.L.C.United StatesIn the service, Érika’s language model and voice transcriptionThe query and the document fragments that query needs; the audio, to transcribe itYour full documents or your credentials
· ElevenLabs, Inc.United StatesÉrika’s voice in the service
On this site, the conversation with Érika by voice or in writing; there her answers are generated by Claude, from Anthropic, through ElevenLabs
The text of the answer, to speak it
On this site, the conversation: your voice or what you write
Recordings: the audio is not recorded
Google · Google LLCUnited StatesSign-in; Gmail and Drive only if you connect themThe account’s email, name and picture; whatever you connectNothing beyond what you authorize
Microsoft · Microsoft CorporationUnited StatesEmail and calendar, only if you connect them (Graph)Whatever you connectNothing if you do not connect
SendGrid · Twilio Inc. (SendGrid)United StatesNotification emailsThe address and the content of the notificationCase documents or attachments
Legale y Legaliza · Legale · Legaliza (Fundación Red Notarial)ChileAdvanced electronic signature and online notarial legalization, once connectedThe document, its annexes and the signer’s geolocationNothing until your organization signs
Anthropic · Anthropic, PBCUnited StatesChannel: Claude enters An:des via MCP when you delegate
On this site, Claude generates Érika’s answers, through ElevenLabs
Whatever you delegate from your Claude
On this site, the conversation, through ElevenLabs
Nothing on An:des’ own initiative
FreeTSA · FreeTSA (RFC 3161 timestamp)Outside ChileTimestamp for a proof of decision, when a person with authority requests itOnly the SHA-256 fingerprintNever the document

What runs in-house and the public sources consulted, by governance.

See what runs in-house (16)
GovernanceWhat it doesWith whatType
ExistenceScreening for sanctions and politically exposed personsOpenSanctions (downloaded data); the cross-check runs on its own services on Render: andeslex-screening-engine and andeslex-screening-indexIts own
ExistenceReading the public webIts own andeslex-public-web-reader service (Playwright) on RenderIts own
ExistencePublic sector signals: port reports and published schedulesTFS (public port reports)Public source
ExistenceReading documents: OCR, PDF, Office, email and archivesTesseract (OCR, Spanish and English) · pdf-parse · pdfplumber · pdfminer · pypdfium2 · mammoth · docx · word-extractor · xlsx · openpyxl · mailparser · msgreader · jszip · yauzl · franc (language)Its own
ExistenceYour email, your calendar and your files, when you connect themGoogle (Gmail and Drive) · Microsoft Graph · IMAP (imapflow)When you ask for it
Absence, decision and workÉrika’s style according to the music you shareoEmbed from Spotify or SoundCloudWhen you ask for it
Absence, decision and workQuantum: control selection and game theoryQuantum · its own andeslex-quantum-sandbox worker (Qiskit, nashpy, NumPy, SciPy)Its own
Absence, decision and workWhistleblowing channel: receives, sets deadlines and protects whoever reportsIts own: the channel runs in the An:des appIts own
Absence, decision and workData subject requests, with their legal deadlineIts own: the request and its response run in the An:des appIts own
ArtifactDocuments that circulate: reports, records, exportspdfkit · docxIts own
ArtifactPasskey confirmation of the decision the app presentsPasskey (WebAuthn), on your deviceIts own
ArtifactFingerprint of each proof of decision and, if whoever holds the authority requests it, its timestamp@noble/hashes · pgcrypto · its own andeslex-rfc3161-anchor worker against FreeTSAIts own
TransversalTraces and observabilityOpenTelemetry to LangfuseIts own
Absence, decision and workPlace and weather for the conversation with ÉrikaApple Maps (MapKit JS) · Apple Weather (WeatherKit)When you ask for it
ExistenceYour organization's data from its Apple accountApple (your organization's account, with its own permission)When you ask for it
TransversalReconciliation of each payment with its workThe payment processor (ready for SumUp)When you ask for it

Your AI

Your AI comes in with permissions

Claude via MCP (Model Context Protocol), or your code with the An:des SDK, comes in with OAuth and a per-case delegation: actions, end date and revocation. ChatGPT comes in through actions, with your organization’s read key and, to write, your session.

  1. Claude, via MCPYou delegate from your Claude; every call carries your permission and its validity.
  2. ChatGPT, via actionsThe An:des GPT reads with your organization’s read key; to write, it uses your session.
  3. The An:des SDKFor your own code, with the same keys and the same revocation.

Érika under the EU AI Act: limited risk; transparency (art. 50), human oversight (art. 14) and record-keeping (art. 12), by design.

You sign in with your passkey, with a code sent to your email, with Google or with Apple. Signing in identifies your session. When the app asks you to confirm a decision, that confirmation stays linked to the content presented. Administration accounts carry a second factor and a passkey.

Construction

How An:des is built

The tools with which An:des is built and maintained do not receive your data.

  1. GitHub and Docker Hubcode and images
  2. Coding assistants from OpenAI and Anthropicbuilding and verification
  3. Grilli Typetype license
  4. GoDaddy and NIC Chiledomains
  5. OpenTelemetry and Langfusetraces with a closed list of metadata

See how we check it

A real An:des test package, with its record. The SHA-256 fingerprint confirms the file has not changed; the provenance, the method and the result let you assess what it proves.

Identifier
CASE-001
Date
Closed on 2 November 2025, in Santiago
Version
Record and report in their version 1.0
Path
The package is assembled, its fingerprint is calculated and entered in the record, and the person responsible signs the record and the report.
Method and inputs
A compressed file of 2,257 bytes with five documents. They are the chain-of-custody checklist, the exhibits index, the validator’s methodology schema, the opinion taxonomy and the manifest with each one’s fingerprint.
Result and evidence
The package’s fingerprint matches the one in the record and both GPG signatures verify; checked again on Oct 24, 2026.
Provenance and signature
GPG signature of Franco Lavín, the person responsible, on the record and on the report: a simple electronic signature. The time is the signer’s; no third party sealed it.
SHA-256 manifest
06c339077fa5118a9bd5338a4882a0657f34c9e4eb0d0db2edbdfea8d448000dTrialPack_CASE-001.zip

How it was checked on Oct 24, 2026, in a terminal

To repeat it you need the package, the record with its signature and the responsible person’s public key. This site does not publish them today.

  1. gpg --import <the responsible person’s public key>First, the responsible person’s key in the keyring: without it, gpg answers “No public key”.
  2. shasum -a 256 TrialPack_CASE-001.zipIt returned the manifest’s fingerprint.
  3. gpg --verify ACTA_SELLADO_CASE-001.md.asc ACTA_SELLADO_CASE-001.mdIt answered “Good signature”, with the responsible person’s key.

Or in your browser

If you have the CASE-001 package, choose it: your browser calculates its SHA-256 fingerprint and compares it with the one in the record. The file never leaves your device.

Inside the PoD package

Every Proof of Decision the app delivers travels in a package you can check without An:des. It has three parts and, if a person with authority requested the timestamp, a fourth.

The record
The record of the decision: what was decided, by whom, with what authority and on what evidence.In the package pods/NNN__<id>.json
The SHA-256 fingerprint
One for every file in the package, in a list anyone can recompute.In the package checksums.sha256
The signature
Who approved it and when, confirmed with their passkey.In the package pods/NNN__<id>.json
The timestamp
The FreeTSA RFC 3161 token over the record's fingerprint and proof that it was verified. It is checked with FreeTSA's two public certificates: its certificate authority's (CA) and the TSA's.In the package anchors/NNN__<id>.tsr · .receipt.jsonVerified with cacert.pem · tsa.crt

A shortcut on your Mac

It recomputes the SHA-256 fingerprint of every file and verifies every RFC 3161 timestamp against FreeTSA's public chain. The code is in plain view: read it before you use it.

All that leaves your Mac is the download of FreeTSA's two public certificates. The script checks their fingerprints before using them.

Download the scriptSHA-256 fingerprint of the script c67741877c90f001e91c04384aae7e4af2c1b18f09d126b90df49965fee3779c

In Terminal

  1. sh verificar-pod.sh <package folder>
  2. sh verificar-pod.sh <record> <record.tsr> <record.sha256>

Without the script, with OpenSSL 3, each timestamp is verified like this:

openssl ts -verify -digest <record fingerprint> -in <record.tsr> -CAfile cacert.pem -untrusted tsa.crt

To create the shortcut

  1. Open Shortcuts and create a new shortcut.
  2. Add «Run Shell Script», paste the code and choose to pass the input «as arguments».
  3. Add «Show Result» and turn on «Use as Quick Action».
  4. In the Shortcuts settings, under Advanced, turn on «Allow Running Scripts».

Then, in the Finder, select the package folder or the record with its timestamp, and open the shortcut from Quick Actions.

The script's messages are in Spanish.

The shortcut's code
#!/bin/sh
# verificar-pod.sh · An:des · verifica un paquete PoD (Proof of Decision) en tu Mac, sin confiar en An:des.
#
# Hace dos cosas, con herramientas que trae el Mac (shasum, openssl y curl):
#   1. Recalcula la huella SHA-256 de cada archivo y la compara con la del paquete.
#   2. Verifica cada sello de tiempo RFC 3161 (.tsr) contra la cadena pública de la TSA (FreeTSA):
#      el sello es de esa huella y lo firmó la TSA con su certificado.
#
# Uso, en el Terminal o como acción de Atajos («Ejecutar script de shell», con la entrada como argumentos):
#   sh verificar-pod.sh <carpeta del paquete>            el paquete descomprimido: checksums.sha256, anchors/*.tsr
#   sh verificar-pod.sh <acta> <acta.tsr> [acta.sha256]  un acta, su sello y, si la tienes, su huella esperada
# Opciones (antes de los archivos):
#   --ca <cacert.pem> --tsa <tsa.crt>      usa estos certificados en vez de bajarlos de freetsa.org
#   --ca-sha256 <hex> --tsa-sha256 <hex>   las huellas que deben tener (por omisión, las de FreeTSA que fija An:des)
#
# Los certificados se bajan de https://freetsa.org/files/ y se comparan con las huellas de abajo antes de usarlos.
# No sube nada: lo único que sale del Mac es la descarga de esos dos certificados, cuando no los das tú.
# Salidas: 0 = comprobaciones criptográficas completas del ámbito descrito; 1 = fallo;
# 2 = comprobación parcial (faltan componentes, receta o herramientas). No acredita facultades ni eficacia jurídica.

CA_SHA256="2151b61137ffa86bf664691ba67e7da0b19f98c758e3d228d5d8ebf27e044438"
TSA_SHA256="8bfb0305bb64e2571ca507552ef3245cb1c2fee8728e0ff8689225081ea13467"
CA=""; TSA=""
while [ $# -gt 0 ]; do
  case "$1" in
    --ca) CA="$2"; shift 2 ;;
    --tsa) TSA="$2"; shift 2 ;;
    --ca-sha256) CA_SHA256="$2"; shift 2 ;;
    --tsa-sha256) TSA_SHA256="$2"; shift 2 ;;
    *) break ;;
  esac
done
[ $# -ge 1 ] || { echo "Uso: sh verificar-pod.sh <carpeta del paquete> | <acta> <acta.tsr> [acta.sha256]"; exit 2; }

FALLAS=0; PARCIAL=0; HUELLAS=0; SELLOS=0; CONTENIDOS=0
bien() { echo "✓ $1"; }
mal() { echo "✗ $1"; FALLAS=$((FALLAS + 1)); }
parcial() { echo "· PARCIAL: $1"; PARCIAL=$((PARCIAL + 1)); }
huella() { shasum -a 256 "$1" | cut -d ' ' -f 1; }
TMP=$(mktemp -d "${TMPDIR:-/tmp}/verificar-pod.XXXXXX") || exit 1
trap 'rm -rf "$TMP"' EXIT

# La cadena pública de la TSA: la que das, o la que se baja de freetsa.org; en los dos casos, con su huella fijada.
cadena() {
  if [ -z "$CA" ]; then CA="$TMP/cacert.pem"; curl -fsS --proto =https -o "$CA" https://freetsa.org/files/cacert.pem || { mal "No se pudo bajar cacert.pem de freetsa.org"; return 1; }; fi
  if [ -z "$TSA" ]; then TSA="$TMP/tsa.crt"; curl -fsS --proto =https -o "$TSA" https://freetsa.org/files/tsa.crt || { mal "No se pudo bajar tsa.crt de freetsa.org"; return 1; }; fi
  if [ "$(huella "$CA")" = "$CA_SHA256" ]; then bien "Certificado raíz de la TSA: huella $CA_SHA256"; else mal "El certificado raíz de la TSA no tiene la huella esperada"; return 1; fi
  if [ "$(huella "$TSA")" = "$TSA_SHA256" ]; then bien "Certificado de la TSA: huella $TSA_SHA256"; else mal "El certificado de la TSA no tiene la huella esperada"; return 1; fi
}

# Un sello: el TimeStampResp (.tsr) de la huella $2 (hexadecimal), firmado por la TSA de la cadena. Se verifica por partes, igual
# con el openssl que trae el Mac (LibreSSL, que no lee el atributo ESSCertIDv2 de «ts -verify») que con el de Homebrew:
#   1. la respuesta dice «Granted» y trae el sello;
#   2. la firma CMS del sello verifica hasta la raíz de la cadena, con un certificado para sellar tiempo (timestampsign);
#   3. quien firmó es el certificado de la TSA fijado (su huella SHA-256);
#   4. lo sellado es esa huella, en SHA-256.
sello() {
  HORA=$(openssl ts -reply -in "$1" -text 2>/dev/null | sed -n 's/^Time stamp: *//p')
  rm -f "$TMP/token.der" "$TMP/tst.der" "$TMP/firmante.pem"
  if openssl ts -reply -in "$1" -text 2>/dev/null | grep -q '^Status: Granted' \
    && openssl ts -reply -in "$1" -token_out -out "$TMP/token.der" >/dev/null 2>&1 \
    && openssl cms -verify -inform DER -binary -purpose timestampsign -in "$TMP/token.der" -CAfile "$CA" -certfile "$TSA" -signer "$TMP/firmante.pem" -out "$TMP/tst.der" >/dev/null 2>&1 \
    && [ "$(openssl x509 -in "$TMP/firmante.pem" -noout -fingerprint -sha256)" = "$(openssl x509 -in "$TSA" -noout -fingerprint -sha256)" ]; then
    INFO=$(openssl asn1parse -inform DER -in "$TMP/tst.der" 2>/dev/null)
    ALG=$(printf '%s\n' "$INFO" | awk '/d=3/ && /OBJECT/ { sub(/.*:/, ""); print; exit }')
    IMP=$(printf '%s\n' "$INFO" | awk '/d=2/ && /OCTET STRING/ { sub(/.*:/, ""); print tolower($0); exit }')
    if [ "$ALG" = "sha256" ] && [ "$IMP" = "$2" ]; then
      SELLOS=$((SELLOS + 1)); bien "Sello RFC 3161 de $(basename "$1"): es de la huella $2 y lo firmó la TSA (${HORA:-sin hora legible})"; return
    fi
  fi
  mal "Sello RFC 3161 de $(basename "$1"): no es de la huella $2 o no lo firmó la TSA de la cadena"
}

# Recalcular únicamente recetas con bytes originales explícitos; las demás
# permanecen parciales, nunca se sustituye una huella declarada por una prueba.
recomputar() {
  if ! command -v python3 >/dev/null 2>&1; then parcial "Falta python3 para recalcular el contenido PoD"; return; fi
  python3 - "$1" "$2" "$3" <<'PY_POD'
import hashlib,json,pathlib,sys
p=pathlib.Path(sys.argv[1]);expected=sys.argv[2];root=pathlib.Path(sys.argv[3]).resolve()
def unique(pairs):
 d={}
 for k,v in pairs:
  if k in d:raise ValueError('clave JSON duplicada')
  d[k]=v
 return d
try:
 d=json.loads(p.read_text(),object_pairs_hook=unique)
 if isinstance(d.get('datos_probados'),str):
  raw=d['datos_probados'].encode();body=json.loads(d['datos_probados'],object_pairs_hook=unique)
  assert all(k in d and d[k]==v for k,v in body.items()),'contenido y registro difieren'
 elif d.get('canonical_algo')=='sha256_raw_bytes_v1' and isinstance(d.get('canonical_event_body_pack_path'),str):
  path=pathlib.PurePosixPath(d['canonical_event_body_pack_path']);assert not path.is_absolute() and '..' not in path.parts
  f=(root/path).resolve();assert f.is_relative_to(root) and f.is_file();raw=f.read_bytes()
 else:sys.exit(2)
 assert hashlib.sha256(raw).hexdigest()==expected,'el contenido no produce la huella anclada'
except Exception:
 sys.exit(1)
PY_POD
  rc=$?
  case "$rc" in
   0) CONTENIDOS=$((CONTENIDOS + 1)); bien "$(basename "$1"): contenido recalculado contra la huella anclada" ;;
   2) parcial "$(basename "$1"): receta sin bytes reconstruibles; no se acredita integridad de contenido" ;;
   *) mal "$(basename "$1"): contenido inválido o no coincide con la huella anclada" ;;
  esac
}

if [ -d "$1" ]; then
  # El paquete: cada archivo contra checksums.sha256, y cada sello contra la huella anclada que declara su constancia de anclaje (.receipt.json).
  P="$1"
  [ -f "$P/checksums.sha256" ] || { mal "Falta checksums.sha256 en $P"; exit 1; }
  if (cd "$P" && shasum -a 256 -c checksums.sha256 >/dev/null 2>&1); then
    HUELLAS=$(grep -c . "$P/checksums.sha256"); [ "$HUELLAS" -gt 0 ] || mal "Manifiesto de huellas vacío"; bien "Huellas SHA-256: los $HUELLAS archivos de checksums.sha256 coinciden"
  else
    mal "Huellas SHA-256: algún archivo no coincide con checksums.sha256"
    (cd "$P" && shasum -a 256 -c checksums.sha256 2>/dev/null | grep -v ': OK$' | sed 's/^/    /')
  fi
  find "$P/anchors" -name '*.tsr' 2>/dev/null | sort > "$TMP/sellos"
  if [ ! -s "$TMP/sellos" ]; then parcial "El paquete no trae sellos RFC 3161 (anchors/*.tsr)"; elif cadena; then
    while IFS= read -r T; do
      R="${T%.tsr}.receipt.json"
      H=$(sed -n 's/.*"content_hash"[[:space:]]*:[[:space:]]*"\([0-9a-f]\{64\}\)".*/\1/p' "$R" 2>/dev/null | head -n 1)
      [ -n "$H" ] || { mal "$(basename "$T"): falta la huella anclada en $(basename "$R")"; continue; }
      POD="$P/pods/$(basename "${T%.tsr}").json"
      if [ -f "$POD" ]; then
        A=$(sed -n 's/.*"anchored_hash"[[:space:]]*:[[:space:]]*"\([0-9a-f]\{64\}\)".*/\1/p' "$POD" | head -n 1)
        [ "$A" = "$H" ] && bien "$(basename "$POD"): su huella anclada es la de su constancia de anclaje" || mal "$(basename "$POD"): su huella anclada no es la de su constancia de anclaje"
        recomputar "$POD" "$H" "$P"
      else mal "$(basename "$T"): falta el PoD asociado; no se omite el contraste"
      fi
      sello "$T" "$H"
    done < "$TMP/sellos"
  fi
else
  # Un acta suelta, su sello y, si la das, su huella esperada (un .sha256 de shasum o la huella en hexadecimal).
  ACTA=""; TSR=""; ESPERADA=""
  for X in "$@"; do
    case "$X" in
      *.tsr) TSR="$X" ;;
      *.sha256) ESPERADA=$(cut -d ' ' -f 1 < "$X") ;;
      *) if printf '%s' "$X" | grep -Eq '^[0-9a-fA-F]{64}$'; then ESPERADA=$(printf '%s' "$X" | tr 'A-F' 'a-f'); else ACTA="$X"; fi ;;
    esac
  done
  [ -f "$ACTA" ] || { mal "No encuentro el acta"; exit 1; }
  H=$(huella "$ACTA"); HUELLAS=1
  echo "· Huella SHA-256 de $(basename "$ACTA"): $H"
  if [ -n "$ESPERADA" ]; then [ "$H" = "$ESPERADA" ] && bien "Coincide con la huella esperada" || mal "No coincide con la huella esperada ($ESPERADA)"; else parcial "No se aportó una huella esperada independiente"; fi
  if [ -n "$TSR" ]; then cadena && sello "$TSR" "$H"; else parcial "Sin sello .tsr: solo se calculó o contrastó la huella"; fi
fi

# Enumerar solo verificaciones efectivamente ejecutadas, incluso en modo parcial.
echo "Comprobado: $HUELLAS huella(s) de archivo; $SELLOS sello(s) RFC 3161; $CONTENIDOS contenido(s) PoD recalculados."
if [ "$FALLAS" -gt 0 ]; then echo "Resultado: FALLIDO, $FALLAS comprobación(es) no verifican."; exit 1; fi
if [ "$PARCIAL" -gt 0 ]; then echo "Resultado: PARCIAL. No se acredita un paquete íntegramente verificado."; exit 2; fi
echo "Resultado: VERIFICADO dentro del ámbito enumerado. No comprueba facultades, validez jurídica ni vigencia actual."; exit 0

Back to the case card

Documents

What you sign and what you read

The five notices of the site and the service live here, versioned, in Spanish and English.

The contract is the first document An:des governs. The version presented to you and the one you accepted are both recorded, and what you accepted prevails. No material change comes in through your silence, and you can export every version.

  1. Privacy
  2. Terms
  3. Data processing agreement
  4. Security and retention
  5. Service level
  6. En español

What’s new

What changed, with its date

Substantive changes to the trust center, with their date.

  1. 2026-10-09First version of the trust center: certified infrastructure with source and date, eight controls of its own with their path and their proof, subprocessors with what each one receives, channels and construction.
  2. 2026-10-23Érika on this site and in the service, separately: what each provider does. The privacy notice moves to version 3; the data processing agreement, to version 2.
  3. 2026-10-24Each control cites its paths in the app’s code. The real case CASE-001, with its fingerprint, its signatures and a verifier in your browser.
  4. 2026-10-25The controls, reconciled with the app’s code: the key per act and its optional window, and the PoD timestamp when whoever holds the authority requests it. The subprocessors describe this site’s conversation only when the site has it.

Regulation by country

The comparable law, country by country

What your company risks in each area and what counts in its favor, with the same skeleton in every country. Every figure carries its source and its reading date; any that still needs validating against the official text says so.

Area

Compare Chile with

Loading the data for Delaware…

See Chile and Delaware, field by field (2)
FieldChileDelaware
Rule—Loading
Official source—Loading

Request access for Delaware

General information, with date and source; it does not replace local advice.

Regulatory calendar 2026–2027

The dated milestones this matrix names, by law, subject and jurisdiction, each with its source and the date it was read. You subscribe once and your calendar keeps it up to date on its own.

Subscribe: all jurisdictionsDownload the .ics file

In the United States (federal)

This matrix names no dated milestones in the United States (federal) between 2026 and 2027. You can subscribe to all jurisdictions.

All milestones, by date
  1. Oct 28, 2026Poland · Polish Act on Artificial Intelligence Systems: Artificial intelligenceFrom Oct 28, 2026, the chapters on supervision, procedure, settlements and fines of the Polish act on artificial intelligence systems apply: the Komisja Rozwoju i Bezpieczeństwa Sztucznej Inteligencji may impose the fines of Regulation (EU) 2024/1689.Official source · read on Oct 24, 2026
  2. Oct 28, 2026Spain · Royal Decree 813/2026, amending the Regulation of Law 10/2010: Money launderingFrom Oct 28, 2026, the risk analysis on which obliged entities base their internal control must take into account, at a minimum, the national risk assessment, the Union's supranational risk assessment, sectoral assessments and information on the risks of non-implementation and evasion of international financial sanctions.Official source · read on Oct 24, 2026
  3. Nov 22, 2026Ecuador · Organic Law for the Strengthening of Cybersecurity: CybersecurityBy Nov 22, 2026, the cybersecurity governing body must issue the national minimum cybersecurity standards and the regulations on incident management and notification and on the classification of critical digital infrastructure. It is a calculated date: six months after the publication of the Organic Law for the Strengthening of Cybersecurity.Official source · read on Oct 15, 2026
  4. Nov 30, 2026Peru · Supreme Decree 016-2024-JUS, Regulation of Law 29733: Personal dataFrom Nov 30, 2026, two years after the publication of the Regulation of Law 29733 (a calculated date), medium-sized companies with annual sales of more than 1700 UIT and up to 2300 UIT must appoint a Personal Data Officer when they fall within art. 37.1, items 2 and 3 (among others, processing of large volumes of data or of sensitive data). For those above 2300 UIT it has applied since Nov 30, 2025.Official source · read on Oct 15, 2026
  5. Nov 30, 2026Uruguay · Decree 224/026: Health and safety at workDecree 224/026 comes into force: the new regulation on the powers, procedure and penalties of the General Labor and Social Security Inspectorate, which repeals Decrees 371/022 and 19/023. Nov 30, 2026 is a calculated date: 60 days from its publication on Oct 1, 2026.Official source · read on Oct 24, 2026
  6. Dec 1, 2026Chile · Law 21.719: Personal dataChile’s new personal data Law 21.719 will come into force on 1 December 2026.Official source · read on Oct 24, 2026
  7. Dec 1, 2026Georgia · Law on State Procurement: Public procurementFrom Dec 1, 2026, anyone who acted in bad faith to obtain a state contract stays on the blacklist for two years, unable to take part or contract, and the ban extends to companies whose founding partner or shareholder is on the list or that share a director or representative with it.Official source · read on Oct 15, 2026
  8. Dec 1, 2026Japan · Act No. 62 of 2025, amending the Whistleblower Protection Act: Whistleblowing and retaliationFrom Dec 1, 2026, the amendment to the Whistleblower Protection Act (Act No. 62 of 2025) applies: dismissal or disciplinary action in retaliation for a report is punishable by up to 6 months' imprisonment or 300,000 yen, and the company by a fine of up to 30,000,000 yen; obstructing a report and searching for the whistleblower are also prohibited.Official source · read on Oct 24, 2026
  9. Dec 2, 2026Austria, Belgium, Bulgaria, Denmark, Estonia, European Union, France, Germany, Lithuania, and Netherlands · Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744: Artificial intelligenceFrom Dec 2, 2026, providers of AI systems that generate synthetic audio, image, video or text and that were already on the market before Aug 2, 2026 must comply with the marking under art. 50(2) of the AI Act; the obligations for the high-risk systems of Annex III apply from Dec 2, 2027.Official source · read on Oct 10, 2026
  10. Dec 2, 2026Greece · Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744: Artificial intelligenceFrom Dec 2, 2026, providers of AI systems that generate synthetic audio, image, video or text and that were already on the market before Aug 2, 2026 must comply with the marking under art. 50(2) of the AI Act; the obligations for the high-risk systems of Annex III apply from Dec 2, 2027. In Greece, removing those markings is a criminal offense (Law 5321/2026, art. 23).Official source · read on Oct 10, 2026
  11. Dec 9, 2026Moldova · Law 165/2026: Whistleblowing and retaliationFrom Dec 9, 2026, Law 165 of Jul 30, 2026 applies: it strengthens the protection of integrity whistleblowers, partially transposes Directive (EU) 2019/1937 and amends several laws, starting with the Code of Civil Procedure (art. I); its art. IV applies from Jan 1, 2027.Source · read on Oct 24, 2026Pending official validation
  12. Dec 10, 2026Australia · Privacy and Other Legislation Amendment Act 2024: Personal dataFrom Dec 10, 2026, the privacy policy of APP entities must state what personal data is used by software that makes decisions, or does something substantially and directly related to making them, that could significantly affect a person's rights or interests, and what kinds of decisions are made by that software alone or with its help (APP 1.7 to 1.9). Failing to do so is a civil contravention under s 13K, for which infringement notices can be issued.Official source · read on Oct 15, 2026
  13. Dec 30, 2026Romania · Regulation (EU) 2023/1115 (EUDR): Supply chain due diligenceFrom Dec 30, 2026, the due diligence of Regulation (EU) 2023/1115 on deforestation-free products applies (from Jun 30, 2027 for micro and small enterprises); in Romania it is enforced by the National Sanitary Veterinary and Food Safety Authority and the Ministry of Environment, Waters and Forests, and as of Oct 15, 2026 Romania had not yet set the penalties.Source · read on Oct 15, 2026Pending official validation
  14. Dec 31, 2026Albania · Law 155/2020, as amended by Law 95/2025: Climate changeBy Dec 31, 2026, greenhouse gas emission permits must be issued to all installation operators; their monitoring and reporting duties apply from when they obtain the permit and, at the latest, from Jan 1, 2027.Official source · read on Oct 24, 2026
  15. Dec 31, 2026Türkiye · Communiqué 2026/1 of the Turkish Competition Authority: Competition lawUntil Dec 31, 2026, the minimum of 302,484.86 Turkish lira applies to procedural fines under art. 16 of Law 4054, set with the revaluation rate of 25.49%; Turkish administrative fines are revalued every 1 January.Official source · read on Oct 24, 2026
  16. Jan 1, 2027Brazil · CVM Resolution 193/2023, as worded by CVM Resolution 244/2026: Sustainability reportingFrom Jan 1, 2027, a publicly held company that chooses not to file the sustainability-related financial information report must justify it in a notice to the market, no later than the date on which it files its annual financial statements with the CVM.Official source · read on Oct 24, 2026
  17. Jan 1, 2027China · Trademark Law as revised in 2026: Industrial propertyFrom Jan 1, 2027, the Trademark Law as revised by the Standing Committee of the National People's Congress on Jun 26, 2026 applies: it adds a warning and a fine of up to 100,000 yuan for bad-faith registration applications and keeps the fine for infringement of up to 5 times the illegal turnover or 250,000 yuan.Official source · read on Oct 15, 2026
  18. Jan 1, 2027Delaware · Delaware Personal Data Privacy Act, as amended by 85 Del. Laws c. 463: Personal dataFrom Jan 1, 2027, Delaware’s privacy law applies to anyone who processes data of at least 10,000 consumers (currently 35,000), or 5,000 if more than 20% of their revenue comes from selling data (currently 10,000); the data protection assessment is required from 50,000 consumers (currently 100,000); and it also reaches third parties that receive data from a controller.Official source · read on Oct 24, 2026
  19. Jan 1, 2027Finland · Kaupparekisterilaki 564/2023 (Trade Register Act): Beneficial ownershipFrom Jan 1, 2027, limited companies, cooperatives, European companies and cooperatives and branches of foreign companies must confirm each calendar year that their details in the trade register are up to date (Kaupparekisterilaki, § 23, applicable from that date under § 39). If they fail to do so despite a reminder, the register charges a default fee of 300 euros, or 600 euros for public limited companies and European companies (§ 24).Official source · read on Oct 24, 2026
  20. Jan 1, 2027Italy · Legislative Decree 125/2024, as amended by Decree-Law 95/2025: Sustainability reportingFor financial years beginning on Jan 1, 2027, the sustainability reporting of Legislative Decree 125/2024 extends to large companies that are not public-interest entities and to the other parent companies of large groups; Directive (EU) 2026/470 must be transposed by Mar 19, 2027 and may change that scope.Official source · read on Oct 15, 2026
  21. Jan 1, 2027Kazakhstan · Law 312-VIII of 2026: BriberyFrom Jan 1, 2027, the Criminal Code also punishes offering or promising a bribe, not only giving it (art. 367), and fines for administrative corruption offenses fall outside the general cap of the KoAP (art. 44(3)), under Law 312-VIII of Jun 12, 2026.Official source · read on Oct 15, 2026
  22. Jan 1, 2027Mexico · 2026 amendment to the Federal Labor Law: Health and safety at workFrom Jan 1, 2027, the maximum ordinary working week drops from 48 to 46 hours, on the gradual path to 40 hours in 2030, and the provisions on the electronic record of each worker's working hours come into force (art. 132, sec. XXXIV).Official source · read on Oct 15, 2026
  23. Jan 1, 2027Mongolia · Law on the Corporate Governance of State-Owned and Municipal Enterprises: Sustainability reportingFrom Jan 1, 2027, the law on the corporate governance of state-owned and municipal enterprises applies: their annual report must cover sustainable development and social responsibility work and non-financial risks, and the Law on Infringements fines failure to file or publish it with 5,000 units.Official source · read on Oct 15, 2026
  24. Jan 1, 2027Morocco · Law 19-20, amending Law 17-95: Corporate governanceFrom Jan 1, 2027, public limited companies that make public offerings must have at least 40% of each sex on their board of directors or supervisory board, from the next ordinary general meeting; the 30% threshold has applied since Jan 1, 2024.Official source · read on Oct 15, 2026
  25. Jan 1, 2027Norway · 2024 transitional regulation under the Regnskapsloven: Sustainability reportingFor financial years beginning on Jan 1, 2027, large companies that were not in the first phase (public-interest entities with more than 500 employees) must include the sustainability report in their management report.Source · read on Oct 15, 2026Pending official validation
  26. Jan 1, 2027Portugal · Law No. 37-A/2026: Lobbying and public officialsFrom Jan 1, 2027, the Assembly of the Republic's Registo de Transparência da Representação de Interesses (RTRI) is fully operational; those who professionally represent third-party interests must register within the following 60 days, and the penalty regime of Lei n.º 5-A/2026 applies from Jun 1, 2027.Official source · read on Oct 15, 2026
  27. Jan 1, 2027Switzerland · Federal Act on the Transparency of Legal Entities (TJPG): Beneficial ownershipPublic limited companies subject to an ordinary audit have three months from the entry into force of the transparency act (Oct 1, 2026) to enter their beneficial owners in the Transparency Register; Jan 1, 2027 is a calculated date (Oct 1, 2026 plus three months). Other companies with an ordinary audit have four months, and public limited companies without one, until Mar 1, 2027.Source · read on Oct 15, 2026Pending official validation
  28. Jan 1, 2027United Arab Emirates · Federal Decree-Law 26/2025 on Child Digital Safety: Personal dataOn Jan 1, 2027 the one-year period ends for digital platforms and internet service providers operating in the Emirates or targeting their users to comply with Decree-Law 26/2025 on child digital safety, in force since Jan 1, 2026, which prohibits processing data of children under 13 without verifiable parental consent. It is a calculated date: one year from Jan 1, 2026.Official source · read on Oct 15, 2026
  29. Jan 31, 2027Israel · Temporary Law 5784-2023 on serious cyberattacks: CybersecurityOn Jan 31, 2027 the temporary law on serious cyberattacks on digital and hosting services expires: its arts. 1 to 10, including the duty to report significant cyberattacks within 24 and 72 hours, apply until that date unless extended.Source · read on Oct 15, 2026Pending official validation
  30. Mar 19, 2027Montenegro · Law 133/2026 on Personal Data Protection: Personal dataFrom Mar 19, 2027, the new Law on Personal Data Protection (Law 133/2026) applies, with fines of up to €2,000,000 or 4% of annual worldwide turnover, and Law 79/2008 ceases to apply, except for its video surveillance rules.Official source · read on Oct 24, 2026
  31. Mar 24, 2027Ukraine · Public Procurement Law No. 4888-IX: Public procurementFrom Mar 24, 2027, the new Public Procurement Law No. 4888-IX of May 27, 2026 applies, repealing Law 922-VIII.Official source · read on Oct 15, 2026
  32. May 13, 2027India · DPDP Act 2023, notification G.S.R. 843(E): Personal dataFrom May 13, 2027, the obligations of the Digital Personal Data Protection Act, 2023 apply in India, along with fines of up to 250 crore rupees imposed by the Data Protection Board of India; on that day s.43A of the Information Technology Act is repealed.Official source · read on Oct 15, 2026
  33. May 31, 2027Colombia · External Circular 100-000020 of 2026, Superintendence of Companies: BriberyBy May 31, 2027, companies already required to have SAGRILAFT or PTEE must align their system with Chapter IX of the new Basic Legal Circular of the Superintendence of Companies (External Circular 100-000020 of Jul 2, 2026), which unifies the management of the risks of money laundering, terrorist and proliferation financing, corruption and transnational bribery.Source · read on Oct 15, 2026Pending official validation
  34. Jul 1, 2027Azerbaijan · Law 462-VIIQD, amending the Code of Administrative Offenses: CybersecurityFrom Jul 1, 2027, information infrastructure entities, including owners of internet resources and internet and hosting providers, are fined if they fail to adopt cybersecurity measures or to report cyber incidents immediately.Official source · read on Oct 15, 2026
  35. Jul 1, 2027Pakistan · SECP Order on IFRS S1 and S2, Phase III: Sustainability reportingFor financial years beginning on Jul 1, 2027, all listed companies that did not enter phases I and II, and unlisted public-interest companies registered or licensed by the SECP, must report under IFRS S1 and S2.Official source · read on Oct 15, 2026
  36. Jul 1, 2027Panama · Law 473 of 2025, as amended by Law 531 of 2026: Consumer protectionFrom Jul 1, 2027, the new rules on price information and special sales of Law 45 of 2007 apply: the total cash price must be displayed including taxes and fees, and a discount must state the lowest price of the last three months.Official source · read on Oct 15, 2026
  37. Jul 1, 2027Sweden · Act (SFS 2026:1459): Lobbying and public officialsFrom Jul 1, 2027, legal persons and sole traders who communicate with members of the Riksdag, ministers or their staff to influence a matter before the Riksdag or the Government must register with Kammarkollegiet within 30 days and report those contacts three times a year; those already doing so have 60 days to register.Official source · read on Oct 15, 2026
  38. Nov 27, 2027Paraguay · Law 7593/2025 on Personal Data Protection: Personal dataLaw 7593/2025 on personal data protection comes into force twenty-four months after its official publication, which the BACN dates Nov 27, 2025: Nov 27, 2027 is a calculated date. It creates the National Personal Data Protection Agency and fines of up to ten thousand minimum daily wages.Official source · read on Oct 15, 2026

Test drive

Access starts with a conversation

Tell us whether we take you for a co-driver lap with a demo or, better still, you drive with your data room in a one-to-five-day Bootcamp and leave with your compliance map: what is on record and what is missing.

Let’s talk about your Bootcamp

Already working with An:des?

Sign in with a passkey or with Apple

Before you start

Privacy