Privacy engineering
How secure enclaves work
Major AI providers promise not to read your prompts. Here's how public-key cryptography, secure enclaves, and hardware attestation let garlic.ai prove that instead of asking you to trust it.
Privacy engineering
What private AI chat should hide
A practical engineer's view of what AI chat privacy should protect: plaintext, saved history, and the trust boundary between the browser and the server.
Product privacy
Saved on device is a product decision
Why garlic.ai keeps chat history local by default and treats sync as a privacy tradeoff, not a missing feature.
Search
Private search needs a smaller promise
How garlic.ai thinks about AI chat with web search: useful context, narrow claims, and no pretending metadata does not exist.
Try garlic.ai
Private chat, without the transcript trail
Browser-side encryption. Signed-in access. Saved conversations stay on this device.