Your inbox stays yours.
Relay retrieves an email code only when you ask. This page explains the information involved in that lookup.
How Relay gets your email
You choose one or more ways in Settings. Relay reads email only when you click Find & fill or Check again.
Forwarding (recommended). You create a Gmail filter that forwards emails containing words such as “code” or “verification” to a private Relay address. Relay’s mail receiver, hosted on Google Cloud, accepts mail for that address only from Google’s mail servers and passes it to Relay’s service, which keeps each forwarded email for ten minutes and then deletes it. Gmail’s forwarding-confirmation email is kept for up to a day so Settings can show its code. Relay never has access to the rest of your mailbox. Delete the filter or forwarding address in Gmail to stop.
App password. A Google app password can read, send and delete all mail in your account. Relay stores it only in this browser’s extension storage and sends it to Relay’s service only during a lookup. The service signs in to Gmail over IMAP, reads the three newest received messages from the last ten minutes, and signs out; it does not store the password or the messages. Revoke it any time on Google’s App passwords page.
Google sign-in (preview). For invited testers, Relay’s service uses your connected accounts’ Google access tokens to verify that you authorized Relay and reads the latest three messages in each connected Gmail inbox.
In every case Relay reads text, sender, recipient, subject and receipt time. Attachments are ignored. Email is never sent, deleted, or marked as read.
The extension also reads the current website’s hostname, page title, and text near the code field. It does not send your browsing history, cookies, passwords, or other tabs.
How the code is found
The recent messages from your connected sources and page context are sent to OpenAI’s API. Only messages from the last ten minutes are considered. OpenAI’s model picks the code that matches the page, and Relay fills it. If no code matches, the field is left unchanged. Relay does not click Submit, though a website may continue automatically when its code is entered.
Google Messages and SMS
SMS is an optional, unofficial connection using a desktop helper. Google Messages session cookies and pairing keys stay in the helper’s local configuration directory; they are never sent to Relay’s hosted service or OpenAI. Unlike Gmail OAuth, these are sensitive browser session credentials, not a narrowly scoped read-only permission. You explicitly import a local session file and confirm pairing on your phone. The extension does not request browser cookie access.
When you choose SMS and click Find & fill, the helper inspects recent inbox conversations locally and returns up to five incoming text messages from the last ten minutes. Their text, sender and receipt time, together with page context, are sent to Relay’s service and OpenAI for selection. Attachments, outgoing messages and group chats are excluded. No SMS content is saved or logged by Relay. Pairing credentials persist locally with restricted file permissions; this is not a promise of encrypted storage at rest.
Turn off SMS processing in Settings to stop SMS lookups. Disconnect Messages attempts to remove the phone pairing and deletes local credentials. If remote removal fails, also remove Relay under Device pairing in Google Messages. Gmail disconnection does not delete the helper’s pairing credentials. Delete any session export file yourself after pairing.
What is saved
Relay saves your connected email addresses, your private forwarding address, any app passwords you add, and your Email or SMS preference in this browser. Temporary lookup status and additional accounts’ access tokens stay in the browser session. Additional accounts renew silently using your Google session; if access expires, reconnect the affected account in Settings. Relay’s service does not store codes, Google tokens, app passwords, or page text, and the application does not log them. The only email content it stores is forwarded email, for ten minutes, as described above.
Netlify hosts Relay’s service and Google Cloud hosts its mail receiver; both may retain infrastructure metadata, such as IP addresses and request times. OpenAI processes the evidence sent for selection under its own terms and privacy practices. This page does not promise a retention period for those providers.
Your controls
Remove an app password or forwarding in Settings, and also revoke the app password at Google or delete the Gmail filter and forwarding address. Use the Disconnect control beside a Google sign-in account to revoke its access. You can also remove Relay’s access from your Google account at any time.
Relay does not sell email data or use it for advertising. Its email access is used only to provide the code-filling feature you requested, and email is never used to train models.
Provider information
Last updated October 21, 2026.