Relay

Privacy Policy

Last updated: 31 July 2026

Relay is a Chrome extension that helps you run your own outreach — collecting prospects you choose on LinkedIn, predicting likely work-email addresses from public company patterns, and sending emails you compose from your own Gmail account. This policy explains what Relay accesses, what it does with it, and — importantly — what it does not do.

The short version. Relay runs in your browser and sends from your own accounts. Your prospects, templates, keys and settings are stored locally on your device. Relay has no server that receives your outreach data, and it never sells or shares your data with advertisers or data brokers.

What the extension accesses

LinkedIn pages you open — to display Relay's panel and to read the public profile information (name, headline, company, profile URL, connection distance) of prospects you add, and to perform the LinkedIn actions you configure (visit, connect, message, follow).
Your own LinkedIn network requests (read-only) — so you can verify in the dashboard that an action matches LinkedIn's current API before you run it. Relay never blocks, alters, or redirects any request.
Hunter.io — when you provide your own Hunter.io API key, Relay sends company domains to Hunter to look up email patterns and real on-file addresses.
Your Gmail account — when you connect it (see below).
An optional tracking endpoint — if you leave open/click tracking on, sent emails include a tracking pixel and click-wrapped links that call a tracking endpoint. You can self-host it or turn tracking off.

How Relay uses Google user data

Relay requests the minimum Google OAuth scopes needed to let you send email from your own Gmail:

openid and userinfo.email — used only to show you which Gmail address is currently connected. Relay does not build a profile of you.
gmail.send — used only to send the specific emails you compose and queue, at the time your cadence sends them. Relay cannot read, search, delete, or modify any message in your mailbox; the send scope grants sending only.

Authentication uses Chrome's identity API and Google's OAuth flow. Relay never sees or stores your Google password; Google issues a revocable access token that Chrome manages. You can disconnect at any time in Relay, or revoke access at myaccount.google.com/permissions.

Limited Use. Relay's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used solely to provide and improve the email-sending feature described above, is never transferred to others except as needed to provide that feature (i.e. Google's own API), is never used for advertising, and is never sold. No humans read your Google user data.

Where your data lives

Your prospects, cadence steps, email templates and attachments, your Hunter.io key, your settings, and the address of your connected Gmail account are stored locally in your browser using Chrome's storage. This data does not leave your device except to reach the endpoints you direct it to: LinkedIn, Hunter.io, Google, and (if enabled) your tracking endpoint.

Data security

All network calls (Google, Hunter.io, tracking) are made over HTTPS (TLS).
Gmail access uses a short-lived OAuth token handled by Chrome's identity API; no password is ever stored, and no long-lived Google credential is written to disk by Relay.
Your outreach data is stored locally and is never uploaded to any server operated by us.
You can clear all stored data at any time by removing the extension.

Tracking (optional)

If open/click tracking is enabled, emails you send include a 1×1 pixel and click-wrapped links that record open and click events against a random, per-install identifier. This is used only to badge ✓ Opened / ↗ Clicked in your own dashboard. You can switch tracking to a self-hosted endpoint or turn it off entirely. Disclose tracking to your recipients where the law requires it.

What Relay does not do

No selling or sharing of your data with advertisers or data brokers.
No reading of your mailbox, contacts, or LinkedIn messages.
No central server that stores your prospects or the content of your emails.
No tracking of your browsing outside the features described here.

Your responsibilities

Generated email addresses are predictions from public company patterns, not verified addresses. Automating LinkedIn is against LinkedIn's User Agreement. You are responsible for using Relay lawfully, including compliance with anti-spam laws (such as CAN-SPAM and GDPR) and the terms of the services you connect.

Changes

We may update this policy; material changes will be reflected in the "Last updated" date above.

Contact

Questions about this policy: manan.hiren.shah@gmail.com.