KIRA privacy

Browsing alone does not create a KIRA activity record.

KIRA starts logging interaction data only after you send a text message or activate the microphone. This page explains what is processed, what may be stored, and how long it is scheduled to remain.

Browsing and conversation records

While you browse without interacting, KIRA may prepare a short on-screen highlight from the public page in your browser, but it does not send or save a KIRA browsing record.

After your first text message or microphone activation, KIRA may store final user messages or speech transcripts, final KIRA replies, and a bounded page reference consisting of the page path, title, and short highlight. Records share a random per-tab session identifier.

When database storage is configured, those records are scheduled to expire after about 90 days. Expiration uses DynamoDB TTL, which deletes asynchronously, so removal may occur after the exact expiry time.

Voice and raw audio

Microphone access is requested only when you press the microphone button. Live audio is carried through LiveKit and processed by speech-recognition services so KIRA can respond in real time.

This site does not persist raw microphone audio. It may store the final transcript and final reply as conversation records after voice interaction begins.

Optional contact details

If you submit the interest form, its name, email, interest, message, and page path may be stored under the same session as your KIRA interaction. This lets Levon understand the context of your inquiry. The site's database copy is scheduled to expire after about 365 days, subject to the same asynchronous TTL deletion.

The submitted contact details and page path are also sent to Formspree for notification delivery. Formspree applies its own retention terms; the site's 365-day schedule does not control Formspree's copy. Read the Formspree privacy policy.

Service boundaries

LiveKit: Carries the realtime text and audio session and routes it to the KIRA agent.
Deepgram / LiveKit Inference: Turns speech into text. The default worker uses Deepgram through LiveKit Inference; a deployment may instead use a direct Deepgram connection.
Google Gemini: Generates KIRA’s reply from Levon’s curated portfolio context and the bounded current-page reference.
ElevenLabs: Turns KIRA’s reply into speech when voice output is used.
AWS DynamoDB: Stores interaction and contact records when database storage is configured, with asynchronous TTL expiry schedules.
Formspree: Receives the contact details and page path only when you submit the optional interest form, so Levon can be notified.

Browser storage and your choices

A random session ID remains in per-tab session storage. Pending interaction records may remain there for retry until the site accepts them or the tab session ends. They are not placed in cross-session local storage.

You can browse without messaging KIRA, keep the microphone off, or disconnect an active KIRA session at any time.

To request access to or deletion of a stored interaction or contact submission, use the Contact page. Include the approximate date and any email used so the record can be located.

KIRA service availability and storage configuration can vary by deployment. Opening this page or the KIRA panel does not itself activate those services.