Privacy Policy

That is a statement about what hYYa receives, not a claim that the app never uses the network. hYYa Vault works with no internet connection, and every AI feature runs on your device. Signed out, with the online features off, hYYa Vault makes no network connection at all — not at startup, not at rest. Each path below opens only because you signed in or switched something on:

• Starting the app while signed in — if you have signed in to a hYYa Cloud account, hYYa Vault refreshes that session with hYYa’s own servers when it launches, so it knows your plan is still current. This goes to hYYa, not to a third party. It is the only path here that repeats on its own, and it stops when you sign out.
• Downloading an AI model — when you install a local model, hYYa Vault downloads it from Hugging Face. When you ask it to check for new models, it reads the model list from GitHub (GitHub Pages). Both are file and list downloads; no personal data is sent.
• Signing in to a hYYa Cloud account — optional, and the gate for the online features below. hYYa Vault then reads your account’s plan so it knows what to offer you. Your on-device conversations are not sent. Signing in to any plan, including hYYa Cloud Free, enables Web Search, Connections and cloud DataLens; BYOK requires hYYa Cloud Ultra.
• Switching to hYYa Cloud — an explicit switch you make. Anything you do in hYYa Cloud mode is covered by section 2 below, including cloud DataLens.
• Web Search — optional, and off unless you turn it on. Your search terms are sent to hYYa, which runs the search and returns the results — the request carries the query only. Your documents and your conversation are never sent with it.
• Local Connections — optional. Gmail and Google Calendar content is fetched directly from Google to your device. See the next section.
• Your own provider API key (BYOK) — optional, and available on hYYa Cloud Ultra. Used only for the online features you choose to run under your own key.

This list is checked by watching what the app actually does on the network, not only by reading its code — that is how the launch-time path above was found and added. hYYa keeps it current as the app changes. It is not a claim that the operating system itself never uses the network on the app’s behalf: your platform’s own app-store, update and crash-reporting behaviour is governed by Apple, not by hYYa. If you want to confirm any of this rather than take hYYa’s word for it, turn the online features off and watch the app’s network activity, or run it with Wi-Fi off.

hYYa Vault's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• Data accessed via Local Connections is retrieved directly from Google to your device and processed by an on-device AI model.
• It is never transmitted to or stored on hYYa servers, never used for advertising, and never shared with anyone.
• Connected-account content is never included in any web search query or any other outbound request from the app.
• You can revoke access at any time in your Google Account settings or from within the app.

• Email address — stored in Supabase to manage your account and send sign-in links.
• Conversation messages — routed via OpenRouter to the AI model provider that generates your response (e.g. Anthropic, Google, xAI, DeepSeek). These providers do not use your messages to train their models. If you add your own provider API key (BYOK), that key is encrypted at rest on hYYa’s servers (AES-256), never shown again after you save it, and used only to send your messages directly to that provider under your own key — across chat and DataLens. You can remove a saved key at any time in Settings → API Keys.
• DataLens documents — if you upload documents to a DataLens, their text is stored in Supabase and sent to Google’s embedding API so hYYa can search and reason over them. Used only to power your DataLens.

• Vercel — hosts the hYYa web app and processes your requests in transit; it does not retain your conversation content.
• Supabase — hYYa’s database and file storage: your account, conversations, memory, and DataLens documents are stored here, protected by row-level security.
• OpenRouter — routes your hYYa Cloud conversation messages to the AI model provider that generates your response. OpenRouter does not retain your prompts, and hYYa configures routing to exclude providers that train on your data.
• AI model providers (such as Anthropic, Google, xAI, DeepSeek, and Moonshot) — receive your message content in order to generate the response. They are not sent your hYYa account identity, and do not use your messages to train their models.
• Google — for DataLens, generates embeddings for the documents you upload and reads (OCR) any images you add, so they can be searched. Used for that processing only.
• Composio — only if you turn on Connections: securely stores the authorization for the apps you connect (e.g. Gmail, Calendar, Outlook, Notion, Drive) and relays read-only data into your chat at your request. SOC 2 Type 2; tokens are encrypted and isolated per user. Inactive unless you connect an app.
• Google (Gemini Live) — only if you use voice: real-time voice runs through Google’s Gemini Live service. Audio streams directly between your browser and Google and does not pass through hYYa’s servers; the voice assistant also uses Google Search to answer real-time questions. Active only during a voice session.
• Polar — processes subscription payments as Merchant of Record. No card data touches hYYa servers.
• GitHub — hosts the list of on-device AI models hYYa Vault can install (GitHub Pages). Contacted when you ask hYYa Vault to check for new models. It receives the request for that list, and nothing about you.
• Hugging Face — hosts the on-device AI models themselves. Contacted when you install one. It receives the model download request, and nothing about you.
• Resend — delivers account and billing emails (sign-in links, subscription notices).