Relay by Empyre

Relay privacy policy

Relay processes account details, the projects and OAuth clients you configure, agent identities, registered redirect URIs and scopes, authorization and audit events, usage measurements, security signals and the metadata required to reconcile card payments.

Secrets and token material are handled only for the authorization service to work and are protected with restricted service access. Relay does not need a user's password for delegated access. Retention, access controls and deletion are applied according to the type of record, security obligations and the subscription in use.

How Relay works

Relay gives AI agents delegated access without handing them a user's password or a permanent credential. Integrators add a hosted OAuth 2.1 consent flow with S256 PKCE, exact redirect matching, short-lived scoped access tokens, refresh rotation, revocation and introspection.

Relay Platform powers Continue with Relay for applications that need an agent to act for a person. Relay Identity gives an agent a verifiable identity and revocable credentials of its own. Both products keep an audit trail, share one Empyre account, and are designed to fail closed when an approval, token or client is no longer valid.

Public pages

• Relay home
• Relay developer documentation
• Simple pricing for agent auth
• Talk to the Relay team
• Relay terms of service
• Relay privacy policy
• Verifiable identity for AI agents
• Pricing for AI agent identities

JavaScript is required to sign in and use the Relay dashboard. The product information above and the linked public pages remain readable without it.