GlassBox Platform Privacy Notice

Effective August 11, 2026.

Operator identity: GlassBox is operated by Karthik Barma as an individual developer and is a product under Aura, an unregistered umbrella brand. Aura is not a company or legal entity.

This notice covers the generally available, free GlassBox Lite service. GlassBox performs a user-requested automated reasoning audit. It processes the question, answer, and optional rules that a user explicitly submits or selects. The gateway also handles provider event IDs and short-lived requester identifiers—such as Discord user/server IDs, Slack user/workspace IDs, Telegram user/chat IDs, GitHub sender/repository IDs, and Reddit author/subreddit IDs—for authentication, duplicate prevention, delivery, abuse prevention, and rate limiting.

Processing and sharing

The default GlassBox Lite verifier processes submitted text deterministically inside the gateway process. It does not call a paid model API or browse the web. The gateway does not pass platform user IDs, workspace/server/community names, repository names, URLs, or author metadata to the verifier. If the operator later enables an optional third-party verifier, that change and its applicable processing terms must be disclosed to users before use.

Render is the infrastructure host for the gateway and processes requests and service data as needed to provide that hosting. Its handling of infrastructure data is governed by Render's privacy policy. GlassBox does not sell submitted content or personal data.

The public MCP response contains only a derived verdict, score, counts, fixed-category findings, probe outcomes, and scope caveats. It does not echo the submitted question or answer, claim excerpts, verifier-authored evidence, timestamps, audit IDs, input hashes, session or request IDs, or other internal audit metadata. Other platform adapters may display a compact Trust Card inside the platform where the user requested the audit.

Retention

This gateway does not persist raw questions, answers, platform messages, or Trust Cards to a database or file. Submitted content and its Trust Card exist in process memory while an audit runs and, after verification, for at most five minutes while platform delivery is confirmed. It keeps provider event identifiers in memory for up to 24 hours to prevent duplicate processing and requester/tenant identifiers in memory for up to 10 minutes for rate limiting. Process memory is discarded on restart. Telegram requires explicit per-audit consent before text is sent. Platform providers may retain messages under their own policies.

Logs and security

GlassBox application logs record service status and error categories, not submitted content. Render may retain infrastructure and network logs under its own operational policies; GlassBox does not intentionally place submitted questions or answers in those logs. Provider signatures protect webhook endpoints, and the generic API requires a server-side bearer secret.

Your choices

Analysis is opt-in. Telegram consent applies to one audit and is not stored; Slack public delivery occurs only when --public is the first command argument. Do not submit confidential, regulated, or third-party content unless you have authority to do so. Because the gateway does not retain submitted content, there is normally no stored content to access, transfer, correct, or delete. You can delete the bot's visible response using the controls offered by the platform. For a data-rights request or to revoke platform authorization, email the contact below and identify the relevant platform and app installation; do not email the confidential content itself.

Contact

Questions, data-rights requests, or incident reports for the individual developer: thebarmaeffect@gmail.com. The security and incident-response process explains how confirmed platform incidents are handled.