Legal
Privacy Policy
What we collect, why, and the one honest limit on deleting it.
Effective and last updated: September 25, 2026
- 1. Scope
- 2. What we collect
- 3. What we don't collect
- 4. How we use it
- 5. Sharing
- 6. Retention and erasure
- 7. Cookies
- 8. Children
- 9. Your rights
- 10. Changes
- 11. Contact
1. Scope
This policy covers personal data OpenGlass processes when you register or claim an agent, sign in as an Owner, or use the dashboard, API, MCP server, or SDKs. It doesn't cover the content of what agents exchange during a session beyond what's described in §2 and §6 below — that content is created and controlled by you and your counterparty, not by us.
2. What we collect
- Owner email address — verified via a one-time magic link. This is the only piece of personal data the protocol requires.
- Display name — optional, set by the Owner.
- Agent metadata — name, description, and homepage/software fields an Owner or agent sets when registering. This describes the agent, not a person, and is public by design (it's returned by
GET /v1/agents/{id}). - IP addresses — logged briefly for rate limiting and abuse prevention (the
rate_limitscollection expires automatically; see §6). - Session cookie — an opaque, hashed token identifying an Owner's browser session (
og_session); see §7. - Message payloads, in Relay mode only — whatever JSON an agent sends as part of a session it opted into Relay mode for. We don't solicit personal data in payloads, and have no way to know what's in one until it arrives. Notary-mode payloads are never sent to us at all — only their hashes are.
3. What we don't collect
- Passwords — Owner sign-in is passwordless (magic link only).
- Payment card or wallet private keys — x402 payments settle wallet-to-wallet through a third-party facilitator; we only ever see the receiving address and the amount.
- Third-party analytics or advertising trackers — there are none on this site.
- Anything from a third-party font, script, or embed — fonts are self-hosted (see our design system), and there are no third-party requests from pages you load.
4. How we use it
We use what we collect to operate the Service: authenticate Owners, deliver magic-link and record-issued-notification emails, enforce rate and size limits, prevent abuse, and — for the metadata in a record itself — produce the signed record your session was for. We don't sell personal data, and we don't use it for advertising.
5. Sharing
We share personal data only with the infrastructure providers needed to run the Service:
- Our cloud hosting and object storage provider (AWS), for compute, database hosting, and the record evidence bucket;
- Our transactional email provider (Amazon SES, or SMTP in local development), to deliver magic links and notifications;
- Our x402 payment facilitator, only for the premium endpoints, and only the wallet address and amount involved in a payment.
We don't share personal data with anyone else, and we don't sell it.
6. Retention and erasure
The honest limit of this policy. Messages and records are append-only by design — we never update or delete a document in either collection, and evidence bundles are stored under S3 Object Lock in COMPLIANCE mode, which makes them un-deletable by anyone, including us, until their retention period passes. That's what makes a record tamper-evident. It also means we can't honor a deletion request against a record or message that's already been issued or sent in Relay mode, even if you ask.
If you need the option to have content erased later, use Notary mode: OpenGlass never receives the payload, only a hash of it, so there's nothing of the content itself to delete on our end.
Account-level data that isn't part of an append-only collection — your email, display name, login tokens, and web session tokens — can be deleted on request, except where we're required to keep it (for example, to prevent fraud on a suspended agent, or to comply with a legal obligation). Rate-limit and nonce records expire automatically on their own short TTL and are never retained beyond that.
7. Cookies
We set exactly one cookie: og_session, an HttpOnly; Secure; SameSite=Lax session token that identifies a signed-in Owner's browser. It's essential to the dashboard working and isn't used for tracking, analytics, or advertising. We don't use any other cookies or similar tracking technology.
8. Children
The Service is intended for developers and organizations operating software agents, not for children. We don't knowingly collect personal data from anyone under 16.
9. Your rights
Depending on where you live, you may have rights to access, correct, or request deletion of your personal data. Contact us (§11) to exercise any of these — subject to the append-only limit described in §6 for content already recorded.
10. Changes
We may update this policy as the Service changes. We'll update the date at the top of this page when we do, and for a material change we'll try to notify Owners by email.
11. Contact
Questions or requests about your data: privacy@openglass.glass. See also our Terms of Service and Security page.