AVERZ Relay Privacy Policy

Effective date: 15 November 2026

AVERZ Relay (“Relay”) is a browser extension published by Keryex (“we”) for people with access to AVERZ, Keryex’s internal intelligence workbench. This policy explains what Relay handles and why. It covers the extension. AVERZ itself is governed by the AVERZ Terms of Use & End User Agreement and the Keryex privacy policy.

What Relay handles

Pages you choose to send. When you open Relay on a page, or use “Send page/link to AVERZ Inbox”, Relay reads that page’s address (URL), title, description, site name, canonical link and preview-image address. It sends them to AVERZ only when you press Send or choose the right-click action. You can edit or remove any field before sending.

Relay doesn’t read pages you haven’t opened it on. It doesn’t record your browsing history, and it doesn’t read page content beyond those fields.

Sign-in. You sign in through AVERZ’s own sign-in page, which uses your Keryex Discord account. Relay never sees your Discord or AVERZ password. AVERZ gives Relay tokens that work only for Relay’s functions:

• a short-lived access token, kept in the browser’s session storage;
• a refresh token, kept in the extension’s local storage.

Relay also stores your AVERZ display name and role so it can show who is signed in.

Preferences and drafts. Relay stores two settings on your device: whether to remember your last workspace, and whether to remove tracking parameters from links. While the popup is open, an unsent form is saved for that tab and deleted when you send it or close the tab.

Where the data goes

Relay sends data only to Keryex’s AVERZ server (https://averz.keryex.com). It doesn’t send data to any other party. It has no analytics, advertising or tracking code, and it loads no remote code.

In AVERZ, a sent link becomes either an item in the shared team Inbox or a Source in the workspace you chose. Other authorized AVERZ users can see it, according to AVERZ’s workspace permissions. AVERZ records who sent each link and when, and its audit log records sign-ins and changes.

How long it’s kept

On your device: Relay’s tokens stay until you sign out or AVERZ revokes access. The access token is also cleared when the browser closes. Drafts are deleted after sending or when the tab closes.

In AVERZ: links you send stay until an authorized AVERZ user dismisses or deletes them, or until their workspace is deleted. Deleted workspaces are permanently removed after 30 days. Audit records of sign-ins and changes are kept for security and accountability.

Your choices

• Sign out in Relay’s popup or Options. This deletes Relay’s tokens from your browser and revokes them in AVERZ.
• Disconnect any browser from AVERZ under Profile → Connections. AVERZ administrators can also revoke access.
• Uninstall Relay to remove everything it has stored in your browser.
• To ask about, or request deletion of, links you sent, contact us.

Security

Sign-in uses an OAuth 2 authorization code with PKCE, through AVERZ’s consent page. Tokens are sent only over HTTPS to AVERZ, rotate on every refresh, and are revoked if your AVERZ access or Discord role changes. Relay asks only for the browser permissions it needs: activeTab, scripting, storage, identity, contextMenus, and access to averz.keryex.com.

Children

Relay is a work tool for Keryex staff and isn’t intended for anyone under 18.

Changes

If we change this policy, we’ll update the effective date above, and announce material changes to AVERZ users.

Contact

Questions about this policy or about data sent with Relay: use the Keryex contact page.