@mavea/mavea 1.0.7

package/dist/fonts/export/families/space-grotesk.css

@@ -0,0 +1,12 @@
+/* Space Grotesk — SIL OFL 1.1 (see ../../LICENSE.txt). Variable weight, one file covers 400-700 —
+ * the Terminal document skin's display+body weight range. */
+@font-face {
+  font-family: 'Space Grotesk';
+  font-style: normal;
+  font-weight: 400 700;
+  font-display: swap;
+  src: url('../../space-grotesk-var-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}

package/dist/fonts/export/families/spectral.css

@@ -0,0 +1,52 @@
+/* Spectral — SIL OFL 1.1 (see ../../LICENSE.txt). Not published as a variable font by Google
+ * Fonts, so each weight/style the Research document skin uses ships as its own static file. */
+@font-face {
+  font-family: 'Spectral';
+  font-style: normal;
+  font-weight: 400;
+  font-display: swap;
+  src: url('../../spectral-400-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Spectral';
+  font-style: normal;
+  font-weight: 500;
+  font-display: swap;
+  src: url('../../spectral-500-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Spectral';
+  font-style: normal;
+  font-weight: 600;
+  font-display: swap;
+  src: url('../../spectral-600-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Spectral';
+  font-style: italic;
+  font-weight: 400;
+  font-display: swap;
+  src: url('../../spectral-400-italic-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Spectral';
+  font-style: italic;
+  font-weight: 500;
+  font-display: swap;
+  src: url('../../spectral-500-italic-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}

package/dist/fonts/fonts.css

@@ -0,0 +1,141 @@
+/* Self-hosted fonts (latin subset) — no render-blocking third-party CSS, works offline.
+ * Every family below is SIL OFL 1.1 (see LICENSE.txt): free for commercial and
+ * non-commercial use. Variable files cover the declared weight ranges. */
+@font-face {
+  font-family: 'Hanken Grotesk';
+  font-style: normal;
+  font-weight: 100 900;
+  font-display: swap;
+  src: url('/fonts/hanken-grotesk-var-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'IBM Plex Mono';
+  font-style: normal;
+  font-weight: 400;
+  font-display: swap;
+  src: url('/fonts/plex-mono-400-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'IBM Plex Mono';
+  font-style: normal;
+  font-weight: 500;
+  font-display: swap;
+  src: url('/fonts/plex-mono-500-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'IBM Plex Mono';
+  font-style: normal;
+  font-weight: 600;
+  font-display: swap;
+  src: url('/fonts/plex-mono-600-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Newsreader';
+  font-style: normal;
+  font-weight: 200 800;
+  font-display: swap;
+  src: url('/fonts/newsreader-var-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+@font-face {
+  font-family: 'Newsreader';
+  font-style: italic;
+  font-weight: 200 800;
+  font-display: swap;
+  src: url('/fonts/newsreader-var-italic-latin.woff2') format('woff2');
+  unicode-range:
+    U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329,
+    U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
+}
+
+@font-face {
+  font-family: 'Lora';
+  font-style: normal;
+  font-weight: 400 700;
+  font-display: swap;
+  src: url('/fonts/lora-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Lora';
+  font-style: italic;
+  font-weight: 400 700;
+  font-display: swap;
+  src: url('/fonts/lora-var-italic-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Space Grotesk';
+  font-style: normal;
+  font-weight: 300 700;
+  font-display: swap;
+  src: url('/fonts/space-grotesk-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Bodoni Moda';
+  font-style: normal;
+  font-weight: 400 900;
+  font-display: swap;
+  src: url('/fonts/bodoni-moda-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Bodoni Moda';
+  font-style: italic;
+  font-weight: 400;
+  font-display: swap;
+  src: url('/fonts/bodoni-moda-400-italic-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Source Serif 4';
+  font-style: normal;
+  font-weight: 200 900;
+  font-display: swap;
+  src: url('/fonts/source-serif-4-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Libre Franklin';
+  font-style: normal;
+  font-weight: 100 900;
+  font-display: swap;
+  src: url('/fonts/libre-franklin-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'IBM Plex Sans';
+  font-style: normal;
+  font-weight: 100 700;
+  font-display: swap;
+  src: url('/fonts/ibm-plex-sans-var-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Instrument Serif';
+  font-style: normal;
+  font-weight: 400;
+  font-display: swap;
+  src: url('/fonts/instrument-serif-400-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Instrument Serif';
+  font-style: italic;
+  font-weight: 400;
+  font-display: swap;
+  src: url('/fonts/instrument-serif-400-italic-latin.woff2') format('woff2');
+}
+@font-face {
+  font-family: 'Archivo';
+  font-style: normal;
+  font-weight: 100 900;
+  font-display: swap;
+  src: url('/fonts/archivo-var-latin.woff2') format('woff2');
+}

package/dist/index.html

@@ -0,0 +1,117 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover" />
+    <!--
+      Content-Security-Policy — defense-in-depth behind the app's input sanitization. It
+      allow-lists exactly the origins Mavéa uses, so even if markup ever slipped past the
+      sanitizers it could neither load a script nor exfiltrate to an attacker origin.
+        script-src   self + wasm-unsafe-eval (Silero VAD / onnx WASM). Shiki, jsPDF,
+                     modern-screenshot, mediabunny, and pdf.js are ordinary bundled dependencies
+                     (self-hosted, code-split, dynamic import()) — they need no CDN allowance.
+        style-src    'unsafe-inline' is required — React inline styles + the design-system CSS vars
+        connect-src  self covers the same-origin /llm·/tts·/stt·/search·/pdf·/actions proxies and
+                     VAD's same-origin assets; the provider + Wikipedia hosts cover a direct baseUrl;
+                     api.github.com
+                     covers Ripple's read-only, browser-direct GitHub intake (public repos keyless,
+                     private with the user's own token). It ALSO has to repeat every image host
+                     below: the raster export (modern-screenshot) inlines a cross-origin image by
+                     fetch()ing it, so a host that img-src can paint but connect-src cannot fetch
+                     renders on screen and then comes out BLANK in the exported PDF/PPTX — which is
+                     how map tiles and photos silently vanished from exports. No new trust: these
+                     origins are already trusted to paint pixels.
+        img-src      data:/blob: (object-URL images) + the photo / map-tile allow-list
+        media-src    blob: — Kokoro TTS mp3 plays from an object URL
+        worker-src   blob: — the VAD / onnx worker
+        frame-src    self — the PDF reader may frame a same-origin PDF/proxy URL; its render
+                     boundary rejects every external or active-scheme frame source
+      This meta tag is the ONE place the policy is defined, so it travels with the app to any static
+      host. `frame-ancestors` is the one directive a meta tag cannot carry — send it as a response
+      header (X-Frame-Options / CSP frame-ancestors) from whatever actually serves dist/.
+    -->
+    <meta
+      http-equiv="Content-Security-Policy"
+      content="default-src 'self'; script-src 'self' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: blob: https://upload.wikimedia.org https://commons.wikimedia.org https://images.unsplash.com https://images.pexels.com https://cdn.pixabay.com https://images-assets.nasa.gov https://www.nasa.gov https://*.basemaps.cartocdn.com; connect-src 'self' https://en.wikipedia.org https://api.anthropic.com https://api.openai.com https://generativelanguage.googleapis.com https://openrouter.ai https://api.x.ai https://api.github.com https://api.search.brave.com https://api.tavily.com https://upload.wikimedia.org https://commons.wikimedia.org https://images.unsplash.com https://images.pexels.com https://cdn.pixabay.com https://images-assets.nasa.gov https://www.nasa.gov https://*.basemaps.cartocdn.com; media-src 'self' blob:; worker-src 'self' blob:; frame-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'"
+    />
+    <title>Mavéa · Talk to AI. See what it means.</title>
+    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+    <!-- Self-hosted fonts (public/fonts, OFL): no third-party request, and the app works offline.
+         Preload only the compact UI face. Newsreader is display:swap and loads at normal priority;
+         preloading its 129 kB variable file competed with the shell on constrained connections. -->
+    <link
+      rel="preload"
+      href="/fonts/hanken-grotesk-var-latin.woff2"
+      as="font"
+      type="font/woff2"
+      crossorigin
+    />
+    <link rel="stylesheet" href="/fonts/fonts.css" />
+    <!-- Boot splash — painted straight from this static document, so a slow connection or an old
+         machine sees Mavéa's pulsing orb instead of a blank white page while the bundle downloads
+         and parses. Root() removes #boot on its first commit (src/main.tsx); if the bundle never
+         arrives the splash simply stays, which beats a blank page. The CSP above allows inline
+         STYLE but no inline script, so this block is the only boot-time styling possible. Colors
+         are literals because no token CSS has loaded yet; each mirrors its token: #0a0e15 =
+         --surface-default (tokens-base.css — dark is the documented startup default, theme.ts),
+         #f3f5fb = light --surface-default (light-theme.css), #6e8cff = --presence. The orb copies
+         SurfaceFallback's (rootBoundary.css) exactly, so the splash → React hand-off is invisible. -->
+    <style>
+      #boot {
+        position: fixed;
+        inset: 0; /* full-viewport cover — zero layout shift when it is removed */
+        z-index: 9997; /* one under SurfaceFallback (9998) so React's own loading UI wins */
+        display: flex;
+        align-items: center;
+        justify-content: center;
+        background: var(--surface-default, #0a0e15);
+      }
+      /* applyTheme stamps data-theme at module scope, before React renders — light users are
+         corrected the instant the bundle executes, not at first paint. */
+      :root[data-theme='light'] #boot {
+        background: var(--surface-default, #f3f5fb);
+      }
+      .boot-orb {
+        width: 28px;
+        height: 28px;
+        border-radius: 999px;
+        background: radial-gradient(
+          circle at 35% 30%,
+          color-mix(in oklab, #6e8cff 70%, white 12%),
+          #6e8cff
+        );
+        /* opacity + scale only — compositor-cheap even on the weakest hardware */
+        animation: boot-pulse 1.1s ease-in-out infinite;
+      }
+      @keyframes boot-pulse {
+        0%,
+        100% {
+          transform: scale(0.85);
+          opacity: 0.6;
+        }
+        50% {
+          transform: scale(1);
+          opacity: 1;
+        }
+      }
+      @media (prefers-reduced-motion: reduce) {
+        .boot-orb {
+          animation: none;
+          opacity: 0.85;
+        }
+      }
+    </style>
+    <script type="module" crossorigin src="/assets/index-y8GL67bB.js"></script>
+    <link rel="modulepreload" crossorigin href="/assets/chunk-BVpWp9h4.js">
+    <link rel="modulepreload" crossorigin href="/assets/jsx-runtime-DaSxXjOY.js">
+    <link rel="modulepreload" crossorigin href="/assets/react-BQSORdFI.js">
+    <link rel="modulepreload" crossorigin href="/assets/lazyRetry-D50B1UMY.js">
+    <link rel="stylesheet" crossorigin href="/assets/index-CepQEz75.css">
+  </head>
+  <body>
+    <div id="boot" role="status" aria-busy="true" aria-label="Loading Mavéa">
+      <div class="boot-orb" aria-hidden="true"></div>
+    </div>
+    <div id="root"></div>
+  </body>
+</html>

package/dist/legal/DISCLAIMER.md

@@ -0,0 +1,16 @@
+# Mavéa Disclaimer
+
+Effective: July 16, 2026
+
+Mavéa uses probabilistic AI systems and can be wrong.
+
+- AI-generated text, citations, calculations, classifications, transcriptions, translations, and visualizations may be inaccurate, incomplete, misleading, offensive, or outdated.
+- A citation, confidence label, validation step, or polished visualization does not guarantee that a claim is correct.
+- Verify important information with authoritative sources and qualified professionals before relying on it.
+- Mavéa does not provide medical, legal, financial, tax, accounting, safety, engineering, mental-health, or other professional advice. Do not use it for emergencies or as the sole basis for high-impact decisions.
+- You are responsible for the prompts, files, audio, accounts, credentials, and actions you provide or authorize.
+- Model, search, speech, hosting, OAuth, media, and connected-action providers are independent third parties. Their terms, privacy practices, availability, and charges apply. All costs are your responsibility.
+- Credentials and relevant content travel through the deployment operator's same-origin proxy before reaching selected providers. The operator can access them in transit.
+- Confirmed actions may create external communications, account changes, charges, or other consequences. Review every action and use test accounts and backups where appropriate.
+
+To the maximum extent permitted by law, Mavéa is provided as is and as available, without warranties, and you assume the risk of using it. The [Terms of Use](./TERMS.md) and [PolyForm Noncommercial License 1.0.0](./LICENSE) contain the controlling warranty disclaimers and liability limitations. This summary does not expand or replace them, and no document can waive rights or liabilities that applicable law does not allow to be waived.

package/dist/legal/LICENSE.txt

@@ -0,0 +1,75 @@
+# PolyForm Noncommercial License 1.0.0
+
+<https://polyformproject.org/licenses/noncommercial/1.0.0>
+
+Required Notice: Copyright (c) 2026 Akash Maitra and Aryan Chordia
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose. However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license).
+
+## Distribution License
+
+The licensor grants you an additional copyright license to distribute copies of the software. Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license).
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software. For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, is use for a permitted purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else. These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice. Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.

package/dist/legal/PRIVACY.md

@@ -0,0 +1,127 @@
+# Mavéa Privacy Notice
+
+Effective: July 19, 2026
+
+This notice describes the current, unmodified local and self-hosted Mavéa software. It does not describe a future hosted service. Local-first does not mean every feature stays on your device: connected features send data through the deployment to third parties you choose. If a person or organization deploys Mavéa for others, that operator must provide any additional privacy notices and controls required for its deployment.
+
+## 1. Who handles your information
+
+The Mavéa Maintainers publish software. They do not receive your prompts or browser-local data merely because you install or run it. The person or organization hosting the copy you use is the **deployment operator**. When you self-host, you control that deployment and its logs, storage, configuration, and provider accounts.
+
+The unmodified project has no Mavéa user-account system, first-party cloud database, advertising network, product-analytics service, telemetry, or conversation-retention service. Normal network requests can still be visible to the deployment host, infrastructure providers, and the third-party services described below. A modified or separately hosted deployment may behave differently, and its operator is responsible for disclosing any additional collection, logging, accounts, analytics, retention, or sharing it adds.
+
+The current repository does not set analytics or advertising cookies and does not include first-party usage tracking. A modified deployment that adds cookies, analytics, advertising, or other tracking must disclose and manage those technologies separately.
+
+## 2. Information kept in your browser or deployment
+
+Depending on the features you use, browser storage may contain:
+
+- conversations, saved canvases, bookmarks, memory items, and session history;
+- courses, lessons, flashcards, quiz progress, Ripple analyses, and dashboards;
+- preferences such as theme, performance, visual richness, voice, and setup state;
+- drafts, tracked items, presentation settings, and recent feature state;
+- provider and model configuration;
+- remembered provider, search, or optional GitHub credentials; and
+- short-lived demo, tour, route, and in-progress session data.
+
+Saved content is encrypted in browser storage only where the relevant feature and browser support it. Course data, mastery and progress, some Ripple data and analysis caches, preferences, metadata, and fallback content can be stored in ordinary local storage or IndexedDB. Anyone who can use your unlocked device or browser profile, and malicious extensions or same-origin code, may be able to access browser data.
+
+Because this browser data is encrypted to this specific browser, it does not carry over to a different browser, an incognito window, or another device. You can export a backup file of your dashboards, memory, flashcards, saved canvases, map, and courses, and import it elsewhere to move that data. The backup is plain, unencrypted JSON under your control, so store and share it carefully; it deliberately excludes your provider and search keys. Importing a backup merges into existing data and never deletes it, and importing a file you did not create can add content from that file — import only backups you trust.
+
+Browser and operating-system caches may retain application assets and optional voice models. The actions gateway may store connected-service credentials and configuration on the deployment operator's machine.
+
+## 3. Credentials and connected-service tokens
+
+Provider and search keys stay in memory until reload unless you choose Remember. When supported, Remember encrypts them with a non-extractable, device-bound browser key and stores ciphertext locally. Without the required browser cryptography, the unmodified app keeps them session-only rather than writing plaintext. Settings exports exclude provider and search keys.
+
+Keys are decrypted when needed and pass through the deployment's same-origin proxy to the provider you selected. The proxy and its host can technically access credentials and content in transit. Browser encryption does not protect against an active compromise of the device, browser, extension, deployment, proxy, or provider.
+
+Optional GitHub and Google connections can store access tokens, refresh tokens, or repository settings in the actions gateway or its host configuration. The unmodified gateway writes persisted OAuth tokens to an owner-readable host file and keeps limited audit metadata, not request bodies or provider response text. Whoever runs the gateway controls that file, its backups, logs, deletion, and security.
+
+The unmodified gateway has no separate Mavéa user accounts. On a shared deployment, everyone allowed to use action features may act through the deployment operator's connected GitHub or Google account. Use a dedicated, least-privilege gateway and do not expose it to people who should not share those permissions.
+
+## 4. Prompts, files, code, and generated content
+
+Text you type or paste, conversation context, remembered facts, attached files, extracted document text, images, repository content, diffs, search queries, and feature instructions may be sent through the deployment to the model, search, or connected provider needed for the feature you request. Responses and generated content return through the deployment to your browser.
+
+Prism and Synthesis stage and extract supported files locally where possible, but relevant content can still be sent for analysis. Ripple can parse code locally before optional model enrichment sends relevant code or diffs. Local staging is not a promise that later analysis remains local.
+
+## 5. Voice, microphone, speech, and reels
+
+If you enable listening, the browser captures microphone input and its speech-recognition implementation converts speech to text. Depending on the mode, browser, and operating system, audio may be processed by a remote browser-vendor service or sent through the deployment's configured speech-to-text endpoint. Recognized transcripts may then be sent to your selected model provider.
+
+Spoken answers send narration text to the configured text-to-speech service. Reel rendering and encoding are performed in the browser, but optional model direction and narration use the selected providers. A finished export leaves Mavéa only when you save, publish, or send it to a destination you choose.
+
+## 6. Services that can receive data
+
+According to the feature and configuration you choose, recipients can include:
+
+- Google Gemini, Anthropic Claude, OpenAI, xAI Grok, OpenRouter, or another model endpoint you configure;
+- configured web-search providers and Wikipedia;
+- your browser vendor's speech-recognition service and the configured speech-to-text or text-to-speech service;
+- GitHub, Google Calendar, or another configured action destination;
+- map-tile, font, image, and other content hosts such as OpenStreetMap, CARTO, Google Fonts, Wikimedia, or configured image sources used by a view you open;
+- a notification relay URL you configure, which can receive dashboard titles, alert labels, values, units, and timestamps;
+- the jsDelivr content-delivery network, from which the local command-line server downloads version-pinned voice-recognition assets once on first voice use and then serves them from its own cache; and
+- the deployment host, reverse proxy, network, and infrastructure providers.
+
+Those parties process data under their own terms and privacy notices. They may retain requests, use data for abuse prevention or service improvement, or process it in other countries according to your account settings and their policies. The Maintainers do not control those practices. Review each recipient's terms, retention, training, security, location, and deletion settings before use. Mavéa cannot delete data retained by those providers.
+
+## 7. Why information is processed
+
+Information is processed only as needed to:
+
+- provide the feature you request and return results;
+- save state and preferences on your device;
+- authenticate to providers and connected services you configure;
+- perform an external action after the required confirmation;
+- protect a deployment, enforce limits, diagnose failures, and prevent abuse; or
+- comply with law or protect rights and safety where legally required.
+
+The unmodified project does not sell personal information or use it for cross-context behavioral advertising. A deployment operator must separately disclose any different purpose it introduces.
+
+## 8. Retention and deletion
+
+Memory-only values disappear on reload. Session storage generally remains until the tab or browser session ends. Local storage and IndexedDB remain until a feature removes the item, you use an available clear, forget, or reset control, you clear site data, or the browser evicts it. Some session history is capped and expires, but many course, progress, dashboard, memory, and Ripple records have no automatic expiration. Clearing all browser site data is the broadest local deletion control. Removing browser data does not delete copies already sent elsewhere.
+
+Gateway tokens remain until disconnected or removed by the gateway operator. Server, proxy, infrastructure, browser-vendor, and provider retention depends on the relevant operator, logs, backups, account settings, and third-party policy. Contact those parties for deletion of data they control and revoke credentials at the issuing service.
+
+Exports, downloaded files, backups, browser sync, system backups, provider records, and recipients of anything you share must be deleted separately.
+
+## 9. Your controls and privacy rights
+
+You can reduce or remove data by:
+
+- leaving Remember off and using restricted, revocable provider keys;
+- using Mavéa's forget, delete, disconnect, reset, and clear controls where offered;
+- clearing this site's local storage, session storage, IndexedDB, cache, and permissions;
+- revoking model, search, GitHub, Google, and other connected credentials;
+- turning off microphone access and avoiding voice features;
+- not uploading information you do not want sent to a selected provider; and
+- contacting the deployment operator or relevant provider about data they control.
+
+Depending on where you live, you may have legal rights to access, correct, delete, restrict, object to, or obtain a copy of personal information held by a deployment operator. The Maintainers cannot retrieve browser-local or provider-held data they do not possess.
+
+## 10. Sensitive, confidential, and regulated information
+
+Mavéa is not designed as a system of record for health, financial, student, employment, government-identifier, biometric, trade-secret, or other regulated information. Do not submit such information unless you have authority, have assessed every recipient, and have put any legally required contracts and safeguards in place. A disclaimer does not make a deployment compliant with HIPAA, FERPA, GDPR, financial-services rules, workplace duties, or another regulatory regime.
+
+Do not submit children's data or another person's personal, confidential, privileged, or regulated information unless you have appropriate authority and a lawful basis. Mavéa is not a confidential or privileged channel.
+
+## 11. Security
+
+Mavéa uses safeguards such as browser encryption for supported stored data, content sanitization, same-origin request boundaries, confirmation for connected actions, and restricted gateway token-file permissions. No safeguard is perfect. Do not treat local storage or encryption as a guarantee, and do not use Mavéa as a password manager or secret vault.
+
+You are responsible for device security, access controls, backups, proxy configuration, least-privilege provider credentials, and connected-account security. Do not expose a local proxy, development server, or actions gateway to an untrusted network.
+
+## 12. Children
+
+Mavéa is intended for adults and is not directed to children. Do not allow anyone under 18 to use connected model, upload, microphone, or action features or submit personal information through Mavéa. If you believe a child's information reached a deployment or provider, contact that operator and the relevant provider promptly and revoke any affected connection.
+
+## 13. Changes, business transfers, and contact
+
+Material changes to this notice require an updated effective date and, where appropriate, a new in-product acceptance version. A deployment operator must provide its own identity and contact details where applicable law requires them.
+
+If a project, deployment, or relevant assets are reorganized, financed, sold, merged, or transferred, information actually controlled by the relevant operator may be disclosed to advisers and transferred to a successor as permitted by law. Browser-local and provider-held information that the operator does not possess cannot be transferred by that operator. A successor must describe its identity and any materially different data practices.
+
+For a hosted copy, contact the person or organization that gave you access. For the public repository, use the Mavéa GitHub issue tracker for non-sensitive questions. Do not put personal or confidential information in a public issue. Report security concerns through [SECURITY.md](./SECURITY.md).