Demo Privacy Notice

Version: 1.0 Effective Date: 2026-06-19

1. Who is the controller

The data controller is Waldemar Szemat, established in Chile. Contact for any privacy question or data-subject request: waldemar@szemat.pro.

2. Which laws apply

This demo is operated under a layered jurisdiction stack:

Ley 19.628 (Chile) is the primary governing law, as the controller is established in Chile.
GDPR applies for data subjects in the European Union / EEA.
CCPA / CPRA applies for California residents.

3. Lawful basis

The lawful basis for processing is your explicit, granular consent, recorded before processing. Consent is collected through un-bundled checkboxes; you give a separate, optional consent for marketing contact, which is never required to use the demo and may be withdrawn at any time. We do not rely on legitimate interest for the personal data described here.

4. The two data planes

This demo processes data in two distinct planes. Be clear about which is which.

Chat plane (your conversation with the agent). The text you type is sent to third-party AI providers in the United States on every turn to generate responses, embeddings, reranking, and judge scores. Direct identifiers (email, phone, government IDs, No record of your conversation is kept: the Demo writes no chat to any database, so your turns exist only while the conversation is open and are discarded when it ends. Direct identifiers (email, phone, government IDs, card numbers) are redacted before the turn is used for anything other than producing the reply. Names are deliberately not redacted — they are retained in-thread for personalization for the duration of the conversation and are never written to telemetry spans, citations, or evaluator rationales. Raw IP addresses and raw User-Agent strings are not stored.
Contact / funnel plane (your demo-key request). When you request a demo key, the email, name, and organization you submit are stored as real personal data to process your request and, only if you separately opt in, to contact you about a paid pilot.

5. Sub-processors and cross-border transfer

Your chat content is processed by named third-party sub-processors, all located in the United States. Using the demo therefore involves a cross-border transfer of your chat input content to the United States on every turn. The canonical list — Groq, OpenAI, Anthropic (chat and judge); Voyage AI (embeddings and reranking); ElevenLabs (voice, only when enabled), and ElevenLabs Realtime (live realtime speech-to-text over the backend WebSocket proxy, only when the realtime voice feature is used) — is maintained together with the Terms of Use and Consent so the disclosure cannot drift between documents.

The demo also runs on Google Cloud Run (application hosting, US region) and stores operational data (demo keys, redacted interactions, consent records, lead-capture rows) in Supabase (managed PostgreSQL, US East region — us-east-2, Ohio). The documentation site’s “Request access” form additionally sends the name, work email, organization, and interest you submit to Web3Forms (a US form-to-email relay) to deliver that request by email; Web3Forms is used only for that form.

Voyage AI carries a train-by-default posture on the data it receives: it licenses the submitted (redacted) query text for model training by default unless an org-admin opt-out is enabled (not enabled for this demo). The live telemetry sub-processor is Langfuse Cloud (Langfuse GmbH, part of ClickHouse); only redacted span attributes are exported to it. Unlike Voyage, Langfuse does not use the submitted data to train models; it encrypts data in transit and at rest, retains it only for the configured 30-day retention window, and processes it under a GDPR Data Processing Addendum (SOC 2 Type II, ISO 27001).

Executing the Langfuse/ClickHouse Data Processing Addendum and confirming the hosting region remain preconditions before operating on real data.

This is bounded by the demo’s synthetic-only inputs and by redaction of direct identifiers and telemetry span content before egress; enabling the Voyage opt-out and executing the vendor DPAs are preconditions for operating on real data.

6. Retention

Contact details submitted with a demo-key request, where you have given the separate marketing opt-in, are retained indefinitely until you request deletion (“indefinite-until-deletion”). Consented contacts are not auto-deleted; deletion on request is always honored.
Contact details submitted without the marketing opt-in are retained only as long as needed to process the request, up to a ceiling of 12 months, after which they are deletable.
Redacted chat records are operational demo data and are deletable on request via the data-subject-rights controls.

7. Your rights

You may exercise your data-subject rights — access, export, deletion, and opt-out — from within the demo session, or by contacting waldemar@szemat.pro. Deletion resolves your subject across all demo records and is honored on request.