Browser chat
Browser chat works anonymously. A random HttpOnly guest cookie is used only to separate abuse-limit counters. When you sign in, browser-local history is partitioned by WorkOS account. Supported prompt and attachment content is encrypted in your browser before it crosses Garlic’s application edge. Garlic can still observe routing, timing, selected model, protocol metadata, and ciphertext size.
Saved chats are encrypted by your browser and stored in IndexedDB on the current device. Vanish chats remain in memory for the current tab. Garlic does not sync either transcript mode to its servers. Browser storage is best-effort and can be cleared or evicted by the browser, operating system, or user, so it is not a permanent backup.
Account partitioning prevents accidental crossover through Garlic’s interface. It does not protect an unlocked device from same-origin script compromise, a privileged browser extension, developer tools, or malware; those can access the browser context or the non-extractable key handle while the account is open.
Information we process
- Account information, such as your email address and profile details, used to authenticate account and API features.
- API request metadata, including account or organization identity, credential identifier, endpoint, model, privacy mode, status, token totals, latency, and estimated cost. Garlic retains this ledger for approximately 30 days.
- Billing records needed to sell and administer prepaid API credits.
- Coarse product events such as chat starts, response outcomes, model choice, and whether a feature was used. Analytics excludes prompts, responses, search queries and results, filenames, chat identifiers, URLs, referrers, raw errors, IP addresses, and browser user agents. For browser events, Garlic sends PostHog a one-way hash of the existing random guest identifier so it can measure anonymous retention for up to 30 days. PostHog does not receive the raw guest identifier or create a person profile.
- Messages you send to our contact address and the information needed to respond.
Search and rate limits
If you enable web search, the query text is sent through Garlic to Exa. Garlic drops cookies, user agent, referrer, and other request headers before that request and does not retain or cache the query or results server-side. Saved mode includes search activity and source cards in the encrypted on-device chat; Vanish mode does not persist them. Abuse limits use a one-way HMAC of either the signed-in account ID or the random guest identifier, not the client IP address.
Service providers
Garlic uses service providers for specific parts of the service:
- Cloudflare for hosting, delivery, and network protection.
- PrivateMode for confidential AI inference.
- WorkOS for sign-in, sessions, organization API keys, and agent identity.
- Neon for personal API-key digests and the 30-day inference metadata ledger. Raw personal API keys are shown once and never stored.
- Autumn and Stripe for API billing and payment processing.
- PostHog for the restricted analytics described above.
- Exa for optional web search.
Garlic does not sell personal information or use it for targeted advertising. Providers process information only for the functions described here and under their own privacy terms.
Your choices
- Sign out to prevent another account on the device from opening your encrypted local chat partition through Garlic’s interface.
- Keep web search off when you do not want a query sent to Exa.
- Delete saved chats or clear Garlic’s site data in your browser.
- Enable Do Not Track or Global Privacy Control to disable Garlic’s product analytics.
- Ask to access, correct, or delete account information by emailingcontact@garlic.ai. We may need to verify your identity before acting on a request.
Retention, security, and changes
Account, billing, and support records are kept only as long as needed to provide the service, meet legal obligations, resolve disputes, and prevent abuse. Garlic uses technical and organizational safeguards, but no online service can guarantee absolute security.
Material changes will be reflected on this page with a new effective date. Questions about this notice can be sent tocontact@garlic.ai.