Privacy policy

Relay is a coordination tool for event and hackathon outreach. An organizer creates an event, uploads the participant email list once, and defines mail tasks with a fixed recipient, subject, and body. Invited volunteers sign in, connect their own Gmail account, select one recipient set, and send exactly one message for that set. Every address in a set is placed in BCC, so recipients never see each other.

Relay never composes, edits, or sends anything on its own. A message leaves your mailbox only when you press send in the application.

• Account information. Sign-in is handled by Neon Auth. We store the account identifier, email address, and display name it returns, plus your role (organizer or volunteer) and which events you were invited to.
• Google account information. When you connect a Gmail account, we store the Google account identifier (sub), the account’s email address, and its display name, so the interface can show you which mailbox will be used.
• Google OAuth tokens. We store the access token and, where Google issues one, the refresh token for each connected Gmail account, together with the granted scopes and expiry time. Tokens are encrypted before being written to the database.
• Event participant lists. Organizers upload CSV or XLSX files containing recipient email addresses. We store those addresses, a normalized form used for deduplication and suppression, and their per-mail-task delivery status.
• Mail task content. The fixed To address, subject, and body written by the organizer.
• Sending and activity records. For each send we record who sent it, which set and mail task it belonged to, which connected Gmail account was used, the recipient count, the timestamp, the resulting status, and any error returned by Gmail. We also keep an audit log of administrative actions such as connecting an account, creating an invitation, or adding a suppression.
• Suppressions. Email addresses that must never be contacted again, with the reason recorded.

We do not run advertising or third-party analytics trackers, and we do not build advertising profiles.

When you connect a Gmail account, Relay requests only these scopes:

• openid, email, profile — to confirm which Google account you connected and display its address in the interface.
• https://www.googleapis.com/auth/gmail.send — to send the message you explicitly chose to send, using the organizer’s fixed subject and body and the addresses in the set you selected.

Relay does not request permission to read, search, modify, label, or delete your mail, and it does not access your contacts, Drive, or Calendar. Each send is one Gmail API call for one message that you initiated. Relay does not send on a schedule and does not send in the background.

Relay’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, data obtained through Google APIs is:

• used only to provide and improve the sending features described in this policy;
• never sold, rented, or transferred for advertising, credit assessment, or lending purposes;
• never used to train generalized artificial intelligence or machine learning models;
• never read by a human, except with your explicit consent, when required to investigate a security incident or abuse report, when required by law, or when the data has been aggregated and de-identified.

We do not sell your data. We share it only with the service providers that make Relay work:

• Neon — managed PostgreSQL database and authentication.
• Google — the Gmail API, which delivers the messages you send.
• Our hosting provider — serves the application and processes requests in transit.

Within Relay, an organizer can see the participant list for their own event and the send activity of volunteers on that event. Volunteers see only the events they were invited to. Sign-in alone grants no access to any event; access comes only from an organizer’s invitation link.

We may also disclose information where required by law or to protect against fraud or abuse.

Traffic is served over HTTPS. Google OAuth tokens are encrypted with an application key before storage, and the OAuth flow uses PKCE with single-use, expiring state values. Invitation links are stored only as hashes. Sends use idempotency keys, expiring leases, and deterministic message identifiers to protect normal retries and concurrent clicks. Ambiguous provider or network failures remain visible for review before retrying.

No system is perfectly secure. If you believe an account or list has been exposed, contact us at namangeekroom@gmail.com.

• Disconnect a Gmail account. Open Gmail & history in the application and disconnect the account. Its stored tokens stop being usable immediately.
• Revoke access from Google. You can remove Relay at any time from myaccount.google.com/permissions. Revocation takes effect at Google immediately.
• Participant lists. Deleting an event deletes its participant list, its mail tasks, and their delivery records.
• Account deletion. Email namangeekroom@gmail.com from your registered address and we will delete your account and connected Gmail credentials within 30 days.
• Logs. Send activity and audit records are kept while the event exists so organizers can see what was sent and avoid duplicate outreach, and suppression entries are kept so an address that asked not to be contacted stays excluded.

If you received a message sent through Relay and want your address removed, reply to that message or write to namangeekroom@gmail.com. We will add the address to the suppression list so it is excluded from future sets. The organizer who uploaded the list is responsible for how that list was collected.

Relay is not directed at children under 13, and we do not knowingly collect their information. If you believe a child has created an account, contact us and we will remove it.

If this policy changes materially, we will update the date at the top of this page and, where reasonable, notify organizers by email. Questions, deletion requests, and privacy complaints go to namangeekroom@gmail.com, addressed to the Relay team.

See also our terms of service.