Security
Last updated: 2026-08-10
Short version
Glassy is built to keep private work boring: secure transport, JWT auth stored in your browser's localStorage, local AI for supported actions, and no model training on your notes. Your Second Brain corpus stays on your server; only the specific query leaves your machine.
Data at rest
Hosted account data lives in the Glassy application environment and follows the retention rules published in our privacy policy. We keep storage claims here tied to the supported release state instead of naming infrastructure that may change.
Data in transit
Connections to Glassy use HTTPS. Production routing sits behind managed TLS, and we keep transport security checks in the deployment checklist before public rollout.
Local AI
Supported AI actions run on your device when your browser and hardware allow it. Those local prompts and context stay local.
Optional cloud AI
If you opt in to a cloud model, the request leaves your device for that action. We keep cloud AI explicit so privacy-sensitive work can stay local.
Second Brain / MCP data flow
Your knowledge base corpus — bookmarks, notes, documents, voice transcripts, and Obsidian vault files — is indexed on your own server. When you query from Claude Desktop or Cursor via the MCP server, only the search results relevant to your query are returned. Your full corpus never leaves your server. The MCP server uses DNS-rebinding protection, tier-based rate limiting (120/hr Free, 1,200/hr Pro), and the official @modelcontextprotocol/sdk v2.
Authentication
Auth is a signed JWT stored in localStorage['glassy-dash-token'] on the app.glassy.fyi origin. There is no server-side session cookie. The only cookie Glassy sets is glassy_cookie_consent — a client-side preference store for your consent choices, not used for authentication, and not essential for the app to function.
Rate limiting as a security control
Tier-based rate limits protect against abuse and ensure service availability. Free accounts: 120 MCP queries per hour. Pro accounts: 1,200 per hour. Clear accounts: 1,200 per hour with additional cloud AI allocation.
Backups & retention
Account deletion is permanent within 30 days. Encrypted backups are purged on the same schedule.
Disclosure
Report a vulnerability to [email protected]. PGP key on request. We aim to respond within 72 hours and credit reporters in the changelog when they want credit.